W3C home > Mailing lists > Public > public-owl-wg@w3.org > July 2008

Re: An approach to xsd:dateTime

From: Alan Ruttenberg <alanruttenberg@gmail.com>
Date: Thu, 24 Jul 2008 05:42:01 -0400
Cc: public-owl-wg <public-owl-wg@w3.org>
Message-Id: <44BA7AD3-019F-41C4-892A-22F6F9188E40@gmail.com>
To: Michael Smith <msmith@clarkparsia.com>

Personally, I think this is a reasonable constraint. Another  
possibilty is to default to the local timezone  when one is not  
specified.

The mapping is to decimal (= owl:real value space for us). IIRC there  
was something about 3 digits of after decimal point precision,  
minimum, for seconds.

http://www.w3.org/TR/xmlschema11-2/#vp-dt-timeOnTimeline is the  
function that maps a dateTime to a number.

-Alan

On Jul 23, 2008, at 5:33 PM, Michael Smith <msmith@clarkparsia.com>  
wrote:

>
> On Wed, 2008-07-23 at 14:49 -0400, Michael Smith wrote:
>> As I read the XML Schema 1.1 description of dateTime [1], the primary
>> problem it presents as a datatype is that timezone is optional.  If  
>> OWL
>> were to require the timezone property, all values map to a single  
>> point
>> on a discrete number line (see [2]), making implementation  
>> equivalent to
>> implementation of xsd:integer.
>
> Tracker, this was in reference to ISSUE-126.
> -- 
> Mike Smith
>
> Clark & Parsia
>
>
Received on Thursday, 24 July 2008 09:42:39 UTC

This archive was generated by hypermail 2.3.1 : Tuesday, 6 January 2015 21:42:05 UTC