This is an archived snapshot of W3C's public bugzilla bug tracker, decommissioned in April 2019. Please see the home page for more details.
K2-SeqExprCast-207 is "Construct an xs:anyURI from an invalid string." However, F&O 17.1.1 Casting from xs:string and xs:untypedAtomic is clear that: For xs:anyURI, the extent to which an implementation validates the lexical form of xs:anyURI is ·implementation dependent·. It is also worth noting that in Schema 1.1 last call: "The ·lexical space· of anyURI is finite-length character sequences." This is probably because (as previously discussed) the specification of the anyURI datatype in Scheme 1.0 was ambiguous, being a weird union of URIs after escaping and URIs before escaping, which means you can't really ascribe any meaning to them at all.
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.
This is another of the issues of when and how to canonicalize. K2-SeqExprCast-207.txt contains: http:\\invalid>URI\someURI but the canonical result is: http:\\invalid>URI\someURI Not the XQTS specificaton does say the it is my responsibility to canonicale the expected output, and I can handle this issue too. But if you don't mind changing K2-SeqExprCast-207.txt that would be reasonable too.
">" should be escaped in CVS now.
You have mave accidentally reverted something. K2-SeqExprCast-207.txt is gone, and the entry in the XQTSCatalog (dated 2007-01-22+01:00) no longer ocntains an output-file element.
Per, Hopefully this is fixed in CVS. Frans