WebService Design

[Ice]

All -

I just wanted to folks thoughts on what "ideal" webservice design is based
on their experiences taking into consideration the two observations (and any
others you may have) below:
1. Calls to webservices are still RPC-based i.e. explicit method names are
used e.g. "GetWeather" as opposed to generic "Send" with "function"
contained in the message sent.
2. Lack of clarity of what the request/response entities should be i.e.
strongly-typed objects, xmldocument taking into the consideration that the
"consumer" of the webservice may not be running in the CLR and also
considering things like method signature changes etc.

Thanks.

Ice