Default bindings for non-primary inputs

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?

                                        Be seeing you,
                                          norm

-- 
Norman Walsh <ndw@nwalsh.com> | A complex system that works is
http://nwalsh.com/            | invariably found to have evolved from a
                              | simple system that worked.--J. Gall