2 ms·
> ...everyone is inventing their own incompatible representation, can be various ISO string formats... If only we had some sort of international body to standa
by roenxi 6y ago
> ...everyone is inventing their own incompatible representation, can be various ISO string formats...
If only we had some sort of international body to standardise these representations. This and the original articles "JSON has no comments [and this is how you do a comment in JSON]" undermine the complaint on a technical basis.
String with an ISO standard datetime is perfectly reasonable. And quite standard. Use UTC+0 where possible.
- tingletech 6y agoCCYY-Www-dd and CCYY-ddd are part of the same ISO "standard" that CCYY-MM-dd are from
- Const-me 6y ago> String with an ISO standard datetime is perfectly reasonable The standard defines more than one format. Another thing, because it’s not on the spec, people went creative. It’s too late to fix I’m afraid, some widely used APIs already have these seconds in their JSONs.
- dragonwriter 6y agoThe same thing happened with XML, XML Schema and it's datatype support was after the fact of XML popularity, same as JSON Schema, which already solves this for JSON where adopted, with respect to JSON. While adoption takes time, the fact that you don't even realize that XML had this problem (far worse than JSON with dates) demonstrates that it's not too late for JSON schema to solve it for JSON.
- Const-me 6y ago> demonstrates that it's not too late Back in nighties' and early 2000-s the landscape was different. Now there're too many internet connected things that aren't a PC (phones, tablets, home appliance, cars, etc.) who run native code which consumes these JSON APIs. Some of these things aren't upgradeable, many of them aren't easily upgradeable.
- SamWhited 6y agoThe problem isn't that there is no standard date time format, it's that there is no standard way to represent the standard date time formats (plural) in a JSON document.