cygri / void

An RDF schema and associated documentation for expressing metadata about RDF datasets
http://www.w3.org/TR/void/
15 stars 1 forks source link

Mapping to dcat? #63

Open GoogleCodeExporter opened 9 years ago

GoogleCodeExporter commented 9 years ago
The dcat vocabulary is a work-in-progress RDF vocabulary for publishing 
government data 
catalogs, such as data.gov or data.gov.uk, as RDF. 

dcat was initiated [1] at DERI, and is now a project [2] of the W3C eGovernment 
Interest Group.

dcat contains terms such as Catalog, Dataset, and Distribution (a distribution 
represents the 
availability of a dataset in a particular format, such as Excel or KML).

The scope of voiD and dcat overlap when we have government datasets that are 
available in RDF. 
Such datasets could have a voiD descriptions, and they could have a dcat 
description that has a 
distribution with format RDF. Some alignment between voiD and dcat in these 
cases would be 
good.

I see two principal options:

1. void:Dataset and dcat:Dataset have an intersection (some datasets are 
members of both). That 
is, a government dataset that is available in RDF is also an RDF dataset 
described in voiD.

2. a void:Dataset is a subclass of dcat:Distribution. That is, a government 
dataset may have a 
distribution that is an RDF dataset described in voiD.

My preference is (1).

For a mapping, simple subclass/subproperty mappings are insufficient because of 
the different 
structure. VoiD has no concept of distributions.

Perhaps we could develop a CONSTRUCT query that maps from dcat to voiD, and one 
for the 
other direction. Perhaps we could also have an ASK query that determines wether 
a dcat dataset 
is a voiD dataset: The condition is that the dcat dataset must have a 
distribution that is in an RDF 
format.

A related question is how to describe availability of a dataset as a SPARQL 
endpoint in dcat...

[1] http://vocab.deri.ie/dcat-overview
[2] w3.org/egov/wiki/Data_Catalog_Vocabulary

Original issue reported on code.google.com by richard....@gmail.com on 2 May 2010 at 7:14

GoogleCodeExporter commented 9 years ago
As per today's teleconference, we will mark this for Release 3.0, because dcat 
is still a moving target, and the 
alignment can first be developed in a separate document outside of voiD.

Original comment by richard....@gmail.com on 27 May 2010 at 10:09

GoogleCodeExporter commented 9 years ago
Issue 81 has been merged into this issue.

Original comment by richard....@gmail.com on 31 Oct 2010 at 1:32