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 5136 - K2-DirectConElemNamespace-17, 18
Summary: K2-DirectConElemNamespace-17, 18
Status: CLOSED FIXED
Alias: None
Product: XML Query Test Suite
Classification: Unclassified
Component: XML Query Test Suite (show other bugs)
Version: 1.0.2
Hardware: PC Windows NT
: P2 normal
Target Milestone: ---
Assignee: Frans Englich
QA Contact: Mailing list for public feedback on specs from XSL and XML Query WGs
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2007-10-08 13:16 UTC by Tim Mills
Modified: 2007-10-31 15:55 UTC (History)
0 users

See Also:


Attachments

Description Tim Mills 2007-10-08 13:16:26 UTC
Test K2-DirectConElemNamespace-17 and -18 expect XQST0022, and specifically comment that bracket-escapes are invalid in namespace declarations.  In the XQuery spec, 3.7.1.2 Namespace Declaration Attributes we find:

"The value of a namespace declaration attribute must be a URILiteral; otherwise a static error is raised [err:XQST0022]."

I'd argue that the value of this attribute is "content{" which is a URILiteral since it matches:

[140]    	URILiteral 	   ::=    	StringLiteral
[144]    	StringLiteral 	   ::=    	('"' (PredefinedEntityRef | CharRef | EscapeQuot | [^"&])* '"') | ("'" (PredefinedEntityRef | CharRef | EscapeApos | [^'&])* "'")

Where does the specification state that bracket-escapes are invalid in this context?

(:*******************************************************:)
(: Test: K2-DirectConElemNamespace-17                    :)
(: Written by: Frans Englich                             :)
(: Date: 2007-10-02T13:04:11+01:00                       :)
(: Purpose: A namespace must be a literal, for which bracket-escapes are invalid
. :)
(:*******************************************************:)
<e xmlns="content{{"/>

XQST0022
Comment 1 Frans Englich 2007-10-08 14:02:20 UTC
Bug #5083 is relevant to this.
Comment 2 Frans Englich 2007-10-31 10:32:31 UTC
These should be fixed in CVS, and tests added & aligned for bug #5083.


Frans
Comment 3 Tim Mills 2007-10-31 15:55:07 UTC
Thanks.