• From: Richard Tobin <richard@c...>
• To: simonstl@s...
• Date: Tue, 31 Jul 2001 17:27:14 +0100 (BST)

In article <996593189.1232.2.camel@l...> you write:

>Between the qualified/unqualified usage, the codification of QName as
>type which extends beyond element and attribute names, and the use of
>QNames in attribute values used by W3C XML Schema itself, it's
>reasonably clear that W3C XML Schema has enhanced/extended/broken (take
>your pick) what was defined by Namespaces in XML 1.0.

I understand your point, but there is still a clear distinction to
be drawn:

 - Namespaces in XML defines how element and attribute names are
   interpreted as referring to namespaces.  It specifies the
   namespace (or no namespace) that a qualified element or attribute
   name is in.

 - Given an element in no namespace, there are many ways a user can
   interpret it.  XML Schema provides support for two different
   interpretations.  It doesn't change the fact that the element
   is in no namespace.

-- Richard
-- 
Spam filter: to mail me from a .com/.net site, put my surname in the headers.

FreeBSD rules!

• Follow-Ups:
  • Namespaces, W3C XML Schema (was Re: ANN: SAX Filters for NamespaceProcessing)
    • From: "Simon St.Laurent" <simonstl@s...>

• References:
  • RE: ANN: SAX Filters for Namespace Processing
    • From: "Simon St.Laurent" <simonstl@s...>

• Prev by Date: RE: ANN: SAX Filters for Namespace Processing
• Next by Date: Re: Blueberry/Unicode/XML
• Previous by thread: RE: ANN: SAX Filters for Namespace Processing
• Next by thread: Namespaces, W3C XML Schema (was Re: ANN: SAX Filters for NamespaceProcessing)
• Index(es):
  • Date
  • Thread