10.1 Types

This version of ASAM OpenSCENARIO has a complete type system and ASAM OpenSCENARIO 1.2.0 types convert easily into this system.

Values of all types in ASAM OpenSCENARIO 1.2.0 in XML can be specified in two ways:

With a literal value
With the parameter reference ($param_name) , where the parameter should be of the proper type, but ASAM OpenSCENARIO 1.2.0 has no mechanism to enforce this. Parameter references are described in Section 10.2, "Parameters".

Table 291. Types comparison table
Type	ASAM OpenSCENARIO 1.2.0	ASAM OpenSCENARIO 2.0.0	Notes
Boolean (logical value)	`boolean` (literals `true`, `false`)	`bool`
Timestamp (including date and time)	`dateTime` (for example `2002-05-30T09:30:10`)	`date_time`
Floating-point	`double`	`float`	IEEE 64-bit floating-point
Signed integer	`int`	`int`	32-bit signed integer in ASAM OpenSCENARIO 1.2.0, 64-bit signed integer in ASAM OpenSCENARIO 2.0.0
Unsigned 32-bit integer	`unsignedInt`	`uint`	32-bit unsigned integer in ASAM OpenSCENARIO 1.2.0, 64-bit unsigned integer in ASAM OpenSCENARIO 2.0.0
Unsigned 16-bit integer	`unsignedShort`	`uint`	16-bit unsigned integer in ASAM OpenSCENARIO 1.2.0, 64-bit unsigned integer in ASAM OpenSCENARIO 2.0.0
Unicode string	`string`	`string`
Enums	Fixed enums only, defined by standard	`enum`	Extensible enumeration types, with optional integer values
Physical types			Most of the floating-point values in ASAM OpenSCENARIO 1.2.0 map to a physical type instance with the appropriate SI unit, for example, `length`, `speed`)