Integration of martime data

[fulup-bzh]

In the process of moving to VSS, I need to integrate both BMS data and maritime data on top of VSS. While I did not find any signigicant open-source project for BMS data, for navigation there is an active project that is somehow similar to VSS http://signalk.org/specification/1.2.0/doc/signalk.pdf

My goal is to merge both VSS&Signal-K specifications within the same dataset. This in order to provide a single dataset/API for BMS/J1939/Maritime datas.

Any idea would be more than welcome.

[erikbosch]

Meeting notes:

• Fulup presented the topic
• Fulup: Checking if we can leverage VSS: needs relatively quick answers:
• Achim: Infrastructure tree proposal as part of EV charging at https://github.com/COVESA/ev_charging
• Erik: COVESA discussions to introduce a a new metamodel file (HIM, proposed by Ulf from Ford) for datatree registry
• Daniel: We need to differentiate schema and actual model
• Fulup: Boats are different, often multiple engines, desalinators. Often controlled by J1939. Commercial boats may have 10 engines. We are checking leveraging existing tools, to reduce risk
• Sebastian: Some things seems to be able to express in VSS syntax.
• Fulup: Looking at way to express signals with ambiguities
• Erik: KUKSA has VSS<->DBC/J1939 mapping, see https://github.com/eclipse/kuksa.val.feeders/blob/main/dbc2val/mapping/mapping.md
• Erik: No action in VSS-project as of today. We keep this issue open as long as the discussion is active.

[SebastianSchildt]

Just browsing the PDF, a thought crossed my mind: Do the "datapoints" described in Appendix A/B also exists in "machine readable" format somewhere? That would be maybe a starting point to "convert" them to VSS (as entry point into a joint stack). If it doesn't exist, if you were to "manually" "converting" them to vspec/writing them in vspec form on the other hand might be interesting for the signalk community because finally they WOULD have a machine readable version of their Datapoints

[fulup-bzh]

You may find the Signal-k spec on github https://github.com/SignalK/specification/tree/master/schemas the main entry point is vessel.json then it point to sub-group ex for example groups/navigation.json Even if they use heavyly rely on json schema, signal tree model is not than different from VSS.

For low level signal I use canboat project https://github.com/canboat/canboat/blob/master/analyzer/pgns.xml (json is equivalent with less signal description)

[erikbosch]

Meeting notes:

• No action point, has been discussed, closing it

[erikbosch]

Please check https://wiki.covesa.global/display/WIK4/Defining+the+COVESA+data+modeling+strategy+and+its+associated+artifacts as it tries cover also other domains. Add comments/question if wiki