OASIS Mailing List ArchivesView the OASIS mailing list archive below
or browse/search using MarkMail.


Help: OASIS Mailing Lists Help | MarkMail Help

odata message

[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]

Subject: [OASIS Issue Tracker] (ODATA-818) Omit properties whose value is null

    [ https://issues.oasis-open.org/browse/ODATA-818?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=60711#comment-60711 ] 

Ralf Handl commented on ODATA-818:

1) That's my preferred interpretation: if not contained in the payload although it should be due to context URL and concrete type, it is null.
2) Default values that are not null must be part of the payload, no change to current rules.
3) No permission means "PropName@Core.Permissions":"None" has to be sent instead, no change to current rules
4) Server-driven $select must be reflected in the context URL, no change to current rules
5) For declared properties the @odata.type will tell which properties to expect for this instance.
6) I don't want you to guess, so if you requested odata.metadata=none, I'll graciously flood you with PropName:null to make your life easier :-)

> Omit properties whose value is null
> -----------------------------------
>                 Key: ODATA-818
>                 URL: https://issues.oasis-open.org/browse/ODATA-818
>             Project: OASIS Open Data Protocol (OData) TC
>          Issue Type: Improvement
>          Components: OData JSON Format, OData Protocol
>    Affects Versions: V4.0_ERRATA02
>            Reporter: Ralf Handl
>            Assignee: Ralf Handl
>             Fix For: V4.2_WD01
> Entities with many properties that are sparsely filled would benefit from optimizing the payload and omitting properties whose value is null.
> With odata.metadata=minimal the client can deduce from the context URL whether a property is missing due to not being part of the projection or due to being null.
> Maybe switch this on/off via a new preference in the Prefer header.

This message was sent by Atlassian JIRA

[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]