We use cookies on this site to enhance your user experience. By using this site, you are giving your consent for us to set cookies.


You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 10 Next »

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 flexibility to have a discussion about the possibilities? A similar point applies to cloud vs edge analysis.

Agenda


Starting timeExpected durationCVII TrackTopicSpeaker/moderatorComments#
1600 CEST5
Welcome and AgendaGunnar A (GENIVI)
& W3C (tick)

0

10GeneralSurvey questions and results...someone other than Gunnar? (smile)
2

60Common Model/Catalog
(for services/APIs)

VSC and the industry-common
Service Interface Language

VSC language, Franca IDL, OpenAPI, AsyncAPI → single language

  • Work so far
  • Discussion and feedback

Magnus Feuer (warning)
Gunnar Andersson

3

20
ISO Extended Vehicle specification – status and possible futureFlorian Pinzel (DENSO) (warning)
4

10
B R E A K

5

20Tech StackAUTOSAR – Discuss planning for connecting data and service models to common data modelTietoEvery – Piotr?  (warning)
6

20Tech StackAOS – Overview of cloud-and-vehicle frameworkArtem Mygaiev ((warning)TBC )
7

20Tech StackBuilding the CVII technology stack
(overview and discussion)
Gunnar A (tick)
8

15 m
SPARE, TO BE FILLED

9







SUM3h



98
END 1900 CEST3h total



99


Extra / Waiting list

Starting timeExpected durationCVII TrackTopicSpeaker/moderatorComments


Miscellaneous

Quick updates from projects:

  • VSSo, DTDL
  • CCS
  • VSS Tools


VSSo, DTDL – Daniel Wilms? (tick)


  • No labels