From SIOC Wiki

Jump to: navigation, search

This page serves as an overview over existing applications that use or implement SIOC.

Check against recent updates listed at State of the SIOC-o-sphere (#4). Possibly add SIOC for phpBB, IKHarvester, Tom Morris' Twitter2RDF, Fishtank, Tuukka Hastrup's IRC2RDF, BAETLE, etc.

Note for wiki editors: Many subsections of this page use transclusion to display short teasers of the applications' actual wiki pages.


Data Sources

SPARQL Endpoints

These are solutions that expose SIOC Data via SPARQL Endpoints.

OpenLink Data Spaces (ODS) Endpoints

ODS SPARQL endpoints provide access to SIOC instance data from a range of ODS-Application instances

The Live ODS Demo Server and (Alpha) Service are examples of ODS instances that expose SIOC instance data to SPARQL Query Service clients.



These are solutions that export plain old RDF graphs of SIOC Data.

SIOC plugins export the information about the content and structure of blog and forum sites in a machine readable form. Here we list all the existing SIOC export plugins and tools.

Such plugins or exporters can be developed for any blog engine that you want to export the information from. Plugins can be built on their own or can use a SIOC Export API, the latter being the recommended approach.

Most of the exporters implement a SIOC auto-discovery mechanism which allows us to identify webpages that contain SIOC metadata using automated tools such as the Semantic Radar plugin for Firefox .


We have created a SIOC export plugin for WordPress - one of the most popular blogging tools. It makes use of existing WordPress PHP functions to access the information from the underlying relational database and generate SIOC metadata in RDF for each concept instance.



DotClear is a blogging platform, that is widely used in the French blogosphere and written in PHP. Using the PHP API, a SIOC exporter was written and packaged as a plugin so that users can install it from their software backend. The exporter creates data for users, posts, comments and trackbacks.



This plugin for Drupal can be used to export SIOC data from Drupal blogs and forums. As Drupal can be used as a multi-user blogging platform, the plugin will export all blogs and all users account, so that each post can be clearly identified by its users. This plugin is currently used in, a community website with 120 users.



b2evolution is a multi-blog platform that evolved from the same roots as WordPress - from b2/cafelog. A SIOC exporter for b2evolution, built upon the SIOC API for PHP, is now available.


Talk Digger

Talk Digger is a web service that help people to find, follow and enter conversations of the Web. Basically it is a service that tell to people who is linking to a specific web page. Users can create a personal profile, explicit their interests, make new friends, track conversations, leave comments in conversations, etc.



SWAML is a mail list exporter. SWAML reads a collection of email messages stored in a mailbox (from a mailing list compatible with RFC4155) and generates a RDF description.


OpenLink Data Spaces (ODS)

OpenLink Data Spaces is a Distributed Collaborative Application Suite built atop the OpenLink Virtuoso Universal Server platform.

It exposes SIOC instance data in the form of Real and Virtual RDF Graphs for the following applications realms: Weblog, Wiki, Feed Aggregation, Shared Bookmarks, Photo Gallery, Disucssion Forums, and WebDAV based File Servers.



Exports SIOC and FOAF data from vBulletin discussion forums.



We aim to overcome a "chicken-and-egg" problem (no applications without data, and no data without applications) by making it easy to generate and use SIOC data. Most blog and forum engines already have RSS export functionality and the majority of them are based on open source software or can be extended by using plugins, it is straightforward to modify existing export functions or create plugins to generate metadata conforming to the SIOC ontology.

A SIOC Export API makes the development of such SIOC plugins and exporters as easy as possible as developers don't have to change their plugin as the SIOC format evolves - all the changes are made once, at the API level. In either case, the exporter or plugin uses the internal logic (functions, classes, etc.) of the blog engine or else direct database access to get information about the weblog, and then uses the SIOC API or custom code to produce SIOC export data.

At the moment PHP and Perl APIs are available. There is a need for SIOC export APIs in other languages, such as Ruby On Rails (as used in the Typo blog engine).


The PHP Export API provides an easy way for developers to create SIOC exporters, as it maps SIOC Classes to PHP objects, with simple functions to export the created data. In this way it enables developers to create SIOC export tools without the need to get into technical details about how information is represented in RDF/XML – they are operating at the level of SIOC concepts instead. Thus, developers only have to deal with extracting content from their weblog databases and then passing it to the API that will render SIOC data.

When using the API for your exporter, you won't have to deal with SIOC specs or RDF formatting, and you could easily update your exporter to the latest version of SIOC specifications by simply updating the API file in your exporter. The SIOC PHP API is already being used by SIOC export plugins for the export plugins for DotClear, b2evolution and vBulletin.



A SIOC API for Java has been created, based on semweb4j. For each object in the SIOC ontology, this API generates classes with links between the objects realised as Java properties.


Version 1.0 of a SIOC API for Perl has been released on CPAN. The CPAN page for the SIOC API is here. A description of the project itself is available here in German.

Data Consumers


Browsers - Overview

Since people can quite easily create SIOC data from their weblog using the described exporters or the API introduced in the previous chapter, we will now consider different ways to query and view this data.

SIOC browser allow people to browse and receive additional information from SIOC data sources or data stores. Browsers can work in two modes - on-the-fly mode and crawler mode - or can use a combination of both. The former displays the SIOC data received from a community site (thus providing a uniform interface to all SIOC-enabled sites) while the latter stores SIOC data in a repository, allowing one to make more complicated queries via the use of SPARQL, the leading Semantic Web query language.

SIOC data can also be displayed in a graphical format – as a timeline of content posts or as a graphical network of relations between sites, posts and topics. These graphical interfaces offer another user-friendly way to view SIOC data and the crawler mode browser may be extended to provide both a text and graphical view of the same information. Moreover, as SIOC offers an open data format using a formal description in RDF, everyone can create their own tools as appropriate to their needs. Thus, the browsers provided here are an example of what can be done with SIOC, and give a nice overview of its different capabilities.

SIOC Browser

The SIOC RDF browser is an on-the-fly or live browser, which offers a simple and effective way to explore community information available in SIOC. It gives a user-friendly look at the internal structure of the data without requiring the viewers to dive into a more complex RDF/XML syntax.



Figure 5: Buxon used to read SIOC-Dev archives[1]

On SWAML 0.0.3 was released a sioc:Forum browser called Buxon (now it is an independent package ).

Written in PyGTK, it reads a sioc:Forum RDF files and show it as a tree by threads, a screenshot can be seen in Figure 5.

SIOC Explorer

SIOC explorer is a web application similar to a feed-reader: it allows people to subscribe to SIOC feeds and read their content. Because SIOC data is very rich, people can filter the content based on e.g. authors, topics, creation date, or any other properties.



Siocwave (at Google Code) is a SIOC browser similar to Buxon. It tries to be flexible about retrieving linked SIOC data from the Web, and is thus capable of “seeing” more SIOC sites than Buxon. It is a desktop tool based on Python, wxWidgets and RDFLib.


Wordpress Importer

This plugin enables you to create blog posts in Wordpress by taking SIOC data from other weblogs (but also other sources like mailing lists, CMS, etc. are possible). It demonstrates that you don't have to be a developer to benefit from the web of RDF data - any blog user can have use for it.



Semantic Radar

Semantic Radar is a semantic metadata detector for Mozilla Firefox. It detects the presence of SIOC, FOAF and DOAP as well as generic RDF and RDFa data in a webpage, and displays icons in the browser's status bar when one of these data formats is found. By clicking on an icon the user can browse the RDF data in an online semantic browser.


Ping the Semantic Web is a web service archiving the location of recently created/updated RDF documents on the Web. If one of those documents is updated, its author can notify the service that the document has been updated by pinging it with the URL of the document. is used by crawlers or other types of software agents to know when and where the latest updated RDF documents can be found. So they request a list of recently updated documents as a starting location to crawl the Semantic Web.

You can use the URL of an HTML or RDF document when pinging web service. If the service finds that the URL points to an HTML document, it will check if it can find a link to a RDF document. If it finds one, it will follow the link and check the RDF document to see if SIOC, DOAP and/or FOAF elements are defined in the document. If the service found that the RDF document has SIOC, DOAP and/or FOAF elements, it will archive the ping and make it available to crawlers in the export files. Otherwise it will archive it in the general RDF pings list.

Personal tools