- From: Andy Seaborne <andy.seaborne@epimorphics.com>
- Date: Fri, 03 Dec 2010 14:12:51 +0000
- To: SPARQL Working Group <public-rdf-dawg@w3.org>
Easier (hopefully!) YEAR, MONTH, DAY, HOURS, MINUTES Return an xsd:integer. SECONDS Return an xsd:decimal (fractional seconds possible). TIMEZONE is a bit different. In F&O it returns an xs:dayTimeDuration. There are operations like fn:timezone-from-dateTime for each of dateTime, date and time. See also casting rules [1]. xs:dayTimeDuration isn't a datatype we currently require support for - or xsd:duration - this affects the operations of "<" etc. dayTimeDuration is totally ordered [2]. F&O had accessors for xs:duration for years...seconds. 1: Is xsd:dayTimeDuration the appropriate choice for SPARQL? 2: If there is no timezone, what do we return? (we don't have the empty sequence, which is what F&O returns.) 3: If it is going to be a duration, should we document that HOURS, MINUTES, SECONDS also apply to durations (AKA partial support)? (Durations drop a bit of information : writing "00:00" or "Z" yield a duration of zero and you can't tell which because it's value based. May matter if you care about round tripping.) Andy [1] http://www.w3.org/TR/xpath-functions/#casting-to-datetimes [2] http://www.w3.org/TR/xpath-functions/#duration-subtypes
Received on Friday, 3 December 2010 14:13:35 UTC