Why the Semantic Web Marketing Message Has Failed

So some guy writes why the semantic web will fail and ends up on Slashdot. How slashdot picks their articles, I'll never know. The article is pure opinion and guesswork (as all predictions seem to be), and it's perfectly OK for this guy to blog his opinions.

I'm not going to argue that the semantic web (that's *small s* semantic) will succeed, although I think it will prove useful in a large sense in some form, even if that form isn't RDF. I think what's really telling about the doom and gloom post is that the marketing message of the semantic web has failed.

For example, a quote from the blog post:

> The Semantic Web will never work because it depends on businesses working together, on them cooperating

Where, in all of the W3C's semantic web literature does it says that companies must work together for the semantic web to succeed? I think this is one of the biggest misinterpretations about the semantic web. For some reason, people think that the semantic web requires these large agreed upon ontologies before anything useful happens. Not only is that near impossible (for anything but the most generic or free form terms and definitions) but as we all know, specifications born out of committee have an awfully hard time meeting the pragmatic needs of the masses.

For the semantic web to succeed, the W3C doesn't need more technical specifications (although a new RDF XML serialization would be nice). Instead, the W3C needs to completely revamp its marketing message. For instance, distance the semantic web from AI. AI, no matter how promising, leaves a bad taste in your mouth. We need to completely deny any relationship to AI. Secondly, the W3C needs to rebrand the semantic web as "Simply Putting Your Database On The Web. No More, No Less. Anything Else Is Purely Serendipity." Thirdly, the W3C needs to really drive home that the semantic web will succeed *only if* it is not built with large top down ontologies.

So repeat after me: "The semantic web is just an effort to help expose the database that you already have to the web as RDF. Primary keys become URIs, and the intersection of a row and a column is a triple."

Or, to put it another way:

Problem: I have data, most likely in a relational database, that I need to get on the Web.
Solution: Expose that data as RDF. URIs are the primary keys for the data.

Popular posts from this blog

Lists and arrays in Dart

(This is Part 3 in a series about Dart. Check out Part 2, Function in Dart .) Warning : We expect the Dart libraries to undergo potentially sweeping changes before Dart goes to alpha. This document is relevant as of 2011-12-22. Intro Dart is a "batteries included" effort to help app developers build modern web apps. An important "battery" is the bundled core Dart libraries, providing common and rich functionality. Dart is building a solution for large, complex web apps, and providing well tested, integrated, and common libraries is key to helping a web app developer be more productive out of the box. The Collection libraries are a crucial set of APIs that Dart developers get for free. Much more than simple arrays and maps, the Collection library includes standard ways to filter, iterate, inspect, compose, and sort your data. This post specifically looks at List<E> , Dart's ordered, indexable collection of objects. Aside: The Dart project is lucky
Read more

Converting Array to List in Scala

Now, this has to have a built-in somewhere in Scala , because it just seems too common. So, how to convert an Array to a List in Scala? Why do I need this? I needed to drop to Java for some functionality, which in this case returns an Array. I wanted to get that Array into a List to practice my functional programming skillz. **Update**: I figured out how to convert Arrays to Lists the Scala way. Turns out it's a piece of cake. val myList = List.fromArray(Array("one", "two", "three")) or val myList = Array("one","two","three").elements.toList The call to elements returns an Iterator , and from there you can convert to a List via toList . Nice. Because my first version wasn't actually tail recursive, what follows is a true tail recursive solution, if I were to implement this by hand. The above, built in mechanism is much better, though. object ArrayUtil { def toList[a](array: Array[a]): List[a] = { d
Read more

Null-aware operators in Dart

Image
Three new language features just landed in the latest dev channel build of the Dart ! Collectively known as null-aware operators , these new features will help you reduce the code required to work with potentially null objects. I'm excited for these new abilities, because typing less is always a good thing. Read on to learn more, and be sure to try these new features on Dart Pad . ?? Use ?? when you want to evaluate and return an expression IFF another expression resolves to null. exp ?? otherExp is similar to ((x) => x == null ? otherExp : x)(exp) ??= Use ??= when you want to assign a value to an object IFF that object is null. Otherwise, return the object. obj ??= value is similar to ((x) => x == null ? obj = value : x)(obj) ?. Use ?. when you want to call a method/getter on an object IFF that object is not null (otherwise, return null). obj?.method() is similar to ((x) => x == null ? null : x.method())(obj) Yo
Read more