Re: [JXTA discuss] RE: [ebsoa] events and agents as defined in an ebSOA

Dan Pattyn wrote:

>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. 
>
This work was done as part of the Market-Managed Peer-to-Peer Services 
(MMAPPS)
project lead by British Telecoms 
(http://www.tik.ee.ethz.ch/~gerke/publications/Ger04b.pdf)

>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.
>
Agree. This makes lot of sense.

>David Webber (XML) wrote:
>  
>
>>John,
>>
>>The caveat I have is simple - the design of ebSOA should be implementation
>>language
>>neutral.
>>
As a clarification, JXTA is defined as a *network protocol* 
specification, as TCP/IP.
Multiple implementations are available in different languages (C/C++, 
Java, Python, .Net).

>>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.
>
You may want to check Boeing's SOSCOE integrated platform. Boeing 
selected the JXTA Technology to provide the peer-to-peer (P2P) discovery 
service for the System of Systems Common Operating Environment (SOSCOE) 
for the U.S. Army's 15 billion dollar Future Combat Systems (FCS) 
initiative.

Hth,

B.

--http://weblogs.java.net/blog/tra
"As Java implies platform independence, and XML implies language
independence, JXTA implies network independence."


>  
>
>>That I believe is where traditionally OASIS can look to make a significant
>>contribution...
>>
>>DW
>>
>>----- Original Message ----- 
>>From: "john c hardin" <[email protected]>
>>To: <[email protected]>
>>Cc: "Dan Pattyn" <[email protected]>; "David RR Webber"
>><[email protected]>; <[email protected]>; "Goran Zugic"
>><[email protected]>; "Dale Castle" <[email protected]>; "ebSOA
>>    
>>
>OASIS
>  
>
>>TC" <[email protected]>; <[email protected]>;
>><[email protected]>
>>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:
>>>
>>>http://www.oasis-open.org/events/symposium/slides/manning.pdf
>>>
>>>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:[email protected]
>>>
>>>"The new electronic interdependence recreates the world in the image of a
>>>      
>>>
>>global
>>
>>    
>>
>>>village."
>>>
>>>    Marshall McLuhan, "Gutenberg Galaxy", 1962
>>>
>>>
>>>      
>>>
>>
>>
>>    
>>
>
>  
>