Le 2019-09-02 19:27, Kevin Kofler a écrit :
Nicolas Mailhot via devel wrote:
2. However the IETF explicitely forbid it when defining the ISO 8501
subset allowed on the Internet
RFC 3339> Although ISO 8601 permits the hour to be "24", this profile
of
ISO
RFC 3339> 8601 only allows values between "00" and "23" for the hour
in
order
RFC 3339> to reduce confusion.
Therefore, banning the 24:00 notation is necessary for
interoperability,
even if one does not agree with the IETF decision. (00:00 however is
well-defined and not ambiguous)
IETF RFCs are only relevant for software. Humans need to comply only
with
ISO standards.
Humans need not comply with anything, they have free will, however it
helps out if they exert their will wisely.
And when the IETF forbids using 24h to avoid confusion do you really
thing it is writing about software? Software does not get confused,
software is dumb as a brick, people get confused.
RFC 3339 specifically only claims to be about "representing and using
date
and time in Internet protocols", not on websites (which are just an
arbitrary unformatted payload as far as the HTTPS protocol is
concerned).
In this date and age is it quite naïve to think the data on a website is
for human consumption only and will never be plugged on a message bus,
an API, or whatever is the buzzword of the day for automated processing
Regards,
--
Nicolas Mailhot
_______________________________________________
devel mailing list -- devel@xxxxxxxxxxxxxxxxxxxxxxx
To unsubscribe send an email to devel-leave@xxxxxxxxxxxxxxxxxxxxxxx
Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: https://lists.fedoraproject.org/archives/list/devel@xxxxxxxxxxxxxxxxxxxxxxx
