Subject: bug#35032: date ISO 8601 / RFC 3339 formats

From: Nicolas Mailhot <[email-masked]>
Date: Fri, 29 Mar 2019 09:59:33 +0100

Le jeudi 28 mars 2019 à 22:07 +0100, Erik Auerswald a écrit :
> 
> > 1. The W3C profile mandates T as time separator, and ":" as
> > hour/minutes separator
> > 2. RFC 3339 makes both optional
> > 
> > Then, logically, date removed the ":" for its --iso-8601 option,
> > $ date --iso-8601=seconds
> > 2019-03-28T18:09:47+0100
>                        ^^
>                        there should be a ':' for W3C compatibility
> 
> > and then removed T from its --rfc-3339 option
> > $ date --rfc-3339=seconds
> > 2019-03-28 18:10:11+01:00
>             ^
>             there should be a 'T' for W3C compatibility
> 
> > [...]
> 
> Nicolas asks for an ISO 8601 compatible format using both a 'T' as
> separator between date and time, and a ':' as separator between hours
> and minutes in the timezone designator, as well as the other contents
> that are identical in --iso-8601 and --rfc-3339.
> 
> From looking at https://www.w3.org/TR/NOTE-datetime, the important
> part
> is using both 'T' and a TZD with ':' in the middle, the other
> variability
> (e.g. minutes, seconds, fractional seconds as decimals) can be chosen
> as fits.

And, testing some more, on, a system with a more recent version of
coreutils, that I had no access to yesterday:

date --iso-8601=seconds had its output changed 
2019-03-29T09:54:41+01:00

Which is W3C compliant. So it seems someone already reported the
problem in the past, and it has already been fixed.

A lot of thanks to the person who did the fix and the person who
reported the problem before me, whoever they are.

And thanks to Eric for clarifying my report

The bug can be closed.

Regards,

-- 
Nicolas Mailhot