Versions Compared

Old Version 114

changes.mady.by.user Philippe Robin

Saved on

compared with

New Version 115

changes.mady.by.user Philippe Robin

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

  • W3C workshop on data models for transportation - useful readings

    • the list of presentations (and slide decks) is at: https://www.w3.org/auto/events/data-ws-2019/schedule.html

    • 2 presentations need to be highlighted

      • Towards A Common Data Model Kenneth Vaughn, Trevilon

      • https://www.w3.org/2019/09/trans-data-ws/ITS_Data_Model-W3C-2019-09.pptx

      • Gunnar: introduces the slide deck, we should review with the comprehensive web site, the work seems to be fairly USA centric and ITS-related and related to fleet operation, we might be willing to take this into account in our work

      • Steve (who attended the workshop): it was an interesting presentation, consolidation of info from various specs, navigable on-line site with connection through various data models

      • slide 10: shows all data models in scope of this work

      • /TODO/ Bosch review the slide deck and possibly report on findings for next week

      • jira ticket created

      • Towards a SAREF extension for Automotive Michelle Wetterwald, Netellany

      • https://www.w3.org/2019/09/trans-data-ws/SAREF.pdf

      • this work was pointed out by one of the AutoMat project participants interviewed by Philippe late July

      • Philippe: it refers to the work on data ontologies pushed by EU whose motivation is to define and promote an European standard

      • /TODO/ Benjamin review the slide deck on SAREF (TBC), Philippe will ask him about it

      • jira ticket created

      • Don: was VSS discussed there ?

      • Steve not in the workshop because VSS was discussed in a W3C auto WG scheduled the days before

      • Don: what about VSSo work ?

      • Gunnar: VSSowork  is led by Benjamin and Daniel Wilms (BMW)

  • OCF Automotive update

    • Don: the OCF SC is still considering doing a demo at CES, there is an OCF interop event planned later this year, theme of the possible CES demo will be ratherabout  electrification / charging status in the home

  • Gap analysis deliverable - review of drafts

    • Philippe: Benjamin said it will start working on it on Wednesday
      • Gunnar: before I can start writing my contribution, I feld the need to put down my thoughts on the framework design
      • these can be found at Design concerns that shows the different ways we can think about for the framework design
      • Philippe: I would recommend that you review the architecture and building blocks for the neutral server approach with High Mobility because this is their business and the same for the big data approach with Cloudera because this is also their business
      • Philippe (added offline). Kevin said last week he could add to the initial list questions coming from their experience with 3rd parties at High Mobility
      • Gunnar: we need to spot a technical contact at Cloudera (I will ask Michael Ger)

      • Gunnar: we should also dig a little bit into vehicle fleet data management and impact on the "design concerns" content

      • Gerald: this is what Sensoris has looked into

  • Sprint & backlog review

    • VCSCCS-59 to be checked with cloudera and engineers there

    • VCSCCS-35 Philippe will ping daniel wilms

    • VCSCCS-6 we should start populating it with work items related to Gunnar's thoughts on software designs, Gunnar: will do that, a link to Design concerns pzge added to the Jira ticket

    • VCSCCS-38 /TODO/ @Kevin can you close it ?

    • VCSCCS-39 Philippe will ping Sebastien about the status of the Kuksa project

  • AOB

    • notification scheme in Jira to be checked, Philippe will create a test jira ticket, reminders listed above will be sent by email

    • login Don credentials are working now

...

  • Gap analysis deliverable status
    • assignment of sections to contributors: Benjamin, Guru, Gunnar, Kevin
      • look at
    • Jira tickets updated accordingly VCSCCS-54 to VCSCCS-58
  • Sprint & backlog review
    • Jira
      serverJIRA
      columnskey,summary,type,created,updated,due,assignee,reporter,priority,status,resolution
      serverId121ddff2-c571-320f-9e4d-d5b9371533bd
      keyVCS-24
      • Benjamin: this relates for instance work in W3C Data TF, look at https://www.w3.org/community/autowebplatform/wiki/Data_tf
      • Gunnar: this is not gap analysis, this is something different, it relates to the glossary / definition of terms, we should create a wiki page describing what these terms mean
      • the W3C wiki page above is one input for this ticket
    • Jira
      serverJIRA
      columnskey,summary,type,created,updated,due,assignee,reporter,priority,status,resolution
      serverId121ddff2-c571-320f-9e4d-d5b9371533bd
      keyVCS-5
      • assigned to Gerald for adding a description of the work item
    • Jira
      serverJIRA
      columnskey,summary,type,created,updated,due,assignee,reporter,priority,status,resolution
      serverId121ddff2-c571-320f-9e4d-d5b9371533bd
      keyVCS-6
      • discussion on the functional architecture reference diagram
      • Gunnar: the picture is not final yet, it is just an example
      • Philippe: we should ask Cloudera for their vision of the big picture for the big data gathering
      • Jira
        serverJIRA
        columnskey,summary,type,created,updated,due,assignee,reporter,priority,status,resolution
        serverId121ddff2-c571-320f-9e4d-d5b9371533bd
        keyVCS-59
        created and assigned to Michael Ger
    • Sprint 3 completed and Sprint 4 started
  • OCF update
    • Don gives an update of his discussions with OCF leaders
    • there is a discussion with OCF about the level of membership  that should be propose to vehicle OEMS in order to recruit them
    • Don would like to have the OCF Cloud WG lead attend next week's call, an agenda item will be added for this
    • Philippe: provides clarification on the expected use case to be shown at CES2020 from GENIVI standpoint
  • last agenda item: Gunnar Andersson - can you add your notes, since I had to switch over to another call ? thanks

