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

RE: Errors in Kendall Clark's xml.com article on QNames

• To: "Henry S. Thompson" <ht@c...>
• Subject: RE: Errors in Kendall Clark's xml.com article on QNames
• From: "Evan Lenz" <elenz@x...>
• Date: Wed, 13 Feb 2002 13:56:37 -0800
• Cc: <xml-dev@l...>
• Importance: Normal
• In-reply-to: <f5b1yfpqd3g.fsf@c...>

Henry Thompson wrote:
> > If it
> > sits better with you, I'll add the word "non-redundant": "exactly where
> > every [non-redundant] xmlns declaration is and what prefix it uses".
>
> It's the _exactly where_ part I'm disputing.  I couldn't care less
> where the namespaces which are in scope are declared, and the
> [in-scope namespaces] property doesn't record that.

You're quite right that on the single-element level, the [in-scope
namespaces] property does not indicate where the namespace was declared.
However, I can determine that information by recursively traversing the
[parent] property. In other words, for a given Infoset (i.e. the entire
document), I indeed can tell you _exactly where_ all the non-redundant
namespace declarations occurred in the XML source (modulo attribute order).
Individual xmlns declarations are more significant than you're implying. The
extra level of indirection/abstraction provided by the Infoset does not take
away from the fact that this information needs to be preserved.

Evan

• References:
  • Re: Errors in Kendall Clark's xml.com article on QNames
    • From: ht@c... (Henry S. Thompson)

• Prev by Date: Re: Errors in Kendall Clark's xml.com article on QNames
• Next by Date: Re: Errors in Kendall Clark's xml.com article on QNames
• Previous by thread: Re: Errors in Kendall Clark's xml.com article on QNames
• Next by thread: RE: Service discovery
• Index(es):
  • Date
  • Thread