RE: Payload topic

["Ericson, George" <George.Ericson@dell.com>]

How about this:

1. Single Entity
1. Including Delta variants
2. Including By Value/Reference variants
2. Collection of Entities
1. Including Delta variants
2. Including By Value/Reference variants
3. Single Value
1. Including Delta variants
2. Including By Value/Reference variants
4. Collection of Values
1. Including Delta variants
2. Including By Value/Reference variants
5. Operation
6. Error
7. Metadata Document (Entity Container described in CSDL)
8. Service Document (Entity Container contents described in JSON Format)
9. 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?

1. Single Entity
2. Collection of Entities
3. Single Value
4. Collection of Values
5. Operation
6. Error
7. Entity Container

 

Thanks,

George