W3C home > Mailing lists > Public > w3c-rdfcore-wg@w3.org > January 2002

Fwd: Re: rdf-ns-prefix-confusion

From: Graham Klyne <GK@ninebynine.org>
Date: Tue, 15 Jan 2002 11:26:23 +0000
Message-Id: <5.1.0.14.2.20020115111833.00a9fac0@joy.songbird.com>
To: RDF core WG <w3c-rdfcore-wg@w3.org>
Responding to the debate in www-rdf-interest...

> > XML Namespace defines that unqualified attributes do not share
> > the namespace of their element - so 'about' here has no relationship
> > to the element (which is namespace prefixed, although I'm using the
> > defult one here).
>
>Yes it does.  The element is the owner element of the attribute.  This is 
>good
>enough for any half-decent tool to treat it as the (original) RDF spec
>prescribes

I'm personally agnostic about this matter, but it occurs to me that we 
*could* allow unprefixed ID=, about= and resource= attributes, and others, 
within elements whose name is associated with the RDF namespace without 
creating any ambiguity.

My reasoning, supported in part by the (non-normative) appendix A.2 of XML 
namespace spec, is that the meaning of such attributes can be defined by 
the element in which they appear.

Thus, we can define that for all element types in the RDF namespace, the 
appearance of an ID= attribute will be regarded as equivalent to rdf:ID=, 
about= equivalent to rdf:about=, resource= equivalent to rdf:resource=, etc.

But I think it's important that the qualifying prefix be retained when 
these attributes are used in non-RDF elements, as when using a class name 
in place of rdf:Description, etc, and most property elements.

Just a thought...

#g




------------
Graham Klyne
GK@NineByNine.org
Received on Tuesday, 15 January 2002 08:09:58 EST

This archive was generated by hypermail pre-2.1.9 : Wednesday, 3 September 2003 09:43:54 EDT