Hi sebb, On Tue, May 5, 2015 at 7:08 PM, sebb <seb...@gmail.com> wrote: > > > What I can already say is that I do not understand what > > > https://svn.apache.org/repos/asf/infrastructure/site-tools/trunk/projects/data_files > > aim to represent. > > This is the default location for the PMC data [1] files which provide > data about the PMC. > A single such file may be referenced by multiple DOAPs. > E.g. all the Commons components refer to the same PMC data file. >
I do understand how DOAP is being used, and I guess it has been wrong from the very beginning. Taking commons-lang as example, they currently have: <Project rdf:about="http://commons.apache.org/lang/";> <asfext:pmc rdf:resource="http://commons.apache.org/"/> </Project> which does not really link (in RDF) to the file https://svn.apache.org/repos/asf/infrastructure/site-tools/trunk/projects/data_files/commons.rdf 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 PMCs. Beside that issue on linking, I have come to the conclusions that asfext actually have the sense of two things: * asfext:pmc is the property that links a project with its PMC * asfext:PMC should be a class for referring to PMCs And that completely valid, but the tooling should know the difference and not just try to fix wrong data. Let me try to find some time to put some of these things in order to have a better overview... -- Sergio Fernández Partner Technology Manager Redlink GmbH m: +43 6602747925 e: sergio.fernan...@redlink.co w: http://redlink.co
