W3C home > Mailing lists > Public > www-rdf-interest@w3.org > January 2002

Re: rdf-ns-prefix-confusion

From: Uche Ogbuji <uche.ogbuji@fourthought.com>
Date: Tue, 22 Jan 2002 07:44:52 -0700
Message-Id: <200201221444.g0MEiqk09320@localhost.localdomain>
To: Dave Beckett <dave.beckett@bristol.ac.uk>
cc: www-rdf-interest <www-rdf-interest@w3.org>
I think I've pretty much responded to everything in this message, so it looks 
as if we're narrowing in on "agree to disagree".


> and you propose (1)
>   <rdf:Description about="http://example.org/somewhere/" a:b="x" c:d="y" />
> or even with xmlns= the RDF namespace
>   <Description about="http://example.org/somewhere/" a:b="x" c:d="y" />
> 
> which looks odd; why would 'about' be bare, a:b and c:d require prefixes.

I don't see a problem here at all.  Clearly the person viewing the document 
understands default namespaces, otherwise they have far bigget conceptual 
hurdles in front of them.

Therefore, this makes the above no more odd whatsoever than defining rdf: and 
using


<rdf:Description about="http://example.org/somewhere/" a:b="x" c:d="y" />


> > Again, works for XSLT, should work for RDF.
> 
> That just seems horrible.
> 
> I think this is something to do with RDF/XML expecting to see lots
> elements and attributes with many namespaces defined, so picking the
> rdf ones out of them should be easy.  What about embedding?  Which
> one gets the attributes?  The innermost XML standard?  Just a mess.

I don't follow you here.  Do you have an example?


-- 
Uche Ogbuji                               Principal Consultant
uche.ogbuji@fourthought.com               +1 303 583 9900 x 101
Fourthought, Inc.                         http://Fourthought.com 
4735 East Walnut St, Boulder, CO 80301-2537, USA
XML strategy, XML tools (http://4Suite.org), knowledge management
Received on Tuesday, 22 January 2002 09:52:53 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Monday, 7 December 2009 10:51:52 GMT