Skip to content

Commit 40962bb

Browse files
authored
Merge pull request #1609 from json-schema-org/gregsdennis/datetime-rfc-9557
incorporate RFC 9557 time zone extension into 'date-time' format
2 parents e929dbc + d6aba7b commit 40962bb

File tree

1 file changed

+8
-7
lines changed

1 file changed

+8
-7
lines changed

specs/jsonschema-validation.md

Lines changed: 8 additions & 7 deletions
Original file line numberDiff line numberDiff line change
@@ -397,22 +397,23 @@ custom format values.
397397
These attributes apply to string instances.
398398

399399
Date and time format names are derived from
400+
[RFC 9557, section 4.1](https://www.rfc-editor.org/info/rfc9557) which extends
400401
[RFC 3339, section 5.6](https://www.rfc-editor.org/info/rfc3339). The duration
401-
format is from the ISO 8601 ABNF as given in Appendix A of RFC 3339.
402+
format is from ISO 8601 as formalized into ABNF by RFC 3339 Appendix A.
402403

403404
- *date-time*: A string instance is valid against this attribute if it is a
404-
valid representation according to the "date-time" ABNF rule (referenced above)
405+
valid representation of the "date-time-ext" rule in RFC 9557
405406
- *date*: A string instance is valid against this attribute if it is a valid
406-
representation according to the "full-date" ABNF rule (referenced above)
407+
representation according to the "full-date" ABNF rule in RFC 3339
407408
- *time*: A string instance is valid against this attribute if it is a valid
408-
representation according to the "full-time" ABNF rule (referenced above)
409+
representation according to the "full-time" ABNF rule in RFC 3339
409410
- *duration*: A string instance is valid against this attribute if it is a valid
410-
representation according to the "duration" ABNF rule (referenced above)
411+
representation according to the "duration" ABNF rule in RFC 3339 Appendix A
411412

412413
Implementations MAY support additional attributes using the other format names
413414
defined anywhere in that RFC. Implementations SHOULD NOT define extension
414-
attributes with any name matching an RFC 3339 format unless it validates
415-
according to the rules of that format.[^5]
415+
attributes with any name matching an RFC 3339, RFC 9557, or ISO 8601 format
416+
unless it validates according to the rules of that format.[^5]
416417

417418
[^5]: There is not currently consensus on the need for supporting all RFC 3339
418419
formats, so this approach of reserving the namespace will encourage

0 commit comments

Comments
 (0)