Versions Compared

Old Version 44

changes.mady.by.user Gunnar Andersson

Saved on

compared with

New Version 45

changes.mady.by.user Gunnar Andersson

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.
Comment: minor fixes

...

ProjectPerson reportingUpdates

  • ioTEA/Vehicle Edge

Thomas Spreckley (error)


  • Kuksa.VAL
Sebastian (tick)

gRPC, Visual Studio dev containers for easier development

  • VISS server implementation in Go
Ulf (tick)No updates.
  • VSS & Tools

Daniel Wilms (error)
Gunnar   (tick)
(Sebastian as backup)

  • Dropped travis file because GitHub actions cover all now

  • Seat signals were sensors, now actuators

  • VSS meeting group continues discussion of extensible datatypes and units (each separately).  At the moment it's basically a fixed list.
    - Which datatypes and units are predefined as part of the standard VSS model?
    - Are these also used in the current standard catalog?  Are there "standard" types that are not used at all?
    - Shall the model allow extension with new datatypes?  ... and/or with new units?
    - If it shall, what is the method of extension?  Shall the datatypes and units be defined in the program source code or read in from a configuration file.

    Progress is being made on these questions but all (many) stakeholders need to have time to weigh in.
  • Early hints on upcoming issues:  Supporting struct data types (or not, as now), and possibly revisiting the definition of the enum type.
  • VSSo
Daniel W (error)
Ted (question)
  • VSC & Tools
Gunnar  (tick)
  • vsc-tools: Generator function now uses type introspection on nodes, so there is no need to specify the node type in the template any longer. (Issue #16 )
  • vsc-tools: Unit test framework in place (pytest) with a first test example (#13)
  • VSC/RPC meeting this week discussed way forward, and outreach to companies for one-on-one input regarding preferences
  • gRPC, OpenAPI, and other standards are important to get into the mix, as well as Franca usage or migration path as described before. A new Franca input parser may need to be programmed from scratch, but this should be straight forward.
  • W3C VISS specification

Ted (question)

Ulf


  • CCS-client repository
Ulf (tick)
  • AOS
Artem (tick)

Trying to find common ground around authorization etc.  Need a proposal for community to react.

Service representation spec. also of interest (← VSC (and VSS) related discussion).

Minutes/Agenda

  • 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

...