Re: Do we need "summaries" of the Use Cases?

I'm also in favor of not putting the complete use cases in the report, and
leave them in a frozen wiki.

Having a short summary for each of them could be an interesting option for
an appendix, but before starting this extra work (which may be time
consuming) I suggest we take the time to finish the effort on clusters, and
maybe to have a dedicated call on where to go from here (this would include,
in my view, a discussion on the content of the final report as proposed in
the outline).

I also agree with Karen that not all our content will be based on use cases.
We still have the "topics" list, with a lot of interesting stuff in it.

Emmanuelle

On Thu, Jan 13, 2011 at 11:58 PM, Thomas Baker <tbaker@tbaker.de> wrote:

> On Thu, Jan 13, 2011 at 02:21:51PM -0800, Karen Coyle wrote:
> > I'm a bit concerned about the inclusion of the use cases in the
> > final document. While I think the cases are useful, I think that the
> > final document should be an analysis of our thoughts on LLD and what
> > needs to be incubated, even in areas that are not covered by the use
> > cases. The use cases should be a source of ideas, but not the only
> > source.
> >
> > Therefore, I would rather leave the use cases online. The document
> > could summarize what we learned from them, but does not need to
> > summarize the cases themselves. (cf. the suggestion that each use
> > case be given 3 pages in the document). It is my opinion that the
> > value of the use cases is what they teach us about LLD, not the
> > cases qua cases.
>
> I am also unsure whether the full use cases belong in the
> report per se, even as a long appendix.  Personally, I would
> not object simply to leaving them in a frozen wiki archive (see
> for example [2]).  We need to be realistic about the amount
> of effort it would take to move all of those descriptions
> into another publication format.
>
> My concern is that if the narrative of the report does make
> reference to specific use cases (as in [1]), it should be
> possible for the reader to quickly see what the referenced
> use case is about in a sentence or two, with a link to a
> fuller description.
>
> Or to take the case of "Archives", do you see the references to
> specific use cases [1] as scaffolding for building and supporting
> the argument but that will not necessarily carry through into
> the final report?
>
> Tom
>
> [1]
> http://www.w3.org/2005/Incubator/lld/wiki/Cluster_Archives#Scenarios_.28Case_Studies.29
> [2] http://www.w3.org/2006/07/SWD/wiki/
>
> --
> Tom Baker <tbaker@tbaker.de>
>
>