[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]
Subject: [OASIS Issue Tracker] (ODATA-587) Add example for complex value that is an empty object
[ https://tools.oasis-open.org/issues/browse/ODATA-587?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Michael Pizzo updated ODATA-587: -------------------------------- Environment: [Applied] (was: [Proposed]) > Add example for complex value that is an empty object > ----------------------------------------------------- > > Key: ODATA-587 > URL: https://tools.oasis-open.org/issues/browse/ODATA-587 > Project: OASIS Open Data Protocol (OData) TC > Issue Type: Improvement > Components: OData JSON Format > Affects Versions: V4.0_CS02 > Environment: [Applied] > Reporter: Ralf Handl > Assignee: Michael Pizzo > Priority: Minor > Fix For: V4.0_ERRATA01 > > > In some cases a complex value can be an empty object, e.g. if a complex type only contains navigation properties, or only its navigation properties are specified in $select, and the response format is minimal JSON: > - 7.2: A complex value is represented as a single JSON object containing one name/value pair for each property that makes up the complex type. > - 8.1: The navigation link for a navigation property is only represented if the client requests odata.metadata=full or the navigation link cannot be computed[...] > So it clearly is a JSON object with zero name-value pairs (one for each property = zero, one for each non-computable navigation = zero), but it is somewhat hard to deduce this from the specification text. An explicit statement and/or example would help. > Another example is an open complex type that for this instance doesn't have any properties. -- This message was sent by Atlassian JIRA (v6.2.2#6258)
[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]