Clarity needed about if/when Control Information" must be specified in payload sent from client to server

XMLWordPrintable

    • Type: Improvement
    • Resolution: Fixed
    • Priority: Major
    • V4.0_ERRATA01
    • Affects Version/s: V4.0_OS
    • Component/s: JSON Format
    • None
    • Environment:

      [Applied]

    • Hide

      Clarify, for each subsection of 4.5 "Control Information", whether each annotation is optional or required (and in which circumstances it is required) for request from client to server.

      Show
      Clarify, for each subsection of 4.5 "Control Information", whether each annotation is optional or required (and in which circumstances it is required) for request from client to server.

      In regard to section 4.5 "Control Information", (apart from section 4.5.1 odata.context) the JSON format spec is written as if it only considers payload sent in responses from server to client.

      However it is clear that it must in some cases apply to content sent in payload from client to server.

      For example, presumably when an inheritance hierarchy is involved, a POST request needs to set odata.type.

      On the other hand, a client might not know a valid entity-id to put in odata.id for a POST request (in particular where the server does not support canonical URLs).

            Assignee:
            handl
            Reporter:
            evan.ireland.2
            Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

              Created:
              Updated:
              Resolved: