Re: p:input vs. p:parameter-input

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

Norman Walsh writes:

> / ht@inf.ed.ac.uk (Henry S. Thompson) was heard to say:
> | . . .
> | I can live with all this -- I note that the combination of the last
> | two means in practice that 'parameters' is not allowed on the "call"
> | to a step.
>
> I don't follow. If the step being called has a parameter input, then
> they can use it, they simply use p:input to do so.

What I mean is that the following is not allowed:

 <p:xslt>
  <p:input port="parameters" parameters="yes">
   . . .
  </p:input>
  . . .

[yes, we could allow that, but not "parameters='no'", but that would
just be silly, I think.  Both RelaxNG and XSDL can express the
necessary context-dependent constraint.]

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)

iD8DBQFGenQlkjnJixAXWBoRAqZcAJ9eKpTJabLS50f1XfhF82I9Sho4cACdFFUu
HepGmWw4AYjjyUQiYzz5BGM=
=zWUQ
-----END PGP SIGNATURE-----

Received on Thursday, 21 June 2007 12:50:49 UTC