<span style='font-size:
10.0pt;font-family:Arial;color:navy'>Yours is the best description I've
seen so far, Michael.   IMO, it has much to do with understanding for
the procurement side of systems evolution where one sees descriptions of
services to be procured versus data to be provided as part of that
service.   The data may include a finite or open ended set of kinds
and types where the service is a single line item from the point of view of the
procurement.   That is why, I believe, when reading RFPs and RFIs I see
SOA far more often than ROA.

<span style='font-size:
10.0pt;font-family:Arial;color:navy'> 

<span style='font-size:
10.0pt;font-family:Arial;color:navy'>len

<span style='font-size:
10.0pt;font-family:Arial;color:navy'> 





From: Michael Champion
[mailto:mc@x...] 









But maybe it wouldn't be too much to hope that we
could all just get along by understanding that when a system is best
conceptualized as a set of services, service-oriented technologies make a lot
of sense ... and when a system is best conceptualized as a hyperlinked web of
resources, REST technologies make a lot of sense.  Of course, whether
a proposed application is best conceptualized as a ROA or SOA is
going to be an interesting discussion for the designers to have.





 





This email and any files transmitted with it are confidential and intended solely for the use of the individual or entity to whom they are addressed. If you have received this email in error please notify the sender. This message contains confidential information and is intended only for the individual named. If you are not the named addressee you should not disseminate, distribute or copy this e-mail.