W3C home > Mailing lists > Public > www-tag@w3.org > September 2015

W3C TAG feedback on draft-ietf-appsawg-file-scheme-03

From: Mark Nottingham <mnot@mnot.net>
Date: Tue, 15 Sep 2015 16:40:45 -0400
Cc: Matthew Kerwin <matthew@kerwin.net.au>, Anne van Kesteren <annevk@annevk.nl>
Message-Id: <D3E0BEC7-3542-4E58-B339-71EAB2ABD7F4@mnot.net>
To: Apps Discuss <apps-discuss@ietf.org>
<https://github.com/w3ctag/wiki/wiki/fileUrl>

Version under review:
https://tools.ietf.org/html/draft-ietf-appsawg-file-scheme-03

## General comments

There hasn’t been – to this point – a document that describes how the `file://` scheme works, and for that reason this is a good document. We are glad to see that the document specifies how to convert between file URIs and OS-dependent system filepaths.

### Limitations

Regarding the use of `file://` URIs on the web, there are a few issues that need to be resolved for interoperability:

1. How does `file://` fit into the web's origin model?
2. How does retrieval of `file://` URIs fit into
   [Fetch](https://fetch.spec.whatwg.org/) and/or the [URL standard](https://url.spec.whatwg.org)?

This document does not address any of these issues, so we encourage the APPSAWG to consider addressing these.

Regarding Fetch and URL, we recommend coordinating with Anne van Kesteren (@annevk) of the WHATWG.

The TAG would be happy to coordinate with APPSAWG to address the question of what the origin of `file://` is (coordinating with others like Anne as necessary).

--
Mark Nottingham   https://www.mnot.net/
Received on Tuesday, 15 September 2015 20:41:17 UTC

This archive was generated by hypermail 2.4.0 : Friday, 17 January 2020 22:57:12 UTC