W3C home > Mailing lists > Public > public-qt-comments@w3.org > March 2017

[Bug 30080] New: analyzeString-029 assertions assume analyze-string returns untyped values

From: <bugzilla@jessica.w3.org>
Date: Fri, 24 Mar 2017 17:13:47 +0000
To: public-qt-comments@w3.org
Message-ID: <bug-30080-523@http.www.w3.org/Bugs/Public/>
https://www.w3.org/Bugs/Public/show_bug.cgi?id=30080

            Bug ID: 30080
           Summary: analyzeString-029 assertions assume analyze-string
                    returns untyped values
           Product: XPath / XQuery / XSLT
           Version: Candidate Recommendation
          Hardware: PC
                OS: All
            Status: NEW
          Severity: normal
          Priority: P2
         Component: XQuery 3 & XPath 3 Test Suite
          Assignee: oneil@saxonica.com
          Reporter: josh.spiegel@oracle.com
        QA Contact: public-qt-comments@w3.org
  Target Milestone: ---

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.

-- 
You are receiving this mail because:
You are the QA Contact for the bug.
Received on Friday, 24 March 2017 17:13:57 UTC

This archive was generated by hypermail 2.3.1 : Friday, 24 March 2017 17:13:57 UTC