ISSUE-126: Deprecate :xsdDateTime ?
xsdDateTime
Deprecate :xsdDateTime ?
- State:
- CLOSED
- Product:
- Time ontology in OWL
- Raised by:
- Simon Cox
- Opened on:
- 2016-12-21
- Description:
- There are two alternatives provided for the definition of a :DateTimeInterval
- :hasDateTimeDescription - an explicit labelled 7-value model
- :xsdDateTime - using the xsd:DateTime datatype
In the 2006 OWL-Time the usage is not explained very clearly, and no examples are provided. I infer that in either case the beginning and end of the interval are implicitly defined by the precision of the value of the property. While this works OK for :hasDateTimeDescription, it gets pretty awkward in the :xsdDateTime case, because the lexical rule requires that all fields are present, right down to fractional seconds, so the precision is implicitly given by the first of the group of zeroes at the end of the value.
e.g. the intention appears to be that 2016-12-21T00:00:00.00 describes today. But how do we define this month? Is it 2016-12-00T00:00:00.00 ? And what does 2016-12-21T01:00:00.00 describe? or 2016-12-21T10:00:00.00 (which is the zero that matters?)
Looks confusing and kludgy to me.
I propose to deprecate time:xsdDateTime to discourage use of this formulation in future. - Related Actions Items:
- No related actions
- Related emails:
- RE: Please review OWL-Time document (from Simon.Cox@csiro.au on 2017-02-26)
- RE: Please review OWL-Time document (from L.Svensson@dnb.de on 2017-02-20)
- RE: Please review OWL-Time document (from Simon.Cox@csiro.au on 2017-02-20)
- FW: ISSUE-125: Update datatypes in OWL Time (from Simon.Cox@csiro.au on 2017-02-20)
Related notes:
No additional notes.
Display change log
