May 25, 2013

The Semantic Web, Part I: Promises, Promises

Over eight years ago I called the Resource Description Framework (RDF) "dead on arrival". I said back then:

The codification of the Resource Description Framework (RDF) in 1999 was eagerly awaited by those interested in describing electronic resources. Targeted to solve the problem of encoding metadata for digital objects using XML so that software could retrieve, parse, and index this information, it seemed like the weapon that would slay the jumbled mess that the web had become…

The weapon turned out to be a space-age laser. It could slay the monster if you could just understand it well enough to use it. Instead of holding to the rule of simplicity that is a hallmark of XML, as I hoped some two years ago (see "21st-Century Cataloging," LJ 4/15/98, p. 30ff.), a group of experts in database design and information retrieval (as part of the World Wide Web Consortium’s standards process) decided to build a structure based on directed labeled graphs. If you don’t understand the last three words of the previous sentence, neither will you understand RDF.

Unfortunately, this will kill it dead. If no one can understand how to properly use it, or if different individuals encode the same information differently (something that is already happening, even among RDF aficionados), then it will never fill the role it was designed to play. In the end, this was much too important an effort to be left to experts.

For those of you taking notes, RDF was to be an essential technical component that would enable the Semantic Web. According to no less of a source than Sir Tim Berners-Lee himself, "The Semantic Web will bring structure to the meaningful content of Web pages, creating an environment where software agents roaming from page to page can readily carry out sophisticated tasks for users." If you think this sounds like science fiction, you’re right. That (and more, much more) was written over seven years ago in Scientific American. How close are we to that? Well, look around. Where is your promised software agent that can scuttle off and perform "sophisticated tasks" for you? I sure don’t have one.

I think the problem is this — the vision, as compelling as it may be, is too far out in front of the reality. Sir Tim Berners-Lee and company have pegged the goal so far above our heads that folks like me who live in Practical Land can’t even see it from here. But this is pretty much where my dumping on the Semantic Web (at least in this two-part series) ends. I’m writing this because I’m actually changing my view on this, and mostly because I see efforts that have set the goal close enough that I can see it. I still don’t know if we’ll ever get to where my agent will take my doctor’s prescribed treatment, then scurry around the web and find providers in my insurance plan nearby who have good-to-excellent ratings and who can offer apppointment times during the holes in my schedule. I assure you, I’m not making this up.

But I’m beginning to really believe that there is something we can achieve with some of this technology that can be useful and worth doing. It is that which will comprise the second part of this series. Stay tuned, and meanwhile, what do you think about the Semantic Web? Can we do it? If so, how, and by when?

PrintFriendlyEmailTwitterLinkedInGoogle+FacebookTumblrShare
Roy Tennant About Roy Tennant

Roy Tennant is a Senior Program Officer for OCLC Research. He is the owner of the Web4Lib and XML4Lib electronic discussions, and the creator and editor of Current Cites, a current awareness newsletter published every month since 1990. His books include "Technology in Libraries: Essays in Honor of Anne Grodzins Lipow" (2008), "Managing the Digital Library" (2004), "XML in Libraries" (2002), "Practical HTML: A Self-Paced Tutorial" (1996), and "Crossing the Internet Threshold: An Instructional Handbook" (1993). Roy wrote a monthly column on digital libraries for Library Journal for a decade and has written numerous articles in other professional journals. In 2003, he received the American Library Association's LITA/Library Hi Tech Award for Excellence in Communication for Continuing Education. Follow him on Twitter @rtennant.

Comments

  1. Atul Kedar says:

    Roy,

    RDF is slowly gaining acceptance in a much smaller scale. Fortunately, microformats usage is expanding because they are much easier to embed on web pages and browsers as well as search engines can process them.

    Looking forward to reading your views on RDF

  2. ivan silva says:

    i think it is possible. it is a big goal and we have to take small bites at a time. i also dream that library metadata will work harder in the future and our catalogs we’ll be much smarter. looking fwd to part 2

  3. Mark says:

    Roy, Mozilla’s Ubiquity was announced last summer. It is a pretty sophisticated software agent.

    see –> labs.mozilla.com/2008/08/introducing-ubiquity/

  4. Roy Tennant says:

    Thanks for the comments, all, and Mark for the link. I’ll check it out. Part II is now up.

  5. Callie Bowdish says:

    I think the Semantic Web is one of the most exciting things going on. However I agree with you that the execution of it is not easily accomplished. Even XML stylesheets are problematic for most people. Getting people to agree on language standards and cooperate seems to be the biggest hurdle. How much do we really want to communicate or do we all believe in the tower of Babel and throw in the towel.

  6. Ari Tenhunen says:

    I don’t think it is possible to bring out semantic web by making or everybody to stick to strict programming and content classification rules. Semantic web requires new, more intelligent and automatic ways of structuring content and extracting meaning and various kinds of knowledge from it. There are some promising approaches. I have seen neural networks based self-learning system to bring out promising results. As I see it, Semantic web has started to happen already.

Speak Your Mind

*

Notify me of followup comments via e-mail. You can also subscribe without commenting.