- From: Lisa Seeman <lisa@ubaccess.com>
- Date: Tue, 21 Dec 2004 09:43:37 +0200
- To: Danny Ayers <danny.ayers@gmail.com>, Wei Xing <xing@ucy.ac.cy>
- Cc: www-rdf-interest@w3.org
- Message-id: <013601c4e730$f129c730$680aa8c0@IBMA4E63BE0B9E>
Hi Danny, I have been looking into representing time-sensitive resources using RDF , but for a very different application - multi media resources. What we have been doing is regarding a element in a resource that changing over time as being part of our description of the possible states of the resource, where time is a contrition that affects state, and state in turn effects or acts as a condition type property to every other value/ property of the element I have no idea if this is at all helpful, but it may be interesting metaphor for what you are doing Keep well Lisa Seeman ----- Original Message ----- From: Danny Ayers To: Wei Xing Cc: www-rdf-interest@w3.org Sent: Monday, December 20, 2004 12:55 PM Subject: Re: Time-sensitive resources using RDF? On Mon, 20 Dec 2004 11:43:12 +0200, Wei Xing <xing@ucy.ac.cy> wrote: > > Dear all, > > Does anybody have the experience of representing time-sensitive > resources using RDF/S? In particular, for the time-sensitive properties? > > I am trying to describe some time-sensitive resources using RDF/S, of > which the values (Object) of the properties (Predicate) are changed from > time to time, for instance, a computer cluster (the network bandwidth > and the free CPUs number of the cluster are dynamical). > > My way, to describe a "Cluster" using RDF/S, can be descibed as follows: > First, I describe the "Cluster" using reification, i.e. attaching a > constraint (valid only for the year 2004) to the Cluster. Second, I > descibe its properties, e.g. network bandwidth (at the testing moment) > using a 4-tuple format ({Subject, Predicate, [Object, timestamp]}). The > RDF metadata is shown as follows: > .... > <rdf:Description> > <rdf:subject rdf:resource="http://grid.ucy.ac.cy/someCluster1" /> > <rdf:predicate > rdf:resource="http://grid.ucy.ac.cy/2003/12/GrisenSchema#bandWidth" /> > <rdf:object > > <rdf:Seq> > <b> 125Mbits </b> > <t> 200412201023 </t> > </rdf:Seq> > </rdf:object> > ...... <rdf:type rdf:resource = > "http://www.w3.org/1999/02/22-rdf-syntax-ns#statement" /> > <grisen:validFor> 2004 </grisen:validFor> > </rdf:Description> > .... > > Not sure if my way is OK? Is there another way that allows me to > describe such property and its value using RDF without conflicting the > exsiting RDF recommendation? > > I appreciate any comments and suggestions on it. (Sorry, very quick response) Your basic modelling approach (the 4-tuple) looks ok, but I'm not sure about the representation in RDF (/XML). This may be helpful: http://www.w3.org/TR/swbp-n-aryRelations/ Cheers, Danny. -- http://dannyayers.com
Received on Tuesday, 21 December 2004 07:45:46 UTC