rest/json: Difference between revisions
Jump to navigation
Jump to search
(marked as draft) |
|||
Line 3: | Line 3: | ||
== Charter == | == Charter == | ||
[Initial Draft by [[User:DrErnie|Dr. Ernie]] 12:55, 2 Sep 2008 (PDT)] | ''[Initial Draft by [[User:DrErnie|Dr. Ernie]] 12:55, 2 Sep 2008 (PDT)]'' | ||
Given that: | Given that: |
Revision as of 19:57, 2 September 2008
RESTful JSON
Charter
[Initial Draft by Dr. Ernie 12:55, 2 Sep 2008 (PDT)]
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:
- is maximally compatible with existing (RESTful, generic) clients
- enables partial updates
- allows paging and/or partial returns of large datasets
- standardizes linking to related resources
- use of hypermedia (links + context) to manage application state
- does NOT become a full-fledged RPC solution
Resources
- Original proposal
- Google Group
- [AtomPub] (for comparison/inspiration)