[discussion around CES, blockchain/mobi etc]
https://github.com/w3c/automotive/pull/320 agreed end of year to merge
315 related to second agenda topic
https://github.com/w3c/automotive/issues
Ted to respond to 321 and close 265
Ted to merge pull request 320, leave issue 319 open
306 and 301 relate to 315 pr and agenda 2
https://lists.w3.org/Archives/Member/member-automotive/2019Dec/0002.html
Ulf: basically proposing adding
read/write access as a tag on the signals being sent back from
the server
... the 'guard' controlling access will be in the Gen2
implementation or called by it
... client can use its token to authenticate itself
... tag on access is optional
... no tag means no restriction
Peter: this is to be added to VSS itself?
Ulf: yes, this illustrates how it
works within the implementation
... different OEM will have different requirement on read/write
access
Ted: summarize thinking around granular access control in VISS, need for best practices maybe including configuration in application manifests to define expected behavior on given vehicle. still times we may want dynamic acl information sent with the data
Peter: second step would be the how to add?
Ulf: yes
... branch can inherit restriction
Daniel: prompts a couple of
things, this would need to be added on the fly
... this is in the implementation and maybe falls into best
practices
Ted: 3rd party app best practices to be part of business group focus for 2020
Ulf: I'll open an issue
Ted: I see this as a solution potentially along with configuration in manifests to let an app know dynamically on the fly what is current acceptable behavior
https://github.com/w3c/automotive/pull/315
https://lists.w3.org/Archives/Public/public-automotive/2020Jan/0002.html
Ted summarizes discussion between himself, Daniel and Adnan
sends by email
Ted summarizes scoping discussion for BG, sends email
https://lists.w3.org/Archives/Public/public-automotive/2020Jan/0003.html