[egr-rg] Use Case Repository draft plan

[Robert Cohen]

Toshi,

I would agree strongly with Dave Snelling's recommendations.

Is it possible to create a provisional template and move this discussion
ahead?

Bob Cohen

Toshiyuki Nakata wrote:

>Dave's　email bounced..
>Toshi
>-------- Original Message --------
>From: David Snelling <David.Snelling at UK.Fujitsu.com>
>Folks,
>
>How about a rather detailed template with required, desired and
>optional headings. Ask people to file the required ASAP, and then later
>the level of detail they feel able to provide.  This way we should be
>able to achieve the following:
>
>1) Actually get a bunch of new use cases in the package.
>
>2) Trap duplicates before people waste effort, e.g. "Thanks for the
>required elements, but we have this already. If your details are
>roughly the same, save yourself some effort or extend it as you see
>fit."
>
>3) We have a place holder and a contact that we can chase on a
>proactive basis if we wish.
>
>4) There was something else, but I can't remember now.
>
>On 10 Jul 2005, at 17:34, Craig Lee wrote:
>
>  
>
>>Ravi,
>>
>>I think it would be very advantageous for GGF to have some uniformity 
>>across
>>use case formats but it would certainly have to strike the right 
>>balance between
>>semantic content and ease-of-collection, and between structure and 
>>free-form.
>>If we start this use case repository, my feeling was to impose the 
>>absoulute
>>minimum amount of structure necessary at the start since we will have 
>>to
>>deal with all the use cases that have already been collected in many 
>>different
>>formats (hence, the use of just keyword lists).  As we go forward, 
>>however,
>>if EGR can find that right balance of properties, then maybe such a 
>>use case
>>template could find wider use across GGF. ;->
>>
>>--Craig
>>
>>
>>At 02:48 AM 7/9/2005, Subramaniam, Ravi wrote:
>>    
>>
>>>Hi Craig,
>>>
>>>Looks good!!
>>>
>>>I would suggest the EGR Use Case template as a good way to add 
>>>structure
>>>to input that you mention. The template could also be a great way to
>>>identify the attributes that need to be tracked on such a page. We 
>>>don't
>>>want to make this similar to a "multiple choice survey" which is easy 
>>>to
>>>take but sparse in semantics and content. We may also need to promote
>>>the EGR use case template as a way to build the richer use cases where
>>>the web page is a good summary to navigate the "hopefully :-)" large
>>>number of use cases.
>>>
>>>Ravi
>>>
>>>-----Original Message-----
>>>From: owner-egr-rg at ggf.org [mailto:owner-egr-rg at ggf.org] On Behalf Of
>>>Craig Lee
>>>Sent: Wednesday, July 06, 2005 1:35 PM
>>>To: egr-rg at gridforum.org; andre at merzky.net; kielmann at cs.vu.nl;
>>>Bruce.R.Barkstrom at nasa.gov; stodghil at cs.cornell.edu
>>>Cc: craig at rushg.aero.org; gcf at indiana.edu
>>>Subject: [egr-rg] Use Case Repository draft plan
>>>
>>>
>>>All,
>>>
>>>Attached is a draft plan for a GGF Use Case Repository.  Please 
>>>comment.
>>>I've tried to work this out such that we can do the simpliest, easiest
>>>things
>>>first that get us the most benefit, and work towards things that may 
>>>be
>>>useful but would require a little more work.  I'm sure there must be
>>>things
>>>I haven't thought about.
>>>
>>>--Craig
>>>
>>>P.S.   This is an _unofficial_ project at this point.  (I think the 
>>>GGF
>>>Front Office
>>>is on vacation this week. ;-)  But why let that stand in the way of
>>>progress ;->
>>>      
>>>
>>    
>>