OASIS Mailing List ArchivesView the OASIS mailing list archive below
or browse/search using MarkMail.


Help: OASIS Mailing Lists Help | MarkMail Help



   RE: [xml-dev] Partyin' like it's 1999

[ Lists Home | Date Index | Thread Index ]

> -----Original Message-----
> From: Derek Denny-Brown [mailto:derekdb@microsoft.com] 
> Sent: Wednesday, October 27, 2004 13:03
> To: Michael Kay; Alessandro Triglia; Hunsberger, Peter; 
> Bullard, Claude L (Len); Michael Champion
> Cc: xml-dev@lists.xml.org
> Subject: RE: [xml-dev] Partyin' like it's 1999
> > -----Original Message-----
> > From: Michael Kay [mailto:michael.h.kay@ntlworld.com]
> > 
> > It's too late to fix the problems now, but it's easy to 
> identify them.
> Agreed.  Understanding the problem means we can build APIs which
> alleviate the worst pain for the average user.  Writing a new spec
> doesn't those users.  Starting work on a new, cleaner design 
> isn't a bad
> idea, but we also need to address the concerns of people writing
> software today.  It will take another 5 years to get that spec
> implemented as ubiquitously as XML is now.  
> > I have advocated one change which I believe would alleviate the
> problems:
> > there should be a lexical representation of expanded names that uses
> the
> > URI
> > and local name, rather than prefix and local name, and this
> representation
> > should be permitted in any context where a lexical QName is 
> permitted,
> > including in element names and attribute names in source XML, in
> > QName-valued attributes, and in path expressions. This 
> would mean that
> any
> > XML fragment, XPath expression, etc, could be "namespace-normalized"
> to
> > make
> > it context free.
> Yes!

The XML Infoset already has that.  Each element information item and
attribute information item has a [namespace name] property, a [local name]
property, and a [prefix] property.

I think that a change to the XML 1.x syntax for improved support of
namespaces could be devised without affecting the XML Infoset and other
standards that are specified in terms of the XML Infoset (such as XML Schema
and SOAP 1.2).

Oh, well, XML Schema would be affected in a limited way, because of its
QName datatype (which imitates the prefix:localname notation inside values).
This ugly feature brings the "colon" notation into the infoset, creating a
vicious circle between the Infoset, XML 1.x + Namespaces, and the XML Schema
validity assessment.


> -derek
> -----------------------------------------------------------------
> The xml-dev list is sponsored by XML.org <http://www.xml.org>, an
> initiative of OASIS <http://www.oasis-open.org>
> The list archives are at http://lists.xml.org/archives/xml-dev/
> To subscribe or unsubscribe from this list use the subscription
> manager: <http://www.oasis-open.org/mlmanage/index.php>


News | XML in Industry | Calendar | XML Registry
Marketplace | Resources | MyXML.org | Sponsors | Privacy Statement

Copyright 2001 XML.org. This site is hosted by OASIS