I agree, its what I've regularly argued. Service provides the mechanism for interaction, not the bit behind the scenes, hence the reason that process is subservient to service. So I might be saying service is slightly more (i.e. it provides the ability to interact) but I'm certainly not saying that service is the implementation.
Steve On 17/06/07, Sebastian Stein <[EMAIL PROTECTED]> wrote:
Steve Jones <[EMAIL PROTECTED] <jones.steveg%40gmail.com>> [070617 10:31]: > Why isn't Customer Service a Service from an SOA perspective (it is for me) > it has a set of capabilities that demonstrate a real world effect and the > service provides the mechanism for accessing those capabilities. So > Customer Service is certainly a service that complies with the OASIS SOA RM. Our first idea was also to view SOA services as products. But a service is defined as a mechanism bringing together needs and capabilities. There are usually different ways to implement a service with different products. My personal example goes as follows: You want to rent a car for a business trip. Your secretary, your travel agency or a booking terminal at an airport can do this for you. From an abstract perspective, they all provide the same service to you. In case of SOA, you have to abstract from these concrete implementations. The SOA service just covers what the implementations (or realisations) have in common (the capabilities), but it is not the implementation itself. Regards, Sebastian
