- From: Mike Moran <mmoran@netphysic.com>
- Date: Wed, 12 Dec 2001 18:06:56 +0000
- To: RDF Interest List <www-rdf-interest@w3.org>
I'm currently trying to minimize some shared properties that will be the
same between resources eg:
<rdf:RDF xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#"
xmlns:dc="http://purl.org/dc/elements/1.1/">
<rdf:Description rdf:about="http://www.foo.com"
dc:title="Foo" dc:date="2001-12-07"/>
<rdf:Description rdf:about="http://www.bar.com"
dc:title="Bar" dc:date="2001-12-07"/>
</rdf:RDF>
I want to do something like this:
<rdf:RDF xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#"
xmlns:dc="http://purl.org/dc/elements/1.1/">
<rdf:Description rdf:aboutEach="#shared" dc:date="2001-12-07" />
<rdf:Bag rdf:ID="shared">
<rdf:li>
<rdf:Description rdf:about="http://www.foo.com" dc:title="Foo"/>
</rdf:li>
<rdf:li>
<rdf:Description rdf:about="http://www.bar.com" dc:title="Bar" />
</rdf:li>
</rdf:Bag>
</rdf:RDF>
That is, define the shared attributes separately, and then have them be
merged in. However, this is not what happens (at least in cwm).
From the perspective of the author, it would be nice to collect shared
attributes like this, but have them be equivalent to placing them on
each description, from the perspective of the processing application.
Note that I am not saying that http://www.foo.com and http://www.bar.com
are the same class, or type, but rather that they happen to share lots
of properties which will change in sync. As such it is more of a
syntactical and maintainance convienience than a representational aspect.
Is it possible to do this `optimization'? If so, how?
--
Mike
Received on Wednesday, 12 December 2001 13:07:33 UTC