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

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

From: Don Brutzman <brutzman@nps.edu>
Date: Mon, 18 Dec 2017 07:50:35 -0800
To: "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>
CC: "public-exi@w3.org" <public-exi@w3.org>
Message-ID: <4011cb69-28b7-715e-f43d-c709d635107a@nps.edu>
Charles, thank you so much for this direction to follow.  Apologies for erroneously propagating an outdated link.

Updated reference:

W3C XML Schema Definition Language (XSD) 1.1 Part 2: Datatypes
W3C Recommendation 5 April 2012

Latest version:

	3.3.6 duration

	3.3.7 dateTime

	3.3.8 time

Also sections for  date ∑ gYearMonth ∑ gYear ∑ gMonthDay ∑ gDay ∑ gMonth and yearMonthDuration ∑ dayTimeDuration ∑ dateTimeStamp, plus Constraining Facets for (among other things) explicitTimezone.

Of further importance (and including treatment of leap seconds):

	D.2 Date/time Values
         D.2.1 The Seven-property Model
         D.2.2 Lexical Mappings

So it looks like the *EXI group has more review work to do* for confirming canonical representation of dates and times in Canonical EXI.

Wondering, might there be an example corpus of dates and times for confirmation of correct XML schema validation?  Such cases would likely be useful for Canonical EXI test examples as well.

On 12/11/2017 2:35 PM, C. M. Sperberg-McQueen wrote:
>> 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
> cmsmcq@blackmesatech.com
> http://www.blackmesatech.com
> ******************************************** 

all the best, Don
Don Brutzman  Naval Postgraduate School, Code USW/Br       brutzman@nps.edu
Watkins 270,  MOVES Institute, Monterey CA 93943-5000 USA   +1.831.656.2149
X3D graphics, virtual worlds, navy robotics http://faculty.nps.edu/brutzman
Received on Monday, 18 December 2017 15:52:31 UTC

This archive was generated by hypermail 2.3.1 : Monday, 18 December 2017 15:52:34 UTC