W3C home > Mailing lists > Public > public-qt-comments@w3.org > April 2007

[Bug 4471] Casting date/time timezone offset 0 values to string/untypedAtomic

From: <bugzilla@wiggum.w3.org>
Date: Wed, 18 Apr 2007 19:07:26 +0000
To: public-qt-comments@w3.org
Message-Id: <E1HeFV0-0007hz-Js@wiggum.w3.org>


           Summary: Casting date/time timezone offset 0 values to
           Product: XPath / XQuery / XSLT
           Version: Recommendation
          Platform: PC
        OS/Version: Windows XP
            Status: NEW
          Severity: normal
          Priority: P1
         Component: Functions and Operators
        AssignedTo: ashok.malhotra@oracle.com
        ReportedBy: mrys@microsoft.com
         QAContact: public-qt-comments@w3.org

The current casting rules for values of date/time type with timezone offset 0
values to string/untypedAtomic generate the serialization +00:00 instead of the
shorter and much more often used Z. Note that all the examples in the document
normally use Z instead of +00:00 and a few existing implementations also use Z
(Saxon, SQL Server).

We therefore request that the casting rules get changed to produce a Z instead.

Searches in the old documents appear to have moved from the rule (last seen in

<cite>If necessary, the localized value is recovered from the normalized value
as follows: if an explicit timezone was present, the normalized value is
adjusted using the explicit timezone; if an explicit timezone was not present,
the Z timezone is dropped from the normalized value. The localized value and
the explicit timezone, if present, are cast separately to xs:string and
concatenated to yield TV.</cite>

which seem to imply to work with Z, to the current rule... since this was an
editorial rework and after talking to the editors, we assume that this was an

This will also affect the data model serialization.
Received on Wednesday, 18 April 2007 19:07:42 UTC

This archive was generated by hypermail 2.3.1 : Wednesday, 7 January 2015 15:45:33 UTC