Tim B-L: On Moving from the WWW to the GGG

Tim Berners-Lee is an inconic figure for a reason: he's actually rather sharp. This makes his rare blog posts important and interesting - none more so than his most recent one about the Giant Global Graph (GGG):

In the long term vision, thinking in terms of the graph rather than the web is critical to us making best use of the mobile web, the zoo of wildy differing devices which will give us access to the system. Then, when I book a flight it is the flight that interests me. Not the flight page on the travel site, or the flight page on the airline site, but the URI (issued by the airlines) of the flight itself. That's what I will bookmark. And whichever device I use to look up the bookmark, phone or office wall, it will access a situation-appropriate view of an integration of everything I know about that flight from different sources. The task of booking and taking the flight will involve many interactions. And all throughout them, that task and the flight will be primary things in my awareness, the websites involved will be secondary things, and the network and the devices tertiary.

This is probably the best thing I've read about social graphs, not least because it anchors a trendy idea in several pre-existing areas of serious Webby development. (Via Simon Willison's Weblog.)

A Flash of Recognition

Now, where have I heard this before?

I assert that there is something wrong with web-like "rich" formats that aren't hyperlink-able or indexable by search-engines. You could argue that these bugs could be fixed, and Flash is wisely becoming more URI-addressable and view-source-able over time. But it still ain't the Web. It is not hand-authored, easily tweaked incrementally, copy-and-paste-able. It's hardware.

Oh, yes, I remember:

I hate Flash animations even more: they are not only opaque - there is no cyber-there there - they are barriers to my free navigation of the Web and waste my time as they download. In effect, they turn the Web into television.

Well, television is, indeed, hardware.

Blog Perdurability and the Information Commons

Simon Phipps raises an important point: what should be done about corporate blog pages when their owner has, er, passed on (as in to another company)? Sun's solution:

When we started blogs.sun.com, we had a long discussion about what we should do when employees left. The conclusion we all reached, supported strongly by Jonathan Schwartz who attended the meeting, was that they should simply be left in place, merely closed for further changes. Our view was that, if the blog text had been acceptable when it was published, there was no reason a change of employment status should vary that. Not to mention the desire by Tim to preserve URIs. Interestingly, one of Jonathan's motivations for this was also so that people could pick up where they left off when they rejoined Sun!

But I'd go further. I think that companies have a responsibility to maintain the availability of any materials that they make public. This is because of the changed nature of information these days: it's inherently interconnected, and snipping out a weft here and a warp there isn't good for the rest of the data tapestry.

Publicly-available information forms a commons; removing it constitutes a destruction of part of that commons. Ultimately there should be laws against it, just as there are against chopping down historic trees that form part of the landscape commons.