Rob, I even capitalised the service action name. A "Client Business Data" or "Single Customer View" are not services, they are RWE of the services.
I agree with you that just a data retrieval with an execution of an SQL statement is not a service - it is pure technical solution dictated by particular type of the data storage. BTW, do we consider an abstraction like a business data storage being a business thing? It seems that existance of business data model (which is very important business thing becuase it carries business information, knowledge, business treasure) w/o a definition of the place where this information materialises is a bit incomplete... At the same time, I think that an aggregation of business data according to business rules from different data sources may be accepted as a business service because it can provide new RWE unavailable via simple data retrieval. What do you think? - Michael ----- Original Message ---- From: Rob Eamon <[EMAIL PROTECTED]> To: [email protected] Sent: Thursday, June 26, 2008 11:11:48 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: > > 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 simply disagree. "Client Business Data" (or "Single Customer View") is a service? At the business level? I'm not convinced. > We should not forget that creation of a view on a data set may be > quite complex procedure based on many business rules; Complexity does not make a SQL query a service. I know you're referring to something more than just a SQL statement, but the gist is the same--a complex join and transformation of data might be useful as a shared component, but the relative complexity of the data read doesn't make it a business service (we're specifically debating whether this particular case of "Client Business Data model" is a business service, right?). > 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... :-) It doesn't. :-) -Rob
