Oh, SOA RM and RA define "capability" as a resource ( which I do not like 
because it is confusing for English speaking people).

As of data and service, the Client Business Data model certainly not a service 
but CREATION of a view on Client Business Data model or creation of one view 
from another view IS the service. We should not forget that creation of a view 
on a data set may be quite complex procedure based on many business rules; the 
same relates to the transformation from one view into another view, IMO. In 
this case, we can say that the service provides 'transformation' behavior if it 
makes Rob happier... :-)

- Michael


----- Original Message ----
From: Rob Eamon <[EMAIL PROTECTED]>
To: [email protected]
Sent: Thursday, June 26, 2008 8:21:25 PM
Subject: [service-orientated-architecture] ESB/Intermediary in SOA (was Data 
services (was Re: Definition of SOA))


--- In service-orientated- architecture@ yahoogroups. com, 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

    


      

Reply via email to