odata

Welcome to the new OData.org!

There is a vast amount of data available today and data is now being collected and stored at a rate never seen before. Much, if not most, of this data however is locked into specific applications or formats and difficult to access or to integrate into new uses.

Public data is often unfortunately held private or needlessly buried behind random, inefficient, and cumbersome interfaces.

Open Data is a general movement for all types of data, scientific or other, enabling data to be accessible programmatically for public or commercial use.

The Open Data Protocol (OData) provides a way to unlock your data and free it from silos that exist in applications today, making it easy for data to be shared in a manner that follows the philosophy of Open Data. OData enables a new level of data integration across a broad range of clients, servers, services, and tools.

The new odata.org web site is your one-stop shopping for all things related to OData, including:

  • The OData SDK, including sample OData services, client libraries for most platforms, server libraries for the .NET Framework and great samples.
  • A great overview of the OData protocol, both from the technology and the scenario points of view, as well the official specifications themselves.
  • A comprehensive set of articles on how to get started with OData across platforms and languages.
  • A representative set of OData producers for you to use to test your client-side tools and to get a feel for the range of uses that OData supports.
  • A bunch of OData consumer tools and technologies for you to use against existing OData producers or your own new ones.
  • The OData blog manned by the Microsoft Data Services team and containing OData-related articles and links for OData everywhere.
  • A growing list of Frequently Asked Questions about OData-related tools and technologies.

Another key goal of this site is to foster the OData community, and to be as open and responsive to community suggestions as possible. To make this a reality we plan to create and host:

  • A Mailing list and archive.
  • A publically editable Wiki.

But we want your opinion, is this the right thing to do? 

At the same time we are looking to engage with IETF and W3C to explore how to get broader adoption of the OData extentions & conventions.

If you have any ideas please leave a comment or send us your feedback.

 

8 comments for “Welcome to the new OData.org!”

  1. Posted Friday, March 19, 2010 at 9:36:40 AM

    I would definitely encourage you to engage with the IETF or W3C regarding the future development of this specification.

  2. Posted Friday, March 19, 2010 at 1:32:54 PM

    Well done for basing your work on existing open standards such as HTTP, AtomPub, XML, JSON, and using Creative Commons.

    A few suggestions:

    1. Active Transparency. Blog posts should be by individuals with real names who are willing to put their reputation/identity on the line for their words, not "Administrator". Also, please post an "about" page listing the individuals who have conceived, created, and maintain OData, as well as any organizations who are providing funding.

    2. More open licensing. Please consider using a more open license for your work, such as Creative Commons Attribution, or better yet, Creative Commons Public Domain / CC0. microformats.org has successfully used the latter since 2007 (see http://microformats.org/wiki/Microformats_Wiki:Copyrights ). In addition, please consider adopting the Open Web Foundation Agreement ( http://openwebfoundation.org/legal/agreement/ ) for all your specifications.

    3. Create a MediaWiki install at http://wiki.odata.org/ or http://odata.org/wiki/ to enable and encourage a growing open community to contribute to the OData effort.

    Thanks for your consideration and your contribution to open web technologies.

    Tantek Çelik
    disclosure: microformats.org community admin, Open Web Foundation board member

  3. Gravatar of Chris DavisChris Davis
    Posted Sunday, March 21, 2010 at 4:55:36 PM

    In the FAQ, it is mentioned that the "protocol is intended to align with the Open Data movement". However, much of the open data movement is already using the W3C standards of RDF, OWL, and SPARQL, which have been designed explicitly for the purpose of linking open data. If as hinted at in the FAQ that this is not just a Microsoft thing, then why do these standards not seem to be mentioned anywhere on this site?

  4. Posted Wednesday, April 14, 2010 at 8:29:39 PM

    I am also interested in RDF compatibility like Chris Davis.

    If Microsoft is pursuing an open standard, it would thrill many across the world to see compatibility at some level with the existing open data standards that have been in development for many years.

    For a short list of producers of RDF for any unfamiliar readers, see:

    http://esw.w3.org/TaskForces/CommunityProjects/LinkingOpenData/DataSets/Statistics

    There are already .Net RDF APIs, but to see an official one would be quite a boon to the semantic web movement in general. It would also be likely to bring in a additional consumers to this API and major positive attention to Microsoft's openness initiatives in general.

    These are just this commenter's humble opinions. Thanks for opening this forum for feedback.

  5. Gravatar of Arunav SikderArunav Sikder
    Posted Wednesday, August 11, 2010 at 8:49:25 AM

    I was looking at the prospects of OData services and integrating it with BCS so that SharePoint can also become a consumer of OData than just a producer. Do you guys have plans along these lines?

  6. Posted Thursday, August 12, 2010 at 8:48:48 AM

    I like a 3 suggestions from Mr.Tantek Çelik and first of all regarding the Active Transparency.

  7. Posted Saturday, August 14, 2010 at 4:00:59 PM

    I'd like to ask on how to engage with the IETF or W3C regarding the future development of this specification? Do you have entries of it here?

  8. Posted Saturday, August 28, 2010 at 11:19:56 AM

    Open data is really helpful for commercial use. Not only public.

Post a comment