W3C home > Mailing lists > Public > public-dwbp-wg@w3.org > August 2014

RE: dwbp-ISSUE-31: Define categories for the use cases based on the level of use cases details

From: Lee, Deirdre <Deirdre.Lee@deri.org>
Date: Mon, 4 Aug 2014 15:37:41 +0000
To: Data on the Web Best Practices Working Group <public-dwbp-wg@w3.org>
Message-ID: <DA0D3B2CE5F5614AA2307A974AFAC39BFB60FBBF@UDSMBX02.uds.nuigalway.ie>
I can see the distinction, but not sure what the overall benefit of categorising use-cases would be. All requirements are currently general and abstracted from both the specific and general use-cases. Could the deliverables benefit from more specific requirements?

-----Original Message-----
From: Data on the Web Best Practices Working Group Issue Tracker [mailto:sysbot+tracker@w3.org] 
Sent: 03 June 2014 23:38
To: public-dwbp-wg@w3.org
Subject: dwbp-ISSUE-31: Define categories for the use cases based on the level of use cases details

dwbp-ISSUE-31: Define categories for the use cases based on the level of use cases details

http://www.w3.org/2013/dwbp/track/issues/31


Raised by: Makx Dekkers
On product: 

There is quite a difference in the level of detail in the use cases and also in the nature of the technical challenges. As far as I can see, there are two broad categories of use cases. Most of them are based on actual practical experience where specific challenges are derived from problems that were encountered (e.g. UC6, 10 through 25) but some are based on more general considerations, like a general need for documenting release schedules or provision of feedback mechanisms (e.g. UC1, 2, 5, 7, 8, 9) that lead to more open questions or general requirements.
Would it be useful to distinguish the two categories in separate sections?



Received on Monday, 4 August 2014 15:38:11 UTC

This archive was generated by hypermail 2.3.1 : Tuesday, 6 January 2015 20:24:16 UTC