Page History

...

Converters and Code Generators

Note:  The purpose of the technology stack is to lead us (the automotive industry) towards a limited selected set of solid core technologies. 
A table like this might look like a anything-to-anything conversion, but it should be clear that the goal is not to create that – only to make sure there are solutions for technologies that are strongly desired, or unavoidable legacy.

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

)DDS
(code generation

)	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

vspec2graphql TODO TODOplan? existing tools to become open source?

1)  vspec2graphql 2) BMW alternative implementation pending.

WIP TietoEvery Ongoing ideas in AUTOSAR?

1) Via Common API capicxx-someip → see next cell 2) Directly (without CommonAPI) TODO?

BMW considering releasing vss-2-commonapi generation tools?

Evaluate interest

Ongoing Mapping/plan exists.

 proposal

Proposal, needs update

vspec2franca

.  vspec2franca
VSC → x	N/A	N/A	N/A:  gRPC is the corresponding protocol.	Evaluate interest	Useful 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?	Possibly	Via Std Franca IDL – Common API tools consume standard Franca already	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.

Communication protocols / bindings

Completion of technology definition / implementation
VISS (data)	MQTT (data)	Spark (data ingestion)	NiFi (data flow definition and transfer)	W3C-RPC* (services)
Full go-implementation - KUKSA implementation? - more implementations?	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

...

(Ideally these initiatives are after analysis combined into a single consistent architecture?)

Completion of technology definition / implementation
IoT-event-analytics / VehicleEdge	KUKSA.VAL (part of IoTea)	AOS	CCS Reference Architecture and PoC	Other?
		Analysis starting	In large parts done, but details remaining and constantly evolving

...

Historical / preparation information.

...