W3C home > Mailing lists > Public > public-sweo-ig@w3.org > March 2008

Re: Fwd: [Linking-open-data] Drupal 7 to be a major linked data client

From: Kingsley Idehen <kidehen@openlinksw.com>
Date: Tue, 11 Mar 2008 08:08:13 -0400
Message-ID: <47D6762D.8050000@openlinksw.com>
To: Arto Bendiken <arto.bendiken@gmail.com>
CC: W3C SW Education and Outreach IG <public-sweo-ig@w3.org>, Dries Buytaert <dries.buytaert@gmail.com>, Boris Mann <boris@raincitystudios.com>, Miglius Alaburda <miglius@gmail.com>, Ben Lavender <blavender@gmail.com>, Linking Open Data <linking-open-data@simile.mit.edu>


> I think there are a number of things that the SWEO initiative could
> help us out with. Here follow some initial thoughts in brief:
>  1. RDF myths debunked
>     It would be very useful to be able to point people at a collected
> "RDF Myths" wiki page that would debunk some of the more widespread
> basic myths and misunderstandings about RDF, such as those I mentioned
> above. It would preferably be written at a level any RDF novice could
> understand, and would attempt to explain matters from a number of
> viewpoints that people would be likely to be coming from (especially
> taking into account XML or RDBMS bigots). Perhaps such a page exists,
> but I don't know of it.
>     For example, in my experience people stuck in the "RDF = slow,
> bloated, complex" camp tend to be somewhat appeased after learning
> that RDF/XML can, these days, be done away with in favor of more
> human-readable formats such as Turtle; in addition, simple RDFa
> examples have also proved helpful for showing how HTML pages can
> sprinkled with semantics (with the tagline, "RDFa as the ultimate
> microformat") without the need for heavy investment upfront.
>   2. External validation
>     As I wrote before, any positive publicity that you guys could help
> shower on these efforts will help in convincing the Drupal
> community-at-large that the direction Dries has outlined for Drupal
> 7.0 is audacious but not unprecedented nor taking place in a vacuum.
> (The Talis guys, and others, have already been doing a pretty good job
> of disseminating the news from Drupalcon - thanks!)
>   3. Endorsement and adoption
>     One special point of pride that the Drupal community has been able
> to claim for a while now is the fact that Tim BL blogs using Drupal.
> If anyone here would be able to get the word to Tim BL regarding
> Drupal embracing his vision, that would be fantastic.
>   4. Mentorship and participation
>     There is still at present a dearth of RDF know-how in the Drupal
> community, and I would very much like to solicit input from Semantic
> Web folks into the formative discussions now taking place in the
> Drupal Semantic Web interest group [9]. The foundation for RDF in
> Drupal will be firmly laid in the next few months, and decisions taken
> in the immediate future may stick around for a while, so it would be
> great to get things right the first time (where possible).
>   5. RDF Schema for Drupal
>     The immediate action item that could benefit from the RDF
> expertise represented in SWEO is the ongoing effort to define an RDF
> schema for Drupal. Stéphane Corlosquet has posted an initial proposal
> at [10].
> I appreciate the interest shown by SWEO and would be available to
> participate in a SWEO conference call at your convenience should you
> guys think it beneficial for furthering the discussion.
> Best regards from sunny Spain,
> Arto
> PS. I've copied this conversation to my colleagues Miglius Alaburda
> and Ben Lavender, and to Boris Mann, Drupal evangelist extraordinaire
> and marketing czar of the Drupal Association.

In you message above you use the term RDFization. Please clarify that 
you mean exposing Drupal's SQL Data as RDF. If this is what you mean 
then please note that we have produced complete RDFization of Drupal 
(via Relational Schema to RDF Schema / Ontology Mapping) for a while 
now.  Our main problem has been locating the right people on the Drupal 
front re. incorporation into the main Drupal codebase. In our case we 
are using Virtuoso where you would normally have MySQL and Apache, and 
we achieve this by simply making Drupal ODBC compliant (as Virtuoso like 
other DBMS engines supports ODBC and like Apache supports HTTP).

Here are some links to a Live Drupal Instance [1], RDF Linked Data URI 
for a Drupal user that exposes his/her data items [2][3], and a View of 
the Drupal Linked Data Graph via an RDF Browser [4].

Ideally, I would like us to have all the Drupal and RDF efforts in one 
place for reference by others. A nice starting point would be the ESW 
Wiki [5].


1. http://demo.openlinksw.com/drupal/   (user and pwd values: demo)
2. http://demo.openlinksw.com/drupal/user/demo#this  (Hash based URI for 
the user 'demo')
3. http://demo.openlinksw.com/drupal/user/demo (actual RDF information 
resource describing the Drupal Data Space of user 'demo')
(Browser session for exploring the Drupal user's RDF  graph)

All of what I have described above is part of the Virtuoso EC2 AMI 
which is available from Amazon via their AWS service.


> [1] http://blogs.talis.com/nodalities/2008/03/the_best_is_yet_to_come.php
> [2] http://boston2008.datagraph.org/
> [3] http://drupal.org/project/rdf
> [4] http://drupal.org/project/sparql
> [5] http://drupal.org/project/exhibit
> [6] http://groups.drupal.org/node/9010
> [7] http://groups.drupal.org/node/9363
> [8] http://drupal.org/node/219862
> [9] http://groups.drupal.org/semantic-web
> [10] http://groups.drupal.org/node/9311



Kingsley Idehen	      Weblog: http://www.openlinksw.com/blog/~kidehen
President & CEO 
OpenLink Software     Web: http://www.openlinksw.com
Received on Tuesday, 11 March 2008 12:08:31 UTC

This archive was generated by hypermail 2.3.1 : Tuesday, 6 January 2015 20:28:59 UTC