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

I have been looking at both the files,

http://www.isi.edu/~pan/damltime/time-entry.owl
http://www.daml.org/services/owl-s/0.9/Process.owl

here is what we have:
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

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.

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.

The idea is to remove the temporal properties currently defined in 
Process.owl , if something similar is available in the time-entry ontology.

Further,

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 ?

Thanks,

Monika
-- 
**>><<**>><<**>><<**>><<**>><<**>><<**>><<**
Monika Solanki
Software Technology Research Laboratory(STRL)
De Montfort University
Hawthorn building, H00.18
The Gateway
Leicester LE1 9BH, UK

phone: +44 (0)116 250 6170 intern: 6170
email: monika@dmu.ac.uk
web: http://www.cse.dmu.ac.uk/~monika
**>><<**>><<**>><<**>><<**>><<**>><<**>><<**