This is an archived snapshot of W3C's public bugzilla bug tracker, decommissioned in April 2019. Please see the home page for more details.

Bug 28946 - [FO3.1] json-to-xml with unescape=false,fallback=f
Summary: [FO3.1] json-to-xml with unescape=false,fallback=f
Status: CLOSED FIXED
Alias: None
Product: XPath / XQuery / XSLT
Classification: Unclassified
Component: Functions and Operators 3.1 (show other bugs)
Version: Last Call drafts
Hardware: PC All
: P2 normal
Target Milestone: ---
Assignee: Michael Kay
QA Contact: Mailing list for public feedback on specs from XSL and XML Query WGs
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2015-07-13 20:45 UTC by Michael Kay
Modified: 2016-12-16 19:55 UTC (History)
1 user (show)

See Also:

Attachments

Description Michael Kay 2015-07-13 20:45:18 UTC 
I think test case json-to-xml-027 raises a question about the spec: if there's an invalid escape sequence like \uDEAD, and unescape=false, is the processor still expected to detect that it's invalid and call the fallback function, or should it just copy \uDEAD blindly to the XML result?

I would think the latter.
Comment 1 Jonathan Robie 2015-07-15 19:16:15 UTC 
The Working Group agrees that it should just copy \uDEAD blindly to the XML result.  An error is raised if a fallback function is provided in this case.
Comment 2 Michael Kay 2015-07-16 01:34:15 UTC 
The change has been applied to the spec, and the test case has been changed to expect an error.