W3C home > Mailing lists > Public > public-xml-processing-model-comments@w3.org > February 2008

[closed] Re: Default bindings for non-primary inputs

From: Norman Walsh <ndw@nwalsh.com>
Date: Fri, 08 Feb 2008 12:48:30 -0500
To: public-xml-processing-model-comments@w3.org
Message-ID: <m21w7nbaq9.fsf@nwalsh.com>
/ Norman Walsh <ndw@nwalsh.com> was heard to say:
| This is legal:
|
|   <p:xslt>
|     <p:input port='stylesheet'>
|       <p:document href="someURI"/>
|     </p:input>
|   </p:xslt>
|
| The primary input 'source' will automatically be bound to the default
| readable port. The primary output 'result' will presumably get bound
| too.
|
| This is not legal:
|
| <p:xslt/>
|
| It's not legal because there's no binding for the 'stylesheet' input
| and the stylesheet input isn't a primary input.
|
| This is legal:
|
|   <p:xslt>
|     <p:input port='stylesheet'/>
|   </p:xslt>
|
| The stylesheet port is now named but no binding is provided. In this
| case, the port will automatically get bound to the default readable
| port.
|
| I think I used to think that providing default bindings for that last
| case was easy to understand. Now I'm not so sure.
|
| Would it be simpler to just say that non-primary inputs must always
| have explicit bindings?

Yes.

                                        Be seeing you,
                                          norm

-- 
Norman Walsh <ndw@nwalsh.com> | Everything should be made as simple as
http://nwalsh.com/            | possible, but no simpler.

Received on Friday, 8 February 2008 17:48:49 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Friday, 8 February 2008 17:48:49 GMT