M Changes since the Proposed Recommendation of 18 April 2017 (Non-Normative)

This section contains a list of changes that have been made. Trivial typographic errors and changes to non-normative front and back matter are not listed.

  1. Bug30089: A non-normative note in 2.3.6.1 wrongly stated that serializing an array would raise an error. The serialization specification is clear that this is not the case.

  2. Bug30090: A non-normative note in 3.2 referred to the "four standard serialization methods". With the 3.1 version of the serialization specification, there are now six standard methods.

  3. Bug30091: A non-normative note in 3.5.4 advised users to solve a particular problem by using the instruction <xsl:apply-templates/>. Better advice would be to use <xsl:apply-templates select="."/>

  4. Bug30093: An example in 5.5.1 Examples of Patterns (carried over unchanged from the XSLT 2.0 specification) gave incorrect semantics for the pattern //para.

  5. Bug30094: In 9.1 Variables the term local variable is used. The definition of this term appears in 9.8 Local Variables and Parameters. But rather than linking to the definition, the former section gave an incomplete explanation of its meaning.

  6. Bug30095: In 9.9 Scope of Variables, the scope of global variables was described without making clear that the discussion was in the context of a single package; a note has been added explaining that the rules for cross-package visibility are defined elsewhere.

  7. Bug30099: In the proforma for the start-at attribute of xsl:number (appearing in both section 12 and Appendix D), the type of the attribute was given as integer although the normative description of the syntax and semantics of the attribute makes clear that a whitespace-separated sequence of integers is permitted. (For technical reasons this change is not color-highlighted.)

  8. Bug30100: A non-normative note in section 27.4 referred to version "3.0", in a context that made no sense unless this is read as version "2.0".

  9. Bug30109: A non-normative note has been added to explain that as a consequence of the general rules for constructing simple content, the disable-output-escaping attribute has no effect when writing attributes, comments or processing instructions.