Where at all possible, I want a true REST interface. I recognize that
sometimes you need to use POST to send data, but I've found it very helpful
to be able to craft URLs that can be shared that contain a complete request.

Ralph

On Tue, Jul 19, 2011 at 11:22 AM, Devon <[log in to unmask]> wrote:

> I'm getting ready to write a REST interface to OCLC's crosswalking
> system. My problem is that I'm not convinced developers actually want
> a textbook REST interface. I have a hunch that most developers really
> just want a non-SOAP url they can POST to with a crosswalked version
> returned in the response body.
>
> Given the classifications here [1], I was wondering if people could
> give some feedback about what interface type they'd actually want to
> use, what might be too much effort to use, and what they're sure they
> don't want.
>
> Thanks,
> Devon
>
> [1] http://www.nordsc.com/ext/classification_of_http_based_apis.html
>
> --
> Devon Smith
> Consulting Software Engineer
> OCLC Research
> http://www.oclc.org/research/people/smith.htm
>