I started my blog with the intent of having in depth series on WCF, well my focus shifted as other interesting Microsoft technology came my way at work and out of work. It’s not feasible for me at the moment to be able to dedicate a substantial amount of time to a specific topic. So I won’t be committing too much on OData, but I will be presenting an introductory level session of OData at the beginning of May so would like to get my thoughts and notes out here on my blog.
So let’s get started with OData.
Copy-pasting directly off the FAQ on the OData.org site is:
The Open Data Protocol (OData) is an open protocol for sharing data.
It 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.
Ok, that sounds like a plan.
Every producer and consumer of data that participates in this ecosystem increases its overall value.
That last point has the marketing twist, which to me translates into; “unless there’s enough people using this protocol, it will only exist in obscurity.”
Not to make this sound like an attack OData, it’s early days so let’s keep investigating.
One of the initial aspects of OData I find both interesting and commendable is the decision for the protocol to work through the standard HTTP request methods (verbs); GET, POST, PUT, DELETE. But my attention then quickly turned to access policies, security and authentication so I jumped ahead in my research and discovered the concept of Query Interceptors as part of implement an OData services that helps deal with this, I’ll go into detail on this in a future post.
Microsoft is putting some attention behind into OData, with it being featured in the day 2, MIX10 keynote presented by Doug Purdy. There’s also a mid May 2010 “roadshow” (awareness / day conference) happening across 8 locations (3 US, 2 EU, 2 Asia). I am looking forward to seeing the content that comes out of that.
Right now I’m in the process of dissecting the MIX10 Keynote OData segment, and the two other MIX10 sessions on OData. My objective is not only to learn a little bit about OData but also determine if it will assist in making some data as part of my day job more accessible.
My attack plan for understanding the protocol concepts will be:
- To first dig a little into the specification and the use of existing tech (ATOM and JSON), a summary post is here.
- Create an OData service for part of complex system and large set of data.
- Then hopefully being able to determine if it was worth it (so long as I get it working).
Along the way presenting findings here and at Melbourne user groups, so stay tuned.