Julian Reschke wrote:
...2. RFC 3339 allows the replacement of the 'T' with a space which xsd:dateTime does not. [Note: ISO 8601 doesn't either, hence RFC 3339 isn't actually a "profile of ISO 8601" as it claims].
As far as I can tell, ISO 8601 allows this.
And anyway, what RFC3339 says is:
" date-time = full-date "T" full-time
NOTE: Per [ABNF] and ISO8601, the "T" and "Z" characters in this
syntax may alternatively be lower case "t" or "z" respectively. This date/time format may be used in some environments or contexts
that distinguish between the upper- and lower-case letters 'A'-'Z'
and 'a'-'z' (e.g. XML). Specifications that use this format in
such environments MAY further limit the date/time syntax so that
the letters 'T' and 'Z' used in the date/time syntax must always
be upper case. Applications that generate this format SHOULD use
upper case letters. NOTE: ISO 8601 defines date and time separated by "T".
Applications using this syntax may choose, for the sake of
readability, to specify a full-date and full-time separated by
(say) a space character."So as long as we normatively refer to the "date-time" production, only "T" is allowed.
In general, I find RFC3339 a lot easier to read than xsd:dateTime, and for the date representations we actually want to support, they define the same meaning.
Thus -1 on changing it, and +1 on possibly profiling it further.
Best regards, Julian
-- <green/>bytes GmbH -- http://www.greenbytes.de -- tel:+492512807760
