- OData (Open Data Protocol) is a standard protocol for building and consuming RESTful APIs in a simple and standard way. - It allows data from various sources to be unified and consumed using common HTTP methods like GET, PUT, POST, DELETE and common formats like JSON and AtomPub. - Major companies like Microsoft use OData to expose data sources like reporting services through standardized APIs that can then be consumed by various clients and applications in a consistent manner.

1. Breaking down Data Silos The Open Data Protocol AKA OData Chris Woodruff Semantic Technology Conference San Francisco, CA June 8, 2011

2. Who am I? Chris Woodruff cwoodruff@live.com Blog – http://chriswoodruff.com Technical Architect – Perficient, Inc.

3. Goals What is it? Why do we care? How do we use it?

4. Why is OData Needed?

5. Quote – Jim Gray Today, the tools for capturing data both at the mega-scale and at the milli-scale are just dreadful. After you have captured the data, you need to curate it before you can start doing any kind of data analysis, and we lack good tools for both data curation and data analysis.

6. What is OData?

8. Uniform Patterns

9. Focus on Data, not on Formats

10. Stay High-Level, Abstract the StoreRequirements

12. Let people find and use their own data

13. …but where’s the data?

14. Broad direct database access is impractical

15. OData feeds expose data over application logic

16. Reports often represent the best data sources

17. All reports in Reporting Services are now OData feedsInsight from data

19. Scientific data, e.g. OSDI

20. Social data

21. Commercial public data, e.g. Netflix

22. Premium data, DataMarketsData Sharing at Large

23. Consistent, Up to Date

24. Scale to Large Datasets

25. Create Web API to be Consumed with Ease

26. maximize reach, focus investmentsshare libraries, browsers, applications

27. Monetize Data

28. data in modern web applications

29. Where did OData come from?

30. Is OData RESTful?

32. Atom, JSON formats

33. Uniform URL conventions

34. Navigation, filtering, sorting, paging, etc.

35. Uniform operations

36. Addressability

38. JSON

39. The Meta of OData

40. Lets dig into OData Protocol

42. OData services can expose Service Operations

43. OData services expose all these constructs via URIs

44. OData service may also expose a Service Metadata Document

45. OData has the ability for validation and server side securityThe Basics

47. Boolean

48. Byte

49. DateTime

50. DateTimeOffset

51. Time

53. Single

54. Guid

55. Int16

56. Int32

57. Int64

59. Query Navigation

61. Where is OData Used?

63. Who is using OData?

65. Where can you consume it?

66. LINQ

67. OData.org ODataPrimer.com Wrap Up

68. The Fourth Paradigm: Data-Intensive Scientific Discovery

69. http://deepfriedbytes.com