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: conf. call reminder and tech arch notes

ebSOA'ers -
This is a reminder of the upcoming 3PM EST conf call - 712-824-4400 Participant 
Access Code 44999.

I have also attached my notes on changes to the Tech Arch - including how we 
should approach the editing. In other words, I believe that we should first 
determine the standards that have been ratified since the Feb 2001 publishing of 
the v1.04 architecture, which bring SOA capabilities to the set of standards.

I would like each of you (specifically the editors) to add to or edit this set 
of notes, which I will work into a project plan for editing the document. We use 
  these notes as starter for the discussion today.

thanks -

john c hardin
CIO - crossconnections.ws
313.930.5323 cell

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

     Marshall McLuhan, "Gutenberg Galaxy", 1962


Section A. Home Page Revision
Change Group Description from: 

"Advancing architectural patterns for using Service Oriented Architecture in electronic business"


"Delivering Service Oriented Architecture framework composition guidelines, and accompanying technical specifications."

Section B. Charter Revision

Statement of Purpose: 

To provide an updated normative technical architecture specification illustrating the composition of e-Business Service Oriented Architectures through the use of the various specifications ratified by OASIS, including Web Services and ebXML based technologies. To provide a set of high-level usage guidelines accompanying the technical architecture specification, with the purpose of illustrating the features and benefits of e-Business Service Oriented Architectures based on OASIS specifications, for managers and project teams. To facilitate discussion and evolution of architectural models for SOA's. 

Scope - no changes  

Section C. Technical Architecture Revision Notes

Service Oriented Architectures are currently, and may always, evolve to encompass new technologies and new functions. The ebXML specifications (ebMS, CPPA, Reg/Rep and BPSS), when used to create an e-Business framework, deliver a stable SOA. The ebXML Technical Architecture Specification v1.04 document was last revised in February 2001, and requires updates to reflect the latest stable specifications, and usage. 

C.1 Version: update version number to 2.0

C.2 Determine the applicability of SOA related OASIS standards ratified since TA v1.04 was published:

	C.2.1  ebXML Message Service v2.0 / v3.0
	C.2.2  ebXML Registry Services Specification v2.0
	C.2.3  ebXML CPPA v2.0
	C.2.4  SAML v2.0
	C.2.5  XACML v1.0 
	C.2.6  WSS 
	C.2.7	 WS-Reliability v1.1
	C.2.8  UDDI v2
	C.2.9  SPML v1.0
	C.2.10 DSML v2.0
	C.2.11 WSDM v1.0

Edit all sections according to new capabilities. 

C.3 Throughout document: 

Diagrams - update with UML diagrams throughout, specifically package, sequence and activity diagrams to illustrate the usage of the various components and interactions between those components. 

Edit to update the version numbers of all referenced specifications (eg: ebMS 2.0)

C.4  Section revisions: 

- - TA Section 4.1 Problem Description and goals - -

Add descriptions of Service Oriented Architecture advances in modern IT architectures.

Add information describing the solution to these problems as a Service Oriented Architecture framework. 

Include updated language depicting the usage of ebXML specifications as the components of a service oriented arch-itecture. 

- - TA Section 8 ebXML Infrastructure - - 

Based on decisions re: the newly ratified standards (C.2 above), addition of new sections describing the functions of the standard, detailing the architecture and relating these details to other functions listed in section 8. 

Update section 8.2 with BPSS v2.0 capabilities

Update Appendixes to reflect increased functionality of later versions. 

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