intertwingly

It’s just data

Standardizing RESTful JSON

Kris Zyp: The notes in this post are based on the behavior of server implementations of JSON REST including Persevere, CouchDB, GrassyKnowl, Amazon S3, and RoR’s ActiveResource, and on client implementations including Dojo, Jester, and Persevere JavaScript client.

It looks like Joe Gregorio may have started something.  Again.

I didn’t get more than a paragraph in before I scrolled down to the comments to see how quickly the subject of CouchDB came up.  +1 for a standardized approach.  I find that while CouchDB is stunningly effective most of the time, I think parts of the REST interface to it are occasionally bizarre and unexpected, especially the stuff related to calling views.  A community driven approach to figuring out how to interact with that sort of data store would likely be very beneficial.  Especially if it means multiple programs can all be easily integrated, or better yet, used interchangeably.

Posted by Bob Aman at
A community based effort like we had with Atompub would be excellent and quite beneficial. This is some good stuff.

Posted by James Snell at

Bob & James,

CouchDB, being part of the ASF, is a community driven project. If you feel you have something to contribute I encourage you to get involved and help shape it’s future.

Posted by Noah Slater at

RESTful JSON Followup and Mailing List

Wow, that kicked off a great discussion around RESTful JSON with lots of comments and blog posts from Robert Sayre , Sam Ruby , Kris Zyp , and Robert Brewer . The one thing I’ve learned is that my blog comment system is not the place to have a long...

Excerpt from BitWorking | Joe Gregorio at
Noah, yeah, I’m very familiar with CouchDB.  I was referring more to a community effort to standardize the kind of JSON REST APIs implemented by CouchDB.

Posted by James Snell at

Sam Ruby: Standardizing RESTful JSON

Sam Ruby: Standardizing RESTful JSON...

Excerpt from Paragon Adrift at