REST API Best Practices

The "eCollege Best Practices guide" under Resources looks good - that's what I want to see from a tutorial. But why is it only in PDF form? You have a website already, and I don't see any tricky layouts in the PDF - why not just put the text in HTML pages? That would lower the barrier of entry to starting reading, make the book easier to read on small screens by allowing you to adjust the page size and font size, make linking to the book easier, and probably have other benefits.

Is it really incredibly difficult to consume SOAP? I thought any language out there these days can generate the client code from the WSDL.

PUT is most-often utilized for update capabilities, The POST verb is most-often utilized for creation of new resources.

I was under impression people prefer to use POST for updates and PUT for inserts in their REST services...

Nice tutorial though, also a section on security problems and different approaches would be a good article to see there...