W3C home > Mailing lists > Public > uri@w3.org > January 2005

RE: I-D ACTION:draft-hoffman-file-uri-03.txt

From: Israel Viente <israel_viente@il.vio.com>
Date: Mon, 31 Jan 2005 10:16:19 +0200
To: <uri@w3.org>
Cc: "'Mike Brown'" <mike@skew.org>
Message-Id: <20050131080843.2730133C53@sa5.bezeqint.net>

> Well, in what context does it "work"?
1) start->Run->Open box
2) I.E address box
3) Windows explorer address box
4) In command prompt 
C:\Documents and Settings\Israel>start
file://raid-backup/public/Books/ADSI-Scripting-Errata-1578702194.pdf

I think it is much more close to RFC 1738 where file://host/path pattern is
used than the file://// pattern. 

Israel

-----Original Message-----
From: Mike Brown [mailto:mike@skew.org] 
Sent: Thursday, January 27, 2005 9:11 PM
To: Israel Viente
Cc: uri@w3.org
Subject: Re: I-D ACTION:draft-hoffman-file-uri-03.txt

Israel Viente wrote:
> Another comment:
> This draft says:
> | For Windows shares, there is an additional "/" prepended to the name.
> |   Thus, the file "example.doc" on the shared directory "department"
> |   would have the URL:
> |
> |   file:////department/example.doc
> 
> If you are talking about UNC paths like \\server\department\example.doc 
> Translating to file://server/department/example.doc works fine on Windows
as
> well as file:////server/department/example.doc.
> But I think it should be clarified since windows shares has usually
> host/share/path segments.

Well, in what context does it "work", and can we infer from that some kind
of 
canonical format?

The thing you have to realize is that Windows's resolver is very lenient
about 
accepting whatever string you give it and trying to make some sense of it. 
Sometimes it will show you what it thinks you meant (as happens in the
Address 
Bar widget in Explorer and Internet Explorer), and sometimes it won't.

We keep going back and forth on this, but the file URI draft should probably

try to document these situations, and make a recommendation or at least
point
out the caveats, if any, of each format.

Ideally, *Microsoft* should settle on a mapping of UNC paths to URI 
components. Are there any MS engineers on this list who could spearhead
such an effort?

-Mike
Received on Monday, 31 January 2005 08:16:29 UTC

This archive was generated by hypermail 2.3.1 : Tuesday, 6 January 2015 21:25:08 UTC