Microsoft proposes OData as the web data protocol while Google uses GData. Microsoft invites Google to join forces with them in adopting OData. Will they do it?
The Open Data Protocol (OData) is a protocol for querying and updating data on the web, being a set of extensions to the AtomPub protocol. AtomPub is an HTTP-based protocol used for the same purpose, to create and update web resources, working in conjunction with the Atom Syndication Format, an XML-based language used for web feeds. OData was previously known as the Astoria Protocol, ADO.NET Data Services Protocol or as a set of conventions/extensions to AtomPub.
OData adds the following features to AtomPub, according to an ADO.NET Data Services Q&A page:
- A convention for representing structured data
- A resource addressing scheme and URL syntax
- A set of common query options (filter, sort, etc.)
- Schema describing resource structure, links and metadata
- Payload formats and semantics for batch and “unit of work” requests
- Alternate representations of resource content (JSON)
Microsoft has developed the protocol internally by using it in a number of applications over the last few years: SharePoint Server 2010, Excel 2010 (through SQL Server PowerPivot for Excel), Windows Azure Storage, SQL Server 2008 R2, Visual Studio 2008 SP1 and the .NET Framework. Client libraries are available for .NET, Silverlight, AJAX, PHP, Java, and work is underway to support it in other clients.
Google has a very similar protocol called Google Data Protocol (GData), having the same purpose of extending AtomPub, and it has client libraries for Java, JavaScript, .NET, PHP, and Python. Besides, GData extends RSS 2.0 too. Already as version 2.0, GData is used internally by Google across many services accessing data.
GData, the protocol and the API, is available online and it can be used to program against Google services, the license offering “a perpetual, worldwide, non-exclusive, no-charge, royalty-free, irrevocable (except as stated in this License) patent license for patents necessarily infringed by implementation (in whole or in part) of this specification”, the license being withdrawn only when someone initiates a litigation related to this patent. This sounds like an open license. Microsoft has released OData under Open Specification Promise, making it open to everyone, and there is already a major implementation outside of Microsoft, namely WebSphere eXtreme Scale REST data service. Microsoft invites the community, including Google, to participate in adopting and building OData:
We intend on working with others in the community, including Google, to move the features of OData into future version of AtomPub or other appropriate standards. We encourage Google (GData) to join us in these conversations.
It looks like each of the two companies, Microsoft and Google, has a similar protocol and it is inviting the other to use it. It remains to see who makes the next step in building a common data protocol or which protocol will have a wider adoption.
Community comments
OData or Entity Framework for everyone?
by Ryan Riley,
Re: OData or Entity Framework for everyone?
by Jamie Thomson,
Google Data Protocol License
by Joe Gregorio,
Re: Google Data Protocol License
by Abel Avram,
OData is excellent news
by Tim Acheson,
OData Q&A
by Tim Acheson,
No trust of Microsoft
by Larry Johnson,
OData or Entity Framework for everyone?
by Ryan Riley,
Your message is awaiting moderation. Thank you for participating in the discussion.
If you look at the spec, OData is nothing more than the Entity Framework + ADO.NET Data Services stack with some extensions to Atom. Yes, it's similar to what GData is doing, but it is not really open. The W3c is pushing several other stacks for open, linked data. So now we have more, competing options. As if it wasn't hard enough to get standards spread. I see this as a FAIL and a real loss for the open web.
Google Data Protocol License
by Joe Gregorio,
Your message is awaiting moderation. Thank you for participating in the discussion.
""the license being unclear [the author has not found it].""
code.google.com/apis/gdata/patent-license.html
Re: Google Data Protocol License
by Abel Avram,
Your message is awaiting moderation. Thank you for participating in the discussion.
Joe,
thanks. I updated the article.
OData is excellent news
by Tim Acheson,
Your message is awaiting moderation. Thank you for participating in the discussion.
This is great news for system architects, great news for web developers, and a positive thing for alt.net and the whole Open movement regardless of Microsoft.
I'm a big fan of ADO.NET Data Services. But this is a much broader positive step towards improved Open-ness. I welcome this move. Anybody who is genuinely a proponent of the Open philosophy will welcome this. Those who are at heart anti-MS will not welcome it, of course, because it comes from MS.
OData Q&A
by Tim Acheson,
Your message is awaiting moderation. Thank you for participating in the discussion.
I don't agree with everything in this article. Thanks for the analysis, however. This inspired me to write my own very simple blog post containing just the key facts which I think everybody will agree on, and some links for further information:-
www.timacheson.com/Blog/2009/nov/microsoft_anno...
I would particularly reccomend the official Open Data Protocol Q&A page.
No trust of Microsoft
by Larry Johnson,
Your message is awaiting moderation. Thank you for participating in the discussion.
I don't trust any of Microsoft's open Licences (or the company in general). I do trust Google licenses and the company in general when it comes to providing open software. I may not like all the info google gathers, but at least its upfront about it. Google gives code... MS wants to own/license all code. Microsoft's history speaks for itself. Not to be trusted.
Re: OData or Entity Framework for everyone?
by Jamie Thomson,
Your message is awaiting moderation. Thank you for participating in the discussion.
Hi Ryan,
Microsoft's implementation of OData can be thought of as nothing more than Entity Fx + ADO.Net but don't confuse an implementation with a spec. As the author says WebSphere has implemented OData and that has nothing to with Entity Fx, ADO.Net or .Net in general as far as I am aware.
Regards
-Jamie