Nah, ISO is a shit organization. The biggest issue is that all of their “standards” are blocked behind paywalls and can’t be shared. This creates problems for open source projects that want to implement it because it inherently limits how many people are actually able to look at the standard. Compare to RFC, which always has been free. And not only that, it also has most of the standards that the internet is built upon (like HTTP and TCP, just to name a few).
In any case, ISO-8601 is a garbage standard. P1Y is a valid ISO-8601 string. Good luck figuring out what that means. Here’s a more comprehensive page demonstrating just how stupid ISO-8601 is: https://github.com/IJMacD/rfc3339-iso8601
if i am not wrong, it is because essentially both are same (slight differences in what is allowed and what is not, https://github.com/IJMacD/rfc3339-iso8601), but RFC is more free as in freedom
Said no-one ever?
EDIT: thanks for informing me i now retract my position
Nah, ISO is a shit organization. The biggest issue is that all of their “standards” are blocked behind paywalls and can’t be shared. This creates problems for open source projects that want to implement it because it inherently limits how many people are actually able to look at the standard. Compare to RFC, which always has been free. And not only that, it also has most of the standards that the internet is built upon (like HTTP and TCP, just to name a few).
Besides that, they happily looked away when members were openly taking bribes from Microsoft during the standardization of OOXML.
In any case, ISO-8601 is a garbage standard.
P1Yis a valid ISO-8601 string. Good luck figuring out what that means. Here’s a more comprehensive page demonstrating just how stupid ISO-8601 is: https://github.com/IJMacD/rfc3339-iso8601if i am not wrong, it is because essentially both are same (slight differences in what is allowed and what is not, https://github.com/IJMacD/rfc3339-iso8601), but RFC is more free as in freedom
Thx i take that back