- From: Matthias Schunter <mts@zurich.ibm.com>
- Date: Sun, 18 Sep 2011 17:26:21 +0200
- To: public-tracking@w3.org
Hi Folks, I like and support a common format. The proposed format is fine with me. I expect it to drive some structure into the use cases. Regards, Matthias On 9/18/2011 12:37 AM, Karl Dubost wrote: > Hi everyone, > > to avoid losing too much time in collecting use cases and to ground our discussions in pragmatic cases meant to solve current issues, I propose to write our issues according to: > > > # Summary > What is the issue? > (1 simple short sentence) > > # Issue > What problem are we trying to solve (one issue only) > (1 or 2 paragraphs) > > # Positive Effects > Why should we care? What are we improving for people? implementers? > (1 or 2 paragraphs) > > # Risks > Are there any risks associated with this feature, proposal? > What might fail and why? > > # Implementations > Is it already implemented? > Where? How? Who? > > # Related > List of references > (specification, tutorial, articles, code) > > > ps: mostly stolen from the W3C HTML WG and the (now defunct) W3C QA WG > -- Dr. Matthias Schunter, MBA IBM Zurich Research Laboratory, Ph. +41 (44) 724-8329 Homepage: www.schunter.org, Email: schunter(at)acm.org PGP Fingerprint 989AA3ED 21A19EF2 B0058374 BE0EE10D
Received on Sunday, 18 September 2011 15:26:56 UTC