Re: Type errors with xsd:boolean arguments

On Mon, Sep 19, 2005 at 01:51:39PM +0100, Dave Beckett wrote:
> 
> There seems to be a clash between:
>   "Functions invoked with an argument of the wrong type will produce a
>   type error." (11.2)
> vs
>   "When a operand is coerced to xs:boolean through invoking a function
>   that takes a xs:boolean argument, the following rules apply: ..."
>   (11.2.2)
> 
> which seems to imply that an arguments to a function that are of type
> xsd:boolean are always co-erced and never produce a type error?

I believe that is true. The ebv rules will give a boolean from any
arguments. 

> If that's the case, I suggest changing 11.2 something like:
>   Functions invoked with an argument of the wrong type (except
>   xsd:boolean) will produce a type error.
>   Functions requiring an argument of type xs:boolean are coerced to
>   xs:boolean using the EBV rules in section 11.2.2

Done (1.503)

> (Maybe there should be a new sub-section called "Type Errors"?)
> 
> Dave
> 
-- 
-eric

office: +81.466.49.1170 W3C, Keio Research Institute at SFC,
                        Shonan Fujisawa Campus, Keio University,
                        5322 Endo, Fujisawa, Kanagawa 252-8520
                        JAPAN
        +1.617.258.5741 NE43-344, MIT, Cambridge, MA 02144 USA
cell:   +81.90.6533.3882

(eric@w3.org)
Feel free to forward this message to any list for any purpose other than
email address distribution.