[ https://jira.jboss.org/jira/browse/DNA-55?page=com.atlassian.jira.plugin.... ] Randall Hauch commented on DNA-55: ---------------------------------- One of the things we want to develop for JBoss DNA is an ability to interface and interact with the repository using a RESTful API. We should consider RESTeasy - no way do we want to implement our own RESTful library. But there's more to a RESTful API than just picking an enabling library. Perhaps the biggest task is actually designing the RESTful API. This includes among other things the design of the URIs (e.g., what the URIs look like, how they map to the "resources" that exist in a repository, and how they different verbs map to actions on these resources), the representations of the resources and the choice of media types used by those representations (e.g., HTML, XML, JSON,etc.), and ensuring that the appropriate actions are mapped to the underlying resources. For future reference, here are some interesting links: - Recent post by Roy Fielding on what a REST API actually needs to be like: http://roy.gbiv.com/untangled/2008/rest-apis-must-be-hypertext-driven - Roy's definition of "hypertext", which is more general than what most people probably assume: http://roy.gbiv.com/untangled/2008/rest-apis-must-be-hypertext-driven#com... - Interpretation of Roy's REST API post (above): http://www.25hoursaday.com/weblog/2008/10/24/RESTAPIDesignInventMediaType... - Apache Sling: http://incubator.apache.org/sling -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira