Page History

...

Minutes are now stored in COVESA Wiki

Wednesday 2021-12-15

Move to COVESA wiki

• https://github.com/slawr/vss-otaku

• https://drive.google.com/file/d/1kVXB7bdTarzQdiwtZyNqCK-vHihJeW0w/view?usp=sharing

Wednesday 2021-12-08 - COVESA wiki

Wednesday 2021-09-29

Project	Person reporting	Updates
Kuksa.VAL	Sebastian (Bosch)	--
VISS server implementation in Go	Ulf	--
VSS & Tools	Daniel Wilms (BMW) Gunnar    (Sebastian as backup)
VSSo	Daniel W Ted	Formal publication plans continue. Transition to W3C working group. VSSo → DTDL translation (still) exists.
VSC & Tools	Gunnar
W3C VISS specification	Ted Ulf	Access control PRs moving forward, and some specification text changes. (more details see last week's minutes on COVESA Wiki)
CCS-components	Ulf	Updated picture (PR sent)
AOS	Artem	Publishing started.  Hopefully links to source within a week.

• DAPR - evaluation, discussion, plans for VSS integration
• Initial code drops from BMW.  Full signal-source (SOME/IP) to GraphQL data server, serving VSS data. 
  Note:  All parts of the end-to-end are not here yet, but these initial 3:
  • https://github.com/COVESA/vss2graphql_schema
  • https://github.com/COVESA/test_franca2vss_mapping_layer
  • https://github.com/COVESA/test-someip-service
• VSS serialization reusable C++ library? (not discussed today in particular - but note that serialization/messaging format remains a need for connecting to the frameworks such as DAPR and other transparent "transports" that do not define a format yet.)

...

• Several vacation/apologies this week from Bosch, BMW, ...
• Project updates above, for those that are available
• Catch up with Artem regarding AOS issues
  • See above
  • Also working on modularity - identifying components for reuse.
• VSC and tools
  • → synergy opportunities with gRPC support in KUKSA.VAL?
  • Let's discuss "decisions" taken during this development → how to find consistency with the VSC-related work (which intends to integrate gRPC and other technologies as needed).
• Awareness:  CVII-TS: Binary encoding for VSS-based data transfer
  • → synergy opportunities with gRPC impl. also here?
  • Artem: We have seen some problems with binary encodings, so JSON mostly for now, which is adequate for a lot of the needs at the moment.  We see potential need (for binary efficient encoding) however.
  • Sebastian:  For gRPC we replace some of the JSON protocol parts of course, but data encoding is often still using strings for simplicity at the moment.
  • Gunnar: OK, I conclude this is still important and interesting to together define one or two canonical binary encodings for VSS.
• Updates/discussion on other priority-list projects:  
  • VISS v2 server Planning / Work Breakdown page
  • Needs a proper "need"/request for resource allocation.  Discussion on if current development frameworks (using python, NodeJS and other) are acceptable in in-vehicle embedded space or if this need actually does  exist already.
• Android AAASIG update
  • Plan to start implementing VSS to AOSP translation - WBS using a combination of VSS-tools examples for reading VSS and VSC-tools examples for code generation using jinja2.  Bittium is  leading.

...

• Introductions (Artem's first meeting)
• Brief discussion on AOS (principles, not the technology).  Embedded parts are planned to be open-source.  Process ongoing (outlook - a few months).
• Artem to give AOS architecture/tech overview next week
• Artem mentioned Android HAL using a VISS-protocol external server was implemented and shown by EPAM a few years ago.  
  • Gunnar:  So this was before AASIG was started...  It is good input, although current work has considered GraphQL as the protocol for the internal VSS-data server.
  • => Artem to provide a link to the published code.
• New table-based tracking of wanted/expected/missing tech stack components was added to the CVII Tech Stack overview page   Feedback/changes welcome!
  • This could drive priority discussions also
• Sub-topics moved to separate pages for deeper analysis, e.g. protobuf (already existed), mqtt (new), etc.
• Eclipse: short discussion on the liaison with Eclipse, to be followed up with the Bosch team

...