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-1353) Clarity for "@odata.type" in request payloads

Evan Ireland created ODATA-1353:

             Summary: Clarity for "@odata.type" in request payloads
                 Key: ODATA-1353
                 URL: https://issues.oasis-open.org/browse/ODATA-1353
             Project: OASIS Open Data Protocol (OData) TC
          Issue Type: Improvement
          Components: JSON Format
    Affects Versions: V4.01_OS
            Reporter: Evan Ireland

We ran into an interoperability issue where servers don't accept "@odata.type" in request payload (this is for a case where there is no inheritance in model).

Client is sending "@odata.type" because previously we encountered servers that required "@odata.type".

Now we were hoping to argue that servers not accepting "@odata.type" in request payload were non-compliant with the spec, however...

The âminimalâ and âfullâ metadata are defined in subsections of OData 4.01 JSON section 3.1 Controlling the Amount of Control Information in *Responses*.

Nowhere do we appear to define the amount of control information in *requests*.

Although we could take it as an unstated assumption that "@odata.type" MAY appear even where it isnât required to appear, it would be best if we have a separate section describing what control information MAY (and MUST, in the case of entity inheritance) appear in request payloads.

This message was sent by Atlassian Jira

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