Semantic Web Company

The Vienna-based company punkt. netServices is just about to release a demo version of their PoolParty service, a SKOS-based thesaurus management tool with linked data capabilities. I had the chance to pre-read a white paper and test their service. Here is a brief overview. You can also try a demo.

Purpose

Poolparty was conceived to facilitate various applications like

• Semantic search engines
• Recommender systems (similarity search)
• Corporate bookmarking
• Annotation- & tag recommender systems
• Autocomplete services and facetted browsing.

These use cases can be either achieved by using PoolParty stand-alone or by integrating it with existing Enterprise Search Engines and Document Management Systems or Enterprise Wikis.

Thesaurus Management

PoolParty is aiming to be easy to use for people without a strong Semantic Web background or special technical skills. The GUI is entirely web-based and utilizes AJAX so the user can e.g. quickly merge two concepts via drag & drop. An overview over the thesaurus can be gained with a tree or a graph view on the concepts.

PoolParty also helps to semi-automatically add concepts to a thesaurus as it can be used to analyse documents (e.g. web pages or PDF files) relevant to a thesaurus’ domain in order to glean candidate terms. This is done by the key-phrase extractor of KEA. The extracted terms can be selected by the user, thereby becoming “free concepts” which later can be integrated into the thesaurus, turning them into “approved concepts”.

Documents can be searched in various ways – either by keyword search in the full text, by searching for their tags or by semantic search and similarity search. The latter takes not only a concept’s preferred label into account, but also its synonyms and the labels of its related concepts are considered in the search. The user might manually remove query terms used in semantic search. Boost values for the various relations considered in semantic search may also be adjusted. In the same way the recommendation mechanism for document similarity calculation works.

PoolParty by default also publishes a Semantic Wiki version of its thesauri, which provides an alternative way to browse and edit concepts. Through this feature anyone can get read access to a thesaurus, and optionally also edit, add or delete labels of concepts. Search and autocomplete functions are available here as well. The Wiki’s XHTML source is also enriched with RDFa, thereby exposing all RDF metadata associated with a concept to be picked up by RDF search engines and crawlers. (See two examples: Cocktail thesaurus &  Standard Thesaurus for Economics)

PoolParty also supports the import of thesauri in SKOS (including several consistency checks) or Zthes format. Those functionalities can also be consumed as stand-alone web services via PoolParty SKOS Services. Additionaly, lists of concepts and their labels can also be imported via CSV files.

Linked (Open) Data

PoolParty not only publishes its thesauri as Linked Open Data (in addition to a SPARQL endpoint), but it also consumes LOD in order to expand thesauri with information from LOD sources.

Concepts in the thesaurus can be linked to e.g. DBpedia  via a service like Georgi Kobilarov’s DBpedia lookup service, which takes the label of a concept and returns possible matching candidates. The system suggests relevant resources from DBpedia and the user can select the one that matches the concept from his thesaurus, thereby creating a skos:exactMatch relation between the concept URI in PoolParty and the DBpedia URI. The same approach can be used to link to other SKOS thesauri available as Linked Data.

Other triples can also be retrieved from the target data source, e.g. the DBpedia abstract can become a skos:definition and geographical coordinates can be imported and be used to display the location of a concept on the map, where appropriate. The DBpedia category information may also be used to retrieve additional concepts of that category as siblings of the concept in focus, in order to populate the thesaurus.

PoolParty is capable of importing a SKOS thesaurus from a Linked Data server, and may also receive updates to thesauri imported this way. This feature has been implemented in the course of the KiWi  project funded by the European Commission. KiWi also contains SKOS thesauri and exposes them as LOD. Both systems can read a thesaurus via the other’s LOD interfaces and may write it to their own store. This is facilitated by special Linked Data URIs that return e.g. all the top-concepts of a thesaurus, with pointers to the URIs of their narrower concepts, which allow other systems to retrieve a complete thesaurus through iterative dereferencing of concept URIs.

Additionally KiWi and PoolParty publish lists of concepts created, modified, merged or deleted within user specified time-frames. With this information the systems can learn about updates to one of their thesauri in an external system. They then can compare the versions of concepts in both stores and may write according updates to their own store.

This means each system decides autonomously which data it accepts and there is no risk of a system pushing data that might lead to inconsistencies into an external store. Data transfer and communication are achieved using REST/HTTP, no other protocols or middleware are necessary. Also no rights management for each external systems is needed, which otherwise would have to be configured separately for each source.

Technology

The software is written in Java and utilizes the SAIL API, so it can be used with various triple stores. The thesaurus management itself (viewing, creating and editing SKOS concepts and their relationships) can be done in an AJAX Frontend based on Yahoo User Interface (YUI). Editing of labels can alternatively be done in a Wiki style HTML frontend. For key-phrase extraction from documents PoolParty uses a modified version of the KEA 5 API, which is extended for the use of controlled vocabularies stored in a SAIL Repository (this module is available under GNU GPL). The analysed documents can be stored and indexed in Lucene/Solr or any other (enterprise) search system along with extracted and semantically related concepts.

