KiWi, the Open Source development platform for building Semantic Social Media Applications, offers features required for Social Media applications such as versioning, (semantic) tagging, rich text editing, easy linking, rating and commenting, as well as advanced “smart” services such as recommendations, rule-based reasoning, information extraction, intelligent search and querying, a sophisticated social reputation system, vocabulary management, and rich visualisation.

Just like the overall organization of the project meeting was very good, so Sebastian Dietzold, Sebastian Hellmann, Michael Martin and Jörg Unbehauen did a real good job at putting the ideas behind key concepts of the semantic web across in several introductory SemWeb presentations. Their talks about various technologies from the semantic web stack like URIs, RDF and its serialisations, RDFS, SPARQL and some related tools were well suited to bring people who are relatively new to the semantic web up to speed. Links to the presentation slides can be found at the project page in the coming days.

Later Jens Lehmann outlined the new things OWL 2 brings, e. g. profiles, which are subsets of OWL 2 and which provide different degrees of expressivity and reasoning efficiency.

The last day started with Sören Auer’s presentation of their semantic wiki OpenResearch, a site where information on conferences, journals and scientists is pooled. OpenResearch is built with Semantic MediaWiki (SMW), just like our Social Semantic Web wiki.

While SMW is a very useful tool as it lowers the entry barriers for using semantic wikis, Sören also pointed out  that in comparison OntoWiki provides some important features that SMW doesn’t have:

• SMW doesn’t use SPARQL for its queries, but a less powerful custom query language, whereas OntoWiki has full SPARQL support.
• OntoWiki’s UI has many widgets that support the user when entering data or new properties on a page (e. g. there is an autocomplete feature for suggesting properties)
• With SMW changes to the wiki’s semantic structure often entail manual changes to many, many pages. With OntoWiki it is easy to e.g. change poperties at any time.

For the new version of OntoWiki Sören and his team use the Zend framework and develop the Erfurt API to store and access RDF data. The Erfurt API supports SPARQL, versioning, caching and RDF based authentification/access control. It abstracts different stores using the adapter pattern, so it can be used with Virtuoso and any other store which has an interface provided by Zend_Db (MySQL, Oracle, PostgreSQL, etc.) plus they are working on an interface for Redland. Find the slides for Philipp Frischmuth’s Erfurt API presentation here, the API documentation here and Norman Heino’s Zend & OntoWiki Application Framework presentation here.

Julian Jöris demonstrated how Selenium is used for acceptance testing. This is a very promising testing framework for web applications, where one can e.g. record interactions with different browsers and automatically run them as tests. Selenium has a Firefox extension to record macros and is integrated with PHPUnit.

Finally we had a very good discussion about our conX-OntoWiki integration use case and application ideas, so we left Leipzig with a pleasant anticipation of the coming co-operation in the project.

It’s good to see that the visibility of Semantic Web is also growing outside academia and involved industry.

Author: Pascal Hitzler

We opted for Semantic MediaWiki (SMW) and the extensions Semantic Forms and Semantic Drilldown. In this blog post we’ll take a look at the handy features you get with these. This short tutorial is based on my SMW demonstration at the Web of Data Practitioners’ Days in Vienna two weeks ago.

As the book is in German, the wiki is set up in German, too, but that shouldn’t be a problem for understanding the demonstrated features. For the following examples, we have created a mirror of our productive wiki, so don’t hesitate to edit and play with this mirror wiki (we might refresh it occasionally, so don’t write any data into the wiki that you don’t also have stored elsewhere). This tutorial is going to take you through the following SMW features:

• Automatically created lists
• Faceted search
• Semantic queries
• Entering data via forms
• RDF export

So let’s see what these features hold for us.

• Automatically created lists

A common problem in wikis like Wikipedia is the (amount of) effort it requires to create and maintain various lists like the list of the EU’s largest cities. It’s an equally laborious and error-prone activity to keep such lists up to date; as a result, there are a lot of useful Wikipedia lists we can imagine that don’t exist at all, like a list of the world’s largest corporations with a CEO younger than 35.

In SMW it is easy to create all kinds of lists with queries. This page for the book’s table of contents is an example. View its source to see the inline queries used to generate the page (click to enlarge or view the source on the wiki):

As a result, the list is generated afresh any time the table of contents page is called up. If the data on an article’s page has changed, it will also be updated in that list – while in regular MediaWikis one has to manually update the data in both places (the article, and the list), which, apart from the extra work, also makes errors and inconsistencies much more likely.

• Faceted search

Take at look at the list of articles page… it uses Semantic Drilldown, so you can narrow the displayed articles down by author (“geschrieben von” = “written by”) or by topic (“Schlagwort”): For instance, select a topic from the tagcloud style list and you’ll be presented with a list of articles covering the subject in question. You can add another topic (which makes the set of results larger) or additionally specify an author (which further narrows it down).

• Semantic queries

A straightforward approach to exploring the values of a semantic property is to just look at the property’s wiki page. E. g. view a list of everyone’s blog URLs on this page: Property:Weblog.

