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

Re: Namespaces? (was: Enlightenment via avoiding the T-word)

  • From: Seairth Jacobs <seairth@s...>
  • To: xml-dev <xml-dev@l...>
  • Date: Wed, 29 Aug 2001 14:07:11 -0400

nested namespace
Evan Lenz wrote:
> Seairth Jacobs wrote:
> > The problem with the XML Namespace specification is that it is designed
to
> > disambiguate the two schemas at the document instance level.
>
> Sorry, but this is woefully inaccurate, and I'm sickened by the thought
that
> it might have been the XML Schemas spec that made you conclude this.

Sorry your are sick, but  XML Schemas itself has nothing to do with this.  I
was speaking in the generalized concept of a schema, not the specific
syntactic definition of one.  Yes, I understand that the spec does not
specify an explicit link between the Namespace name and a specific schema or
XML Schema.  However, one of the common practical uses of the Namespace is
to "scope" two conflicting elements such that they no longer conflict.  If
there is no conflict to start with, what is the value of the Namespace (esp.
if it it not explicitly tied to a schema definition)?

> Namespaces disambiguate names at the element or attribute name level. I'm
> sure someone out there will also qualify this as bad practice, but many of
> my company's document types (distinct de facto schemas) use the same
> namespace. There's nothing in the Namespaces spec that disallows us from
> doing this, or that makes us anticipate that 1-1 mappings between
namespaces
> and schemas will be considered the world over to be the only reasonable
> practice.

Sure, there is nothing wrong with having several document types (schemas)
that use the same Namespace... as long as none of those document types that
have the same element declaration that can be used in the same exact XPath
are combined.  As soon as you have combined two document types into a new
document type, two elements of the same name and the same scoped usage will
conflict.  If they are both within the same Namespace, then the Namespace
here is useless.  You either have to start doing nested namespaces or you
have to rename one of the elements to avoid the conflict.  The nested
namespace concept is just too much to think about.  The renaming concept
goes back to what I was originally saying...

Seairth Jacobs
seairth@s...





PURCHASE STYLUS STUDIO ONLINE TODAY!

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.
Email
First Name
Last Name
Company
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.