Representations and resources defined by the standard
The standard defines a small set of JSON representations covering the generic constructs in a domain object model including the following:
- A list of links to domain objects
- A single domain object
- A property, collection, belonging to a domain object
- An action that may be invoked on a domain object
- An action result (which will typically include a domain object or list)
- A domain service (essentially a stateless domain object)
- A small number of very specific representations such as Home, Version, and User.
Restful Objects also defines a standard set of resources for accessing or manipulating these representations. The specification defines which HTTP methods may be used with each resource, and their meaning. The table below shows a partial summary:
|GET||Object summary, member summary, property values||Property ,details and value||Collection details and content||Action prompt||Invoke (if query only)|
|PUT||Update or clear multiple property values||Update or clear value||Add object (if set semantics)||N/A – 405 error||invoke (if idempotent)|
|DELETE||Delete object||Clear value||Remove object||N/A – 405 error||N/A – 405 error|
|POST||N/A – 405 error||N/A - 405 error||Add object (if list semantics)||N/A – 405 error||Invoke (any)|
Taken together the resources and representations allow the complete functionality of a domain object model to be accessed over HTTP. The following diagram, taken from the specification, illustrates the relationship between the most commonly used resources and representations:
History and status
The Restful Objects specification version 1.0.0 was released in June 2012.
There are two known implementations of the Restful Objects specification, both open source:
Relationship to other ideas
The Restful Objects specification states that it operates at a higher-level of abstraction than other restful standards such as the JAX-RS specifications for Java platform, or the WCF specification on .NET. There are some conceptual similarities to Odata - though Restful Objects places much more emphasis on exposing the behaviour of domain objects, not just their data.
There is an overlap with the naked objects pattern, in that both are concerned with creating generic interfaces to domain objects models. But while the latter creates some kind of user interface, Restful Objects creates an API - specifically a Restful API. The first two frameworks to implement the Restful Objects standard are both built on top of existing frameworks that implement the Naked Objects pattern.