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

Namespaces 'n Schemas

  • To: "Xml-Dev" <xml-dev@l...>
  • Subject: Namespaces 'n Schemas
  • From: "Jim Theriot" <Jim.Theriot@p...>
  • Date: Tue, 26 Mar 2002 11:42:12 -0600
  • Importance: Normal
  • In-reply-to: <NDBBKGBEKKCNMDLMKFOIGEPDDMAA.Jim.Theriot@P...>

jim theriot
I hope someone can help me with an apparent discrepancy between the
Namespaces spec and the XML Schema spec and XSV:

According to the Namespaces spec, each element in an XML document (qualified
or unqualified) has a type name comprised of a local name and an optional
namespace name.  The value of the namespace name is determinable,
independent of any schema information, by finding the applicable 'xmlns'
attribute and taking its value.  There is a default mechanism, so that both
qualified and unqualified names may be equivalently associated with a
namespace.  I assume that association by qualification and association by
inheritance from a qualified ancestor are 'equivalent' - at least the
namespaces spec doesn't define any intended distinct semantic.

The XML Schema spec places restrictions:  in certain cases (depending on
'elementFormDefault', globality of declaration, default namespace
declaration in the instance, ...) a qualified name must be used or may not
be used.  Does the XML Schema contradict the Namespaces resolution logic, or
does it only require or prohibit qualification?  Would the namespace
associations resolved by the Namespaces algorithm ever be different than the
association resolved according to the XML Schema spec?  I notice that when
XSV reports the erroneous lack of qualification of an element, it reports it
as being in no namespace, rather than as an unqualified element in its
inherited namespace -- is this a reporting shorthand, or an indication that
XSD defines a namespace inheritance logic that overrides one defined in the
namespaces spec?

If a document is parsed with a DOM parser, is the resulting infoset a tree
with element nodes and namespaces associated in accordance with the
Namespaces spec?  If the infoset is then validated with an XML Schema
validator, wouldn't the issue of explicit qualification of element names
necessarily be indeterminate?  Or do I have an incorrect view of the
'canonicalness' of the infoset?  Or is the explicitness of association
somehow an information or semantic issue and not just a lexical one?

Thanks in advance for any enlightenment,
Jim Theriot
POSC -- Energy eStandards
9801 Westheimer, Suite 450
Houston TX 77042


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.