« Essay: Is big business heading for mass extinction? | Main | Ecosystem 1 - Physical technology meets social technology »

The puzzle of semantic web adoption

I am a believer in the rise of the web of data. In fact I am CTO of Talis which is investing heavily in semantic web technologies. So don’t take this the wrong way but I can’t help but feel the semantic web community is ignoring a vital part of the semantic web jigsaw and this is creating a major credibility problem between it and large parts of the technology community. I am concerned because I think that the semantic web currently lacks two critical things that drove mass adoption of the web.

To be fair the W3C has created a semantic web outreach group and Talis has two representatives on this, so we are doing our bit to help to spread the word :-) but this is only going to really work if the semantic web community really understands what the major missing pieces are for mass adoption. Today, looking at the conversations in the semantic web community, I don’t think the real barrier is being seen clearly.

So here is my personal view on what is going on here.

Many in the semantic web community have been concerned mainly with the rightness of the technology and not the utility of the technology. That is fine for the invention process but badly wrong for the adoption process. Just ask the inventors of the Beta Max :-) . It doesn’t matter how right you are!

Adoption is a strong function of day 0 utility. That means: “What can I do better today by using semantic web technology rather than existing technology?” You can’t use the argument that when everyone has adopted RDF it will be really really useful, because the people who need to adopt the technology in order reach that critical mass of RDF won’t do it because of belief in the semantic web vision. These adopters are pragmatic and need technology to give them advantage today not in 5 years. Network effect based features always have this kind of initiation problem.

To overcome the network effect initiation problem there needs to be day 0 value to drive adoption until the network effect kicks in and takes over as the main reason for adoption. In short there needs to be a killer application of the technology.

What is the semantic web killer application?

So my question to the semantic web community is what exactly can I do far better today with the more unproven semantic web technology than I can today with more established technology such as agreeing simple XML standards?


A clear answer to this question is vital. 

I actually think that for most specific instance of usage you could achieve faster adoption and lower risk through de facto standards agreement with a simple XML approach. Take RSS.  Was this a success because it was RDF or because is was the de facto emergence of a simple standard based on its raw day 0 utility, not some far off network effect based value. It is not a semantic web killer application.


So it seems to me that semantic web adoption is a very different problem to the web of documents in the early days.

The web had 0 day utility. Many people will remember that feeling of seeing the web for the first time and knowing that you could easily publish any thing you liked and the whole world could read it instantly, mind blowing.
You didn’t need any special tool to write a HTML document, doing it by hand was easy enough.

The web was its own killer application. The semantic web is not.

But the web had a piece missing. You could start at any resource and navigate the links but you couldn’t search the space itself to find a good starting resource in the first place. This meant that as the web grew, more and more of the content could not in practice add any extra value to a users experience.
Of course the missing piece was the search engine. This allowed a user of the web to query the whole space and now every document no matter how obscure could potential enrich a users web experience.
I don’t think it is right to characterise this as something missing from the architecture of the web because search engines could be layered on top and that is better than building in complexity to the core standards, but from a users point of view, the real potential of the web of documents could not be realised until it was possible to query the whole web space.

We talk about the semantic web in terms of a web as database. But where is the database engine? Google is the free text engine for the web of documents. Where is the equivalent for the semantic web? 

So the semantic web appears to have little day 0 utility over a specific approach, it is not its own killer application and it lacks the ability to query the semantic web information space itself.

This may appear a provocative conclusion, I don’t know. But is it correct? If it is then who is doing what about it?

If true does this mean the semantic web will forever be a dream?
No I don’t believe that. But I do believe it changes the way we should think about semantic web adoption.

For example, it would be crazy to believe all data must be in RDF, that would create a huge barrier. Instead the question should be how RDF and other data approaches can work together to create a powerful web of data, the superior value of the RDF approach should over time increase the amount of RDF versus other approaches.

But I think the single biggest blocker on web of data adoption and by extension, the semantic web, is the lack of ability to query the whole space. Where is the database engine for the semantic web?



Posted on Friday, December 8, 2006 at 09:39PM by Registered CommenterJustin Leavesley in , , | CommentsPost a Comment

Reader Comments

There are no comments for this journal entry. To create a new comment, use the form below.

PostPost a New Comment

Enter your information below to add a new comment.

My response is on my own website »
Author Email (optional):
Author URL (optional):
All HTML will be escaped. Hyperlinks will be created for URLs automatically.