Inheritance of points from route_element semantically broken

Consider route_element (see https://publications.pages.asam.net/standards/ASAM_OpenSCENARIO/ASAM_OpenSCENARIO_DSL/v2.0.0/domain-model/road_abstractions.html#sec-roads-abstract-route_element) and its children crossing, lane, lane_section, odr_point, path, road, route_point, xyz_point as they are currently defined.

I would argue that the parent child relationship described her is not semantically correct in the sense of a proper taxonomy since most of these children also need to be able to exist alone. And furthermore, a route element requires the addition of additional data such as length of the route until this point. In other words a point can not be a subclass of a route element, instead a point is used by a route element together with other information but the same point can also be used for something completely different like a vertex of a bounding box.

To solve this problem we could instead define something like

xyz_point_route_element which is a child of route_element and a child of point as well and xyz_point is a child of point. Or alternatively we can work with some form of composition instead of inheritance where a route_element uses/contains a point and 'xyz_point' is a child of 'point'.