More sophisticated queries can be made on the Special:Ask page.
To display all organisations located in Vienna or Graz just copy paste

[[Category:Organisation]][[Hat Sitz in::Wien||Graz]]

into the left hand box (“Hat Sitz in” = “is based in”).

Now go a step further and ask for the name and email address of all persons that work for a organisation located in Vienna or Graz and print their e-mail addresses. Again, copy and paste

[[Category:Person]][[arbeitet bei::<q>[[Category:Organisation]][[Hat Sitz in::Wien||Graz]]</q>]]

into the query box and copy and paste

Email

into the box for additional printouts

What is also very useful is that you can save any query on its own page, so users don’t have to know or remember the syntax. Here is the query page for people living in Vienna or Graz: Concept:Persons_working_in_Vienna_or_Graz,

• Entering data via forms

This feature is one of the essential advantages that SMW holds over a regular MediaWiki: Most of the content of our wiki is automatically generated from data which have comfortably been entered by filling in forms. This means a regular user doesn’t have to edit any wiki text to be able to contribute content.

See for yourself:

Log in with testuser and testuserpw, go to the page Form:Person and enter a name (e.g. your own name; click to enlarge).

When you fill in the fields “Works for”, “Friends” and “Topics” you will notice that an autocomplete feature assists you by suggesting pages that are already in the wiki. This helps to avoid multiple wiki pages for a single entity.

Before you submit the form, copy this line and paste it into the “free text” box – it’s the line that calls up the appropriate template, in this case for a person:

{{Template:Person_additional}}

In combination with the data you entered, this will generate the actual wiki page.

There is one thing you need to observe: You will probably find that your information is missing in some of the page’s paragraphs. If that happens just click on “edit” and save the page again, after which the page content will be updated properly.

In this way, a properly set up SMW with Semantic Forms enables the users to enter data without knowing how to write wiki syntax, and assists him or her in the data entering process.

• RDF export

To top it off, SMW enables you to link your data into the LOD cloud and to reuse properties and classes from external ontologies. Take a look at this exported RDF/XML containing data about the author Andreas Blumauer. You’ll see a lot of foaf terms reused and also an owl:sameAs pointing to his personal URI.

This sums up the introductory tutorial – if you want to learn more about SMW, then check out the wiki document for the complete tutorial or see SMW’s own documentation.

Author: Thomas Schandl, SWC

Related articles by Zemanta

• ontoprise Semantic MediaWiki+

Also published yesterday was an interview with Matthias Schindler, former member of board of Wikimedia Germany, at the occasion of the publication of a physical Wikipedia, i.e. a one-volume encyclopedia in print (publisher: Wissen Media, a Bertelsmann division). According to the English Wikipedia, “the volume is planned to include abbreviated entries for the 50,000 most commonly used search terms of the prior two years. The book is to be priced at 19.95 euros, with one euro from every sale going to the German chapter of the Wikimedia Foundation.”

The interviewers also asked Schindler for his “encyclopedic Wikipedia dream” – I hope his response will catch on in the Wikimedia chapters worldwide:

I would one day like to see a large edition of Wikipedia (including a German language edition), which makes use of the Semantic MediaWiki extension. The dream in a nutshell, without consideration of the current state of research and development: A wikipedia that can be read not only by humans, but also by computers, a Wikipedia that can offer concrete answers to concrete questions and that creates content individually for users, something that they can make use of; great if Wikipedia played the role of the first, mainstream Semantic Web application. While this is still in the process of coming together, there are enough other things for us to do.

(btw, my translation).

Concrete answers to concrete questions, a personalized Wikipedia – I am not even aiming that high at the moment.

Just consider the absurd amount of lists in Wikipedia, all of which are maintained manually. Take for instance the list of hardcore punk bands, the list of fictional countries (to be distinguished from the list of European fictional countries) or the list of military operations.

How often do you think these need an update? And if a new hardcore punk band is added – will the creators of the new article think about adding it to the list? What about articles which make make a reference to or mention things that are or should be on a particular list?

As a list has the inherent claim of being complete, it shouldn’t be left to humans to create and maintain them – leave that to the machines! Vote Semantic MediaWiki for Wikipedia!

Author: Jana Herwig

Related articles by Zemanta

• 10 Millionth Article Written on Wikipedia
• Jimmy Wales and the Church of Latter-Day Wikipedians [The Sum Of All Human Knowledge]

An interesting use of wikis was introduced with the Moki plugin for Semantic Media Wiki, developed as a side product of the APOSDLE project. APOSDLE (EU-project leaders love their acronyms;-) aims to develop an Advanced Process-Oriented Self-Directed Learning Environment, which in plain language is a platform to support the process of learning at work. In the course of this project, a model of the enterprise knowledge had to be developed that was to be the collaborative result of domain experts within the enterprise and external knowledge engineers. The APOSDLE image video below conveys a sense of the complexity of the knowledge to be represented.

