- From: <bugzilla@jessica.w3.org>
- Date: Sat, 13 Sep 2014 13:39:59 +0000
- To: public-qt-comments@w3.org
https://www.w3.org/Bugs/Public/show_bug.cgi?id=26780 Abel Braaksma <abel.braaksma@xs4all.nl> changed: What |Removed |Added ---------------------------------------------------------------------------- Summary|[XSLT30] Forwards |[XSLT30] Editorial: |compatibility mode and |forwards compatibility mode |packages, after |and packages |xsl:stylesheet became | |obsolete as a child | --- Comment #1 from Abel Braaksma <abel.braaksma@xs4all.nl> --- As discussed by mail (see https://lists.w3.org/Archives/Member/w3c-xsl-wg/2014Sep/0030.html and previous, member only), the conclusion was: - I misinterpreted the spec, the "SHOULD" does not preclude forwards/backwards compatibility mode on package manifests - The suggestion in the mail by MKay was to change the sentence as follows, which prompted me to mark this bug as Editorial. Textual proposal from MKay: > "For this version of XSLT, the value SHOULD normally be 3.0. Specifying a > different value invokes backwards-compatible processing (see 3.10), or > forwards-compatible processing (see 3.11)." Marked EDITORIAL. -- You are receiving this mail because: You are the QA Contact for the bug.
Received on Saturday, 13 September 2014 13:40:00 UTC