RE: Difficulty overriding parameter values

It looks like a bug to me. Could you try to use p:pipeline instead of
p:declare-step for the top-level pipeline? I remember that in the older
versions of the spec, the default binding to the pipeline's primary
parameter input port happened only when p:pipeline was used. Perhaps
Calabash does not handle this properly with p:declare-step?
 
Regards,
Vojtech


________________________________

	From: xproc-dev-request@w3.org [mailto:xproc-dev-request@w3.org]
On Behalf Of Kevin Flynn
	Sent: Friday, July 03, 2009 11:06 AM
	To: xproc-dev@w3.org
	Subject: Re: Difficulty overriding parameter values
	
	
	No, that doesn't seem to work.
	
	The main pipeline has a primary parameter input port:
	
	<p:declare-step ...[ns-declarations]... name="import">
	...
	      <p:input port="parameters" kind="parameter"/>
	...
	
	and so does the called step eb:rng-ebk:
	
	  <p:declare-step type="eb:rng-ebk">
	        <p:input port="source"/>
	        <p:input port="parameters" kind="parameter"/>
	        <p:output port="result"/>
	
	This works:
	
	          <eb:rng-ebk>
	            <p:input port="parameters">
	              <p:inline>
	                <c:param name="parent" value="book"/>
	              </p:inline>
	            </p:input>
	          </eb:rng-ebk>
	
	This doesn't:
	
	          <eb:rng-ebk>
	            <p:input port="parameters"/>
	            <p:with-param name="parent" select="'book'">
	              <p:empty/>
	            </p:with-param>
	          </eb:rng-ebk>
	
	Explicitly connecting the port to the import/parameters port
makes no difference, as expected.
	
	Is this a bug in Calabash, perhaps?
	
	Kevin