- From: <bugzilla@jessica.w3.org>
- Date: Tue, 11 Jun 2013 09:26:46 +0000
- To: public-qt-comments@w3.org
https://www.w3.org/Bugs/Public/show_bug.cgi?id=21960
Tim Mills <tim@cbcl.co.uk> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|RESOLVED |REOPENED
CC| |tim@cbcl.co.uk
Resolution|FIXED |---
--- Comment #3 from Tim Mills <tim@cbcl.co.uk> ---
We do not report an error on this test case for the following reason.
<e /> is of type element(e, xs:anyType)
The declared type of $v is
element(*, xs:untyped?)+
Purely on use of the type information available, there exist values which match
element(e, xs:anyType) and element(*, xs:untyped?)+. Therefore this is
postponed to a runtime (dynamic) check.
Since $v is never evaluated, this dynamic type check is never invoked, and
therefore the dynamic error is never raised. Thus the processor is entitled to
return 1.
Generally, given a variable $v which is never evaluated, since a processor may
implement dynamic type checking, any type check errors in the definition of $v
may be legitimately ignored.
--
You are receiving this mail because:
You are the QA Contact for the bug.
Received on Tuesday, 11 June 2013 09:26:47 UTC