Abstract:
This specification adds basic grouping/aggregation functionality (min, max, sum, average, count, distinct-count) to OData without changing any of the base principles of OData.
1 Introduction
This specification adds the notion of aggregation to OData without changing any of the base principles of OData. It defines a representation and semantics for aggregation of data, especially:
• Semantics and operations for querying aggregated data,
• Results format for queries containing aggregated data,
• Annotations to indicate what can be aggregated, and how.
Abstract:
This specification adds basic grouping/aggregation functionality (min, max, sum, average, count, distinct-count) to OData without changing any of the base principles of OData.
1 Introduction
This specification adds the notion of aggregation to OData without changing any of the base principles of OData. It defines a representation and semantics for aggregation of data, especially:
• Semantics and operations for querying aggregated data,
• Results format for queries containing aggregated data,
• Annotations to indicate what can be aggregated, and how.
Note: If you as a reader are hoping to find anything remotely related to "advanced analytics" capabilities added to OData then you are unfortunately reading the wrong document. In this context think about augmenting the Entity Data Model (EDM) with annotations adding analytic type context to the model and some basic grouping/aggregation functionality (min/max/sum/average/count/distinct-count, provider specific and rule based aggregations) based on the data exposed in the EDM.
To craft a proposal, at least for me further information is needed:
1. Is there a 'better place' for 'advanced analytics' capabilities added to OData ?
2. what does 'advanced analytics' capabilities actually paraphrase ?
3. What context is indicated with 'In this context think about augmenting ...' is it
3.a the imagined 'advanced analytics' not being serviced by the current document or
3.b the content being served by this document (i.e. 'OData Extension for Data Aggregation') ?
Expecting the answer to 3 as 3.b I would suggest - and I am willing to help craft a readable 'infoset' - rewrite Abstract and Introduction to yield well separated readable views on this extension. As of now, I have to read further to understand a minimum about that topic, but after that I may come up with suggestions for abstract and Introduction.
One remark w.r.t. abstracts: I would refrain from 'additional formal structuring' of content (as in this case with an itemized list). Abstracts IMO are meant (and work best) as english prose, which carries clarity and shows structure only in and by itself, i.e. by choice of the right words and phrases that make it up.
Note: If you as a reader are hoping to find anything remotely related to "advanced analytics" capabilities added to OData then you are unfortunately reading the wrong document. In this context think about augmenting the Entity Data Model (EDM) with annotations adding analytic type context to the model and some basic grouping/aggregation functionality (min/max/sum/average/count/distinct-count, provider specific and rule based aggregations) based on the data exposed in the EDM.
To craft a proposal, at least for me further information is needed:
1. Is there a 'better place' for 'advanced analytics' capabilities added to OData ?
2. what does 'advanced analytics' capabilities actually paraphrase ?
3. What context is indicated with 'In this context think about augmenting ...' is it
3.a the imagined 'advanced analytics' not being serviced by the current document or
3.b the content being served by this document (i.e. 'OData Extension for Data Aggregation') ?
Expecting the answer to 3 as 3.b I would suggest - and I am willing to help craft a readable 'infoset' - rewrite Abstract and Introduction to yield well separated readable views on this extension. As of now, I have to read further to understand a minimum about that topic, but after that I may come up with suggestions for abstract and Introduction.
One remark w.r.t. abstracts: I would refrain from 'formally structuring' of content like here with a itemized list. Abstracts IMO are meant (and work best) as english prose, which carries clarity and shows structure only in itself by choice of the right words and phrases that make it up.
Note: If you as a reader are hoping to find anything remotely related to "advanced analytics" capabilities added to OData then you are unfortunately reading the wrong document. In this context think about augmenting the Entity Data Model (EDM) with annotations adding analytic type context to the model and some basic grouping/aggregation functionality (min/max/sum/average/count/distinct-count, provider specific and rule based aggregations) based on the data exposed in the EDM.
To craft a proposal, at least for me further information is needed:
1. Is there a 'better place' for 'advanced analytics' capabilities added to OData ?
2. what does 'advanced analytics' capabilities actually paraphrase ?
3. What context is indicated with 'In this context think about augmenting ...' is it
3.a the imagined 'advanced analytics' not being serviced by the current document or
3.b the content being served by this document (i.e. 'OData Extension for Data Aggregation') ?
Expecting the answer to 3 as 3.b I would suggest - and I am willing to help craft a readable 'infoset' - rewrite Abstract and Introduction to yield well separated readable views on this extension. As of now, I have to read further to understand a minimum about that topic, but after that I may come up with suggestions for abstract and Introduction.
One remark w.r.t. abstracts: I would refrain from 'additional formal structuring' of content (as in this case with an itemized list). Abstracts IMO are meant (and work best) as english prose, which carries clarity and shows structure only in and by itself, i.e. by choice of the right words and phrases that make it up.
Please see description, implementable proposal will follow.
Abstract:
This specification adds basic grouping/aggregation functionality (min, max, sum, average, count, distinct-count) to OData without changing any of the base principles of OData.
1 Introduction
This specification adds the notion of aggregation to OData without changing any of the base principles of OData. It defines a representation and semantics for aggregation of data, especially:
• Semantics and operations for querying aggregated data,
• Results format for queries containing aggregated data,
• Annotations to indicate what can be aggregated, and how.
Improvement
Minor