The problem with OPTIONS is it doesn't describe anything about the data the resource returns.
I really wish there was a DESCRIBE verb that would return a structure of what is expected to be received/sent.
Then microformats could spring up around datatypes returned by DESCRIBE. This is of course very XML.
Edit: This would also allow for automatic discovery of new APIs.
Re:Stop Writing REST API Clients
by steveklabnik on Sunday February 24, 2013 @09:10PM
(#5276916)
That's what resources that have form-style affordances offer. See, for example, Collection+JSON.
REST means more than just GET, POST, PUT, DELETE.
Some may make the excuse that call OPTIONS /path isn't straightforward, but I have no clue how you could get more obvious than that.