Update subchapters/3-1_work_packages.adoc

parent 0dcaac6c
Pipeline #1398 passed with stage
in 14 seconds
......@@ -46,7 +46,7 @@ This comprises the generic parts of expressions (e.g. arithmetic, logic, etc.) b
|===
|*Description* | Syntax definition of the OpenSCENARIO 2.0 language
| *Responsibles* | R. Hadar
|*Deliverable* | Full syntax definition, including grammar, of the OpenSCENARIO 2.0 language. Basic building blocks are file organization, type definitions, compound type definitions and their internals, temporals, behavior description and expressions. Integration of the other WG syntax definition into a single syntactic entity that shares the same look and feel.
|*Deliverable* | Full syntax definition, including grammar, of the OpenSCENARIO 2.0 language. Basic building blocks are file organization, type definitions, compound type definitions and their internals, temporals, behavior description and expressions. Integration of the other WG syntax definition into a single syntactic entity that shares the same look and feel. To cover functional scenarios, abstract descriptions of road topologies/infrastructure elements have to be included. For the use case of regulatory reviews, a natural-language syntax has to be supported.
| *Effort* | 100 man-days
| *Service Provider* | Documentation of language syntax. ~25% of effort.
|===
......@@ -57,7 +57,7 @@ This comprises the generic parts of expressions (e.g. arithmetic, logic, etc.) b
|===
|*Description* a| A well-defined semantics for OpenSCENARIO 2.0.
As the levels of abstraction have been raised, so the effort and understanding needed for a simulation engine to implement support for this standard is raised. As such, the semantics of a scenario become more important: to give an unambiguous understanding of a) whether that scenario could be executed at all; b) whether that scenario could be executed on a given map; c) how to execute that scenario unambiguously. #F.Bock will add description relevant to non-simulation/testing use cases (e.g. description for regulatory bodies).#
As the levels of abstraction have been raised, so the effort and understanding needed for tool developers (e.g., for simulation engines or document processors) to implement support for this standard is raised. As such, the semantics of a scenario become more important: to give an unambiguous understanding of a) whether that scenario could be executed at all; on a given map; and unambiguously. Additionally, especially for legally required reviews of functional specification documents by regulatory institutions, natural language semantics have to be covered.
| *Responsibles* | I. Whiteside
|*Deliverable* | Semantic rules for the OpenSCENARIO 2.0 language.
| *Effort* | 100 man-days
......
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