Page History

...

• 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:

• VISS v2 server Planning / Work Breakdown page

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.

• Volunteers needed – see Planning / Work Breakdown page

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.

...

Input	Output
	VSSo	JSON (VSS definition in alternative format)	Protobuf (VSS/message definition in alternative format)	gRPC	GraphQL (Schema, Apollo format)	ARA:COM (XML)	SOME/IP (code generation, vSomeIP stack)	CommonAPI (enables backends vSOMEIP and others)	DDS (code generation)	Android Vehicle-Properties (mapping via code generation)	Franca IDL (standard)
VSS → x	vspec2vsso	vspec2json	vspec2protobuf	Ongoing support in KUKSA.VAL	1)  vspec2graphql 2) BMW alternative implementation pending.	WIP TietoEvery Ongoing discussions. VSS formatted data to/from AUTOSAR systems?	1) Via Common API capicxx-someip → see next cell 2) To vSOMEIP stack directly. e.g. to vSomeIP API	BMW considering releasing tools mapping VSS-to-FrancaIDL (which is consumed by CommonAPI)	Evaluate interest	Making progress, first draft code available (C++ code for VHAL)	Proposal, needs update.  vspec2franca
VSC → x	N/A	N/A	N/A:  gRPC is the corresponding protocol.	Likely candidate	Can be a candidate for the "W3C RPC protocol" to carry VSC services.	1) Std Franca ↔ARA:COM via FARACON (needs maintenance) 2) Possibly new implementation for VSC language?	TODO, obvious mapping.	Via Std Franca IDL →  Common API tools. Those tools take standard Franca as input	Evaluate interest	N/A	Definitely planned TODO. because "VSC language" will be very Franca compatible, (or will be Franca itself).  Therefore, expect interop with Std Franca IDL.

Data Serialization

Technology name:	Protobuf	AVRO	JSON (canonical format)
VSS → x	Very likely	Work started (see serialization branch in vss-tools)	This should be defined as similar to VISS as possible, but a separate specification would be useful.
VSC → x	N/A	N/A	N/A

Communication protocols / bindings

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:	Data	Data	Data (events)	Data	Services / RPC
	Full GoLang  implementation Other implementations? >> A request for C++ implementation came up (due to compiler support in some embedded system). =>  See priority list above.	TODO initial thoughts defined and/or possible to reuse from IoTEA? See working page	TODO Evaluate interest	TODO Evaluate interest	Pending analysis of VSC/interface language

...

Frameworks and Databases and Processing

Completion of technology definition / implementation
Project Name	Time-series database implementation (e.g. INFLUX / similar)	IoT-event-analytics / VehicleEdge	KUKSA.VAL (part of IoTea)	Spark	AOS	CCS Reference Architecture and PoC	Other?
Scope:			Data	Data	Data (events)	Data	Services / RPC
	TODO - define/implement how to insert VSS data into database.			Spark is an analytics engine, but implementing the data ingestion part and showing analytics on data that came from VSS format.	Analysis starting	In large parts done, but details remaining and constantly evolving

...