5 Backward compatibility

ASAM OpenSCENARIO v1.3.0 contains several corrections of errors in the XML schema file (.xsd) and is therefore not fully backwards compatible. All these corrections refer to errors where it was allowed to define semantically invalid scenarios (for example, specifying no element instead of exactly one element in an XOR). Therefore, a migration script (.xslt) is provided for converting scenario files from v1.2.0 to v1.3.0. If the migration script issues a warning, then the v1.2.0 scenario was already semantically invalid and would be syntactically invalid in v1.3.0. A scenario for which the migration script issues warnings has to be checked and fixed manually.

ASAM OpenSCENARIO v1.3.0 also contains several corrections of calculation specifications for positions and orientations in the Position sub-classes, which makes this version not fully backward compatible. These changes do not affect the XML schema file, but alter the interpretation and implementation of the standard in simulators. Because the previous calculation specifications would lead to incorrect or unexpected positions / orientations of entities in specific use cases, it is not necessary to implement different calculations for scenarios of version >= v1.3.0 and <= v1.2.0 respectively.

ASAM OpenSCENARIO v1.2.0 is fully backward compatible to v1.1.1 as well as v1.0.0. That means, there is no need for migration.

For all versions, a strict XML schema file without the deprecated elements is provided, so that deprecated elements can be detected and removed or replaced manually.