W3C home > Mailing lists > Public > www-rdf-interest@w3.org > May 2003

RE: rdfs:class and rdfs:resource

From: LYNN,JAMES (HP-USA,ex1) <james.lynn@hp.com>
Date: Mon, 12 May 2003 16:16:03 -0400
Message-ID: <079FD72E42C9D311B854009027650E6F0F264F27@xatl02.atl.hp.com>
To: "'Seth Ladd'" <seth@brivo.net>, www-rdf-interest@w3.org

This would certainly accomplish the task. I guess my question is - is there
a need for a predifined property (or three?) to express a point in time or a
duration of time in a simply manner. In other words, how common is this need
- enought to warrant an addition to the spec?

Just a thought.


-----Original Message-----
From: Seth Ladd [mailto:seth@brivo.net]
Sent: Monday, May 12, 2003 11:32 AM
To: www-rdf-interest@w3.org
Subject: RE: rdfs:class and rdfs:resource

On Mon, 2003-05-12 at 10:17, LYNN,JAMES (HP-USA,ex1) wrote:
> This brings up an important issue. I don't believe there is any mechanism
> RDF/RDFS for expressing notions of "time-varying properties" That's not
> say that it cannot be expressed with the current specs, rather I should
> it is not a specified property. At the risk of adding one more thing to
> list of "things which need to be ruled upon" (like "who owns URIs" and
> "social meaning"), does this need to be part of the next spec? I'm sure
> everyone has their own favorite examples, but just as a starting point
> RDF):
> 	"John Doe is in Paris."
> Is this true? To make it unambiguous, do I need to specify a time range?
> I don't know the time range, can I use a relative term such as "during the
> time I was in Paris" ?

It might help to think about the statement as a noun.  Something like:

John Doe has Travel Itinerary.
Travel Itinerary has Layover.
Layover hasCity Paris.
Travel Itinerary startsOn "June 5".
Travel Itinerary endsOn "June 8".
Layover startsOn "June 5, midnight".
Layover endsOn "June 6, 3 am".

So, instead of saying "John Doe is running." you can say "John Doe had
Run."  By taking the action (or the "is" in your above example) and
making it a Thing (noun), you can assign all sorts of properties to it. 
Such as startsOn or endsOn, to take care of the time issue.

I can elaborate if that helps,
Received on Monday, 12 May 2003 16:16:16 UTC

This archive was generated by hypermail 2.4.0 : Friday, 17 January 2020 22:44:42 UTC