Use Case Categorization

Dear All,

We need do an initial refinement of the Use Case categorization on the wiki so that we have an initial consensus driven scheme to organize our use case collection efforts and reduce the need to move wiki pages around in the future.  Here is the current categorization from Lloyd:


*       Profile Scenarios

*       Profile Use Cases

*       Social Data Syntax Use Cases

*       Social API Use Cases
And here is what I added:

*       Human Interaction Use Cases

*       About the Human Use Cases

*       Technical Foundations

*       Ubiquitous Attributes
The first 4 are based on specific requirements.  My thinking is that the links on the main Use Case Page should be hierarchical in that we minimize the links from the main wiki page to concept areas and then have further drill downs on the sub pages.  So for example, Profile Use Cases might fall under About the Human and Social API Use Cases might
fall under technical attributes and would be listed on that subpage rather than the main Use Case wiki page.

Question  - do we adopt the approach of the first four or the second four, or is there a better alternative?
Request - regardless of which categorization scheme you support, please identify missing categories/sub categories/use case titles you envision to help us flesh this out.

Best Regards,
Mark