Skip to content

Clarify that the time format shouldn't include leap seconds #1644

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
wants to merge 1 commit into
base: main
Choose a base branch
from
Open

Clarify that the time format shouldn't include leap seconds #1644

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
13 changes: 11 additions & 2 deletions specs/jsonschema-validation.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -402,14 +402,23 @@ Date and time format names are derived from
format is from ISO 8601 as formalized into ABNF by RFC 3339 Appendix A.

- *date-time*: A string instance is valid against this attribute if it is a
valid representation of the "date-time-ext" rule in RFC 9557
valid representation of the "date-time-ext" rule in RFC 9557. This SHOULD
allow and validate published leap seconds. See RFC 3339, section 5.7.
- *date*: A string instance is valid against this attribute if it is a valid
representation according to the "full-date" ABNF rule in RFC 3339
- *time*: A string instance is valid against this attribute if it is a valid
representation according to the "full-time" ABNF rule in RFC 3339
representation according to the "full-time" ABNF rule in RFC 3339. This MUST
NOT include leap seconds.[^3]
- *duration*: A string instance is valid against this attribute if it is a valid
representation according to the "duration" ABNF rule in RFC 3339 Appendix A

[^3]: The `time` format represents a time value that is independent of any
specific date, such as a scheduled time of day or a measured duration. Because
there is no date, it is not well suited for capturing a moment in time. For
that, you would need `date-time`. Because `time` isn't for capturing a moment in
time, leap seconds don't make sense because leap seconds only apply to
specific dates. See RFC 3339, section 5.7.

Implementations MAY support additional attributes using the other format names
defined anywhere in that RFC. Implementations SHOULD NOT define extension
attributes with any name matching an RFC 3339, RFC 9557, or ISO 8601 format
Expand Down
Loading