W3C home > Mailing lists > Public > public-grddl-comments@w3.org > January to March 2007

Please declare in GRDDL spec that XML validation is not required

From: Dave Beckett <dave@dajobe.org>
Date: Fri, 09 Feb 2007 22:13:18 -0800
Message-ID: <45CD627E.2040700@dajobe.org>
To: public-grddl-comments@w3.org


<chimezie> .grddl
http://www.ibiblio.org/hhalpin/homepage/notes/vcardtable.html "SELECT
?homeSyn WHERE { ?homeSyn owl:equivalentProperty foaf:homePage }"

<Emeka> Querying against 98 triples

Raptor failed on this document.

Checking I found:

$ xmllint --valid --noout
http://www.ibiblio.org/hhalpin/homepage/notes/vcardtable.html:29: element
div: validity error : ID v.Address already defined
w3.org/2006/vcard/ns#Address">v:Address</a></td><td></td><td><div id="v.Address"
http://www.ibiblio.org/hhalpin/homepage/notes/vcardtable.html:48: element
tr: validity error : Element tr content does not follow the DTD, expecting
(th | td)+, got (td td a td td )
</tr><tr id="v.url">
http://www.ibiblio.org/hhalpin/homepage/notes/vcardtable.html:134: element
tr: validity error : ID v.role already defined
</tr><tr id="v.role">

However GRDDL.py was generating triples.   It was not obvious to me
that you are assuming the GRDDL process runs in WF-only XML mode.

I shall change Raptor's use of libxml accordingly, if this is
the case.

Is XML validation of the profile/namespace URIs, XSLT documents
also ignored?  I would assume not, since they are somebody else's
mime type, spec.  RDF/XML aka application/rdf+xml does use validation.

Received on Saturday, 10 February 2007 06:13:36 UTC

This archive was generated by hypermail 2.3.1 : Tuesday, 6 January 2015 19:55:02 UTC