W3C home > Mailing lists > Public > public-qt-comments@w3.org > November 2011

[Bug 14734] [XSLT 2.0] Literal result elements should not be laxly validated

From: <bugzilla@jessica.w3.org>
Date: Wed, 09 Nov 2011 11:24:26 +0000
To: public-qt-comments@w3.org
Message-Id: <E1RO6GY-00082S-O3@jessica.w3.org>
http://www.w3.org/Bugs/Public/show_bug.cgi?id=14734

--- Comment #1 from Michael Kay <mike@saxonica.com> 2011-11-09 11:24:26 UTC ---
Of course, using processContents="skip" would have the disadvantage that the
xsl:if element (and any other descendants of the LRE) would not be validated.
What we really need is a different processContents value that says "skip
elements that match the wildcard but process their children as follows: use
strict validation if they are in namespace XSLT but recurse otherwise". Not
expressible, of course. Interestingly, it's the inverse of the problem we had
in XSD of defining validation for xs:documentation sections where we want to
validate any XHTML content but not validate any XSD content.

-- 
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 Wednesday, 9 November 2011 11:24:32 UTC

This archive was generated by hypermail 2.4.0 : Friday, 17 January 2020 16:57:36 UTC