W3C home > Mailing lists > Public > public-qt-comments@w3.org > December 2009

[Bug 6951] [XSLT] Conflicting requirements for type annotations from XSLT validation='lax' and XDM

From: <bugzilla@wiggum.w3.org>
Date: Mon, 07 Dec 2009 15:50:09 +0000
To: public-qt-comments@w3.org
Message-Id: <E1NHfqj-0000Qe-Nc@wiggum.w3.org>
http://www.w3.org/Bugs/Public/show_bug.cgi?id=6951





--- Comment #2 from Michael Kay <mike@saxonica.com>  2009-12-07 15:50:09 ---
Following email discussion and discussion at the telcon on 2009-11-17, there
was agreement in principle that when lax validation "succeeds", the resulting
document should always be annotated as xs:anyType rather than xs:untyped
regardless whether any elements were found that could actually be validated:
this ensures that the process can be streamed, and it means that the accidental
presence of an insignificant declaration in the schema (for example a
declaration for the xml:lang attribute) does not switch the whole document from
xs:untyped to xs:anyType.

I was actioned to propose wording changes to implement this decision. I believe
it can be effected by changing the third bullet in XDM section 3.3.1.1 from

<old>The [validity] property exists and is "notKnown", and the [validation
attempted] property exists and is "none", the schema type of an element is
xs:untyped and the type of an attribute is xs:untypedAtomic.</old>

to

<new>The [validity] property exists and is "notKnown", the schema type of an
element is xs:anyType and the type of an attribute is xs:anyAtomicType.</new>


-- 
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 Monday, 7 December 2009 15:50:18 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Tuesday, 27 March 2012 18:14:58 GMT