You are here


Drupal, the semantic web and search

All major search engines, including Google and Yahoo!, are moving aggressively trying to capture structured data. This isn't exactly a surprise because it provides tremendous opportunity. Let's take the example of product search. Imagine the web as a huge database of millions of products, and search engines like Google and Yahoo! giving you a rich set of controls to filter by price, availability, color, shipping cost, user ratings, and more. Wouldn't it be great to be able to search all the world's products from a single page with a single interface? I'd think so too.

It is waiting to happen; we just have to connect the dots. That is, we have to make Drupal emit structured information.

Hundreds of thousands of Drupal sites contain vast amounts of structured data, covering an enormous range of topics, including product information. Unfortunately, that structure is hidden deep in Drupal's database and doesn't surface to the HTML code generated by Drupal. As such, search engines can't pick it up as a product, and they'd fail to include it in their world-wide product database.

I first talked about the semantic web and Drupal in my DrupalCon keynote last year in Boston. In my presentation, I laid down the challenge that we need to put fields in core and make them first class citizens. Once fields are thus empowered, they can be associated with rich, semantic meta-data that Drupal could output in its XHTML as RDFa. For example, say we have an HTML textfield that captures a number, and that we assign it an RDF property of 'price'. Semantic search engines then recognize it as a 'price' field. Add fields for 'shipping cost', 'weight', 'color' (and/or any number of others) and the possibilities become very exciting. I envision a Drupal core CCK with the power to do just that.

Here is another example. Imagine a standard Drupal node-type called 'job'. The fields in the job node-type would have RDF properties associated with them mapping to salary, duration, industry, location, and so on. Creating a new job posting on a Drupal site would generate RDFa that semantic search engines like Yahoo!'s SearchMonkey would pick up and the job would be included in their world-wide job database.

Technologies like this disintermediate so many existing websites and organizations that it makes my head spin. It is too great an opportunity for us to pass up on. By adding semantic technology to Drupal core, I think we can make a notable contribution to the future of the web.

This kind of technology is not limited to global search. On a social networking site built with Drupal, it opens up the possibility to do all sorts of deep social searches - searching by types and levels of relationships while simultaneously filtering by other criteria. I was talking with David Peterson the other day about this, and if Drupal core supported FOAF and SIOC out of the box, you could search within your network of friends or colleagues. This would be a fundamentally new way to take advantage of your network or significantly increase the relevance of certain searches.

I can has semweb in Drupal core?

ICANN using Drupal

ICANN (Internet Committee for Assigned Names and Numbers), the non-profit organization that oversees the use of Internet domains is using Drupal at They are using Mollom too!
Public icann

Addison Berry new Drupal documentation team lead

For the past few years the Drupal Documentation Team has been led by Steven Peck (sepeck). Steven was the first person to take on this role, and he has done a great job. Not only has he grown the documentation team to include a lot of talented and hard-working volunteer writers, he has overseen the restructuring and reorganization of's documentation handbooks, greatly improving their structure and accessibility. Thank you Steven for the great work!

Like so many Drupal contributers, Steven works on Drupal completely as a volunteer. His day job has been demanding a lot of time lately, and he has decided to step down from being the Documentation Team Leader. That means it is time to pass the torch to the next person who can then sprint with it for a while.

One great thing about the Drupal community is seeing people grow into new roles and take more responsibility upon themselves. This is certainly the case for Addison Berry (add1sun), who in her two years working with Drupal has become involved with virtually every aspect of the Drupal project. Lately Addi has been more and more active with the documentation team, making her a clear choice in my mind to carry on where Steven left off. I'm therefore very happy to announce that Addison Berry, aka add1sun, is the new documentation team leader, effective immediately. Keep up the great work, Addi!

Addison Berry

Addison Berry at DrupalCon Yahoo! in Sunnyvale, 2007.

Acquia launch coverage

Cheers to the Acquia launch, which went really well. Hundreds of people signed up for a free community subscription. Also, check out Jeff Whatcott's blog post covering some of the blog posts, press articles, and Tweets about our new product and service offerings. Awesome!
Drupal lager


Acquia out of beta

After months of hard work, Acquia is now open for business! Starting today, everyone can connect their Drupal 6 site to the Acquia Network to take advantage of our services. Oh my!

The Acquia Network (previously code-named Spokes) is a hosted service that helps you with site management (update notifications, spam blocking, cron service, modification detection, etc) and provides real-time visibility into the health and usage of all your Drupal sites that are connected to the Acquia Network.

Second, the Acquia Network gives you access to Acquia's technical support team. Whether it is an installation question, a development question or a configuration question, our Drupal experts are ready to provide you with technical support. The kicker? Acquia Network subscriptions are available for every budget -- including a free community version. Give it a try!

Third, we are also releasing Acquia Drupal today. Acquia Drupal (previously code-named Carbon) is our Drupal distribution that bundles some of the best, most essential Drupal modules for building social publishing sites. Acquia Drupal is available for free, and all our bug fixes and improvements go straight to the module maintainers on Acquia Drupal defines the collection of modules that you can get technical support for.

Starting Acquia wasn't straightforward. To setup Acquia for success, it required hiring world-class people smarter than me, but that often lacked Drupal background, or even Open Source experience. It took a while before we hit our stride, but it is truly amazing to see how everyone got hooked on Drupal, and how much we have come together as a team. Thank goodness I didn't take that job at the bank, because I couldn't be happier. Everyone in the company is determined to contribute to Drupal's growing success, and with Acquia's offering, I think we can get Drupal into a lot of new and interesting places.

Going forward, you can expect us to help port more modules to Drupal 6 and to add more modules to Acquia Drupal to expand our support offering. You can also expect us to extend the existing network services in the Acquia Network and to see us add new network services that extend what we've started with update notifications, spam-blocking, and uptime monitoring. Details are available on our Acquia Drupal roadmap page (registration required) and on our Acquia Network roadmap page (registration required) respectively. And last but not least, you will continue to see Acquia employees be very active in the community. So buckle up, because this is only a glimpse of what is to come, and we're on the fast track now.


© 1999-2015 Dries Buytaert Creative Commons Attribution-NonCommercial-ShareAlike 3.0 License.
Drupal is a Registered Trademark of Dries Buytaert.