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


Help: OASIS Mailing Lists Help | MarkMail Help

ebsoa message

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

Subject: RE: [ebsoa] events and agents as defined in an ebSOA

I have been looking at JXTA as a middleware peering discovery management
mechanism for Asterisk the open source IP PBX. JXTA is available from
Verizon and I have heard that Telenor and some other northern European
telcos have incorporated a security model on top of JXTA.  Anybody know of
these links. 

I don't know why we got off on the discussion of the implementation
language. We should just be sending a declarative logic description of the
service contract(policy and contract-- BPSS 3.0?) (XML? Or OWL?) to the
agent ecosystem.  I think this is where the FERA CPIM comes into play.

Verizon JXTA service for $14.95 a month.

You can provide the same services and epr functionality on Asterisk IP PBX
offering enterprise level email with collaboration and federation support
over VOIP with team specific collaboration presence, discovery, and role
based availability.  Eventually they will figure out how to add services on
top of this generic infrastructure service.  Maybe they will look to


-----Original Message-----
From: john c hardin [mailto:johnchardin@comcast.net] 
Sent: Monday, May 09, 2005 2:46 PM
To: David Webber (XML)
Cc: john@crossconnections.ws; Dan Pattyn; vasco.drecun@cpd-associates.com;
Goran Zugic; Dale Castle; ebSOA OASIS TC; richard.manning@sun.com;
Subject: Re: [ebsoa] events and agents as defined in an ebSOA

Understood David, thank you. I was suggesting that we use applicable
"concepts" from the JXTA projects, not the actual implementation. Obviously,

JXTA could be implemented as an agent framework if the implementer chose to
do so.

I just wanted to make sure that we get a well-rounded picture of agent

David Webber (XML) wrote:
> John,
> 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
> classical
> declarative logic processing - and can be expressed as XML structures -
> 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*
> That I believe is where traditionally OASIS can look to make a significant
> contribution...
> DW
> ----- Original Message ----- 
> From: "john c hardin" <johnchardin@comcast.net>
> To: <john@crossconnections.ws>
> Cc: "Dan Pattyn" <danpattyn@austin.rr.com>; "David RR Webber"
> <david@drrw.info>; <vasco.drecun@cpd-associates.com>; "Goran Zugic"
> <gzugic@ebxmlsoft.com>; "Dale Castle" <dcastle@ebxmlsoft.com>; "ebSOA
> TC" <ebsoa@lists.oasis-open.org>; <richard.manning@sun.com>;
> <discuss@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
>>>- Possibly including JXTA concepts, where possible, as they describe
>>>peering between components and applications.
>>>- 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
>>313.279.1377 new *VONAGE* number
>>"The new electronic interdependence recreates the world in the image of a
> global
>>     Marshall McLuhan, "Gutenberg Galaxy", 1962

john c hardin
Chair, OASIS ebSOA Technical Committee
313.279.1377 new *VONAGE* number

"The new electronic interdependence recreates the world in the image of a

     Marshall McLuhan, "Gutenberg Galaxy", 1962

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