This is a brain-dump of some thoughts I have about Resource Oriented Programming/Architecture.

• Unlike OOP in which associations are managed in the objects level, when focusing on resources, the associations are managed in the resource representation, such as using hypermedia’s anchors to link to related resources.
• Resources are mapped to DDD’s Aggregate Root. Inside the aggregate, association to other aggregates should be (/translation should be) supported by the environment like openrasta CreateUri extension method).
• I think OO and RO have different scopes. RO is on the protocol level (it supports rigid and simple interface) - it is the entry point to the domain - the way to manipulate it. It is also not the necessarily the best solution as an entry point. It just fits very well to web applications as HTTP is about resources. Objects on the other hand are a very flexible protocol, this makes them very convenient mean to manage the internal domain but they can be confusing as the external protocol.