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 3158 - fn-resolve-uri-3
Summary: fn-resolve-uri-3
Status: RESOLVED FIXED
Alias: None
Product: XML Query Test Suite
Classification: Unclassified
Component: XML Query Test Suite (show other bugs)
Version: 0.9.0
Hardware: PC Windows XP
: P2 normal
Target Milestone: ---
Assignee: Carmelo Montanez
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2006-04-27 08:46 UTC by Michael Kay
Modified: 2006-05-01 18:59 UTC (History)
0 users

See Also:

Attachments

Description Michael Kay 2006-04-27 08:46:13 UTC 
The expected results for fn-resolve-uri-3 seem to presume that "http//" is not a valid relative URI. However, I believe it is valid according to RFC 3986.

Specically, the RFC in section 4.2 allows

   relative-ref  = relative-part [ "?" query ] [ "#" fragment ]

   relative-part = path-noscheme
                   (as one of the options)

   path-noscheme = segment-nz-nc *( "/" segment )

   segment = *pchar

Note that the ABNF syntax notation (RFC2234) defines *pchar to mean zero-or-more occurrences of pchar". Thus empty segments are allowed, and therefore (given that "http" is a valid segment-nz-nc) "http//" is a valid relative URI reference.
Comment 1 Carmelo Montanez 2006-05-01 18:59:04 UTC 
Michael:

This is correct.  Changed test to use ":" as the relative part.
Please close the bug if in agreement.

Thanks,
Carmelo