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 29707 - [QT3] EQName tests for XPath and corner cases
Summary: [QT3] EQName tests for XPath and corner cases
Status: CLOSED FIXED
Alias: None
Product: XPath / XQuery / XSLT
Classification: Unclassified
Component: XQuery 3 & XPath 3 Test Suite (show other bugs)
Version: Candidate Recommendation
Hardware: PC Windows NT
: 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: 2016-06-26 17:29 UTC by Abel Braaksma
Modified: 2016-09-21 00:46 UTC (History)
0 users

See Also:

Attachments
Updated test cases EQName (25.40 KB, text/xml)
2016-06-28 10:40 UTC, Abel Braaksma 		Details
(corrected) Updated test cases for EQName (25.40 KB, text/xml)
2016-06-28 10:41 UTC, Abel Braaksma 		Details

Description Abel Braaksma 2016-06-26 17:29:23 UTC 
There are currently three valid EQName tests in the EQName.xml file. I would like to see some more XPath tests is possible. Also, it would be helpful if some corner cases were tested, namely:

1) rogue "}" or "{" in the EQName
2) spaces in the URI
3) trailing/leading spaces in the URI (allowed, should be ignored)
4) illegal URI characters (which, if I understand the spec correctly, should not be treated as illegal)
5) relative URI (will not be resolved, but allowed)

(this request follows from a lengthy discussion on EQName productions, most conclusions of which can be found here: https://lists.w3.org/Archives/Public/public-xsl-query/2016Jun/0068.html)
Comment 1 Abel Braaksma 2016-06-28 10:40:17 UTC 
Created attachment 1647 [details]
Updated test cases EQName

(In reply to Abel Braaksma from comment #0)
> There are currently three valid EQName tests in the EQName.xml file. I would
> like to see some more XPath tests is possible. 
Done: in attachment there are now more XP30 tests

> 1) rogue "}" or "{" in the EQName
Done: see attachment

> 2) spaces in the URI
Done, see attachment

> 3) trailing/leading spaces in the URI (allowed, should be ignored)
Done, see attachment

> 4) illegal URI characters (which, if I understand the spec correctly, should
> not be treated as illegal)
Done, see attachment. Note that apparently we may raise XQST0046 on an invalid URI, but the algorithm for doing so is very lenient (you must first escape all non-special characters, as written in XLink, only if it is still illegal, you can raise this).

> 5) relative URI (will not be resolved, but allowed)
Done, see attachment

I think this also resolves Bug 29808 and Bug 29806.
Comment 2 Abel Braaksma 2016-06-28 10:41:42 UTC 
Created attachment 1648 [details]
(corrected) Updated test cases for EQName

(see latest attachment, I accidentally submitted an older version)
Comment 3 Abel Braaksma 2016-09-20 13:38:04 UTC 
I have seen more tests in CVS, and the incorrect ones I submitted have been fixed. I think this bug can now be closed.
Comment 4 O'Neil Delpratt 2016-09-20 13:39:09 UTC 
Resolving this bug according to comment 3