Ode to OData

Are you using OData? If so, you’ll be happy to know that OData Version 4.0 and OData JSON Format Version 4.0 have now been standardized by OASIS (Organization for the Advancement of Structured Information Standards). 

The nice thing about standardization is that it provides a level of stability to a technology. With companies like Microsoft, Citrix, IBM, Red Hat, and SAP behind the push for standardization, you can expect a good outlook for OData beyond just Microsoft.

OData is a protocol that was created to provide the ability to manipulate data via a website in much the same way that JDBC and ODBC are used. Built upon the AtomPub and JSON, the protocol provides features such as allowing for working with typed and untyped values. It provides a defined way to Create, Read, Update, and Delete (CRUD). Ultimately, OData provides the means for consuming data on the web.

While Microsoft initially defined the Open Data Protocol (OData), they have once again handed their work over to the standards bodies to help solidify the standard and to allow the industry more control on its future.

(Yes, I said Ode to OData and I've not written any sort of poem. Rather, I've left that for you to do. Feel free to post your best OData poem in the comments.)



Blog Categories

Blog Archives

Comments

  • There are no comments yet. Be the first to comment!

Leave a Comment
  • Your email address will not be published. All fields are required.

Top White Papers and Webcasts

  • When individual departments procure cloud service for their own use, they usually don't consider the hazardous organization-wide implications. Read this paper to learn best practices for setting up an internal, IT-based cloud brokerage function that service the entire organization. Find out how this approach enables you to retain top-down visibility and control of network security and manage the impact of cloud traffic on your WAN.

  • Following an IT incident through to resolution is more than just acknowledging an alert and restarting a server. The recent State of On-Call Report found that it takes most companies an average of 10-30 minutes to resolve an incident with an average of 5 people involved. Imagine how much money and time companies are spending to deal with incident resolution. But what if you had a tool that offered solutions baked in? Or a tool that sent alerts to the right person or team every time? These are the kind of …

Most Popular Programming Stories

More for Developers

RSS Feeds

Thanks for your registration, follow us on our social networks to keep up-to-date