Posted on 09-25-2011
I’m working on reviewing various APIs as part of my database industry overview, where I’m trying to understand the different approaches to delivering database platforms using web APIs as the primary interface.
One of these database platforms is Database.com. I really like what SalesForce.com is doing with Database.com, but I take issue with their section declaring Database.com as an open platform. SalesForce.com claims because you can access Database.com from any language, any platform, and any device through standards-based APIs, it is "open".
I think many folks in the enterprise space truly believe this makes something open. All it means is, if you have the money and approved credentials, you can access. If I launch a database on Database.com it is open for "me" to access, and those I give access to. And yes, since it uses REST I am "open" to access via any language or platform I choose. But I'm sorry, that does not make it "open".
I recommend SalesForce.com take a look at Freebase. All the data contained in Freebase is licensed by a Creative Commons Attribution License, which means that it's free for you to browse, query, copy, and even use the data in your own systems or software, even for commercial use, all you have to do is attribute it back to Freebase.
Anyone has access to use and contribute to Freebase, as well as use any programming language or platform to access the data available on the platform. Access to data is only one aspect of "open", developers must also be freely open to use and contribute to it, as the community sees fit.
As much as I love and evangelize the power of the API, an API alone does not make systems or data open.
comments powered by Disqus
Winning in the API Economy
|Download as PDF|
Latest Blog Posts
- Publishing Your APIs To Product Hunt
- Providing Users With Reciprocity Tools So Important Intuit Purchases itDuzzit
- Bing Developer Assistant for Visual Studio Delivers Relevant API Code
- Average Number of APIs Used In A Modern App
- An APIs.json Collection Of API Resources Across Your Public, Partner Or Internal Resources
- One Possible Reboot Of The API Stack
- How Are Dev Shops In Chicago Using APIs? A Talk With Bryson Pouw At Blaze Portfolio
- Every API Provider Should Have A Logo And Branding Page
- What Is An API First Strategy? IT architecture And Catalyst For Engagement
- The Speed Of Federal Government When It Runs On Github
- Swagger, APIs.json, And Review For The New Developer.Trade.gov
- Student, Instructor, Classroom, Class, And Course API Planning At BYU
- Can You Add My API To Your Website Listing?
- Adding Google To List Of API Deployment Companies
- What Is An API First Strategy? Adding Some Dimensions To This New Question
- The Five Month Journey Toward A Stable APIs.json Discovery Format
- How Are Mobile Dev Shops In Chicago Using APIs? A Talk With Dave Devitt At SYDCON
- An API Case Study Format From Google Cloud Platform
- Next Stable Version of APIs.json + APIs.io Is Ready - Are Your APIs Discoverable?
- Expanding API Gateway Connectors Into A World of API Deployment Startups
- Where The Good IPAs Are In Chicago While At API Strategy And Practice In September
- The Blog For Your API Is The Most Important Signals You Can Send
- Public APIs Are Tough When You Are In A Tightly Controlled Industry
- Give Me A URL To Request Then Store My API Keys In My Private Github Repo
- Mapping The World Of Internal APIs Via Rogue API Registry