W3C home > Mailing lists > Public > public-dxwg-wg@w3.org > March 2019

Re: [dxwg] Usage notes [RUN] (#86)

From: Alejandra Gonzalez-Beltran via GitHub <sysbot+gh@w3.org>
Date: Mon, 11 Mar 2019 21:41:29 +0000
To: public-dxwg-wg@w3.org
Message-ID: <issue_comment.created-471741537-1552340488-sysbot+gh@w3.org>
@riccardoAlbertoni @andrea-perego I wonder if there is a particular reason you didn't refer to the [Data Use Vocabulary](https://www.w3.org/TR/vocab-duv/), https://www.w3.org/ns/duv, which we also mentioned on the last call? 

While it is quite compact in its definitions, it does provide a class ```duv:Usage``` and a property d

duv:Usage a owl:Class, rdfs:Class ;
  rdfs:label "Usage"@en ;
  rdfs:comment "A helpful description of actions that can be performed on a given dataset or distribution."@en .
duv:hasUsage a rdf:Property ;
    rdfs:label "has dataset/distribution usage"@en ;
    rdfs:comment "Dataset/distribution usage guidance or instructions."@en ;

However, I note that while the definitions seem to refer on how the data can be used (that is the requirement we are trying to address), the example given is more about how the data is actually used (see example 6 at https://www.w3.org/TR/vocab-duv/#examples). The property name ```duv:hasUsage``` is also indicating more how the data is used than any restrictions of usage.

In terms of vocabularies for specifying data use restrictions or limitations for Data Use Agreements, in the context of the Global Alliance for Genomic Health, the [Data Use Ontology](https://github.com/EBISPOT/DUO) has been developed. It defines common terms for determining how the data case be used (see, for example, [data use limitations](https://github.com/EBISPOT/DUO#research-purpose--data-use-limitation-matching) such as 'data available for future general research use', etc).

My understanding is that also [ODRL](https://www.w3.org/TR/odrl-vocab/) could be used to express conditions of usage. 

So, we need a property that allows us to refer to some textual description of the data use conditions (usage notes), an ontology term (such as those from DUO), as well as a more detailed expression of the usage conditions (such as an ODRL expression).

If ```uv:hasUsage``` is appropriate for this, we could re-use it. Otherwise, I think it would be good to create our own property - maybe ```dcat:usageNote``` or perhaps a better name could be ```dcat:useCondition``` if we restrict it to describe "how to use the data."

(BTW, in the context of DATS, we did some analysis on data access and use requirements that is available in this pre-print: https://doi.org/10.1101/518571)

GitHub Notification of comment by agbeltran
Please view or discuss this issue at https://github.com/w3c/dxwg/issues/86#issuecomment-471741537 using your GitHub account
Received on Monday, 11 March 2019 21:41:33 UTC

This archive was generated by hypermail 2.4.0 : Friday, 17 January 2020 19:42:15 UTC