W3C home > Mailing lists > Public > public-qt-comments@w3.org > September 2010

[Bug 7355] [XSLT 2.0] Precise definition of region for which forwards compatibility applies

From: <bugzilla@jessica.w3.org>
Date: Thu, 30 Sep 2010 17:02:53 +0000
To: public-qt-comments@w3.org
Message-Id: <E1P1MWz-0000K1-2Z@jessica.w3.org>
http://www.w3.org/Bugs/Public/show_bug.cgi?id=7355

Henry Zongaro <zongaro@ca.ibm.com> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|ASSIGNED                    |RESOLVED
         Resolution|                            |FIXED

--- Comment #3 from Henry Zongaro <zongaro@ca.ibm.com> 2010-09-30 17:02:52 UTC ---
Draft erratum was issued, replacing seventh paragraph of section 3.9 with the
following:

If forwards-compatible behavior is enabled for an element, then:

* if the element is in the XSLT namespace and appears as a child of the
xsl:stylesheet element, and XSLT 2.0 does not allow such elements to occur as
children of the xsl:stylesheet element, then the element and its content must
be ignored.

* if the element has an attribute that XSLT 2.0 does not allow the element to
have, then the attribute must be ignored.

* if the element is in the XSLT namespace and appears a child of an element
whose content model requires a sequence constructor, and XSLT 2.0 does not
allow such elements to appear as part of a sequence constructor, then:

   1. If the element has one or more xsl:fallback children, then no error is
reported either statically or dynamically, and the result of evaluating the
instruction is the concatenation of the sequences formed by evaluating the
sequence constructors within its xsl:fallback children, in document order.
Siblings of the xsl:fallback elements are ignored, even if they are valid XSLT
2.0 instructions.
   2.  If the element has no xsl:fallback children, then a static error is
reported in the same way as if forwards-compatible behavior were not enabled.


I am satisfied that this resolves the problem.

-- 
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 Thursday, 30 September 2010 17:02:54 GMT

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