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 2310 - 4.2 Module declaration
Summary: 4.2 Module declaration
Status: CLOSED FIXED
Alias: None
Product: XPath / XQuery / XSLT
Classification: Unclassified
Component: XQuery 1.0 (show other bugs)
Version: Last Call drafts
Hardware: All All
: P4 trivial
Target Milestone: ---
Assignee: Don Chamberlin
QA Contact: Mailing list for public feedback on specs from XSL and XML Query WGs
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2005-09-28 12:29 UTC by Pierrick Brihaye
Modified: 2005-09-28 14:33 UTC (History)
0 users

See Also:

Attachments

Description Pierrick Brihaye 2005-09-28 12:29:07 UTC 
From :

[5]    	ModuleDecl 	   ::=    	"module" "namespace" NCName "=" URILiteral Separator

then :

[140]    	URILiteral 	   ::=    	StringLiteral

Syntactically, a URILiteral is identical to a StringLiteral: a sequence of zero
or more characters enclosed in single or double quotes.

... it is not clear whether :

module namespace foo="";

is legal or not.

Should it be ?
Comment 1 Don Chamberlin 2005-09-28 14:11:26 UTC 
Pierrick,
Thank you for this comment. On Sept. 28, 2005, the Query Working Group decided 
that it is an error for a module declaration to specify a target namespace 
using an empty URILiteral. A new static error will be defined for this 
condition in the next edition of the XQuery specification. I have marked this 
issue as "Fixed." If you agree with this resolution, please mark the issue 
as "Closed."
Regards,
Don Chamberlin (for the Query Working Group)
Comment 2 Pierrick Brihaye 2005-09-28 14:33:34 UTC 
An alternative would be to have the opportunity to declare modules in the
"default" namespace by not specifying any binding.

However, it would have too many side effects on the current XQuery grammar, I'm
afraid :-)

I'm so closing this bug.

Thank you for your quick answer.

p.b.