Mailing-List: contact cocoon-dev-help@xml.apache.org; run by ezmlm
Precedence: bulk
Reply-To: cocoon-dev@xml.apache.org
Message-ID: <3CE41FB5.8080008@yahoo.de>
Date: Thu, 16 May 2002 23:08:05 +0200
From: "J.Pietschmann" <j3322ptm@yahoo.de>
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US;
 rv:1.0rc1) Gecko/20020417
MIME-Version: 1.0
To: cocoon-dev@xml.apache.org
Subject: Re: [Bugs] URLSource
References: <3CE29CE1.4030608@apache.org>
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit

Stefano Mazzocchi wrote:
> NOTE: there is no official indication on how the file: URI should be
> addressed, but all these
> 
>    file:/file
>    file://file
>    file:///file
> 
> are all valid URIs and should point to the same file (at least, this was
> my understanding).

Your understanding is wrong. Only the last is a valid URI.
The RFC for this appears to be
   http://www.rfc-editor.org/rfc/rfc2396.txt
and some predecessors.

> It could be possible to add
> 
>    file:file
> 
> to indicate a relative location.

This is wrong too. An URI starting with an URI scheme
identificator (like file:) is *always* an absolute URI.
This:
   /file
is an *relative* URI, despite being an *absolute* path.

> This is normally achieved by avoiding
> to indicate the protocol (such as in "file"), but since we need a
> protocol to identify the handler, "file:file" might just be a way to
> encode relativity in file positioning.

A relative URI is resolved against a base URI, which sepcifies
the URI scheme. If your base URI is a file URL, *all* relative
URIs encountered are resolved to files. You can't have a base
HTTP URI and suddenly have a relative URI point to a file.

Well, hope this helps:
  http://marc.theaimsgroup.com/?l=xml-cocoon-dev&m=102027988321347&w=2

J.Pietschmann


---------------------------------------------------------------------
To unsubscribe, e-mail: cocoon-dev-unsubscribe@xml.apache.org
For additional commands, email: cocoon-dev-help@xml.apache.org