On Tuesday, October 18, 2022 18:13 +0200 Carsten Bormann <[email protected]> wrote:
>>...
>> Whoever invented the adaptation of -00:00 to the RFC 3339 format did
>> not have a copy of ISO 8601, did not bother to look, or didn't think
>> that the resulting incompatibility would be a problem in practice.
>> Turns out, it actually is.
John C Klensin (19 October 2022 17:07) replied (inter alia):
> (3) We are, however, supposed to be about interoperability and
> reality.
Speaking of which, while I realise other software may have implemented
ISO 8601 carefully enough to reject -00:00, I note that the Qt framework
(for C++ development) has a QDateTime whose ISO 8601 format handling
blithely accepts -0000 or -00:00 if given it, while consistently
producing +00:00. I shall not be hugely surprised if plenty of other
real-world parsers and serializers of "ISO 8601" have similarly lenient
parsing but conformant serialization.
The present discussion was the first I ever heard of -00:00 having a
special meaning in e-mail headers, or of ISO 8601 forbidding it; and I
strongly suspect many other implementors of these specs are in the same
position.
None of which is an attempt to talk anyone out of fixing the problem,
but hopefully it can give a sense of perspective to how dire it might be.
Let us all remember the words on the cover of the hitch-hiker's guide to
the galaxy,
Eddy.
_______________________________________________
TICTOC mailing list
[email protected]
https://www.ietf.org/mailman/listinfo/tictoc