I will give a talk about the relevance of Semantic Web and Linked Data for news publishers at this year’s IFRA summit in Vienna on October 15, 2009. IFRA is the World Association of Newspapers and News publishers and within their Technical Group Publishing they are starting to deal with Semantic Web. Further invited speakers are Michael Steidl (IPTC) and Robert Schmidt-Nia (dpa mediatechnology).

The Semantic Web Company created a series of online seminars (aka webinars) for you to acquire basic and practical knowledge about methologies, technologies and standards of the Semantic Web. In 90 minute sesseions we will cover the business aspects of topics such as content engineering, Knowledge Management, business intelligence, e-Business and more.

In order to allow for a high level of interaction, the attendance is limited to ten participants and ample time for questions and discussion with our experts is designated. Each webinar works as a stand-alone module, so you can pick and choose some of them or book the whole series of 6 webinars.

We’ll kick off with a session about Semantic Wikis on Thursday 22nd of October. A German language version will be held at 9 a.m., alternatively you can atted an English version at 6 p.m. CET.

Each Thursday we cover a different topic such as Semantic Search, Corporate Thesaurus Management, Text Mining on the Corporate Semantic Web, Linking Open Data and Semantic Advertising.

In order to participate you only need broadband access to the internet, Windows or a Mac and a fairly up-to-date browser. For detailed system requirement see the webinar overview.

We hope to talk to you in one or more of these sessions!

That’s the title of my diploma thesis and first of all, thanks to SWC for the possibility to say some words about it. My interest in knowledge management reaches back some time now and I decided to make it the subject of my diploma thesis in my first attempt to write one back in 2001. The semantic web “came to me” in the last one or two years and the TRIPLE-I conference last year was somehow the trigger for me to connect the two topics.

My basic idea was very simple. When you read about the Semantic Web you are confronted right away with connections to creating knowledge and knowledge management. But in my understanding the Semantic Web is a technical thing and knowledge management is primarily a cultural and organisational thing. So the research questions for my thesis where:

• What relevance do knowledge management and semantic technologies have in the daily work of people working in knowledge intensive domains?
• Which possibilities lie in the adoption of knowledge management and semantic technologies?
• Are semantic technologies already fit for practical use?

The basis of the empirical part of my thesis are group discussions held in different organisations. As a result I developed starting points for an understanding of the topics “Knowledge Management” and “Semantic Web” and their relevance in organisations. The empirical results, in short, provide the following answers to the research questions:

• The “theoretical relevance” of both topics is high, the “practical relevance” on the other hand is rather low. Neither do structured concepts for knowledge management exist in the studied organisations, nor are there attempts at using semantic technologies
• Most of the participants have not heard of the “semantic web” prior to the discussions. After having been introduced to the topic, the relevance of the semantic web and of semantic technologies is rated high
• Possibilities are seen in a better management of information or knowledge in organisations and, especially for semantic technologies, in the improvement of search functionality’s and search results
• Semantic technologies are not yet seen as fit for practical use
• The connection between knowledge management and semantic web is taken as a fact without giving any justification for it.

In my conclusion I tried to match my results with the results of the Semantic Web Barometer 2009 and it was very interesting for me, that there were several similarities. I also found that talking to the people that have to work with technologies that are developed for them can be quite interesting and that group discussion are a great way to do that.

I wrote most parts of my diploma thesis in a wiki (and the rest is available as PDF) so you can find it on my wiki.

Your comments and annotations are very welcome!

Thanks for reading as far as this, Helmut

Related articles by Zemanta

• ISWC Workshop on Semantic Web Applications in Scientific Discourse (w3.org)
• Leo Sauermann – gnowsis: Weak memory remedy @ webinale (tiburon-tv.com)

Luckily, times have come, where semantic search techniques have found their way to enhance knowledge providing theme portals. Nearly once a week a new knowledge portal with built-in semantic search pops up. They deal with environmental issues, health care, economy etc. These sites are good examples how the vision of a knowledge web is fostered by semantic technologies. Such focused approaches are great showcases for “a” semantic web (even if they are not based on “the” RDF semantic web) in the next few months besides general knowledge portals like Wolfram Alpha.

But the potential of these semantic theme portals is often reduced essentially by their bad usability. You get lost in categories and flags – you get puzzled by pulldowns, mouseovers and embedded hierachies – it’s sometimes a mess out off 1001 functions. You need to understand the underpinning semantic concept to get oriented within these applications – and this is not the goal of the exercise. Search has to be easy.

To show the potential of semantic technologies, we need good examples, which offer good usability. This is a call to everyone to provide such examples.

See my favorites:

• NextBio, a platform that enables life science researchers to search, discover, and share knowledge locked within public and proprietary data
• reegle, the Search Engine for Renewable Energy and Energy Efficiency
• CultureSampo, a Finnish cultural heritage platform for institutional organizations as well as private citizens

