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

RE: ANN: SAX Filters for Namespace Processing

• From: Evan Lenz <elenz@x...>
• To: "David E. Cleary" <davec@p...>, xml-dev <xml-dev@l...>
• Date: Tue, 31 Jul 2001 14:11:37 -0700

> > > In this case, I wish this usage had been considered during the
> > > development of the namespaces spec and dealt with explicitly.
> >
> > I wouldn't blame the namespaces spec for not handling this. The
> > namespaces spec is quite clear about how to get a universal name: get
> > the namespace URI from the prefix (or the default) and the local name
> > from the local name.
> >
> > Can you imagine the list of rules to disallow things?
>
> 1 rule. For an XML document to be namespace compliant, it will not contain
> any unqualified elements once any namespace is in scope.

...which would completely break XSLT literal result elements which represent
a pretty intuitive use case for unqualified child elements.

Also of note is the fact that XML Schemas was not the first technology to
use QNames in attribute values. Whether good or bad, that approach was
adopted by XSLT.

Evan Lenz
XYZFind Corp.

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

• References:
  • RE: ANN: SAX Filters for Namespace Processing
    • From: "David E. Cleary" <davec@p...>

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