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 30080 - analyzeString-029 assertions assume analyze-string returns untyped values
Summary: analyzeString-029 assertions assume analyze-string returns untyped values
Status: RESOLVED INVALID
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-24 17:13 UTC by Josh Spiegel
Modified: 2017-03-24 17:57 UTC (History)
1 user (show)

See Also:

Attachments

Description Josh Spiegel 2017-03-24 17:13:47 UTC 
Some of the test assertions assume the result of analyze-string is untyped.  For example:

<assert>$result/out/fn:analyze-string-result[1]/fn:match[1]/fn:group[@nr=4] = 'Sample test/some other keys/'</assert>

Atomization of the result of the path expression may raise an error.  i.e. it is a complex type with element only content (FOTY0012)


I propose to update the assertions as follows:

<assert>string($result/out/fn:analyze-string-result[1]/fn:match[1]/fn:group[@nr=4]) = 'Sample test/some other keys/'</assert>

Which should work in both cases.
Comment 1 Michael Kay 2017-03-24 17:30:46 UTC 
The fn:group element (and all the others) have mixed="true" in the type definition, so atomization should not fail. I don't think this change is necessary.
Comment 2 Josh Spiegel 2017-03-24 17:57:36 UTC 
Yes, you're right, thanks.  Closing as invalid.