>>>>> Stephane Bortzmeyer <[email protected]> writes:
>>>>> On Sun, Oct 21, 2012 at 01:54:14AM +0700, Ivan Shmakov wrote:
>> What I'm interested in right now is where this I-D is being
>> discussed, as I feel that the empty-authority (ni:///) form is
>> unwarranted there just as well, and a no-authority URI (ni:) should
>> be used instead. (Just like the news: examples above, but contrary
>> to the file: URI scheme.)
> Nobody remembers but note that file:/// also has three slashes for
> "no authority".
Actually, the file: scheme mandates that empty authority shall
be treated identical to the special “localhost” one:
--cut: urn:ietf:rfc:1738 --
As a special case, <host> can be the string "localhost" or the empty
string; this is interpreted as `the machine from which the URL is
being interpreted'.
--cut: urn:ietf:rfc:1738 --
(That being said, there /are/ use cases for file: URI's with
explicit FQDN's.)
While I don't seem to find the “no-authority” variant in the
specification, it seems like a common extension. At the very
least, my browser of choice doesn't complain about, say,
file:/etc/passwd. (Even though it doesn't understand data:.)
Also to note is that I was recently pointed [1] to the following
bit of the 4395bis I-D:
--cut: http://tools.ietf.org/id/draft-ietf-iri-4395bis-irireg-04.txt --
3.2. Syntactic Compatibility
[…]
Avoid improper use of "//". The use of double slashes in the first
part of a URI/IRI is not an artistic indicator that what follows is a
URI/IRI: Double slashes are used ONLY when the syntax of the <scheme-
specific-part> contains a hierarchical structure. In URIs and IRIs
from such schemes, the use of double slashes indicates that what
follows is the top hierarchical element for a naming authority.
(Section 3.2 of RFC 3986 has more details.) Schemes that do not
contain a conformant hierarchical structure in their <scheme-
specific-part> SHOULD NOT use double slashes following the
"<scheme>:" string.
--cut: http://tools.ietf.org/id/draft-ietf-iri-4395bis-irireg-04.txt --
[1] news:c68cb012d9182d408ced7b884f441d4d1e36c36...@nambxv01a.corp.adobe.com
--
FSF associate member #7257
_______________________________________________
p2p-hackers mailing list
[email protected]
http://lists.zooko.com/mailman/listinfo/p2p-hackers
