ISSUE-70: Should we have use-cases in specifications
usecases-in-spec
Should we have use-cases in specifications
- State:
- CLOSED
- Product:
- APIs — General
- Raised by:
- Max Froumentin
- Opened on:
- 2010-01-27
- Description:
- Should specifications have a use-case section? Or should the decision be made on a case-by-case basis?
Max's claim: Use-cases (and requirements) are helps, meant for writing the specification itself, but not part of the specification. Examples are ok, as they help the implementer get a quick overview of a specific API, but use-cases are just as well replaced by more generic wording saying "this specification enables webapps to do XXX, YYY and ZZZ".
- Related Actions Items:
- No related actions
- Related emails:
- Re: Publishing System Information API FPWD (from maxfro@opera.com on 2010-01-27)
- ISSUE-70 (usecases-in-spec): Should we have use-cases in specifications [APIs — General] (from sysbot+tracker@w3.org on 2010-01-27)
Related notes:
We resolved to leave that up to the editors, as they see fit; closing
Dominique Hazaël-Massieux, 25 Aug 2010, 16:21:02Display change log
