...
VSS feeder proof-of-concept demo
- Stefan: shows a slidedeck (Stefan Wysocki please upload your slide deck, thanks) this slidedeck presenting the analysis and experimentation he made on the VSS feeder of the EDS part of the proof-concept
- first topic is about using opends as the vehicle simulator to feed the vss feeder
- code written in nodejs
- use a naive database written in json
- Gunnar: the transformation of signals into VSS is done manually in your example, we could make a generic mapping on how to translate from one signal to the VSS tree
- Stefan: agreed
- second topic is about using the genivi-vehicle-simulator (GVS) - as the vehicle simulator to feed the vss feeder
- Stefan: provides a short overview of the simulator
- Gunnar: did you have trouble compiling the vehicle simulator code
- Stefan: none
- Philippe: asks question to Magnus about the simulation of EV vehicle signals in GVS
- Magnus: will look at how to implement a small model for simulating EV signals in GVS
- Philippe: explains as a side comment the reason why the GENIVI CCS project is introducing EV signals in the VSS tree: first this is to a state-of-the-art demo showing connected EV data rather connected ICE vehicle data and second this is also an attempt to trigger OEMs on providing inputs on EV data
- Johan: we are using a different version of opends in W3C, we made some small changes
...
- Alex: we are using Apollo graphql server which needs an addition for web token management, and other stuff we are working on, I have discussed which contribution we could do with Markus
- BMW has the blue box on the right box (authentication) (look at the EDS architecture diagram)
- BMW has only the EDS implementation, not the Internal Data Server one
- Alex: the permissions are not yet what we need
- discussion on the work to do for the authentication and the access control groups
- Gunnar: we need to do a more formal description of things to be done for the authentication
- Alex: might be able to do some work in the next days, will try out my ideas on an actual implementation, as soon as I have something (next week possibly), I will generate some docs like ppt
- Alex: tooling is not clear for me yet, as soon as we agree on the way to specify things, we will talk about tooling and manifest generation
- discussion on the naming of artefacts
- Alex: we want to have a nodeJS graphql implementation running
- Alex: I can describe the nodeJS and graphql installation and the deployment of json files
- Gunnar: the wiki page for documenting tihs is AASIG: Implementation notes
- /TODO/ Alex to describe the nodeJS and graphql installation in the above wiki page
- Stefan: at Alex, since you have the authentication implementation under way, could you spent some time to describe what you have done so that we can identify the leftovers ?
- Alex: I can explain that, for instance we need a json web token implementation
- /TODO/ Alex & Stefan to clarify what could be the contribution of BMW & Tieto to the authentication mechanism implementation
...