Difference between revisions of "rest/json"

From Microformats Wiki
Jump to navigation Jump to search
(→‎Charter: query)
Line 18: Line 18:
 
# allows paging and/or partial returns of large datasets
 
# allows paging and/or partial returns of large datasets
 
# standardizes linking to related resources
 
# standardizes linking to related resources
# use of hypermedia (links + context) to manage application state  
+
# defines a generic query syntax
 +
# uses hypermedia (links + context) to manage application state  
 
# does NOT become a full-fledged [http://hideoustriumph.wordpress.com/2008/05/05/ws-deathstar-for-the-rest-of-us/ RPC] solution
 
# does NOT become a full-fledged [http://hideoustriumph.wordpress.com/2008/05/05/ws-deathstar-for-the-rest-of-us/ RPC] solution
  

Revision as of 04:35, 13 September 2008

RESTful JSON

Charter

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

that:

  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. defines a generic query syntax
  6. uses hypermedia (links + context) to manage application state
  7. does NOT become a full-fledged RPC solution

Resources

Proposals

Issues

  • Is the top-level entity a simple array (Persevere, Dojo) or a full-fledged object (CouchDB, ActiveRecord?)

Implementations