Michael Kay wrote:

>I think web services were driven more by the need to deliver XML data to
>applications that carry out business logic using the data, rather than
>merely doing presentation. People who only want to do presentation have
>largely found that HTTP is sufficient. But that's just one view...
>  
>
+1 to this view,

I would think that the primary use case *currently* for web services
adoption is dealing with enterprise level integration where there are
plenty of suppliers with plenty of heterogeneous systems and
software...all set within a more closed 'extranet' type environment.
They are not being driven at the 'web' layer where 80% of us live,
though things such as REST are growing up from the grassroots and things
such as WS* are growing down, hopefully they will meet up.

the next primary selection characteristics for web services (for the
future) would be;

- perform software to software integration, underpinning true machine to
machine collaboration (e.g. along with commodisation it brings)

- application composition enabled using real time service discovery and
inspection

as for seperation of content and presentation...not sure if perhaps its
confusing to use the term presentation where 'interface' would do, along
with 'content' where 'data' would....slight differences in semantics
though implying that a human is involved in one whereas it is not in the
other.

cheers, Jim Fuller