Is Twitter RDFization or triplification by Virtuoso usable?

Image representing OpenLink Software as depict...
Image via CrunchBase

The W3C lists many solutions for converting any non-rdf data to rdf data. After taking a closer look to the list, it became clear that there exists a very well documented system: Virtuoso Sponger. There is a broad support for many data sources. The architecture is very modular. This is realized by the use of so-called cartridges. I want to be sure that this promising middleware can support the framework I need. I investigated a twitter use case presented on a dedicated page. Since the architecture overview and the presentation about the mechanism is astonishing, my expectations were very high.The first experiment I did was a run on my own twitter account. I used the url they provided to preview the RDFication in html format:

The result was perfect!

RDFication of my twitter account

In addition, it successfully identified the rss feed of my timeline:

Then I wanted to see if it succeeded in parsing one of my tweets and how it is processed.

The result was that the page had been identified as a “foaf:document”.

This was of course very accurate, since this page was not the actual tweet, but a webpage with a representation of the tweet. An interesting property I noticed was the “primaryTopic”. It contains a link to my actual tweet in RDF format, it referred no longer to “…” but an entity created on the server! This entity was identified as: “sioct:MicroBlogPost”. Perfect! There is no way another service could do better.…

It also linked to an entity of my user profile – including a picture… A gimmick that gives this entire experiment just that bit more glamour……

For this result of course the Twitter built-in cartridge was used, but Openlink Virtuoso provides extensive documentation for developers. A tutorial is available about how to develop an test your own cartridge. It should be possible to adapt the twitter mapper (xsl demo) to make it work with the Grabeteer. This middleware  also handles RDF Store.

One of my tweets RDFized by Virtuoso

One of my tweets RDFized by Virtuoso

To get a better feel on how this middleware works and how complex the deployment of this web service is, I will deploy it on a test server. Then if this succeeds, I will take a closer look at the Twitter cartridge and interface. I will see how I can make it work with Grabeteer. There exists a commercial and an open source version. To save time and not to have problems with building and deploying the server, I will first install and run the commercial version. If this is a succes I will switch to the open source version. The difference between the open source and the commercial version is in the os-specific and database optimization. The installation procedure is significantly easier.

The answer if it is usable at the moment: definitely, Yes!



About laurensdv
Computer Science Student, interested in creating more innovating user experiences for information access. Fond of travelling around Europe!

5 Responses to Is Twitter RDFization or triplification by Virtuoso usable?

  1. Pingback: End of the easy learning curve… « Laurens goes semantic…

  2. Pingback: Something more about storing triples… « Laurens goes semantic…

  3. Pingback: End of the easy learning curve… | Laurens goes semantic

  4. Pingback: The Twitter data extraction begins! « Laurens goes semantic…

  5. Pingback: The Twitter data extraction begins! | Laurens goes semantic

Leave a Reply

Fill in your details below or click an icon to log in: Logo

You are commenting using your account. Log Out /  Change )

Google+ photo

You are commenting using your Google+ account. Log Out /  Change )

Twitter picture

You are commenting using your Twitter account. Log Out /  Change )

Facebook photo

You are commenting using your Facebook account. Log Out /  Change )


Connecting to %s

%d bloggers like this: