Tracking change and innovation in the enterprise software development community
Scaling Scrum
in the enterprise?
ScrumWorks Pro
can help.
Start a trial today
Free Book Offer
SOA Demystified
$40 Value
QCon London 2010!
March 10-12, 100
Speakers, 80 sessions,
"THE" team leads and,
architects conference.
Posted by Abel Avram on Nov 18, 2009
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.
Learning to be a Good Product Owner: Foundation Skills
The 5 Mandates of Software Development Teams - Presto Manifesto
Understand and Align BPM, SOA, and Lean Six Sigma: 43 page IBM Redguide
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.
""the license being unclear [the author has not found it].""
code.google.com/apis/gdata/patent-license.html
Joe,
thanks. I updated the article.
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.
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.
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.
Brian Marick takes us through a quick tour of the most important values and challenges to adopting Agile successfully (they aren't the typical challenges and values we hear in the community).
The line between development and architecture is tricky. Does it exist at all? Is an ivory tower actually needed? There's a balance in the middle, but how do you move from developer to architect?
The word 'authority' sometimes produces an allergic response in hard-line agilists. Freedom and authority – both are bad if misused and both are good if used in right spirit for a noble cause.
"Getting Started with Grails" brings you up to speed on this modern web framework. Companies as varied as LinkedIn, Wired, and Taco Bell are all using Grails. Are you ready to get started as well?
Those familiar with only ITIL V2 often scoff at the thought that ITIL could serve as a governance framework for SOA. With ITIL V3, the focus of the framework shifted towards service-orientation.
SpringSource CTO Adrian Colyer discusses AspectJ, SpringSource's dm Server and tc Server products, OSGi and Scrum.
Heroku's Adam Wiggins talks about Rails, Background Jobs, Add-Ons, Ruby, and how Heroku manages to work around Ruby's inefficiencies using Erlang and other languages.
For Grady Booch the foundation of a good architecture is patterns, SOA being just one of many patterns. In this Second Life presentation, Booch attempts to bring more clarity on what architecture is.
6 comments
Watch Thread Reply