Page History

Quick links: [ CVII home page ] [ Tech Stack components ]

2022-

...

10-

...

12

Agenda:

1. Project Status and info sharingAoB
   summary
2. Autumn AMM meeting planning + longer term topic planning
3. ISO ExVe updateMeeting next week

Minutes:

• WAII VISS based Vehicle to Cloud arch
  • Ulf has pushed the code he had summarised previously that introduces clients to provide a connection between VISS in the vehicle and the cloud.
  • See branch https://github.com/w3c/automotive-viss2/tree/ecuAdaptation for the code. The readme for the vehicle shows the arch
    https://github.com/w3c/automotive-viss2/tree/ecuAdaptation/client/client-1.0/VEC
• Florian continued his standards update from last week:
  • ISO ExVe cont.
    • Florian looped feedback to the ExVe group. The coordinator and Philippe agree that ExVe should be aligned and not creating new data model. Recognition that the two groups move at different speeds.
    • In answer to question whether standard can reference upstream the answer is yes. It would need to specify whether it is informative (info) or normative (must). So ExVe could reference a specific VSS version rather than duplicate.
    • ExVe WG continues to discuss whether its scope is pure data or interfaces as well.
  • Service Orientated Vehicle Diagnostics (SOVD)
    • Florian gave a quick intro to SOVD. This was unfortunately time limited. The group agreed we should ask Florian to expand on the topic after the AMM
    •  Florian's presentation:

      View file
      name Infosharing_CVII_October 2022.pdf height 250

2022-10-05

Agenda:

1. Project summary
2. Autumn AMM meeting planning + longer term topic planning
3. ISO ExVe update

Minutes:

• Florian gave an update on ISO ExVe
  • Liason agreement concluded with Covesa
  • WG 6
    • REST (web) API for external access to car data
  • Discussion of  ExVe thoughts around data models and the challenges of firstly avoiding competing models and secondly the slow speed of ISO updates. If ISO adopts VSS as the model or aspects of it for example there is still a challenge around the version it uses and a probably faster moving VSS version upstream.
  • Discusssion of the use of VSS rule set outside of the VSS standard catalog, e.g. it would be useful for interoperatability, example would be development cost sharing and familarity, if non-VSS standard catalog data used the VSS rule set.

2022-09-28

Agenda:

1. Project summary
2. Autumn AMM meeting planning + longer term topic planning

Minutes:

• ISO ExVe
  • Florian kindly offered to give an update on the state of the data model discussion in ISO ExVe next week
• Discussion of 2022 Autumn AMM Detroit Planning (CVII Tech Stack)
  • VISS client
    
    • Ted reports that where to do VISS client presentation discussed in W3C call. Paul will be discussing with conference team.
    • Ted is owning liasion with Issac and team.

2022-09-21

Agenda:

1. Project summary
2. Autumn AMM meeting planning + longer term topic planning

Minutes:

• Short readout on Autosar discussions
• Steve outlined the current plan for the AMM / future planning workshop (2022 Autumn AMM Detroit Planning (CVII Tech Stack)
  • • Please add any topics you wish to discuss

2022-09-07

Agenda:

1. Project summary
2. Autumn AMM meeting planning + longer term topic planning
3. Rescheduling VISSv2 client deep dive

Minutes:

• AMM / future planning (2022 Autumn AMM Detroit Planning (CVII Tech Stack)
  • Next steps
    • Discuss data storage proposals with Adnan to get clearer picture of what and when. Can we clarifty before AMM or do we workshop it at AMM for example
    • Schedule needs some time (1hr at least?) to allow for the future planning discussion whilst we are together
    • Go back to Issac to discuss where to schedule VISSv2 client outreach. If there is an AMM session it will feed into the schedule
• VISSv2 client from UMA
  • Deep Dive possible but summer slowdown may result in low attendance. What is best?
  • Ted: AMM session if remote allowed? 30 mins?
  • Paul/Steve: possible
  • Client has a focus on security so there is a connection to the security

2022-08-31

Agenda:

1. Project summary
2. Autumn AMM meeting planning + longer term topic planning

Minutes:

• AMM / future planning
  • Planning page added 2022 Autumn AMM Detroit Planning (CVII Tech Stack) and populated from in meeting discussion. Feel free to add ideas
• Discussion of Android EG / VHAL

2022-08-24

Agenda:

1. Project summary
2. Autumn AMM meeting planning + longer term topic planning
3. Brief report on production system using Kafka and MQTT between vehicle and cloud

Minutes:

• Project Summary
  • Android VHAL
    • Chris Tingley from Conjure says they intend to work on VSS to VHAL translation in the autumn. Introduced Chris to Stefan Wysocki the Android EG lead so they can collaborate.
• AMM
  • Need to plan Data Architecture / Infrastructure sessions
    • Ideation on future EG: cloud, in-vehicle
    • Data Storage / sync
    • vehicle to cloud link
    • CCS
• Return of Experience
  • Steve summarised use of MQTT (transport) and Kafka (ingest) outlined in webinar he attended
    • Bringing hyper-connectivity to hypercars with MQTT and Kafka - Mobex

2022-08-17

Agenda:

1. Project Status and info sharing
2. AMM
3. Data Expert Group
4. AoB

Minutes:

• Project Status:
  • VSS v3 released
  • Kuksa.val
    - kuksa.val and kuksa.val.feeders repo completely Apache-2.0 now
    - Removed experimental HTTP interface https://github.com/eclipse/kuksa.val/pull/316
    - Updated all kuksa.databroker dependencies https://github.com/eclipse/kuksa.val/pull/321/files (due to cirtical security bug in nix dependency)
      -  Update architecure pictures (mention GRPC in addition to VISS and add VSS Logo): https://github.com/eclipse/kuksa.val/pull/324 
     - Fix some remaining GENIVI references to COVESA. Better late than never :) https://github.com/eclipse/kuksa.val/pull/327
  • VSS
    - Released Version 3.0 !!! https://github.com/COVESA/vehicle_signal_specification/releases/tag/v3.0 
    - Decided way forward wrt complex datatypes/structs  https://github.com/COVESA/vehicle_signal_specification/issues/326 
    - Updated docs and logo https://github.com/COVESA/vehicle_signal_specification/pull/470 
    - tools: Fixed regression in DDS and GraphQL exporters: fixed issue w.r.t. value attribute generation in DDS-IDL file,  Extend exporter tests
• AMM
  • Paul: call for session topics.
  • Steve: To help plan whether we can have workshops who plans to travel? Seb hopes too, Ted yes, Ulf not clear yet, Steve yes.
• Data Expert Group
  • Approved in board meeting.
  • Now move to implementation.
  • Call for chair and co-chairs/project leads

2022-08-03

Agenda:

1. Project Status and info sharing
2. AoB

Minutes:

• With only four present with the summer slowdown and other absences had a general state of the nation discussion including the EV meeting directly prior to this one.
• Ted reported from the W3C call that BMW continue to work towards publishing the source to their VISS server

2022-07-27

Agenda:

1. Project Status and info sharing
2. AoB
   
   1. Data EG

Minutes:

• Discussion of proposed Data Expert Group
• VSS
  • Discussion of complex data types in VSS
  • Nik: Is VSS v3 coming soon?
  • Seb: Should be soon after summer break

2022-07-20

Agenda:

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

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

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.
  Misc info sharing
  • Ted: there are 3 VSS protobuf serialisation versions - work ongoing to converge:

2022-06-29

Agenda:

1. Project Status
2. Continue Vehicle Edge To Cloud Edge (VE2CE) project proposal (Slides here) discussion from last week

...