- From: Sean B. Palmer <sean@mysterylights.com>
- Date: Wed, 20 Dec 2000 16:40:24 -0000
- To: "Seth Russell" <seth@robustai.net>
- Cc: "RDF-IG" <www-rdf-interest@w3.org>
> > Also, if (or rathr, "as") the context URI's are RDF Schema, could we use > > classes/properties of the Schema (i.e. further pointing out the context), > > and if so how? > > I think I would prefer doing it outside the schema as illustrated above. > What do you think? Good idea. In the context Schema, we could define further context models for whatever assertions we have. For example, in your model:- [contextUri3]--subContextOf-->[contextUri1] [contextUri3]--subContextOf-->[contextUri2] [contextUri3]--contextFor-->[id1,http:..../Lassila, Creator, "Ora Lassila"] This is a Schema itself, but one that points "backwards" from the actual context Schemas. As such, contextUri3 could itself be the context of another context Schema:- [contextUri4]--subContextOf-->[contextUri3] In that case would it automatically import the "contextFor" triple that is included in contextUri3 for the purposes of the RDF code you made? In other words, would this example have the same context as yours(?):- <?xml version="1.0"?> <RDF xmlns="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:s="http://description.org/schema/" contextFor="contextUri4" > <Description about="http://www.w3.org/Home/Lassila"> <s:Creator>Ora Lassila</s:Creator> </Description> </RDF> If so, then it's lucky you use contextFor in the literal sense rather than just pointing out a node! In summary, if these are your proposals, then I think that they are very useful indeed and should probably be added as RDF serialization properties. Kindest Regards, Sean B. Palmer http://www.mysterylights.com/sbp/ http://www.w3.org/WAI/ [ERT/GL/PF] "Perhaps, but let's not get bogged down in semantics." - Homer J. Simpson, BABF07.
Received on Wednesday, 20 December 2000 11:41:51 UTC