OASIS Open Data Protocol (OData) TC

Join TC     TC Page     Send a comment to this TC

Simplifying data sharing across disparate applications in enterprise, Cloud, and mobile devices

Ralf Handl, ralf.handl@sap.com, Chair
Michael Pizzo, mikep@microsoft.com, Chair
Stefan Hagen, stefan@hagen.link, Secretary

Table of Contents


ISO/IEC JTC 1 Approves OASIS OData Standard for Open Data Exchange; 23 Feb 2017.

OData V4.0 and OData JSON Format V4.0 Approved Errata are published; July 13 2016.

OData was named as a 2014 Open Standards Cup Finalist in the Outstanding Accomplished Technical Committee category. Congratulations!


The OASIS OData TC works to simplify the querying and sharing of data across disparate applications and multiple stakeholders for re-use in the enterprise, Cloud, and mobile devices. 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.

For more information on OData, see the TC Charter.


  • Chairs: Ralf Handl (SAP SE), Mike Pizzo (Microsoft)
  • Secretary: Stefan Hagen (Individual)


  • OData Protocol 4.0, OData URL Conventions 4.0, OData Conceptual Schema Definition Language (CSDL) 4.0, OData ABNF Construction Rules 4.0: Michael Pizzo (Microsoft), Ralf Handl (SAP AG), Martin Zurmuehl (SAP AG)
  • OData Atom Format 4.0: Martin Zurmuehl (SAP AG), Michael Pizzo (Microsoft), Ralf Handl (SAP AG)
  • OData JSON Format 4.0: Ralf Handl (SAP), Michael Pizzo (Microsoft), Mark Biamonte (Progress Software)
  • OData Extension for Data Aggregation: Ralf Handl (SAP AG), Hubert Heijkers (IBM), Michael Pizzo (Microsoft), Gerald Krause (SAP AG), Martin Zurmuehl (SAP AG)
  • OData Extension for Temporal Data: Ralf Handl (SAP AG), Hubert Heijkers (IBM), Michael Pizzo (Microsoft), Martin Zurmuehl (SAP AG)
  • OData Extension for XML Data: Andrew Eisenberg (IBM) [primary editor], Ken Baclawski (Northeastern University)
  • OData Extension for JSON Data: Susan Malaika (IBM) [primary editor], Mark Biamonte (Progress Software)


No subcommittees have been formed for this TC.

TC Tools and Approved Publications

Technical Work Produced by the Committee

In February 2014, the membership of OASIS approved the following two OASIS Standards:

(1) OData Version 4.0 Plus Errata 03 (multi-part Work Product)

(2) OData JSON Format Version 4.0 Plus Errata 03

The OData Technical Committee has approved Committee Specification 02 of the following Work Product:

(3) OData Atom Format Version 4.0

The OData Technical Committee has approved Committee Note 01 of the following Work Product:

(4) What’s New in OData Version 4.0

The OData Technical Committee has approved Committee Specification 02 of the following Work Product:

(5) OData Extension for Data Aggregation Version 4.0

For your convenience, OASIS provides a complete package of the prose documents and related files mentioned above in ZIP distribution files:

  1. OData Version 4.0: http://docs.oasis-open.org/odata/odata/v4.0/errata03/os/odata-v4.0-errata03-os.zip
  2. OData JSON Format Version 4.0: http://docs.oasis-open.org/odata/odata-json-format/v4.0/errata03/os/odata-json-format-v4.0-errata03-os.zip
  3. OData Atom Format Version 4.0: http://docs.oasis-open.org/odata/odata-atom-format/v4.0/cs02/odata-atom-format-v4.0-cs02.zip
  4. What’s New in OData Version 4.0: http://docs.oasis-open.org/odata/new-in-odata/v4.0/cn01/new-in-odata-v4.0-cn01.zip
  5. OData Extension for Data Aggregation Version 4.0: http://docs.oasis-open.org/odata/odata-data-aggregation-ext/v4.0/cs02/odata-data-aggregation-ext-v4.0-cs02.zip

Expository Work Produced by the Committee

  • Webinar: "OData at OASIS" recorded 11 July 2012
  • OData video delivered by Sanjay Patil of SAP at the OASIS Cloud Standards Lightning Rounds, July 2012

External Resources

Although not produced by the OASIS OData TC, the following information offers useful insights into its work:

Mailing Lists and Comments

odata: the list used by TC members to conduct Committee work. TC membershipis required to post. TC members are automatically subscribed; the public may view archives.

odata-comment: a public mail list for providing input to the OASIS OData TC members. Send a comment or view archives.

Press and Commentary

Additional Information

No additional information available.

Providing Feedback: OASIS welcomes feedback on its technical activities from potential users, developers, and others to better assure the interoperability and quality of OASIS work.