RE: [soa-rm] Initial draft of paper to explain OASIS SOA work to public

[<marchadr@wellsfargo.com>]

This is a good point Joe.
The WS-CAF definitions need to align at some point especially with the SOA Blueprints since it seems to be an implementation of a blueprint is some way.

- Dan

-----Original Message-----
From: Chiusano Joseph [mailto:chiusano_joseph@bah.com]
Sent: Wednesday, November 02, 2005 10:06 AM
To: Oleg Mikulinsky; Duane Nickull; Miko Matsumura;
soa-rm@lists.oasis-open.org; soa-blueprints@lists.oasis-open.org
Subject: RE: [soa-rm] Initial draft of paper to explain OASIS SOA work
to public


Thanks Oleg. Duane, can you please clarify whether or not this is
related to the "SOA Message" effort that we discussed on our SOA-RM call
today? I am not certain as this document references only 2 OASIS TCs
(SOA-RM and SOA Adoption Blueprints), whereas the description you
provided lead me to believe that the "SOA Message" effort would include
other TCs such as ebSOA, WS-CAF. Just want to make sure my associations
are correct.

Joe

Joseph Chiusano
Associate
Booz Allen Hamilton
 
700 13th St. NW
Washington, DC 20005
O: 202-508-6514  
C: 202-251-0731
Visit us online@ http://www.boozallen.com
 

> -----Original Message-----
> From: Oleg Mikulinsky [mailto:oleg.mikulinsky@weblayers.com] 
> Sent: Wednesday, November 02, 2005 12:09 PM
> To: Duane Nickull; Miko Matsumura; 
> soa-rm@lists.oasis-open.org; soa-blueprints@lists.oasis-open.org
> Subject: [soa-rm] Initial draft of paper to explain OASIS SOA 
> work to public
> 
>  
> Duane, Miko, 
> 
> Attached is version of the "Introduction to the OASIS SOA 
> work" that is ready for broader review.
> As I mention before the only Q/A I am not yet sure about is 
> the "Business Architecture document" Q/A. I would like to get 
> some feedback from the both TC's before we can vote this "in" 
> or "out" of the document.
> 
> Please send any additions or proposed changes to me to be 
> incorporated into the next versions.
> 
> 
> Regards,
> Oleg.
> 
> -----Original Message-----
> From: Duane Nickull [mailto:dnickull@adobe.com]
> Sent: Friday, October 14, 2005 11:16 AM
> To: Oleg Mikulinsky; Jones, Steve G; Miko Matsumura; Ken Laskey
> Subject: RE: Initial draft of paper to eplain OASIS SOA work to public
> 
> I concur with Oleg's assessment.  This can also be a living 
> document although both TC's should initially approve it.  I 
> would like to recommend that Oleg be the owner of this (sorry 
> to put you on the spot), being our official liaison. 
> 
> Oleg - if this is ready for our call next Wed, I would like 
> to place it on the agenda for approval.  Perhaps you can flag 
> the paragraphs that our TC needs to approve.  Thanks.
> 
> Best wishes
> 
> Duane
> 
> -----Original Message-----
> From: Oleg Mikulinsky [mailto:oleg.mikulinsky@weblayers.com]
> Sent: Friday, October 14, 2005 6:56 AM
> To: Jones, Steve G; Duane Nickull; Miko Matsumura; Ken Laskey
> Subject: RE: Initial draft of paper to eplain OASIS SOA work to public
> 
> Steve, 
> 
> I believe the latest version is the one that contains your edits. 
> 
> I have a few suggestions on the Business/Functional 
> Requirements of SOA Blueprints section and would like TC 
> chairs to comment on it.
> 
> 1. Business/Functional Requirements are outlined in the 
> current SOA-BP charter as integral part of the overall 
> implement able technical blueprint.
> 2. Contributed GeneriCo Blueprints have two documents: 
> "concepts" and "requirements specification". Concepts 
> document has a one pager Business requirements section. 
> Requirements specification has mostly functional requirements 
> mixed with technical implementation details. GeneriCo 
> "Disconnected Profile" does not have business requirements 
> section at all.
> 3. I think the charter stated that GeneriCo Blueprints will 
> become OASIS SOA-BP draft within 3 months period.
> 
> I see the merits for the Business Blueprints Steve is talking 
> about, however It would be quite difficult to accomplish this 
> even in a scope of the existing contribution and TC charter.
> 
> I would like to propose the following:
> 
> 1. Lets have a discussion and a formal vote in the SOA-BP TC on the
> subjects: "Is there a need to split the existing Generico BP 
> contributions to Business Blueprint and Technical blueprints 
> for us to release GeneriCo as a SOA-BP draft.
> 2. Until we have a consensus, I would like to limit Q&A 
> document to only the items clearly outlined by both BC 
> charters and existing FAQ sections. Regarding a need to 
> explain "What is the scope of Business/Functional 
> requirements on SOA-BP". I would like to have no more then a 
> paragraph for each without referencing "SOA Business 
> Blueprints" as this is not referenced in the charter or a current FAQ.
>  
> Regards,
> Oleg.
> 
> -----Original Message-----
> From: Jones, Steve G [mailto:steve.g.jones@capgemini.com]
> Sent: Friday, October 14, 2005 8:24 AM
> To: Duane Nickull; Miko Matsumura; Ken Laskey; Oleg Mikulinsky
> Subject: RE: Initial draft of paper to eplain OASIS SOA work to public
> 
> 
> What stage are we at now on the document, I'm going to update 
> the SOA Biz bits and I couldn't work out what was the latest version!
> 
> Steve
> 
> 
> > -----Original Message-----
> > From: Duane Nickull [mailto:dnickull@adobe.com]
> > Sent: 03 October 2005 19:54
> > To: Miko Matsumura; Ken Laskey; 
> oleg.mikulinsky@weblayers.com; Jones, 
> > Steve G
> > Subject: Initial draft of paper to eplain OASIS SOA work to public
> >
> 
> > Comments?
> >
> 
> > Duane
> >
> 
> > *******************************
> > Adobe Systems, Inc. - http://www.adobe.com Vice Chair - UN/CEFACT 
> > Chair - OASIS SOA Reference Model Technical Committee
> > *******************************
> 
> 
> 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.
> 
>