Re: unbound option bug in Calabash, I think

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

Toman_Vojtech writes:

>> Should this pipeline run w/o error?
>> 
>>    <p:pipeline xmlns:p="http://www.w3.org/ns/xproc">
>>     <p:option name="notBound"/>
>>     <p:identity/>
>>    </p:pipeline>
>
> I think so. The option is not required and not used, I think there is no
> problem.

I agree.  We discussed this ages ago -- it is perfectly reasonable for
an engine to provide means for (extension) steps to detect the absence
of non-defaulted optional options, indeed since we allow non-defaulted
optional options, it follows that engines which support extension
steps _must_ provide such a means.

If we weren't in CR, I would argue that this applies to steps defined
with p:declare-step, so we should (have) provided an XPath extension
function p:isBound or p:unbound or whatever. . .

ht
- -- 
       Henry S. Thompson, School of Informatics, University of Edinburgh
                         Half-time member of W3C Team
      10 Crichton Street, Edinburgh EH8 9AB, SCOTLAND -- (44) 131 650-4440
                Fax: (44) 131 651-1426, 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)

iD8DBQFKDUFZkjnJixAXWBoRAl7aAJ9Q78VcUeMiiu3vPjcI1oUk8KRrPQCeJnly
2EKtRYc9mOYwnv61JLH0tJg=
=zqxY
-----END PGP SIGNATURE-----

Received on Friday, 15 May 2009 10:18:38 UTC