W3C home > Mailing lists > Public > public-rdf-dawg-comments@w3.org > July 2012

Re: Serializing datetime

From: Andy Seaborne <andy.seaborne@epimorphics.com>
Date: Tue, 31 Jul 2012 09:05:39 +0100
Message-ID: <501791D3.5080708@epimorphics.com>
To: public-rdf-dawg-comments <public-rdf-dawg-comments@w3.org>
CC: David Booth <david@dbooth.org>

Thank you for your comment on serializing datetime values.

As noted in the response to your comment on "Serializing xsd:decimal, 
xsd:float, xsd:double", SPARQL reuses the body of work for XSD and 
XQuery/XPath functions and operators.  The rules for operations on 
datetimes derive from that work and this includes comparing datetime 
values.  Support is also now to be found in many programming languages.

An implementation is free to provide custom function that converts 
between timezones; XQuery/XPath does not itself provide such a function.

The working group is not planning to make any changes in this area.

I would be grateful if you reply to this message to confirm that the 
working group has responded to your comment.

Yours, on behalf of the SPARQL Working Group,


On 20/07/12 16:21, David Booth wrote:
> I have also noticed that it is a hassle trying to compare datetime
> values from two different SPARQL servers, because the same datetime may
> be written with different timezone offsets.  This is less vexing than
> xsd:decimal serializations, because at least timezone offsets are
> information preserving, but still it makes comparisons more difficult
> than they otherwise need to be.
> I think the WG should consider defining a default datetime format (such
> as UTC or zero timezone offset) that SHOULD be use, while allowing
> servers to make this a configurable option.
> I assume it is too late in the WG process to consider this for SPARQL
> 1.1, so please add this to the wish list for the next version.
> Thanks!
Received on Tuesday, 31 July 2012 08:06:10 UTC

This archive was generated by hypermail 2.4.0 : Friday, 17 January 2020 17:01:30 UTC