- From: Jeni Tennison <jeni@jenitennison.com>
- Date: Fri, 25 May 2007 19:48:56 +0100
- To: public-xml-processing-model-wg <public-xml-processing-model-wg@w3.org>
Alessandro Vernet wrote:
> But instead of adding the concept of parameters to XProc just for
> XSLT, can't we just deal with that at the level of the XSLT component?
> That would mean passing parameters in a document, say to a
> "parameters" input of the XSLT component.
That was the essence of my proposal. The only addition was <p:parameter>
because otherwise creating parameter sets based on options is incredibly
tedious:
<p:pipeline name="pipe">
<p:input name="source" />
<p:option name="view" />
<p:string-replace name="construct-parameters">
<p:input port="source">
<p:inline>
<c:parameters>
<c:parameter name="view" value="" />
</c:parameters>
</p:inline>
</p:input>
<p:option name="match"
value="/c:parameters/c:parameter[@name = 'view']" />
<p:option name="replace" select="$view" />
</p:string-replace>
<p:xslt>
<p:input port="source">
<p:pipe step="pipe" source="source" />
</p:input>
<p:input port="stylesheet">
<p:document href="style.xsl" />
</p:input>
<p:input port="parameters">
<p:pipe step="construct-parameters" source="result" />
</p:input>
</p:xslt>
</p:pipeline>
becomes:
<p:pipeline name="pipe">
<p:input name="source" />
<p:option name="view" />
<p:xslt>
<p:input port="stylesheet">
<p:document href="style.xsl" />
</p:input>
<p:parameter name="view" select="$view" />
</p:xslt>
</p:pipeline>
Cheers,
Jeni
--
Jeni Tennison
http://www.jenitennison.com
Received on Friday, 25 May 2007 18:49:01 UTC