Meeting minutes
VISSv2
VISSv2 review is done, feedback incorporated by Ulf, privacy section started, wanting breakout calls with Sebastian/others from Bosch before we publish
Ted: figured today we can do a summary of breakout calls, status
VSSo
Ted: we're having regular
VSS/VSSo calls preceding this one, some open design decision
discussions in github repo, getting good input from Bosch, meeting
with Microsoft Digital Twin Definition Language (DTDL) and connected
vehicle people to map VSSo to DTDL
… Benjamin and I have been attending these EDM
Council meetings on developing related automotive ontologies and
we might hear of some from (handful of companies, some participating
in this activity) around vehicle life-cycle
Peter: we are mapping our signals to VSSo/VSS currently internally for a PoC
Ted: he is in some of those calls and aware we are refactoring
Adnan: you in contact with Daniel?
Peter: Joakim is and will make sure he's aware he can reach out
Gunnar: you're welcome on those calls too
Peter: purpose of the PoC is to demonstrate the usefulness
Daniel: we are hopefully going to start getting some input and requirements from MS and others
… need to collect those as issues in repo
RPC
Arman: vehicle delivery has a number of potential impersonation problems, either decoy vehicle or bogus delivery person
Ted: true, when think of the multitude of delivery services and how strong their communications security is. my preferred pizza place was hacked a few weeks ago...
RPC
Ted summarizes, adding to Geofencing use case notes in RPC and Best Practices' location handling section
Gunnar: right in a holding pattern, waiting for a particular oem
… intent is to build out some concrete services built by tooling before looking at WAMP, gRPC etc
Ted: also interest in aligning with Bosch IoT events and BMW WoT approaches, see if we can agree on common catalog if protocols vary
Gunnar: we will be having a webinar
webinar (link from Glenn)
Ted: maybe also encourage people to read your proposals on slack earlier, and related to RPC event leaf type
Gunnar: events and signals may be related to operation, signals is easy to refer back to but still discussing if events should be there or somewhere else
… how are events defined or can they carry data?
Daniel: WoT is taking semantics of signals and making RPC like calls
… in github we have a couple comments on VSC, how to use YAML discussion as well
Semantic Object Modeling Uber schema handling (links Daniel provided from VSS call earlier)
https://www.asyncapi.com/(link provided by Adnan)
Gunnar: we need something more elaborate than OpenAPI
Daniel: yes but the structure is the same
… agree OpenAPI is really REST based
Gunnar: we have some motivation to map to Franca
Daniel to update VSSo wiki in github
Best Practices and Geofencing
Ted summary of call last week, sent some notes and links
Adnan: we used a JS library and will need to look at what we used
Glenn: I don't have details on how that works in our setup either but agree it is a useful use case
Ted also reached out to SDW group
Glenn: I was reading an article about elephants being tracked via geofences
MagnusG: I was involved in a dangerous goods working group that was using geofencing for detecting route deviation
… that is handled with UN regulations
Ted: might be worth seeing how they define that
Glenn: I have seen where hazardous routes are known/shared
MagnusG: this is heavily regulated and has come up with V2x
Ashish: I'm looking for a related paper where they created groups within a city. notifications are sent based on location, eg deer citing
Please contribute any notes around Geofencing usage to Best Practices wiki in either Location/Geofencing section or links in Reading List