- My eBooks
Current song: Loading ...
About Stephen Downes
About Stephen's Web
Subscribe to Newsletters
Privacy and Security Policy
Web - Today's OLDaily
Web - This Week's OLWeekly
Email - Subscribe
RSS - Individual Posts
RSS - Combined version
JSON - OLDaily
Stephen's Web and OLDaily
Half an Hour Blog
Google Plus Page
Huffington Post Blog
National Research Council Canada
Research Topics, Research Wiki, Code
All My Articles
Whither the Semantic Web
Posted on SemanticWeb Discussion grouo, June 17, 2004
I have been and continue to be a supporter of the Semantic Web. It is, however, an idea that I believe has drifted and with each passing day is becoming more irrelevant. I have enormous respect for the creativity and innovation of those working on it. But I wonder whether they haven't been led astray.
To me, the most successful aspect of the Semantic Web isn't the WWW (because nobody thinks of the WWW as part of the Semantic Web, and simply saying it won't make it so). The most successful part of the Semantic Web is RSS (Rich Site Summary, or Really Simple Syndication). That RSS is successful is beyond dispute; there are millions of sites using RSS worldwide and millions of people reading RSS. But what is ironic is that RSS developed outside the Semantic Web development infrastructure; if the Semantic Web is what the W3C is building (and only that), then RSS is not a part of the Semantic Web.
What's going wrong, it seems to me, is that the developers of the Semantic Web have lost any sense of the idea that these technologies must be used by millions of users, and that for this to happen, the technologies must be (a) capable of being understood by millions of people, and (b) easily implemented by these same people. I think that the Semantic Web is failing on both counts, not because the technologies and concepts are inherently incomprehensible or difficult, but because the descriptions and implementations are.
From where I sit, there are two ways of developing a new technology (a new specification, a new language, whatever):
- develop a simple core that users can expand if they need to
- develop a comprehensive system anticipating the way users would expand it
RSS developed the first way. The RSS language is very easy to learn - it has only a half dozen core elements, expressed in the simplest possible XML. An RSS file can be created by any person with a minimum of technical skill. Examples that they can use as templates abound. RSS has been extended in various ways, and various versions have emerged, and they all work. Just like with HTML, you don't have to be letter perfect to a detailed spec to make it work, you need only create valid XML.
But, for a contrast, look at any W3C page describing this or that specification. These pages are difficult to read, the specification is described in a dense, developer-oriented style, examples are hard to come by, and there is no room for error or modifications - it's the W3C's way or the highway (yes, this may not be technically true, but it's the impression a reader gets). The Semantic Web (in capitals) is something hard-edged Java gurus write, which can be used in academic or enterprise systems, but is hardly something you would put on your web page. And it is therefore (to the vast majority of people) useless.
To me, it seems that the W3C and the semantic web people should get back to their roots. It is still not too late to take a leadership position here, though it seems to me that it will require some hard rethinking. The future isn't enterprise systems, proprietary databases, web services, Java runtime engines, or standardized ontologies. That's not what the web was, that's not what RSS is, and that's not the future of online semantics.
Here is some gospel: if you can't do it simply, with a simple text-editor, a web server and a standard browser, it's broken.
The fact is, the vast majority of people out there do not have administrator level access to a web server and database implementation. This means that the complex Java infrastructures, XML databases, application servers, and the like, are out for them. They probably don't have privileges to compile, they certainly cannot install Tomcat. One version of Java was too many for them, while several different and incompatible versions was too much.
More gospel: if you can't say what you want to say with it, it's broken.
Semantic web infrastructure is incredibly complex and expressive. But there's no simple way to describe yourself, except in plain text. The same community that developed RSS has had to develop FOAF, a hack. Why don't we have an RSP (Really Simple People) protocol that people can create in Notepad (or generate with a simple Perl script) and post on their website? It's like the W3C has created a way to Say Everything but haven't given a person a way to say "I exist".
Why can't we describe events? The RSS community is searching for a nice, simple events format, RSE (Really Simple Events) again analagous to RSS, to say that 'This event, which is part of [ref] this event, starts on April 9 at the Grand Hall in Moncton, and ends an hour later.' It would take, what, an hour for one of the W3C gurus to specify and propose? Again, simple Perl that people could hack and modify would make this a powerful technology. But where is it? It appears as though the W3C wants to describe The Unfolding of the Universe, but not Joe's graduation party.
A Third Gospel: if you can't link, it's broken.
The RSS community badly needs a way to link one resource with another. Even if we had RSP, there's no clear and unambiguous way to link the person with, say, the blog entry. Like this, maybe?
Or what? Nobody knows - or at least, if they know, they're not saying. What is The Way to link things? Gosh, this is the core of the Semantic Web and yet is mired in obscurity and mystery. I want a simple page saying here's How to Do It - nothing more, nothing less. Something that leaves me free to link anything with anything, the semantic equivalent in XML to a web link.
A Fourth Gospel: if you can't find it, it doesn't exist.
Now, again, all this may exist. But where? Buried somewhere under the morass that is the W3C's website? Paragraph 47.3.45 in the Resource Description Format technical manual? If any of this exists (which I personally doubt) it should be up front on the W3C site: here's how to get started - describe yourself, describe your resource, link them together. *This* is what we mean by the Seamntic Web. *Here* is some script *you* can run using your limited resources that makes it work.
If the system that evolves from the work on the semantic web is one system for Enterprise, and another for the people, then we are creating an information infrastructure that is fundamentally flawed from the outset. The developers of the Semantic Web must, in my opinion, step back from the drawing boards for a bit, and roll out a basic infrastructure that allows people, real people, to communicate real things in a straightforward manner. The potential is there and people are just waiting for it.
Agree with everything. The thing that really gets me about the semantic web. If RDF-XML is just an XML serialization of RDF triples why doesn't it look like this? :
If it did, I could look at a couple of examples, grasp the principle and start doing something useful. [Comment] [Permalink] [Previous][Next]
The lack of easy tutorials and simple standards at the W3C website simply reflects their true constituency. Despite regular claims of democratic ideals, the W3C is an industry consortium dominated by big corporations. Dense standards that require talented professionals to implement benefit entrenched interests and big corporations who have the money to pay such professionals. Easy to implement standards and clear descriptions take power away from the corporations and redistribute it to the people. You'll get none of that from the W3C. They know who pays their bills, and it isn't you or me. [Comment] [Permalink] [Previous][Next]
RDF/iCal + FOAF:
RSS Feed containing FOAF:
RDF-backed aggregated site, using a FOAF-based blogroll:
More RDF resources than you can shake a stick at:
http://www.ilrt.bris.ac.uk/discovery/rdf/resources/ [Comment] [Permalink] [Previous][Next]
I agree that the grassroots haven't so far been addressed very well by the W3C, but people are beginning to see the utility of the Semantic Web technologies. This is building on the existing web.
I see the utility as well; it's the implementation that I am concerned about.
Sure, things need to be as simple as possible, but according to your gospel every image (not text!), every page generated dynamically from a database and every RSS feed (which can't be done in a standard browser) is broken.
If the semantic web were described using images, then it would indeed be broken. As a mechanism for describing and handling images, then the strictures apply. Look at HTML - you can easily embed images.
As for databases, one of the beauties of Cold Fusion - and the reason why it was so popular - is that database requests were, for the designer, very similar to HTML code. This allowed ordinary people the capacity to use databases, and the database itself simply became a part of the server, an invisible bit of infrastructure/
As for RSS, one of my complaints (expressed most recently on the RSS-Dev list) is that you can't easily manage displays in text browsers. Of course, with the addition of a CSS or XSL link in the second line of the RSS, it is easily viewable in the browser. But whomever designed this made it impossible to manipulate that client-side, which means that RSS must be processed through a server in order to allow customization of display. That is broken.
Describing people is inherently difficult, FOAF does a very good job. You could use a new format for it but then that format would be incompatible with other ways of describing resources. FOAF can be used alongside RSS 1.0 and any other RDF-based language.
Can be, but significantly, isn't.
There are several ways of describing events, the most promising-looking approaches using RDF/iCal which is also entirely compatible with RSS 1.0.
Correct me if I'm wrong, but the iCal specification isn't even RDF. You have to write a special parser/reader. It's hard to imagine this being within the reach of people.
The RSS community has a very rich means to linking, thanks to RSS 1.0 and RDF. There are plenty of links on the FOAF site to ways of describing yourself, using simple tools. The RDF model is at its heart very simple, but complex things are possible. Check out the Primer: http://www.w3.org/TR/rdf-primer/.
I agree that the grassroots haven't so far been addressed very well by the W3C, but people are beginning to see the utility of the Semantic Web technologies. This is building on the existing web. Sure, things need to be as simple as possible, but according to your gospel every image (not text!), every page generated dynamically from a database and every RSS feed (which can't be done in a standard browser) is broken. Describing people is inherently difficult, FOAF does a very good job. You could use a new format for it but then that format would be incompatible with other ways of describing resources. FOAF can be used alongside RSS 1.0 and any other RDF-based language. There are several ways of describing events, the most promising-looking approaches using RDF/iCal which is also entirely compatible with RSS 1.0. The RSS community has a very rich means to linking, thanks to RSS 1.0 and RDF. There are plenty of links on the FOAF site to ways of describing yourself, using simple tools. The RDF model is at its heart very simple, but complex things are possible. Check out the Primer: http://www.w3.org/TR/rdf-primer/ [Comment] [Permalink] [Previous][Next]
Thanks Stephen for your valuable & insightful articles & sharing on various aspects of learning communities, trends & develoments. Truely appreciate your article on "An Introduction to RSS for Educational Designers" (http://www.downes.ca/files/RSS_Educ.htm). [Comment] [Permalink] [Previous][Next]
As superisor Multimedia at the South Australian Museum in Adelaide, I use Stephens Oldaily and links regularly. It's invaluable to me to keep informed about what's happenning O'seas. While we work towards more online content, digital publishing using our CMS, it's important to keep abreast of as much as possible to stear in the right direction. It's become an integral part of my working week. I don't feel quite so alone. I hope you keep up the great work, it's a must! thanks Trevor [Comment] [Permalink] [Previous][Next]
I'm no dummy when it comes to html and website design - but all this 'other web services stuff' like rss just confuses. Then I remember that we're in the infancy of the Internet. When it grows up, designing for the Web will all be so easy. Thanks for helping the Web mature. Bern [Comment] [Permalink] [Previous][Next]
You can preview your comment and continue editing until you are satisfied with it. Comment will not be posted on the Stephen's Web until you have clicked 'Done'.
Your comments always remain your property, but in posting them here
you agree to license under the same terms as this site
(CC By-NC-SA). If your comment is offensive it will
Automated Spam-checking is in effect. If you are a registered user you may submit links and other HTML. Anonymous users cannot post links and will have their content screened - certain words are prohibited and your comment will be analyzed to make sure it makes sense.