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 17:34:47 -0700
Message-ID: <28d56ece0704181734h4459f9f4ke577ca4bd4461c99@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/18/07, Alex Milowski <alex@milowski.org> wrote:
> > The same thing that happens when you import a transformation
> > and change the output method.  The inner output method is
> > ignored.
> >
> > 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.
> This is consistent with XSLT, and I am all for consistency with XSLT.
> But like Norm, I don't like the idea of associating a serialization
> method with a pipeline output. I like to keep pipeline outputs as
> simple as possible. If an output needs to be serialized, this can be
> done outside of the pipeline, for instance in another pipeline, which
> decides how (html, text, ...) and where (HTTP response, file on disk,
> ...) the data is serialized.

If the pipeline really needs to convey to the outside world how its
> output should be serialized, it can do so for instance using an other
> output, which contains the serialization method.

What then is the URI of the location of the entity body of an HTTP
response?   Our current store step requires a URI to store the

--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 Thursday, 19 April 2007 00:35:00 UTC

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