Re: Use Case 5.27: Integrate Computation Components (MathML)

On 7/10/06, Alex Milowski <alex@milowski.org> wrote:
> Here is a version without the use of the pipe element.

Alex,

I like most of what I see in your syntax. One thing related to the
name of the outputs gets me confused though:

My assumption is each component declares what input(s) it expects and
what output(s) it generates. The component also assigns a name to each
input/output. So when we use a component in a step, I expect to see in
the <p:input> and <p:output> the names declared by the component.

If we have a component p:xslt that has 2 inputs (input and stylesheet)
and 1 output (transformed), I expect that a step using this component
would look like:

<p:step kind="p:xslt">
    <p:input name="input" from="decomposition-computed"/>
    <p:input name="stylesheet">in-line stylesheet</p:input>
    <p:output name="transformed" label="gap-formulate-request"/>
</p:step>

Instead in your code I see:

<p:step kind="p:xslt">
    <p:input name="input" from="decomposition-computed"/>
    <p:input name="stylesheet">in-line stylesheet</p:input>
    <p:output name="gap-formulate-request"/>
</p:step>

This seems to indicate that the pipeline author uses the "name"
attribute on <p:output> to give a label or ID to that output. This
label/ID in the name="..." attribute can be later referenced with
from="...". If my understanding is correct, I have 2 questions:

1) How do we deal with components that have multiple outputs?
2) In a step, the names are defined by the component and but the
output names are chosen by the pipeline author. Doesn't this create an
inconsistency?

Best,

Alex
-- 
Blog (XML, Web apps, Open Source):
http://www.orbeon.com/blog/

Received on Thursday, 13 July 2006 00:18:17 UTC