Neat!
ISO 8601 would be perfect if it didn't require a T as a delimiter between date and time, which negatively affects readability and just looks really ugly.
Neat!
ISO 8601 would be perfect if it didn't require a T as a delimiter between date and time, which negatively affects readability and just looks really ugly.
RFC mandates a timezone info, so at minimum a trailing Z. Both standards aren't perfect.
The formats most programming languages support match more with what I'd like to see. Both rfc support, support for the sane parts of iso, and also support for leaving out the reduntant parts of rfc or iso.
Html as shown there still has some odd stuff, I'd suspect the average of datetime parsers of various common languages are gonna yield results best matching to common sane usage.
The lack of date interval on mainstream languages hurts.
But yeah, except for that ISO 8601 is way too complex and bureaucratic. It's way too complex and bureaucratic for intervals too, but we don't have a better standard on the wild.
Isn't that usually done with time difference objects? Either you subtract two datetimes, or you take one datetime and one length of time.
What does iso notation offer here?
How do you encode it into a JSON? Or parse from user input. Or write in the command line?
That's what there isn't a good option.