Re: effect of p:compare

/ "Innovimax SARL" <innovimax@gmail.com> was heard to say:
| p:compare is one of those step which has no primary output port
|
| In 2.5 Environment,
|
| [[
| If there is a preceding sibling step element:
|
|    -
|
|    If that preceding sibling has a *primary output
| port<http://www.w3.org/XML/XProc/docs/langspec.html#dt-primary-output-port>
|    *, then that output port becomes the *default readable
| port<http://www.w3.org/XML/XProc/docs/langspec.html#dt-default-readable-port>
|    *.
|    -
|
|    Otherwise, the *default readable
| port<http://www.w3.org/XML/XProc/docs/langspec.html#dt-default-readable-port>
|    * is undefined.
|
| ]]
|
| does it mean that
|
| <p:identity/>
| <p:compare/>
| <p:identity/>
|
| 1) will throw an error on the second p:identity, because the default
| readable port is undefined

Yes.

| 2) will use the last defined "default readable port", which is the result of
| the first identity

No. After a p:compare (or p:parameters, I think), you must make the next
binding explicit.

                                        Be seeing you,
                                          norm

-- 
Norman Walsh <ndw@nwalsh.com> | Internet connection, $19.95 a month.
http://nwalsh.com/            | Computer, $799.95. Modem, $149.95.
                              | Telephone line, $24.95 a month.
                              | Software, free. USENET transmission,
                              | hundreds if not thousands of dollars.
                              | Thinking before posting, priceless.
                              | Somethings in life you can't buy. For
                              | everything else, there's
                              | MasterCard.--Graham Reed, in the Scary
                              | Devil Monastery