- From: <bugzilla@jessica.w3.org>
- Date: Thu, 12 May 2016 10:32:18 +0000
- To: public-qt-comments@w3.org
https://www.w3.org/Bugs/Public/show_bug.cgi?id=29602 --- Comment #2 from Michael Kay <mike@saxonica.com> --- The problem with the xml-to-json stylesheets can be solved, I think, by changing text in para 2 of 22.4. Instead of "is functionally identical to the xml-to-json function described in the previous section" we should say "has largely similar behavior to the xml-to-json function described in the previous section. (It should not be regarded as a conformant implementation of that function: for example, it does not perform complete validation of the input, and it does not follow the escaping rules precisely.)" The problem with the option parameter conventions is trickier. Reproducing the OPCs in the XSLT 3.0 spec is overkill and increases the risk of inconsistencies creeping in. I do think we should bite the bullet and reference F+O 3.1 normatively. -- You are receiving this mail because: You are the QA Contact for the bug.
Received on Thursday, 12 May 2016 10:32:20 UTC