Mailing-List: contact dev-help@community.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@community.apache.org
MIME-Version: 1.0
In-Reply-To: 
 <CAOGo0VbFinUxL32=hs3Xoa076H2JNSO7kxHLUoD2f-HCQyVbDA@mail.gmail.com>
References: <2327903.WXJlqcQsHS@herve-desktop>
 <CAOfJQJ0C8_+oH0rbfTgW7T63B3sqYOjT3xT3XZsA_209LApiYQ@mail.gmail.com>
 <CAOGo0VYB8jhvm4QjNc1w5yRqB12BymsXs5Tiubst1BfKXXL+9Q@mail.gmail.com>
 <2372264.ya6xRq0jk6@herve-desktop>
 <CAOGo0VbwttSF5FOL1pRJoFEQzmdrPjOEPEnYDvKV=o34E0SZFw@mail.gmail.com>
 <CAOfJQJ2P8jQdAjU_+ayT4FnoEmjtwHCajD5BT4cyR7JrxXD8fA@mail.gmail.com>
 <CAOGo0VaRKLz6Wsh8O=Sk_Em8L+-KbQ9LSAR8tOKn=tk0vF8+7w@mail.gmail.com>
 <CAOfJQJ1SU=EBGMUHXa=3UxpZUVCmanM-kD-_iEpsAxRXb5COhQ@mail.gmail.com>
 <CAOGo0VY98h6mpyY0DWXBBwVXvCqYKU6DhjtV5zOpMteSJih=5g@mail.gmail.com>
 <CAOfJQJ1j0Tn=yDJFGMDQn8cQQ_a7c2kyXq9bd3whUh=StFKcvQ@mail.gmail.com>
 <CAOGo0VbFinUxL32=hs3Xoa076H2JNSO7kxHLUoD2f-HCQyVbDA@mail.gmail.com>
From: =?UTF-8?Q?Sergio_Fern=C3=A1ndez?= <sergio.fernandez@redlink.co>
Date: Mon, 11 May 2015 14:21:33 +0200
Message-ID: 
 <CAOfJQJ0EQoeTO0aVsHFp=n_VPNinPgOJo9t12R-YEVLdVZsWTg@mail.gmail.com>
Subject: Re: DOAP format question
To: dev@community.apache.org
Cc: =?UTF-8?Q?Herv=C3=A9_BOUTEMY?= <herve.boutemy@free.fr>,
	ASF Site-Dev <site-dev@apache.org>
Content-Type: multipart/alternative; boundary=f46d043c7e666303630515cd6c7f

--f46d043c7e666303630515cd6c7f
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

Hi,

On Mon, May 11, 2015 at 1:13 PM, sebb <sebbaz@gmail.com> wrote:
>
> There is some special-case XSL code which does this conversion.
> If the rdf:resource URL does not end in ".rdf", then the the http://
> and .apache.org/ header and trailer are stripped off, leaving
> "commons"
> This is then assumed to be the name of an RDF file in data_files/
>

Then such " assumption" is a custom patch, it' d need to be know by any
other tool. Therefore no external tool is able to process such data.


> > RDF is a directly-label graph data model that uses URIs as names.
> Therefore
> > the URI you put as as value of a property has a meaning, you should be
> able
> > to directly fetch it, but not having such implicit rules where files a
> > located in a svn. I guess apply that would mean a major restructuration
> of
> > the current DOAP data, but that's something I can help to do to all PMC=
s.
>
> Changing it now would be very time-consuming and tedious.
> However, if this were to be done, I suggest dropping the data_files
> directory entirely and insisting that PMCs host their own PMC data
> files. This would mean adding a new script to create a basic PMC file.
>

We can provides some infrastructure, either to validate or create whatever
in the right way.


> Another aspect of this is where the RDF files are stored.
> These need to be under the control of the project, and it makes sense
> to keep them under source control (SC).
> However SC URLs tend to change, thus breaking the project build.
> Therefore I suggest it would be best if the RDF files were stored
> under the website URL - which is much less prone to change, and
> redirects can deal with any required changes.
> Website source is nowadays stored in SC anyway.
>

FMPOV the cleanest approach would be to serve all that files from each web
site.


> Another aspect is that DOAP files are not useful in source/binary release=
s.
>

We can workout a DOAP extension for such feature.

I just need time ;-)

Cheers,

--=20
Sergio Fern=C3=A1ndez
Partner Technology Manager
Redlink GmbH
m: +43 6602747925
e: sergio.fernandez@redlink.co
w: http://redlink.co

--f46d043c7e666303630515cd6c7f--