- From: Data on the Web Best Practices Working Group Issue Tracker <sysbot+tracker@w3.org>
- Date: Fri, 10 Apr 2015 16:26:56 +0000
- To: public-dwbp-wg@w3.org
dwbp-ISSUE-154 (Eric Stephan): Handling data usage references to collection of datasets [Data Usage Vocabulary] http://www.w3.org/2013/dwbp/track/issues/154 Raised by: Eric Stephan On product: Data Usage Vocabulary Dataset is currently defined along the lines of the DCAT definition. It is fairly common that organizations or scientific domains refer to a dataset as a collection of data. How do we accommodate the need to provide feedback on a collection of data? For instance if I am performing a simulation of climate change and sharing the results with a collaborator they will be mainly providing feedback on the entire collection of datasets and not each dataset individually. If we use dcat:Dataset and dcat:Catalog without breaking the DCAT model then we basically have to duplicate all properties in the data model. I'd like to avoid this. What I propose is that we have: 1) a duv:Collection class as you suggested Bernadette 2) make a parent class for dcat:Dataset and duv:Collection that would serve as a "inode" 3) Call this parent class duv:Data (or something else - please suggest) 4) All data usage and feedback would relate to duv:Data. Also we could consider: schema.org tends to use a parent class called CreativeWork that carries many of the aspects of data usage. CreativeWork (https://schema.org/CreativeWork ) acts as a parent class of anything on the web including DCAT. It also provides mechanisms for citation, discussion, etc. http://schema.org/docs/schema_org_rdfa.htm
Received on Friday, 10 April 2015 16:26:57 UTC