This document describes the operation model for the protocol, specifying the interactions between clients and servers for retrieving and manipulating data in an OData service.It builds on the [OData-Core] document for core concepts, [OData-URI] for URI conventions and on the formats specifications for Atom [OData-Atom] and JSON [OData-JSON] for the description of data representations.To indicate it can handle all of them a client would set the Servers are expected to honor the client request for a format or fail with status code 406 (Not Acceptable).While HTTP 1.1 allows servers to return alternate representations when none of the requested ones are available, OData servers should return one of the requested representations or fail.
Clients can choose to support only specific content-types or all of them.
Clients retrieve a feed, Entry or service document by issuing an HTTP GET request against its URI.
Servers respond with the feed, Entry or service document in the response body in the proper format.
OData supports two formats for representing resources, the XML-based Atom format and the JSON format.
As described in the HTTP specification [RFC2616], clients can indicate their preference of resource representation by including an For the Atom format there is more than one MIME type involved.
The OData service interface has a fixed number of operations that have uniform meaning across all the resources it can act on.