A REST-based protocol, OData builds on HTTP, AtomPub, and JSON using URIs to address and access data feed resources. It enables information to be accessed from a variety of sources including (but not limited to) relational databases, file systems, content management systems, and traditional Web sites. OData provides a way to break down data silos and increase the shared value of data by creating an ecosystem in which data consumers can interoperate with data producers in a way that is far more powerful than currently possible, enabling more applications to make sense of a broader set of data. Every producer and consumer of data that participates in this ecosystem increases its overall value.
Specification development in the OASIS OData TC builds on the core OData Protocol V3 released in April 2012 and addresses additional requirements identified as extensions in four directional white papers: data aggregation, temporal data, JSON documents, and XML documents as streams. OData features lacking complete definition will also be addressed.
For example, consideration will be given to design of an OData pull-model "delta protocol" to support incremental maintenance of local (i.e., cached) results through "delta queries". Though not suitable for multi-master synchronization scenarios, it would support synchronization of data from a single store to multiple clients; coupled with the ability to submit updates from the client to the server, this can be used to provide a solution for keeping client's local data in sync with a single store.