|john c hardin||May 9, 2005 11:33 am||.ppt|
|john c hardin||May 9, 2005 11:48 am|
|David Webber (XML)||May 9, 2005 12:14 pm|
|john c hardin||May 9, 2005 12:45 pm|
|Richard Manning||May 9, 2005 4:29 pm|
|David Webber (XML)||May 10, 2005 6:51 am|
|Dan Pattyn||May 11, 2005 8:07 am|
|Goran Zugic||May 11, 2005 4:16 pm|
|Carl Mattocks||May 12, 2005 7:15 am|
|Goran Zugic||May 12, 2005 9:20 pm|
|David Webber (XML)||May 13, 2005 9:02 am|
|Subject:||Re: [ebsoa] events and agents as defined in an ebSOA|
|From:||David Webber (XML) (dav...@drrw.info)|
|Date:||May 9, 2005 12:14:35 pm|
The caveat I have is simple - the design of ebSOA should be implementation language neutral.
That is the whole point behind the BCM linking and switching - its based on classical declarative logic processing - and can be expressed as XML structures - that can then be read and processed by any agent engine.
There are literally 100 different agent engines out there - all with their own proprietary syntan and API - (even if they are written in Java - or maybe especially if they are written in Java!).
What the world does not have is a common method of integrating *all* these. That I believe is where traditionally OASIS can look to make a significant contribution...
----- Original Message ----- From: "john c hardin" <john...@comcast.net> To: <jo...@crossconnections.ws> Cc: "Dan Pattyn" <danp...@austin.rr.com>; "David RR Webber" <dav...@drrw.info>; <vasc...@cpd-associates.com>; "Goran Zugic" <gzu...@ebxmlsoft.com>; "Dale Castle" <dcas...@ebxmlsoft.com>; "ebSOA OASIS TC" <ebs...@lists.oasis-open.org>; <rich...@sun.com>; <disc...@jxta.org> Sent: Monday, May 09, 2005 2:48 PM Subject: Re: [ebsoa] events and agents as defined in an ebSOA
Richard Manning from Sun Microsystems presented on JXTA at the 2004 Symposium. Slides are found at:
john c hardin wrote:
I would like to start a conversation on the list re: the agent architecture, as proposed in the Federated Enterprise Reference Architecture approach.
Thanks to Goran, Vasco and the ebXMLsoft team for creating the presentation attached, and to David Webber and Dan Pattyn for pointing me to the BCM material.
I think that there are several inputs that we can include to round out the ideas of a non-intrusive, event-driven agent model. Opinions are requested from the group on these, and preferences for how to specify the agent mechanisms using a combination of the approaches here:
- The Agent Framework is described in the attached BCM / FERA presentation. There is a lot of good material here, however, we need to make sure that we are re-using stable OASIS specs where possible. I would like to map the specifications mentioned in the presentation to the existing specs.
- The BCM Linking and Switching as a mechanism to bind to the agent framework
- Possibly including JXTA concepts, where possible, as they describe peering between components and applications. http://www.jxta.org/JXTAFAQ.html
- Complex Event Processing, using the concepts outlined by David Luckham: From http://www.complexevents.com/
Complex Event Processing (CEP) is an emerging technology for building and managing information systems including:
* Business Activity Monitoring * Business Process Management * Enterprise Application Integration * Event-Driven Architectures * Application Servers and Middleware * Network and Systems Security
-- ~~~~~~~~~ john c hardin Chair, OASIS ebSOA Technical Committee http://www.oasis-open.org/committees/tc_home.php?wg_abbrev=ebsoa 313.279.1377 new *VONAGE* number mailto:jo...@crossconnections.ws
"The new electronic interdependence recreates the world in the image of a global village."
Marshall McLuhan, "Gutenberg Galaxy", 1962