- From: Norman Walsh <Norman.Walsh@Sun.COM>
- Date: Wed, 18 Apr 2007 12:16:24 -0400
- To: public-xml-processing-model-wg@w3.org
Received on Wednesday, 18 April 2007 16:16:53 UTC
/ Alex Milowski <alex@milowski.org> was heard to say: |> <p:store> |> <p:option name="method" select="'html'"/> |> ... |> </p:store> | | That doesn't work for my use case. I want to associate | serialization parameters to output ports of pipelines. Of pipelines, or of steps? It seems to me that the pipeline processor can do whatever it wants with pipeline outputs. That's explicitly out of scope. | 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. I don't follow the analogy. But in any event, my knee jerk reaction to having outputs carry around extra metadata about their anticipated serialization is strongly negative. Be seeing you, norm -- Norman Walsh XML Standards Architect Sun Microsystems, Inc.
Received on Wednesday, 18 April 2007 16:16:53 UTC