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

Clarify handling of null values for complex-typed properties

    XMLWordPrintable

    Details

    • Type: Improvement
    • Status: Closed
    • Priority: Major
    • Resolution: Fixed
    • Affects Version/s: V4.01_OS
    • Fix Version/s: V4.01_ERRATA01
    • Component/s: JSON Format
    • Labels:
      None
    • Proposal:
      Hide

      Add the sentence from section 7.1 in the JSON Format document also to section 7.2: "Null values are represented as the JSON literal null."

      Show
      Add the sentence from section 7.1 in the JSON Format document also to section 7.2: "Null values are represented as the JSON literal null."
    • Resolution:
      Show
      https://github.com/oasis-tcs/odata-specs/pull/133

      Description

      The JSON Format specification describes in section 7.1 Primitive Value how a null value is represented for a property of primitive type. However, an analogous description is not provided in section 7.2 Complex Value

      The case of complex-typed properties having null values is intended as the URL Conventions specification describes in  5.1.1.1.1 Equals how the eq-operator works for such properties to test against the null value.

      Hence it seems to be a gap that section 7.2 of the JSON Format document does not explicitly mention null values.

        Attachments

          Activity

            People

            • Assignee:
              handl Ralf Handl
              Reporter:
              gerald.krause1 Gerald Krause
            • Watchers:
              3 Start watching this issue

              Dates

              • Created:
                Updated:
                Resolved: