WP6 meeting at Sofia, 2010-05-11
Participants
- Cefriel: Manu, Irene
- Saltlux: Tony, Kono, Stanley + guys from KICT
- Siemens: Volker
- VUA: Spyros, Jacopo
- Cyc: Michael, Luka
- HLRS: Matthias
- ...
Agenda
- understand
- set the goals
- plan
Discussion
Korean scenario
- porting the urban larkc in Korea? (to demonstrate replicability of LarKC)
3 workflows --> events (just using EVDB? NO), monuments (maybe, from LGD), path finding (NO; but student at PoliMI working on extracting topology data from OSM)
- Korean road sign management
- KM problem, POIs are not isolated
- hypothesis of scenario for September: map with "pins" indicating road signs and their change over time (new building: which signs should be updated?); further use: inconsistency checking, suitability checking
- how to use LarKC:
parallel with Milano monument workflow: wikipedia --> dbpedia --> linked data --> sindice --> LARKC PLATFORM --> URBAN LARKC APPLICATION
road sign relational database --> RDF version --> LARKC PLATFORM --> URBAN LARKC APPLICATION (nothing published as linked data because private)
Siemens traffic prediction
- current status: prediction upon historical data (traffic + weather + calendar)
- currently only for one sensor
- how many sensors? how many junctions/links? how broad will be the experiments? decision to be taken!!!
- traffic-aware path finding
- plugin which loads the graph with predicted "weights" of roads, then several selection plugins to extract only subsets of the reads which goes inti the path-finding algorithm (aim: shortest-time path finding instead of shortest-length path finding); not necessary to handle the evolution during the path following (even if this dynamics is a really interesting research problem)
Parallelization
Matthias shows the experiments with the event workflow parallelization (actually XML2RDFTransformer) --> single thread vs. multi-thread, 2 core vs. 8 core, distribution functionality (dynamically loaded on the cluster)
- if/how to show? help from HLRS to make comparison tests (code in the trunk with some very small instrumentation, maybe not in the release)
Platform releases
- WP6 to deliver D6.7 in July (so document ready by end of June)
- version 1.1 will be ready by the end of June, but WP5 people meeting in middle June for the major coding
- maybe Daniele D. from Cefriel to participate? if helpful (WP5 to discuss this during next week phone call)
Goals for the review
- Road Sign Management: Saltlux + KICT + VUA (Zhisheng) + any other support
- Traffic-aware Path Finding: Siemens + Cefriel
- Comparison between v0.1, v1.0 + parallel plugin manager: Cefriel + HLRS + Ontotext
Plan towards the review (HARD DEADLINES !!!)
- June 9 (with phone call at 10CEST): concept description fixed (mockup of interface + LarKC usage description)
July 7 (with phone call at 10CEST): prototype demonstrable (partial business logic, partial look&feel but 50% functionalities available)
- July 29 (with phone call at 10CEST): prototypes ready for demonstration, business logic stable (in order to have time for adjustments)
August 27 (with phone call at 10CEST): prototype can be shown to the review, look&feel ready
- September 6-9: review
- September 27-29: ICT 2010 event
if anybody thinks he cannot respect the deadlines, let the WP6 list know as soon as possible