...

  • Kevin Valdek opened the meeting and welcomed participants.
  • Discussing the organization of the gap analysis document...
  • Kevin has produced an outline proposal in VCSCCS-48. 
  • Gunnar has put some ideas into a wiki page
  • How do we slice the document.  One chapter per compared (data model) covering all characteristics, or one chapter per characteristics/topic covering all data models.
    • some discussion, no obvious conclusion - but let's write an outline for clearer proposal we can decide on.
  • SC: I would like to see a motivation chapter (for the GENIVI deliverable itself) to clarify document purpose and organization to the reader.
  • Gunnar: Seems like we need to rework this a bit with the given input.
  • Kevin: I volunteer to propose a (new, detailed) outline of the document
  • Kevin will rework the Wiki page that Gunnar started on (because it is now kind of obsolete).
  • Gerald: I can report on my action (VCSCCS-28).  Yes, overall we think CCC digital key is not much in scope. About car data, they are apparently not planning to create a data model / data taxonomy.
  • Gunnar: OK so their main deliverable is requirements, or a design and a programming API?   If a programming API, there can be some similarity between an API and a data exchange model, so I would at least take some look (for overlap) if it is an API.
  • Gerald: ... yes it seems mostly requirements, use-cases, ... maybe more.  I can check a bit more.
  • Kevin/Gunnar: We should include them (any organization that falls a bit out of scope) in the report nonetheless, just to document that we have analyzed them and drawn a conclusion.
  • Gunnar: Let's go through the JIRA tickets so we don't miss anything
  • Kevin: I can do that, I will display...
  • VCS 25 - Gerald: I sent a mail to Sensoris chairman about a joint meeting.  No answer, need to retry this.
  • VCSCCS-50 - (W3C workshop) Steve Crumb: Yes it is confirmed that GENIVI will present the project on the W3C workshop
  • VCSCCS-2  This is Philippe's ticket and looks like a kind of overview tracking ticket (An Epic, sort of)
  • VCSCCS-33 - (SENSORIS vs VSS) Still open only because the presentation has not been published in the Wiki (Benjamin was reminded)
  • VCSCCS-25, Guru working on it.  Keep it open.
  • VCSCCS-34 - Sensoris vs CVIM. We think we can close the ticket.  Overlaps other analysis.
  • VCSCCS-38 - Steve Crumb:  I have an update.  I contacted ANSI via helpdesk.  They require us a site license ($1200) to get the specification and we must put limits on the individuals that may read it.  How many of you can get your own access via your organization?
  • Kevin: I can read the ExVe document.
  • Gerald and Guru: Also we can do that.
  • ...BMW?  (Benjamin can't go on audio, but we assume it ought to be accessible – follow up)
  • SC:  GENIVI might purchase it only for staff since the limited circulation requirement will in that case not allow us to distribute to the members.  Steve will investigate this.
  • VCSCCS-39.  Kuksa. Gerald will contact Sebastian to see status
  • VCSCCS-42.  Automat Security analysis.  Gunnar:  I will try to make sure it is presented to the security meeting this Thursday, as requested.  We assume this ticket stays open until then.
  • VCSCCS-47.  Don:  This is on track.  I am talking to OCF tomorrow.
  • Kevin: Any other business?
  • Meeting adjourned

...

  • review of Jira tickets, Sprint 1 done, Sprint 2 started

    VCSCCS-2

    Analyze data and signal specifications

    • We need to start defining the content and format of the deliverables for those analysis activities
    		Philippe Robin

    VCS Sprint 2, VCS Sprint 1

    (i.e. carried over from Sprint 1 to Sprint 2)

    VCSCCS-42

    Contact OCF Automotive and check for status

    		Philippe Robinadded to VCS Sprint 2
    VCSCCS-41

    Dissemination of connected services projet results (i.e. deliverables, charter, etc.)

    • new epics created for tracking the publishing of results


    VCSCCS-33

    Perform gap analysis of VSS vs. CVIM

    • summary change : comparison changed to gap analysis
    		Benjamin Klotzadded to VCS Sprint 2
    VCSCCS-40

    Publish AutoMat cybersecurity overview

    		Petar Vorotnikovadded to VCS Sprint 2
    VCSCCS-39

    Provide an update on Kuksa project

    		Sebastian Schildtadded to VCS Sprint 2
    VCSCCS-37

    Review CS project charter

    • the charter is attached to the Jira ticket
    • /TODO/ all review the charter and provide comments in Jira
    		Philippe RobinVCS Sprint 2, VCS Sprint 1
    VCSCCS-26

    Survey AUTOMAT specifications (Common Vehicle Information Model - CVIM)

    • findings should be presented shortly at the next call and then published to VCSCCS-2 recommendation
    		Kevin ValdekVCS Sprint 2, VCS Sprint 1
    VCSCCS-38

    Survey ISO Extended Vehicle

    		Gerald SpreitzVCS Sprint 2, VCS Sprint 1
    VCSCCS-34

    Perform gap analysis of Sensoris vs CVIM

    		Gerald SpreitzVCS Sprint 2, VCS Sprint 1
    VCSCCS-25

    Survey SENSORIS specifications

    • Guru will start looking at the Sensoris specifications now (i.e. before the specifications are published which should happen anytime soon) since as Bosch he has access to it
    		GururajaVCS Sprint 2, VCS Sprint 1
    VCSCCS-28

    Survey CCC specifications and check for relevance

    • we need someone to take this work item
    		UnassignedVCS Sprint 2

...

  • news

    • project charter

      • Philippe is preparing a project charter for advertizing our work, we foresee to breakdown the project into 2 stages

      • Stage 1 focusing on data, i.e. what we are initiating now with an objective to decrease the fragmentation of the ecosystem with several different approaches to describe the vehicle data and the communication framework to access them

      • Stage 2 focusing on compute, initial though is to look into cloud computing platform to support mobility and vehicle autonomy

      • this charter will be shared with this project participants
    • project tracker
  • new participant
    • Ilios introduced himself, he works for Obigo (Korea) and is their representative in Europe, he is based in Portugal-based representative attended the weekly call, he will be an observer for the time being, we had a discussion on the GENIVI Korea REG
    • Gerald: asked Iliol whether there are public funded projects related to vehicle data in Korea
  • project status
    • we use the Jira tickets of the active sprint
    • Kevin (High-Mobility) has reviewed the automat project Commoin Vehicle Information Model and presented his findings VCSCCS-26 - Survey AUTOMAT specifications (Common Vehicle Information Model - CVIM) In Progress

      • the model describes big data for connected cars, it is quite different from VSS, it goes very deep in data harmonization and proposes several layers like signals + measurement layer + data package layer

      • Gunnar: how is it compared to W3C

      • Kevin: I have not seen the same information than in W3C

      • Benjamin:  we have a metadata Task Force in W3C, it is part of what next generation will do, we will have different kind of meta data, I would recommend to use the best practice, no competition now from W3C because there is no spec on this topic yet

      • Kevin will summarize his findings in the wiki
    • Petar (Visteon) is reviewing the automat project security model VCSCCS-32 - Read AUTOMAT security document In Progress
    • Gerald (Bosch) will spot the colleague within Bosch who attended the OADF conference, objective is to learn about the Sensoris specifications status VCSCCS-25 - Survey SENSORIS specifications To Do
    • Gerald: we need to make a comparison between the various data and protocol specifications

      • sensoris va automat ==> Gerald / Kevin (due date: 3-week time

      • vss vs sensoris ==> not assigned yet

      • vss vs automat ==> Benjamin (after submitting his thesis at the end of the month) , Gunnar

      • Jira tickets created in VCS

...