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

Re: XSLT non-XML output (was: standard components edits)

From: Alex Milowski <alex@milowski.org>
Date: Tue, 17 Apr 2007 20:23:37 -0700
Message-ID: <28d56ece0704172023u7c7a984erc1b0c51f2abda8c5@mail.gmail.com>
To: public-xml-processing-model-wg@w3.org
On 4/17/07, Innovimax SARL <innovimax@gmail.com> wrote:
>
>
> You are typing flow here, isn't it ? So you' re going a little bit
> further than me.



Well... not really... regardless of the syntax, all I want is the
ability for the pipeline author to declare serialization intent
associated with a pipeline output port much as an XSLT transformation
author does with the output method.

I wasn't thinking of this as a general facility for any step.

...adding a store step doesn't help because that means
I need to know *where* the document is being stored.  I don't know
that because that happens in the environment in which the
pipeline is run.  In some cases, that is the protocol wire!


-- 
--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, 18 April 2007 03:23:40 GMT

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