- From: Larry Masinter <masinter@adobe.com>
- Date: Tue, 9 Dec 2014 19:54:41 +0000
- To: Matthew Kerwin <matthew@kerwin.net.au>, IETF Apps Discuss <apps-discuss@ietf.org>
- CC: Sam Ruby <rubys@intertwingly.net>
- Message-ID: <DM2PR0201MB09602B351692D424A49C6B0DC3650@DM2PR0201MB0960.namprd02.prod.outlook.>
I applaud the move to document file:. Three comments on http://tools.ietf.org/html/draft-kerwin-file-scheme First comment: Please align with the special processing for “file:” in: https://specs.webplatform.org/url/webspecs/develop/ That spec (developed in sync with WHATWG URL) focuses on parsing and processing of base + relative, when the scheme (or base scheme) is “file:”, while the kerwin-file-scheme talks more about mapping between local file paths and “file:” IRIs (URLs). But the overlap is significant, and I hope could be eliminated, if the direction of moving the webplatform.org spec to obsolete 3987 is accepted. Second comment: You describe the relationship between local file names and ‘file:’ URLS for “UNIX-like”, “DOS- or Windows-based” and “VMS Files-11”. These categories aren’t precise or exhaustive, and file system processing of file names can vary depending on version, language pack installed in OS, as well as network protocol (Nfs?). I would rather see a more extensible organization of the specification by establishing a template, and then separately documenting, on a file-system by file-system basis, how to translate and match, based not on the URI but on the parsed components resulting from URL-parsing. This would allow new or different file systems to be documented. Third comment: The translation between file names and URLs and things like them happen in several specs: content-disposition for file download, multipart/form-data for file upload, by common HTTP servers, when packaging files together into archive types as being discussed by those proposing a new ‘archive’ top level media type. It would be beneficial if we converge these, as it reduces interoperability to have incompatible methods of translation for local files names depending on the categorization. Larry -- http://larry.masinter.net From: apps-discuss [mailto:apps-discuss-bounces@ietf.org] On Behalf Of Matthew Kerwin Sent: Thursday, September 25, 2014 6:13 PM To: IETF Apps Discuss; uri@w3.org Subject: [apps-discuss] Fwd: FW: New Version Notification for draft-kerwin-file-scheme-13.txt FYI: this is my file URI draft, now listing apps-discuss as the official place for discussion. >>> A new version of I-D, draft-kerwin-file-scheme-13.txt has been successfully submitted by Matthew Kerwin and posted to the IETF repository. Name: draft-kerwin-file-scheme Revision: 13 Title: The file URI Scheme Document date: 2014-09-26 Group: Individual Submission Pages: 16 URL: http://www.ietf.org/internet-drafts/draft-kerwin-file-scheme-13.txt Status: https://datatracker.ietf.org/doc/draft-kerwin-file-scheme/ Htmlized: http://tools.ietf.org/html/draft-kerwin-file-scheme-13 Diff: http://www.ietf.org/rfcdiff?url2=draft-kerwin-file-scheme-13 Abstract: This document specifies the "file" Uniform Resource Identifier (URI) scheme, replacing the definition in RFC 1738. It attempts to document current practices, while at the same time defining a common core which is intended to interoperate across the broad spectrum of existing implementations. Note to Readers (To be removed by the RFC Editor) This draft should be discussed on the IETF Applications Area Working Group discussion list <apps-discuss@ietf.org<mailto:apps-discuss@ietf.org>>. Please note that it may take a couple of minutes from the time of submission until the htmlized version and diff are available at tools.ietf.org<http://tools.ietf.org>. The IETF Secretariat -- Matthew Kerwin http://matthew.kerwin.net.au/
Received on Tuesday, 9 December 2014 19:55:15 UTC