Semantic Web Company

George Anadiotis is an expert on artificial intelligence with academic roots at the Vrije Universiteit, Amsterdam. In February 2009 he took the position as R&D Director at the Greek technology company IMC. I met him in September at I-SEMANTICS 2009 where he and his team contributed to the Triplification Challenge. In their paper Linked Data for the Masses they were pondering about the pragmatic value of Linked Data from an inbound and outbound perspective.  In his words:

We started experimenting with the technical infrastructure needed and created some proof-of-concept applications. Part of this work was enabling Linked Data access for the front-end infrastructure we used, Liferay portal. We decided on the appropriate vocabularies for the type of content we wanted to publish (FOAF, SIOC and MOAT mainly), delved on the internals of Liferay and used D2R to map its relational database to the vocabularies of choice, also using techniques to improve performance as much as possible. Since Liferay itself is also based on the notion of communities, we thought our work would be more widely applicable and useful, so we chose to submit it for review at the Triplification Challenge and make it available to the community as open source software. Our applications have gradually matured and are about to be deployed in our commercial projects, while at the same time we are now making the Liferay Linked Data Module available as a Sourceforge project and we are working with Liferay management in order to disseminate this effort to the community and also include it in a future release of the software.

Read the full interview here.

From November 11 – 13, 2009 this will be one of the big issues at the 5th International Conference on Topic Maps taking place in Leipzig/Germany. When asked about the relationship between TM and SemWeb conference organizer Lutz Maicher says:

With the vision of the web of data Topic Maps and the Semantic Web move closer over time. Anywhere URIs represent subjects, structured statements are gathered around them. In this context I see subj3ct.com as an interesting ventures. This recently launched service provides URIs for 15 million subjects to be used in structured data. Naturally, linked data hubs like dbpedia or geonames.org are part of it. The crowd is invited to contribute to this collection, also the Topic Maps Lab provides several feeds to register new URIs. Subj3ct.com turns out to be an infrastructure technology for Web 3.0 applications, regardless whether they are based on Topic Maps or other Semantic Web technologies.

Through this convergence the uniqueness of each technology sharpens. Reasoning is the strong point of the Semantic Web. But the strength of Topic Maps are semantic portals and the global federation of facts around subjects. Bringing together all and even contradictory information about each subject – and not building reasoning-ready consistent models of the world – is built into the genes of Topic Maps.

Read the full interview here.

There’s a lot to know about semantic standards, languages, technologies and their application, so last week I attended TopQuadrant’s first European training from Oct 5th to 9th in Amsterdam.

We kicked off with Eddy Vanderlinden elaborating on the lessons he learned from 30 years of work in the financial sector. He outlined how improvements could be achieved by using data models relying on semantic web standards. You can read about his ideas in this essay.

TQ’s chief scientist Dean Allemang then continued with his talk “Enabling Creativity at the Edge”. “The edge” refers to the boundary between an information system and the real world, where the end users of a system work. As business needs change faster and faster, the people working at the edge need to be able to adapt the company’s applications on their own and shape them to their everyday needs.

Dean Allemang

Nowadays end user often achieve this kind of creativity on the edge by using self-made spreadsheets. The problem with that is their lack of interoperability. These data from different spreadsheets, databases, reports, etc. are often connected through business processes that rely on repetitive and error prone human processing, like copying things from a spreadsheet to a database, creating a report and pasting its result into another system, and so on.

The result is a complex system with many heterogenous parts and an organisation that cannot possibly know what it knows.

As a solution Dean proposed to “think outside the table” and go beyond the relational database way of orgranising data. This of course can be achieved by integrating the data using semantic technologies. TopQuadrant’s software offers possibilities to do just that, and makes it possible to create highly customizable dashboards and applications that all rely on the same data.

During the following days we learned about the ins and out of using semantic standards and languages and tried out TopBraid tools in several hands-on excercises. The TopBraid Suite is a very powerful, commercial toolkit. It includes TopBraid Composer, Live and Ensemble. Composer is a semantic web modeling and application developement tool, that uses the Eclipse framework. TopBraid Live is a server for semantic applications built with TopBraid Ensemble. Ensemble is a graphical application assembly toolkit, that enables end users to create custom apps that run in a browser and use RDF data and data models – thereby allowing for the above mentioned “creativity at the edge”.

I am very impressed with the capabilities of these tools, they enable the user to realize manifold possibilities that come with using semantic web standards – and that without programming. You can see some of these tools in action and learn about applying semantic standards in a series of webcasts from Semantic Universe. For the latter topic you might also attend one of our webinars.

On the last day Dean coverd several case studies, like connecting ontologies to legacy data sources (using e.g. D2RQ inside Composer), applying semantic technologies to the customer service management of a larger retailer or using ontologies in Federal Enterprise Architecture.

All in all I am very happy to have attended TopQuadrant’s training and hope they will establish a successful series of trainings in Europe just as they did in the US.

Jamie Taylor, Metaweb

Andreas Blumauer from Semantic Web Company (SWC) talked with Jamie Taylor, Minister of Information at Metaweb Technologies Inc. about Freebase & Linked Data and Google´s announcement to use RDFa.

SWC: At ISWC 2008 Freebase became “officially” part of the LOD Cloud. What exactly has changed since that time?

Jamie: Since Freebase is a community writable semantic database, the addition of the RDF interface allows anyone to publish data into the LOD cloud. LOD Applications can access any Freebase Topic through the RDF interface by constructing a URI from the Freebase identifier.  But perhaps more importantly, because entities in Freebase can be annotated with multiple identifiers, Freebase Topics can be retrieved by constructed URIs using the identifiers used by other systems and data sets.
For instance, the movie Blade Runner can be referred to as http://rdf.freebase.com/ns/en.blade_runner, but it can also be referenced as http://rdf.freebase.com/ns/authority.netflix.movie.70053131 using the Netflix identifier, http://rdf.freebase.com/ns/authority.imdb.title.tt0083658 using the IMDB identifier, or as http://rdf.freebase.com/ns/wikipedia.en.Dangerous_Days using a Wikipedia wikiword (which in this case is a Wikipedia redirect to the wikiword Blade_Runner).
Freebase also provides a user maintained mapping of how these identifiers can be used to address resources in other LOD systems. The sameas.freebase.com schema can tell an LOD user that the Freebase Blade Runner Topic can also be found in DBpedia using Wikipedia identifiers or how musical artists can be found at the BBC using Musicbrainz identifiers.  In fact, the Freebase RDF interface uses the sameas.freebase.com schema to create the owl:sameAs links in the RDF output allowing the user community to expand the interconnections between Freebase and the LOD Cloud.
Linked Data providers are also using the strong identifiers in Freebase to identify entities such as companies and locations in their own data sets.  When they find an entity that is not represented in Freebase, they simply add the entity to Freebase and use the newly minted Freebase identifier.  This permits anyone using their data to understand how their entities relates to any of the more than 5 million things interconnected within Freebase.

The RDF interface can also be used to reference the Freebase type system, giving LOD data set providers vocabularies across a wide range of subject areas.  And because anyone can expand Freebase’s data model, data providers can use our schema development tools to build and extend these vocabularies to suite their needs.
Freebase was not designed for ephemeral or fast changing data, like weather conditions or stock ticks.  But this type of information is well suited for publication as Linked Data.  Freebase entities representing a location or company can be annotated with references to LOD services that provide these types of volatile data.  Similarly, Linked Data provides a great way to disseminate very fined grained information that might be associated with a scientific study or financial report.  Linked Data provides a seemless transition from Freebase, where a user (or application) can run a query with constraints that run across a wide range of types to find entities of interest along with the LOD services that provide access to temporal or high resolution data not available in Freebase.
We recently demonstrated MQL Extensions which allows the Metaweb Query Language to use data from other systems as a part of the query constraint and result set.  While MQL Extensions are user extensible and work with a wide array of systems,  this capability makes the connection between Freebase and the LOD Cloud even more transparent.
For example, because US companies that are registered with the SEC are annotated CIK code in Freebase and the sameas.freebase.com schema indicates that the CIK annotation can be used to create a URI that is dereferencable at rdfabout.com, it is possible to write a MQL query that asks who is on the board of financial services companies that trade on NASDAQ and are  headquartered in California (and using another MQL Extension, you can ask for their stock price as well!)

