The document specifying the usage of ISO8601 doesn't use ISO8601
The document specifying the usage of ISO8601 doesn't use ISO8601
Well, in their defense, when they were writing the document there was no standard yet
85It's just a standard specification. The standard specification doesn't specify which standards it itself should use. That will have been done (and should be done) in a different document. Imagine if each standard specification also references all the standards it employs. That would lead to unnecessarily bulky documents.
Additionally, the keywords informatiemanagement and metadata indicate that this standard is intended for use in information management and metadata settings. Not necessarily applicable to a web front-end setting34From a programming Perspective:
They probably use a JS Library that automatically converts the Date to the Format that is the default in your Region. Try it out with a VPN in the US or in Japan and you'll see different Dates I'd bet.
4VPN shouldn't change anything because it works off of the browser settings.
5Nope, it stays the same.
1
Just chiming in to say fuck ISO, all my homies use rfc
(In this case rfc 3339)
3what's wrong with ISO?
2They aren’t open standards like rfc, you have to pay to access them:
https://www.iso.org/store.html
It’s similar to the UN in membership, and in my opinion the member states should pay to allow the standards to be open
7ISO uses a weird separator 'T' between the time and the date. eg. 2018-04-01T15:20:15.000-0700
RFC3339 can have a space instead which is a bit more readable: eg. 2020-12-09 16:09:53+00:00
6