Versions Compared

Old Version 37

changes.mady.by.user Stephen Lawrence

Saved on

compared with

New Version 38

changes.mady.by.user Stephen Lawrence

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.
Comment: minutes for 2/3/2022

...

  • Regular project recap
  • Continue the extra meeting discussions. Work on the "deep dive" topic list.k
    • Fill out the timing doodle if you have not already.
    • Add to the deep dive page.
  • AMM topic planning
  • Tech discussion with remaining time.


Related projects walkthrough walk-through (every week):

Steve (Renesas)
ProjectPerson reportingUpdates
  • Kuksa.VAL
Sebastian (Bosch)  Upgraded GRPC dependency to enable build on current Raspberry OS (and other platforms using similarly new GCC) https://github.com/eclipse/kuksa.val/issues/250
  • W3C VISS specification (v2)


Ulf 
Ted as backup (both Geotab)

No update this week (Ulf and Ted absent)
  • WAII VISS server implementation in Go
Ulf 

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

  • VSSo
Daniel W  
Ted  
  • VSC & Tools
Gunnar
  • CCS-components
Ulf  
  • AOS
Artem (EPAM)
  • Android Automotive VSS→ Vehicle Properties
    Code Generator
  • Covesa GraphQL components
Alexander Domin (BMW)(proposed.  worth tracking in CVII call?)(Thomas S) 

Ulf has pushed the Redis statestorage support mentioned last week, you can find it here:
https://github.com/COVESA/ccs-components/tree/master/statestorage

Publication for its use in WAII on the VISSv2 server github pending.

Steve reports that Renesas have integrated WAII onto the R-Car S4 SoC using the AGL Linux distro, with a data feeder for a simulator writing VSS data to the statestorage DB. Planning to demo this PoC at the AMM.

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

- spec: Doc/wording  clarification, that sensors, actuators and attributes are all considered „signals“ https://github.com/COVESA/vehicle_signal_specification/pull/408 
 - spec: Slight refactoring of GPS coordinates (separate vertical/horizontal accuracy) https://github.com/COVESA/vehicle_signal_specification/pull/417
 - spec: Max Line length recommendation https://github.com/COVESA/vehicle_signal_specification/pull/409 
 - tools: vss2ttl (aka ontology) converter merged do official vss-tools repo https://github.com/COVESA/vss-tools/pull/141
 - tools. Unify codebase of 2json, 2csv and 2yaml converters https://github.com/COVESA/vss-tools/pull/146 
 - tools: Fixed warning on badly escaped regexp strings https://github.com/COVESA/vss-tools/pull/147

- FAQ being collected. Github wiki will be used to collect inputs. Not up yet, but now draft on Covesa wiki here: VSS FAQ - Draft Questions and Answers

  • VSSo
Daniel W  
Ted  		Ted update to ML:

We have decided to cut back this workshop to one day for three hours, specifically 14 March from 7-10PDT / 10-13EDT / 16-19CET.

Those who want to propose items for the agenda may do so in Github although with more limited time we have less flexibility.

https://github.com/w3c/vsso/issues/26

  • VSC & Tools
Gunnar

AMM demo around Bosch washer ECU service.

Next task: architectural diagram

  • CCS-components
Ulf  See statestorage above
  • AOS
Artem (EPAM)
No update this week.
  • Android Automotive VSS→ Vehicle Properties
    Code Generator

Work continuing on Android 12 emulation environment
  • Covesa GraphQL components
Alexander Domin (BMW)No update this week
(proposed.  worth tracking in CVII call?)(Thomas S) 

Kanto devs in Bosch wish to present VSS aspects of Kanto:

  • 20 min overview + 10 min Q&A
  • See minutes
Steve (Renesas)Time limited this week. Work continues on data model conversion.


Apologies:

  • Ulf

Minutes:

  • Kanto
    • Thomas reports that project leads in Bosch working on Eclipse Kanto would like to present project
    • Source now available on Eclipse github
    • When?
      • Discussion about how to do 30+min session as this meeting has limited time
      • One approach is to do it as a "deep dive". Paul concerned about having people new to CVII having to sit through rest of the meeting.
      • AI: Thomas will get devs to add it as a topic to deep dive page and get feedback on when.
      • 5pm CET Monday is most liked time slot in Paul's deep dive doodle. Paul realises now that clashes with HV bi-weekly.
      • AI: Paul will consider timings.
    • What, why?
      • Assumption is that presentation is focused on CVII Tech Stack goals. Understanding architecture components and non-differentiating areas of collaboration.
      • From initial presentation discussion we can determine collab areas.
        • Some points that came up in first discussion:
          • Service definition
          • Container orchestration configuration
  • Extra meeting / deep dive
    • Doodle results show preference for "old CCS time" of Monday 5pm CET.
    • Please update the "deep dive" topics page with your thoughts and ideas. This page will be used as driving force for organisation of coming meetings.
  • AMM planning
    • Little time left to discuss. Please think about topic list.


2022-02-23

agenda:

...