Lists Home |
Date Index |
"Evan Lenz" <email@example.com> writes:
> HT wrote:
> > 1) "Consequently, all scope information, i.e. exactly where every
> > xmlns declaration is and what prefix it uses, must always be passed
> > to the application, regardless of whether it's needed or not..."
> > (quoting Evan Lenz , ellipses in original)
> > This is wrong on two counts. The Infoset REC clearly defines what
> > _is_ required for applications that need it, namely the [in-scope
> > namespaces] property, which is much simpler than "where every xmlns
> > declaration is and what prefix it uses".
> The [in-scope namespaces] property is just another representation of the
> same information. The only xmlns attributes that get lost are those that
> merely repeat a unique prefix-URI pair that's already in-scope. These hardly
> ever arise in practice, so it's hard to argue this is "much simpler". 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.
Henry S. Thompson, HCRC Language Technology Group, University of Edinburgh
W3C Fellow 1999--2001, part-time member of W3C Team
2 Buccleuch Place, Edinburgh EH8 9LW, SCOTLAND -- (44) 131 650-4440
Fax: (44) 131 650-4587, e-mail: firstname.lastname@example.org