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 30077 - Results for xml-to-json-065 and -066 need updating to reflect bug #29917
Summary: Results for xml-to-json-065 and -066 need updating to reflect bug #29917
Status: RESOLVED FIXED
Alias: None
Product: XPath / XQuery / XSLT
Classification: Unclassified
Component: XQuery 3 & XPath 3 Test Suite (show other bugs)
Version: Candidate Recommendation
Hardware: PC All
: P2 normal
Target Milestone: ---
Assignee: O'Neil Delpratt
QA Contact: Mailing list for public feedback on specs from XSL and XML Query WGs
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2017-03-19 19:30 UTC by Michael Kay
Modified: 2017-04-05 09:54 UTC (History)
1 user (show)

See Also:

Attachments

Description Michael Kay 2017-03-19 19:30:37 UTC 
Bug #29917 allows the outermost element of a tree supplied to fn:xml-to-json to have an escaped or escaped-key attribute (which is ignored).

This means that test cases xml-to-json-065 and -066 are no longer error cases.
Comment 1 Josh Spiegel 2017-03-20 13:47:55 UTC 
I think you mean 064 and 065?
Comment 2 Michael Kay 2017-03-20 15:37:47 UTC 
Yes, sorry, -064 and -065.
Comment 3 Michael Kay 2017-04-05 09:43:13 UTC 
Test case -065 reveals a minor issue with the spec. The schema does not allow a `<map>` element to have an `escaped` attribute. However, the rules are written to say that the input must either

1. conform to the schema, or

2. conform to the schema after removing any `escaped` or `escaped-key` attribute at the top level.

So although it doesn't make much sense, the spec seems unambiguous that this test case is allowed.
Comment 4 Michael Kay 2017-04-05 09:54:25 UTC 
The same problem applies to test case xml-to-json-C-016.

All three tests have been changed to expect success results.