Andreas Blumauer

Google and the Semantic Web: About Quad Stores and URIs

Just recently Google launched another interesting service called “In Quotes”. It delivers quotes from stories linked to from Google News and users can compare opinions of e.g. politicians in a very comfortable way.

If  a closer look is taken at the system, one can see that any person whose quotes are listed has got a URI: Barack Obama has got the uniform “qsid” tPjE5CDNzMicmM.

It seems like “qsid” stands for “Quad Store ID” which would perfectly support such a URI based system.

Does Google slowly approximate to the Semantic Web?

Thomas Schandl

KiWi Annual Meeting

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).

Community Equity Diagram

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.

Thomas Thurner

Keep the Semantic Web trusty

Tim Berners-Lee at a Podcast Interview
Image via Wikipedia

In recent days – here at Semantic Web Company – we have had a lot of discussions on how the future of the Semantic Web (name it Web3.0 if you like) will develop. Several stakeholders on the future of the Semantic Web see already, that also a potential danger will come along with the technical realisation of the web3.0: This is the present possibility to create applications and mashups with semantic technologies that are a real drain on privacy and information ethics. Without an underpinning discussion about the ethical framework within technolgies like linked data, text-mining, biometric-systems and geo-systems in combination with the web of data, the whole domain is in danger to be doomed like genetic engineering some years ago.

It’s crucial for the public opinion on the Semantic Web, to adress the immanent risks regarding privacy and ethics. In this context I’ll see also Tim Berners-Lee‘s statement yesterday: “W3C wants to help make sure data use is appropriate,” he said. Berners-Lee, who is director of W3C, said in an interview on Wednesday that the teams working on the Semantic Web project are making sure that privacy principles are included in its architecture: “The Semantic Web project is developing systems which will answer where data came from and where it’s going to — the system will be architectured for a set of appropriate uses.”

Maybe it’s an important step in keeping the further development of Semantic Web trusty in the eyes of public opinion, that the W3C has privacy and information ethics on their agenda and persons like Berners-Lee stand with their reputation for it. But it is also crucial to build this awareness on the corporate side. Only if everyone within the domain follows a common ethic understanding we have a public opinion, which is on the future potential of the Semantic Web, and not in fear of the same.

Reblog this post [with Zemanta]