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

RE: ANN: SAX Filters for Namespace Processing

• From: "Simon St.Laurent" <simonstl@s...>
• To: Michael Brennan <Michael_Brennan@a...>
• Date: Tue, 31 Jul 2001 20:25:50 -0400

On 31 Jul 2001 17:03:18 -0700, Michael Brennan wrote:
> Given this example, I'd say it is terribly dangerous to make the general
> assumption that an unqualified child element is equivalent to one in the
> containing namespace. You have to know the explicit intent of the author.

That's why the namespace filters allow developers to explicitly include
and exclude particular namespaces from such extension to their child
elements. For example, if you want to make sure SOAP envelopes don't
influence their child elements, it's simple:

<namespaces xmlns="http://simonstl.com/ns/namespaces/elements/">
<include nsURI="##any" />
<exclude nsURI="http://www.w3.org/2001/6/soap-envelope" />
</namespaces>

Exclusions always override inclusions.

Honestly, though, I'm finding less and less interest in (or sympathy
for) the intentions of the author.  It seems like these are really
choices for recipients, to be made with consideration for how much they
have to gain or lose by dealing with authorial intention.

Maybe I've just spent too long in publishing, where the reader is the
final arbiter.

• Follow-Ups:
  • Re: ANN: SAX Filters for Namespace Processing
    • From: Ronald Bourret <rpbourret@r...>

• References:
  • RE: ANN: SAX Filters for Namespace Processing
    • From: Michael Brennan <Michael_Brennan@a...>

• Prev by Date: Re: Namespaces,
• Next by Date: Re: Question on id constraints
• Previous by thread: RE: ANN: SAX Filters for Namespace Processing
• Next by thread: Re: ANN: SAX Filters for Namespace Processing
• Index(es):
  • Date
  • Thread