W3C home > Mailing lists > Public > public-sdw-wg@w3.org > February 2017

RE: OWL-Time - superclasses for Position and Duration

From: <Simon.Cox@csiro.au>
Date: Sun, 12 Feb 2017 11:56:45 +0000
To: <public-sdw-wg@w3.org>
Message-ID: <317259a42a204c24ab733fd579dba945@exch1-mel.nexus.csiro.au>
Hearing no objections, and since this proposal is expected to be generally benign and uncontroversial, I have accepted the pull-request and will close ISSUE-149.


From: Cox, Simon (L&W, Clayton)
Sent: Thursday, 9 February, 2017 15:40
To: 'public-sdw-wg@w3.org' <public-sdw-wg@w3.org>
Subject: RE: OWL-Time - superclasses for Position and Duration

Unless anyone objects, I propose to accept the pull-request https://github.com/w3c/sdw/pull/515 which adds two superclasses to OWL-Time.

The effect of these is to properly recognize that

-          :GeneralDurationDescription and :Duration are both the same kind of thing, here called :TemporalDuration

-          :GeneralDateTimeDescription and :TimePosition are both the same kind of thing, here called :TemporalPosition

Without these superclasses there is not a proper connection from the classes :DurationDescription and :DateTimeDescription from OWL-Time 2006, and :Duration and :TimePosition introduced in this revision.

This is in the tracker as ISSUE-149


From: Simon.Cox@csiro.au<mailto:Simon.Cox@csiro.au> [mailto:Simon.Cox@csiro.au]
Sent: Friday, 27 January, 2017 11:21
To: public-sdw-wg@w3.org<mailto:public-sdw-wg@w3.org>
Subject: [ExternalEmail] OWL-Time - superclasses for Position and Duration

I've done a little more work on the OWL-Time spec to introduce superclasses for temporal duration and temporal position. These provide a common superclass above Duration/GeneralDurationDesciption and TimePosition/GeneralDateTimeDescription, respectively.

I've pushed these into a new branch https://github.com/w3c/sdw/tree/simon-time-superclasses
Probably the easiest way to grok is to look at the diagrams


and compare with the disjointed figures in the current draft


Note that the subclassing of these classes is based on implementation options, rather than actual topology which is the case for


While this does not affect the existing functionality, it provides a better upper level to the OWL-Time ontology and thus makes the whole thing a bit clearer. (i.e. I know this just looks like more tinkering, but I think it helps the overall picture).


Simon J D Cox
Research Scientist
Environmental Informatics
CSIRO Land and Water<http://www.csiro.au/Research/LWF>

E simon.cox@csiro.au<mailto:simon.cox@csiro.au> T +61 3 9545 2365 M +61 403 302 672
   Mail: Private Bag 10, Clayton South, Vic 3169
   Visit: Central Reception, Research Way, Clayton, Vic 3168
   Deliver: Gate 3, Normanby Road, Clayton, Vic 3168

The information contained in this email may be confidential or privileged. Any unauthorised use or disclosure is prohibited. If you have received this email in error, please delete it immediately and notify the sender by return email. Thank you. To the extent permitted by law, CSIRO does not represent, warrant and/or guarantee that the integrity of this communication has been maintained or that the communication is free of errors, virus, interception or interference.

Please consider the environment before printing this email.
Received on Sunday, 12 February 2017 11:57:41 UTC

This archive was generated by hypermail 2.4.0 : Thursday, 24 March 2022 20:31:29 UTC