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] RE: Service definition at nauseum


Sorry Michael,
I am with Rex on this one, I do not think you can separate service contract (policies) from description. They are integral part of description
 

From: mpoulin@usa.com [mpoulin@usa.com]
Sent: Friday, April 23, 2010 5:11 PM
To: rexb@starbourne.com; jeffrey.a.estefan@jpl.nasa.gov
Cc: soa-rm@lists.oasis-open.org
Subject: Re: [soa-rm] RE: Service definition at nauseum

Yes, Rex, it is fortunately indeed because 
"SOA Service offered a capability according to a contract." 
is simply incorrect: SOA Service offered a capability according to Service Description but executes them according to the Service Contract, IMO.

- Michael



-----Original Message-----
From: Rex Brooks <rexb@starbourne.com>
To: Estefan, Jeff A (3100) <jeffrey.a.estefan@jpl.nasa.gov>
Cc: soa-rm@lists.oasis-open.org <soa-rm@lists.oasis-open.org>
Sent: Fri, Apr 23, 2010 9:24 pm
Subject: Re: [soa-rm] RE: Service definition at nauseum

Well said Jeff, 
 
I ran into this in the DM2 meeting today when I gave a cut down version of this, saying that a SOA Service offered a capability according to a contract and then added that the details were contained in the service description but not necessarily revealed to an end user but might be to another service provider for use in a composition or aggregation. What was heard was "SOA Service offered a capability according to a contract." Fortunately Dave and I took on the Action Item to clarify that and a few other things, so we can convey our consensus. 
 
However the one sentence rule applies. 
 
Cheers, 
Rex 
 
Estefan, Jeff A (3100) wrote: 

> Frank, 

> Your right, however, the alternative would be to chunk up the formal > definition into separate sentences, which I would ordinarily be OK > with but clearly from our experience, the stakeholder community out > there ends up adopting a one sentence definition. For example, if we > simply defined a SOA service as a capability offered and stopped > there, nobody would get the essence of what services means in the > context of SOA. 

> There are some key elements to our *service* (in the context of SOA) > definition that it has to embody. One, is to articulate that a SOA > service IS a capability offered by a provider for a consumer. Second, > that access is provided using a prescribed *[service] interface* that > abstracts (or hides) the implementation details of the capability. And > finally, that it (the service) is exercised consistent with *contract* > and *policy *constraints* *as specified by its *[service] description*. 

> <SIDEBAR> The last sentence is a slight variation from my earlier > proposed definition and could be worded using slightly better English. > What I noticed missing from the original definition of service in the > RM was the notion of *contract* and it originally stated “…constraints > and policies…” and we know, of course, that contracts are key to ANY > service paradigm, and that both contracts and policies are just > specific types of constraints. If somebody could clean up the wording > a bit, that would be great. Maybe it’s OK as written above.</SIDEBAR> 

> I’m OK if we chunk these key characteristics of the definition for SOA > service into separate sentences but they MUST be articulated in such a > way that the collective whole constitutes the formal definition of > this very important core concept of the SOA paradigm. 

> Cheers! 

> - Jeff 

 
-- Rex Brooks 
President, CEO 
Starbourne Communications Design 
GeoAddress: 1361-A Addison 
Berkeley, CA 94702 
Tel: 510-898-0670 
 
--------------------------------------------------------------------- 
To unsubscribe from this mail list, you must leave the OASIS TC that 
generates this mail. Follow this link to all your TCs in OASIS at: 
https://www.oasis-open.org/apps/org/workgroup/portal/my_workgroups.php


The information contained in this communication may be CONFIDENTIAL and is intended only for the use of the recipient(s) named above. If you are not the intended recipient, you are hereby notified that any dissemination, distribution, or copying of this communication, or any of its contents, is strictly prohibited. If you have received this communication in error, please notify the sender and delete/destroy the original message and any copy of it from your computer or paper files.



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