W3C home > Mailing lists > Public > public-exi@w3.org > December 2017

Re: Any interest in participating Canonical EXI interoperability test? canonical time representations

From: C. M. Sperberg-McQueen <cmsmcq@blackmesatech.com>
Date: Mon, 11 Dec 2017 15:35:31 -0700
Cc: "C. M. Sperberg-McQueen" <cmsmcq@blackmesatech.com>, "Peintner, Daniel" <daniel.peintner.ext@siemens.com>, Takuki Kamiya <tkamiya@us.fujitsu.com>, Carine Bournez <carine@w3.org>, "public-exi@w3.org" <public-exi@w3.org>
Message-Id: <41BF2274-F89A-42E0-86F9-FAB16273F326@blackmesatech.com>
To: Don Brutzman <brutzman@nps.edu>

> On Dec 11, 2017, at 9:18 AM, Don Brutzman <brutzman@nps.edu> wrote:
> 2. Next, XML Schema reference says
> Canonical representation
> 	https://www.w3.org/TR/2004/REC-xmlschema-2-20041028/#dateTime-canonical-representation
> ===============================
> 	"Except for trailing fractional zero digits in the seconds representation, '24:00:00' time representations, and timezone (for timezoned values), the mapping from literals to values is one-to-one. Where there is more than one possible representation, the canonical representation is as follows:
> 	The 2-digit numeral representing the hour must not be '24';
> 	The fractional second string, if present, must not end in '0';
> 	for timezoned values, the timezone must be represented with 'Z' (All timezoned dateTime values are UTC.).
> ===============================

Please, please donít build things on the XSD 1.0 date / time types; use
XSD 1.1 instead.  

In addition to have a much more explicit treatment of the mappings between 
values and lexical representations, 1.1 shifts the treatment of time zones to 
agree with the date/time types used in XPath 2.0 and higher, XSLT 2.0 and 
higher, and XQuery, which do retain time zones.  


C. M. Sperberg-McQueen
Black Mesa Technologies LLC
Received on Monday, 11 December 2017 22:36:03 UTC

This archive was generated by hypermail 2.3.1 : Monday, 11 December 2017 22:36:03 UTC