Mailing-List: contact dev-help@forrest.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@forrest.apache.org
Received-SPF: pass (herse.apache.org: domain of ross.gardler@googlemail.com
 designates 209.85.146.179 as permitted sender)
DomainKey-Signature: a=rsa-sha1; c=nofws;
        d=googlemail.com; s=beta;
        h=received:message-id:date:from:sender:to:subject:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references:x-google-sender-auth;
        b=ZVKAt/mVjxSJbte/vUpKuADwVT5spAI764ejbaDKm3EKiKIhgqZFjocOpPO1ccyn5yZxXiboC2qjWoyWJ91xdl24ZtSSqICvZgtfF0rvClVSw1bxuFWZ44JXibE+eQk8bPp9f4i18J29wqgOjuDdbHV9ipn6egrfwlQ0nKOWDp4=
Message-ID: <61c9bc470707121619m67061653u2eb09a7446477ae8@mail.gmail.com>
Date: Fri, 13 Jul 2007 00:19:35 +0100
From: "Ross Gardler" <rgardler@apache.org>
Sender: ross.gardler@googlemail.com
To: dev@forrest.apache.org, sina@khakbaz.com
Subject: Re: Type Detection for RDF/XML files
In-Reply-To: <36815.192.168.1.35.1184067327.webmail@192.168.1.35>
MIME-Version: 1.0
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
References: <36815.192.168.1.35.1184067327.webmail@192.168.1.35>

On 10/07/07, Sina K. Heshmati <sina@khakbaz.com> wrote:
> I'm currently using the following pattern to catch the target files for the SKOS plugin:
>
> <map:match pattern="**skos.xml">
> ...
> </map:match>
>
> As the pattern suggests, files whose name ends with 'skos.xml' will be processed as SKOS files. Fine, but how bad is it?

It means that all requests need a fixed URL space. Forrest should not
define a users URL space. However, keeping things moving is important
at this stage.

> The issue FOR-1005 [1] suggests that the 'sourcetypeaction' mechanism should be used
> to determine the type of a file and set actions accordingly. We see in FOR-1018 [2]
> that we need to extend our existing implementation of the sourcetypeaction mechanism
> to be able to support RDF/XML formats.
>
> One might take an approach similar to bootstrapping, that is:
>
> 0. Try to determine the file type by parsing the filename; if failed,
> 1. Fallback to sourcetypeaction mechanism with a minimum number of tests; if failed,
> 2. Type left undetermined, that is no actions.
>
> If we decide to parse the filename to determine the type of a file, then we'll need to have conventions set for each format.
>
> What do you think should be done to determine the type of RDF/XML formats?

In an ideal world we will always avoid using filename. However, there
is a need to progress with your work and a good enough solution is,
well, good enough, until someone has the desire to fix it.

I would say your 0. and 1. steps should be reversed.

Ross