W3C home > Mailing lists > Public > xproc-dev@w3.org > December 2009

RE: Difficulty overriding parameter values

From: <Toman_Vojtech@emc.com>
Date: Wed, 9 Dec 2009 04:36:44 -0500
Message-ID: <997C307BEB90984EBE935699389EC41C4F31FB@CORPUSMX70C.corp.emc.com>
To: <xproc-dev@w3.org>
Oops, of course I meant:

 

...

<p:identity>

  <p:input port="source">

    <p:pipe step="..." port="..."/>

  </p:input>

</p:identity>

...

 

Vojtech

 

From: xproc-dev-request@w3.org [mailto:xproc-dev-request@w3.org] On
Behalf Of Toman_Vojtech@emc.com
Sent: Tuesday, December 08, 2009 1:59 PM
To: xproc-dev@w3.org
Subject: RE: Difficulty overriding parameter values

 

	I was just investigating without luck if using a p:group I could
wrap say 5 variables and specify only once which port the following
statements are using?  (had a pascal "with" statement on my mind)  Is is
possible to do something that in xproc? 

	 

	It is possible. You can do it, for example, by wrapping the
variables (and the rest of the pipeline) in a p:group and "redirecting"
the default readable port using p:identity:

	 

	<p:declare-step>

	  ...

	  <p:identity>

	    <p:pipe step="..." port="..."/>

	  </p:identity>

	  <p:group> 

	    <p:variable name="v1" select="..."/>

	    <p:variable name="v2" select="..."/>

	    ... the rest of the sub-pipeline ...

	     </p:group>

	 </p:declare-step> 

	 

	It is not always a nice solution, but I guess you can see the
pattern. The thing with p:variable is that it must always come before
any steps in the pipeline, so wrapping it in some compound step is often
the only way to get more control over what you can connect it to.
	 

	Regards,

	Vojtech 
Received on Wednesday, 9 December 2009 09:37:26 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Wednesday, 9 December 2009 09:37:26 GMT