Re: p:xslt

2008/12/12 Norman Walsh <ndw@nwalsh.com>:

> So, one of the following must be true:
>
> 1. You declared a parameter input port on your top-level pipeline.
>
> 2. You used p:pipeline to declare your top-level pipeline (this
>   satisfies point 1 by default)
>
> 3. You provided an explicit binding for the 'parameter' input port on
>   your p:xslt step.

I'll try a write up on this, adding to dpawson.co.uk/xproc/connections.html
I'd appreciate a review from anyone who understands this.



>> Ah. Thanks.
>> OK. 5.1.2
>> If no binding is provided for a parameter input port other than the
>> primary parameter input port, then the port will be bound to an empty
>> sequence of documents.
>>
>> Does that say the same as what you've just said?
>> Note the 'other than the primary' bit?
>
> Ok, the situation is actually a wee bit more complex. I was just
> trying to keep things simple(er).
>
> A step could define more than one parameter input port (though now
> standard steps do). In that case, the defaulting rules for the primary
> parameter input port (if there is one) and the non-primary ones are a
> little different. The primary one gets bound back to the pipeline
> parameters; the non-primary ones just get empty sequences.

Thanks. Another gem!



> In Calabash, if you pass a binding for that port on the command line,
> that's what it gets bound to. If you pass parameters on the command
> line, Calabash manufactures a c:parameter-set with those parameters
> and that's what it gets bound to. If you do neither of those, it gets
> bound to an empty sequence.

c: being a calabash extension ?
<grin> That you're going to document? I saw the blog entry
about parameter sets</




Thanks Norm.

-- 
Dave Pawson
XSLT XSL-FO FAQ.
Docbook FAQ.
http://www.dpawson.co.uk

Received on Friday, 12 December 2008 15:20:22 UTC