- From: Eric Stephan <ericphb@gmail.com>
- Date: Thu, 16 Apr 2015 13:47:15 -0700
- To: Public DWBP WG <public-dwbp-wg@w3.org>
- Message-ID: <CAMFz4jiRDii9E=Kzo1DNRViXrutqfsmjB4Pc7aDn2M6_5TPxWw@mail.gmail.com>
Question: Does the following help clarify/confuse the quality needs from the Dataset Usage Vocabulary perspective? I'm not sure if anyone from the Data Quality Vocabulary was on the call on the second day of F2F3 when we discussed the Data Usage Vocabulary topic. I think there were some important points that were made: 1) The "Data Usage Vocabulary" had been changed to the "Dataset Usage Vocabulary". 2) This name change was done with the intention to focus our efforts on providing a vocabulary at the DCAT:Dataset level only. 3) By focusing efforts at the DCAT:Dataset level it allowed us to avoid the seemingly endless are we talking data or dataset discussions. Most importantly it allowed us to talk about DCAT:Dataset has being a logical container for a "set of data". My hope is that this might simply how we build bridges between the Dataset Usage Vocabulary and the Data Quality Vocabulary. Below are listed some tangible minimal quality related requirements for DCAT:Dataset Usage: * Consumer DCAT:Dataset usage should be tracked by metrics such as a counter. * Consumers should be able to provide feedback on overall DCAT:Dataset quality * Consumers should be rated for their qualifications when commenting on DCAT:Dataset. * Metrics should be used to rate consumer acceptability for a DCAT:Dataset. - Boolean metrics should be used to indicate overall approval/disapproval. - Integer scale metrics should be used to indicate levels of acceptability. * Metrics should be used to rate qualifications of consumer providing opinions about a DCAT:Dataset I welcome more ideas for requirements, but these requirements do illustrate the data quality needs of the Dataset Usage Vocabulary. I look forward to your thoughts and ideas, Eric S
Received on Thursday, 16 April 2015 20:47:42 UTC