we're upgrading to JIRA 5 this week, which means we can use the Ruby JIRA REST gem to do this stuff. sure we could come up with something useful from this

interesting thread on the perils of committing to a URI scheme too early.

"Hypermedia as the engine of application state (HATEOAS). If that concept was better understood by more people we might finally make some progress on things other than how to make pretty URLs."

Web architects must understand that resources are just consistent mappings from an identifier to some set of views on server-side state. If one view doesn’t suit your needs, then feel free to create a different resource that provides a better view (for any definition of “better”). These views need not have anything to do with how the information is stored on the server, or even what kind of state it ultimately reflects. It just needs to be understandable (and actionable) by the recipient.

Apache Shindig is an OpenSocial container and helps you to start hosting OpenSocial apps quickly by providing the code to render gadgets, proxy requests, and handle REST and RPC requests

Just do it as part of your REST index action, okay

WS-* is North Korea and REST is South Korea. While REST will go on to become an economic powerhouse with steadily increasing standards of living for all its citizens, WS-* is doomed to sixty+ years of starvation, poverty, tyranny, and defections until it

great article on using REST for complex solutions

SOAP framework for java

great articles on REST issues

dissertation on REST