Andrew Daviel wrote:
> Do we allow "naked" dates (no time component) ?
I suggest we allow all six levels of granularity: the four proposed in my mail
"Profile of ISO 8601 (draft) - RESEND" plus the two later requested by Pete
Ciuffetti:
Year:
YYYY (eg 1997)
Year and month:
YYYY-MM (eg 1997-07)
Complete date:
YYYY-MM-DD (eg 1997-07-16)
Complete date plus hours and minutes:
YYYY-MM-DDThh:mmTZD (eg 1997-07-16T19:20+01:00)
Complete date plus hours, minutes and seconds:
YYYY-MM-DDThh:mm:ssTZD (eg 1997-07-16T19:20:30+01:00)
Complete date plus hours, minutes, seconds and decimal fractions of a second
YYYY-MM-DDThh:mm:ss.sTZD (eg 1997-07-16T19:20:30.45+01:00)
The "s" after the "." stands for one or more digits representing a decimal
fraction of a second.
"TZD" stands for a time zone designator, of which more later.
> Do we go with hyphens as per HTML 4.0, e.g.
> 1994-11-05T13:15:30Z
> 1994-11-05T08:15:30-05:00
Yes, please.
> or dots as per PICS ,e.g.
> 1994.11.05T08:15-0500
This was an error in PICS 1.1. I believe it has been fixed in PICS-NG.
> or almost everything, as I gather ISO8601 allows ...
No, thanks; too hard to process.
> Do we allow Z for UTC (as HTML), or require +0000 as PICS ?
On the subject of time zone offsets, my above-mentioned proposal says:
: This profile defines two ways of handling time zone offsets:
:
: 1. Times are expressed in UTC, with a special UTC designator ("Z").
: 2. Times are expressed in local time, together with a time zone offset
: in hours and minutes. A time zone offset of "+hh:mm" indicates that
: the date/time uses a local time zone which is "hh" hours and "mm"
: minutes ahead of UTC. A time zone offset of "-hh:mm" indicates that
: the date/time uses a local time zone which is "hh" hours and "mm"
: minutes behind UTC.
I think we should allow both formats, as does HTML 4.0.
BTW, the missing colon in the "+hhmm" (or "-hhmm") of PICS 1.1 was, again, an
error and was (I believe) fixed for PICS-NG.
> Andrew Daviel
Misha
------------------------------------------------------------------------
Any views expressed in this message are those of the individual sender,
except where the sender specifically states them to be the views of
Reuters Ltd.
|