[OASIS Issue Tracker] Updated: (ODATA-574) Rationalize Aggregatable Properties, Dynamic Aggregates, and floating aggregates

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

     [ http://tools.oasis-open.org/issues/browse/ODATA-574?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Michael Pizzo updated ODATA-574:
--------------------------------

    Resolution: Applied and reviewed 2013-12-12:https://www.oasis-open.org/apps/org/workgroup/odata/download.php/51703/odata-data-aggregation-ext-v4.0-wd02-2013-12-12.docx  (was: Applied:https://www.oasis-open.org/apps/org/workgroup/odata/download.php/51703/odata-data-aggregation-ext-v4.0-wd02-2013-12-12.docx)

> Rationalize Aggregatable Properties, Dynamic Aggregates, and floating aggregates
> --------------------------------------------------------------------------------
>
>                 Key: ODATA-574
>                 URL: http://tools.oasis-open.org/issues/browse/ODATA-574
>             Project: OASIS Open Data Protocol (OData) TC
>          Issue Type: Improvement
>          Components: OData Extension for Data Aggregation 
>    Affects Versions: V4.0_CSD01
>         Environment: [Proposed]
>            Reporter: Michael Pizzo
>             Fix For: V4.0_CSD02
>
>
> In the CSD01 specification we sometimes treat properties as aggregates by applying a "default aggregation method". This was confusing to folks who didn't expect this special aggregation behavior to automatically apply to properties. other times the user can apply an aggregation method to a property or expression. In some cases an alias was required, in others it was not, and the type could be dependent on whether or not an alias was used. 
> The addition of floating aggregates added yet a new way to apply define aggregates, leaving services multiple ways to do the same thing and clients either having to support all different combinations or pick a subset of combinations and not be interoperable. 
> Also, we could use this opportunity to refactor the annotations so they are not nested under one huge annotation but are more naturally specified in the context which they apply.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://tools.oasis-open.org/issues/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira