This isn't necessarily a new idea, but it helps to have a visual metaphor to get past the API-geekspeak and look at where we're really going. I know that OmniDrive ("The Universal Web Storage Platform") is already planning on integrating with Flickr as a "storage device"... so what happens when you literally can hook up to remove stores of data, media and so on, that aren't restricted to FTP and SAMBA and so on, but typical web APIs? What happens when you can access event data on Upcoming.org not using an XML API, but by simply consuming the microformatted XHTML pages? Essentially, any webpage or website becomes a data store and an application, all rolled into one. It's curious that when I first started creating this graphic, I wanted to illustrate the idea of networked harddrives -- but that get their data from web services. Looking at it now, if each name had ".app" on the end, these would be a collection of desktop executables. So, with the line blurring further between representing applications and data, we start to glimpse just what a desktop-enabled web service access interface might actually look like...
💬 Comments from the original post