Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.
Comment: 20th July minutes
Quick links: [ CVII home page ] [ Tech Stack components ]

2022-07-20

Agenda:

  1. Project Status and info sharing
  2. AoB
    1. Board discussions


  • Kuksa.VAL
Sebastian (Bosch)  

No announcements. See source repository for code changes

  • W3C VISS specification (v2)


Ulf, Ted as backup (both Geotab)

Explainer started for VISS (work in progress).
BMW have given green light to publish their VISS implementation report.

  • WAII VISS server implementation in Go
Ulf 

No announcements. See source repository for code changes

Daniel Wilms (BMW)
(Erik J or Sebastian S as backup)

Big discussion about adding complex data types to VSS for the first time: https://github.com/COVESA/vehicle_signal_specification/issues/326. Needs more input. Please read and input.

  • VSSo
Daniel W  
Ted  

New chairs (Daniel A and Felix) in place. Daniel A will take over tooling. Plan to discuss with Ford data scientist. Github: https://github.com/w3c/vsso

  • VSC & Tools
VSC team membersVSC-Core: waiting on code-drop and result of MBition staffing their dev team.
Container deployment: Page created for discussion of non-differentiating parts of VSC deployment VSC Deployment - Containers
  • CCS-components
Ulf  No announcements. See source repository for code changes
  • AOS
Artem (EPAM)
No announcements. See source repository for code changes
  • Android Automotive VSS→ Vehicle Properties
    Code Generator

Next step is for Covesa to articulate actionable points to take to Google.
  • Covesa GraphQL components
Alexander Domin (BMW)No announcements
(Thomas S) No announcements. See source repository for code changes
Steve (Renesas)Updating to new Apache IoTDB v0.13 which adds more efficent APIs for large data input and MQTT broker.


Minutes:

  • Ulf: Should we discuss the EG changes discussed in the recent board meeting?
    • Paul summarises the current situation

2022-07-06

Agenda:

  1. Project Status and info sharing
  2. AoB
    1. Meeting next week


  • Kuksa.VAL
Sebastian (Bosch)  

On-going work to upgrade GRPC binding and adding GRPC into Python and Go SDKs (alongside VISS, not to replace).

On-going work to integrated Code drops from https://sdv.eclipse.org in kuksa.val (“databroker” https://github.com/eclipse/kuksa.val/tree/master/kuksa_databroker )

  • W3C VISS specification (v2)


Ulf, Ted as backup (both Geotab)

Ted plans to create "explainer" document for v2 that is required as part of the standardisation process over summer.

  • WAII VISS server implementation in Go
Ulf 

Master branch now points at single process (threaded) version of WAII. web-client maintainers rebasing on that.

Daniel Wilms (BMW)
(Erik J or Sebastian S as backup)

Remove obsolete files
https://github.com/COVESA/vehicle_signal_specification/pull/463
(unused/outdated documentation)

Binary tool bug fixes
https://github.com/COVESA/vss-tools/pull/175 

Discussed how JSON output might be adapted to OpenAPI json schema subset
https://github.com/COVESA/vehicle_signal_specification/issues/457

Discussion of complex data types (coming from AWS https://github.com/COVESA/vehicle_signal_specification/issues/326).
GeoTab engineer showed examples of serialisation to json that allowed simpler connection to OpenAPI.

  • VSSo
Daniel W  
Ted  

  • VSC & Tools
VSC team membersSee source repository for code changes. Epam/Renesas presented proposal for open definitions for container deployment - next discussion milestone is once VSC example developed enough to discuss controls.
  • CCS-components
Ulf  
  • AOS
Artem (EPAM)
No announcements. See source repository for code changes
  • Android Automotive VSS→ Vehicle Properties
    Code Generator

Next step is for Covesa to articulate actionable points to take to Google.
  • Covesa GraphQL components
Alexander Domin (BMW)
(Thomas S) 
Steve (Renesas)


Minutes:

  • Kuksa
    • Seb outlines background to the work in progress changes listed above
    • gRPC
      • Steve: You mentioned gRPC vs VISS. Where there use cases where you favoured one over the other that necessitated the new work on gRPC?
      • Seb: gRPC came about from feeders where gRPC more easily connected to lang like C++ then having to use websocket for VISS.
      • Steve: Ted reported last week that there were already multiple definitions for binary VSS data serialisation in protobuf. Is this adding another? Coordination needed?
      • Seb: Good point. Currently only single values are supported so there is no much (no data stream) to serialise.
    • kuksa dataserver:
      • gRPC get/set VSS data server. No WS
      • Currently parallel to kuksa VISS server.
      • Internal discussions ongoing in Bosch about respective uses for each and to what extent they may merge.
  • AoB
    • Steve will be travelling after the Covesa Board Meeting at the time of next weeks call. Do you want to have a call next week or skip?
    • Paul B will host the call.

...