Re: [soa-rm-ra] Disambiguating Action (Part I) - Take 2

Michael,

The service is more than the interface because access is more than the door you go through to get to the capability.

The service has a role in understanding and responding to the initiating message, including understanding and acting appropriately with regard to identified policies.  It may make use of other services in doing this, and thus acts as both a provider and consumer.  In an orchestration or choreography, it will have a role in following the defined process or responding to events during the process.  However, most of this is not seen by the consumer whose interest is in the functionality being provided (but the consumer doesn't know how) and the real world effects realized.

Ken

On May 28, 2008, at 11:43 AM,  wrote:

I think I have an explanation why Capability is a resource and why it exists on its own outside of SOA:

     Service is seemed as an interface, nothing more. 

In this case, ANYTHING that could be done through the interface (i.e. by the service) may be done by a resource only. Plus, resource, certainly, exists outside of such service

I am looking for this standard to finally move from the service=interface concept and we did a lot in this direction already. 

If we accept that a service has its own business value besides interfaces (service actions, e.g.), then service can act by itself instead of a resource, at least, in some cases. That is, my definition of Capability (which includes service) is valid.

- Michael
 

 

 
------------------------------------------------------------------------------------------
 
Ken Laskey
 
MITRE Corporation, M/S H305     phone:  703-983-7934
 
7515 Colshire Drive                        fax:        703-983-1379
 
McLean VA 22102-7508