* http://www.faqs.org/rfcs/rfc1738.html {{//Section 3.10 of RFC1738The file URL scheme is used to designate files accessible on a particular host computer. This scheme, unlike most other URL schemes, does not designate a resource that is universally accessible over the Internet. 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'. The file URL scheme is unusual in that it does not specify an Internet protocol or access method for such files; as such, its utility in network protocols between hosts is limited.}} * The file URI Scheme (Internet-Draft) http://www.ietf.org/internet-drafts/draft-hoffman-file-uri-03.txt * 关于 c|/foo/bar.txt 的用法 相对URI c:/foo/bar.txt 根据RFC2396 是不合法的。但某些URI 处理器允许用 | 代替 : (The file URI Scheme (Internet-Draft) Section 3.2 中有提到) 使得可以表达上述相对URI {{ RFC2396 Authors should be aware that a path segment which contains a colon character cannot be used as the first segment of a relative URI path (e.g., "this:that"), because it would be mistaken for a scheme name. It is therefore necessary to precede such segments with other segments (e.g., "./this:that") in order for them to be referenced as a relative path. }} * 一个关于file scheme在各种系统上的实现的调查 http://www.dpawson.co.uk/xsl/sect4/uriIncl.html Test on file access Expectations: An xml uriincl.xml is in same directory as stylesheet program run from /sgml/uriincl directory Access to an h: drive is accessible(else change it) - Not viable on *nix? If windows, \\church is available (same as h:). The test file is available on h: Form used SAXON 6.5.2 from Michael Kay vsn 1 Microsoft vsn 1 libxslt vsn 1.0 Apache Software Foundation vsn 1 Fourthought Inc. vsn 1 uriIncl.xml OK OK OK OK OK file:/uriIncl.xml failed Not run failed failed failed file://uriIncl.xml failed Not run failed failed failed file:///uriIncl.xml failed Not run OK failed failed file:///c:/sgml/uriincl/uriIncl.xml OK OK OK OK failed file://c:/sgml/uriincl/uriIncl.xml OK OK failed OK failed file:/c:/sgml/uriincl/uriIncl.xml OK OK failed OK failed file:///h:/uriIncl.xml OK OK OK OK failed file://h:/uriIncl.xml failed OK failed failed failed file:/h:/uriIncl.xml OK OK failed OK failed file:/localhost/c:/sgml/files/uriIncl.xml failed Not run failed failed failed file://localhost/c:/sgml/uriincl/uriIncl.xml OK OK OK OK failed file:///localhost/c:/sgml/files/uriIncl.xml failed Not run failed failed failed h:/uriIncl.xml failed OK OK OK Not run \\church\data3\users\dpawson\uriIncl.xml failed OK failed OK failed //church/data3/users/dpawson/uriIncl.xml failed OK OK failed OK file://church/data3/users/dpawson/uriIncl.xml failed OK failed failed OK file://\\church\data3\users\dpawson\uriIncl.xml failed OK failed OK OK file:///h:/uriIncl.xml OK OK OK OK failed file:///h:/uriIncl.xml OK OK OK OK failed '' failed Not run failed failed failed file:///c:/sgml/uriincl/uriincl.xml OK OK OK OK Not run Conclusions uri access is quite variably implemented. Also limited by OS (acceptable), by language (variable, e.g. Java security restricts access to networked drives) and by implementors options.