The document discusses the Open Data Protocol (OData), emphasizing its role in facilitating effective data sharing across various platforms, including cloud services and on-premises data. It outlines the need for a uniform interface to manage data interoperability and provides a concise overview of OData's functionalities, including data representation and common operations. Additionally, it highlights the adoption of OData among major products and companies in the industry.

1. Open Data Protocol (OData)Pablo CastroSoftware ArchitectMicrosoftpablo.castro@microsoft.com

2. Industry TrendsData Silos -> Open DataImpacts government, science and enterpriseWeb Sites -> Web APIsDevice/Language/Runtime proliferation On Premises -> CloudIncludes shift to Web API’sAPIs need to support both on-premises and cloud

3. Data SharingEffective data sharing is trickyAvoid imposing how data should be accessedProvide a uniform interface to all dataMaintain consistency & business logic rulesSemantics may come with data or added separatelyEnabling interoperabilityBuild on existing infrastructureHTTP, JSON, etc.Establish common patternsMost data services need filters, sorting, paging, etc.

4. OData in 1 SlideUniform way of representing structured dataAtom, JSON formatsUniform URL conventionsNavigation, filtering, sorting, paging, etc.Uniform operationsAddressabilityGET, POST, PUT, DELETE always mean the sameKeep the barrier of entry as low as possible

5. Using ODataServer frameworksWCF Data Services (.NET), odata4j (java), RubyClient environmentsAndroid, iOS, Windows Phone 7, HTML/JavaScript, Silverlight, Java, PHPProductsMicrosoft: SharePoint, Dynamics, Reporting Services, …Other companies: IBM, SAP, WebNodes, Telerik, Tableau, Pebble Reports, …

6. http://odata.org