Mailing-List: contact site-dev-help@apache.org; run by ezmlm
Precedence: bulk
Received-SPF: softfail (nike.apache.org: transitioning domain of
 sebbaz@gmail.com does not designate 54.76.25.247 as permitted sender)
MIME-Version: 1.0
In-Reply-To: <2372264.ya6xRq0jk6@herve-desktop>
References: <2327903.WXJlqcQsHS@herve-desktop>
	<CAOfJQJ0C8_+oH0rbfTgW7T63B3sqYOjT3xT3XZsA_209LApiYQ@mail.gmail.com>
	<CAOGo0VYB8jhvm4QjNc1w5yRqB12BymsXs5Tiubst1BfKXXL+9Q@mail.gmail.com>
	<2372264.ya6xRq0jk6@herve-desktop>
Date: Tue, 5 May 2015 11:51:03 +0100
Message-ID: 
 <CAOGo0VbwttSF5FOL1pRJoFEQzmdrPjOEPEnYDvKV=o34E0SZFw@mail.gmail.com>
Subject: Re: DOAP format question
From: sebb <sebbaz@gmail.com>
To: =?UTF-8?Q?Herv=C3=A9_BOUTEMY?= <herve.boutemy@free.fr>
Cc: =?UTF-8?Q?Sergio_Fern=C3=A1ndez?= <wikier@apache.org>,
	dev@community.apache.org, ASF Site-Dev <site-dev@apache.org>
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

On 5 May 2015 at 07:06, Herv=C3=A9 BOUTEMY <herve.boutemy@free.fr> wrote:
> Le mardi 5 mai 2015 01:05:31 sebb a =C3=A9crit :
>> > OK, but that's because whoever code the XSLT decided to be defensive t=
o
>> > such interpretation.
>>
>> If you read back in this thread you will see that I did this in order
>> to support both asfext:PMC and asfext:pmc.
>>
>> > But that does not mean is right.
>>
>> The code is right in the sense that it works with the input files that
>> are provided.
> +1
> that's a temporary workaround that we should try to not need any more in =
the
> future

Ideally, yes, but as already noted that is not trivial.

> [...]
>
>> >> Also if it is possible to validate that the various RDF files are
>> >> correct according to the formal definitions.
>> >> PMCs could then submit their files for checking.
>> >
>> > I think we can discuss that infrastructure for the new site. I'm happy=
 to
>> > help. Python provides the required libraries. I'll open a thread, prob=
ably
>> > tomorrow.
>>
>> I think there needs to be a way for PMCs to check their RDF files
>> against the formal definitions.
>> For example, a CGI script that accepts the URL of a file.
> +1
> I tried W3C checker, but as it is only a syntax checker, it checked only
> syntax, not references to the namespace
> and I couldn't find any other useful tool :(
>
> Other tools to make effective use of the DOAP files would be useful too: =
but I
> completely agree that the first priority seems to have a more complete ch=
ecker

It's possible to add warning checks to the cron job scripts, but this
will create a lot of noisy e-mails until projects have been notified
and fixed their files.
Experience shows that fixing DOAPs can take months for some PMCs.

One approach that might be worth trying is creating an additional
on-demand report that checks the list of RDFs for known issues.
Initially it could just check for asfext:PMC, but could be extended as
other issues are found or better syntax checking is available.

Checking for such simple typos could be done with almost any scripting lang=
uage.

The RDF files are listed in

https://svn.apache.org/repos/asf/infrastructure/site-tools/trunk/projects/f=
iles.xml
(DOAPs)
and
https://svn.apache.org/repos/asf/infrastructure/site-tools/trunk/projects/p=
mc_list.xml
(PMC definitions)

Most of the PMC definitions are stored locally, and have already been fixed=
.

> Regards,
>
> Herv=C3=A9
>
>>
>> > Cheers,
>> >
>> > --
>> > Sergio Fern=C3=A1ndez
>> > Partner Technology Manager
>> > Redlink GmbH
>> > m: +43 6602747925
>> > e: sergio.fernandez@redlink.co
>> > w: http://redlink.co
>