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 15283 - [QT3TS] module-URIs-5, -6: use of base URI to resolve module namespace
Summary: [QT3TS] module-URIs-5, -6: use of base URI to resolve module namespace
Status: CLOSED FIXED
Alias: None
Product: XPath / XQuery / XSLT
Classification: Unclassified
Component: XQuery 3 & XPath 3 Test Suite (show other bugs)
Version: Member-only Editors Drafts
Hardware: PC All
: P2 normal
Target Milestone: ---
Assignee: Matthias Brantner
QA Contact: Mailing list for public feedback on specs from XSL and XML Query WGs
URL:
Whiteboard:
Keywords:
: 15677 (view as bug list)
Depends on:
Blocks:
 
Reported: 2011-12-20 17:10 UTC by Michael Kay
Modified: 2012-06-06 09:01 UTC (History)
3 users (show)

See Also:

Attachments

Description Michael Kay 2011-12-20 17:10:06 UTC 
The expected results for tests module-URIs-5 and module-URIs-6 assume that the module namespace URI if relative is resolved against the base URI of the query. There is nothing in the spec that says this should happen. Module namespaces are like other namespaces: relative URIs are deprecated and their behaviour is undefined.
Comment 1 Matthias Brantner 2011-12-20 18:21:55 UTC 
In general, I agree with Mike's comment and propose to remove the two tests in question.

However, there are two places in the spec which might be misleading and could be improved.

4.5 Base URI Declaration
"For example, the Static Base URI property is used when resolving relative URIs for module import."

It seems that this is only referring to location hint URIs.

4.12.1 Module URIs
"Module URIs should be treated in the same way as other namespace URIs."

I was wondering whether this sentence could be a bit stronger. That is, replace "should" with "must".
Comment 2 Michael Kay 2012-01-23 21:36:49 UTC 
*** Bug 15677 has been marked as a duplicate of this bug. ***
Comment 3 Matthias Brantner 2012-06-04 21:13:58 UTC 
The two tests were removed in rev. 1.7 of prod/ModuleImport.xml.
Comment 4 Tim Mills 2012-06-06 09:01:20 UTC 
Confirmed fixed.  Thanks.