LarKC WP4 Teleconference, 11.00 -11.50, Feb 12, 2010
The skype ID of the chair: larkc-wp4
Participants
Yi (WICI), Yang (WICI), Axel (HLRS), Alex (HLRS), Vassil (Ontotext), Hans (MPG), Zhisheng (VUA), Florian (STI), Emanuele (CEFRIEL)
Regret: Gaston (VUA), Lael (MPG)
Agenda
- Month 24 deliverable D4.3.2 (Implementation of Interleaving reasoning and selection)
- MPG's contribution to Stop Rules
- Month 24 deliverable D 4.4.1 (Design of Rule-based Reasoning)
- Ontotext's contribution
- Month 24 deliverable D4.6.1 (Design of Stream Reasoning)
- Joint WP2+WP4 Workshop in Interleaving Reasoning and Selection
(more to be added)
Month 24 deliverable D4.3.2 (Implementation of Interleaving reasoning and selection)
- Implementation of PION for interleaving reasoning and selection with LarKC Platform (VUA),
including the implementation of DIG reasoner plug-in, OWLAPI reasoner plug-in, OWLLink Reasoner plug-in, and PION with stop rules.
- Anytime Instance Retrieval by Ontology Approximation (VUA)
- Unifying selection and reasoning with user interests (WICI)
Yi: The title of the chapter will be changed.
- Human Task Stopping and Switching for interleaving reasoning and selection (MPG)
Hans: going to send an email to have a further discussion.
Deadline: M24 (end of March)
- Feb 16th: first draft ready
- Feb 26th: final integration
- March 6th: final draft ready
- March 8-15: internal review
- March 16-23: revision after review
- March 24-29: sent to Frank
- March 31: release
All: the timeline is fine.
Integration:
- Use UML for the illustration of chart/architure/workflow
- Contribution should focus on the implementation issues. It is not necessary to provide a complete implementation. Some initial implementation is fine.
- If the implementation is ready for release, it should provide a user guide in the document.
MPG's contribution to Stop Rules
In the existing implementation, PION uses a simple stop rule to decide when the selection should be stopped. How can we use more complex stop rules for interleaving reasoning and selection.
Month 24 deliverable D 4.4.1 (Design of Rule-based Reasoning)
Ontotext's contribution
- rule-based consistency checking
Vassil: yeah, i have experiement with consistency checking rules to validate the results from the data integration basically the first simple setup is to validate the used thesauri and enforce the seamtncs of the SKOS schema e.g. - one concept may have only a single prefLabel. i have a working prototype of OWLIM + consistency checking rules, now the questions is where to contribute this work
- Reasoning with LDSR data
Zhisheng: have a discussion with Vassil later.
Month 24 deliverable D4.6.1 (Design of Stream Reasoning)
- Main Content
- Integration with LarKC
?TimeLine
- Reviewer
Emanuele is going to find a reviewer for D4.6.1. Emanuele: Going to integrate the comments and suggestions of ESWC2010 reviewers.
Joint WP2+WP4 Workshop in Interleaving Reasoning and Selection
For the LarKC second year review, we have to provide convincing scenarios to show how the scalability can be solved by interleaving reasoning and selection. That needs a joint WP2+WP4 effort. We are planning to have a joint WP2+WP4 workshop (in April or May? in Amsterdam or Sofia?) to discuss those issues. We expect some presentations from WP4 for the joint Workshop.
- Requirement on selection plugins for PION (VUA)
- Selection for rule-based reasoning (STI)
- Selection for approximate reasoning (VUA)
- Selection with user interests (WICI)
Yi: It would be better to have the joint workshop in May in Sofia, or later.
Alex: WP5 is also interested in joining this workshop.