If the web is become an infrastructure for global computing rather than only for global human browsing, and if it is to be easily extended with objects of a plethora of types, it would be a major step backward were the power of OOP to be excluded by virtue of the web protocol design. However, within the OOP world, there are many different models. In what the web does, it does in a very flexible way. Format negotiation allows data formats to introduced smoothly over time, and the URI format allows new protocols to be introduced over time. The web puts as few constraints as possible on anything, defining the minimum amount for interoperability.
Applications can interact to the limit of the concepts which they share.
The challenge is to make an OO WWW which does not force one to buy into one OO model. OO systems vary in their typing models, their inheritance models. Distributed OO systems vary in their models for asynchronous invokation of methods. I propose the following general requirements. The ability to interogate a remote object as to the interfaces which it supports, with a format negotiation in which the response is sent.