Skip to content

Commit fce3f0d

Browse files
clemenshabedankpmai
authored andcommitted
Minor consistency changes for traffic participants
Fix missing mention of traffic participant models in first sentence. Use version=3.3.0 for examples where top-level messages are introduced in V3.3. Signed-off-by: Pierre R. Mai <[email protected]>
1 parent c4e82a5 commit fce3f0d

File tree

1 file changed

+8
-8
lines changed

1 file changed

+8
-8
lines changed

doc/specification.rst

Lines changed: 8 additions & 8 deletions
Original file line numberDiff line numberDiff line change
@@ -2,9 +2,9 @@ OSI Sensor Model Packaging Specification
22
========================================
33

44
This document specifies the ways in which environmental effect models,
5-
sensor models and logical models using the `Open Simulation Interface`_
6-
are to be packaged for their use in simulation environments using FMI
7-
2.0.
5+
sensor models, logical models and traffic participant models using the
6+
`Open Simulation Interface`_ are to be packaged for their use in simulation
7+
environments using FMI 2.0.
88

99
This is version 1.1.0 of this document. The version number is to be
1010
interpreted according to the `Semantic Versioning Specification (SemVer)
@@ -24,7 +24,7 @@ can be packaged as FMUs:
2424
and produce ``osi::SensorView`` as output,
2525

2626
- Sensor models, which consume ``osi::SensorView`` as input and generate
27-
``osi::SensorData`` as output, and
27+
``osi::SensorData`` as output,
2828

2929
- Logical models, like e.g. sensor fusion models, which consume
3030
``osi::SensorData`` as input and produce ``osi::SensorData`` as output.
@@ -33,7 +33,7 @@ can be packaged as FMUs:
3333
and generate ``osi::TrafficUpdate`` as output. These models can
3434
internally use e.g. Environmental effect, Sensor and/or Logical models
3535
as part of a modeled autonomous vehicle, but they can also be used to
36-
implement surrounding traffic in simplified ways. Optionally traffic
36+
implement surrounding traffic in simplified ways. Optionally, traffic
3737
participant models can consume ``osi::TrafficCommand`` as input, to
3838
allow control by a scenario engine as part of the simulation.
3939

@@ -401,7 +401,7 @@ GroundTruth Initialization Parameters
401401
``causality="parameter"``, ``variability="fixed"`` and ``initial="exact"``.
402402

403403
- The MIME type of the variable MUST specify the ``type=GroundTruth``, e.g.
404-
``application/x-open-simulation-interface; type=GroundTruth; version=3.2.0``.
404+
``application/x-open-simulation-interface; type=GroundTruth; version=3.3.0``.
405405

406406
- ``OSMPGroundTruthInit`` MUST be encoded as ``osi::GroundTruth`` (see the OSI
407407
specification documentation for more details).
@@ -442,7 +442,7 @@ Traffic Update Outputs
442442

443443
- The MIME type of the variable MUST specify the ``type=TrafficUpdate``,
444444
e.g.
445-
``application/x-open-simulation-interface; type=TrafficUpdate; version=3.0.0``.
445+
``application/x-open-simulation-interface; type=TrafficUpdate; version=3.3.0``.
446446

447447
- The traffic update MUST be encoded as ``osi::TrafficUpdate`` (see the
448448
OSI specification documentation for more details).
@@ -486,7 +486,7 @@ Traffic Command Inputs
486486

487487
- The MIME type of the variable MUST specify the ``type=TrafficCommand``,
488488
e.g.
489-
``application/x-open-simulation-interface; type=TrafficCommand; version=3.0.0``.
489+
``application/x-open-simulation-interface; type=TrafficCommand; version=3.3.0``.
490490

491491
- The traffic command MUST be encoded as ``osi::TrafficCommand`` (see
492492
the OSI specification documentation for more details).

0 commit comments

Comments
 (0)