Nested parameter declarations or catalog references inside catalogs

Dear ASAM,

Every possible element of Catalog can contain a 'parameterDeclarations' element at the top level (e.g., Vehicle can contain 'parameterDeclarations'). When importing a catalog element in a scenario file using a CatalogReference, these parameters can be overwritten using the 'parameterAssignments' element. However, some catalogs can contain nested ParameterDeclarations as well. For example, Catalog → Maneuver → Event → Action → PrivateAction → RoutingAction → FollowTrajectoryAction → Trajectory can contain a 'parameterDeclarations' element. The standard does not specify whether the ParameterAssignment should only assign to the top level parameter, or if it should overwrite any parameter at any level. For example, if a ParameterAssignment occurs at the top level of a Catalog element, then a nested level ParameterAssignment temporarily overwrites this value, and a CatalogReference uses a ParameterAssignment to overwrite the parameter, then it is unclear at what level this should occur. For ease of implementation, Prescan has opted to only allow ParameterAssignment at the top level of a Catalog element.

Similarly, catalogs can refer to other catalogs. For example, Catalog → Trajectory → Shape → Polyline → Vertex → Position → TrajectoryPosition → TrajectoryRef → CatalogReference. Since catalog files cannot contain a CatalogLocations element, and to prevent recursion of catalogs referencing each other, Prescan does not allow CatalogReferences inside a Catalog element. However, the standard does not technically specify this.

Kind regards, Harmen Wierenga Software Developer Prescan, Siemens DISW