[OASIS Issue Tracker] (ODATA-1430) Clarify handling of null values for complex-typed properties

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

Gerald Krause created ODATA-1430:
------------------------------------

             Summary: Clarify handling of null values for complex-typed properties
                 Key: ODATA-1430
                 URL: https://issues.oasis-open.org/browse/ODATA-1430
             Project: OASIS Open Data Protocol (OData) TC
          Issue Type: Improvement
          Components: JSON Format, URL Conventions
    Affects Versions: V4.01_OS
         Environment: proposed
            Reporter: Gerald Krause
             Fix For: V4.01_ERRATA01


The JSON Format specification describes in section [7.1 Primitive Value|http://docs.oasis-open.org/odata/odata-json-format/v4.01/odata-json-format-v4.01.html#_Toc38457753] 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|http://docs.oasis-open.org/odata/odata-json-format/v4.01/odata-json-format-v4.01.html#_Toc38457754].Â;

The case of complex-typed properties having null values is intended as the URL Conventions specification describes in Â[5.1.1.1.1 Equals|http://docs.oasis-open.org/odata/odata/v4.01/odata-v4.01-part2-url-conventions.html#_Toc31360958] 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.



--
This message was sent by Atlassian Jira
(v8.3.3#803004)