Re: Question on namespace confusion (more on Re: New syntax spec )

At 05:14 PM 9/18/01 +1000, Rick Jelliffe wrote:
> > This was done due to widespread confusion about
> > namespaces and attributes.  Different deployed applications thought
> > that in
> >      <eg:property resource="http://example.org/resource2/"/>
> >
> > resource actually was eg:resource, others that it was
> > (default xmlns namespace):resource, and others recognised it
> > as the rdf special attribute that it is.
>
>Well, it is certainly not eg:resource nor defaultNamespace:resource
>(see 5.2 "Note that default namespaces do not apply directly to attributes.")
>nor rdf:resource, according to the namespaces spec.
>
>A local resource attribute on an element in another namespace might
>be RDF's resource, but it is never rdf:resource.
>
>Sorry for being really thick on this, but I tend to think the refactored
>RDF still does not strike at the heart of the problem I have: I know
>the XML layer, I know the namespace layer, but RDF by providing home-made
>grammars (whether syntax or information set) lumps together bits of the
>requirements from XML, Namespace and RDF without discipline.

Let's see if this helps:

RDF requires that every property used is identified by a URI + optional 
fragment identifier.  It defines a rule for constructing a such URI from a 
namespace-qualified attribute or element name used as a property.

If we allow unqualified attributes, how is the corresponding URI to be 
constructed?  I think a satisfactory answer to this question might allow 
the restriction to be reconsidered.

#g


------------
Graham Klyne
GK@NineByNine.org

Received on Tuesday, 18 September 2001 07:19:29 UTC