Difference between revisions of "URI/File scheme"

From Offset
Jump to navigationJump to search
(changed Netscape link to refer to latest incarnation)
(added charter and links; moved plan of action to separate article)
Line 1: Line 1:
−
== Plan of action for updating the file: URI scheme ==
+
== Charter ==
  
−
=== Survey implementations of file: URIs ===
+
This workspace is for the W3C [http://www.w3.org/2001/12/URI/ URI Interest Group] — consisting of subscribers to the group's [http://lists.w3.org/Archives/Public/uri/ mailing list] (which is open to any interested party) — to prepare a '''new draft specification for the 'file' [[Wikipedia:en:Uniform Resource Identifier|URI]] scheme'''.
  
−
What do they implement? How do they map file: URIs to various operating system special situations, including handling of character set transformations, inclusion of drive letters, remote mount directories, individual mount points, symbolic links or redirections?
+
The 'file' scheme is currently defined in section 3.10 of RFC 1738, published in December 1994. Due to the publication of subsequent RFCs, most parts of <nowiki>RFC 1738</nowiki> have been rendered obsolete. However, some of the sections pertaining to a handful of schemes, such as 'file', are still in effect. Members of the URI Interest Group are hoping to produce new RFCs for each of these schemes so that <nowiki>RFC 1738</nowiki> can finally be retired.
  
−
What is useful common practice for getting interoperable results when creating file: URIs?
+
The 'file' scheme draft will be initially prepared here, then taken by an as-yet undesignated editor (most likely, [[User:Lmm|Larry Masinter]]) and reworked into a proper RFC that can then be submitted to the [[Wikipedia:en:Internet Engineering Task Force|IETF]].
  
−
Based on this, update the Proposed Standard for file: URIs to be consistent with common current practice.
+
== What's here ==
 +
* The [[URI/File scheme/Plan of action|plan of action]] for updating the 'file' scheme
  
−
&mdash; [[User:Lmm|Lmm]] 09:35, 21 Jun 2005 (MDT)
+
== Related specifications ==
 +
* RFC 1738
 +
* RFC 2396
 +
* RFC 3986
  
−
Robert Herriot proposes:
+
== Other external links ==
−
 
+
* [http://www.w3.org/2001/12/URI/ W3C URI Interest Group]
−
Here is my quick [[Wikipedia:en:List of web browsers|list of browsers]] that I think we should cover:
+
* [http://lists.w3.org/Archives/Public/uri/ uri@w3.org mailing list archives]
−
 
 
−
*[[Wikipedia:en:Mozilla Firefox|Firefox]]: Windows 2000/XP, maybe Windows 98, Mac OS X, Linux (I hope one flavor is enough)
 
−
*[[Wikipedia:en:Netscape Browser|Netscape]]: same as above
 
−
*[[Wikipedia:en:Mozilla Application Suite|Mozilla]]: same as above (there is a new version, even though I thought that Firefox was supposed to replace Mozilla)
 
−
*[[Wikipedia:en:Opera (web browser)|Opera]]: same as above
 
−
*[[Wikipedia:en:Windows Explorer|Windows Explorer]]: same Windows OSs as above. I assume there is no support for Mac OS X or Linux
 
−
*[[Wikipedia:en:Safari (web browser)|Safari]]: Mac OS X
 
−
*[[Wikipedia:en:Konqueror|Konqueror]]: Linux (KDE)
 
−
*[[Wikipedia:en:Galeon|Galeon]]: Linux (Gnome)
 
−
 
 
−
There are a few more browsers that I have found, but I think the list above covers the major browsers and perhaps a few minor ones.
 
−
 
 
−
I'm not sure whether we should look at any version other than the latest of each. Though perhaps some older versions with a large installed base should be included. As I went through the above list, I would assume that if the latest version doesn't support much, then the earlier versions would do the same or less. I didn't look at the possible versions of each. I have access or could install most of these browsers. The exceptions are Mac OS X and Gnome.
 
−
 
 
−
Among your questions, you listed drive letters, remote mounts, etc. I would add "file" access to local files with a) no hostname, b) "localhost", c) the actual host name. I would also ask whether "file" accesses remote hosts either via their name or IP address when not remotely mounted. My experience with this last question is that it fails with the browsers that I have tried.
 

Revision as of 23:28, 22 June 2005

Charter

This workspace is for the W3C URI Interest Group — consisting of subscribers to the group's mailing list (which is open to any interested party) — to prepare a new draft specification for the 'file' URI scheme.

The 'file' scheme is currently defined in section 3.10 of RFC 1738, published in December 1994. Due to the publication of subsequent RFCs, most parts of RFC 1738 have been rendered obsolete. However, some of the sections pertaining to a handful of schemes, such as 'file', are still in effect. Members of the URI Interest Group are hoping to produce new RFCs for each of these schemes so that RFC 1738 can finally be retired.

The 'file' scheme draft will be initially prepared here, then taken by an as-yet undesignated editor (most likely, Larry Masinter) and reworked into a proper RFC that can then be submitted to the IETF.

What's here

Related specifications

  • RFC 1738
  • RFC 2396
  • RFC 3986

Other external links

Retrieved from "https://offset.skew.org/index.php?title=URI/File_scheme&oldid=12"