OASIS Mailing List ArchivesView the OASIS mailing list archive below
or browse/search using MarkMail.

 


Help: OASIS Mailing Lists Help | MarkMail Help

odata message

[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]


Subject: [OASIS Issue Tracker] Commented: (ODATA-161) Clarify and if possible add directions for 'stranded' readers in the ending note of section 1 Introduction


    [ http://tools.oasis-open.org/issues/browse/ODATA-161?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=31793#action_31793 ] 

Stefan Drees commented on ODATA-161:
------------------------------------

Resolution acknowledged. Thanks! 

> Clarify and if possible add directions for 'stranded' readers in the ending note of section 1 Introduction
> ----------------------------------------------------------------------------------------------------------
>
>                 Key: ODATA-161
>                 URL: http://tools.oasis-open.org/issues/browse/ODATA-161
>             Project: OASIS Open Data Protocol (OData) TC
>          Issue Type: Improvement
>          Components: OData Extension for Data Aggregation v1.0
>    Affects Versions: WD01
>         Environment: [Proposed]
>            Reporter: Stefan Drees
>            Assignee: Ralf Handl
>            Priority: Minor
>             Fix For: WD01
>
>
> In the current revision of the document for [OData Extension for Data Aggregation Version 1.0 Working Draft 01](https://www.oasis-open.org/committees/download.php/47363/odata-data-aggregation-ext-v1.0-wd01-2012-11-02.docx) the ending note (last paragraph) in section 1 Introduction reads:
> 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.

-- 
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

        


[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]