W3C home > Mailing lists > Public > www-rdf-interest@w3.org > June 2000

RE: RDF and XLink

From: Ron Daniel <rdaniel@metacode.com>
Date: Fri, 2 Jun 2000 07:30:27 -0700
Message-ID: <0D611E39F997D0119F9100A0C931315C61069F@datafusionnt1>
To: "Eve L. Maler" <Eve.Maler@east.sun.com>, w3c-xml-linking-ig@w3.org, www-rdf-interest@w3.org, sergey Melnik <melnik@db.stanford.edu>, stefan Decker <stefan@db.stanford.edu>
Eve said:

> I have another question that I hope will spur discussion.  In discussing 
> with Sergey and Stefan the fact that a single arc specification may create
> 
> multiple arcs (when the same arc label value appears on multiple 
> resources), I was warned:
> 
> "I'd recommend to be very careful with such things. RDF spec has a
> similar construct "aboutEach" which has been the subject of controversy
> and misunderstanding. The spec demands that the "batch" process of
> assigning the given relationship with every member of the bag (or in
> your case, every element with the same label) takes place during
> parsing, i.e. is transparent to the applications. However, a similar
> syntactic element "aboutEachPrefix" can only be expressed at the model
> level, i.e. using special relationships with predefined meaning."
> 
> Having read through Ron's writeup, I don't think this really comes into 
> play, since each *actual arc specified* (not merely each arc-type element)
> 
> spins off its own set of RDF statements.  However, I would be grateful for
> 
> feedback on whether this is a gray area/problem in XLink and its 
> relationship to RDF.  Thanks--
> 
In fact, I briefly considered using 'aboutEach' to allow
a more direct harvesting of Links that used roles to
identify several resources.
I dropped that idea as being needlessly complex, and
went with the approach where each traversal arc gave
rise to a single RDF statement.

Ron  
Received on Friday, 2 June 2000 10:30:34 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Monday, 7 December 2009 10:51:43 GMT