W3C home > Mailing lists > Public > public-qt-comments@w3.org > January 2013

[Bug 20642] [FO30] non-hierarchic URIs

From: <bugzilla@jessica.w3.org>
Date: Fri, 11 Jan 2013 11:38:25 +0000
To: public-qt-comments@w3.org
Message-ID: <bug-20642-523-PWJGHl6XSM@http.www.w3.org/Bugs/Public/>
https://www.w3.org/Bugs/Public/show_bug.cgi?id=20642

--- Comment #3 from Tim Mills <tim@cbcl.co.uk> ---
The text

"  A path consists of a sequence of path segments separated by a slash
   ("/") character.  A path is always defined for a URI, though the
   defined path may be empty (zero length).  Use of the slash character
   to indicate hierarchy is only required when a URI will be used as the
   context for relative references. "

might lead one to believe that a URI is hierarchic if it contains a slash.

Microsoft's .NET System.Uri class allows resolution against "opaque" URLs.  Why
does F&O forbid it, since an "opaque" URI is absolute?

var urn = new Uri("urn:isbn:foo");
var mailto = new Uri("mailto:you@example.org");
var foo = new Uri(urn, mailto);
Console.WriteLine(foo); // prints mailto:tim@cbcl.co.uk

var bar = new Uri(mailto, urn);
Console.WriteLine(bar); // prints urn:isbn:foo

-- 
You are receiving this mail because:
You are the QA Contact for the bug.
Received on Friday, 11 January 2013 11:38:27 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Friday, 11 January 2013 11:38:27 GMT