How about this: Single Entity Including Delta variants Including By Value/Reference variants Collection of Entities Including Delta variants Including By Value/Reference variants Single Value Including Delta variants Including By Value/Reference variants Collection of Values Including Delta variants Including By Value/Reference variants Operation Error Metadata Document (Entity Container described in CSDL) Service Document (Entity Container contents described in JSON Format) Batch requests/response George From:
odata@lists.oasis-open.org <
odata@lists.oasis-open.org> On Behalf Of Michael Pizzo Sent: Thursday, April 2, 2020 12:57 PM To: Ericson, George;
odata@lists.oasis-open.org Subject: [odata] RE: Payload topic [EXTERNAL EMAIL] Comparing this to our section on ContextUrl , which describes the contextUrl for different types of payloads, and assuming your “Value” == “Primitive or Complex Type”, you may want to consider the following additional payload types: -ServiceDocument (which may be your #7 EntityContainer?) -MetadataDocument -Delta Payload -EntityReference/Collection of EntityReferences -PropertyValue -batch requests/response From:
odata@lists.oasis-open.org <
odata@lists.oasis-open.org > On Behalf Of Ericson, George Sent: Thursday, April 2, 2020 5:59 AM To:
odata@lists.oasis-open.org Subject: [EXTERNAL] [odata] Payload topic Thinking about kinds of payloads (generically) that are passed via OData. Not worrying about variants within these generic payload types, are there more? Single Entity Collection of Entities Single Value Collection of Values Operation Error Entity Container Thanks, George