Use Cases and Requirements

Hi All,

While  we continue technical discussions  re the Pointer Events 
submission(#PE-Sub) and await the first Editor's Draft, I think it would 
be useful to start identifying the related Use Cases and and requirements.

UCs can help define the scope and purpose of the spec, and that is 
especially useful for those interested in the spec but not actively 
participating. They can also be usefulto describe the  relationship to 
related technologies, in this case Touch Events, Mouse Events, etc. 
Additionally, they can be useful to identifythose features/requirements 
that apply to various versions of the spec. And, lastly, as the spec 
moves to Candidate Recommendation, the group will be asked to identify 
the UCs addressed by the spec.

There are numerous ways to document UCs and Requirements and we are free 
to choose what works best for us. For example, see #UC-Touch and 
#UC-Indie for the UC documents created for the Touch Events and IndieUI 
specs, respectively.

Although we could just start a Call for UCs now, perhaps it would be 
more fruitful to first get someone (more than one person is fine too) to 
commit to leading the UC effort. That personcan then propose the type of 
data/info wanted, create the related "skeleton" document in the group's 
wiki, issue a Call for UCs and then edit the UC document accordingly.

WDYT?

If you would like to help and/or leadthis effort, please let us know (or 
contact me off-list if you prefer).

-Thanks, AB

#PE-Sub <http://www.w3.org/Submission/pointer-events/>
#UC-Touch <http://www.w3.org/2010/webevents/wiki/UCsandReqs>
#UC-Indie <http://www.w3.org/WAI/IndieUI/wiki/Use_Cases_and_Requirements>

Received on Monday, 19 November 2012 16:30:51 UTC