4. OWL-Time and enhancements | Cox4 |
“2015-03-10T17:10:00.00+01:00”^^xsd:DateTime
gYear, gMonth, gDay tied to Gregorian Calendar
No way to use (or even indicate) other temporal reference systems
e.g. geologic time, GPS/Unix time, Hebrew calendar, archeological periods, dynastic systems …
5. Generalization to enable other time systems
OWL-Time and enhancements | Cox5 |
No change to existing rdf instances!
6. Summary
• OWL-Time is based on rigorous temporal calculus, supporting
ordering of events
• All of Allen’s temporal relations are supported for ‘ProperIntervals’
• Time position in OWL-Time is limited to Gregorian calendar
would drive technical and cultural users elsewhere
• Proposed generalization supports
• Indication of a temporal reference system (externally described)
• more representations:
Coordinate (number on timeline), ordinal values (named intervals)
• Interval logic is retained, no change for existing OWL-Time users
OWL-Time and enhancements | Cox6 |
Notas del editor
OWL Time was designed to support time-stamps related to contemporary events described in web pages.
Allen’s interval calculus was designed to support sorting of events in record-keeping systems.
Based on Allen’s ‘interval calculus’: primitive is interval, has duration, beginning, end
(even an Instant has beginning and end!)
Two alternative representations of temporal position:
inXSDDateTime – uses familiar 7-component micro-format 2015-03-10T17:10:00.00+01:00
inDateTime – decomposes components in separate elements: year, month, day, hour, minute, second, timeZone
Proposed generalization has these features:
GenDateTimeDescription generalizes DateTimeDescription
Year, month day are not limited to Gregorian Calendar
hasTRS property
TimePosition supports other representations of time position
Temporal coordinates (GPS time, Unix time, Loran-C)
Ordinal values (named intervals – archeology, geology, dynasties)
(assuming enhancement is deployed in the same namespace) NO CHANGE to existing usage of OWL-Time