W3C home > Mailing lists > Public > public-dxwg-wg@w3.org > April 2018

Re: [dxwg] Allow license property to link to other than LicenseDocument

From: Karen Coyle <kcoyle@kcoyle.net>
Date: Wed, 18 Apr 2018 16:43:58 -0700
To: public-dxwg-wg@w3.org
Message-ID: <cbef6928-6891-587b-0ac3-f5cb933e6107@kcoyle.net>


On 4/18/18 3:31 PM, Andrea Perego via GitHub wrote:
> Thanks for the example, @nicholascar .
> 
> As requested during [today's call of the DCAT
> subgroup](https://www.w3.org/2018/04/18-dxwgdcat-minutes.html#x04), I
> include a pointer to the [Open Data Rights Statement (ODRS)
> vocabulary](http://schema.theodi.org/odrs/) designed by @ldodds , which
> could be relevant to this discussion.
> 
> Consider the following (quite common) scenario:
> 
>> I have two resources, both using CC-BY, but with different attribution
>> and copyright notices. Attribution and copyright notice are clearly
>> not part of the licence (CC-BY). So, where can I specify this
>> information, and how can I link it to the relevant resource and its
>> licence?

https://wiki.creativecommons.org/wiki/CC_REL
https://creativecommons.org/ns#

CC has a rights language that includes creator, title, along with a link
to the CC license. This can be generated using the "select a license" on
the CC site. I assume that nothing in DCAT will prevent someone from
linking to a CC license using its REL.

I have some CC licenses on documents on my own site, but they are very
old and may have been superseded. If you use the selector on the CC site
you'll see what gets generated. Like schema.org, it is intended to be
embedded in HTML - not sure if anyone is using it in any other way, or
if it is used much at all.

kc

> 
> The ODRS approach is to attach attribution and copyright notice to a
> `dct:RightsStatement` (by using _ad hoc_ properties), and then link the
> `dct:RightsStatement` to both the resource and the licence - which are
> also directly linked via `dct:license`. The [diagram included in the
> ODRS specification](http://schema.theodi.org/odrs/) gives a clear
> picture of this pattern.
> 
> Note that ODRS addresses also other requirements - e.g., rights
> jurisdiction, being able to specify licence compatibility, having
> different licences/rights for a database and its content (about this,
> see the notion of [_sui generis_ database
> rights](https://en.wikipedia.org/wiki/Sui_generis_database_right)). More
> details are provided in the documentation accompanying ODRS:
> - the [use
> cases](https://github.com/theodi/open-data-licensing/wiki/Use-cases)
> behind its design
> - the [publishers'
> guide](https://github.com/theodi/open-data-licensing/blob/master/guides/publisher-guide.md)
> 
> - the [re-users'
> guide](https://github.com/theodi/open-data-licensing/blob/master/guides/reusers-guide.md)
> 
> 
> 
> 

-- 
Karen Coyle
kcoyle@kcoyle.net http://kcoyle.net
m: 1-510-435-8234 (Signal)
skype: kcoylenet/+1-510-984-3600
Received on Wednesday, 18 April 2018 23:44:26 UTC

This archive was generated by hypermail 2.3.1 : Monday, 25 March 2019 10:33:22 UTC