RE: [ebsoa] Groups - Work breakdown and schedule draft (ebSOA Task Breakdown and Draft Deliverables Schedule.doc) uploaded

Radha,

 

Great clarification points.  I think we need to include
something about the notion of the types of exchanges as well - the
SOA/COP group just posted something on the three types of collaboration
that is instructive here.

 

I think we should have some liaison across our two groups - even if
its just at an ad hoc "emergent" level through mutual cross
membership!?! ; -)

 

Thanks, DW
===================================================

From: 
"Cory Casanave" <>

Date: 
Fri, Mar 31, 2006 8:04 am

To: 
"'Service-Oriented Architecture CoP'" <>

Just
as a point of interest, we could identify 3 kinds of
community
behavior;
* Directed (Implies a director)
*
Contracted (Agreed behavior, does not imply a director - this is most
of
SOA)
* Emergent (Group behavior emerges from common traits or
behavior of
individual - this is most of "nature")

 

Contracted behavior is a very human thing that we have now imparted
to our
machines.  Our machines previously required directed
behavior (the "workflow
manager" instead of SOA contracts).

 

Emergent behavior - such as can be seen in an ant colony, is
very
interesting and what some of the agent community has
explored.  However
emergent behavior does imply some shared
environment or (probably
contracted) method of exchanging
information - perhaps more as event
notifications.  But in the
emergent case there is much less agreement but
there is some level
of common behavior.  Emergent behavior probably comes
from some
kind of evolution.

 

SOA can support all 3 kinds of behavior, but the very common case
of
creating and meeting obligations (from commerce to fire a
missile) is
generally contracted behavior.

-------- Original Message --------
Subject: Re:
[ebsoa] Groups - Work breakdown and schedule draft (ebSOA 
Task
Breakdown and Draft   Deliverables Schedule.doc) uploaded
From:

Date: Fri, March 31, 2006 2:09 am
To:


David,

Resending the mail, as one
sentence in line 5 was sent
incomplete.

******************

There seem to be
replication of capabilities and characteristics between

a.
   Internal collaboration oriented processes and enterprise
information
integration processes.

Also may help in
specifying

a.    What is the difference between
interface and integration (Atleast
from the SOA perspective.
Especially because the ebsoa spec defines areas
of interface -
gateway specification which includes multiple interface
mechanisms
like web service intermediation, MQ, Direct
communication,
broker-feed mode, etc )?

b.    How
the internal collaboration oriented processes defined by EBSOA
are
going to co- exist with the existing message driven solutions
that
exists in the market or what are the reasons one should look at
them?

The vision/ any other relevant document may choose to
define it.

******************
P.S-> Parallel work done on
ebpp and the proposed work on semantic web (In
relevance to
collaboration profile work specified by Goren) also may be
looked
at.

Regards

POLARIS, THE LEADER IN SPECIALITY
APPLICATION DEVELOPMENT
:
-------------------------------------------------------------

Polaris
has been awarded the Leader in the category of "Speciality Application
Development" among the Top 100 global Companies from Cyber Media
Publications for the Year
2006.

--------------------------------------------------------------

This
e-Mail may contain proprietary and confidential information and is sent
for the intended recipient(s) only. 
If by an addressing or
transmission error this mail has been misdirected to you, you are
requested to delete this mail immediately.
You are also hereby
notified that any use, any form of reproduction, dissemination,
copying, disclosure, modification,
distribution and/or publication
of this e-mail message, contents or its attachment other than by its
intended recipient/s is strictly prohibited.

Visit Us at
http://www.polaris.co.in