A few weeks back I made my first trip to Dublin to attend XTech 2008 (Live blogging? I’ve heard of it). The subtitle of the conference was ‘the web on the move‘ and in my ignorance I thought that this simply referred to web access on mobile phones (a favourite topic of mine at the moment).
On arriving it was obvious that the multiplicity of meaning in that phrase was completely lost on me. The organisers had three topics in mind:
The future of the web
How the web is moving forward (Web 3.0, if you like). To many attendees, the Semantic Web is that future.
Data portability
Our data is ever more portable in the sense of intelligible file formats, but there is now the problem of moving your data around when the Web 2.0 world insists on locking it into proprietary silos. How do we solve this problem?
And yes, web clients and servers that move
Fire Eagle. More on that later.
It was only when I had been around for a day or so that I realised that XTech had started life as an XML conference some years ago. That change of emphasis was not to too pleasing to one attendee I met in the coffee queue. She was a lecturer specialising in XML for an Irish university. She heard one speaker say something like ‘We want this to be simple, so obviously no XML…’. Her heart sank.
XML, JSON, s-expressions… we are all the same under the skin. Can’t we just get along?
Anyway, a mere month after the event, here are my personal highlights from Dublin…
Simon Wardley
Simon Wardley is, amongst other things, a professional keynote presenter, and he likes to smash convention. His 408 slides in 43 minutes covered innovation, de Architectura, commoditisaton, things-as-a-service and ducks.
The most enlightening section for me was the discussion of invention versus innovation. I hadn’t grasped the difference between these two before, and I’m meant to be working in an innovation team. Apparently, invention (or discovery) is the eureka moment. From this comes an idea, and the innovation is the first(-ish) attempt to put the idea into practice. Simple, really.
Simon has a wealth of experience in the IT industry and was able to share a few war stories in the pub later. He told us of his time working for a bank where the atmosphere was so competitive that rival development teams would trash each other’s source code repositories. Makes me glad to work in the pink palace.
JavaScript: The Good Parts
Javascript has a bad reputation amongst many developers. I have to admit that, until recently, I shared the widely-held belief that Javascript was the devil’s own language (rather than, say, Japanese)
Douglas Crockford (who has been described as “the Yoda of Javascript”) made a very strong case that this reputation is undeserved. In fact, Javascript-the-language (as distinct from Javascript-the-crufty-web-wrangling-system) is a thing of rare beauty. It was the first language to introduce the concept of the closure to the masses. It has a super-cool prototype-based inheritance. Oh, and it’s the world’s most popular programming language, at least by number of installed interpreters.
But Javascript has its bad parts (hence the name of this talk and Douglas’ new book). There are all sorts of gotchas to do with the arcaner parts of the language syntax. Douglas has managed to address these by writing jslint which defines a sane subset of Javascript and validates your program against it, warning you if you stray into dangerous syntactic territory.
He told me that he may spin off this more narrowly-defined version of Javascript into a new language. He has yet to devise a cool name for it — Secure Javascript is what he’s calling it at the moment on account of its lack of dangerous global variables, but it’s one to watch whatever it’s going to be called.
A video is available of a similar talk he gave last year.
Why you should have a website
It was standing room only for this talk by one of the great minds at the W3C, the Albanian Amsterdamer Steven Pemberton. He was laying down the law. Several laws, in fact.
The first was Moore’s Law. Steven talked about its consequences in everyday life. I didn’t realise my phone was as powerful as 30 Crays (although if you’ve ever waited for the web browser to start up on an N95, you may doubt it).
The next was the slightly lesser-known Nielsen’s Law (as in Jakob Nielsen) which says that available bandwidth will double every year or so. Steven showed graphs of the bandwidth available from his ISPs over the years, which seemed to bear this out.
But the interesting law for this conference was Metcalfe’s Law. That’s the one that says the value of a network is proportional to the square of the number of users in the system.
Steven’s contention was that Web 2.0 sites which lock you into their network effectively cut the web in two, hence halving the value of each half and so quartering the value of the whole network. Facebook is an obvious case of this phenomenon, although Flickr was used as example in the discussions after the talk, much to the annoyance of the Flickrers in the audience.
So, onto what you could call Pemberton’s Law. Well, more of a vision than a law. We should each have our personal website on our own little webserver (an actual low-wattage piece of hardware in our houses under the stairs or somewhere) where our data lives. That data is marked up semantically (RDFa, to begin with), and aggregators make use of that extra richness to create new and exciting services. Our data stays where it belongs, and there is no lock-in. The network achieves its full ‘Metcalfe value’. Welcome to Web 3.0.
The BBC Programmes Ontology
Tom Scott and his gang at the Big British Castle are doing a lot of work on the semantic web, and in a domain that I like to think I know something about - British telly and radio! So I thought I had better make a beeline for their talk.
According to the beta BBC Programmes site, their aim is to ensure that every programme the BBC broadcasts has a permanent, findable web presence. But that’s only the start of it, as they used to sing on a certain show in the seventies. Here’s the document that describes the ontology. Jolly impressive, and Creative Commons to boot. Here’s all you need to know about ‘In the Night Garden’, for example. And again, this time in all its gory semweb detail. You can see more of the fruits of their labours at the http://bbc-programmes.dyndns.org.
The new Freesat set-top boxes in the UK have an ethernet connection as standard. Given that Freesat is half-owned by the BBC, I suggested to Tom that the data in the programmes database would make a killer EPG. He didn’t disagree. I think it’s only a matter of time.
Fire Eagle
Evan ‘rabble’ Henshaw-Plath (the Obi-Wan of location-based services?) spoke about Fire Eagle from Yahoo Brickhouse. I can’t really describe it any more clearly than he does:
It’s a system which lets you collect your location from any number of sources, such as your cellphone, and then provide that back out to other applications. Fire Eagle then lets you fuzz your location and control who is using it. Share the city you’re in with dopplr, the neighborhood with facebook, but let the taxi locator see your exact location.
There’s quite a bit of buzz around this service, as evidenced by the haste with which attendees made their way to the front to receive developer invites. I’m pretty sure we’ll be making use of Fire Eagle before long — it’s a great idea.
CHIP Project
As part of the lightning 20:20 presentations (20 slides, 20 seconds a slide — a very entertaining format) Natalia Stash talked about the brilliant CHIP project at the Rijksmuseum in Amsterdam. Using a wealth of semantically-enriched data, users of the CHIP software can plan a tour around the museum on their PC, with the software providing recommendations about exhibits. The tour can then be downloaded to the user’s PDA, for use whilst wandering around the building.
The web, as they say, on the move.
Other random observations
- Rock shandy doesn’t contain any shandy. Or rocks.
- Erlang is starting to make inroads into the web-development mainstream. See CouchDB.
- Mapstraction is an abstraction layer over of various javascript mapping interfaces. It does what it says on the tin. I like that.
- I haven’t marked this up in RDFa, therefore I’m partly responsible for the slow take-up of Web 3.0. Sorry about that.
- Esse est percipi.