[XML-DEV Mailing List Archive Home] [By Thread] [By Date] [Recent Entries] [Reply To This Message]

Re: A multi-step approach on defining object-orientednatureof

dom only one namespace

John Cowan wrote:

> Joe English scripsit:
> >     * Do not use default namespace bindings
> But if only one namespace is involved, then making it the default namespace
> is not pernicious.

It still complicates things for applications, since
the default namespace is one more piece of information
they need to keep track of, the rules for reserializing
need to account for (the) default namespace, et cetera.

Besides, the property of only using one namespace is not
preserved under all operations: if you insert an element
or attribute from a new namespace, then what do you do
with the previously-defaulted element names?

(Actually, I would go one step further and argue that
any XML vocabulary which is not designed to be mixed
with elements from other vocabularies ought not to use
namespaces at all.  There are valid arguments against
this position, of course.)

--Joe English



Purchasing Stylus Studio from our online shop is Easy, Secure and Value Priced!

Buy Stylus Studio Now

Download The World's Best XML IDE!

Accelerate XML development with our award-winning XML IDE - Download a free trial today!

Don't miss another message! Subscribe to this list today.
First Name
Last Name
Subscribe in XML format
RSS 2.0
Atom 0.3

Stylus Studio has published XML-DEV in RSS and ATOM formats, enabling users to easily subcribe to the list from their preferred news reader application.

Stylus Studio Sponsored Links are added links designed to provide related and additional information to the visitors of this website. they were not included by the author in the initial post. To view the content without the Sponsor Links please click here.

Site Map | Privacy Policy | Terms of Use | Trademarks
Free Stylus Studio XML Training:
W3C Member
Stylus Studio® and DataDirect XQuery ™are products from DataDirect Technologies, is a registered trademark of Progress Software Corporation, in the U.S. and other countries. © 2004-2013 All Rights Reserved.