A 2003 post written looking at the shortcomings of the Semantic Web:
Excellent read, with thoughtfulness and insight into why the classic Semantic Web won't work for most. My talk at DERI covered a aligned topic of slow adoption , outlining the need for the Semantic Web more usable for web developers.
5 years later...
Starting a new project over at Drupal.org for running Drupal on top of Vertica.
Why? I like MySQL, and have used it for years - and it's been reliable, fast, and useful for just about every application I've needed to use - except one: as an RDF backend.
Article summarizes Semantic Search, and also shows Dries talking about RDF in Drupal 6 and 7.*
http://www.duvien.com/semantic-search-web-30-drupal
Here's the vid:
If you haven't seen Twine - here it is:
Stephane (aka "SCOR") has been working on a schema for the Drupal 6.0 RDF API.
http://groups.drupal.org/node/9311
Attached below is my presentation given for DERI in Galway Ireland, one of the premier academic research institutes building all sorts of applied Semantic Web applications.
Special thanks to Stephane Corlosquet of DERI, whom I met at Drupal Con Barcelona 2007.
Announced: http://www.deri.ie/teaching/invited-talks/archive/
Yum.
Faceted search, javascript, and recipes.
"Supercook is a new recipe search engine that finds recipes you can make with the ingredients you have at home. To begin, simply start adding ingredients you have. The more ingredients you add, the better the results will be."
This is an excellent example of what Semantic Search is currently capable of.
Looking for a way to automatically create meta data?
A new web service has launched which generates RDF for any text you send along. The semantic web is now one step closer to being something real and usable.
I'm still looking into it - looks like there are some Ruby and Java sample applications.
The Drupal post which alerted me to it:
http://groups.drupal.org/node/8801
Open Calais:
http://opencalais.mashery.com/Overview
There's a few anomalies with the current setup.
First, Sesame's memory store is truly stored in memory, and I access via both a custom app, and the standard REST interface. This produces concurrency issues, since the Sesame application stored for the REST interface doesn't seem to sync as often. Also, the console fails to catch this unless the url at http://localhost:8080/openrdf-sesame has its web container restarted.
These are all stored in memorystore.data. I plan to ask if sync is set to 0, how long does it take?
The (Slowly) Open Sesame article here provides an honest assessment of using Sesame for real world applications.
Here's an excerpt: