Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.
Comment: Update links

...

  • C++ seems to be requested.   There is also some mild interest in Rust in the industry, but so far it seems not strong enough to supplant C/C++ as the main choice.
  • AOS and KUKSA have both done VISS implementations in C++, based on VISS v1, which could be starting points.

   Details:

2. Demonstration of VSC-based development

...

      A)  For individual message updates through protocols (VISS? MQTT, etc.)
      B)  For in-memory storage of multiple data points and possibly subsequent batch (image) transfer.


Project Backlog – development project candidates

  • VSS to Android Properties implementation (Code Generator).   It should likely introduce jinja2 template based generation, similar to the vsc-tools.  → Work breakdown page.
  • VSS over MQTT (Starting point exists in IoTea impl. Develop full implementation, include access-control/security, and as a reusable component separated out from IoTea framework) Work breakdown page
  • VSS to/from Autosar ARA:COM XML format
  • VSC to/from Autosar ARA:COM XML format
  • ..Proper VSS to Franca IDL converter.  Status and remaining steps are in vss-tools/PR#6.

for further, potential examples, refer to the table based overview below.

...


Procotol / technology name:VISS v2
protocol definition
MQTT
(data)

Kafka
(event streaming platform, make it VSS-aware and show impl.)

NiFi
(dataflow platform, make it VSS-aware and show impl)


W3C-RPC*
(services)
Scope:DataDataData (events)DataServices / RPC

(tick)  Full GoLang  implementation

Other implementations? >>

(warning) A request for C++ implementation came up (due to compiler support in some embedded system). =>  See priority list above.

(green star) TODO
initial thoughts defined
and/or possible to reuse from IoTEA?

See working page

 TODO
(star) Evaluate interest
TODO
(star)Evaluate interest
Pending analysis of VSC/interface language

...