rest/json: Difference between revisions

From Microformats Wiki
Jump to navigation Jump to search
(: JSON Schema)
Line 38: Line 38:
* [ HyperJSON Path Expressions]
* [ HyperJSON Path Expressions]
* [ Generalized JSON Linking]
* [ Generalized JSON Linking]
* [ JSON Schema]

== Issues ==
== Issues ==

Revision as of 19:16, 12 November 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. defines a generic query syntax
  6. uses hypermedia (links + context) to manage application state
  7. does NOT become a full-fledged RPC solution




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