Error/Warning/Exception handling for partial OSI data

[jdsika]

We have to differentiate between different constellations when handling OSI data:

1. The Lichtblick plugin schema defines different types of primitives: Lines, Cubes, etc (see docs)

   • The application is mapping the osi data to these primitives and we should only consider throwing an error if the necessary information to successfully create such a primitive is missing
   • we already made a note of this in Minimum requirements to display OSI messages #14
   • The primitives define the mandatory fields for the asam osi converter

2. The osi standard will rely on the asam qc framework to enforce the rules assigned to individual osi messages

   • the visualizer should not be responsible for checking osi rules
   • the visualizer should treat any non mandatory field from its own perspective as optional
   • if we consider certain information as necessary from the user perspective like velocity in feat: add additional metadata for moving objects 2 #123 then we should notify the user by e.g. displaying the word "missing" or similar in the metadata field instead of the value.

3. Is a message actually an osi message?

   • we also raised the question in Sanity check for message integrity #13 how we can make sure that an osi topic does actually contain osi?
   • we need to define the type of error and the proper location at which point we decide that a message is not real osi and not displayable

In general the asam osi converter should be a tool to debug osi messages visually. Therefore it should be as robust as possible to faulty and incomplete osi messages but clearly hint to the user if something is not according to expectations