Lists Home |
Date Index |
- From: Ronald Bourret <firstname.lastname@example.org>
- To: "XML Developers' List" <email@example.com>, "'Lars Marius Garshol'" <firstname.lastname@example.org>
- Date: Tue, 9 Feb 1999 10:20:50 +0100
Lars Marius Garshol wrote:
> | It would be nice if and when the namespaces recommendation is
> | updated if it mas made a formality that a conforming namespace aware
> | processor strips namespace nodes from the document model before
> | presenting the parsed content to the application.
> Do you think this is really necessary? I think in some cases it would
> be desirable to see them, and in most cases not. So even if this
> change is made I think it should be "at user option".
> Anyway, it's a rather obvious user option, so methinks there isn't all
> that much need to mention it in the spec. The xmlproc namespace code
> currently has an option that lets the user decide whether the
> declaration attribute should be reported or not.
This is exactly the kind of thing that should be mentioned in this or any
other spec -- one person's obvious is another person's obscure and the
point of a spec is to sort it all out.
By the way, I was a little surprised to read that expat does not pass xmlns
attributes to the application. I had always assumed that attributes were
part of the document's data and therefore the processor was required to
pass them to the application. On re-reading the XML spec, I am not so
sure. Section 2.4 defines markup as "start-tags, end-tags, empty-element
tags, ..." Are attributes part of start-tags? If so, this would certainly
influence the question of whether to use elements or attributes, although I
find it hard to believe any parser wouldn't pass attributes to the
application. If not, why isn't expat's behavior illegal?
-- Ron Bourret
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)