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

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

From: Innovimax SARL <innovimax@gmail.com>
Date: Tue, 17 Apr 2007 23:39:01 +0200
Message-ID: <546c6c1c0704171439s6085c3f8m454dda5ac647d823@mail.gmail.com>
To: "Alex Milowski" <alex@milowski.org>
Cc: public-xml-processing-model-wg@w3.org

Alex,

On 4/17/07, Alex Milowski <alex@milowski.org> wrote:
>
>
> On 4/17/07, Jeni Tennison <jeni@jenitennison.com> wrote:
> >
> > Mohamed,
> >
> > Innovimax SARL wrote:
> > > On 4/17/07, Jeni Tennison <jeni@jenitennison.com> wrote:
> > >> IMO, the result of an XSLT transformation is always a (sequence of)
> > >> documents (node trees). It's only when they're serialised (a separate
> > >> step, with no output) that you might get a text or HTML document.
> > >
> > > But are we going to tell to people that already have crafted their
> > > foo2csv or foo2html xslt stylesheet, that if they want to put it into
> > > XProc, they won't be able to do that ?
> >
> > IMO, we *must* support serialization to HTML documents. But I think it's
> > perfectly acceptable to do so via a separate step:
> >
> > <p:xslt>
> >    <p:input name="stylesheet">
> >      <p:document href="foo2html.xsl" />
> >    </p:input>
> > </p:xslt>
> > <p:serialize>
> >    <p:option name="href" value=" result.html" />
> >    <p:option name="method" value="html" />
> > </p:serialize>
>
> We have a store step and so we could add a serialization method option to
> that
>  step.
>
> I would also like to have a way of associating a serialization method to a
> pipeline output so that when an implementation "binds" the output, it knows
> what serialization is preferred.  For example, if a pipeline is used to
> implement
> a web service that is suppose to return HTML, I'd like the ability to say:
>
> <p:pipeline name="service" ...>
>    <p:output name="result" method="html">
>       ...
>    </p:output>
> ...
> </p:pipeline>
>
> Maybe this is done via another element:
>
>
>  <p:pipeline name="service" ...>
>     <p:output name="result">
>        <p:serialization method="html"/>
>        ...
>     </p:output>
>  ...
>  </p:pipeline>
>
> or another binding element:
>
>  <p:pipeline name="service" ...>
>    <p:output name="result">
>       ...
>     </p:output>
>     <p:serialization method="html" port="result"/>
>  ...
>  </p:pipeline>

You are typing flow here, isn't it ? So you' re going a little bit
further than me.
I was just proposing xml and non-xml (text)
But I will be ok to stick to @method values

Mohamed


-- 
Innovimax SARL
Consulting, Training & XML Development
9, impasse des Orteaux
75020 Paris
Tel : +33 8 72 475787
Fax : +33 1 4356 1746
http://www.innovimax.fr
RCS Paris 488.018.631
SARL au capital de 10.000 
Received on Tuesday, 17 April 2007 21:39:04 GMT

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