[OASIS Issue Tracker] Commented: (ODATA-316) Allow omitting properties with null or default values from responses

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

    [ http://tools.oasis-open.org/issues/browse/ODATA-316?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=33315#action_33315 ] 

Ralf Handl commented on ODATA-316:
----------------------------------

I don't want to loosen the contract that not specifying $select means "give me everything".

I do want to reduce the difference in representatino between structural and navigation properties.

Navigation properties are already omitted in JSON if their value can be calculated by the client from defaults, and we could do the same for  structural properties, making minimal JSON even more minimalistic.

This ticket only affects the JSON format.

> Allow omitting properties with null or default values from responses
> --------------------------------------------------------------------
>
>                 Key: ODATA-316
>                 URL: http://tools.oasis-open.org/issues/browse/ODATA-316
>             Project: OASIS Open Data Protocol (OData) TC
>          Issue Type: Improvement
>          Components: OData JSON Format
>    Affects Versions: V4.0_WD01
>         Environment: [Proposed]
>            Reporter: Ralf Handl
>             Fix For: V4.0_WD01
>
>
> Properties not present in a request payload are already interpreted as having the default value (if defined in $metadata) or the null value (if nullable and without default value).
> Why not allow the same for responses.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://tools.oasis-open.org/issues/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira