Re: [ebxml-jc] Durand 5/24/2005: ebMS v3.0 Packaging and MessagingModel

[john c hardin <johnchardin@comcast.net>]

Dear Monica and JC members,
Here are my *preliminary* notes on the TA v2.0 outline for the White Paper. This 
will shift as we incorporate a deeper level of detail and probably add some 
components.

Monica,
This is still very preliminary, as we have had some time issues coordinating the 
input material, presentations about the input material (so we

could understand it properly) and then getting a statement about IPR intentions 
from those donating the material. Given that, however, I

believe that we can reasonably expect that we will have the following components 
specified in the TA, and therefore descriptions should be in

the white paper:

x. Introduction
x.1 - Overview
x.2 Status of Standards
       2.1 Technical Architecture v1.0
       2.2 Technical Architecture v2.0
x.3 Current Features
3.1 Service Oriented Architecture Features
3.1.1  Transport (ebXML Message Service v3.0 - SOAP w/ Attachments, etc.)
3.1.2  Message Reliability (WS-Reliability and ebMS)
3.1.3  Registry / Repository  (ebXML Registry / Repository v3.0)
3.1.4  Party Agreement (ebXML CPPA v2.0)
3.1.5  Business Process Specification, Execution or Choreography  (ebXML BPSS 
v2.0 and BPEL) ** not sure how to reconcile these as working together **
3.1.6  Integration Interface Metadata (WSDL and other metadata held in ebXML 
reg/rep)
3.1.7  Security and Identity Architecture (Dig Sig, SAML, XACML, XML Encryption
3.1.8  Message Format and Metadata (XML, Schema, CCTS)
3.1.9  Service Management (WSDM)
3.1.10 Service Provider (SOA RM detail)
3.1.11 Service Consumer (SOA RM detail)
x.4 Future Plans
-  Overview
-  Feature Set (overview)
4.1 Federation of Registries
4.2 Discovery and Negotiation
4.3 Agent Framework
4.4 Event Architecture and Messaging
-  Relationship to other specifications and standards
x.5 Business scenario example
x.6 References and materials


Monica J Martin wrote:
> Jacques,
> Perhaps we should discuss in more detail v3.0 ebMS plans for packaging 
> and messaging. I would like to touch specifically on 
> conversation/transaction identifierw and the signal packaging that is 
> proposed, and the assumptions around support for process specifications 
> (this has a 2-way effect). Thanks.
> 
> Reference: ebMS Messaging Model update: 
> http://www.oasis-open.org/apps/org/workgroup/ebxml-msg/document.php?document_id=12653 
> 
> (Not publicly available).
> 
> 
> ---------------------------------------------------------------------
> To unsubscribe from this mail list, you must leave the OASIS TC that
> generates this mail.  You may a link to this group and all your TCs in 
> OASIS
> at:
> https://www.oasis-open.org/apps/org/workgroup/portal/my_workgroups.php
> 
> 

-- 
~~~~~~~~~
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:john@crossconnections.ws

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

     Marshall McLuhan, "Gutenberg Galaxy", 1962