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] When Is An SOA Really An SOA?


Title: Re: [soa-rm] When Is An SOA Really An SOA?
Hmmm....let me see if I understand this:
 
So if someone has something that meets the definition of SOA on line 470, they should be able to look at our RM and see if it is conformant with our Figure 1 - which means that we in effect are defining a subset of what they really need for SOA; otherwise we would be defining something that would meet the definition of SOA on line 470.
 
Is that correct? If so, what are we really defining then? A service orientation RM perhaps (i.e. SO-RM not SOA-RM)?
 
Joe
 

Joseph Chiusano

Booz Allen Hamilton

Visit us online@ http://www.boozallen.com



From: Duane Nickull [mailto:dnickull@adobe.com]
Sent: Thu 5/5/2005 1:06 PM
To: Chiusano Joseph
Cc: soa-rm@lists.oasis-open.org
Subject: Re: [soa-rm] When Is An SOA Really An SOA?

Joseph:

This is a key aspect of why we are doing this exercise.  We have a
section (placeholder) called conformance but at this point it is not
clear if we could (or should) make a blanket statement.  At the face to
face, the thinking was more in tune with what it would mean if someone
stated their SOA was conformant with the SOA RM.

Duane

Chiusano Joseph wrote:

> This question has been on my mind for quite some time, and I would
> like now to put it in the context of our in-process RM.

> In the past, I have pondered the following more specific question
> (please note that this is all scoped to Web Services-based SOA for
> ease of explanation):

> If I have 2 Web Services that communicate, do I have an SOA?

> We can say "certainly not!". One can do point-to-point integration
> with Web Services just as easily (to a certain degree) as without,
> with redundant Web Services rather than shared Web Services (a
> violation of one of the foundational tenets of SOA, which is shared
> services).

> Now let's say that we have 2 Web Services that each conform to the SOA
> Architectural Model in Figure 1 of our most recent draft. There is a
> data model, a policy, a contract, etc.

> Add to that our definition of SOA on line 470, in which we (correctly)
> state that SOA is a form of Enterprise Architecture, which (at least
> in my mind) implies enterprise-level benefits.

> Q: Given the last scenario above (2 Web Services that each conform to
> the SOA Architectural Model ) and our definition of SOA: Is this
> scenario large-scale enough that it *really* meets our definition?
> IOW, how large-scale does an "instance" that conforms to our RM have
> to be to yield benefits on an enterprise scale? Do we need to
> stipulate something regarding this for our RM?

> Joe

>
> Joseph Chiusano
>
> Booz Allen Hamilton
>
> Visit us online@ http://www.boozallen.com <http://www.boozallen.com/>
>




--
***********
Senior Standards Strategist - Adobe Systems, Inc. - http://www.adobe.com
Chair - OASIS Service Oriented Architecture Reference Model Technical Committee -
http://www.oasis-open.org/committees/tc_home.php?wg_abbrev=soa-rm
Vice Chair - UN/CEFACT Bureau Plenary - http://www.unece.org/cefact/
Adobe Enterprise Developer Resources  - http://www.adobe.com/enterprise/developer/main.html
***********



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