Terms to describe which data in a given entity model can be aggregated, and how. Related to the specification document [OData-Data-Agg-v4.0](http://docs.oasis-open.org/odata/odata-data-aggregation-ext/v4.0/odata-data-aggregation-ext-v4.0.html). This entity set or collection supports the `$apply` system query option Default support of the `$apply` system query option for all collection-valued resources in the container Annotating term [`ApplySupported`](#ApplySupported) for a specific collection-valued resource overrides the default support with the specified properties using PATCH semantics: - Primitive or collection-valued properties specified in `ApplySupported` replace the corresponding properties specified in `ApplySupportedDefaults` - Complex-valued properties specified in `ApplySupported` override the corresponding properties specified in `ApplySupportedDefaults` using PATCH semantics recursively - Properties specified neither in `ApplySupported` nor in `ApplySupportedDefaults` have their default value Services that do not fully implement a certain aggregation-related functionality may document this by annotating the [`ApplySupported`](#ApplySupported) or [`ApplySupportedDefaults`](#ApplySupportedDefaults) annotation with a description. Aggregatable property Standard and custom aggregation methods that can be applied to the property. If omitted, all aggregation methods can be applied Recommended method for aggregating values of the property Standard or custom aggregation method Custom aggregation methods MUST use a namespace-qualified name, that is contain at least one dot. For navigation properties, it counts the distinct entities in the union of all entities related to entities in the input set. For collection-valued primitive properties, it counts the distinct items in the union of all collection values in the input set. The context-defining properties need either be part of the result entities, or be restricted to a single value by a pre-filter operation. Examples are postal codes within a country, or monetary amounts whose context is the unit of currency. Every recursive hierarchy function defined in this vocabulary has - a parameter `HierarchyQualifier` of this type and - a parameter `HierarchyNodes` that is a collection of entities of a common type without multiple occurrences of the same entity. `HierarchyQualifier` is the qualifier of a `RecursiveHierarchy` annotation on the entity type of the collection given by the `HierarchyNodes` parameter. This specifies a recursive hierarchy that is evaluated by the function. This function may only occur in the second parameter of a `groupby` transformation whose first parameter contains `rolluprecursive(...)`. It is evaluated as part of the transformation `R(x)` in the "`rolluprecursive` algorithm" (OData-Data-Agg-v4.0, section 6.3). Its behavior is undefined outside of this algorithm. ``` Sales?$apply=groupby((rolluprecursive(...)), filter(SalesOrganization eq Aggregation.rollupnode())/aggregate(...)) ``` constructs a rollup that contains aggregates per hierarchy node while excluding descendants from the aggregation. Every instance in the output set of a `groupby` transformation with M `rolluprecursive` operators has M relationships to M nodes in M recursive hierarchies. This function returns the node x with path r to the root in relationship number N. If several such `groupby` transformations are nested, this function refers to the innermost one. This instance annotation occurs in the result set after a `traverse` transformation (OData-Data-Agg-v4.0, section 6.2.2.2). A use case for this is traversal with multiple parents, when this annotation takes as value one parent node identifier followed by one grandparent node identifier and so on.