I am not sure exposing the service contracts that exist right now really would get us a huge advantage. I guess that depends on which bits of OpenACS need to interoperate.
For example, service contracts in WebDAV really shouldn't be exposed. Its just an API to map WebDAV methods to objects. If you had a need to connect externally to WebDAV, you would just use the WebDAV protocol.
I think it would be a great idea to figure out what sort of functionality it makes sense to offer as a web service and find a way to implement that. I know that acs service contracts were designed originally based partly on WDSL for web services.
Lately we have found that the actualy _use_ of service contracts inside OpenACS really lends itself more to the recently added callback system. Service contracts might be a good idea for web services, but for inter-package communication the callback feature is simpler and easier to work with, while still providing all the functionaly we have been using.
