Uploaded image for project: 'OASIS Open Data Protocol (OData) TC'
  1. OASIS Open Data Protocol (OData) TC
  2. ODATA-1137

Clarify type information for dynamic properties in the aggregated result set

    XMLWordPrintable

    Details

    • Type: Bug
    • Status: Resolved
    • Priority: Major
    • Resolution: Fixed
    • Affects Version/s: V4.0_CSD03
    • Fix Version/s: V4.0_CSD04
    • Component/s: Data Aggregation
    • Labels:
      None
    • Environment:

      Proposed

    • Proposal:
      Hide

      Add ellipses (…) to all these examples to make clear that the payload is not complete, but omit the extra instance annotations from the JSON payload examples to preserve their readability.

      Add a disclaimer at the end of section 3: “The JSON representation of dynamic properties in the result will include type (odata.type) annotations as additional control information where required by [OData-JSON]. For brevity, such annotations are omitted from the examples in the following sections.”
      Remove this sentence from sections 3.1 and 3.14: “The JSON representation of these dynamic properties will include odata.type annotations where required by [OData-JSON].”

      Show
      Add ellipses (…) to all these examples to make clear that the payload is not complete, but omit the extra instance annotations from the JSON payload examples to preserve their readability. Add a disclaimer at the end of section 3: “The JSON representation of dynamic properties in the result will include type (odata.type) annotations as additional control information where required by [OData-JSON] . For brevity, such annotations are omitted from the examples in the following sections.” Remove this sentence from sections 3.1 and 3.14: “The JSON representation of these dynamic properties will include odata.type annotations where required by [OData-JSON] .”

      Description

      The JSON and Atom format specifications list special cases where a property value does not need to be complemented with type information using the type(odata.type) instance annotation. The current Data Aggregation specification contains several examples with dynamic properties, where the data type is missing, because they don’t fall into this category: Examples 5, 9, 10, 12, 15, 57, 58, 59, 63, 64, and 70 contain one or more dynamic properties of type Edm.Decimal without a corresponding type annotation required by [OData-JSON].

        Attachments

          Activity

            People

            • Assignee:
              Unassigned
              Reporter:
              gerald.krause1 Gerald Krause
            • Watchers:
              2 Start watching this issue

              Dates

              • Created:
                Updated:
                Resolved: