Changes in version 1.3 compared to version 1.2

Changed Classes
  • Act (Changed)
    • Annotation changed
      • New Value
        A container for maneuver groups. An Act can be only executed once, whereby the included maneuver groups can be executed several times depending on the maximum execution count within the maneuver groups. New executions are only allowed to start when all contained maneuver groups are either in the complete or standby state and the start trigger evaluates to true.
        From 1.2
        A container for maneuver groups. Can be executed several times depending on the user provided settings. New executions are only allowed to start when all contained maneuver groups are in the complete state.
    • Property 'startTrigger'. Lower cardinality changed.
      • New Value
        0
        From 1.2
        1
    • Property 'startTrigger'. Annotation changed.
      • New Value
        Defines a trigger that starts the act. If no trigger is defined, the act starts when the Storyboard enters runningState.
        From 1.2
        Defines a trigger to that starts the act.
  • Action (Changed)
    • Property 'globalAction'. Lower cardinality changed.
      • New Value
        1
        From 1.2
        0
    • Property 'userDefinedAction'. Lower cardinality changed.
      • New Value
        1
        From 1.2
        0
    • Property 'privateAction'. Lower cardinality changed.
      • New Value
        1
        From 1.2
        0
  • ActivateControllerAction (Changed)
    • Annotation changed
      • New Value
        This action activates or deactivates a user-defined controller which must be assigned to the specified entity. A controller cannot be activated in a domain in which it is not defined. Note: Although it is allowed to omit the objectControllerRef attribute for the sake of a backward compatibility if only a single user-defined controller is assigned to the concerned Entity, it is considered unmeaningful in case of multiple controllers are assigned. This is expected to be addressed in one of the follow-up major versions, where the attribute shall be defined as mandatory to exclude an ambiguity in specifying the reference controller.
        From 1.2
        This action activates or deactivates controller defined (e.g. automated, autonomous) behavior on the given entity. A controller cannot be activated in a domain in which it is not defined.
    • Property 'objectControllerRef' created.
    • Property 'controllerRef'. Annotation changed.
      • New Value
        Reference to a controller assigned to the entity.
        From 1.2
        Reference to a controller assigned to the entity. Note: Although the OpenSCENARIO v1.2 allows to omit the controllerRef attribute for the sake of a backward compatibility if only a single controller is assigned (regardless implicitly or explicitly) to the concerned Entity, it is considered unmeaningful in case of multiple controllers are assigned. This is expected to be addressed in one of the follow-up major versions, where the attribute shall be defined as mandatory to exclude an ambiguity in specifying the reference controller.
    • Property 'controllerRef'. Stereotype <<deprecated>> applied.
  • AngleCondition (Created)
  • AppearanceAction (Changed)
    • Stereotype <<XSDcomplexType>>. Tagged value 'modelGroup' changed.
      • New Value
        choice
        From 1.2
        sequence
  • AssignControllerAction (Changed)
    • Annotation changed
      • New Value
        This action assigns an object controller to the given entity defined in the enclosing PrivateAction.
        From 1.2
        This action assigns a controller to the given entity defined in the enclosing PrivateAction. Controllers could be defined inline or by using a catalog reference.
    • Property 'objectController' created.
    • Property 'controller'. Stereotype <<deprecated>> applied.
    • Property 'catalogReference'. Stereotype <<deprecated>> applied.
  • AssignRouteAction (Changed)
    • Property 'route'. Lower cardinality changed.
      • New Value
        1
        From 1.2
        0
    • Property 'catalogReference'. Lower cardinality changed.
      • New Value
        1
        From 1.2
        0
  • Axles (Changed)
    • Annotation changed
      • New Value
        A set of the axles of a vehicle. A vehicle must have a front axle and a rear axle except for trailers which may also only have a rear axle. It might have additional axles.
        From 1.2
        A set of the axles of a vehicle. A vehicle must have a front axle and a rear axle. It might have additional axles.
    • Property 'frontAxle'. Lower cardinality changed.
      • New Value
        0
        From 1.2
        1
  • ByValueCondition (Changed)
    • Property 'parameterCondition'. Lower cardinality changed.
      • New Value
        1
        From 1.2
        0
    • Property 'timeOfDayCondition'. Lower cardinality changed.
      • New Value
        1
        From 1.2
        0
    • Property 'simulationTimeCondition'. Lower cardinality changed.
      • New Value
        1
        From 1.2
        0
    • Property 'storyboardElementStateCondition'. Lower cardinality changed.
      • New Value
        1
        From 1.2
        0
    • Property 'userDefinedValueCondition'. Lower cardinality changed.
      • New Value
        1
        From 1.2
        0
    • Property 'trafficSignalCondition'. Lower cardinality changed.
      • New Value
        1
        From 1.2
        0
    • Property 'trafficSignalControllerCondition'. Lower cardinality changed.
      • New Value
        1
        From 1.2
        0
    • Property 'variableCondition'. Lower cardinality changed.
      • New Value
        1
        From 1.2
        0
  • Catalog (Changed)
    • Property 'name'. Lower cardinality changed.
      • New Value
        1
        From 1.2
        0
  • ClothoidSpline (Created)
  • ClothoidSplineSegment (Created)
  • CollisionCondition (Changed)
    • Property 'entityRef'. Lower cardinality changed.
      • New Value
        1
        From 1.2
        0
    • Property 'byType'. Lower cardinality changed.
      • New Value
        1
        From 1.2
        0
  • ComponentAnimation (Changed)
    • Stereotype <<XSDcomplexType>>. Tagged value 'modelGroup' changed.
      • New Value
        choice
        From 1.2
        sequence
  • Condition (Changed)
    • Property 'byEntityCondition'. Lower cardinality changed.
      • New Value
        1
        From 1.2
        0
    • Property 'byValueCondition'. Lower cardinality changed.
      • New Value
        1
        From 1.2
        0
  • ConnectTrailerAction (Created)
  • Controller (Changed)
    • Property 'properties'. Lower cardinality changed.
      • New Value
        0
        From 1.2
        1
    • Property 'properties'. Annotation changed.
      • New Value
        Properties of the controller.
        From 1.2
        Describing properties for the controller.
  • ControllerAction (Changed)
    • Annotation changed
      • New Value
        Action that either assigns a new controller, overrides an existing one or activates a controller.
        From 1.2
        Action that assigns a new controller or overrides an existing one.
    • Stereotype <<XSDcomplexType>>. Tagged value 'modelGroup' changed.
      • New Value
        choice
        From 1.2
        all
    • Property 'assignControllerAction'. Lower cardinality changed.
      • New Value
        1
        From 1.2
        0
    • Property 'assignControllerAction'. Stereotype <<xor>> applied.
    • Property 'overrideControllerValueAction'. Lower cardinality changed.
      • New Value
        1
        From 1.2
        0
    • Property 'overrideControllerValueAction'. Annotation changed.
      • New Value
        Override values for throttle, brake, clutch, parking brake, steering wheel or gear.
        From 1.2
        Values for throttle, brake, clutch, parking brake, steering wheel or gear.
    • Property 'overrideControllerValueAction'. Stereotype <<xor>> applied.
    • Property 'activateControllerAction'. Lower cardinality changed.
      • New Value
        1
        From 1.2
        0
    • Property 'activateControllerAction'. Stereotype <<xor>> applied.
  • ControllerDistributionEntry (Changed)
    • Property 'controller'. Lower cardinality changed.
      • New Value
        1
        From 1.2
        0
    • Property 'catalogReference'. Lower cardinality changed.
      • New Value
        1
        From 1.2
        0
  • DisconnectTrailerAction (Created)
  • EndOfRoadCondition (Changed, annotations only)
    • Annotation changed
      • New Value
        Condition becomes true after the triggering entity/entities has reached the end of a road network for a given amount of time.
        From 1.2
        Condition becomes true after the triggering entity/entities has reached the end of a road for a given amount of time.
  • EntityAction (Changed)
    • Property 'addEntityAction'. Lower cardinality changed.
      • New Value
        1
        From 1.2
        0
    • Property 'deleteEntityAction'. Lower cardinality changed.
      • New Value
        1
        From 1.2
        0
  • EntityCondition (Changed)
    • Property 'angleCondition' created.
    • Property 'relativeAngleCondition' created.
    • Property 'endOfRoadCondition'. Lower cardinality changed.
      • New Value
        1
        From 1.2
        0
    • Property 'collisionCondition'. Lower cardinality changed.
      • New Value
        1
        From 1.2
        0
    • Property 'offroadCondition'. Lower cardinality changed.
      • New Value
        1
        From 1.2
        0
    • Property 'timeHeadwayCondition'. Lower cardinality changed.
      • New Value
        1
        From 1.2
        0
    • Property 'timeToCollisionCondition'. Lower cardinality changed.
      • New Value
        1
        From 1.2
        0
    • Property 'accelerationCondition'. Lower cardinality changed.
      • New Value
        1
        From 1.2
        0
    • Property 'standStillCondition'. Lower cardinality changed.
      • New Value
        1
        From 1.2
        0
    • Property 'speedCondition'. Lower cardinality changed.
      • New Value
        1
        From 1.2
        0
    • Property 'relativeSpeedCondition'. Lower cardinality changed.
      • New Value
        1
        From 1.2
        0
    • Property 'traveledDistanceCondition'. Lower cardinality changed.
      • New Value
        1
        From 1.2
        0
    • Property 'reachPositionCondition'. Lower cardinality changed.
      • New Value
        1
        From 1.2
        0
    • Property 'distanceCondition'. Lower cardinality changed.
      • New Value
        1
        From 1.2
        0
    • Property 'relativeDistanceCondition'. Lower cardinality changed.
      • New Value
        1
        From 1.2
        0
    • Property 'relativeClearanceCondition'. Lower cardinality changed.
      • New Value
        1
        From 1.2
        0
  • EntityDistribution (Created)
  • EntityDistributionEntry (Created)
  • EntityObject (Changed)
    • Property 'catalogReference'. Lower cardinality changed.
      • New Value
        1
        From 1.2
        0
    • Property 'vehicle'. Lower cardinality changed.
      • New Value
        1
        From 1.2
        0
    • Property 'pedestrian'. Lower cardinality changed.
      • New Value
        1
        From 1.2
        0
    • Property 'miscObject'. Lower cardinality changed.
      • New Value
        1
        From 1.2
        0
    • Property 'externalObjectReference'. Lower cardinality changed.
      • New Value
        1
        From 1.2
        0
  • EnvironmentAction (Changed)
    • Property 'environment'. Lower cardinality changed.
      • New Value
        1
        From 1.2
        0
    • Property 'catalogReference'. Lower cardinality changed.
      • New Value
        1
        From 1.2
        0
  • FinalSpeed (Changed)
    • Property 'absoluteSpeed'. Lower cardinality changed.
      • New Value
        1
        From 1.2
        0
    • Property 'relativeSpeedToMaster'. Lower cardinality changed.
      • New Value
        1
        From 1.2
        0
  • GeoPosition (Changed)
    • Property 'verticalRoadSelection' created.
    • Property 'altitude'. Annotation changed.
      • New Value
        Altitude is the Earth gravity-related vertical distance along the z-axis above the road surface, specified horizontally by its Longitude/Latitude coordinates and vertically by the verticalRoadSelection attribute. When calculating the road surface, it is accounted for an elevation of the road, an entire road super-elevation, or, in more complex cases, a road lateral shape profile that are specified in the road network definition (external to the OpenSCENARIO). Missing value is interpreted as altitude=0. Unit: [m]. Range: [0..inf[.
        From 1.2
        Altitude is the Earth gravity-related vertical distance from the target position, specified horizontally by its Longitude/Latitude coordinates, to the closest point on the underlying road surface.When calculating the closest point, it is accounted for an elevation of the road, an entire road super-elevation, or, in more complex cases, a road lateral shape profile that are specified in the road network definition (external to the OpenSCENARIO).Missing value is interpreted as altitude=0. Unit: [m]. Range: [0..inf[.
    • Property 'orientation'. Annotation changed.
      • New Value
        In the case of altitude=0, the Pitch and Roll angles are determined by the underlying road surface at the target position and therefore undefined by the OpenSCENARIO standard. The absolute reference context refers to the orientation with respect to the World coordinate system, which is assumed to be the projected coordinate system based on the spherical geographic coordinate system. The relative reference context refers to the orientation with respect to the reference (s,t)-coordinate system of the lane on the road underlying the target position. The Heading angle at the target position on the (s,t)-plane can be arbitrarily specified. To calculate the Heading, the imaginary straight axis at the target position is built parallel to the tangent to the reference lane s-axis on the reference road. The Heading is counted from this imaginary axis. Missing Orientation property is interpreted as the relative reference context with Heading=Pitch=Roll=0.
        From 1.2
        In the case of altitude=0, the Pitch and Roll angles are determined by the underlying road surface at the target position and therefore undefined by the OpenSCENARIO standard. The absolute reference context refers to the orientation with respect to the World coordinate system, which is assumed to be the projected coordinate system based on the spherical geographic coordinate system. The relative reference context refers to the orientation with respect to the reference (s,t)-coordinate system of the lane on the road underlying the target position. The Heading angle at the target position on the (s,t)-plane can be arbitrarily specified. To calculate the Heading, the imaginary straight axis at the target position is built parallel to the tangent to the reference lane s-axis on the reference road. The Heading is counted from this imaginary axis. Missing Orientation property is interpreted as the absolute reference context with Heading=Pitch=Roll=0.
  • GlobalAction (Changed)
    • Property 'setMonitorAction' created.
    • Property 'environmentAction'. Lower cardinality changed.
      • New Value
        1
        From 1.2
        0
    • Property 'entityAction'. Lower cardinality changed.
      • New Value
        1
        From 1.2
        0
    • Property 'infrastructureAction'. Lower cardinality changed.
      • New Value
        1
        From 1.2
        0
    • Property 'infrastructureAction'. Stereotype <<XSDelement>>. Tagged value 'position' changed.
      • New Value
        3
        From 1.2
        4
    • Property 'parameterAction'. Lower cardinality changed.
      • New Value
        1
        From 1.2
        0
    • Property 'parameterAction'. Stereotype <<XSDelement>>. Tagged value 'position' changed.
      • New Value
        5
        From 1.2
        3
    • Property 'trafficAction'. Lower cardinality changed.
      • New Value
        1
        From 1.2
        0
    • Property 'trafficAction'. Stereotype <<XSDelement>>. Tagged value 'position' changed.
      • New Value
        6
        From 1.2
        5
    • Property 'variableAction'. Lower cardinality changed.
      • New Value
        1
        From 1.2
        0
    • Property 'variableAction'. Stereotype <<XSDelement>>. Tagged value 'position' changed.
      • New Value
        7
        From 1.2
        6
  • InRoutePosition (Changed)
    • Property 'fromCurrentEntity'. Lower cardinality changed.
      • New Value
        1
        From 1.2
        0
    • Property 'fromRoadCoordinates'. Lower cardinality changed.
      • New Value
        1
        From 1.2
        0
    • Property 'fromLaneCoordinates'. Lower cardinality changed.
      • New Value
        1
        From 1.2
        0
  • Lane (Created)
  • LaneChangeTarget (Changed)
    • Property 'relativeTargetLane'. Lower cardinality changed.
      • New Value
        1
        From 1.2
        0
    • Property 'absoluteTargetLane'. Lower cardinality changed.
      • New Value
        1
        From 1.2
        0
  • LaneOffsetTarget (Changed)
    • Property 'relativeTargetLaneOffset'. Lower cardinality changed.
      • New Value
        1
        From 1.2
        0
    • Property 'absoluteTargetLaneOffset'. Lower cardinality changed.
      • New Value
        1
        From 1.2
        0
  • LanePosition (Changed, annotations only)
    • Annotation changed
      • New Value
        Position defined in terms of the road segment (roadId), the lane (laneId) of the road, the distance (s) along the road's reference line, and the lateral offset to the lane's center line along the lane center line's t-axis. Orientation is optional. The s-coordinate and the offset should be specified so that the target position is within a road defined by roadId taken from the respective road network definition file (external to the ASAM OpenSCENARIO). If the target position would be outside the road boundaries, the z-coordinate of the position is undefined.
        From 1.2
        Position defined in terms of the road segment (roadId), the lane (laneId) of the road, the distance (s) along the road's reference line, and the lateral offset to the lane's center line along the normal to the road's reference line. Orientation is optional. The s-coordinate and the offset should be specified so that the target position is within a road defined by roadId taken from the respective road network definition file (external to the ASAM OpenSCENARIO). If the target position would be outside the road boundaries, the z-coordinate of the position is undefined.
    • Property 'offset'. Annotation changed.
      • New Value
        The lateral offset to the center line of the target lane (along the t-axis of the target lane center line). Missing value is interpreted as 0. The positive value means the offset is applied in the direction of the t-axis being imagined at the target s-position. Unit: [m].
        From 1.2
        The lateral offset to the center line of the target lane (along the normal to the road's reference line). Missing value is interpreted as 0. The positive value means the offset is applied in the direction of the t-axis being imagined at the target s-position. Unit: [m].
    • Property 'orientation'. Annotation changed.
      • New Value
        The Pitch and Roll angles are determined by the underlying road surface and therefore undefined by the OpenSCENARIO standard. The absolute reference context refers to the orientation with respect to the World coordinate system. Only the Heading angle at the target position can be arbitrarily specified on the (X,Y)-plane counting from the X-axis. The relative reference context refers to the orientation with respect to the (s,t)-coordinate system of the target lane that is considered a reference orientation. Only the Heading angle at the target position can be arbitrarily specified on the (s,t)-plane counting from the tangent to the lane s-axis at the point with the target s-coordinate. Missing Orientation property is interpreted as the relative reference context with Heading=Pitch=Roll=0.
        From 1.2
        The Pitch and Roll angles are determined by the underlying road surface and therefore undefined by the OpenSCENARIO standard. The absolute reference context refers to the orientation with respect to the World coordinate system. Only the Heading angle at the target position can be arbitrarily specified on the (X,Y)-plane counting from the X-axis. The relative reference context refers to the orientation with respect to the (s,t)-coordinate system of the target road that is considered a reference orientation. Only the Heading angle at the target position can be arbitrarily specified on the (s,t)-plane counting from the tangent to the road s-axis at the point with the target s-coordinate. Missing Orientation property is interpreted as the absolute reference context with Heading=Pitch=Roll=0.
  • LateralAction (Changed)
    • Property 'laneChangeAction'. Lower cardinality changed.
      • New Value
        1
        From 1.2
        0
    • Property 'laneOffsetAction'. Lower cardinality changed.
      • New Value
        1
        From 1.2
        0
    • Property 'lateralDistanceAction'. Lower cardinality changed.
      • New Value
        1
        From 1.2
        0
  • LightType (Changed)
    • Stereotype <<XSDcomplexType>>. Tagged value 'modelGroup' changed.
      • New Value
        choice
        From 1.2
        sequence
  • LogNormalDistribution (Created)
  • LongitudinalAction (Changed)
    • Property 'speedAction'. Lower cardinality changed.
      • New Value
        1
        From 1.2
        0
    • Property 'longitudinalDistanceAction'. Lower cardinality changed.
      • New Value
        1
        From 1.2
        0
    • Property 'speedProfileAction'. Lower cardinality changed.
      • New Value
        1
        From 1.2
        0
  • MiscObject (Changed)
    • Property 'properties'. Lower cardinality changed.
      • New Value
        0
        From 1.2
        1
    • Property 'properties'. Annotation changed.
      • New Value
        Properties of the miscellaneous object.
        From 1.2
        Property definitions for the miscellaneous object.
  • ModifyRule (Changed)
    • Property 'addValue'. Lower cardinality changed.
      • New Value
        1
        From 1.2
        0
    • Property 'multiplyByValue'. Lower cardinality changed.
      • New Value
        1
        From 1.2
        0
  • MonitorDeclaration (Created)
  • ObjectController (Changed)
    • Property 'name' created.
    • Property 'catalogReference'. Lower cardinality changed.
      • New Value
        1
        From 1.2
        0
    • Property 'controller'. Lower cardinality changed.
      • New Value
        1
        From 1.2
        0
  • Orientation (Changed, annotations only)
    • Property 'type'. Annotation changed.
      • New Value
        Relative or absolute definition. Missing type value is interpreted as relative.
        From 1.2
        Relative or absolute definition. Missing type value is interpreted as absolute.
  • ParameterAction (Changed)
    • Property 'setAction'. Lower cardinality changed.
      • New Value
        1
        From 1.2
        0
    • Property 'modifyAction'. Lower cardinality changed.
      • New Value
        1
        From 1.2
        0
  • Pedestrian (Changed)
    • Property 'properties'. Lower cardinality changed.
      • New Value
        0
        From 1.2
        1
    • Property 'properties'. Annotation changed.
      • New Value
        Properties of the pedestrian.
        From 1.2
        Properties (values/files) of the pedestrian.
  • Phase (Changed)
    • Annotation changed
      • New Value
        Phase of a TrafficSignalController. A TrafficSignalController has sequential semantic phases, forming the signal cycle. Each semantic phase can have multiple TrafficSignalStates or one TrafficSignalGroupState (mutually exclusive). When TrafficSignalStates are used to model the observable states of a traffic signal individually, exactly one TrafficSignalState has to be defined for every traffic signal controlled by this TrafficSignalController. The semantic phase information like go, attention, stop, etc. is set in Phase attribute name and the observable state like the visual information "off;off;on" in trafficSignalStates or trafficSignalGroupState.
        From 1.2
        Phase of a TrafficSignalController. A TrafficSignalController has sequential phases. Each phase can have multiple TrafficSignalStates or one TrafficSignalGroupState (mutually exclusive). When TrafficSignalStates are used to model the states of a traffic signal individually, exactly one TrafficSignalState has to be defined for every traffic signal controlled by this TrafficSignalController. The semantic information like go, attention, stop, etc. is set in Phase attribute name and the state like the visual information "off;off;on" in trafficSignalStates or trafficSignalGroupState.
    • Property 'trafficSignalGroupState' created.
    • Property 'trafficeSignalGroupState' removed.
    • Property 'trafficSignalStates'. Annotation changed.
      • New Value
        Each phase can have multiple TrafficSignalStates to provide the observable state for all traffic signals individually that are controlled by the controller. One for each TrafficSignal. E.g. name="go" (trafficSignal1:"off;off;on", trafficSignal2:"off;off;on").
        From 1.2
        Each phase can have multiple TrafficSignalStates to provide the state for all traffic signals individually that are controlled by the controller. One for each TrafficSignal. E.g. name="go" (trafficSignal1:"off;off;on", trafficSignal2:"off;off;on").
  • Polygon (Created)
  • Position (Changed)
    • Property 'worldPosition'. Lower cardinality changed.
      • New Value
        1
        From 1.2
        0
    • Property 'relativeWorldPosition'. Lower cardinality changed.
      • New Value
        1
        From 1.2
        0
    • Property 'relativeObjectPosition'. Lower cardinality changed.
      • New Value
        1
        From 1.2
        0
    • Property 'roadPosition'. Lower cardinality changed.
      • New Value
        1
        From 1.2
        0
    • Property 'relativeRoadPosition'. Lower cardinality changed.
      • New Value
        1
        From 1.2
        0
    • Property 'lanePosition'. Lower cardinality changed.
      • New Value
        1
        From 1.2
        0
    • Property 'relativeLanePosition'. Lower cardinality changed.
      • New Value
        1
        From 1.2
        0
    • Property 'routePosition'. Lower cardinality changed.
      • New Value
        1
        From 1.2
        0
    • Property 'geoPosition'. Lower cardinality changed.
      • New Value
        1
        From 1.2
        0
    • Property 'trajectoryPosition'. Lower cardinality changed.
      • New Value
        1
        From 1.2
        0
  • PositionInLaneCoordinates (Changed, annotations only)
    • Property 'pathS'. Annotation changed.
      • New Value
        Position in s coordinates along the reference line of the route. Unit: [m]. Range: [0..inf[.
        From 1.2
        s-coordinate of the actual position. Unit: [m]. Range: [0..inf[.
  • PrivateAction (Changed)
    • Property 'trailerAction' created.
    • Property 'longitudinalAction'. Lower cardinality changed.
      • New Value
        1
        From 1.2
        0
    • Property 'lateralAction'. Lower cardinality changed.
      • New Value
        1
        From 1.2
        0
    • Property 'visibilityAction'. Lower cardinality changed.
      • New Value
        1
        From 1.2
        0
    • Property 'synchronizeAction'. Lower cardinality changed.
      • New Value
        1
        From 1.2
        0
    • Property 'activateControllerAction'. Lower cardinality changed.
      • New Value
        1
        From 1.2
        0
    • Property 'controllerAction'. Lower cardinality changed.
      • New Value
        1
        From 1.2
        0
    • Property 'teleportAction'. Lower cardinality changed.
      • New Value
        1
        From 1.2
        0
    • Property 'routingAction'. Lower cardinality changed.
      • New Value
        1
        From 1.2
        0
    • Property 'appearanceAction'. Lower cardinality changed.
      • New Value
        1
        From 1.2
        0
  • RandomRouteAction (Created)
  • RelativeAngleCondition (Created)
  • RelativeLanePosition (Changed, annotations only)
    • Property 'offset'. Annotation changed.
      • New Value
        The lateral offset to the center line of the target lane (along the t-axis of the target lane center line). Missing value is interpreted as 0. The positive value means the offset is applied in the direction of the t-axis being imagined at the target s-position. Unit: [m].
        From 1.2
        The lateral offset to the center line of the target lane (along the normal to the road's reference line). Missing value is interpreted as 0. The positive value means the offset is applied in the direction of the t-axis being imagined at the target s-position. Unit: [m].
    • Property 'orientation'. Annotation changed.
      • New Value
        The Pitch and Roll angles are determined by the underlying road surface at the target position and therefore undefined by the OpenSCENARIO standard. The absolute reference context refers to the orientation with respect to the World coordinate system. Only the Heading angle at the target position can be arbitrarily specified on the (X,Y)-plane counting from the X-axis. The relative reference context refers to the orientation with respect to the (s,t)-coordinate system of the lane where the target position is located. Only the Heading angle at the target position on the (s,t)-plane can be arbitrarily specified. To calculate the Heading, the imaginary straight axis at the target position is built parallel to the tangent to the lane s-axis at the target s-position on the target road s-axis. The Heading is counted from this imaginary axis. Missing Orientation property is interpreted as the relative reference context with Heading=Pitch=Roll=0.
        From 1.2
        The Pitch and Roll angles are determined by the underlying road surface at the target position and therefore undefined by the OpenSCENARIO standard. The absolute reference context refers to the orientation with respect to the World coordinate system. Only the Heading angle at the target position can be arbitrarily specified on the (X,Y)-plane counting from the X-axis. The relative reference context refers to the orientation with respect to the (s,t)-coordinate system of the lane where the reference entity is located. Only the Heading angle at the target position on the (s,t)-plane can be arbitrarily specified. To calculate the Heading, the imaginary straight axis at the target position is built parallel to the tangent to the reference lane s-axis at the reference entity s-position on the reference road s-axis. The Heading is counted from this imaginary axis. Missing Orientation property is interpreted as the absolute reference context with Heading=Pitch=Roll=0.
  • RelativeLaneRange (Changed, annotations only)
    • Annotation changed
      • New Value
        A range of lanes to the left and/or right of a referenced entity. The properties "from" and "to" define the signed numbers of lanes that are offset the referenced entity's current lane. (0 is the entity's current lane, positive is left of the entity, negative is right of the entity). Set "from" and "to" to the same number in order to check clearance for only one lane.
        From 1.2
        A range of lanes to the left and/or right of a referenced entity. The properties "from" and "to" define the signed numbers of lanes that are offset the referenced entity's current lane. (0 is the entity's current lane, positive is left of the entity, negative is right of the entity).
    • Property 'from'. Annotation changed.
      • New Value
        The lower limit of the range. Range: [-inf, inf[. Default if omitted: -inf
        From 1.2
        The lower limit of the range, if missing "-inf"
    • Property 'to'. Annotation changed.
      • New Value
        The upper limit of the range. Range: ]-inf, inf]. Default if omitted: +inf
        From 1.2
        The upper limit of the range, if missing "+inf"
  • RelativeObjectPosition (Changed, annotations only)
    • Property 'orientation'. Annotation changed.
      • New Value
        The absolute reference context refers to the orientation with respect to the World coordinate system (i.e., the orientation of the reference entity is ignored). The relative reference context refers to the orientation with respect to the corresponding axes of the local (X,Y,Z)-coordinate system of the reference entity. Missing Orientation property is interpreted as the relative reference context with Heading=Pitch=Roll=0.
        From 1.2
        The absolute reference context refers to the orientation with respect to the World coordinate system (i.e., the orientation of the reference entity is ignored). The relative reference context refers to the orientation with respect to the corresponding axes of the local (X,Y,Z)-coordinate system of the reference entity. Missing Orientation property is interpreted as the absolute reference context with Heading=Pitch=Roll=0.
  • RelativeRoadPosition (Changed, annotations only)
    • Property 'orientation'. Annotation changed.
      • New Value
        The Pitch and Roll angles are determined by the underlying road surface at the target position and therefore undefined by the OpenSCENARIO standard. The absolute reference context refers to the orientation with respect to the World coordinate system. Only the Heading angle at the target position can be arbitrarily specified on the (X,Y)-plane counting from the X-axis. The relative reference context refers to the orientation with respect to the (s,t)-coordinate system of the road at the target position. Only the Heading angle at the target position on the (s,t)-plane can be arbitrarily specified. To calculate the Heading, the imaginary straight axis at the target position is built parallel to the tangent to the road s-axis at the s-position of the target position. The Heading is counted from this imaginary axis. Missing Orientation property is interpreted as the relative reference context with Heading=Pitch=Roll=0.
        From 1.2
        The Pitch and Roll angles are determined by the underlying road surface at the target position and therefore undefined by the OpenSCENARIO standard. The absolute reference context refers to the orientation with respect to the World coordinate system. Only the Heading angle at the target position can be arbitrarily specified on the (X,Y)-plane counting from the X-axis. The relative reference context refers to the orientation with respect to the (s,t)-coordinate system of the road of the reference entity. Only the Heading angle at the target position on the (s,t)-plane can be arbitrarily specified. To calculate the Heading, the imaginary straight axis at the target position is built parallel to the tangent to the reference road s-axis at the s-position of the reference entity. The Heading is counted from this imaginary axis. Missing Orientation property is interpreted as the absolute reference context with Heading=Pitch=Roll=0.
  • RelativeSpeedCondition (Changed, annotations only)
    • Property 'value'. Annotation changed.
      • New Value
        Relative speed value. Unit: [m/s]. Range: ]-inf..inf[. Relative speed is defined as speed_rel = speed(triggering entity) - speed(reference entity)
        From 1.2
        Relative speed value. Unit: [m/s].
  • RelativeTargetLane (Changed, annotations only)
    • Annotation changed
      • New Value
        Target lane defined as difference compared to the reference entity's current lane evaluated in the reference entity's coordinate system. I.e. positive values refer to lanes in the positive y-axis of the reference entity's coordinate system, negative values refer to lanes in the negative y-axis respectively. For ASAM OpenDRIVE maps, the road center lane is not counted as a lane and thus omitted.
        From 1.2
        Defines the relative lane offset to a reference entity as target for a LaneChangeTarget.
    • Property 'value'. Annotation changed.
      • New Value
        Signed number defining the target lane as difference compared to the reference entity's current lane evaluated in the reference entity's coordinate system.
        From 1.2
        Signed number of lanes that is offset the reference entity's current lane.
  • RelativeWorldPosition (Changed, annotations only)
    • Property 'orientation'. Annotation changed.
      • New Value
        The absolute reference context refers to the orientation with respect to the World coordinate system (i.e., the orientation of the reference entity is ignored). The relative reference context refers to the angular shift of orientation angles with respect to the corresponding orientation angles of the reference entity in the World coordinate system. The positive value means a counter-clockwise shift. Missing Orientation property is interpreted as the relative reference context with Heading=Pitch=Roll=0.
        From 1.2
        The absolute reference context refers to the orientation with respect to the World coordinate system (i.e., the orientation of the reference entity is ignored). The relative reference context refers to the angular shift of orientation angles with respect to the corresponding orientation angles of the reference entity in the World coordinate system. The positive value means a counter-clockwise shift. Missing Orientation property is interpreted as the absolute reference context with Heading=Pitch=Roll=0.
  • RoadCursor (Created)
  • RoadPosition (Changed, annotations only)
    • Property 'orientation'. Annotation changed.
      • New Value
        The Pitch and Roll angles are determined by the underlying road surface and therefore undefined by the OpenSCENARIO standard. The absolute reference context refers to the orientation with respect to the World coordinate system. Only the Heading angle at the target position can be arbitrarily specified on the (X,Y)-plane counting from the X-axis. The relative reference context refers to the orientation with respect to the (s,t)-coordinate system of the target road that is considered a reference orientation. Only the Heading angle at the target position can be arbitrarily specified on the (s,t)-plane counting from the tangent to the road s-axis at the point with the target s-coordinate. Missing Orientation property is interpreted as the relative reference context with Heading=Pitch=Roll=0.
        From 1.2
        The Pitch and Roll angles are determined by the underlying road surface and therefore undefined by the OpenSCENARIO standard. The absolute reference context refers to the orientation with respect to the World coordinate system. Only the Heading angle at the target position can be arbitrarily specified on the (X,Y)-plane counting from the X-axis. The relative reference context refers to the orientation with respect to the (s,t)-coordinate system of the target road that is considered a reference orientation. Only the Heading angle at the target position can be arbitrarily specified on the (s,t)-plane counting from the tangent to the road s-axis at the point with the target s-coordinate. Missing Orientation property is interpreted as the absolute reference context with Heading=Pitch=Roll=0.
  • RoadRange (Created)
  • RoutePosition (Changed, annotations only)
    • Property 'orientation'. Annotation changed.
      • New Value
        Orientation. The relative reference context refers to the referenced road's s and t coordinates, to the current lane's s and t coordinates or to the orientation of the reference entity. Missing Orientation property is interpreted as the relative reference context with Heading=Pitch=Roll=0.
        From 1.2
        Orientation. The relative reference context refers to the referenced road's s and t coordinates, to the current lane's s and t coordinates or to the orientation of the reference entity. Missing value is interpreted as (heading=0, pitch=0, roll=0, type='absolute').
  • RouteRef (Changed)
    • Property 'route'. Lower cardinality changed.
      • New Value
        1
        From 1.2
        0
    • Property 'catalogReference'. Lower cardinality changed.
      • New Value
        1
        From 1.2
        0
  • RoutingAction (Changed)
    • Annotation changed
      • New Value
        Controls entity routing, either by following a predefined route or trajectory, alternatively by specifying a destination position which the entity should aim to reach. Further, it can be enforced that an entity selects its routing at each junction randomly.
        From 1.2
        Controls entity routing, either by following a predefined route or trajectory, alternatively by specifying a destination position which the entity should aim to reach.
    • Property 'randomRouteAction' created.
    • Property 'assignRouteAction'. Lower cardinality changed.
      • New Value
        1
        From 1.2
        0
    • Property 'followTrajectoryAction'. Lower cardinality changed.
      • New Value
        1
        From 1.2
        0
    • Property 'acquirePositionAction'. Lower cardinality changed.
      • New Value
        1
        From 1.2
        0
  • ScenarioDefinition (Changed)
    • Property 'monitorDeclarations' created.
    • Property 'catalogLocations'. Stereotype <<XSDelement>>. Tagged value 'position' changed.
      • New Value
        4
        From 1.2
        3
    • Property 'roadNetwork'. Stereotype <<XSDelement>>. Tagged value 'position' changed.
      • New Value
        5
        From 1.2
        4
    • Property 'entities'. Stereotype <<XSDelement>>. Tagged value 'position' changed.
      • New Value
        6
        From 1.2
        5
    • Property 'storyboard'. Stereotype <<XSDelement>>. Tagged value 'position' changed.
      • New Value
        7
        From 1.2
        6
  • ScenarioObjectTemplate (Created)
  • SelectedEntities (Changed)
    • Property 'entityRef'. Lower cardinality changed.
      • New Value
        1
        From 1.2
        0
    • Property 'byType'. Lower cardinality changed.
      • New Value
        1
        From 1.2
        0
  • SetMonitorAction (Created)
  • Shape (Changed)
    • Property 'clothoidSpline' created.
    • Property 'polyline'. Lower cardinality changed.
      • New Value
        1
        From 1.2
        0
    • Property 'clothoid'. Lower cardinality changed.
      • New Value
        1
        From 1.2
        0
    • Property 'nurbs'. Lower cardinality changed.
      • New Value
        1
        From 1.2
        0
    • Property 'nurbs'. Stereotype <<XSDelement>>. Tagged value 'position' changed.
      • New Value
        4
        From 1.2
        3
  • SpeedActionTarget (Changed)
    • Property 'relativeTargetSpeed'. Lower cardinality changed.
      • New Value
        1
        From 1.2
        0
    • Property 'absoluteTargetSpeed'. Lower cardinality changed.
      • New Value
        1
        From 1.2
        0
  • StochasticDistributionType (Changed)
    • Property 'logNormalDistribution' created.
    • Property 'uniformDistribution'. Stereotype <<XSDelement>>. Tagged value 'position' changed.
      • New Value
        4
        From 1.2
        3
    • Property 'poissonDistribution'. Stereotype <<XSDelement>>. Tagged value 'position' changed.
      • New Value
        5
        From 1.2
        4
    • Property 'histogram'. Stereotype <<XSDelement>>. Tagged value 'position' changed.
      • New Value
        6
        From 1.2
        5
    • Property 'userDefinedDistribution'. Stereotype <<XSDelement>>. Tagged value 'position' changed.
      • New Value
        7
        From 1.2
        6
  • Storyboard (Changed)
    • Property 'stopTrigger'. Lower cardinality changed.
      • New Value
        0
        From 1.2
        1
    • Property 'stopTrigger'. Annotation changed.
      • New Value
        Trigger to stop the Storyboard instance. If no trigger is defined, the Storyboard will be never stopped.
        From 1.2
        Trigger to stop the Storyboard instance.
  • TimeReference (Changed)
    • Property 'none'. Lower cardinality changed.
      • New Value
        1
        From 1.2
        0
    • Property 'timing'. Lower cardinality changed.
      • New Value
        1
        From 1.2
        0
  • TimeToCollisionConditionTarget (Changed)
    • Property 'position'. Lower cardinality changed.
      • New Value
        1
        From 1.2
        0
    • Property 'entityRef'. Lower cardinality changed.
      • New Value
        1
        From 1.2
        0
  • TrafficAction (Changed)
    • Property 'trafficAreaAction' created.
    • Property 'trafficSourceAction'. Lower cardinality changed.
      • New Value
        1
        From 1.2
        0
    • Property 'trafficSinkAction'. Lower cardinality changed.
      • New Value
        1
        From 1.2
        0
    • Property 'trafficSwarmAction'. Lower cardinality changed.
      • New Value
        1
        From 1.2
        0
    • Property 'trafficStopAction'. Lower cardinality changed.
      • New Value
        1
        From 1.2
        0
    • Property 'trafficStopAction'. Annotation changed.
      • New Value
        Stops traffic instances (area, swarm, source, sink).
        From 1.2
        Stops traffic instances (swarm, source, sink).
    • Property 'trafficStopAction'. Stereotype <<XSDelement>>. Tagged value 'position' changed.
      • New Value
        5
        From 1.2
        4
  • TrafficArea (Created)
  • TrafficAreaAction (Created)
  • TrafficDefinition (Changed, annotations only)
    • Annotation changed
      • New Value
        Definition of macroscopic traffic based on vehicle and controller definitions.
        From 1.2
        Definition of macroscopic traffic based on vehicle and controller definitions.
  • TrafficDistribution (Created)
  • TrafficDistributionEntry (Created)
  • TrafficSignalAction (Changed)
    • Annotation changed
      • New Value
        Action used to change the state of a traffic signal.
        From 1.2
        Action used to set or override a signals state or a signal controllers state.
    • Property 'trafficSignalControllerAction'. Lower cardinality changed.
      • New Value
        1
        From 1.2
        0
    • Property 'trafficSignalControllerAction'. Annotation changed.
      • New Value
        Action used to set a semantic phase of a TrafficSignalController.
        From 1.2
        Action used to control the state of a signal.
    • Property 'trafficSignalStateAction'. Lower cardinality changed.
      • New Value
        1
        From 1.2
        0
    • Property 'trafficSignalStateAction'. Annotation changed.
      • New Value
        Action used to control the observable state of a signal.
        From 1.2
        Action used to set a specific phase of a signal controller.
  • TrafficSignalCondition (Changed, annotations only)
    • Annotation changed
      • New Value
        Considered true if a referenced traffic signal (e.g. from an OpenDRIVE file) reaches a specific observable state.
        From 1.2
        Considered true if a referenced traffic signal (e.g. from an OpenDRIVE file) reaches a specific states. Signal IDs are listed in the TrafficSignal list of the RoadNetwork together with their states and their controllers to enable dynamic signal modelling.
    • Property 'name'. Annotation changed.
      • New Value
        ID of the referenced signal in a road network file.
        From 1.2
        ID of the referenced signal defined in a road network. The signal ID must be listed in the TrafficSignal list of the RoadNetwork section.
    • Property 'state'. Annotation changed.
      • New Value
        Observable state of the signal to be reached for the condition to become true.
        From 1.2
        State of the signal to be reached for the condition to become true.
  • TrafficSignalController (Changed, annotations only)
    • Annotation changed
      • New Value
        The TrafficSignalController provides a signal cycle to a single signal or a signal group.
        From 1.2
        The controller provides identical Phases for one or more dynamic signals. Controllers serve as wrappers for the behavior of a group of signals. (see OpenDRIVE definition of a Controller and civil engineering specifications like the German "Richtlinien für Lichtsignalanlagen" about Signalgroups)
    • Property 'name'. Annotation changed.
      • New Value
        ID of the TrafficSignalController for reference within the scenario and the reference to an OpenDRIVE signal group ID.
        From 1.2
        ID of the traffic signal controller in the road network, e.g. a OpenDRIVE controller ID.
    • Property 'reference'. Annotation changed.
      • New Value
        A reference (ID) to a TrafficSignalController. If reference is set, a delay is required.
        From 1.2
        A reference (ID) to the connected controller in the road network. If reference is set, a delay is required.
    • Property 'phases'. Annotation changed.
      • New Value
        Semantic phases of a TrafficSignalController, forming the signal cycle.
        From 1.2
        Phases of a TrafficSignalController.
  • TrafficSignalControllerAction (Changed, annotations only)
    • Annotation changed
      • New Value
        Sets a specific semantic phase of a traffic signal controller, typically affecting a signal group.
        From 1.2
        Sets a specific phase of a traffic signal controller, typically affecting a collection of signals.
    • Property 'phase'. Annotation changed.
      • New Value
        Targeted phase of the signal controller.
        From 1.2
        Targeted phase of the signal controller. The available phases are defined in type RoadNetwork under the property trafficSignalControllers.
    • Property 'phaseRef'. Annotation changed.
      • New Value
        The reference to the semantic phase (phase is the referential key in the referenced TrafficSignalController).
        From 1.2
        The reference to the phase (phase is the referential key in the referenced TrafficSignalController).
  • TrafficSignalControllerCondition (Changed, annotations only)
    • Annotation changed
      • New Value
        Considered true if a given TrafficSignalController (which shall be defined within OpenSCENARIO) reaches a specific semantic phase.
        From 1.2
        Considered true if a given traffic signal controller (which may be defined within OpenSCENARIO or externally) reaches a specific state.
    • Property 'phase'. Annotation changed.
      • New Value
        Name of the referenced phase of the TrafficSignalController to be reached for the condition to become true.
        From 1.2
        Name of the phase of the signal controller to be reached for the condition to become true. The available phases are defined in type RoadNetwork under the property trafficSignalControllers.
    • Property 'trafficSignalControllerRef'. Annotation changed.
      • New Value
        Name of the referenced TrafficSignalController.
        From 1.2
        ID of the referenced signal controller in a road network.
    • Property 'phaseRef'. Annotation changed.
      • New Value
        The reference to the semantic phase (phase is the referential key in the referenced TrafficSignalController).
        From 1.2
        The reference to the phase (phase is the referential key in the referenced TrafficSignalController).
  • TrafficSignalGroupState (Changed, annotations only)
    • Annotation changed
      • New Value
        Observable state of a traffic signal group within one semantic phase.
        From 1.2
        State of a traffic signal group controlled with the same controller within a phase. One group state per phase.
    • Property 'state'. Annotation changed.
      • New Value
        Observable state of all signals controlled by this TrafficSignalController, e.g. the visual information "off;off;on". The number of values in the state depends on the traffic signal in the roadnetwork , e.g. type and subtype in OpenDRIVE
        From 1.2
        State of all signals controlled by this TrafficSignalController, e.g. the visual information "off;off;on". The number of values in the state depends on the traffic signal in the roadnetwork , e.g. type and subtype in OpenDRIVE
  • TrafficSignalState (Changed, annotations only)
    • Property 'state'. Annotation changed.
      • New Value
        Observable state of the signal, e.g. "off;off;on". The number of values in the state depends on the traffic signal in the roadnetwork , e.g. type and subtype in OpenDRIVE
        From 1.2
        State of the signal, e.g. the visual information "off;off;on". The number of values in the state depends on the traffic signal in the roadnetwork , e.g. type and subtype in OpenDRIVE
    • Property 'trafficSignalId'. Annotation changed.
      • New Value
        ID of the referenced signal in a road network file.
        From 1.2
        ID of the referenced signal in a road network. The signal ID must be listed in TrafficSignal list of the RoadNetwork.
  • TrafficSignalStateAction (Changed, annotations only)
    • Annotation changed
      • New Value
        Controls the observable state of a traffic signal.
        From 1.2
        Controls the state of a traffic signal.
    • Property 'name'. Annotation changed.
      • New Value
        ID of a signal in a road network file.
        From 1.2
        ID of a signal in a road network. The signal ID must be listed in the TrafficSignal list of the RoadNetwork.
    • Property 'state'. Annotation changed.
      • New Value
        Targeted state of the signal. The number of light bulbs, i.e. observable states can be derived from the type of the dynamic signal in the road network file.
        From 1.2
        Targeted state of the signal. The available states are listed in the TrafficSignal list of the RoadNetwork.
  • TrafficSinkAction (Changed)
    • Property 'trafficDefinition'. Stereotype <<deprecated>> applied.
  • TrafficSourceAction (Changed)
    • Property 'trafficDistribution' created.
    • Property 'trafficDefinition'. Lower cardinality changed.
      • New Value
        0
        From 1.2
        1
    • Property 'trafficDefinition'. Stereotype <<deprecated>> applied.
  • TrafficSwarmAction (Changed)
    • Property 'trafficDistribution' created.
    • Property 'trafficDefinition'. Lower cardinality changed.
      • New Value
        0
        From 1.2
        1
    • Property 'trafficDefinition'. Stereotype <<deprecated>> applied.
    • Property 'initialSpeedRange'. Stereotype <<XSDelement>>. Tagged value 'position' changed.
      • New Value
        4
        From 1.2
        3
  • Trailer (Created)
  • TrailerAction (Created)
  • TrailerCoupler (Created)
  • TrailerHitch (Created)
  • TrajectoryPosition (Changed, annotations only)
    • Property 'orientation'. Annotation changed.
      • New Value
        The Pitch and Roll angles are determined by the underlying road surface at the target position and therefore undefined by the OpenSCENARIO standard. The absolute reference context refers to the orientation with respect to the World coordinate system. Only the Heading angle at the target position can be arbitrarily specified on the (X,Y)-plane counting from the X-axis. The relative reference context refers to the orientation with respect to the (s,t)-coordinate system of the reference trajectory. Only the Heading angle at the target position on the (s,t)-plane can be arbitrarily specified. To calculate the Heading, the imaginary straight axis at the target position is built parallel to the tangent to the reference trajectory s-axis at the point with the target s-coordinate. The Heading is counted from this imaginary axis. If the reference trajectory s-axis shape contains sharp "kinks" (e.g., vertices on the polyline shape), the relative reference context with respect to such points cannot be interpreted within the OpenSCENARIO standard. Missing Orientation property is interpreted as the relative reference context with Heading=Pitch=Roll=0.
        From 1.2
        The Pitch and Roll angles are determined by the underlying road surface at the target position and therefore undefined by the OpenSCENARIO standard. The absolute reference context refers to the orientation with respect to the World coordinate system. Only the Heading angle at the target position can be arbitrarily specified on the (X,Y)-plane counting from the X-axis. The relative reference context refers to the orientation with respect to the (s,t)-coordinate system of the reference trajectory. Only the Heading angle at the target position on the (s,t)-plane can be arbitrarily specified. To calculate the Heading, the imaginary straight axis at the target position is built parallel to the tangent to the reference trajectory s-axis at the point with the target s-coordinate. The Heading is counted from this imaginary axis. If the reference trajectory s-axis shape contains sharp "kinks" (e.g., vertices on the polyline shape), the relative reference context with respect to such points cannot be interpreted within the OpenSCENARIO standard. Missing Orientation property is interpreted as the absolute reference context with Heading=Pitch=Roll=0.
  • Trigger (Changed, annotations only)
    • Annotation changed
      • New Value
        A trigger is defined as an association of condition groups. A trigger evaluates to true if at least one of the associated condition groups evaluates to true, otherwise it evaluates to false (OR operation).
        From 1.2
        A trigger is then defined as an association of condition groups. A trigger evaluates to true if at least one of the associated condition groups evaluates to true, otherwise it evaluates to false (OR operation).
    • Property 'conditionGroups'. Annotation changed.
      • New Value
        List of condition groups as a container of conditions. Omitting this attribute is deprecated.
        From 1.2
        List of condition groups as a container of conditions.
  • VariableAction (Changed)
    • Property 'setAction'. Lower cardinality changed.
      • New Value
        1
        From 1.2
        0
    • Property 'modifyAction'. Lower cardinality changed.
      • New Value
        1
        From 1.2
        0
  • VariableModifyRule (Changed)
    • Property 'addValue'. Lower cardinality changed.
      • New Value
        1
        From 1.2
        0
    • Property 'multiplyByValue'. Lower cardinality changed.
      • New Value
        1
        From 1.2
        0
  • Vehicle (Changed)
    • Property 'trailerHitch' created.
    • Property 'trailerCoupler' created.
    • Property 'trailer' created.
    • Property 'properties'. Lower cardinality changed.
      • New Value
        0
        From 1.2
        1
    • Property 'properties'. Annotation changed.
      • New Value
        Properties of the vehicle.
        From 1.2
        Additional properties as name value pairs.

Changed Enumerations
  • AngleType (Created)
  • CoordinateSystem (Changed)
    • Enumeration literal 'world' created.
    • Enumeration literal 'trajectory' changed. Annotation changed.
      • New Value
        Trajectory-based s,t coordinate system (s-axis is the trajectory-arc, which the entity follows).
        From 1.2
        Trajectory-based s,t coordinate system (s-axis is the trajectory-arc, which the entity follows).

Changed Interfaces
  • Entity (Changed, annotations only)
    • Annotation changed
      • New Value
        Instances of the types ScenarioObject, ScenarioObjectTemplate, EntitySelection and SpawnedObject are considered to be instances of type Entity. Or less formal: scenario objects and entity selections are both entities. An entity is either a scenario object or an entity selection.
        From 1.2
        Instances of the types ScenarioObject, EntitySelection and SpawnedObject are considered to be instances of type Entity. Or less formal: scenario objects and entity selections are both entities. An entity is either a scenario object or an entity selection.