May 20, 2010
When I say I'm developing an "open" API, what does that mean to you?
To Facebook, it means something where you can get at some of your own data, as long as you abide by their restrictions on what you can do with it.
To Twitter, it means something where you get back what you put in.
To Flickr, it means something where you can get every single piece of data that you've ever put in the system, enriched by any value that Flickr can provide.
To Google, it means something where you can get back what you put in, you can host your own version of the API on your own server, and your server has exactly the same status as any Google server has, and that Google's servers and your server will interact and work as a system.
We need new words. Words that have more specific meaning--which encompass the broad idea of "open", yet remain accessible and recognizable by everyone. Federated is a good word, but it's possible to have a closed, federated system.
What words should we use?