W3C home > Mailing lists > Public > public-gld-comments@w3.org > May 2012

Comments on DCat

From: Rufus Pollock <rufus.pollock@okfn.org>
Date: Thu, 31 May 2012 16:59:30 +0100
Message-ID: <CAEvtuKqDMUGp+Y9F-_Gx0KTAt2eD_5=kAf27GrWOH9Gxfzvt8g@mail.gmail.com>
To: public-gld-comments@w3.org
Cc: David Raznick <david.raznick@okfn.org>, James Gardner <james@3aims.com>, "Maali, Fadi" <fadi.maali@deri.org>, Richard Cyganiak <richard@cyganiak.de>, Ross Jones <ross.jones@okfn.org>
Hi All,

A few weeks ago I spoke in some detail with Faadi Mali about DCat and
to discuss some suggested modifications. The results of this
discussion are inlined below. I'd be interested to hear people's
thoughts and whether people would be happy to make these
modifications.

Regards,

Rufus

## Dataset concept

* Remove dcat:accessURL and just use Resource (Distribution)

  * Status: agreed and in progress

* Remove dcat:dataDictionary (leave for v2 or v1.1)

  * Better to introduce once practice has established a need and consistent
    usage. One should be parsimonious in generating new properties at this
    early stage.
  * Also currently has Inconsistent usage
  * Status: ticket and discuss

* Remove dcat:dataQuality (ditto)

  * As previous

* Remove dcat:granularity (or specify better)

  * As previous

* Remove dc:references (is it used and how would it be used)

  * Suggest removal since for linking datasets we should have (at some point):
    derives, links_to, sibling, partof
  * Remember that people can always add other attributes they want ...
  * Status: ticket and discuss

* Make clear what is optional versus required (?) e.g.

  * Designate as optional: dcterms:accrualPeriodicity
  * Designate as optional: dcat:theme
  * Resolution: ticket and discuss

Possibly to add (but will not happen for the present):

* version
* partof

## Distribution / Resources concept

* Rename dcat:Distribution to dcat:Resource

  * Distribution has a strong connotation from software of a packaged version
    of the entire dataset whereas, in fact, in most cases it will be a data
    file or API associated to the Dataset for which the term Resource is more
    appropriate.
  * Status: ticket and discuss

* Extend the set of attributes a Resource may have

  * [Optional] Add dc:title to Resource
  * [Optional] dcat:mimetype - see
http://docs.ckan.org/en/latest/domain-model-resource.html

    * http://docs.ckan.org/en/latest/domain-model-resource.html#resource-format-strings
    * could also have mimetypeInner

  * [Optional]: hash (md5 or sha1, must be of form md5:{hash} or sha1:{hash})
  * [Optional]: dc:created and dc:modified

* Size: define it as bytes and add sizeString. That is:

  * dcat:size = number / size in bytes
  * [Add] dcat:sizeString: informal string description size e.g. >1Mb
Received on Thursday, 31 May 2012 16:00:06 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Thursday, 31 May 2012 16:00:07 GMT