Re: Context for p:option

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Norman Walsh writes:

> For p:input (and its friends: p:iteration-source, etc.) if there's
> no explicit binding, the binding is made to the default readable port.
> Jeni pointed out, I think correctly, that users will expect a select
> expression on p:option to also be bound to the default readable port
> by default.
>
> Anyone disagree?

Not strongly, but I think what people will _really_ expect is that it
will be bound to the primary input of the step by default.  As long as
that input defaults, this makes no difference, but I think users will
be surprised if they write

 <p:pipeline name="top">
  <p:input port="stylesheet"/>
  . . .
  <p:customize>
   <p:input port="primary">
    <p:pipe step="top" port="stylesheet"/>
   </p:input>
   <p:option name="version" select="/xsl:stylesheet/@version"/>
   . . .

and it doesn't work.

Unfortunately, we still don't have a notion of primary input, do we?

ht
- -- 
 Henry S. Thompson, HCRC Language Technology Group, University of Edinburgh
                     Half-time member of W3C Team
    2 Buccleuch Place, Edinburgh EH8 9LW, SCOTLAND -- (44) 131 650-4440
            Fax: (44) 131 650-4587, e-mail: ht@inf.ed.ac.uk
                   URL: http://www.ltg.ed.ac.uk/~ht/
[mail really from me _always_ has this .sig -- mail without it is forged spam]
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.6 (GNU/Linux)

iD8DBQFGZoaOkjnJixAXWBoRArXwAJ9zqFaAbHftig85nMRpMHhMeVkRKgCfYxue
R9vbpsnxG+g1EIaMcEGm+H8=
=7DJP
-----END PGP SIGNATURE-----

Received on Wednesday, 6 June 2007 10:04:10 UTC