1. GENIVI – W3C Collaboration October 10, 2017 | AMM Seoul
Gunnar Andersson
Development Lead GENIVI Alliance
GENIVI is a registered trademark of the GENIVI Alliance in the USA and other countries. Copyright © GENIVI Alliance 2017.

2. Strategic Partnerships: W3C
(World Wide Web Consortium) 2
W3C is discussing new future specifications and maybe yet another version of Vehicle Information Service
– will it be continued on GENIVI standard or based on Volkswagen protocols, or a combination?
GENIVI is proposing our existing Navigation (LBS) API to lay foundation for the Web Navigation (LBS) API. + other GENIVI APIs
2 | October 10, | Copyright © GENIVI Alliance 2017

3. Strategic Partnerships: W3C (World Wide Web Consortium)1
GENIVI has had a unique partnership and influence in W3C, through mutual membership
First W3C report on Vehicle Web API was influenced a lot from the GENIVI Web API from the Korean Expert Group.
The second and current draft spec. of Vehicle Information Service Specification, VISS is based on GENIVI’s Vehicle Signal Specification, VSS
3 | October 10, | Copyright © GENIVI Alliance 2017

4. W3C – Volkswagen Proposal2
VW propose the “RSI” specification for dealing with various automotive related Web APIs
Focus is on REST (RESTful) interface approach
But also includes a proprietary PubSub protocol over WebSocket
REST is REST... understood by all web developers
The WS protocol is however unique for VW, and if adopted into standard, it would be unique for automotive.
4 | October 10, | Copyright © GENIVI Alliance 2017

5. 2. GENIVI has unique experience and breadth in automotive input.
Why should GENIVI Alliance work with W3C? 3
1. W3C struggles with resources/contribution like everyone, but their specifications are widely adopted when finished. Likely also in automotive.
2. GENIVI has unique experience and breadth in automotive input.
3. Avoid disconnect between IVI and other Automotive systems and the “Web interface”
5 | October 10, | Copyright © GENIVI Alliance 2017

6. GENIVI:s unique(?) offer
Why should we support this work through GENIVI? 3
GENIVI:s unique(?) offer
to the automotive industry: Define interfaces once!
6 | October 10, | Copyright © GENIVI Alliance 2017

7. and Connected services!
Define interfaces once! 3
Write all IPC and Network interfaces in an Independent Interface Description Language
Then generate bindings to technologies from the IDL
...to all our technology domains:
Native
Web-app
Car-Network
and Connected services!
7 | October 10, | Copyright © GENIVI Alliance 2017

8. Don’t let different areas (e.g. Native systems vs. Web)
Independent IDL Approach
Functionality driven by APIs, need to be independent and movable between ECUs, and between technologies.
Don’t let different areas (e.g. Native systems vs. Web)
compete and be incompatible causing lots of
unnecessary translation software.
Do the work once!
8 | October 10, | Copyright © GENIVI Alliance 2017

9. With W3C (and Volkswagen)we are discussing this:
Counter-proposal
With W3C (and Volkswagen)we are discussing this:
1. Ensure separation of data model from protocol.
(We agree on that…)
2. Don’t define an automotive-unique protocol,
when others exist.
9 | October 10, | Copyright © GENIVI Alliance 2017

10. We propose: Web Application Messaging Protocol
Counter-proposal
We propose: Web Application Messaging Protocol
- Already defines the JSON data format
- Open standard that already existed
- Existing subprotocol for WebSockets
- Several implementations
- Proposed to IETF as a standard
- Includes Pub/Sub and almost every other feature you can imagine
- Is a general proposal – i.e. potential for adoption outside automotive
- Efficient native adoption with MsgPack encoding
10 | October 10, | Copyright © GENIVI Alliance 2017

11. FRANCA IDL / WAMP proposal3
11 | October 10, | Copyright © GENIVI Alliance 2017

12. FRANCA IDL / WAMP proposal3
The “Franca to Web” tools are now being developed.
REST is yet another (automatic) binding. A good one, but not more complicated than any other.
This project enables taking any interface in Franca IDL and translating it through code generation to a C++ framework
for implementing the service, and the necessary client code (Javascript) to use the data in a Web Application.
In addition, the proposed messaging standard, WAMP, could be applied also in Native use cases, using an efficient binary. Encoding. Best of two worlds?
12 | October 10, | Copyright © GENIVI Alliance 2017

13. Franca development
- Adoption within companies/projects not bad… - Translations, possible when needed, let’s talk!
- Proprietary/internal tools being developed... WHY!?
- Eclipse tooling for Franca still very powerful
Deployment model editor with real-time syntax check
based on (your own) real-time specification!
(Not everyone has tried it?)
- If you don’t want the Java that comes with it → PyFranca – hack on tools written in modern python!
- Get engaged in this & let’s make Franca awesome!
13 | October 10, | Copyright © GENIVI Alliance 2017

14. Future - Discussion, research & evaluation ongoing
- GENIVI will show the outcome of our Franca-to-Web project
- GENIVI can adapt to W3C standards
and/or continue to offer Franca→WAMP tooling
- We agree on separating Data definition and transport
GENIVI will use Franca IDL (and VSS) for data
definition.
- We could exchange some code to adopt VW Pub/Sub protocol in case it becomes standard
14 | October 10, | Copyright © GENIVI Alliance 2017

15. 1. GENIVI Alliance has experience, and influence
SUMMARY
1. GENIVI Alliance has experience, and influence
2. Mostly good collaboration, just a little bit of politics
3. We all want a good outcome
4. No dead ends. It’s possible to adapt and change, so that we reach common standards.
! Engage in trying, using and developing our
GENIVI / Franca technologies !
15 | October 10, | Copyright © GENIVI Alliance 2017