This is very interesting. The idea and requirement between ease of use and full-REST implementation is definitely worth discussing. Two Points: * Consistency c

This is very interesting. The idea and requirement between ease of use and full-REST implementation is definitely worth discussing. Two Points: * Consistency could be very useful across web-services * Simplicity is exceptionally important If all API's were created with a 'full-REST implementation', that would comply with the need (Desire?) for consistency, however it would not necessarily be easier. What might be "hard": * Some limitations (firewalls, lack of knowledge) on PUT and DELETE * The debate on when to use PUT and DELETE * Editing headers to request content type (xml vs json etc) So the big question seems to be: What is the mix between consistency and ease of use? Perhaps we can be full-on REST but then make it easier with code libraries?