Commit dc81939b authored by Benjamin Engel's avatar Benjamin Engel
Browse files

Merge remote-tracking branch 'origin/kraines_additions_edits'

parents 75498a28 563d5040
Pipeline #1356 passed with stage
in 15 seconds
......@@ -22,29 +22,29 @@ The Concept document is using M-SDL language to demonstrate all the concept. It
=== Domain Model
OSC lies within the domain of closed-loop system testing for automotive functions. The Domain Model introduces domain-specific content to the otherwise generic Language Concept of OSC 2.0. The domain model provides the semantics, whereas the Language Concept delivers the syntax. Therefore, the Domain Model enables the preservation of semantics when scenario definitions are exchanged between different tools.
The OpenSCENARIO standards target the domain of closed-loop system testing for automotive functions. A Domain Model provides the semantics for the terms that are used in the Language component of OSC 2.0. In particular, an explicit specification of the Domain Model, e.g. in the form of a DL ontology, enables the preservation of semantics when scenario definitions are exchanged between different tools.
The <<Entity Definition>> builds the core of the Domain Model. This definition should cover all objects that are necessary to describe a wide range of relevant scenarios. The definitions of the identified entities should be unambiguous and should include the main properties and possible actions of each entity. The development of the entity definition will follow two tracks. First, the existing domain model of OSC 1.0 needs to be analyzed and transferred to OSC 2.0 to ensure compatibility between the two versions of the standard. Second, the already identified gaps in OSC 1.0 need to be closed by extending the Domain Model.
The <<Entity Definition>> work package provides the foundation of the Domain Model. This definition should cover all of the entities that are necessary to create scenarios according to the requirements identified in the concept document. The definitions must be unambiguous and include the characteristic properties and possible actions of each entity. The development of the entity definition will follow two tracks. First, the existing entity definitions of OSC 1.0 will be analyzed for migration to OSC 2.0 to ensure compatibility between the two versions of the standard. Second, the already identified gaps in OSC 1.0 will be closed by extending the Domain Model with additional entity definitions.
It will neither be possible nor meaningful to try to attempt to cover all possible scenarios and simulators with the entity definition of OSC 2.0. Therefore, a technical concept on a standard-conform <<Extensibility>> of the Domain Model needs to be developed.
It will neither be possible nor meaningful to try to attempt to cover all possible scenarios and simulators with the entity definition of OSC 2.0. Therefore, a technical concept on a standard-conform <<Extensibility>> of the Domain Model needs to be developed.
Another pillar of the Domain Model is the definition of the relationships between the entities with predicate logic. Such an <<Ontology>> will support an unambiguous formulation and categorization of scenarios as it enables inferrment with natural language.
As identified in the concept document, the Domain Model for OpenSCENARIO 2.0 should be specified using some form of predicate logic in order to achieve maximum clarity and portability. This is particularly important for defining the types of relationships that can hold between entities. The <<Ontology>> work package provides this formal specification of the Domain Model in the form of an ontology, possibly using one of the description logics supported by the W3C OWL standard. Having the Domain Model expressed as a formal ontology enables the use of reasoning software for classifying and matching scenario descriptions as well as providing a basis for computer inference that can assist human authors in creating scenario descriptions in natural language that are logically coherent and semantically valid.
==== Entity Definition
[NOTE]
Responsibles for filling this sub-chapter: J. Tscheak (maybe), M. Kluge, J.Kaths, F. Bock (maybe), S. Rosenberg (maybe)
Persons responsible for filling this sub-chapter: M. Kluge, S.Kraines
The definition of the domain model specific entities is essential as they build the vocabulary of the new language. A full support of the https://www.asam.net/standards/detail/openscenario/#[OpenSCENARIO 1.0 standard], which has already been released by ASAM, is one major requirement for OpenSCENARIO 2.0. This includes a full migration path from the 1.x versions to the language to be developed in this project, which directly leads to the first work packages for the domain model group:
Clear and unambiguous definitions of all of the key entities in the Domain Model are essential for providing the semantics for the vocabulary of the new domain specific language. One major requirement for OpenSCENARIO 2.0 given in the concept document is full support of the https://www.asam.net/standards/detail/openscenario/#[OpenSCENARIO 1.0 standard], which has already been released by ASAM. This includes a full migration path from the 1.x versions to the domain specific language to be developed in OpenSCENARIO 2.0, to be delivered by WP_DM1_Transfer1x.
*WP_DM1_Transfer1x*
The domain model, that has been defined in the https://www.asam.net/index.php?eID=dumpFile&t=f&f=3460&token=14e7c7fab9c9b75118bb4939c725738fa0521fe9[OpenSCENARIO 2.0 Concept Project], did not focus on the compatibility to OpenSCENARIO 1.0. However, OpenSCENARIO 1.0 already contains multiple domain model entities, for which possible deviations to the new model have to be identified. For each of those deviations it has to be defined how they should be handled in order to achieve compatibility. Inconsistent naming and terminology has to be resolved or, if this is not feasible, a mapping between entities in both models has to be defined. All entities in the 1.0 model must have a counterpart in 2.0.
The entity definitions given for the Domain Model in the concept document (https://www.asam.net/index.php?eID=dumpFile&t=f&f=3460&token=14e7c7fab9c9b75118bb4939c725738fa0521fe9[OpenSCENARIO 2.0 Concept Project]) did not address support for OpenSCENARIO 1.0. OpenSCENARIO 1.0 already contains multiple definitions for entities, which may not be compatible with the entity definitions given in the OpenSCENARIO 2.0 concept document. All entities in the 1.0 model must have a counterpart in 2.0. Inconsistencies in naming and scope must be resolved or, if this is not feasible, a mapping between entities in both models has to be defined.
[NOTE]
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)
*WP_DM2_Extend2x*
The need to extend the domain model of OSC 1.0 has been identified in the initiation phase of OSC 2.0. The model draft of the OSC 2.0 concept project provides an initial draft for such an extension. During the development of OSC 2.0, it needs to be refined and extended, as the result of the concept project focused on "most important properties, attributes, possible actions and interrelations.". New entities, their actions and attributes have to defined, for example to cover high-level scenario descriptions, which will be introduced in OpenSCENARIO 2.0. All different use cases for the scenario definition and contents from the 1.0 domain model have to be properly integrated in the final model for 2.0. As experienced in the OSC 2.0 concept project, a close working-level interaction and interrelation with the language group is essential for the success of this work package. This needs to be established already in the beginning of the project.
The need to extend the entity definitions of OSC 1.0 has been identified in the initiation phase of OSC 2.0. The OSC 2.0 concept document provides an initial draft for such an extension. This extension will be refined by focusing on "most important properties, attributes, possible actions and interrelations." All different use cases for the scenario definition in OSC 1.0 must be properly handled by the OSC 2.0 domain specific language. In addition, new entities must be defined, together with their actions and attributes, e.g. to cover the high-level scenario descriptions to be introduced in OpenSCENARIO 2.0. Drawing from experiences in the OSC 2.0 concept project, the team developing this work package will interact closely with the language group.
==== Extensibility
A standard domain model allows users to:
......@@ -66,15 +66,19 @@ On top of addition extensions, user may want to ignore parts of the domain model
Later, these new extensions be efficiently leveraged for automated user-defined scenarios.
==== Ontology
Responsibles for filling this sub-chapter: F. Sanchez, I. Whiteside, P. Parekh, S. Kraines (maybe), M. Nieto (maybe)
WP DM-Ontology - Develop ontology to establish relations between entities
* 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)
===== Ontology
[NOTE]
Persons responsible for filling this sub-chapter: S. Kraines, I. Whiteside
This work package will to leverage the outcomes of the OpenX Ontology project in order to provide a clear and unambiguous conceptual foundation for the OSC2.0 Domain Model. It is envisaged that some form of description logic will be applied and that lessons will be drawn from existing applications of ontologies in industry. Technologies to be evaluated in the work package include upper level ontologies, W3C standards, reasoning engines, and authoring tools.
Deliverables:
- definitions of main OSC2.0 terms using concepts and relationships from the OpenX Ontology
- guidelines for how to use semantic inference to classify and match scenario descriptions based on their meaning
- guidelines for how to implement computer reasoning to identify semantic errors in scenario definitions
- guidelines for how to use computer reasoning to assist people in creating abstract-level scenarios that are complete and logically coherent
=== Language Concepts
......
Markdown is supported
0% or .
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment