--- In [email protected], Michael Poulin <[EMAIL PROTECTED]> wrote: > > After talking to many people in OASIS SOA RM and RA, I believe > that "service" in the SOA sense" is not necessary a business > service.
I believe we already agreed on the applicability of "service" to different levels--and that we just need to be clear. > What is wrong, even from a business perspective, with > creation of new/another view on the Client Business Data model > (provided by a data transformation service)? IMO, a "Client Business Data model" is not a service. It is data. Or a view of data. And that's data oriented, not service oriented. Putting an access wrapper around data does not make a service. > This view has a well reasonable meaning for the business - I'm > talking about single Client Business Data model represented as a > different sub-views to different business interfaces/channels. IMO, data views are not services. A service and its operations decidedly support data models and views, but as covered earlier in this long-lived and morphing thread, data access is not the primary focus of a service IMO. Data models and subviews are a by-product of proper service defintions. The focus of services is to provide access to capabilities and behavior, not data. -Rob
