W3C home > Mailing lists > Public > public-lod@w3.org > August 2015

Re: First DCAT validator in the world

From: Gregg Kellogg <gregg@greggkellogg.net>
Date: Sun, 2 Aug 2015 18:48:56 -0700
Cc: Pieter Colpaert <pieter.colpaert@ugent.be>, "public-lod@w3.org" <public-lod@w3.org>
Message-Id: <D766E13C-49EB-4DFF-AB99-DDD60E0F0146@greggkellogg.net>
To: Stan Callewaert <callewaert.stan@gmail.com>
> On Aug 1, 2015, at 8:50 AM, Stan Callewaert <callewaert.stan@gmail.com> wrote:
> 
> Hi Gregg
> 
> There's a big difference between the site you mentioned (http://linter.structured-data.org <http://linter.structured-data.org/>) and our site: www.dcat.be/validator <http://www.dcat.be/validator>.
> The site you mentioned just gives back the stucture of the DCAT feed. Our site really returns the errors and warnings of the dcat feed, that way users can correct their dcat feed and make fully correct to the rules of DCAT-AP (http://dcat.be/images/dcat-ap.png <http://dcat.be/images/dcat-ap.png>).
> 
> To sum things it up i would say your website shows the stucture, ours shows the mistakes that are in it.

The linter also looks for “errors” that can be detected based on violation of domain and range for a number of vocabularies, including DCAT (taking the interpretation that, e.g., an inferred domain that conflicts with the stated type of the subject can be considered a markup error, rather than an implicit assertion that the subject has the type of the conflicting domain). It’s principally used for schema.org markup, but can be used with any RDF serialization and about 50 different vocabularies.

Of course, it also shows site structure and may attempt to show a “snippet” based on the semantic content, for selected classes and properties.

Errors and warnings are displayed after the extracted structure.

Of course, if there are errors not being detected, these would be bugs, and may indicate an outdated version of DCAT loaded into the linter.

Gregg

> Kind regards
> Stan
> 
> 2015-07-31 16:57 GMT+02:00 Gregg Kellogg <gregg@greggkellogg.net <mailto:gregg@greggkellogg.net>>:
> The Structured Data Linter <http://linter.structured-data.org <http://linter.structured-data.org/>> should also be able to validate DCAT in arbitrary RDF markup.
> 
> Gregg Kellogg
> 
> Sent from my iPad
> 
> On Jul 31, 2015, at 12:56 AM, Pieter Colpaert <pieter.colpaert@ugent.be <mailto:pieter.colpaert@ugent.be>> wrote:
> 
>> Hi Stan,
>> 
>> I doubt whether it's the first DCAT validator ever, but it certainly is a great contribution to the LOD community. Worth mentioning for the people on this list as well:
>> 
>> There is an npm (javascript/nodejs) library which you can customize with your own mandatory or recommended properties:https://www.npmjs.com/package/dcat-validator <https://www.npmjs.com/package/dcat-validator>
>> 
>> Furthermore the source code of both the GUI as the npm package are available: https://github.com/oSoc15/dcat-validator <https://github.com/oSoc15/dcat-validator> andhttps://github.com/oSoc15/dcat-validator.js <https://github.com/oSoc15/dcat-validator.js>.
>> 
>> Next to seeing your contributions to the codebase, we'd love to see you use the dcat-validator as a specific data catalog validator for your country or field of expertise. Let us know what you think!
>> 
>> Kind regards,
>> 
>> Pieter
>> 
>> On 31-07-15 06:48, Stan Callewaert wrote:
>>> Hello DCAT-users,
>>> 
>>> We are two students working on the DCAT-project for open Summer of code 2015. The project is about creating the first DCAT validator, which gives you feedback, telling you whether your DCAT feed is valid or not. This project is organised by Open Knowledge Belgium and funded by the Flemish government. 
>>> The intention of the DCAT validator is to show the user errors or wanings when respectively mandatory or required properties are missing. The validation can easily be done by manually inserting the feed, uploading a file or inserting a URI. Through the use of different tabs you can change the way you insert your feed. As a user you can also select and insert different formats like RDF:XML, JSON-LD and Turtle. These formats are supported by the validator as well. The validator will parse these formats and serialize them as Turtle so they can be validated. Once you have selected your format you can add your feed to the validator.
>>> 
>>> After validation, your errors and warnings are presented. To find more information about the error or warning you can expand the box which will show you what properties are wrong or missing. Each property can be expanded as well to show a property URI which will direct the user to a page which contains more information about the property. As an extra feature, when inserting a URI, the user can select the option 'Automatic' instead of selecting a format. This option checks which format your URI contains, automatically selects the right parser and validates it. This way the user doesn't have to select a format when he wants to validate by URI. Selecting a format and inserting your DCAT feed is very easy and doesn't take long, depending on the size of your feed.
>>> 
>>> In short, this is the first DCAT validator which helps you as a user to check if your DCAT feed is valid or not. It contains a few features to help insert different formats and validate them. The errors and warnings are shown and can be expanded for more information about its properties. 
>>> You can test the validator right here: www.dcat.be/validator <http://www.dcat.be/validator>
>>> Kind regards
>>> 
>>> The DCAT-validator team.
>>> 
>>> Stan Callewaert 
>>> e-mail: callewaert.stan@gmail.com <mailto:callewaert.stan@gmail.com>
>>> Sébastien Henau
>>> e-mail: sebastienhenau@hotmail.com <mailto:sebastienhenau@hotmail.com>
>> -- 
>> +32486747122 <tel:%2B32486747122>
>> Linked Open Transport Data researcher
>> UGent - MMLab - iMinds
>> 
>> Board of Directors Open Knowledge Belgium
>> http://openknowledge.be <http://openknowledge.be/>
>> 
>> Open Transport working group coordinator at Open Knowledge International
>> http://transport.okfn.org <http://transport.okfn.org/>


Received on Monday, 3 August 2015 01:49:27 UTC

This archive was generated by hypermail 2.4.0 : Friday, 17 January 2020 16:22:24 UTC