Lists Home |
Date Index |
> Mike Champion wrote:
> > That's very human readable ... but RDF-challenged as I am, I don't
> > understand how it uses RDF. Where is all the cruft that people complain
> > about? :-)
> As I've said many times RDF doesn't *have* to be complicated, unfortunately,
> RDF all too often get's way too complicated and that's where sensible folks
> get thrown off the boat.
> that XML makes the following assertions:
> <#foo> rdf:type rddl:resource .
> <#foo> rddl:nature <http://example.org/nature> .
> <#foo> rddl:nature <http://example.org/purpose> .
> <#foo> rddl:nature <http://example.org/L.dtd> .
> <#foo> rddl:prose "<p>A description of the 'L' language>"^^rdf:XMLLiteral .
> where that last one is the new typed literal syntax where a string literal
> is separated from a type QName or URI by "^^".
> > Would a "native" RDF processor understand the assertions in there, or
> > a RDDL->RDF filter be needed?
> A processor would only need to know where to look in the RDDL document for
> the XML to be parsed as RDF. I've suggested an attribute on the top element:
> <html rddl:annotation-ns="http://www.w3.org/1999/xhtml">
> which would tell a parser to ignore elements in the XHTML namespace, and
> start parsing as RDF elements in any other namespace e.g. <rddl:resource>.
> An *actual* RDF document would look like:
Wow. You took a strange left turn on me. The "<rdf:RDF>" wrapper is optional
in the RDF M&S 1.0 grammar, so a compliant RDF parser can look at your
rddl:resource as a simple typed node that defines an object.
So the version you posted here is indeed "real" RDF.
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