Versions Compared

Old Version 25

changes.mady.by.user Stephen Lawrence

Saved on

compared with

New Version 26

changes.mady.by.user Stephen Lawrence

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.
Comment: completed minutes for 9/2/22

...

ProjectPerson reportingUpdates
  • Kuksa.VAL
Sebastian (Bosch)  Skipped - no Bosch engineer this week
  • W3C VISS specification (v2)


Ulf 
Ted as backup 

Final stages towards v2 spec. Discussions about enhancements for access between ECUs.

Ted: Looking for industry feedback on VISS protocol. Whats' good, what's missing. Etc.

  • VISS server implementation in Go
Ulf No change

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

Adding FAQ documentation
Update vss-tools submodule
Updates to standard data catalog to follow new naming conventions, etc.  (some things still pending)
Weird fundamental bug/problem:  keywords like "on" "off" interpreted as booleans (true/false).  Studying formal YAML specification, as well as behavior of python libraries to sort this.

  • VSSo
Daniel W  
Ted  		Advancing onto formal standards draft
Planning to hold couple day workshop. See https://lists.w3.org/Archives/Public/public-automotive/2022Feb/0001.html
  • VSC & Tools
GunnarGood session preparing these ideas:
  1. Introducing VSC-interface reference in AOS definition of service containers.  (Still needs to be discussed with AOS leads)
  2. More examples of useful services in a standard catalog.  Bosch is proposing Wiper functions (concrete proposal not yet)
  3. Plan to reach out to interface-tooling/methodology team at Bosch (OpenAPI ↔ more generic interface language)
  • CCS-components
Ulf  No change
  • AOS
Artem 
No change
  • Android Automotive VSS→ Vehicle Properties
    Code Generator

Stefan Wysocki at TietoEvry taking over

  • Covesa GraphQL components
Alexander Domin (BMW)

GraphQL fixes. Android VHAL team can now check their issue.
Small patch to improve build process.

Eclipse Kanto
(proposed.  worth tracking in CVII call?)		(Thomas S) Skipped - no Bosch engineer this week

...

  • Sebastian S (Bosch)

Minutes:

  • Project coordination

  • Android VHAL

    • Ted: W3C talking to Google Cloud ppl. They want to learn more about VSS to AOSP VHAL properties converter. Who to loop in to explain to them?

    • Paul: Loop me in.

    • Gunnar: Stefan from TietoEvry leading the work.
  • VSC
    • Heads up on discussions in VSC call.
    • Followed by illustration from Gunnar on specifying protocol and access control for VSC APIs and mapping the latter to existing systems, e.g. in GraphQL and VISS.
  • Extra meeting
    • Continue discussion of whether to repurpose the CCS meeting into a wider CVII Tech Stack meeting dedicated to deep diving design discussions. Do we do want to do it? If so when?
    • Ulf, Steve would like to see it continue. Alex is interested but is time constrained.
    • Two CVII Tech Stack meetings:
      • Weds: CVII Tech Stack: project coordination
        • This call. Coordination update as already done, followed by general discussion with time remaining.
      • TBD: CVII Tech Stack: detailed design
        • New call. Scope is deep dive on tech stack topics not specific to the VSS, VSC specific calls. Engineering focus. Will be small # of topics, known in advance.
      • AI: Create Doodle for timing
    • Deep dive topic list:
      • Alex: Discussion of connecting VSS Data Store to GraphQL
  • Remaining 10 mins:

    • Southbound x2VSS conversion and code generators

      • Outline of two methods we currently have for conversion:
        • Android VHAL design pattern using JINJA template and yaml conversion description
        • vss-otaku is looking at a varient to the VHAL pattern that uses VSS vspec rule set to define the source data model. Outcomes will include pluses (vss-tools function set) and minuses (need to avoid polluting VSS standard catalog with source data types and units) of that approach.
      • We expect to need to expand the VSS Terminology set to include converters and generators. Please consider what they should be. A good set will ease coordination in and outside the group.
    • In-vehicle VSS Data Store


      • Steve outlined the direction of travel for VSS Data Store investigations in vss-otaku
      • Some universal themes to investigate collectively for Tech Stack such as connections between VSS Data Feeders, Data Stores and Data Servers.
      • Alex: I would really like to have a deep dive on the VSS Data Store and how it relates to what we are doing with GraphQL. To share our viewpoint and align.
      • Steve: Would love to. Your production/OEM perspective would be invaluable to guide later work connecting Data Stores to Data Servers.
      • Steve: This would also be a perfect topic for the proposed CVII Tech Stack Detailed Design meetings. Added it as a starting topic above.


...

2022-02-02

Related projects walkthrough (every week): SKIPPED

...