Turns out I’m an RFC 3339 guy through and through. I thought I was ISO 8601, but I’m just not. Every so often you learn something new about yourself. Today is one of those days.
I mean, I have no end of respect for all those good ISO 8601 people out there, but if it’s not in RFC3339, it’s not for me. Unless it’s that ambiguous but pretty stuff that’s only in the html living standard bubble.
RFC 3339 has less ambiguities, see https://ijmacd.github.io/rfc3339-iso8601/
What a lovely webpage.
Turns out I’m an RFC 3339 guy through and through. I thought I was ISO 8601, but I’m just not. Every so often you learn something new about yourself. Today is one of those days.
I mean, I have no end of respect for all those good ISO 8601 people out there, but if it’s not in RFC3339, it’s not for me. Unless it’s that ambiguous but pretty stuff that’s only in the html living standard bubble.
Sure, but that’s also iso8601:
https://www.rfc-editor.org/rfc/rfc3339
What exactly does it mean to be a “profile” of ISO-8601?
I’m just making it up as I type, but I’d say it’s within the iso frame but more specific
RFC3339 allows certain things that ISO8601 doesn’t, like leaving out the T
Right … what makes it a “profile” exactly?
From what I can find they define a profile as
How is it a subset if it actually contradicts the standard? ( by using a space instead of T or no separator between date and time)
Yeah, I prefer a space or underscore instead of the T, much easier to read.
[email protected]