OASIS Mailing List ArchivesView the OASIS mailing list archive below
or browse/search using MarkMail.


Help: OASIS Mailing Lists Help | MarkMail Help



   Re: [xml-dev] [good] Question about NS 1.1

[ Lists Home | Date Index | Thread Index ]

the infoset is not itself the problem. the problem begins where one
expects or specifies that the set of "in-scope" namespaces be available
as a static value.

i'm curious how that came to pass.


Leigh Dodds wrote:
> I think I'm misunderstanding something, can anyone point
> where my train of thought is being derailed:
> - The Infoset defines that the namespace information items
> for an element are all those that are in scope. i.e. defined
> on this element or it's ancestors.
> - This leads to bleeding of namespaces from ancestors causing
> the problems cited in the NS 1.1 Reqs. w.r.t SOAP/XQuery
> - This leads to revising the namespace spec to allow undeclaring of
> namespaces, alleviating the issues in the other specifications.
> Why let changes ripple out like this? Why can't the infoset definitions be
> changed? Why does an element need namespace information items?
> I'm sure there's a good reason, I'm just not sure what it is.
> Cheers,


News | XML in Industry | Calendar | XML Registry
Marketplace | Resources | MyXML.org | Sponsors | Privacy Statement

Copyright 2001 XML.org. This site is hosted by OASIS