ISSUE-181: Add support for xsd:duration
Add support for xsd:duration
- State:
- CLOSED
- Product:
- Time ontology in OWL
- Raised by:
- Simon Cox
- Opened on:
- 2017-04-21
- Description:
- Comment recived during wide review drew attention to the fact that OWL-Time did not use xsd:duration.
- Related Actions Items:
- No related actions
- Related emails:
- Response to ISSUE-181 (from Simon.Cox@csiro.au on 2017-04-21)
- FW: Wide review - help needed (from Simon.Cox@csiro.au on 2017-04-21)
- related to ISSUE-181 (from Simon.Cox@csiro.au on 2017-04-21)
Related notes:
Response in email 2017-04-17
Thanks Payam, Chris –
I suggest
(i) Adding time:hasXSDDuration with rdfs:domain time:TemporalEntity and rdfs:range xsd:duration
(ii) Expanding the paragraph at the top of Section 3.2 to also mention this.
I guess the goal is to enable users who don’t need any more than the XSD types to use them, sensibly. We inherited the time:inXSDDateTime (etc.) properties on time:Instant from the 2006 edition already, so it would be perverse to exclude xsd:duration. I wonder why Hobbs and Pan didn’t? However, also note that xsd:duration is not one of the OWL2 built-ins, though we are already breaking that rule with xsd:gYear etc. (inherited from the 2006 version).
The general answer to Stephan’s question is the background one, that the primary goal of the revision was to not restrict the temporal reference system in use to only Gregorian, but we recognize that Gregorian is likely to be the most used, so we hold our nose and nod some sub-optimal features through because we know people will be looking for them.
Display change log
