Home. 
.

transparent

transparent

transparent

Altova Mailing List Archives


Re: xsd:dateTime is uncompliant?

From: Joseph Kesselman <keshlam-nospam@-------.--->
To: NULL
Date: 10/4/2006 2:26:00 PM

jsnX wrote:
> I'm not asking what the schema spec says - I'm asking whether it's
> wrong or not. All the examples of ISO-8601 that I've seen use a comma,
> not a period - and the schema spec claims conformance to ISO-8601.

Actually, no. The Schema spec actually says only that "The date and time 
datatypes described in this recommendation were inspired by [ISO 8601]" 
-- not that their lexical or value spaces are identical to that ISO 
specification.

For what it's worth, ISO-8601 appears to accept *either* comma or period 
as its decimal-point mark, though I'm told comma is considered preferred.

So you could try contacting the W3C and suggesting that comma be added 
as an acceptable alternative, either as an erratum or in a future 
revision of the Datatypes spec. I think you'll get some pushback, since 
this would mean new documents could break old processors, but you might 
be able to get them to add a variant (superset type?) of dateTime which 
accepts either.

-- 
Joe Kesselman / Beware the fury of a patient man. -- John Dryden


transparent
Print
Mail
Like It
Disclaimer
.

These Archives are provided for informational purposes only and have been generated directly from the Altova mailing list archive system and are comprised of the lists set forth on www.altova.com/list/index.html. Therefore, Altova does not warrant or guarantee the accuracy, reliability, completeness, usefulness, non-infringement of intellectual property rights, or quality of any content on the Altova Mailing List Archive(s), regardless of who originates that content. You expressly understand and agree that you bear all risks associated with using or relying on that content. Altova will not be liable or responsible in any way for any content posted including, but not limited to, any errors or omissions in content, or for any losses or damage of any kind incurred as a result of the use of or reliance on any content. This disclaimer and limitation on liability is in addition to the disclaimers and limitations contained in the Website Terms of Use and elsewhere on the site.

.
.

transparent

transparent