RE: Use case comparison of REST & Web services

>What's the exact syntax for the URI to specify the *specific* bits of
information that my program needs (e.g., the team)? 

Instead of putting it in the URL, that could be part of the document I send
(same thing if I take the message-oriented web service approach).

> What's the actual schema (broadly defined) of the result?  

Couldn't that be derived from namespace(s) information embedded in the XML
document returned?

> How would my program find the specific information it needs in the
response?  

The namespace(s) embedded in the response should point to the related
schema(s). (Some people will certainly disagree, but I always thought that
namespaces and schemas should be closely related). Based on that information
my program will parse the information in the response and might (or might
not) be able to make sense of the parsed information (but that should not be
that different from a WSDL file giving me some parameter names and type
information, in the RPC style, or some schema information, in the message
style).

Ugo