njyx

See Kin Lane's take here: http://blog.apievangelist.com/2012/07/12/dont-forget-about-t...

The programmableweb profile for the API is here: http://www.programmableweb.com/api/walgreens-quickprints.

Who knew that IRC keep APIs running...

I guess the model needs to be right so everybody along the way gets paid, then people may step up.

Pretty interesting way to think of twitter - kind of a message bus.

I'd say platforms like stackmob which create mobile APIs + wordpress, drupal etc. which make it easy to add an API to those + then platforms like 3scale, mashery etc. which help manage access.

We're based in Barcelona - We'll do an office exchange if the counter location is right!

You arguably don't have to go that far from home I guess - depending on where you live - just needs to be "away" and a great place (and have great Internet!)

Genius move!

The US definitely seems to be leading here - makes more sense to open data than to try to provide more and more different UIs that people need (iPhone, Android, ...). Of the APIs on programmable web in that period almost all were US, a couple were UK and a couple we Canadian.

Further back in time there are other countries also though - and a lot of the Scientific APIs were European.

I think this will end up happening - Amazon already lets you suck out it's catalogue and push affiliate sales back to it. You could likely build very sophisticated niche virtual retail sites if all the bricks and motar data was there also.

Interestingly in the survey the number of ecommerce APIs was actually a lot lower than we thought it would be. This might be a blip in this "generation" of APIs, or that it's simply hard to do still.

Yes, agreed - but the total number of APIs listed is a little over 6000, so it's a reasonable sample to some extent. There are a lot more APIs out there which aren't public / listed - so it's hard to account for those.

Yep - here: http://www.programmableweb.com/api/programmableweb

Yep, I guess that's a big part of what's missing still. Mass use of platforms to make it easy for anybody to do this.

This makes total sense for the data storage providers, but it's also clearly not an equilibrium in the long run since it'll be economical for all of the data to replicate to multiple locations (where each group of users has privileged data access rates).

Looks very cool - do you normalize based on the number of developers per project?

Would be interesting to know what people think of these guidelines and any good/bad API T&C's experiences people have had.