It’s just a standard specification. The standard 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.
The document specifying the usage of ISO8601 doesn't use ISO8601
Submitted 1 year ago by qaz@lemmy.world to mildlyinfuriating@lemmy.world
https://lemmy.world/pictrs/image/6277126d-302a-4396-9947-826a89e1d3f7.png
Comments
witty_username@feddit.nl 1 year ago
Neon@lemmy.world 1 year ago
From 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.
bjoern_tantau@swg-empire.de 1 year ago
VPN shouldn’t change anything because it works off of the browser settings.
qaz@lemmy.world 1 year ago
Nope, it stays the same.
anemoia_one@lemmynsfw.com 1 year ago
Just chiming in to say fuck ISO, all my homies use rfc
(In this case rfc 3339)
strawberry@kbin.run 1 year ago
what's wrong with ISO?
zik@lemmy.world 1 year ago
ISO uses a weird separator 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
anemoia_one@lemmynsfw.com 1 year ago
They aren’t open standards like rfc, you have to pay to access them:
It’s similar to the UN in membership, and in my opinion the member states should pay to allow the standards to be open
cfi@lemmy.world 1 year ago
Well, in their defense, when they were writing the document there was no standard yet