...

Notes from Ulf

Hi,

As I am missing the Interface Pillar Alignment meeting next week I would like to provide some comments that I would have liked to be brought up at the meeting.

So if you see an opportunity to bring it up I would appreciate it. If you do not find a suitable opportunity I will not hold you to it .

It is Ok for me if you think it could be added to some page related to the meeting.

BR

Ulf

HIM:

• I think that if VSS is discussed, then HIM should be part of that discussion. HIM is a superset of VSS. It is backwards compatible with VSS, as shown in the Common Rule Set and the Resource Data Rule Set in the HIM documentation https://covesa.github.io/hierarchical_information_model/.
• HIM provides two significant additions in comparison with VSS, a structured model for handling of multiple trees, AND the ability to represent not only “signal data” but also “service data”.
• The “service data part” provides support for definition of a “common catalogue for services”. An example is shown on this link https://github.com/COVESA/hierarchical_information_model/blob/master/examples/HIM_Service.v1.0.0.him.
• Ford is interested in participating in populating a “common catalogue for services” using the HIM model.

VISSv2 evolution:

• The existing VISSv2 uses VSS as the data model. It lends itself very well to being evolved to use HIM instead. This combination would provide a comprehensive interface standard for both signals and services.
• The VISSv2 reference implementation (https://github.com/w3c/automotive-viss2/tree/master) now has support for using gRPC for the transport of protobuf encoded VISSv2 messages. This could be added to the VISSv2 evolution specification, which then very well could become the “common IDL format” (= the protobuf part).
• Ford is interested in participating in driving the work on evolving VISSv2 to use HIM instead of VSS. Which can be hosted by either W3C or COVESA.
• Ford is also interested in participating in a reference implementation of the evolved VISSv2 spec. Which can be hosted by either W3C or COVESA.

September Session

Candidate date and place is Sept 26 Stuttgart-area (before ETAS connection, Bosch/ETAS can most likely arrange a room)

...