W3C home > Mailing lists > Public > public-qt-comments@w3.org > April 2005

[Bug 1230] New: Rules for forwards-compatibility mode

From: <bugzilla@wiggum.w3.org>
Date: Fri, 08 Apr 2005 16:04:07 +0000
To: public-qt-comments@w3.org
Message-Id: <E1DJvxn-00014g-LA@wiggum.w3.org>


           Summary: Rules for forwards-compatibility mode
           Product: XPath / XQuery / XSLT
           Version: Last Call drafts
          Platform: PC
        OS/Version: Windows XP
            Status: NEW
          Severity: normal
          Priority: P2
         Component: XSLT 2.0
        AssignedTo: mike@saxonica.com
        ReportedBy: mike@saxonica.com
         QAContact: public-qt-comments@w3.org

There's an inconsistency in the rules for forwards-compatibility mode (section
3.9). It says:

Within a section of a stylesheet where forwards-compatible behavior is enabled,
errors that would normally be static errors are treated instead as dynamic
errors. This means that no error is signaled unless the construct containing the
error is actually evaluated.

This includes, but is not limited to, the following situations:

and then, inter alia:

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

The first statement would suggest that if the instruction <xsl:copy
copy-namespaces="not-on-your-nelly"/> is actually executed, it should be treated
as a dynamic error.

The second statement suggests that this instruction should be evaluated as if it
were <xsl:copy/>. (This was the XSLT 1.0 rule, and I believe is the correct one.)
Received on Friday, 8 April 2005 16:04:08 UTC

This archive was generated by hypermail 2.3.1 : Wednesday, 7 January 2015 15:45:23 UTC