Towards Enhanced User Interaction to Qualify Web Resources for Higher-Layered Applications

By the way, there are some more photos of the conference:

Photos of the DW10@IARIA

First, we introduce some background regarding the qKAI application framework. In Section 2 follows what we see as prerequisite to utilize Open Content for higher-layered applications. Section 3 gives an overview of the qKAI application frameworks’ system design. Section 4 offers some more details concerning the qKAI hybrid data layer as one system level of the 4-tier design. Section 5 shows further services and components, Section 6 exemplifies use cases and further application scenarios. At least this contribution ends up with a conclusion and future work in Section 7.

In this contribution we present our adaption of information quality aspects to qualify Web resources. We selected knowledge-related iq-criteria and take it now as tool to implement iq-mechanisms stepwise into the qKAI framework. We exemplify some criteria of information quality like relevance, accuracy or response time and then derive assessment methods for certain iq-criteria enabling rich, game-based user interaction and semantic resource annotation.

These are “code lines” only, whatever CLOC means by that. Unit tests have not been counted as well as code within comments and the documentation.

Since the first version (revision 863), written by Jan Hein, the distribution changed a lot. Here is another visualization, again only “code lines” count:

In the next few days the amount of C/C++ code will double as our MySQL customizations will be extended. Most probably JSP will vanish in favour of Java and it could happen that the SQL code amount will stall where it is and a lot of Flex will be checked in.

We have about 12 design patterns in use, most of them have been introduced since revision 863.

But, as a future contributor to qKAI you don’t need to be afraid of mastering all the languages. Indeed you have the freedom to stick to two or three you know the best. That’s how everyone started and you can see where qKAI is now…

Maven is a software project management and comprehension tool. Based on the concept of a project object model (POM), Maven can manage a project’s build, reporting and documentation from a central piece of information. (http://maven.apache.org/)

With Maven we got a nice project documentation now – available under http://docs.qkai.org. Especially the API section is work in progress and will be enhanced by and by.

http://esw.w3.org/topic/SparqlEndpoints

Of course there are lots of other interesting things to find in the ESW wiki

Towards Utilizing Open Data for Interactive Knowledge Transfer

The presentation slides are available here.

Thanx a lot to Mark!