DOAP validation code (was DOAP format question)

[sebb <se...@gmail.com>]

On 5 May 2015 at 16:57, Sergio Fernández <wi...@apache.org> wrote:
> Hi,

<snip/>

> I didn't have much time today, but what I already did was implementing the
> basics of how the DOAP processing could look like. For the moment is at
> https://github.com/wikier/asf-doap until I'll get something more
> functional, then I'll commit it to the asf repo.
>
> Basically what if currently does that simple code is to get all DOAP/PMC
> files and report some basics (size). You can run it by yourself executing:
>
> $ python doap.py
>
<snip/>

I've tried the code, and it does find some syntax errors.

[The code needs to be tweaked so it catches & reports syntax errors
rather than failing]

However, it does not seem to detect asfext:PMC as an error - it seems
to be case-blind.

I cannot work out whether the library supports exact case checking,
and if so, how to enable this.

Nor does it appear to detect invalid tags (perhaps that's why case
checking does not work).

Re: DOAP validation code (was DOAP format question)

[Sergio Fernández <se...@redlink.co>]

As a said, that was a quick approximation of the problem. So the next step
should be a implement such validator, ok, I'll do it in the following days.

On Fri, May 8, 2015 at 1:36 PM, sebb <se...@gmail.com> wrote:

> On 8 May 2015 at 11:51, sebb <se...@gmail.com> wrote:
> > On 5 May 2015 at 16:57, Sergio Fernández <wi...@apache.org> wrote:
> >> Hi,
> >
> > <snip/>
> >
> >> I didn't have much time today, but what I already did was implementing
> the
> >> basics of how the DOAP processing could look like. For the moment is at
> >> https://github.com/wikier/asf-doap until I'll get something more
> >> functional, then I'll commit it to the asf repo.
> >>
> >> Basically what if currently does that simple code is to get all DOAP/PMC
> >> files and report some basics (size). You can run it by yourself
> executing:
> >>
> >> $ python doap.py
> >>
> > <snip/>
> >
> > I've tried the code, and it does find some syntax errors.
> >
> > [The code needs to be tweaked so it catches & reports syntax errors
> > rather than failing]
> >
> > However, it does not seem to detect asfext:PMC as an error - it seems
> > to be case-blind.
> >
> > I cannot work out whether the library supports exact case checking,
> > and if so, how to enable this.
> >
> > Nor does it appear to detect invalid tags (perhaps that's why case
> > checking does not work).
>
> Also, only the first error is reported.
> Ideally the validation needs to find all the errors in one pass.
>
> It would be OK if the code gave up for serious syntax errors such as
> mismatched tags, but where there are multiple other errors these
> should be reported without needing to fix them one by one.
>



-- 
Sergio Fernández
Partner Technology Manager
Redlink GmbH
m: +43 6602747925
e: sergio.fernandez@redlink.co
w: http://redlink.co

Re: DOAP validation code (was DOAP format question)

[Sergio Fernández <se...@redlink.co>]

As a said, that was a quick approximation of the problem. So the next step
should be a implement such validator, ok, I'll do it in the following days.

On Fri, May 8, 2015 at 1:36 PM, sebb <se...@gmail.com> wrote:

> On 8 May 2015 at 11:51, sebb <se...@gmail.com> wrote:
> > On 5 May 2015 at 16:57, Sergio Fernández <wi...@apache.org> wrote:
> >> Hi,
> >
> > <snip/>
> >
> >> I didn't have much time today, but what I already did was implementing
> the
> >> basics of how the DOAP processing could look like. For the moment is at
> >> https://github.com/wikier/asf-doap until I'll get something more
> >> functional, then I'll commit it to the asf repo.
> >>
> >> Basically what if currently does that simple code is to get all DOAP/PMC
> >> files and report some basics (size). You can run it by yourself
> executing:
> >>
> >> $ python doap.py
> >>
> > <snip/>
> >
> > I've tried the code, and it does find some syntax errors.
> >
> > [The code needs to be tweaked so it catches & reports syntax errors
> > rather than failing]
> >
> > However, it does not seem to detect asfext:PMC as an error - it seems
> > to be case-blind.
> >
> > I cannot work out whether the library supports exact case checking,
> > and if so, how to enable this.
> >
> > Nor does it appear to detect invalid tags (perhaps that's why case
> > checking does not work).
>
> Also, only the first error is reported.
> Ideally the validation needs to find all the errors in one pass.
>
> It would be OK if the code gave up for serious syntax errors such as
> mismatched tags, but where there are multiple other errors these
> should be reported without needing to fix them one by one.
>



-- 
Sergio Fernández
Partner Technology Manager
Redlink GmbH
m: +43 6602747925
e: sergio.fernandez@redlink.co
w: http://redlink.co

Re: DOAP validation code (was DOAP format question)

[sebb <se...@gmail.com>]

On 8 May 2015 at 11:51, sebb <se...@gmail.com> wrote:
> On 5 May 2015 at 16:57, Sergio Fernández <wi...@apache.org> wrote:
>> Hi,
>
> <snip/>
>
>> I didn't have much time today, but what I already did was implementing the
>> basics of how the DOAP processing could look like. For the moment is at
>> https://github.com/wikier/asf-doap until I'll get something more
>> functional, then I'll commit it to the asf repo.
>>
>> Basically what if currently does that simple code is to get all DOAP/PMC
>> files and report some basics (size). You can run it by yourself executing:
>>
>> $ python doap.py
>>
> <snip/>
>
> I've tried the code, and it does find some syntax errors.
>
> [The code needs to be tweaked so it catches & reports syntax errors
> rather than failing]
>
> However, it does not seem to detect asfext:PMC as an error - it seems
> to be case-blind.
>
> I cannot work out whether the library supports exact case checking,
> and if so, how to enable this.
>
> Nor does it appear to detect invalid tags (perhaps that's why case
> checking does not work).

Also, only the first error is reported.
Ideally the validation needs to find all the errors in one pass.

It would be OK if the code gave up for serious syntax errors such as
mismatched tags, but where there are multiple other errors these
should be reported without needing to fix them one by one.

Re: DOAP validation code (was DOAP format question)

[sebb <se...@gmail.com>]

On 8 May 2015 at 11:51, sebb <se...@gmail.com> wrote:
> On 5 May 2015 at 16:57, Sergio Fernández <wi...@apache.org> wrote:
>> Hi,
>
> <snip/>
>
>> I didn't have much time today, but what I already did was implementing the
>> basics of how the DOAP processing could look like. For the moment is at
>> https://github.com/wikier/asf-doap until I'll get something more
>> functional, then I'll commit it to the asf repo.
>>
>> Basically what if currently does that simple code is to get all DOAP/PMC
>> files and report some basics (size). You can run it by yourself executing:
>>
>> $ python doap.py
>>
> <snip/>
>
> I've tried the code, and it does find some syntax errors.
>
> [The code needs to be tweaked so it catches & reports syntax errors
> rather than failing]
>
> However, it does not seem to detect asfext:PMC as an error - it seems
> to be case-blind.
>
> I cannot work out whether the library supports exact case checking,
> and if so, how to enable this.
>
> Nor does it appear to detect invalid tags (perhaps that's why case
> checking does not work).

Also, only the first error is reported.
Ideally the validation needs to find all the errors in one pass.

It would be OK if the code gave up for serious syntax errors such as
mismatched tags, but where there are multiple other errors these
should be reported without needing to fix them one by one.