[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=33050#action_33050 ] 

Michael Pizzo commented on ODATA-316:
-------------------------------------

Assuming that omitting properties with null or default values is dangerous.

There may be multiple reasons that a service omit values; there may be permissions issues, or certain properties may be expensive.

We should say that, in the absence of $select, services may return a subset of properties defined in the $metadata. If $select is specified, each property must be returned or an error generated.

Client should never make assumptions about missing properties.

> 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