But on to Moki: As wikis are an ideal, readily available tool for collaboration, the simple solution was to build a plugin (Moki) for Semantic Media Wiki that allow to structure and engineer the domain knowledge. Moki is a hierarchy builder that supports drag and drop so that categories and relations can easily be fitted in place – the special benefit of using Semantic Media Wiki was that the structure of the generated knowledge can be exported in Semantic Web compliant formats. Apart from the browser, no further software is required.

The APOSDLE website doesn’t yet offer any information about Moki, but a description can be found in the conference proceedings: Collaborative Knowledge Engineering via Semantic MediaWiki, by Chiara Ghidini, Marco Rospocher (who gave the presentation), Luciano Serafini, Viktoria Pammer, Barbara Kump, Andreas Faatz, Andreas Zinnen, Joanna Guss, Stefanie Lindstaedt.

For those looking for good arguments for setting up a wiki in a global business environment: Peter Kemper‘s keynote was the perfect primer for that. Peter, a Knowledge Management portfolio manager at Shell’s IT-Department, gave some insights into the process of their conversion to wikis. Before there were wikis at Shell, they had global discussion forums, connecting 20,000 people around topics and questions, which were intensively used – the question whether wikis should be adopted or not alone generated 800 responses in these forums.

Instead of going for team wikis, Shell opted for the encyclopedic approach and a wiki that would be accessible to anyone at Shell, and for using MediaWiki – which was, interestingly, the first open source software ever used at Shell. Peter Kemper named scalability and the lean architecture as prime arguments for MediaWiki, and they have indeed not had any technical hiccups so far. It was also an asset that people, being used to Wikipedia, know how to use the MediaWiki interface.

Examples of uses case with which the feasibility of wikis within Shell were tested were: Drilling salt, Geology of the Atlantic Margin, and Production Chemistry. Before that, the main media for maintaining and passing on knowledge had been emails and Powerpoint – not exactly because these were considered appropriate for knowledge management, but because of the effects these media had had on the communication within Shell:

With the advent of email, People wrote less and less memos. Less and less reports were sent to the archive, because people kept powerpoint presentations. If that same information, previously locked in emails and powerpoint, went now into wiki, it would finally be accessible to everyone in the company.

Peter Kemper allowed us a glimpse of the information their wiki held, for instance, about the Atlantic Margin – as geological structures are described, most of the information relies on images. It would be a nightmare to maintain this kind of information in Powerpoint! No offense meant: Powerpoint is good for presentations but not for creating and maintaining a knowledge base. According to Peter, with wikis Shell achieved six times the productivity in comparison to using Powerpoint, in particular due to the linkability of content.

Wikis also turned out to be the superior solution for the integration of curricula from an internal learning environment, as wikis support the modular structure of a learning curriculum. Furthermore, they are also a good means to sustain communication in the time between workshops or team meetings.

At shell, they even use wiki for instance for the translation of contracts into the requirements of day to day procedures – a typical contract in the business that Shell is in has around 400 pages, and it is probably not very likely that a single person is going to read (and immediately understand) the entire contract. In this regard, the wiki also serves as a tool to translate lawyer-readable prose into transparent instructions (and there are probably many more ways in which wikis can be used to support business processes, a statement also put forward by Rolf Sint from Salzburg Research; see his 12 seconds statement below).

Rolf Sint talks about workflows in wikis on 12seconds.tv

A noteworthy detail about the integration of wikis in Shell’s IT architecture: If a user logs onto the wiki for the first time and goes beyond the disclaimer, a new wiki account is automatically created that is identical with his or her windows account – this is not about checking on people, Peter Kemper said, but about creating organisational transparency.

On the one hand, this reveals whether there are organisational units within Shell where the wiki is not as intensively used as elsewhere, meaning that these units probably have specific needs which need to be addressed first. On the other hand, people can (and do) also contact each other via the wiki, e.g. one can contact the person who created an article if one is on need of further information.

About stimulating content production: 60% of Shell’s employees will go into retirement over the next eight years, and with them knowledge that is needed in the company. They even asked and paid former employees to come out of retirement to work on the wiki – that’s what I call commitment to content creation and knowledge preservation.

The Shell wiki already has more than 40,000 registered users (with 150,000 employees in the company, plus contract staff). What is interesting regarding user activation is that the number of active users stays relatively the same, even if the number of users in total increases. Peter Kemper’s account for this was that content comes in waves, meaning that users are activated in those areas where fresh knowledge is generated.

Kemper distinguished three types of users: content owners who create content from scratch; content editors who often just correct syntax or make things ‘look nicer’; and information consumers. Kemper rejected the term ‘lurkers’ for information consumers as looking for information is an activity in itself.

All in all, Peter Kemper’s talk confirmed many of the assumptions which have informed our own KiWi – Knowledge in a Wiki project, the aim of which is to merge the wiki philosophy with knowledge management, enhanced by semantic (web) technologies. Sebastian Schaffert (Salzburg Research) puts it in a nutshell in the video below. Featured in a cameo appearance: the KiWI!

Sebastian Schaffert about KiWi – Knowledge in a Wiki on 12seconds.tv