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

Re: rdf:resource, reference to same-named attributes and elements in the same namespace

From: by way of <a.cuellar@auckland.ac.nz>
Date: Fri, 12 Apr 2002 06:52:42 -0400
Message-Id: <200204121431.KAA03267@tux.w3.org>
To: www-rdf-interest@w3.org
[freed from spam filter -rrs]

Date: Thu, 11 Apr 2002 21:26:27 -0400 (EDT)
Message-ID: <3CB63799.3546CEA3@auckland.ac.nz>
From: Autumn Cuellar <a.cuellar@auckland.ac.nz>
Organization: Bioengineering Research Group, University of Auckland
To: www-rdf-interest@w3.org
References: <3CB61E54.BCB11DD0@auckland.ac.nz>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit

Right.  Just went back to my XML Namespace spec and realized what I
really want to know is if there is a way to represent the expanded
attribute name (with namespace known) in an rdf:about attribute.  


Autumn Cuellar wrote:
> Hi,
> I've been writing an RDF Schema for our xml language, following the
> Dublin Core's example in their "Expressing Qualified Dublin Core in
> RDF/XML" document
> (http://dublincore.org/documents/2001/11/30/dcq-rdf-xml).  My problem
> concerns, well, namespaces, really.  The xml language I'm coding into
> RDFS has certain attributes that have the same name as an element.  For
> instance, if we have a units attribute with the value identifying units
> declared somewhere in the document, we'll declare the units with a
> <units> element.  There should be no problem with this.  An element and
> an attribute are two separate concepts.  Yet, they both occupy the same
> space in the namespace, i.e.
> http://www.example.org/example_xml_language#units.  Surely this problem
> has cropped up for others.  Suggestions for a way around it?
> Thank you for your help!
> --
> Autumn A. Cuellar
> Bioengineering Institute
> The University of Auckland
> New Zealand

Autumn A. Cuellar
Bioengineering Institute
The University of Auckland
New Zealand
Received on Friday, 12 April 2002 10:31:07 UTC

This archive was generated by hypermail 2.3.1 : Wednesday, 7 January 2015 15:07:40 UTC