[OASIS Issue Tracker] Created: (ODATA-577) Do we need a way to distinguish between properties that are omitted due to being aggregated away versus those that don't apply (i.e., in a concatenated result)?

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

Do we need a way to distinguish between properties that are omitted due to being aggregated away versus those that don't apply (i.e., in a concatenated result)?
----------------------------------------------------------------------------------------------------------------------------------------------------------------

                 Key: ODATA-577
                 URL: http://tools.oasis-open.org/issues/browse/ODATA-577
             Project: OASIS Open Data Protocol (OData) TC
          Issue Type: Bug
          Components: OData Extension for Data Aggregation 
    Affects Versions: V4.0_CSD01
            Reporter: Michael Pizzo


There appear to be (at least) two ways a property may be omitted from an aggregated result:
1) The property may be omitted because it has been aggregated away (i.e., in a rollup)
2) The property may be omitted because an operator has been applied (i.e., concat) that leaves certain properties undefined for certain rows

Do we need a property annotation for either (or both) so that clients can distinguish between properties being omitted because they were aggregated away versus because they didn't 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