- From: <bugzilla@jessica.w3.org>
- Date: Thu, 13 Jun 2013 13:25:28 +0000
- To: public-qt-comments@w3.org
https://www.w3.org/Bugs/Public/show_bug.cgi?id=21960 --- Comment #6 from Michael Kay <mike@saxonica.com> --- This test seems to have a long and unhappy history (see also bugs 11584 and 6988). There seem to be two separate issues. The first issue is that a processor that does dynamic type checking isn't obliged to raise any error because the global variable is never evaluated. To remove that problem, I propose to change the test to: declare variable $v as element(*, xs:untyped?)+ := <e/>; exists($v/*) The second issue is whether a processor is allowed to make the element untyped rather than anyType. This is the subject of bugs 11585 and 20828. I believe the outcome of these bugs is that if a processor does not support the typed data feature, then the constructed element will be untyped. I am therefore proposing to split the test into two, with dependencies to require the typed data feature to be on or off, and results false or error respectively. -- You are receiving this mail because: You are the QA Contact for the bug.
Received on Thursday, 13 June 2013 13:25:36 UTC