OASIS Mailing List ArchivesView the OASIS mailing list archive below
or browse/search using MarkMail.

 


Help: OASIS Mailing Lists Help | MarkMail Help

soa-rm-ra message

[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]


Subject: Re: [soa-rm-ra] Communicative Action Diagram


ARGHH!!!

Frank - this is getting nowhere quickly.  If we are going to spawn  
action types, we need a clear model of all those types and how they  
relate.  Right now, we just keep generating new ones, further adding  
to the confusion.  I AM STILL LOOKING FOR A VERB DIRECTLY BETWEEN  
COMMUNICATIVE ACTION AND SERVICE ACTION!  Putting Message between them  
and saying conveys doesn't do it.  What the heck is conveys???

The RA is still abstract but if it is to be used it MUST be able to be  
directly translated into concrete things people will build.  Design is  
necessary but the generic component (or a number of options for) must  
be straightforward to see.  How does our model(s) for Action support  
this?

As I've noted before, as part of my day job I'm working on a visual  
representation and ideas for the underlying data by which to express  
service description.  The RA models have to relate to something  
someone can both use and describe.  So far the action exercise has  
been very little in the way of help.

Also remember that whenever we reach closure on Action, I need to  
reflect that is description and Jeff needs to check for changes to  
Interaction.  Our closure has got to be crisp and make sense.  If we  
have six different types of Action and clearing discriminate between  
them, I'll choose the appropriate one(s) and make it work.  If we  
continue to wander here, we will just revisit the questions in those  
sections.

How do our models support description and interaction?  Can they be  
easily realized in concrete implementations?  Those are key questions  
we need to answer.

Deciding less agitated,

Ken



On Jul 9, 2008, at 2:18 AM, Francis McCabe wrote:

> This diagram more-or-less follows the discussion from last week...
>
> <Communicative Actions.png>

-----------------------------------------------------------------------------
Ken Laskey
MITRE Corporation, M/S H305      phone: 703-983-7934
7515 Colshire Drive                         fax:       703-983-1379
McLean VA 22102-7508





smime.p7s



[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]