W3C home > Mailing lists > Public > public-lod@w3.org > October 2018

Re: Use the void and schema.org [Was; Re: LODAtlas 1.0 release - Browsing Linked Data Catalogs]

From: <emmanuel.pietriga@inria.fr>
Date: Thu, 4 Oct 2018 15:22:15 +0200
To: Linking Open Data <public-lod@w3.org>
Message-Id: <693B24AE-834F-447C-B903-88C1B83D7BDB@inria.fr>

> On 4 Oct 2018, at 14:55, Jeremy Debattista <jeremy.debattista@adaptcentre.ie> wrote:
> Hi Emmanuel,
> I will try to answer your questions:
>> - Has VoID achieved good coverage yet? (I remember reading that few datasets were exposing VoID descriptions, but that may have been several years ago and things might have changed)
> Around December 2015, we wanted to evaluate the quality of the datasets in the LOD cloud. Back then we thought that one of the main entry points for a dataset would be via voID metadata. From 569 datasets, only around 98 datasets had a voID description defined (not necessarily in their datahub metadata though). Furthermore, we also found out that most voID metadata had broken links to their datasets (one in particular is DBpedia, whom I’ve recently asked to fixed - not sure if it is fixed or not now). We performed more experiments which we discussed in our paper [1]

Thanks for the pointer to the paper. For reference, the one I was vaguely remember is at http://dx.doi.org/10.1007/978-3-319-11955-7_61 

>> - How do we get those decentralized VoID descriptions? Is there a crawling service somewhere that would give us access to such descriptions?
> Back when voID was introduced, the editors said that one best practice is to put the metadata in the /.well-known/void path of the fully qualified domain name [2]. We did check that but I don’t remember if we had any success with it.
> Fast-forward to 2018. We have restarted our quality assessment. This time we are doing a monthly assessment. Getting access to these supposedly open datasets is still painful imo. I thought of doing what Alasdair suggested, however, I think it would only be beneficial if whoever is publishing datasets is also updating this metadata (void, schema, dcat.. whichever suits them best). Furthermore, if we need some sort of a crawling service, then I would prefer if the /.well-known mechanism is used for such metadata.

What I’m contemplating, following this discussion, is to enable dataset import by submitting VoID description URIs, possibly automatically following links to other VoID descriptions of declared interlinked datasets. Anything beyond that, I consider (for the time being) as "outside of our jurisdiction”.

We won’t be making much progress on this issue until after ISWC (next week). People who want to discuss this issue (or any other related to LODAtlas) will have an opportunity to talk to us there (Hande, the senior engineer in charge of this project, will be presenting the paper).

Thanks for the feedback provided so far, it’s highly relevant.

best regards,
Emmanuel Pietriga
Received on Thursday, 4 October 2018 13:22:39 UTC

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