During the November issue of Semantic Web Gang podcast, we also talked about DBpedia, which led me to share new thoughts about Linked Data. And more specifically, two things:
- my growing concerns that adoption of Linked Data is going slower than expected (an observation I will test further) given the R&D investment and focus of a large community including the inventor of the web and the W3C, which led us to anticipate a faster growth curve.
- the possibility this slow adoption rate might be due to inherent flaws in the design of Linked Data. Even if adoption is in fact rapid (which I don't think it is), I am nonetheless concerned those flaws could also limit the potential of Linked Data to "turn the Web into a database", as per the main promise associated with the Semantic Web by its apostles (to this day...).
My thinking on this topic has further progressed following good discussions with a number of people including Bill Roberts of Swirrl, Ian Davis of Talis, and Pawel Lubczonok of Thought Express (I have a business relationship with Thought Express, although the views expressed here are my own entirely, developed prior). I will expand on this in the future as I keep learning about the flaws I suspect (please share your inputs either through blog comments or by emailing me at gregboutin -AT- gmail.com).
In the meantime, I would recommend some good blog posts closely related (or even directly related, in the case of Bill's post) to all of the above:
- Delivering Linked Data quickly by Bill Roberts of Swirrl
- What’s in a name? And the Linked Data Police by Richard Cyganiak of DERI (see my comment there too)
And some other tidbits I came across on the adoption of Linked Data:
- This Semantic Web Job’s For You, by Jennifer Zaino, SemanticWeb.com Contributor - showing 3 ads only on a popular start-up job board for jobs requiring RDF skills, 15 quoting the "Semantic Web" and 3,000 for "web 3.0" (a much broader term including alternative approaches to realizing the Semantic Web - and also some complementary ones, although those would probably make a direct reference to Linked Data skill requirements)
- Observing the Growth of the LOD Cloud, by Alexandre Passant, which shows that about 55 sources have joined the Linked Data cloud in the past 12 months, and about 25 in the 12 months before that. The conclusion seems to be that there is growth. Although technically, that's true, I find it hard to see the addition of such a small number of domains to the cloud as the explosion that we were expecting, 7 long years after Tim Berners-Lee described his vision for the Semantic Web in Scientific American, and almost 2 years after he declared the Semantic Web "open for business"
- Machine-Readable Web Still a Ways Off, an acknowledgement by Tim Berners-Lee himself of the slow adoption of Linked Data.
As some in the Linked Data community are quick to attack the reputation of commenters not sharing their enthusiasm unequivocally, let me remind those that asking questions is very much a constructive (if an unrewarding) job, helping strenghten the efforts and push them in sometimes new and better directions.
Certainly, offering solutions is important, and I try to wherever I can, but it should not be a pre-requisite to highlighting some possible flaws. If someone had done that for subprime mortgages prior to the financial crisis, we would not have gone through the mess we did. Assuming anyone listened.
I have been an unbiased (I believe) fan of all semantic web efforts from the start of my involvement (see the early posts on this blog), but with time I have come to believe that Linked Data might have some flaws preventing it from delivering on the promised benefits. Certainly it does offer interesting possibilities and advances, but so did the Concorde!
Is Linked Data a new Concorde or Artificial Intelligence market failure in the making? I don't know and wouldn't go as far as to assert that. But I believe it's time we think deeper and take a closer look at possible limitations in the design, to ensure a positive ROI on linked data efforts.
The benefits of Linked Data have been very slow at materializing, and I'm not sure we should buy the argument that it's hinging on yet another R&D effort or the adoption of those standards by more web players. If it's going to be of any use, it should be useful today, not in another 7 years.
To be continued.
Related articles by Zemanta
- What's in a name? And the Linked Data Police (dowhatimean.net)
- Linked Data and the Semantic Web: What Are They and Should I Care? (slideshare.net)
- The end of Search? Linked Data, Semantic Web & thoughts. (webr3.org)
- Querying Linked Data with SPARQL (slideshare.net)
- Preparing Yourself for Web 3.0, LOD and 2010+ (webr3.org)
- Justifying the cloud (accmanpro.com)
![Reblog this post [with Zemanta]](http://img.zemanta.com/reblog_e.png?x-id=686aeb11-41e5-4490-9d25-fa26405ad284)
![Reblog this post [with Zemanta]](http://img.zemanta.com/reblog_e.png?x-id=9d7872c0-2599-4fd1-8174-19f27f25beb7)
![Reblog this post [with Zemanta]](http://img.zemanta.com/reblog_e.png?x-id=92a94a9a-3992-4e71-8c2d-a7691334f2d9)
![Reblog this post [with Zemanta]](http://img.zemanta.com/reblog_e.png?x-id=38c1e238-fa26-423b-baf9-9b30715a4aec)
![Reblog this post [with Zemanta]](http://img.zemanta.com/reblog_e.png?x-id=79039acc-2c20-42b2-9f26-b426b2799725)
![Reblog this post [with Zemanta]](http://img.zemanta.com/reblog_e.png?x-id=2fd6cc5c-8b2d-409b-bccb-0ae9552d39a9)
![Reblog this post [with Zemanta]](http://img.zemanta.com/reblog_e.png?x-id=f6e2234a-3a66-4fe3-b506-102149d01f8c)
![Reblog this post [with Zemanta]](http://img.zemanta.com/reblog_e.png?x-id=0b45e4f6-6906-43c9-9dd2-1e2702093beb)
![Reblog this post [with Zemanta]](http://img.zemanta.com/reblog_e.png?x-id=1b7bc2cb-4367-48c6-a19f-628548271b2a)
![Reblog this post [with Zemanta]](http://img.zemanta.com/reblog_e.png?x-id=7da1377e-e2e6-47dc-b587-26253a07b89a)
![Reblog this post [with Zemanta]](http://img.zemanta.com/reblog_e.png?x-id=72e7e102-96ae-4e2f-81be-08fd125aedf4)
![Reblog this post [with Zemanta]](http://img.zemanta.com/reblog_e.png?x-id=e7a99aa0-445c-4895-acfb-3a2fbddc4f15)

Recent Comments