RE: draft-hoffkohn-rfc1738bis-00.txt

> From: uri-request@w3.org [mailto:uri-request@w3.org]On Behalf Of Paul
> Hoffman / IMC
> Sent: Sunday, August 17, 2003 1:32 AM
> To: uri@w3.org
> Subject: draft-hoffkohn-rfc1738bis-00.txt
>
>
>
> Greetings. After being prodded to produce an Internet Draft on
> historical URI schemes, I completely dropped the ball and didn't
> announce the draft to this mailing list. So, here it is:
>     draft-hoffkohn-rfc1738bis-00.txt
>
> All comments are welcome. There are two open issues listed in the
> document, and I look forward to hearing opinions on them.
>
>     Section 2.8: will be updated to include specific usage of the file:
>     scheme on different operating systems
>
> Having done some experimentation, I believe that we can't say much
> general about particular operating systems. Instead, it seems like
> various versions of browsers and other URL resolvers do different
> things for file: based on the whim of the implementer. I can
> certainly discuss that in a paragraph, but that's probably all we
> need.
> ...

I think the document should try to give answers to the following FAQs --
even if the answer happens to be that there is no interoperable
solution/answer:

1) How do I embed a Windows drive letter?

-> file:///c:/path

2) Can I put in relative paths?

-> not in an absolute URL

3) What's the syntax for accessing Windows file shares?

-> file:////share/path

4) How do I encode non-ASCII characters in filenames?

Encode the filename in UTF-8, then URL-escape (this may not be widely
implemented, but I think this what SHOULD be implemented).


Julian


(see also
<http://www.mozilla.org/quality/networking/testing/filetests.html>)

--
<green/>bytes GmbH -- http://www.greenbytes.de -- tel:+492512807760

Received on Sunday, 17 August 2003 06:33:51 UTC