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

 


Help: OASIS Mailing Lists Help | MarkMail Help

 


 

   Re: The Peace Process: DOM and namespaces...

[ Lists Home | Date Index | Thread Index ]
  • From: Tyler Baker <tyler@infinet.com>
  • To: Don Park <donpark@quake.net>
  • Date: Thu, 11 Feb 1999 00:25:47 -0500

Don Park wrote:

> Andrew,
>
> >Don Park suggests that we could "establish a business practice requiring
> all
> >URI used as namespace name to
> >not contain any illegal XML name characters."  That rules out "/", thereby
> >limiting namespaces to second-tier domain names and similar unsegmented
> >names. That goes against the desire for unlimited scalability and the goal
> >to allow _anyone_ to create namespace names as they need to.
>
> I guess what I am proposing is a creation of a new URI scheme for XML
> Namespace that is more friendly to namespace-ignorant applications.  The URI
> production rules are defined as:
>
> uri ::= scheme : path [ ? search ]
>
> We can use 'xmlns' as the URI scheme name, outlaw the optional search
> segment, and then use Java package naming scheme for the path.  Here is an
> example:
>
> <dh:foo xmlns:dh="xmlns:com.docuverse.dom.html." dh:bar="foobar"/>
>
> which expands to:
>
> <xmlns:com.docuverse.dom.html.foo
> xmlns:com.docuverse.dom.html.bar="foobar"/>

I like this idea except that your chances of the W3C adopting it are likely slim and none, so
is any idea of splitting XML 1.0 and "Namespaces in XML" into two different types of documents
so that applications are free to choose which method they want to use in their applications
without having to worry about handling the ambiguities that arise from combining XML 1.0 data
and "Namespaces in XML" data together all at once.  A clean break between the two
specifications I think would be good for XML.  It would end the namespaces issue as people who
want and need to use "Namespaces in XML" will use "Namespaces in XML" and those who don't want
to be bogged down with the complexities of "Namespaces in XML" or would prefer to use a
different method of managing unique names could choose to do so.  I just feel like some people
have the attitude that I will be using "Namespaces in XML" whether I like it or not.  Please,
lets formally split these two obviously different document formats for the good of XML and end
this namespaces issue right now.

Tyler


xml-dev: A list for W3C XML Developers. To post, mailto:xml-dev@ic.ac.uk
Archived as: http://www.lists.ic.ac.uk/hypermail/xml-dev/ and on CD-ROM/ISBN 981-02-3594-1
To (un)subscribe, mailto:majordomo@ic.ac.uk the following message;
(un)subscribe xml-dev
To subscribe to the digests, mailto:majordomo@ic.ac.uk the following message;
subscribe xml-dev-digest
List coordinator, Henry Rzepa (mailto:rzepa@ic.ac.uk)





 

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

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