RE: [Bug 29707] New: [QT3] EQName tests for XPath and corner cases

For most of today, W3C's BugZilla appears to be down (I keep getting a 503 error on every page). I wanted to resolve this bug by proposing test cases. Since I cannot commit them myself, I attach this proposal here.

It also resolves Bug 29706 (test incorrectly marked XP30) and likely also solves Bug 29708 (discussion on production rules of EQNames and spaces in the URI). For the latter, several test cases have been added.

Quite a few of these new tests seem to fail currently, it possible that I introduced typos, a review of the new tests is therefore warranted.

Some of these tests are taken as variants of Michael Sperberg-McQueen's earlier test cases in the mail on fixing the serialization spec. This is, however, not related to serialization.

Thanks,
Abel 

> -----Original Message-----
> From: bugzilla@jessica.w3.org [mailto:bugzilla@jessica.w3.org]
> Sent: Sunday, June 26, 2016 7:29 PM
> To: public-qt-comments@w3.org
> Subject: [Bug 29707] New: [QT3] EQName tests for XPath and corner cases
> 
> https://www.w3.org/Bugs/Public/show_bug.cgi?id=29707
> 
>             Bug ID: 29707
>            Summary: [QT3] EQName tests for XPath and corner cases
>            Product: XPath / XQuery / XSLT
>            Version: Candidate Recommendation
>           Hardware: PC
>                 OS: Windows NT
>             Status: NEW
>           Severity: normal
>           Priority: P2
>          Component: XQuery 3 & XPath 3 Test Suite
>           Assignee: oneil@saxonica.com
>           Reporter: abel.braaksma@xs4all.nl
>         QA Contact: public-qt-comments@w3.org
>   Target Milestone: ---
> 
> 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)
> 
> --
> You are receiving this mail because:
> You are the QA Contact for the bug.