Markus Luczak-Rösch and his team from FU Berlin have published loomp, a WYSIWYG annotation tool especially designed for inhouse use. loomp is aiming at the Corporate Semantic Web market, providing a semantic application with low entry barriers and high usability designed for non-techies.

When asked about the concrete application area Markus says:

We have found various use cases especially in knowledge and content intense domains. The most interesting one is the journalists use case. Consider journalists which research and write articles and editors which revise and publish the work of journalists.

Journalists research specific topics on demand and access various information sources for this purpose, e.g. websites, books, related articles, and human informants. Only few journalists use digital devices for this task and even fewer apply information management systems. To transfer the finished article to the responsible editor at the publishing house the people use free text documents and email communication. Finally, an editor revises and releases the articles for his department. loomp can help journalists to manage their notes, interview logs, references, addresses, etc. loomp helps to link an article to its information sources.

Read the full interview here.

Last week the partners of the KiWi (Knowledge In a Wiki) project met in Salzburg for the 2009 Annual Meeting.

Sebastian Schaffert and his team demonstrated the latest version of this semantic based framework based on wiki principles and built on JBoss Seam.
You can take a look at the online showcase and download the one click installer of the pre-release.
Sebastian emphasised that KiWi will follow Linus Torvald’s maxim of releasing early and releasing often.
In June 2009 KiWi 1.0 should be ready, followed by 1.5 in December 2009, at which time Enabling Technologies and a first implementation of the uses cases will be included in the system.

After hearing talks about the KiWi User experience, data model and transaction management, we learned about the status of reasoning, querying, information extraction and personalisation of the Enabling Technologies groups (online slides forthcoming here).

Peter Reiser presented the Sun use case, in which the focus now is on realising an expert finder mechanism based on the “Community Equity” concept found in Sun Spaces (their highly popular, heavily customized version of Confluence).

In short Community Equity is a system for analysing the social activities in a community and measuring the value of the contributions to the community. Social activities are anything from creating content to simply viewing it. These activities are used to calculate the Community Equity (which is simply a number) of content, tags and people.
Consider this example for a content page: The more people view, download, reuse, comment on or rated the page positively, the higher the page’s Information Equity will be.
In turn the community members acquire Contribution Equity through the content items they create, i. e. the Information Equity of a content item “spills over” to its creator.
The same goes for Tag Equity: Each tag obtains the Equity from all the pages it is applied to. E.g. if there are 3 pages with the tag “JBoss” with Information equity of 10, 5 and 20, then the Tag Equity of JBoss is 35.
These things alone is very helpful for motivating people to contribute to the community and for judging the quality of content and ranking it accordingly.

On top of that, the Equity system allows for a expert finder system. People are related to all the tags that are used on the content items they created. Imagine a contributor has created several documents that were tagged with java and the sum of information equity of those pages is 550, then the person also has
That way a search for “Java” doesn’t only bring documents tagged with java, but also people with expertise in Java.
In KiWi this Community Equity system will be implemented and extended. For one, instead of flat tags KiWi will use concepts coming from SKOS thesauri, which will be managed using PoolParty.
These thesauri act as a shared knowledge model. In this way synonyms, parent/child concept relationships, etc. can be considered for Equity calculation, therby taking personalization, querying and expert finding to a whole new level.
Research will engage with questions like how should the Equity disperse through the graph: Imagine a community member with high Equity in “JBoss”. This means she probably has good expertise in Java too. As this subconcept relationship is expressed in the thesaurus, it is possible to transfer Equity from JBoss to Java, but one has to consider what percentage the equity will be transferred, if Equity only can only spread upwards from subconcept to parent concept or whether other kinds of relationships also warrant the transfer of some Equity.

In his recent interview Andreas Blumauer (SWC) asked Mario Lenz, from german-based knowledge management solution provider EMPOLIS, about their OS-Initative SMILA. As Lenz explained, SMILA acts within a domain of various approaches and already established solutions re. Enterprise Resource Planning Systems. So, he sees SMILA’s USP in: “a standardized way of representing, accessing and managing those unstructured data which not exist today. Rather, each vendor ships his own, proprietary solution. SMILA’s goals are to define and implement such a standard infrastructure framework and to establish a community bringing it forward.”

Besides an insight in many aspects of the initiative, the interview provides thoughts on how connected business-models, in providing services, could look like.

[read more]

KiWi – Knowledge in a Wiki, Day 2 – Josef Holy from Sun Microsystems Prague led the first part of today’s use case presentation. With the KiWi semantic wiki system (or: wiki on steroids, as Josef Holy put it), they want to be able to increase the productivity of knowledge workers. Sun Microsystems have extensive experience with online and community collaboration and they want Kiwi to become a social wiki platform that is deployable in various contexts, i.e. that ties in with other platforms such as Netbeans or Zembly.

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.

KiWi – Knowledge in a Wiki session, pt. 2: This afternoon, we turned to the Logica use case, which is dedicated to the development and optimization of KiWi as a knowledge management tool specifically tailored to the needs of project management.

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.