- From: Henry S. Thompson <ht@inf.ed.ac.uk>
- Date: Tue, 17 Apr 2007 10:39:22 +0100
- To: Norman Walsh <Norman.Walsh@Sun.COM>
- Cc: public-xml-processing-model-wg@w3.org
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Norman Walsh writes: > Three test cases with > > <p:parameter name="foo" select="5"/> > <p:parameter name="bar" value="$foo+1"/> > > has solidified my believe that that having both @value and @select on > p:parameter and p:option is a recipe for user confusion. I guess we differ about co-constraints. The tableaux in the spec. [1] are pretty clear to me -- I don't see any confusion arising. Maybe I don't use XSLT enough :-). People will make one of the two mistakes above, get the obvious error message, and learn their lesson. After all, the constraints can be expressed in Relax-NG, so why are you worrying :-)? ht [1] http://www.w3.org/TR/xproc/#parameter-values - -- 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) iD8DBQFGJJXKkjnJixAXWBoRArTZAJ9GRc6ozfLBa3zb6l+nVWuB3Vj+gACcC/QI Vo/3DWVKIQVpK5R6GfI0Ixc= =hvdy -----END PGP SIGNATURE-----
Received on Tuesday, 17 April 2007 09:39:35 UTC