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.

Alex Wilhelm from The Next Web writes:

There is data outside of Facebook that the company wants to be brought in and made relevant inside of the Facebook platform. Enter the Open Graph protocol, Facebook’s way to say, in the common tongue ”all your graph are belong to Zuck.”

The product combines graphs, be they music graphs from Pandora or what have you, into the Facebook wider social graph. You can think of it has a “knit-up” with Facebook for other websites that are not Facebook affiliated.

Nick O’Neill from AllFacebook:

If HTML is the way developers get information into Google’s search engine, meta data is the way developers will get data into Facebook’s semantic search engine which will be based on the company’s “Open Graph”. Through the use of easy to implement plugins, Facebook is rapidly collecting structured data on every user. Facebook has also upgraded their API to make building on top of the Open Graph a much easier process. What’s pretty clear is that it’s an attempt to tackle the residing search giant.

[...] As Mark Zuckerberg said on stage an hour ago, by the end of the day Facebook should have more than 1 billion likes and that data will grow exponentially.

[...] There are a number of standards that have been created in the past as some developers have pointed out, microformats being the most widely accepted version, however the reduction of friction for implementation means that Facebook has a better shot at more quickly collecting the data. The race is on for building the semantic web and now that developers and website owners have the tools to implement this immediately.

Sören Auer and his team from AKSW at Uni Leipzig are the coordinators of this EU funded project which supports the development of innovative software products. All industry partners are SMEs which offer services for different fields like E-learning, E-tourism or Business Intelligence. Leipzig and OpenLink Software will work on an integration of OntoWiki & Virtuoso.

The first day of the meeting was, of course, dedicated to socialize and get to know each other. The mixture of the project team turned out to be well chosen – and in the evening we flew at higher game: We had a nice overview over Leipzig standing on the highest building of the town.

On the second day of the meeting Orri Erling, Program Manager at OpenLink Software, came up with an idea which is pretty forward: Why shouldn´t we provide OntoWiki as a Linked Data Browser, e.g. on top of DBpedia etc.? One possible outcome of this project.

Some other use cases which make already use of the existing OntoWiki system were demonstrated: Take a look at Vakantieland (…and start to plan your holidays in the Netherlands) and also at LinkedGeoData where a nice user interface can be tried out.

The Kick-Off Meeting will proceed with two workshops dedicated to semantic technologies and to Application Development with the OntoWiki Framework. Thanks to Sören and his team for the excellent hosting of this event!

One of Sun’s further assumptions is that users will migrate to KiWi neither immediately nor completely – and that’s an insight anyone developing yet another social platform should take to their heart. What was true in Field of Dreams – “If you build it, they will come” – does not quite apply here. The network effect works in favour of existing communities, and instead of striving to replace an existing platform, one might be better off with mashable contents and services.

The particular benefit of a semantic wiki is that it allows moving from unstructured to structured information (relatively) easily. For KiWi @ Sun (and in favour of mashed information), this means that what is relevant will be structured, both by people and by machines – a process that is going to extend beyond company boundaries. People will bring in structure by creating links from KiWi documents to external systems as well as by writing new facts (which the KiWi system will represent as triples) about external information. What is not relevant, won’t be structured – and will be forgotten. After all, it’s forgetting that makes you remember the important stuff.

One note about the users of KiWi at Sun: Since this use case focuses on knowledge management for software development, it can be taken for granted that users will have an above-average level of web savvyness. Primary users will be software designers (i.e. the people who design for the users of the final product) and developers – learn more about the different roles in a software development project at Sun here.

Consequently, the User Interface (UI) concept Josef introduced also comprises a social networking unit – things such as a ‘My Contacts’, ‘My Pages’ list, but most importantly an activity feed, which will help users to collaborate, participate, discover activities that others are currently working, develop a mental ‘social map’ of the community. Such an activity stream (similar to Facebook’s News Stream) would contain items such as:

• Szaby wrote a blog post
• Josef rated document XUI specs: five stars
• Peter created document ToDoList KiWi-UI
• Stephanie is now a contact of Marek
• Klara shared a document with Sebastian

Considering the target group, it is also planned that the UI will be extensible through widgets that users are able to write themselves.

*coffee break*

Above: The KiWi-Team, hailing (officially) from Austria, the Czech republic, Denmark and Germany

After the break, Andreas Blumauer (Semantic Web Company, Vienna) followed up with a talk entitled “Open Ontology Management & Linked Data” which explored the uses of the Web of Data for the Sun usecase.

His argument was that content and topic-centred, open communities should have mechanisms at their disposal for relating content and activities to particular parts of a shared concept model, e.g. of an ontology. In particular in projects like NetBeans, where contents and related processes evolve over time, different NetBeans groups utilizing the KIWI system should be allowed to maintain and share their own concept models. The combination of bottom-up and top-down approaches would, for instance, come as the combination of free tagging (where people often use different labels to refer to the same, or the same label to refer to different things) and concept tagging.

Free concepts can be turned into controlled ones, too, by being inserted into an existing controlled vocabulary, as either a narrower or related concept of any existing controlled concept. Open Ontology Management done this way is a Learning system: Through the combination of a Free Extraction Model (FEM) and a Controlled Extraction Model (CEM), text extraction improves over time.

