- From: Fadi Maali <fadi.maali@deri.org>
- Date: Thu, 30 May 2013 11:32:30 +0100
- To: Jeni Tennison <jeni@theodi.org>
- Cc: public-gld-comments@w3.org, Stuart Harrison <stuart.harrison@theodi.org>
Hello Jeni, Thanks a lot for your feedback on DCAT vocabulary. The Working Group supported your suggestion of using dct:rights instead of dct:license. It is implemented in the draft now: https://dvcs.w3.org/hg/gld/raw-file/default/dcat/index.html Best regards, Fadi -------------------------------------------------- Fadi Maali PhD student @ DERI Irish Research Council Embark Scholarship holder http://www.deri.ie/users/fadi-maali On 3 Apr 2013, at 11:56, Jeni Tennison <jeni@theodi.org> wrote: > Hi, > > I've been looking at DCAT from an legal perspective. The extent of the legal metadata supported within DCAT, are that both Distributions and Catalogs have a license property (described as "The license under which the distribution is made available"). > > In Europe, data publishers have both copyright and database rights over the data that they publish, and may have to reference more than one licence as a result. In addition, there is often extra information that supplements the licence to enable reusers to fulfil it, such as the attribution that they have to provide when they reuse. Having a single link to a licence and not having a mechanism to give this supplementary information might be too simplistic. > > So, I wonder whether it would be better to incorporate dct:rights than dct:license, and link to a rights statement that would include licensing and attribution information both for the copyright and for the database right if there is one. > > I note that in CKAN the link to the licence uses the relation dct:rights. The only things related to licensing in data.gov are around attribution (I believe this is because all US government data is public domain). > > Cheers, > > Jeni > -- > Jeni Tennison, Technical Director theODI.org > +44 (0) 7974 420 482 @JeniT > > >
Received on Thursday, 30 May 2013 10:32:59 UTC