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 22792 - Incorrect spec Dependency on test cbcl-matches-006b
Summary: Incorrect spec Dependency on test cbcl-matches-006b
Status: RESOLVED FIXED
Alias: None
Product: XPath / XQuery / XSLT
Classification: Unclassified
Component: XQuery 3 & XPath 3 Test Suite (show other bugs)
Version: Working drafts
Hardware: PC Linux
: 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: 2013-07-24 10:03 UTC by O'Neil Delpratt
Modified: 2015-01-03 10:41 UTC (History)
1 user (show)

See Also:

Attachments

Description O'Neil Delpratt 2013-07-24 10:03:04 UTC 
For the test-case cbcl-matches-006b, which is given below:

 <test-case name="cbcl-matches-006b">
      <description> test with a character class containing an escaped character </description>
      <created by="Tim Mills" on="2008-07-17"/>
      <dependency type="spec" value="XP10+"/>
      <test>fn:matches('&#x9;', '[\t]')</test>
      <result>
         <assert-true/>
      </result>
   </test-case>

 it has dependency on the spec 'XP10+' however fn:matches is only applicable to 'XP20+', therefore this is incorrect. If there are no objections I will make the change to the dependency.
Comment 1 O'Neil Delpratt 2013-07-24 10:23:00 UTC 
spec dependency updated to XP20+
Comment 2 O'Neil Delpratt 2013-07-24 11:50:21 UTC 
The same XP10+ spec dependency appears in the following test case:

cbcl-matches-041b
cbcl-matches-047b
cbcl-cast-nmtoken-001b
cbcl-cast-normalizedString-001b
cbcl-cast-token-001b
cbcl-castable-nmtoken-002b
cbcl-normalizedstring-002b
cbcl-token-002b

Fix applied to CVS. But did not make it in QT3 1.0 version

Another problem discovered is the counts of test reported in the report stylesheet is incorrect in a couple of places because of this XP10 spec dependency. I am making progress to fix this. Just to make it clear the QT3 documentation does not mention anything about XP10.
Comment 3 Michael Kay 2013-07-24 11:56:56 UTC 
It might be a good idea to add a test in the CatalogCheck test set to ensure that the value of the dependency field is valid.
Comment 4 Michael Kay 2015-01-03 10:41:21 UTC 
I have added a test CatalogCheck013 as suggested in comment #3 and I believe the bug can now be closed.