W3C home > Mailing lists > Public > public-gld-wg@w3.org > March 2012

Re: DCAT - issues related to dcat:Distribution

From: Ghislain Atemezing <auguste.atemezing@eurecom.fr>
Date: Thu, 22 Mar 2012 12:23:56 +0100
Message-ID: <4F6B0BCC.1070907@eurecom.fr>
To: public-gld-wg@w3.org, "Maali, Fadi" <fadi.maali@deri.org>
Hi Fadi, all
> I am summarizing below the discussions related to dcat issues 7,8 and 9 which are all related to dcat:Distribution
> 1)ISUUE 7 - drop dcat:accessUrl:https://www.w3.org/2011/gld/track/issues/7
> based on the discussion on the mailing list dcat:accessUrl is essential for distributions that are not direct downloads which is currently a very common case on catalogs. I suggest we close this issue with no actions required.
+1
> 2) ISSUE 9 - dcat:Distribution and its subclasses are unnecessary:https://www.w3.org/2011/gld/track/issues/9
> dcat:Distribution is needed at least for the same reason that makes dcat:accessUrl needed. However, the subclasses (currently Download, Feed, WebService) need further discussion. The main reason for defining them was to enable some further processing of data based on the distribution class.
> I am slightly inclined towards dropping the subclasses if we define a way to distinguish between distributions that are directly accessible (i.e. clicking on their accessUrl gives back the data) and those that are indirectly accessible (e.g. have to click through a number of links on HTML pages to agree on license ore specify some search criteria).
  AFAIK, for both Feed and WebService, there exists some vocabularies 
specialised in describing them.
Do you mean for Feed vocabs like dady[1] or sioc:feed?
And for webservice, vocabs like gr:relatedWebservice[2] or 
ntag:hasForMedium[3] ?
> 3) ISSUE 8 - add a property to distinguish direct and indirect access of dcat:Distributionhttps://www.w3.org/2011/gld/track/issues/8
> this distinction looks important but not sure if using dcterms:type along with two newly defined values as suggested in the issue description is the best approach.
> at a previous workshop (http://wiki.okfn.org/OpenDataCatalogues/2#Gold_Standard_Best_Practices_Proposal) I found a suggestion for the same issue better:
  There are three suggestion to make this distinction.
+1 for the last suggestion, defining two subclasses "Direct" and 
"InDirect".

Cheers,

Ghislain

[1] http://purl.org/NET/dady
[2]http://www.heppnetz.de/ontologies/goodrelations/v1#relatedWebService
[3]http://ns.inria.fr/nicetag/2010/09/09/voc.html#hasForMedium

-- 
Ghislain Atemezing
EURECOM, Multimedia Communications Department
2229, route des Crêtes, 06560 Sophia Antipolis, France.
e-mail: auguste.atemezing@eurecom.fr & ghislain.atemezing@gmail.com
Tel: +33 (0)4 - 9300 8178
Fax: +33 (0)4 - 9000 8200
Web: http://www.eurecom.fr/~atemezin
Received on Thursday, 22 March 2012 11:24:27 UTC

This archive was generated by hypermail 2.3.1 : Tuesday, 9 December 2014 23:03:31 UTC