It is arguable that the client has the right to have whatever adpatation
they want performed on the content that they view. However, it enters into
a troublesome area where we obscure what exactly is being provided by the
content provider, although the identity of the content provider is still
used.
Micah,
It appears as if you're assuming that the OPES interface has to interpose
that adaptation between the provider and the audience, by usurping
the normal client-to-server interface and obscuring the original content -
probably by some sort of HTTP proxy. I don't think this is a reasonable
assumption, or a reasonable design constraint. In fact I would argue
that it is essential that the normal client-to-server interface not be
interfered with, precisely so that the audience has a choice - exposed
in his user interface - regarding whether to enable a particular translation.
For this and several other reasons OPES should defintely NOT be based on HTTP.
Keith