[Bug 6160] [FS] 7.1.1 The fs:convert-operand function: incorrect type rules


Tim Mills <tim@cbcl.co.uk> changed:

           What    |Removed                     |Added
                 CC|                            |tim@cbcl.co.uk

--- Comment #2 from Tim Mills <tim@cbcl.co.uk>  2008-10-24 10:28:15 ---
While we agree that the new rules you have proposed are correct,
recalling your comment from Bug 5915

"The new rules will probably change the static type of
    fs:convert-operand(data(()), 1)
to 'empty'"

they are not the most precise.

Under your new rules, I think

    fs:convert-operand(data(()), 1)

will come out as xs:double?, rather than the more precise type 'empty'.

statEnv |- none <: xs:untypedAtomic
statEnv |- xs:double <: fs:numeric
statEnv |- convert_operand none against xs:double is xs:double

statEnv |- empty <: xs:anyAtomicType?
statEnv |- xs:double<: xs:anyAtomicType
prime(empty) = none
statEnv |- convert_operand none against xs:double is AtomicTypeName1'
statEnv |- (FS-URI,"convert-operand")(empty, xs:double) :
               xs:double . quantifier(empty) = xs:dobule?

Configure bugmail: http://www.w3.org/Bugs/Public/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the QA contact for the bug.

Received on Friday, 24 October 2008 10:28:25 UTC