Lists Home |
Date Index |
> Shelley Powers wrote:
> However, these semantics have to do with implementation, not data,
> > and as such really don't have a place within the RDF semantics document. A
> > container can be replaced with a typed node and get the same RDF graph,
> > without the processing baggage (or benefit) attached. There is no 'new'
> > semantics -- the notation is more a convenience then new
> > Same with reification if you look at the RDF graph of a reified statement
> > and break it down into its parts.
> Please, if you are writing a book about RDF, don't say these things because
> you are just going to confuse anyone and everyone who believes what you say.
> You have a particular obligation to thouroughly read
> http://www.w3.org/rdf-mt/ . It is a very well written document.
I haven't read the latest draft of that document, but I share your worry about
what Shelley's book might say about reification and containers.
I ceased using both ages ago because, as many here have pointed out, they are
terribly B.A.D. People cannot be forbidden from using them because in the end
they are just regular triples with no special status (i.e. using predicates
such as "rdf:subject" and "_1". But I am glad that in earlier drafts of post
RDF-1.0, that even their status in the serialization has been stripped. I
also think that daml:Collection (which I understand has been drafted into RDF)
is a much better solution for containers, if not perfect. For things that RDF
M&S originally suggested as applications of reification, as I've said, I
instead use blank node constructs or 4RDF scopes.
My main point is that if any RDF book covers reification and containers, it
should at least tell the user about the very widely expressed warnings
problems with these constructs, and the fact that many RDF experts avoid them.
Endless discussion on such topics can be found in the www-rdf-interest
Let's not lead RDF newbies into that foetid sinkhole.
Uche Ogbuji Fourthought, Inc.
http://uche.ogbuji.net http://4Suite.org http://fourthought.com
Python&XML column: 2. Introducing PyXML - http://www.xml.com/pub/a/2002/09/25/p
The Past, Present and Future of Web Services 1 - http://www.webservices.org/ind
The Past, Present and Future of Web Services 2 - 'http://www.webservices.org/in
Serenity through markup - http://adtmag.com/article.asp?id=6807
Tip: Using generators for XML processing - http://www-106.ibm.com/developerwork