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

 


Help: OASIS Mailing Lists Help | MarkMail Help

soa-rm message

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


Subject: RE: [soa-rm] Proposal for Sub Committee


Title: [soa-rm] Proposal for Sub Committee
Just like to say that I'm definately keen on being involved with this.
 
Steve


From: Duane Nickull [mailto:dnickull@adobe.com]
Sent: Wed 08/02/2006 16:56
To: soa-rm@lists.oasis-open.org
Subject: [soa-rm] Proposal for Sub Committee


-----Original Message-----
From: Frank McCabe [mailto:frank.mccabe@us.fujitsu.com]
Sent: Wednesday, February 01, 2006 10:15 AM
To: SOA-RM
Subject: [soa-rm] [soa-ra] Notes from telcon on 2/1/06

Since this was not an official formal meeting, we did not take formal 
official minutes :)

However, a summary of the results of the meeting is:

Attendees:

Theo Beack
Duane Nickull
Joe Chiusano
Michael Stiefel
Al Brown
Danny Thornton
Greg Kohring
Ken Laskey
Jeff Estefan
Frank McCabe

The name of the new committee will be: The OASIS Service Oriented 
Architecture Reference Architecture Sub-TC

The purpose will be: To develop one or more Reference Architectures 
for SOA based on the current SOA RM (versions 1 and later as 
appropriate).

The deliverables will be: One or more specification documents 
containing descriptions of the Reference Architecture(s).

The chair will be: Frank McCabe

Process:

We will use an official OASIS email list, together with a WIKI and a 
folder in KAVI for documents and other artifacts associated with the 
work.
We will have regular telephone conferences, alternating with the SOA 
RM TC every other week. (I.e. every other Wednesday, on those weeks 
where the SOA RM TC is not meeting)

Technical Discussions:

There was a wide ranging discussion about many topics; including 
issues about the scope of the RA, whether it includes POA, BPM etc. 
how concrete it should be, whether issues involving migration from 
stovepipe systems to service markets was included, and so on.

There was some thought about what an Reference Architecture actually 
is. This will probably evolve some, but in essence it seems that it 
is an architectural design pattern; with, of course, a focus for us 
on architecting SOAs.

We will need to evolve a set of requirements. This process will be 
critical in determining if we need more than one RA.

This message contains information that may be privileged or confidential and is the property of the Capgemini Group. It is intended only for the person to whom it is addressed. If you are not the intended recipient, you are not authorized to read, print, retain, copy, disseminate, distribute, or use this message or any part thereof. If you receive this message in error, please notify the sender immediately and delete all copies of this message.



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