I just published a full featured use case of using WSDL 2.0 HTTP Binding to describe a Music service. This is my best attempt at describing a use case using WSDL. It shows how to use WSDL for describing RESTful applications, and a significant number of design issues and shortcomings.
I had orginally posted it to the WSDL WG mailing list, but it got so long and big that I thought it deserved it's own HTML formatting and a web page. Any comments from WSDL WG, REST-discuss, WebDAV, WS-ResourceFramework, Atom, or other folks would be appreciated.
If I had oodles of spare time, I'd probably take a stab at modelling Atom using WSDL 2.0. In fact, I think it would be fun to use Atom as the official use case and scenario for WSDL 2.0. But that probably won't happen for a large # of reasons.
I think this kind of sucks to be blunt. I have some rough ideas about a more full featured XML to URI binding that would be simpler than the current x-www-uri-formencoded example, but I've run into a few problems.
