Page History

...

Value measurement formats

Monday,  June 8 - Communication Framework

First call - Asia friendly time 11:30am CET

Agenda

• weekly sync with Sanjeev : review of workplan on other technology options for implementing the framework
  

Participants

• Sanjeev, Gunnar, Philippe

Minutes

review of workplan

• review of slide deck attached to

  Jira
  server JIRA serverId 121ddff2-c571-320f-9e4d-d5b9371533bd key CCS-124

• Milestone content (slide #2)

  • checking of the milestones content

  • TODO Philippe to projectize slide #2 DONE

  • Jira
    server JIRA serverId 121ddff2-c571-320f-9e4d-d5b9371533bd key CCS-160

    created with subtasks

• Edge Computing (slide #5)

  • Samsung is working on the smart phone aspects of edge computing

  • link https://docs.edgexfoundry.org/1.2/microservices/device/sdk/Ch-DeviceSDK/

  • TODO TBD to look a little deeper in edgexdoundry for a demo poc

    • Jira
      server JIRA serverId 121ddff2-c571-320f-9e4d-d5b9371533bd key CCS-163

      unassigned for the time being

• Apache Spark (slide #4)

  • Gunnar: it is not only a database

• VSS on Eclipse Paho (slide #6)

  • Gunnar: mentions the ticket about mapping VSS to MQTT (specification only)

  • Sanjeev: Eclipse Paho is just a tooling

  • Sanjeev: it comes with a simulator which is quite attractive

  • Gunnar: VSS on MQTT - maybe we need to work on this earlier than December; someone else can perhaps look at it

Cloudera

• 
  

  
  

  Gunnar: Cloudera contacted, no feedback from them yet

• Jira
  server JIRA serverId 121ddff2-c571-320f-9e4d-d5b9371533bd key CCS-59

  commented

Second call only - US friendly time 16:00 CET

Agenda

• CVII

Participants

• Keith, Ted, Ulf, Glenn, Steve, Kevin, Gunnar, Philippe

Minutes

CVII

• Gunnar: makes a recap on CVIM discussion, Gunnar Andersson please update the slide you showed, thanks

• Keith: who is the OEM active in W3C ?

• Ted: JLR

• Keith: what is the service catalog about ? VSS is about the data acquisition

• Ted: JLR is proposing something to GENIVI & W3C for the command side (service catalog)

• Ted: please have a look at https://www.w3.org/2020/03/26-auto-minutes.html#item05

• Keith: I heard quite a few OEMs would not get on-board a command API, their concerns is that if you have an API, here are also the parameters on the command, and it gives your IP away from this knowledge, I have been pushed back

• Keith: OEMs even described which functions they do not want to be visible

• discussion on proprietary vs. non-proprietary model items

• Keith: Autosar define their own internal stanfards (for application component APIs) but the architects of the vehicle projects did not use them because they consider it is too much effort

• Keith: OEMs love standards for off-the-shelf ECUs and sensors but not for internal work

• Gunnar: there is an ability to have private branches in VSS, they could be positioned as VSS Extensions

• Gunnar: currently we name everything as VSS, it might be worth thinking about differentiating the naming of the data model and the tooling and the spec langage

• Kevin V: IMHO it is a little bit tricky to make a common service API

• Gunnar: shows an example of a service catalog from the github repo, we use same words and features as Franca

• discussion with Kevin on the service API, for instance the function turnonheater

• Kevin V: approach has changed in order to make no assumption on how an OEM intends to implement the control of a function, a signal group is used then for this purpose

• Ulf likes the structured way we used

learning about production platforms for connected vehicle services

• Philippe: reminds Glenn about

  Jira
  server JIRA serverId 121ddff2-c571-320f-9e4d-d5b9371533bd key CCS-125

  , our expectation was added as a comment there

Wednesday,  June 3 - Communication Framework

...