Difference between revisions of "rest/json"

From Microformats Wiki
Jump to navigation Jump to search
Line 22: Line 22:
== Resources ==
== Resources ==
* [http://bitworking.org/news/restful_json Original proposal]
* [http://bitworking.org/news/restful_json Original proposal] by Joe Gregorio
* [http://www.json.com/2008/08/19/standardizing-restful-json/ Standardizing RESTful JSON] by Kris Zyp
* [http://groups.google.com/group/restful-json Google Group]
* [http://groups.google.com/group/restful-json Google Group]
* [AtomPub] (for comparison/inspiration)
* [http://tools.ietf.org/html/rfc5023 AtomPub] (for comparison/inspiration)
== Proposals ==
== Proposals ==

Revision as of 16:15, 4 September 2008



Given that:

  • REST is a powerful architecture for scalable web services
  • JSON is a lightweight container for exchanging data
  • AtomPub, while RESTful, requires XML documents with strict metadata requirements

The goal of the RESTful JSON project is to develop a series of conventions for:

  • URLs
  • HTTP methods
  • HTTP headers
  • JSON fields


  1. is maximally compatible with existing (RESTful, generic) clients
  2. enables partial updates
  3. allows paging and/or partial returns of large datasets
  4. standardizes linking to related resources
  5. use of hypermedia (links + context) to manage application state
  6. does NOT become a full-fledged RPC solution