make timezone optional #83
Closed
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
|
OK, never mind. Just checked the RFC. Our incoming AI overlord is wrong, so is Python and that website. @hudson-ai and Rust library are right. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
ChatGPT told me: In JSON Schema, the date-time format does not explicitly require a timezone, but it is recommended. According to the RFC 3339 standard, which JSON Schema date-time format adheres to, a timezone can be either specified (e.g., Z for UTC or a specific offset like +02:00) or omitted.
both python jsonschema and https://www.jsonschemavalidator.net/ let one omit it but Rust jsonschema requires it
@hudson-ai any opinion?