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

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

From: <bugzilla@jessica.w3.org>
Date: Tue, 08 Nov 2011 21:35:27 +0000
To: public-qt-comments@w3.org
Message-ID: <bug-14734-523@http.www.w3.org/Bugs/Public/>
http://www.w3.org/Bugs/Public/show_bug.cgi?id=14734

           Summary: [XSLT 2.0] Literal result elements should not be laxly
                    validated
           Product: XPath / XQuery / XSLT
           Version: Recommendation
          Platform: PC
        OS/Version: All
            Status: NEW
          Severity: normal
          Priority: P2
         Component: XSLT 2.0
        AssignedTo: mike@saxonica.com
        ReportedBy: mike@saxonica.com
         QAContact: public-qt-comments@w3.org


In the XSLT 2.0 schema for stylesheets, literal result elements are validated
against a wildcard with processContents="lax". Consider this scenario:

<xsl:template match="/*">
  <book>
    <xsl:if test="@isbn">
      <xsl:attribute name="color" select="'green'"/>
    </xsl:if>
  </book>
</xsl:template>

If there is a global element declaration for 'book', it is very likely that it
will not permit an xsl:if element as a child. Performing lax validation of the
book element would therefore report a validity error. I believe therefore that
literal result elements should be processed using a processContents="skip"
wildcard.

(Discovered as a consequence of research into a separate question raised
off-list by Norm Walsh)

-- 
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 Tuesday, 8 November 2011 21:35:29 UTC

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