- From: <bugzilla@jessica.w3.org>
- Date: Tue, 28 Jun 2016 10:40:17 +0000
- To: public-qt-comments@w3.org
https://www.w3.org/Bugs/Public/show_bug.cgi?id=29707 --- Comment #1 from Abel Braaksma <abel.braaksma@xs4all.nl> --- Created attachment 1647 --> https://www.w3.org/Bugs/Public/attachment.cgi?id=1647&action=edit 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. -- You are receiving this mail because: You are the QA Contact for the bug.
Received on Tuesday, 28 June 2016 10:40:34 UTC