Agenda

A recording of the workshop is available.

Starting time	Expected duration	CVII Track	Topic	Speaker/moderator	Comments	#
1600 CEST	5		Welcome and Agenda	Gunnar A (GENIVI) & W3C		0
	10	General	CVII Survey questions and results	Philippe Robin	Slides (PDF)	2
	55	Common Model/Catalog (for services/APIs)	Vehicle Service Catalog and the potential of an industry-common Service Interface Language VSC language, Franca IDL, OpenAPI, AsyncAPI → single language Work so far Discussion and feedback	Magnus Feuer  (Gunnar Andersson)	Slides (PDF)	3
1710	20-25	Alignment	ISO Extended Vehicle specification – status and future discussion	Florian Pinzel (DENSO)	Slides (PDF)	4
1735	10		B R E A K			5
1745	20-25	Tech Stack	The AUTOSAR connection – potential and plans for connecting data and service models (TBC) FARACON review? 10 min Q&A / discussion time	TietoEvery –	Slides (PDF)	6
~1810	20	Tech Stack	AOS – Cloud-and-vehicle framework as an example of CVII-related ongoing development	Artem Mygaiev, EPAM	Slides (PPTX)	7
~1825	20-25	Tech Stack	Building the CVII technology stack – Plans and discussion	Gunnar A	Slides (PDF)	8
~1850	10 m		SPARE TIME			9
SUM	3h					98
END 1900 CEST	3h total					99

Extra / Waiting list

Interesting questions (to new participants):

• Do you think the data representation in vehicle and in cloud should and can be the same?
• Value of container technologies?
  • Architectural questions (microservices, one service per container, or several, ...?)
  • Choice of programming language could be "hidden" in containers.

Areas of interest (brainstorm)

• Stephen Lawrence: I am interested in discussing areas lower in the in-vehicle stack that are current pain points in the industry that we can collaboratively improve. I am thinking of things like points Unknown User (alexander.domin) raised in Tech Stack call 19/6 about interfacing above and below VISS and the issues of integrating buses. Related would be issues around the nexus of cross-domain functionality. This might start purely as information sharing from which like minded groups are identified.
• Short summary of survey, especially where people are willing to contribute, etc.
  • (full PDF available but not presented all details)
• Backdrop for taking next step is proof of adoption of VSS&VSSo. 
  • BMW any news?  Microsoft connection?
• VSC / interface language next steps (status, options, dialog) 
  • Status = language proposal, open questions
  • APIs being defined "elsewhere" (digital key being defined via Android?, other necessary standard interfaces?)
  • Are you willing to put forward descriptions?
  • Survey results + input from this meeting
  • Drivers for industry standard interfaces → Rental companies?
• Alignment Track:  ISO ExVe current state and plans?  (Florian)
• Alignment Track:  OPIN and eSync progress.
• AOS ?
• Stephen Lawrence : Hard to summarise the possible scope here but I have been thinking about in-vehicle and wondering about integration into embedded build systems. Is there discussion to be had at this point about the usefulness, or not, of shared development of embedded distro recipes, e.g. Yocto, or perhaps the current focus on containers is sufficient?
• Stephen Lawrence : Certain functionality shown in the "OEM Cloud" section of the CCS "Big picture" could also optionally migrate to the "Vehicle Edge", or something close to it such as near-road V2X. Would it help to have a discussion about the possibilities and if that affects technology decisions? A similar point applies to cloud vs edge analysis.
• Stephen Lawrence : Possibility to define API "southbound" for adapters into VISS? Goal is to improve portability of adapters and reduce integration efforts.