IRC log of auto on 2021-01-18

Timestamps are in UTC.

17:59:06 [RRSAgent]
RRSAgent has joined #auto
17:59:06 [RRSAgent]
logging to https://www.w3.org/2021/01/18-auto-irc
17:59:08 [Zakim]
RRSAgent, make logs Public
17:59:09 [Zakim]
Meeting: Automotive Working Group Teleconference
18:01:40 [ted]
Meeting: RPC / VSC
18:01:47 [ted]
Present+ Gunnar, Ted, Ulf, MagnusF
18:03:55 [ted]
Present+ Glenn
18:06:25 [ted]
Present+ Jon
18:08:17 [ted]
[Magnus shares screen to demo a code generator he is trying to open source]
18:08:52 [ted]
[seat service YAML, type defs, structs...]
18:09:43 [ted]
[we can use enums. interfaces with commands but no return values]
18:10:29 [ted]
[not fire and forget. state reflected in signals]
18:11:00 [ted]
MagnusF: want to see if people agree on this, what we're putting into the catalog
18:11:35 [ted]
… can't show code until released. there is a dbus python template, stub code IDL generator
18:12:30 [ted]
… we have a dump template
18:12:46 [ted]
Gunnar: you look at ginga (python templating system)?
18:13:23 [ted]
MagnusF: back in JLR days and forget what we didn't like about it. cheeta works, bit difficult to read
18:24:01 [ted]
MagnusF: intent is to have enough Franca compatability
18:24:07 [ted]
Gunnar: YAML syntax a bit different
18:24:11 [ted]
… if you are formal about parsing, there is potential to have different ways to represent syntax tree
18:24:26 [ted]
MagnusF: we have a formal syntax though
18:24:44 [ted]
Gunnar: I guess it depends on how it is parsed and what the python objects look like
18:25:10 [ted]
MagnusF: it mirrors and expands the tree
18:26:03 [ted]
Gunnar: there are some Franca/python couplings that might be worth looking at
18:26:14 [ted]
scribenick: ted
18:26:43 [ted]
MagnusF: purpose of all this is to agree on service catalog format, integrate VSS into it
18:28:34 [ted]
… we have configuration service, deployment file... service file
18:28:56 [ted]
… I do simple key/value storage for sake of demonstration, would be tied to back end
18:29:20 [ted]
… I also did a simple http service to be able to GET values
18:30:16 [ted]
… we then start creating interfaces... interface file picked up from extensions
18:31:11 [ted]
… even though it doesn't look great, the generated code works
18:32:10 [ted]
[demo starting config server, client and client profile]
18:32:39 [ted]
Gunnar: what is a profile here?
18:32:54 [ted]
MagnusF: user profile, music stations, seat position...
18:33:13 [ted]
… it allows you to support multiple users (drivers)
18:33:53 [ted]
… the intersting thing will be in rust, mixing and matching python, rust and later RPC
18:34:04 [ted]
… you can mix and match between languages and networks
18:35:21 [ted]
… this is what I intend to open source, will work on rust and a powerpoint to better present
18:35:52 [ted]
… I understand this may compete with WoT. I see it more as a backdrop for conversation
18:37:29 [ted]
Ted: I see WoT as a bridge, short and long term as IoT will be desireable after we settle on rpc and it gets established
18:38:32 [ted]
Gunnar: AGL has a rest interface with JSON, we may want a wrapper for that as well
18:38:48 [ted]
MagnusF: there may be multiple mappings
18:39:58 [ted]
Gunnar: big picture for CVII we can make clear the different paths for same purpose. in some cases there will be legacy technology but still benefit from a common underlying model
18:40:01 [RRSAgent]
I have made the request to generate https://www.w3.org/2021/01/18-auto-minutes.html ted
18:40:43 [ted]
MagnusF: resulting in different code generators potentially?
18:41:09 [ted]
Gunnar: yes, but we will see the same VSS/VSC data types, meanings etc
18:41:32 [ted]
MagnusF: we want model passthrough
18:41:44 [ted]
… I will look into ginga
18:47:06 [ted]
YSS and YAML. unattended delivery
18:47:26 [ted]
Ted will take an initial pass after finishing a grant proposal
18:47:50 [ted]
MagnusF: I need to think about how to roll VSS into this
18:48:02 [ted]
… do we want to treat VSS as properties on a global level?
18:48:08 [ted]
… or we do we treat them as events?
18:48:23 [ted]
Gunnar: settable and gettable
18:48:49 [ted]
MagnusF: event for maybe actuation
18:49:06 [ted]
Gunnar: property if we look at the protocols with get/set and subscription
18:49:12 [ted]
… an obersvable property
18:49:29 [ted]
MagnusF: this is going to get interesting. are we going to use RPC to set signals?
18:49:49 [ted]
… if not...
18:50:26 [ted]
Gunnar: we discussed what an actuator is. actuator can be written, sensors for only reading
18:50:48 [ted]
… if you look at the other side, someone/something is writing the value inside the system
18:53:31 [ted]
Ted: in some cases the events will set/change values and in different order
18:54:31 [ted]
Gunnars: events are distinct. signals can be confused with events. we may want the named events in VSS tree
18:56:03 [ted]
MagnusF: then it is an integration question, how to incorporate
18:56:41 [ted]
Ted: I don't want to go too far in this discussion without Daniel
18:56:52 [ted]
Gunnar: speculation and discussion fine
18:57:03 [ted]
… we're not making decisions
18:57:04 [ted]
Ted: agree
18:58:04 [ted]
MagnusF: we can extend VSS with an event concept
18:58:18 [ted]
Gunnar: that is a possiblity
18:59:13 [ted]
MagnusF: I'll give it more thought
19:10:27 [RRSAgent]
I have made the request to generate https://www.w3.org/2021/01/18-auto-minutes.html ted
19:10:29 [Zakim]
leaving. As of this point the attendees have been Gunnar, Ted, Ulf, MagnusF, Glenn, Jon
19:10:29 [Zakim]
Zakim has left #auto
19:10:30 [RRSAgent]
I see no action items