W3C home > Mailing lists > Public > www-tag@w3.org > June 2006

RE: RDFa reliance on namespace declaration

From: Misha Wolf <Misha.Wolf@reuters.com>
Date: Wed, 14 Jun 2006 13:48:22 +0100
To: Ian Davis <iand@internetalchemy.org>, public-rdf-in-xhtml-tf@w3.org
Cc: www-tag@w3.org, newsml-2@yahoogroups.com
Message-id: <A29ADE959C70A1449470AA9A212F5D80020C997B@LONSMSXM06.emea.ime.reuters.com>

Hi Ian,

Good point.  NewsML 2 has also taken your approach #2.  What syntax 
is eRDF using for this?

------------------- NewsML 2 resources ------------------------------
http://www.iptc.org         | http://www.iptc.org/std-dev/NAR/1.0
http://www.iptc.org/std-dev | http://groups.yahoo.com/group/newsml-2

-----Original Message-----
From: public-rdf-in-xhtml-tf-request@w3.org
[mailto:public-rdf-in-xhtml-tf-request@w3.org] On Behalf Of Ian Davis
Sent: 14 June 2006 09:41
To: public-rdf-in-xhtml-tf@w3.org
Subject: RDFa reliance on namespace declaration

I'd like to highlight a likely problem with RDFa's use of qname-like 
constructs in attribute values. I'm referring to CURIEs here but the 
same applies to any binding between XML namespace declarations and text 
content in the XML.

The problem lies with the coupling of the specific prefix used in the 
namespace declaration with the prefix used in content. Any XML 
processor, such as an XSLT stylesheet or a SAX pipeline, can change the 
namespaces prefix arbitrarily thereby breaking the syntactic link 
between the qname/CURIE used in the attribute and the namespace

The breakage happens because the XML processor has no knowledge of the 
semantics of particular text content in specific attributes.

So, passing the following through a stylesheet:

<p class="contactinfo" about="http://example.org/staff/jo"
     My name is
     <meta property="contact:fn">
         Jo Smith

could very easily result in the following, with the consequent loss of 
all embedded triples:

<p class="contactinfo" about="http://example.org/staff/jo"
     My name is
     <meta property="contact:fn">
         Jo Smith

As far as I can tell the only solutions are:

1) replace use of CURIEs in content with namespaced elements/attributes

2) replace namespace declaration mechanism with declarations based in 
the actual content with semantics specified by RDFa

3) replace CURIEs in content with full URIs

4) change XML namespaces spec to somehow understand CURIEs/qnames in

I think 1 is unlikely given that we're working within the limits of DTD 
and XSD validation

2 is the approach used by eRDF

3 would work for copy and paste at the expense of looking ugly, but I 
don't believe visual impact is a requirement of RDFa?

4 seems difficult and would introduce yet another dependency for RDFa 

Blogging at... http://iandavis.com/blog
Working on... http://directory.talis.com/

To find out more about Reuters visit www.about.reuters.com

Any views expressed in this message are those of the individual sender, except where the sender specifically states them to be the views of Reuters Ltd.
Received on Wednesday, 14 June 2006 12:48:44 UTC

This archive was generated by hypermail 2.4.0 : Friday, 17 January 2020 22:56:12 UTC