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

Add 2.1.2 Considerations for 1.x J.Krasser

parent a6252d71
......@@ -128,6 +128,23 @@ Finally, the overall semantics of the language should be clearly and unambigousl
Also included is the definition of the exact semantics of temporal composition operators like serial, parallel and mix. Another important aspect is how to combine the two different approaches of specifying behavior: a) the declarative way (like intended for OpenScenario 2.0) and b) the more execution/command-oriented way of OpenScenario 1.0 (that still should be supported)."
===== Considerations for 1.x
OpenSCENARIO 2.0 shall be a full superset of the features of OpenSCENARIO 1.0, and it shall be possible to convert any OpenSCENARIO 1.0 scenario into an OpenSCENARIO 2.0 scenario with identical run time behavior.
This goal is partially addressed by the work on the Domain Model by ensuring that every entity of OSC 1.0 (including attributes and actions) has a respective counterpart in the OSC 2.0 domain model.
Additional concepts of OpenSCENARIO 1.0 for which a proper mapping to OpenSCENARIO 2.0 must be ensured include:
* The event-driven temporal behavior as effected by the hierarchy, state machine and condition semantics (e.g. edges) of OpenSCENARIO 1.0 storyboard elements.
* The concept of longitudinal and lateral domains of actions/controllers as well as their parallel existence.
* Basic references such as coordinates systems and unit of measure.
* Reuse-mechanisms such as Parameters and Catalogs
* Entity Selections
* Extensibility mechanisms such as Properties, UserActions and Controllers
* Routes and Trajectories
As the OpenSCENARIO 1.x standard will be further developed in parallel to this project, it will be required to constantly co-ordinate with the OpenSCENARIO 1.x project. At the end of this project a complete semantic mapping (migration path) from the most recent OpenSCENARIO 1.x version to OpenSCENARIO 2.0 shall be provided.
===== Library Concepts and Packaging (scenario definition & scenario execution)
With the expected usage of scenarios at different abstraction levels, and it being aimed at different ODDs and different automated driving systems, the need for encapsulating scenarios in libraries is obvious.
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