- From: Norman Walsh <ndw@nwalsh.com>
- Date: Sun, 22 Apr 2007 12:20:22 -0400
- To: public-xml-processing-model-wg@w3.org
- Message-ID: <87d51w4bzt.fsf@nwalsh.com>
/ Innovimax SARL <innovimax@gmail.com> was heard to say: |> Assuming the following pipe is loaded from a library: |> |> <p:pipeline name="ex:myPipe"> |> <p:input port="source"> |> <p:inline> |> <foo/> |> </p:inline> |> </p:input> |> <p:output port="result"/> |> <p:identity/> |> </p:pipeline> |> |> What is the output from this pipeline? |> |> <ex:myPipe> |> <p:input port="source"> |> <p:inline> |> <bar/> |> </p:inline> |> </p:input> |> </ex:myPipe> | | The output is <bar/>, because this use case, is the "default input" one. | This is a very useful use case, for auxiliary inputs which could be | "overloaded" by the user Yes, I think that should be the answer too. Be seeing you, norm -- Norman Walsh <ndw@nwalsh.com> | It is good to have an end to journey http://nwalsh.com/ | toward; but it is the journey that | matters, in the end.--Ursula K. LeGuin
Received on Sunday, 22 April 2007 16:20:30 UTC