Processing fragments? http://www.ideaspace.net/users/wkearney/archives/entries/000458.html wkearney 2003-08-09T13:03:57-05:00 http://www.ideaspace.net/users/wkearney/archives/entries/000458.html en-us RDF 1 2003-08-09T13:03:57-05:00 What's better here?

<hamsandwich:group rdf:resource="http://ideaspace.net/schema#parent/child"/>
This:
<hamsandwich:group rdf:resource="http://ideaspace.net/schema/parent#child"/>
Or this:
<hamsandwich:group rdf:resource="http://ideaspace.net/schema/parent/child"/>

What I'm after here is a vocabulary listed at http://ideaspace.net/schema has a hierarchy within it. It's a descriptive vocabulary with many parent and subsequent child layers.

When I ask "what's better" I'm asking in the context of what's the least horrible way to express it such that it doesn't put undue burden upon the various tools that might be used to parse it?

Realizing that I may also make it more human readable by serializing it this like as well:


<hamsandwich:group rdf:resource="http://ideaspace.net/schema/parent#child">
<rdf:label>Child of Parent</rdf:label>
</hamsandwich:group>

In reality, however, the labelling of the various points within the hierarchy might not need to be marked up as such when both sides already know what human-readable labelling should be applied to them. This if just to stave of the nitwits that want to jump in and whine about verbosity.

So there's my question, if I emit data that's marked up in this manner what would be the least painful way for something doing triplespace queries to reach into the dataset and find exact points in the hierarchy as well as possible portions 'higher' in it?

]]> 458 457 459