Andreas also revealed a first glimpse of a project currently in stealth mode, code name ‘PoolParty’, which is an Open Ontology Management System that can be used to enrich local knowledge with data from the web. PoolParty consumes Linked Data and provides Linked Data; in the context of the current use case, it will be able to communicate with the KiWi System. Please contact Andreas if you would like to be notified about the further development of PoolParty.

Regarding the use case requirements: As Daniel Grolin, a process expert and business architect at Logica (formerly WM Data), pointed out, what is most required at the moment is an application for designing processes, i.e. for designing the ways that people do things. This can be a painful process, in particular if one group of people (consisting of process designers) thinks about the ways that another group of people (e.g. the project managers) are going to do certain things – a collaborative approach should be able to

1) alleviate this challenge
2) generate commitment among the involved parties.

The primary users will be on the one hand the process engineers, and on the other hand the project managers who are the recipients and users of these processes.

In his presentation, Daniel Grolin chose one of four scenarios in which KiWi would ideally be employed: the risk analysis process – which is a vital process for Logica, as the outcomes of this analysis influence the decision whether or not a project will be accepted. From an architectural point of view, KiWi is going to mediate between the process guidance column – which consists of process and workflow features – and the final work product, i.e the result of a process, in this case the report of the risk analysis.

In practice this means that if, for instance, a user has selected the risk analysis process, the Kiwi core system and enabling technologies will provide concepts related to risk analysis, supporting the user in the tagging process. Wiki technology is already being used in the industry, said Daniel, but what is lacking at the moment is the integration of structure, and this is also where he sees the potential of KiWi as a knowledge management tool, and as a means to move easily from unstructured to structured information (by the way, if you are interested in using wikis in the enterprise, I also recommend this article: Wikis for Knowledge Engineering, and in Global Businesses).

Karsten Jahn (Aalborg University) then gave us a preview of a possible user interface (i.e. not of the screen design, but the functionalities) which seeks to address one particular problem: Many companies use many different, sophisticated tools which operate fine on their own, but are not integrated (i.e. there is no communication or exchange of data between them). With KiWi, the aim is to develop a tool that is going to be able to cover all features and processes currently being taken care of by individual tools, to allow for an optimum of data integration.

To conclude, Rolf Sint (Salzburg Research) showed us screens of the current configuration of KiWi for Logica’s needs – the example below is related to the risk analysis process outlined by Daniel Grolin above.

In the first presentation today, Sebastian Schaffert from Salzburg Research gave us a tour of two different configurations of the KiWi system. The KiWi core system is oriented towards content versatility, meaning that content items can be displayed and used in various contexts and configurations. As a service to the user, KiWi uses Javascript-based WYSIWYG Editor TinyMCE enhanced with a few home-grown plug-ins which, for instance, make it easier to set links to other wiki pages. Memorizing wiki shorthand is sometimes a challenge, so this feature helps getting things done.

Using a different skin and interface, KiWi can take various forms and shapes – even shapes where you might not spot the wiki in it at first glance. TagIT is such an example of an adaptation of the KiWi core system: a geotagging platform targeting youth in Salzburg who can locate, tag and comment on places that matter to them.

Vice versa, KiWi in its wiki incarnation displays a little map, provided a content item is enhanced with geoinformation; technically, the map on the wiki page is an interpretation of a georelated tag (learn more about complex, structured tags proposed by the KiWi Enabling Technologies Work Package in this article: Usage Data Model Day in the KiWi Project).

Take a look at the screenshots below:

It is the same article that is being displayed, in the first example using the classic KiWi interface, in the second example using the TagIT interface with the article appearing as an info page.

This afternoon, we expect to see another configuration of the system, in a presentation about how the system is specifically tailored to the needs of Logica’s “Knowledge Management for Project Management” usecase.

N.B. The system is not yet publicly available, if you have questions, please contact Sebastian Schaffert.

Related articles by Zemanta

• KiWi Joint Work Package Meeting in Prague
• KiWi: Knowledge in a Wiki
• Usage Data Model Day in the KiWi Project
• Not a pipeline, but a graph: software development in the KiWi/Sun usecase

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+

Secondly: I published an “inaugural interview” Marion Fugléwicz-Bren did with two of my colleagues, Matthias Samwald and Thomas Schandl (not so inaugural for the former, as he already joined SWC in January). I’d like to extract this quote by W3C member Samwald regarding privacy on the (corporation owned) social web and the future (user-managed) social semantic web:

I also think that Semantic Web technologies will receive a lot of media attention when the first big, public breach in security / privacy happens in one of the websites that currently dominate the whole world wide web. At the moment, we all are uploading most of our private and business lives to web sites such as Google, Facebook, Flickr and others. It is just a matter of time until a big scandal happens, be it the companies themselves that misuse the vast amounts of data they have, or be it a government agency in an overzealous effort of crime prevention.

When this will happen, people will re-evaluate the trend towards massive centralisation on the web, and will search for opportunities to make the same feeling of being ‘in the network’ happen in a distributed environment, without selling ones soul to a multinational corporation. Then we will find that such an opportunity already exists — the Semantic Web.

Read the whole interview here.