W3C home > Mailing lists > Public > public-xml-processing-model-wg@w3.org > March 2007

Re: in-scope namespaces & inline documents

From: Alex Milowski <alex@milowski.org>
Date: Wed, 14 Mar 2007 08:16:47 -0700
Message-ID: <28d56ece0703140816p547f91c9g86301aac50f3dcd9@mail.gmail.com>
To: public-xml-processing-model-wg <public-xml-processing-model-wg@w3.org>
On 3/14/07, Henry S. Thompson <ht@inf.ed.ac.uk> wrote:
>
> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
>
> Alex Milowski writes:
>
> >
> > The problem is that the  in-scope namespaces  has namespaces
> > that aren't declared on that element.  As such, you need to fabricate
> > the namespace declarations.  This is the difference between the
> > [in-scope namespaces] property and the [namespace attributes]
> > property of the element information item.
>
> I still don't see your point.  The infoset has all the information the
> pipeline needs.  Serialisation of such a document has work to do, but
> that's always the case when sub-trees are serialised.



If you map  that infoset back to a DOM for processing through JAXP  (which
is one thing I do),  what are the namespace attributes?

If you don't fabricated namespace attributes for all the in-scope
namespaces,
the compile of the XSLT transformation will fail.


-- 
--Alex Milowski
"The excellence of grammar as a guide is proportional to the paucity of the
inflexions, i.e. to the degree of analysis effected by the language
considered."

Bertrand Russell in a footnote of Principles of Mathematics
Received on Wednesday, 14 March 2007 15:17:35 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Tuesday, 8 January 2008 14:21:50 GMT