SWC: Many organisations are very interested in Linking Open Data now but they are still not sure if they can benefit from publishing data on the web – what´s your experience so far?

Jamie: Linked Open Data provides a simple, standard way for organizations to distribute structured data.  For most organizations, providing access to data is another important outlet to announce the availability of higher value services.  For organizations involved in building or selling physical goods, the bits representing what they provide are not the goods themselves, but a way of attracting potential customers.  Making catalogs and specification sheets available in electronic form, so other applications can connect buyers to their physical goods is simply an effective marketing system.  Even for firms involved in electronic services, providing access to open structured data is generally a lead-in to value added services.  For instance, if I ran a service collecting hard-to-find information about manufacturing relationships between medium sized businesses, I would publish open company profiles covering things like market size, industry, location for the medium-sized businesses I tracked, so potential users the premium data would know I had the coverage they were looking for.

SWC: Just recently Google has announced to use RDFa to enhance their search results. What do you think?

Jamie: We are excited about Google’s announcement. Yahoo’s use of RDFa for Search Monkey and Google’s announcement gives RDFa users tangible benefits. The Search Monkey team was very quick to realize that because users can create data models in Freebase, and because the elements of those models all have strong RDF identifiers, Freebase provides a large and user extensible vocabulary for RDF/RDFa (see the list of vocabularies). When a user wants to create a Search Monkey application that works with their film review site, they need not invent a new vocabulary (that will probably be used only once),  they can use the Freebase Film Domain vocabulary which supports over 63,000 instances in Freebase alone.
Similarly, with over 5 Million well described Topics in Freebase and over 14,000,000 Named Objects (Topics, images, musical tracks and documents) when a user wants to unambiguously identify a subject or object in RDF/RDFa, Freebase has an extremely large collection of identifiers to draw from.  These cover people, places, companies, movies, music, books and wide variety of other subjects.  If Freebase doesn’t have the entity the user is looking for, they can of course add it themselves and make use of the identifier immediately. I think this is why Google used some Freebase identifiers in their examples. We hope that with Yahoo and Google’s support for RDFa the web will become a strongly annotated source of data which can support a wide range of user applications.

SWC: Thank you, Jamie!

Related articles by Zemanta

• Putting Freebase in a Star Schema (gen5.info)
• RDFa, Google (ivan-herman.name)

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.

Maybe you have noticed it already; today in the morning something new appeared at Google’s search engine interface: A bunch of corresponding search-suggestions based on your search query. Google spoke about this enhancement:

Starting today, we’re deploying a new technology that can better understand associations and concepts related to your search, and one of its first applications lets us offer you even more useful related searches (the terms found at the bottom, and sometimes at the top, of the search results page).

I tried it. So, if you type in “time travel” you also get search proposals like “theory of relativity time travel” or “wormhole time travel”. Google annouced, that the service is available in various languages. The direct test with German is a little disillusioning: Searching for “zeit reise” (which is the same concept as above, in german) leads to alternative searches like “reisen 50er jahren” (travel 50ies) and “reisen im mittelalter” (travel in the medieval).

Even if this semantic-like extension of the basis search function still needs some tuning, the point is getting clearer: Also Google is doing developments to get more meaningful results into their search algorithms. And parts of the semantic methodology are finding their way into mainstream services like search engines – as we have seen with Wolfram Alpha some days ago. So keep your eyes open – maybe next morning you’ll find another piece of the semantic puzzle embedded into one of your favorite web-apps.

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.

Presently more and more tools come up in the Web 2.0 – Domain, which bring semantic technologies into blogger´s everyday life. Zemanta was for sure a break-through in annotation of blog entries. I’m running this service on my private and my corporate blog. It is easy to integrate in every common blog-software and it is really a save of time in my daily work. Unfortunaly it is avaible only for english blogs.

Another service which came up recently is Quintura, which provides search capabilities for your own blog with a visual map of tags or hints based on an index created of the own blog entries. It is easy to customize for the own blog’s style with the use of a simple interface. Quintura offers code-snippets to copy to your blog-post or sidebar. Even if it is no semantic search engine in the narrow sense, Quintura provide a fine semantic-like interface for a meaning-sensitive search. See how Quintura is implemented into The Semantic Puzzle at our sidebar.

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]