W3C home > Mailing lists > Public > public-qt-comments@w3.org > May 2012

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

From: <bugzilla@jessica.w3.org>
Date: Wed, 16 May 2012 20:39:36 +0000
To: public-qt-comments@w3.org
Message-Id: <E1SUl0S-0001ID-2e@jessica.w3.org>
https://www.w3.org/Bugs/Public/show_bug.cgi?id=14734

Michael Kay <mike@saxonica.com> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|NEW                         |RESOLVED
         Resolution|                            |WONTFIX

--- Comment #5 from Michael Kay <mike@saxonica.com> 2012-05-16 20:39:35 UTC ---
There has been considerable discussion on this issue both here and in the XSL
WG mailing list. The consensus seems to be that there is nothing we can do
given XSD as it exists today. A good point was made by Michael Sperberg McQueen
to the effect that literal result elements in a stylesheet are a form of tag
abuse: the content model for a <para> element in a stylesheet is not the same
as for a <para> element in a normal document, and therefore it is to be
expected that when the schema used for validating stylesheets includes the
declaration of a <para> element as in appears in a normal document, validation
should fail. Nevertheless, lax seems a better option than skip, because it
causes validation to recurse through the literal result element to inner XSLT
instructions.

I'm therefore closing this (unilaterally, but taking the consensus reached by
extensive discussion into account) as WONTFIX.

-- 
Configure bugmail: https://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, 16 May 2012 20:39:39 UTC

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