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

Re: XSLT non-XML output

From: Alex Milowski <alex@milowski.org>
Date: Wed, 18 Apr 2007 14:27:14 -0700
Message-ID: <28d56ece0704181427g43db2f41p21c25c18292312d1@mail.gmail.com>
To: public-xml-processing-model-wg <public-xml-processing-model-wg@w3.org>
On 4/18/07, Alessandro Vernet <avernet@orbeon.com> wrote:
> On 4/17/07, Alex Milowski <alex@milowski.org> wrote:
> > That doesn't work for my use case.  I want to associate
> > serialization parameters to output ports of pipelines.  That way
> > the environment in which the pipeline is executed can do
> > the "right thing" much as is the case when you execute
> > an XSLT transform with the 'html' serialization output method.
> Alex, assuinge we allow the pipeline author to specify that a certain
> output should use the html serialization method, what happens to this
> output when this pipeline is called from another pipeline?

The same thing that happens when you import a transformation
and change the output method.  The inner output method is

In the case of calling a pipeline, the outputs of the called pipeline
have to be XML and aren't being serialized.  As such, the serialization
method information can safely be ignored.

--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

Bertrand Russell in a footnote of Principles of Mathematics
Received on Wednesday, 18 April 2007 21:27:19 UTC

This archive was generated by hypermail 2.3.1 : Tuesday, 6 January 2015 21:32:42 UTC