Using W3C Time Ontology for Relative Time Constraint

Hi Simon and all,

at the POE call on 8 August you, Simon, proposed to use the W3C Time Ontology in OWL [1] for solving the requirements emerging from the Relative Time Constraint use case [2].

 

I had a look at [1] and am not convinced it will cover the requirement from [2].

The Time Ontology’s TemporalEntity has a properties for the times of its beginning and end and a period for its duration. But by my understanding all these properties take only exact values – expressed in different formats and calendars, but a calendar based on an event does not exist.

 

But the Relative Time Constraint use case does not have an exact time as reference. There are quite strict license agreements for events – primarily sports and cultural – which state in natural language: “photos may be posted online only 30   minutes after the event has ended”. For e.g. soccer games this could be a big range of time: after the regular play time of 90 minutes or with an extension of 30 minutes added or even with kicking penalties added. (That makes it almost impossible for a fully automated processing of “now we are licenced to publish the photo” but event organisers don’t care that much about it.)

 

POE’s challenge is to communicate this constraint. Therefore we need based on the model [3]:

-          The option to set a relative time as constraint: e.g. by new kind of constraint entity like relativeTimeAfterEventEnd, the rightOperand would set the period of e.g. 30 minutes …

-          … but we would need also an identifier for the related event. 
Option 1: requiring to use a second constraint of kind “event” with the rightOperand providing the event identifier.
Option 2: to add a property to Constraint



Best,

Michael

 

 

[1] https://www.w3.org/TR/2016/WD-owl-time-20160712/#topology

[2] http://w3c.github.io/poe/ucr/#relTimeConstraint

[3] http://w3c.github.io/poe/model/

 

Michael Steidl

IPTC [mdirector@iptc.org]