LarKC WP4 Teleconference, 11.00 -12.20, June 11, 2010

The skype ID of the chair: larkc-wp4

Participants

Reto (STI), Yan (WICI), Vassil (Ontotext), Zhisheng (VUA), Gaston (VUA), Hans (MPG), Lael (MPG), Emanuele (CEFRIEL), Matthias (HLRS), Alex (HLRS), Axel (HLRS), Barry (?OntoText)

Regret: Yi (WICI)

Agenda

M33 deliverable D4.7.2

D4.7.2 Evolved Evaluation & Revision of plug-ins deployed in use-cases. This deliverable will report on the performance of plug-ins from tasks T4.3 (interleaved reasoning and selection), T4.4 (rule-based reasoning) and T4.6 (stream reasoning), in terms of the targets defined in D4.7.1.

from the case studies for the evaluation, iii) use the standard benchmarks (such as Oxford benchmarks and LUBM benchmarks, and iv) cooperate with the SEALS project to make joint effort for the standarization of the evaluation technology.

Reto: The Lehigh University Benchmark is developed to facilitate the evaluation of Semantic Web repositories in a standard and systematic way.

Structure of D4.7.2

  1. Introduction (ALL)
  2. Evaluation of Approximate reasoners
    • 2.1.Interleaving reasoning and selection with knowledge summarization(VUA and WICI) 2.2 Approximate reasoners with heuristics (VUA and MPG) 2.3 Reasoner with Stop rules (VUA and MPG)
  3. Evaluation of Rule-based reasoners
    • 3.1 STI's work on rule-based reasoners 3.2 Ontotext's work on consistency checking by rule-based reasoning
  4. Evaluation of Steam reasoning (CEFRIEL)
  5. Evaluation of Parallel reasoning (HLRS and VUA)
  6. Conclusion (ALL)

Matthias: Chapter 5 can be optional until we make clear the work become good enough to report as a separate chapter, or report it in Chapter 2, 3, and 4.

Reto: as said, we could do some evaluation about IRIS, which is also done in SOA4All. there will not be any time to do evaluation about the parallelized rule-based reasoner, as the implementaiton for it has not yet started! so section 3.1 might be missing at the end!

Timeline of D4.7.2

June - September: Implementation, Experiments/Data tests, and evaluation

October 1-30,2010, First draft

November 1-30, 2010, Final Integration

December 1-9, 2010, Final Revision

December 10-17, 2010, Deliverable Review

December 18-24, 2010, Quality Control

December 31, 2010, Submit to the Commission.

Task 4.4 on Rule-based reasoning (leader: STI Innsbruck)

Barry: an example:

Consistency: eq-diff1


Another example is the cardinality checking.

Zhisheng: The cardinality checking would be also useful for the consistency checking for the Korean Traffic Sign Data. They may need the logical consistency checking as well.

Barry: We need more information to see whether or not we can use the same approach of consistency checking on OWLIM for the Korean Traffic Sign Data.

Parallel reasoning (leader: HLRS) and Stream reasoning (leader:CEFRIEL)

Vassil: a typical example of reasoning query over ?PubMed and LLD:

PREFIX skos: <http://www.w3.org/2004/02/skos/core#>

PREFIX lifeskim: <http://linkedlifedata.com/resource/lifeskim/>

PREFIX pubmed: <http://linkedlifedata.com/resource/pubmed/>

SELECT ?title ?respiratoryDisorder ?leukocytes ?obesity

WHERE {

}

WICI and VUA are going to test it with the implementation of interleaving reasoning and selection with knowledge summarization.

Stop rules and reasoning (MPG)

Minutes

WP4/Meeting&TeleConf/Minutes/11June2010 (last edited 2010-06-11 10:40:13 by ZhishengHuang)