ASPN ActiveState Programmer Network
ActiveState
/ Home / Perl / PHP / Python / Tcl / XSLT /
/ Safari / My ASPN /
Cookbooks | Documentation | Mailing Lists | Modules | News Feeds | Products | User Groups


Recent Messages
List Archives
About the List
List Leaders
Subscription Options

View Subscriptions
Help

View by Topic
ActiveState
.NET Framework
Open Source
Perl
PHP
Python
Tcl
Web Services
XML & XSLT

View by Category
Database
General
SOAP
System Administration
Tools
User Interfaces
Web Programming
XML Programming


MyASPN >> Mail Archive >> xml-dev
xml-dev
Re: namespace prefixes within attribute values
by Eve L. Maler other posts by this author
Mar 9 2000 10:26PM messages near this date
Re: namespace prefixes within attribute values | It's the syntax. . .
At 11:53 AM 3/9/00 -0500, Simon St.Laurent wrote:
> Both the XML Schemas drafts and the XLink drafts use namespace prefixes
> within attribute values.  As far as I can tell, this usage isn't sanctioned
> by the Namespaces in XML Recommendation.

As Richard Tobin has already noted, the namespace declaration information 
will typically be made available; the higher-level application would only 
be responsible for catching/validating the usage of a prefix in the 
attribute value.  I'm comfortable with that, as far as it goes.  I have a 
different problem.

Back in February, I wrote up a minority opinion on QName usage in XLink 
attribute values (located at 
http://lists.w3.org/Archives/Public/www-xml-linking-comments/2000JanMar/0041 
.html).  This writeup didn't quite describe my biggest concern, but I 
finally figured out a way to explain it:

The Namespaces specification 
(http://www.w3.org/TR/REC-xml-names/#sec-intro) defines an XML namespace as 
a "collection of names ... which are used in documents as element types and 
attribute names."  I can see using QNames attribute values when you're 
manipulating element types and attribute names, as is done in XML Schema 
and XSLT.  However, in XLink, QNames are used -- in the true Namespaces 
specification sense -- for values that have nothing to do with element 
types and attribute names.

A lot of people are hoping that one day they'll be able to point to some 
kind of document (compound or not...whatever) that will serve as the 
definitive source for information about a namespace.  I fear that any 
future work to figure this out will be hampered by legacy cases of names 
that don't fall into the sanctioned categories.  If I've defined 
show="myco:popupFor10Seconds" to have meaning in my XLink application, and 
I want to define the name "popupFor10Seconds" in my namespace definition 
document, have I now precluded the possibility of having a 
<popupFor10Seconds> ? an <x myco:popupFor10Seconds="..." />?

         Eve
--
Eve Maler            Sun Microsystems
elm @ east.sun.com    +1 781 442 3190

***************************************************************************
This is xml-dev, the mailing list for XML developers.
To unsubscribe, mailto:majordomo@xml.org&BODY=unsubscribe%20xml-dev
List archives are available at http://xml.org/archives/xml-dev/
***************************************************************************
Thread:
Simon St.Laurent
Richard Tobin
Eve L. Maler

Privacy Policy | Email Opt-out | Feedback | Syndication
© 2004 ActiveState, a division of Sophos All rights reserved