Do we need "summaries" of the Use Cases?

Dear all,

The final report outline [1] foresees an appendix with
edited Use Cases, one per page.

I'm wondering if each Use Case should have a one- or 
two-sentence summary describing what it is and how it 
uses (or plans to use) linked data?

For now, these summaries could be added just after the "Owner"
section and before "Background and Current Practice".  If the
summaries were short enough, maybe we could even put them into
the body of the report, where they would take up perhaps one
and a half pages that people might actually read as opposed
to forty pages that people are more likely to skim.

I'm even wondering if the summaries could be "transcluded"
into the outline, but I never quite got my head around how
that really works (and whether it would be worth the extra 
technical work).

If others think this is a good idea, I'd be willing to pick
off a few Use Cases as examples.  Writing a summary, I find,
it is a good way to re-read something carefully.

More generally, we're moving into a phase in which we will
need to be doing alot more re-reading, and I'm wondering what
ground rules we should set for making editorial corrections.
It would require alot of extra email for everyone to ask
permission of curators before making edits, but I'm guessing
that in most cases the additional effort would be welcome.

Unless there are objections, I suggest we all feel free to
make corrections of a minor wordsmithing or editorial nature
to any document, even "curated" ones, but that after we have
done so, we should as a courtesy send a note to the authors
with a link to the "diff" showing our changes (e.g., [2]).

Tom

[1] http://www.w3.org/2005/Incubator/lld/wiki/FinalReportOutline
[2] http://www.w3.org/2005/Incubator/lld/wiki/index.php?title=ScribeDuty&diff=2668&oldid=2526

-- 
Tom Baker <tbaker@tbaker.de>

Received on Thursday, 13 January 2011 19:53:13 UTC