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

Re: XSLT non-XML output

From: Norman Walsh <Norman.Walsh@Sun.COM>
Date: Tue, 17 Apr 2007 17:26:53 -0400
To: public-xml-processing-model-wg@w3.org
Message-ID: <87tzveelpe.fsf@nwalsh.com>
/ Alex Milowski <alex@milowski.org> was heard to say:
| We have a store step and so we could add a serialization method option to
| that
| step.

Yes, as I think I've said several times, I think our store step ought
to support the serialization parameters of XSLT.

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

I really dislike that.

|   </p:output>
| ...
| </p:pipeline>
|
| Maybe this is done via another element:
|
| <p:pipeline name="service" ...>
|   <p:output name="result">
|       <p:serialization method="html"/>

And I'm not a big fan of that.

How about:

  <p:store>
    <p:option name="method" select="'html'"/>
    ...
  </p:store>

                                        Be seeing you,
                                          norm

-- 
Norman Walsh
XML Standards Architect
Sun Microsystems, Inc.

Received on Tuesday, 17 April 2007 21:26:59 GMT

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