--- In [email protected], Michael wrote: > > Kamen, we are talking about 2 things in here. > > 1. Satisfaction. I do not like this term because we are trying to deal with measurable things in SOA. 'Satisfaction' carries more connotation than 'need'. The latter represents concrete requirement. I think if a service meets requirements, its work is done well, we can control it. But we still do not know for sure that the customer is satisfied. This is simple semantic. > > 2. As of meta-data, I just tried to re-phrase (seems like with no success) Rob's explanation why an aggregation of data appears as a service in question - is it real SOA service or not. That is, we mostly agree that just retrieval a data with SQL expression from a database is not a service's but a data access component's work, it does not bring a RWE. At the same time, an aggregation of data via the same SQL, plus, aggregation business rules, brings concrete, new business value, i.e. the RWE. > > This is not about a user and its interest in meta-data. It is about what we consider a service in SOA. > > - Michael >
Michael I agree that satisfaction is not easy to measure but this is the final goal in many cases about 2: I agree that I did not understand completely the topic but my ideas can be extended to cover this case too: You are trying to outline your way of thinking and to align terms and code to it. Do you agree this time? By the way if you click reply it will be easier to track the conversation because the messages will be grouped better. Kamen
