This is an archived snapshot of W3C's public bugzilla bug tracker, decommissioned in April 2019. Please see the home page for more details.
In static typing implementations, declarations such as: declare variable $vA as xs:string := ("B STRING", current-time(), string(<e>cont ent</e>))[1]; may fail because under the FS typing rules, the RHS is typed as the union type ( xs:string | xs:time ). (:*******************************************************:) (: Test: K2-StringEqual-1 :) (: Written by: Frans Englich :) (: Date: 2007-01-15T15:15:44+01:00 :) (: Purpose: Compare two values returned from fn:lower-case(). :) (:*******************************************************:) declare variable $vA as xs:string := ("B STRING", current-time(), string(<e>cont ent</e>))[1]; declare variable $vB as xs:string := ("b string", current-time(), string(<e>cont ent</e>))[1]; (lower-case($vA) eq lower-case($vB))
K2-GenCompEq-1 to 6 fail in a similar way.
K2-compareFunc-4 to 9 have a similar problem.
K2-CodepointEqual-1 to 6 also have this problem.
... and K2-ContainsFunc-1 to 6
Not identical, but a similar problem in K2-SeqSubsequenceFunc-1 with: declare variable $start as xs:integer := (current-time(), 2)[2]; declare variable $len as xs:integer := (current-time(), 1)[2];
A fix has been attempted in CVS, and XQTS_current.zip has been updated to contain the new change. If it can be verified that the change is correct, it would be appreciated. If this resolution is satisfiable, feel free to change status to closed. Otherwise, reopen this report. If no opinion on the resolution is expressed within two weeks, I will change status to closed. This change to this report was part of a batch-change of several reports.
These are all now fixed. THanks.