W3C home > Mailing lists > Public > w3c-sgml-wg@w3.org > May 1997

RE: trivia, but it's a niggle

From: Andrew Layman <andrewl@microsoft.com>
Date: Fri, 30 May 1997 11:16:25 -0700
Message-ID: <7BB61B44F197D011892800805FD4F792A4C05F@RED-03-MSG.dns.microsoft.com>
To: "'James Clark'" <jjc@jclark.com>, w3c-sgml-wg@w3.org
As usual, James is right.

--Andrew Layman
   AndrewL@microsoft.com

> -----Original Message-----
> From:	James Clark [SMTP:jjc@jclark.com]
> Sent:	Friday, May 30, 1997 12:42 AM
> To:	w3c-sgml-wg@w3.org
> Subject:	RE: trivia, but it's a niggle
> 
> At 17:49 29/05/97 -0700, Andrew Layman wrote:
> >If on Unix, you would indeed say file:///home/ht/mymasterpiece.xml.
> 
> Yes.
> 
> >If
> >on MS Windows, it would be file://\home\ht\mymasterpiece.xml.
> 
> That's not what RFC 1738 says:
> 
>    A file URL takes the form:
> 
>        file://<host>/<path>
> 
>    where <host> is the fully qualified domain name of the system on
>    which the <path> is accessible, and <path> is a hierarchical
>    directory path of the form <directory>/<directory>/.../<name>.
> 
>    For example, a VMS file
> 
>      DISK$USER:[MY.NOTES]NOTE123456.TXT
> 
>    might become
> 
>      <URL:file://vms.host.edu/disk$user/my/notes/note12345.txt>
> 
>    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'.
Received on Friday, 30 May 1997 14:16:26 UTC

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