W3C home > Mailing lists > Public > public-rdf-in-xhtml-tf@w3.org > October 2004

xml:id and validation

From: Jeremy Carroll <jjc@hplb.hpl.hp.com>
Date: Tue, 26 Oct 2004 15:39:30 +0100
Message-ID: <417E61A2.1020306@hplb.hpl.hp.com>
To: public-rdf-in-xhtml-tf <public-rdf-in-xhtml-tf@w3.org>


It seems to me that some of the goals of RDF/A depend on validation ...
I raise this not because I see it as a problem, but because I am aware 
that some people do.
I might be wrong here, it interacts with XHTML modularisation and 
documents from multiple namespaces.

====

Here is my thought process:

RDF/A is explicitly a set of attributes to be used within an XML host 
language, e.g. XHTML.
The attributes do not themselves have qualified names, and so depend on 
the namespace of the element.

Thus if we have svg and xhtml2 mix we may find something like

<svg:svg id="image">
    <xhtml2:meta property="dc:creator" content="an artist"/>
</svg:svg>

The meta element has a property and an object and so takes its subject 
from the parent.
The subject of the parent is either an xml:id or a gensymed blank node, 
depending on whether the id attribute on svg:svg is, or is not, an ID 
attribute. IIRC this can only be resolved by looking at the DTD.

===

I think my implementation would be likely to treat any id as an ID, in 
this sort of case - in practice the cost of rejecting invalid xhtml is 
just too high to require validation.

Jeremy
Received on Tuesday, 26 October 2004 14:39:57 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Tuesday, 8 January 2008 14:14:59 GMT