- From: Lee, Deirdre <Deirdre.Lee@deri.org>
- Date: Mon, 4 Aug 2014 14:30:23 +0000
- To: Data on the Web Best Practices Working Group <public-dwbp-wg@w3.org>
Just because requirements are obvious, doesn't mean we shouldn't include them :) Measuring what 'high-value' is may be subjective, but 'Datasets selected for publication should be in demand by potential users' is measurable. However not sure if not publishing data because there is no immediate/obvious demand is good best practice either... Do these requirements make sense in the context of quality vocabulary? -----Original Message----- From: Data on the Web Best Practices Working Group Issue Tracker [mailto:sysbot+tracker@w3.org] Sent: 03 June 2014 23:19 To: public-dwbp-wg@w3.org Subject: dwbp-ISSUE-25: Review requirements: R-SelectHighValue and R-SelectHighDemand dwbp-ISSUE-25: Review requirements: R-SelectHighValue and R-SelectHighDemand http://www.w3.org/2013/dwbp/track/issues/25 Raised by: Antoine Isaac On product: Could #20 (Radar Parlamentar) be grouped with #12 (Dados.gov.br)? It seems the former is actually a usage case of the latter.
Received on Monday, 4 August 2014 14:30:53 UTC