SYNERGIES Interoperability with ASAM OSI

[jdsika]

Hi team,

I was directed to this library in the context of the SYNERGIES reserach project. We are discussing practical formats to re-use and further develop in the research project.
I would like to engage in a meeting to discuss my first impressions regarding this repository. My contact is Lennart Vater and I would want to ask who else might be interested in a technical discussion.
My questions would be regarding the re-use of this repository and compatibility with existing industry standards.
In addition I would like to understand the scope of this project. The repository states that in contains a "format" but there are a lot of features like, convertion (e.g. from OpenDRIVE to Omega), visualization, (de-)serialization, packaging in container and more I might not see at first glance.
As a python only libarary (c seems deprecated since last release) I want to ask for the vision regarding the use of the omega format in projects which are not python based?
I would also like to engage in a discussion that de-couples the specification of the format from the implementation of convinience functionality.
At BMW we are using and developing the ASAM OSI format since 2016. One of the important aspects is the definition of the interfaces, the semantics and datatypes using the protobuffer DDL and therefore enabling the support of the interface on all platforms and languages. My initial evaluation shows great overlap and omaga being a subset of OSI. I would like to discuss the integration of OSI in this library to decouple the functionality from the definition of the format. There are multiple ways to package OSI traces but my latest suggestion is the combination with MCAP. I would be happy to support with understanding OSI and discussing the benefits of using a widely supported format. I believe this might be an interesting work package for RWTH for the SYNERGIES project regarding the interoperability.

Best regards
Carlo

[MSSandroid]

Hi Carlo,
Thanks for the fruitfull discussion. We are looking into "integrating" with OSI and keep you posted. In regards to your other questions:

• Scope of the project: The main scope of this repository is to provide a library to interact with the omega-format.
• Where is the format definition?: The format definition is in textform in the doc/specification.md and doc/signal_list_reference.md file and "documented as code" in the omega-format library. You are right it would be nice to have something like proto for the format definition to more easily work with other programming languages, but we are not aware of alternatives for hdf5.
• What happend to the C code?: We removed it because our build instructions where not working anymore because of now offline repositories.