Re: [soa-rm-ra] Interacting w/Services Model Updated (a start on EDA & event-driven SOA)

[Danny Thornton <danny_thornton2@yahoo.com>]

We could use "Notification Of" between "Event" and
"Real World Effect" in the Interaction Action/Event
model.

http://wiki.oasis-open.org/soa-rm/TheArchitecture/ServiceView/Interaction

Staying at the same level of abstraction as the
Action/Event model on this page of the wiki, the first
three message exchange patterns listed are action
patterns and the fourth MEP listed is an event
pattern.

Danny

--- Duane Nickull <dnickull@adobe.com> wrote:

> Frank:
> 
> I don't even think of events as reports.  They just
> are things of interest.
> A report of an event is the event message that
> carries the notification of
> the event to another entity who has registered to
> receive such
> notifications.  Events themselves should be agnostic
> to what happens based
> on them and if an action is taken as a result of the
> event, that is up to
> the entity who received the notification.
> 
> Duane
> 
> 
> On 3/19/07 10:40 AM, "Francis McCabe"
> <frankmccabe@mac.com> wrote:
> 
> > Michael
> >   You have misunderstood the connection that we
> looked at before here.
> > 
> >   An event cannot cause anything. Least of all an
> action.
> > 
> >   By definition, an event is a report f something
> that has happened
> > that is of interest to someone.
> > 
> >   An action is the application of intent (I
> personally prefer the
> > term force over intent, but that riases more
> potential for
> > misunderstanding) on a target to achieve an
> effect.
> > 
> >   Actions may (but then again may not if the
> action was unsuccessful)
> > give rise to events. An event may be interpreted
> by an agent as a
> > reason for initiating actions.
> > 
> >   Messages may be used to denote events and
> actions. More accurately:
> > 
> > We use message exchange as the realization of
> communication of
> > actions and events.
> > 
> >   More accurately still, following from Herbert
> Clark's notion of
> > joint action:
> > 
> > Participants send and receive messages (which are
> inherently
> > individual actions) in order to participate in
> joint actions (the
> > exchange of a message, the performance of an
> action, the reporting of
> > an event).
> > 
> > In our architecture, actions and events are both
> realized via message
> > exchange. A message may be used to denote an
> action and/or an event.
> > 
> > Frank
> > 
> > On Mar 18, 2007, at 3:13 PM,
> michael.poulin@uk.fid-intl.com wrote:
> > 
> >> Replying to the Jeff's question about
> relationship between Event
> >> and Action, let me suggest that an Event can
> cause an Action
> >> directly or indirectly; plus, in some cases, one
> Action might be
> >> not enough to cause particular Action. All this
> looks complex.
> >> 
> >> Would it be easier to define that an Event can
> relate to the Action
> >> via a Message? On the UML diagram, the 'denote'
> relationships might
> >> be bi-directional... In other words, I propose
> using following UML
> >> construct here:
> >> 
> >>       :EVENT  ------x-------->  :ACTION
> >>                     !
> >>                     !
> >>                     !
> >>                     !
> >>                  :MESSAGE
> >> - Michael
> >> 
> >> 
> > 
> 
> -- 
>
**********************************************************
> Sr. Technical Evangelist - Adobe Systems, Inc.      
>     *
> Chair - OASIS SOA Reference Model Technical
> Committee    *
> Blog: http://technoracle.blogspot.com               
>     *
> Music:
> http://www.mix2r.com/audio/by/artist/duane_nickull*
>
**********************************************************
> 
> 



 
____________________________________________________________________________________
It's here! Your new message!  
Get new email alerts with the free Yahoo! Toolbar.
http://tools.search.yahoo.com/toolbar/features/mail/