Joint WG decisions affecting XSLT 3.0

ACTION 2016-09-29-001 Mike Kay will extract the relevant parts of the
minutes of the joint telcon for the changes for UCA collations.
and post to the mailing list.

Two decisions made on 27 Sept affect the XSLT spec:

(a) Bug 29872: brings parse-json() and json-to-xml() into line by making clear that when escape=true() is set in the options, existing escape sequences in the input are retained. For example if "%" is unnecessarily escaped in the input as \u0025, then it ends up in the output as \u0025. Previously parse-json() was specified this way but json-to-xml() left the question open.

In applying this change I noticed that a previously-agreed change, to change the option unescape=false() to escape=true(), had been applied in the F+O 3.1 spec but not in the XSLT 3.0 spec.

(b) Bug 29865: adds the option maxVariable=space|punct|symbol|currency to the options available in a UCA collation URI. This option (which like everything else in UCA collation URIs uses the terminology of UCA and LDML) controls which characters (such as spaces and punctuation) are treated as insignificant (or less significant) for collation purposes. I'm not sure why it was omitted before, but there have been changes to the UCA and LDML specs in this area and I suspect that when we did the work previously, UCA and LDML were not in sync with each other so we just left it out.

The relevant minutes are at

https://lists.w3.org/Archives/Public/public-xsl-query/2016Sep/0033.html

Michael Kay
Saxonica

Received on Friday, 30 September 2016 09:37:37 UTC