W3C home > Mailing lists > Public > www-ws@w3.org > October 2003

Re: [owl-s] Time ontology usage for OWL-S 1.0

From: Feng Pan <pan@ISI.EDU>
Date: Fri, 10 Oct 2003 12:22:27 -0700 (PDT)
To: Monika Solanki <monika@dmu.ac.uk>
Cc: David Martin <martin@AI.SRI.COM>, hobbs@ISI.EDU, www-ws@w3.org
Message-ID: <Pine.GSO.4.21.0310101041160.6284-100000@nitro.isi.edu>

Hi Monika,

> Process.owl:
> <owl:ObjectProperty rdf:ID="startTime">  
>   <rdfs:comment> Start time for the Event </rdfs:comment>
>   <rdfs:domain rdf:resource="#ProcessComponent"/>
>   <rdfs:range rdf:resource="&time;#Instant"/>
> </owl:ObjectProperty>
> <owl:ObjectProperty rdf:ID="endTime">
>   <rdfs:comment> End time for the Event </rdfs:comment>
>   <rdfs:domain rdf:resource="#ProcessComponent"/>
>   <rdfs:range rdf:resource="&time;#Instant"/>
> </owl:ObjectProperty>
> Time-entry.owl
> <owl:ObjectProperty rdf:ID="begins">
>     <rdf:type rdf:resource="&owl;FunctionalProperty" />
>     <rdfs:domain rdf:resource="#TemporalThing" />
>     <rdfs:range  rdf:resource="#InstantThing" />
>   </owl:ObjectProperty>
>   <owl:ObjectProperty rdf:ID="ends">
>     <rdf:type rdf:resource="&owl;FunctionalProperty" />
>     <rdfs:domain rdf:resource="#TemporalThing" />
>     <rdfs:range  rdf:resource="#InstantThing" />
>   </owl:ObjectProperty>
> startTime corresponds   to begins [do we want to make this a subproperty?]
> endTime corresponds to ends

Yes, "begins/ends" in entry subontology of time can replace the
"startTime/endTime". I don't think subproperty is needed unless you
want to have more specific begins or ends for process component, for
example, "process_begins" with its domain restricted to
"ProcessComponent" rather than the general "TemporalThing".

> The domain values are ofcourse different, however the difference in the 
> range value would not really matter as  InstantThing
> is a union of Instant and InstantEvent.

Yes, we generalized Instant and Interval to InstantThing and IntervalThing 
to include events (InstantEvent/IntervalEvent).

> Similarly we have
>  Process.owl
> <owl:ObjectProperty rdf:ID="during">
>  <rdfs:comment> Event/Process is during Interval, the exact time
>                 interval over which the event occurs
>  </rdfs:comment>
>   <rdfs:domain rdf:resource="#ProcessComponent"/>
>   <rdfs:range rdf:resource="&time;#Interval"/>
> </owl:ObjectProperty>
> Time-entry.owl
>   <owl:ObjectProperty rdf:ID="intDuring">
>     <rdfs:subPropertyOf rdf:resource="#startsOrDuring" />
>     <rdfs:domain rdf:resource="#ProperIntervalThing" />
>     <rdfs:range  rdf:resource="#ProperIntervalThing" />
>   </owl:ObjectProperty>
> Feng, are these semantically the same?, I am not very clear here.

If "ProcessComponent" is defined as "IntervalEvent" in entry sub-ontology,
"during" property can be safely removed, because the sub-ontology has
generalized all the properties and relations of intervals to interval
things (i.e. intervals and interval events), so that you can specify 
temporal properties (e.g. begins/ends, duration) directly for interval
events (e.g. process components).

> In process.owl we have properties like timeout and timeoutAbsolute, the 
> documentation for which says the following
> We may need absolute timeout (like calender time or timeOfDay, so
> we allow for the timeoutAbsolute property
> Here, can we use "inCalendarClock", which has as range 
> "CalendarClockDescription", which has everything that might be needed to 
> specify timeoutAbsolute ?

"inCalendarClock" is a property of instant things (i.e. instants and
instant events) that specifies an instant thing in a specific
calendar-clock interval, but "timeout" and "timeoutAbsolute" are
properties of process components that should be interval events.

I think what you want to say is the duration of a timeout interval of a
process component, for example, time out after 5 days, right?

In order to do this, I suggest you keep the timeoutAbsolute definition:

<owl:ObjectProperty rdf:ID="timeoutAbsolute">
  <rdfs:domain rdf:resource="#ProcessComponent"/>
  <rdfs:range rdf:resource="&time;#Interval"/>

Then, you can use either the "durationDescriptionOf" or
"durationDescriptionDataType" property to describe the duration of the
time out interval.

Please let me know if you have more questions or comments on this.


Received on Friday, 10 October 2003 15:22:39 UTC

This archive was generated by hypermail 2.3.1 : Tuesday, 6 January 2015 20:37:10 UTC