ISSUE-25: Review requirements: R-SelectHighValue and R-SelectHighDemand
Review requirements: R-SelectHighValue and R-SelectHighDemand
- State:
- CLOSED
- Product:
- Data Usage Vocabulary
- Raised by:
- Antoine Isaac
- Opened on:
- 2014-06-03
- Description:
- I doubt that R-SelectHighValue and R-SelectHighDemand are workable requirements. Who wouldn't need this? Are there really cases that will flourish on crap, irrelevant data?
- Related Actions Items:
- No related actions
- Related emails:
- Re: dwbp-ISSUE-25: Review requirements: R-SelectHighValue and R-SelectHighDemand (from augusto.herrmann@gmail.com on 2014-09-02)
- Re: dwbp-ISSUE-25: Review requirements: R-SelectHighValue and R-SelectHighDemand (from aisaac@few.vu.nl on 2014-08-29)
- RE: dwbp-ISSUE-25: Review requirements: R-SelectHighValue and R-SelectHighDemand (from Deirdre.Lee@deri.org on 2014-08-29)
- Re: dwbp-ISSUE-25: Review requirements: R-SelectHighValue and R-SelectHighDemand (from aisaac@few.vu.nl on 2014-08-22)
- RE: dwbp-ISSUE-38: Review motovation for R-SelectHighValue (from Deirdre.Lee@deri.org on 2014-08-04)
- RE: dwbp-ISSUE-25: Review requirements: R-SelectHighValue and R-SelectHighDemand (from Deirdre.Lee@deri.org on 2014-08-04)
- dwbp-ISSUE-25: Group Dados.gov.br and Radar Palarmentar (from sysbot+tracker@w3.org on 2014-06-03)
Related notes:
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?
Display change log
