[OASIS Issue Tracker] (ODATA-871) Clarify that properties added with Compute MUST include the odata.type (if not described in $metadata)

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

Michael Pizzo created ODATA-871:
-----------------------------------

             Summary: Clarify that properties added with Compute MUST include the odata.type (if not described in $metadata)
                 Key: ODATA-871
                 URL: https://issues.oasis-open.org/browse/ODATA-871
             Project: OASIS Open Data Protocol (OData) TC
          Issue Type: Bug
          Components: OData Extension for Data Aggregation
    Affects Versions: V4.0_CSD02
         Environment: [Proposed]
            Reporter: Michael Pizzo
             Fix For: V4.0_CSD03


Properties computed using the Compute clause are generally treated as dynamic properties, and thus require an odata.type in the response. There is a case where the aggregated property has the same name as the property being aggregated, and in some cases this can cause numeric promotion. Call out this case explicitly as requiring the odata.type annotation in minimal metadata or greater.



--
This message was sent by Atlassian JIRA
(v6.2.2#6258)