Lists Home |
Date Index |
- From: "Bill la Forge" <email@example.com>
- To: "John Cowan" <firstname.lastname@example.org>, "XML Dev" <email@example.com>
- Date: Fri, 12 Feb 1999 11:15:53 -0500
From: John Cowan <firstname.lastname@example.org>
>> I'm writing a program that needs to use the DOM to process documents that use namespaces.
>> So I wrap John Cowan's inheritance filter
>Namespace filter, that is. The inheritance filter (as Bill knows
>but some may not) processes inheritable attributes like xml:lang
Sorry John, but I was actually thinking of a cross between the two,
where all xmlns attributes were inherited.
The advantages here are:
1. You can slip namespaces right past anything that isn't namespace aware;
2. You can manipulate the DOM without worries about scope;
3. You can strip the inherited values off on the output side, and have something
reasonably readable and predictable, with all the original xmlns attributes
preserved. (The names chosen may actually be meaningful to the author, mm?)
When you create new elements in such a DOM, the APPLICATION does need to
be aware of which namespace it is using, and supply the appropriate xmlns attribute.
That doesn't seem to be too much to ask.
xml-dev: A list for W3C XML Developers. To post, mailto:email@example.com
Archived as: http://www.lists.ic.ac.uk/hypermail/xml-dev/ and on CD-ROM/ISBN 981-02-3594-1
To (un)subscribe, mailto:firstname.lastname@example.org the following message;
To subscribe to the digests, mailto:email@example.com the following message;
List coordinator, Henry Rzepa (mailto:firstname.lastname@example.org)