This is the mail archive of the
docbook-apps@lists.oasis-open.org
mailing list .
Re: extension for saxon 6.4.3 broken?
On 20010727 18:51 (Friday), Dave Pawson wrote:
> I'd love to have this confirmed.
> Even the 'experts' back off from declaring a position on this.
>
> win32 file://
> Unix file:///
>
> Anyone say any different?
For more information on this, I would suggest to refer to the
* RFC "Uniform Resource Identifiers (URI): Generic Syntax"
http://www.ietf.org/rfc/rfc2396.txt
* RFC "Uniform Resource Locators (URL)"
http://www.ietf.org/rfc/rfc1738.txt
Here are some chosen pieces :
----------------------------------------------------------------------
The URI syntax is dependent upon the scheme. In general, absolute
URI are written as follows:
<scheme>:<scheme-specific-part>
An absolute URI contains the name of the scheme being used (<scheme>)
followed by a colon (":") and then a string (the <scheme-specific-part>)
whose *interpretation depends on the scheme*.
The URI syntax does not require that the scheme-specific-part have
any general structure or set of semantics which is common among all
URI. However, a subset of URI do share a common syntax for
representing hierarchical relationships within the namespace. This
"generic URI" syntax consists of a sequence of four main components:
<scheme>://<authority><path>?<query>
----------------------------------------------------------------------
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'.
BNF
fileurl = "file://" [ host | "localhost" ] "/" fpath
----------------------------------------------------------------------
So the following are correct on Unix:
file://localhost/home/user/data/fileResource
file:///home/user/data/fileResource
And I can only guess, and cannot test, for Microsoft Windows:
file://localhost/C:\somedir\anotherone\fileResource
file:///C:\somedir\anotherone\fileResource
So I don't see any reason why "file://" could be correct for a win32 platform...
Hope it helps,
--
Marc-Aurčle DARCHE <http://ma.darche.free.fr>
AFUL <http://www.aful.org>
Association Francophone des Utilisateurs de Linux/Logiciels Libres
French speaking Linux and Free Software Users' Association
------------------------------------------------------------------
To unsubscribe from this elist send a message with the single word
"unsubscribe" in the body to: docbook-apps-request@lists.oasis-open.org