[OASIS Issue Tracker] (ODATA-1466) Behaviour of custom aggregation methods cannot be explained

[OASIS Issues Tracker <workgroup_mailer@lists.oasis-open.org>]

Heiko Theissen created ODATA-1466:
-------------------------------------

             Summary: Behaviour of custom aggregation methods cannot be explained
                 Key: ODATA-1466
                 URL: https://issues.oasis-open.org/browse/ODATA-1466
             Project: OASIS Open Data Protocol (OData) TC
          Issue Type: Improvement
          Components: Data Aggregation
            Reporter: Heiko Theissen


[OData-Aggr, section. 3.1.3.6|https://docs.oasis-open.org/odata/odata-data-aggregation-ext/v4.0/cs02/odata-data-aggregation-ext-v4.0-cs02.html#_Toc432754680] states that services can define custom aggregation methods, and the annotation term property [{{Aggregation.ApplySupportedDefaults/CustomAggregationMethods}}|https://github.com/oasis-tcs/odata-vocabularies/blob/main/vocabularies/Org.OData.Aggregation.V1.xml#L86] is used to advertise them.

But this leaves no room for explaining the _behaviour_ of a custom aggregation method. Could this be modelled as a client-side only function (see ODATA-1428)? The one from example 13 in OData-Aggr would then be modelled as
{code:xml}
<Schema Name="Custom">
 <Function Name="concat" IsBound="true?">
  <Annotation Term="Core.ClientSideOnly"/>
  <Annotation Term="Core.Description" String="Concatenates distinct string values separated by commas"/>
  <Parameter Name="InputSet" Type="Collection(Edm.String)"/>
  <ReturnType Type="Edm.String"/>
 </Function>
</Schema>
{code}

Instead of {{Core.ClientSideOnly}}, a more specific term {{Core.CustomAggregationMethod}} could be used.



--
This message was sent by Atlassian Jira
(v8.3.3#803004)