ISSUE-62: Clarify scope of datasets and distributions


Clarify scope of datasets and distributions

Raised by:
Richard Cyganiak
Opened on:
This issue combines several items of Last Call feedback. Readers of the spec come away with some uncertainty about its scope and applicability. For example, can it be used to describe APIs? Is everything a dataset? Is it really only intended for downloads? Why the bias towards downloads?

At the F2F3, there seemed to be rough consensus on the following:

* dcat:Dataset is to be interpreted broadly, it's certainly not just for tabular files
* Same for dcat:Distribution
* APIs are a kind of distribution, but DCAT does not include properties for describing them in detail because that would be hard, and existing catalogs don't really go into this
* We have properties for describing one kind of distributions in more details -- downloads. That's because they are common and easy to describe. This doesn't mean that DCAT isn't applicable to other kinds.
* We considered re-introducing a single subclass of dcat:Distribution, for downloads.
* It would be reasonable for extensions to define additional subclasses and properties to specify other kinds of distributions, like APIs, in more detail.

Now we need to work out what changes are required to the spec in order to clarify the document so that readers get this interpretation.
Related Actions Items:
No related actions
Related emails:
  1. ISSUE-62 (DCATscope): Clarify scope of datasets and distributions [DCAT] (from on 2013-04-12)

Related notes:

A paragraph is added to the vocabulary overview addressing this:

Fadi Maali, 25 Jun 2013, 07:01:24

Display change log ATOM feed

Chair, Staff Contact
Tracker: documentation, (configuration for this group), originally developed by Dean Jackson, is developed and maintained by the Systems Team <>.
$Id: 62.html,v 1.1 2014-07-10 11:36:16 carine Exp $