Keith Moore wrote:
On the other hand, if you are trying to define a standard interface to a
service that modifies content in arbitrary ways, and particularly one that
is usable on either the client or the server end, I suspect that it would be
a poor design choice to base OPES on top of HTTP.
Not sure whether there's a misunderstanding - the proposed OPES work
is NOT based on top of HTTP. It is meant that OPES, in a first step,
would focus on services for HTTP-based transactions (and possible
other protocols later on). This does NOT mean that the protocols to be
worked on would be based on top of HTTP.