====== RFC8089 - The "file" URI Scheme ======
[[dido:public:ra:xapend:xapend.b_stds:tech:ietf:start| return to the IETF Standards ]]
Data sheet for RFC8089 The "file" URI Scheme (file)
| Title | The "file" URI Scheme |
| Acronym | file |
| Version | 2017 |
| Document Number | RFC8089 |
| Release Date | February 2017 |
| Reference | [[https://tools.ietf.org/html/rfc8089]] |
: **Note**: The following is an excerpt from the official IETF RFC. It is provided here as a convenience and is not authoritative. Refer to the original document as the authoritative reference.
===== Introduction =====
A file URI identifies an object (a "file") stored in a structured
object naming and accessing environment on a host (a "file system").
The URI can be used in discussions about the file, and if other
conditions are met, it can be dereferenced to directly access the
file.
This document specifies a syntax based on the generic syntax of
[RFC3986] that is compatible with most existing usages. Where
incompatibilities arise, they are usually in parts of the scheme that
were under-specified in earlier definitions and have been tightened up
by more recent specifications. Appendix A lists significant changes
to syntax.
/**=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
/* To add a discussion page to this page, comment out the line that says
~~DISCUSSION:off~~
*/
~~DISCUSSION:on|Outstanding Issues~~
~~DISCUSSION:off~~