strictProperties for date-time formatMinimum and formatMaximum

[avrilvg]

I'm having problems with Json Schema Validator when I'm trying to validate date-time value between interval of time [2013-11-17T00:00Z, 2015-11-17T00:00Z] I have this Json Schema:

{
  "strictProperties": true ,
  "type": "object",
  "properties": {
    "data": {
      "type": "object",
      "properties": {
        "exampleDate": {
          "format": "date-time",
          "formatMinimum": "2013-11-17T00:00Z",
          "formatMaximum": "2015-11-17T00:00Z"
        }
      }
    }
  },
  "required": [
    "data"
  ]
}

And with this json always out is as valid json:

{
    "data": {
        "exampleDate": "2010-11-17T00:00:00Z"
    }
}

But as you can see, this json is not valid because of the date, it is out of valid range.

I've tested in online tools http://www.jsonschemavalidator.net/, http://jsonschemalint.com/draft4/# and with com.github.fge:json-schema-validator:2.2.6. I thougth in order to enable v5 options, should be enough put strictProperties as true (as here https://github.com/fge/json-schema-validator/wiki/v5:-strictProperties), but is not working. Could someone help me please? Maybe I missing some configuration besides strictProperties? some step?. Thanks in advance =)

[fge]

Hello,

It is just that those two keywords are not implemented. Note that I don't maintain the project anymore, but there are examples of how to add your own keywords.

In this case though you're going to have a hard time because those two keywords are not independent of one another, in fact they even require that a format also be present. Argh.

[Zilev]

@fge I see, thanks for clarification.

I have a question please (maybe should I open other issue?), since date-time is following ISO 8601 https://en.wikipedia.org/wiki/ISO_8601, then the following examples of formats should be accepted for json schema validaror, should not?

Date: 2016-03-05
Combined date and time in UTC: 2016-03-05T06:24:57+00:00
2016-03-05T06:24:57Z
20160305T062457Z
Week: 2016-W09
Date with week number: 2016-W09-6
Ordinal date: 2016-065

in http://json-schema-validator.herokuapp.com/ only accepts as valid date format this two:

Combined date and time in UTC: 2016-03-05T06:24:57+00:00
2016-03-05T06:24:57Z

the others are validated as failure:

[ {
  "level" : "error",
  "schema" : {
    "loadingURI" : "#",
    "pointer" : "/properties/example_date"
  },
  "instance" : {
    "pointer" : "/properties/example_date"
  },
  "domain" : "validation",
  "keyword" : "format",
  "attribute" : "date-time",
  "message" : "string \"20160305T062457Z\" is invalid against requested date format(s) [yyyy-MM-dd'T'HH:mm:ssZ, yyyy-MM-dd'T'HH:mm:ss.SSSZ]",
  "value" : "20160305T062457Z",
  "expected" : [ "yyyy-MM-dd'T'HH:mm:ssZ", "yyyy-MM-dd'T'HH:mm:ss.SSSZ" ]
} ]

Is ok this behavior? Or maybe I misunderstood something? Thanks in advance =)

[fge]

@Zilev the validator is right to complain; the format is very strict, and the lack of dashes, in your year day for instance (that is 20160305 instead of 2016-03-05) is enough for the format to be considered invalid.

[Zilev]

@fge but as 2016-03-05 as 20160305 are considered invalid and both are expressed according to ISO 8601. Isn't it true?

[fge]

@Zilev draft v4 only defines "date-time" and this format expects a full ISO 8601 date; specifically, as the draft mentions (see here), a date format should be valid according to the date-time specification as mentioned here. Which has to include the time, full date and time zone. So this error, again, is to be expected.

[drwharris]

I note the same issue and found that it is case sensitive. "T" needs to be "t" and "Z" needs to be "z".

[huggsboson]

can you see if #235 fixes your issues?