ISSUE-20: Review use cases organization - change the order

Review use cases organization - change the order

Data Usage Vocabulary
Raised by:
Antoine Isaac
Opened on:
Many cases are not real 'cases', let alone 'use cases'. Especially those at the beginning. E.g. case #5 (tracking of data usage), #7 (machine-readability of licenses) and #8 (machine-readability of SLAs) do not have obvious usage scenarios. They look more like general challenges or even requirements. In fact they appear almost as such as requirements later.
There are also cases like #3 and #4 that just call for datasets in specific domains to be published. They don't really say who needs them, for what, nor what the challenges are.
On the other hand, we've got mammoth cases, with real usage scenarios, or at least real data publishers: #21, #25, #21...
Putting them at the end is a bit counter-productive. I would recommend to start with these much more flesh, and then put the smaller or less obvious cases after. Actually in such an editorial state these lesser cases could be just use as a mere excuse to introduce challenges or requirements that are not introduced in the bigger ones.
Related Actions Items:
No related actions
Related emails:
  1. Issue tracking (from on 2014-07-18)
  2. UCR issues (from on 2014-07-18)
  3. dwbp-ISSUE-20: Review use cases organization - change the order (from on 2014-06-03)

Related notes:

Order of use cases presentation was changed. More real usage scenarios are presented first.

Bernadette Farias Loscio, 5 Jun 2014, 02:14:04

Display change log ATOM feed

Chair, Staff Contact
Tracker: documentation, (configuration for this group), originally developed by Dean Jackson, is developed and maintained by the Systems Team <>.
$Id: 20.html,v 1.1 2017/02/13 15:26:30 ted Exp $