First steps towards developing the Domain Model for OSC 2.0 * Until 15:45 * Goals: 1. Rough steps / timeline for actual development of the Domain Model A A1. overhaul entity definition with regard to OSC 1.0 (maybe Jupp Tscheak, Michael, Jakob) * identify deviations * clarify if deviations are necessary or should * clarify naming / terminology * create a mapping where necessary A2. identify entities and their actions / methods that are introduced by high-level description of OSC 2.0 (so not part of OSC 1.0) (maybe Florian Bock, Michael Kluge, Jakob Kaths, maybe Sharon Rosenberg) * identify new entities, their actions and attributes that are necessary to cover high-level scenario descriptions in OSC 2.0 (e.g. Road, drive(), etc.) * integrate them properly in Domain Model * close interrelation on working-level with language group (was a lack during concept phase) B develop technical concept of extensibility (Sharon Rosenberg, maybe Hans Bothe (ODS experience)) * check with OTX where there are working groups for extensions (more firm extensions in line with Michael's (dSPACE) proposal) * feature sets may add parts to the domain model * "quick" extensions by (even single) users need to be possible as well * possibly introduce mandatory / optional C bring ontology towards a technical level from theory to practice (Fran, Iain, maybe Steven and Puran, maybe Marcos Nieto) * synchronize with global ontology developed by ASAM * what are the technical artifacts that come out of the ontology development * Fran (FiveAI) can contribute, FiveAI developed own ontology for scenario description * Iain Whiteside (FiveAI) can provide a presentation on practical usage of their ontology * UK has developed a standard (or a PAS really) called 1883 for a driving ontology (Siddhartha could help here) * possible input as well from Steven and Florian Bock (Audi) A, B and C can be parallelized during development phase 2. Who brings what into the Proposal for the Development Project (assign people)