"Plan B" on VSC tooling development - discuss options
Bosch I-O-Tea and Vehicle Edge evaluation
Notes
Integrations to AUTOSAR
Tieto platform running, ready to use for investigations
Gunnar: For "Any"2Autosar tooling, first step is usually a definition of the mapping (spread-sheet showing language features that map to each other, where is it simple, where are challenges, etc.)
VSS2ara would be basically solving the "autosar side" of the system, similar to how Franca → AUTOSAR XML converter was used with AUTOSAR.
Alternative is to first focus on the "non-AUTOSAR" side of systems, e.g. generate a SOME/IP binding directly, or DDS, or other. (VSS/VSC to SOME/IP binding directly).
ASAM service oriented diagnostics seems interesting.
"Plan B"
The VSC-related tooling is taking even longer time to go through company legal reviews and final approvals for releasing it with an open source license, although there is a clear desire to get it done.
A discussion started on how to develop a first set of tools in parallel with waiting for the other.
Wednesday 2021-04-14
Notes
Tieto: AUTOSAR analysis ongoing. Need tooling soon.
VSC tooling seems held up by something. End of this week consider if we should launch plan B. Talk to Magnus about it.
VSC:
Piotr: Has ASN.1 been considered as a definition language? (it could be an alternative to protobuf?)
... the compilers are often able to generate a compact binary format
... likely less availability of open-source tools. There should be some however.
Gunnar: For VSS I think it's "overkill" since VSS has very simple datatypes but for VSC and arbitrarily complex data definitions, maybe
Gunnar: FYI: OpenAPI and AsyncAPI have however come up as potential reuse or inspiration for VSC definition. Franca IDL is still a strong basis however. OpenAPI is only REST-focused and AsyncAPI seems to describe primarily a pub/sub direction.
VSS
Stephen: I was recently reading about GraphQL Federation that allows seperation of concerns and for domain teams to create parts of the data graph that are then federated into a whole. The seperation of concerns resonated with in-vehicle engineering where you have for example services with very different safety and security requirements. Could this help us?