Last November at PDC 09 we announced the Open Data Protocol (OData), providing a way to unlock your data and free it from silos that exist in applications today. OData makes it easy for data to be shared in a manner that follows the philosophy of Open Data and enables the creation of REST-based data services. These services allow resources identified using Uniform Resource Identifiers (URIs) and defined in an abstract data model, to be published and edited by Web clients using simple HTTP messages. OData enables a new level of data integration across a broad range of clients, servers, services, and tools.
This morning during the Keynote at Mix 2010, Doug Purdy announced the re-launch of OData.org and the release of the OData SDK.
The OData SDK brings together a wealth of resources to help developers participate in the OData Eco-system including:
Also announced today at Mix, there are some new OData services available publicly:
How can you get involved in the OData ecosystem? Check out OData.org – Expose OData – and the next time you’re developing an app ask yourself, is there a feed for that?
- The OData Team
Interesting how a post about OData gets turned into a discussion about the viability of keeping VB6 around.
No wonder meetings waste so much time.
To the poster, thanks for the info, look forward to setting up a playground
Never seen such preparation needed to do a relatively simple procedure.
more of the same aand I do mean more.
My site has interesting data to share (online TV shows guide), currently via WCF. May I work with one of your experts to add OData?
send me an email (mike.flasko at microsoft.com) and I'll help you out.
I was able to locate the DSPToolkit, but I cannot find the whitepaper...Any ideas where I can get my hands on this?
Oops nevermind...I see it is in the Custom Data Service Providers.html...I was trying to find a .doc or something.
Thanks a bunch to the whole OData team.
I can quite happily call Http endpoints from VB6. There is nothing that OData exposes that is not accessible via VB6 or VBA.
@Bill VB6 apps can still run quite fine under Windows 7 64bit. I'm not sure why you would think otherwise.
Here is a link to a PDF of the OData specs http://download.microsoft.com/download/B/0/B/B0B199DB-41E6-400F-90CD-C350D0C14A53/[MC-APDSU].pdf
"The dilemma of wether to continue VB6 support is a difficult one for both sides. A company who has legacy VB6 applications shouldn't be forced to replace them just because they are old, if they do the job they were intended for and do it well then there is unlikely to be a business case for upgrading."
This is a great comment, but it's proof that nobody on a forum ever actually reads the comments properly. Nobody said anything about upgrading a particular application or collection of code. This whole conversation started by someone asking about VB6 libraries being developed to work with this technology. The assumption is that these libraries would be used to create NEW VB6 code. (an oxymoron, I know).
Asking whether or not MS should continue to support VB6's development (i.e. publishing VB6 libraries for newer technologies) - I say absolutely not. Those of you who have called it a dead language are right. It is a corpse. But should MS allow companies to continue to use existing VB 1-6 applications/runtimes? Absolutely. It's like a contractor coming to your house to redo your driveway. He says he can do the job, but the new surface won't allow you to park your older car on it... only new cars. That's sorta crap, no?
re: VB6 - has anyone here ever heard of COBOL? and thats not meant in a derogatory sense - just a parallel.
Software development is about Pragmatism not Idealism.
Anyway - does anyone idea what kind of overhead using OData will create? - especially on WCF apps that don't necessarily need an abstract DAL?
Link to the pdf doc.
captcha = 144. gross!