Skip to content
Discussion options

You must be logged in to vote

For RFC 3339, a space character is technically allowed (see the note): https://datatracker.ietf.org/doc/html/rfc3339#section-5.6

CBOR's definition is indeed more precise, but it is narrower and stricter than RFC 3339. So even if Jiff offered a "strict RFC 3339" mode, it wouldn't be strict enough for your use case. What you need is an RFC 4287 conformant parser, which Jiff does not provide either.

Note also that parsing into a timestamp allows probably even more than you want, since it's technically RFC 9557 conformant and thus includes time zone annotation strings. See this example: https://docs.rs/jiff/latest/jiff/fmt/temporal/struct.DateTimeParser.html#example-parsing-a-timestamp-from-a…

Replies: 1 comment

Comment options

You must be logged in to vote
0 replies
Answer selected by AudaciousAxiom
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Category
Q&A
Labels
None yet
2 participants