rest
Jump to navigation
Jump to search
Microformats in REST Web Services
This the home page for discussion, research, and standards regarding how to optimally use Microformats as the encoding for REST web services. The goal is for all REST-related information in the microformats world to live under this URL.
Discussion Forums
- uf-rest discussion list on microformats.org
- rest-discuss @ Yahoo Groups
Topics
URLs
- rest/opacity
- Properly Interpreting the "Axiom of URI Opacity"
- rest/urls
- How should URLs be structured for maximum clarity & discoverability?
HTML
- rest/ahah
- Asychronous HTML vs. AJAX
- rest/datatypes
- How to encode type information in HTML
- rest/description
- What, if anything, is the analogue of WSDL for REST services?
- rest/webforms
- Upgrading browsers to support PUT and DELETE properly
Implementations
- rest/cgi
- CGI is slow, and FastCGI is designed for C parsers. Is there a third option?
- rest/rails
- Ways to make Ruby on Rails more REST-friendly out of the box.
Standards
- HTTP as a Substrate - Best Current Practice
- text/uri-list (Section 5, URI Resolution Services)
Background Research
Examples
Brainstorming
Proposals
Note that these are all preliminary.
- [REST-Enabled XHTML] by Dr. Ernie
- original at rest/rex-proposal
- WebUtopia by Toydi
- more details in rest-discuss thread: "Dreams about ReSTifying web apps"
Implementations
Tools
- XOXO parser (python)
- also xoxo-plist.py, a pyobjc variant support Mac OS X plists]
- ahah.js Asynchronous HTML over HTTP
- Ruby RESTifarian plugin
$ script/plugin install restifarian # need beta gems/edge rails for this to work
- See also prototype controller
Examples
Sites
- Larry Staton Jr. AHAH-enabled homepage (a first!)