Our resource model has numerous has-a relationships between resources. These are usually modeled by a URI that references a collection. For example, a component has a set of related components, a set of operations, and a set of resources. Getting a complete picture of a component requires the Consumer to perform 4 GET operations (GET component, GET related components, GET operations, GET sensors).

CAMP needs a generic way for the Consumer to indicate to the Provider that they would like the Provider to "roll up" all of these has-a relationships into a single JSON response.