18:28:10 RRSAgent has joined #auto 18:28:10 logging to https://www.w3.org/2022/01/04-auto-irc 18:28:12 RRSAgent, make logs Public 18:28:13 Meeting: Automotive Working Group Teleconference 18:28:22 Chair: Peter, Ted 18:28:23 scribenick: ted 18:28:27 Scribe: Ted 18:29:42 agenda+ Advancing VISSv2 18:30:23 agenda+ VSS et al uptake 19:03:28 Present+ Carine, Ulf, Ted, Daniel, Gunnar, Glenn, Ashish, MagnusG 19:03:30 zakim, next agendum 19:03:30 agendum 1 -- Advancing VISSv2 -- taken up [from ted] 19:03:43 * Explainer 19:03:44 * Review 19:03:44 * Implementation experiences 19:03:45 * Publish WD snapshot 19:04:11 Ted: per Carine's suggestion, we hould create an -> https://tag.w3.org/explainers/ Explainer and perhaps update -> W3C Auto page https://www.w3.org/auto/ after 19:07:19 … landing page needs to emphasize CVII and that it is a joint effort with COVESA more 19:07:19 … it needs to understandable by a layperson, what problem[s] are we trying to solve? 19:07:19 … it can be short, in fact better if it is. Looking for volunteers 19:08:34 Peter volunteers to co-author with Ted 19:08:55 Ted: ask Adnan/Daniel to bring back his BMW colleagues for an update, learn from Bosch intention (+timeline) to implement 19:10:42 Daniel: various colleagues are still on holiday but can check with them 19:10:53 Ted: Carine, could you setup Echidna so we have a contemporary Working Draft that reflects latest Editor's Draft? 19:11:42 Carine: there are some some things we can do to automate publishing the pair together 19:12:13 https://github.com/w3c/automotive/pull/440 19:12:30 Ulf: some minor stuff has come up from working on protobuf implementation 19:13:33 … for example error messages could arise instead of content and may confuse what request it is with 19:13:48 … worth adding subscription id to error message to know which it belongs with 19:14:08 … we have examples on most filtering alternatives but were missing one for range so added 19:14:58 … some minor cleanup on terms 19:16:22 … we allowed for an empty string in request in the Core document whereas now we require a value 19:16:39 [range example] 19:19:36 Ted: Wonsuk has been very helpful on editorial suggestions so perhaps tag him as a reviewer. I can also handle the merge 19:22:02 Topic: Business Group and other news 19:22:28 Ted: no progress on Best practices draft, still on me 19:22:43 … anything from VSSo side? @@report 19:23:21 Daniel: we should coordinate on slack and can be ready by next week 19:23:23 zakim, next agendum 19:23:23 agendum 2 -- VSS et al uptake -- taken up [from ted] 19:24:40 -> https://www.politico.com/news/magazine/2021/12/27/self-driving-car-big-tech-monopoly-525867 Industry Trends and Uptake 19:26:43 * VSS in the cloud 19:26:43 * EV startups in addition to traditional OEM 19:26:43 * Improve communications 19:27:22 Gunnar: yeah that we were creating benchmarks for AAOS 19:31:50 Ted makes case for promoting the activity with our respective communications teams 19:32:07 Glenn: we can perhaps work on a draft and share with this group, what is the next step? 19:34:08 Gunnar: our marketing team has encouraged participants to take an active role in promoting and would welcome that 19:34:58 … we can include Brandy and Matt from our side and welcome W3C involvement 19:41:10 Ted: @@EV startups 19:41:29 Peter: I have some good connections at Rivian, former Volvo guysk, and heard a rumor that they're using VSS 19:41:34 Ted: yes, please 19:41:56 … and makes sense since AWS is going VSS 19:42:07 s/guysk/guys/ 19:43:18 Peter: I've been using an EV for the last couple weeks and can attest to need to align on data around charging 19:43:29 Gunnar: a great example 19:43:37 Peter: I don't see any other alternatives to VSS 19:44:17 @@Inago 19:46:48 Gunnar: getting these types of companies into the conversation would be helpful 19:47:03 … we come across companies starting to use VSS etc after the fact 19:51:19 … I still want to align more with Sensoris 19:52:10 Daniel: no more contact on my side with Sensoris 19:52:54 … agree collaboration with them would make sense, it would be an investment on time 19:53:33 Glenn: appreciate the discussion, wanted to also bring up the cloud providers and assume OEM would want to see VSS taken up there more 19:53:57 Gunnar: fully agree 19:55:37 Ted: that was part of AWS announcement, MS perhaps with software defined vehicle with Bosch and others, DTDL..? 19:57:54 @@voice_brief_history 20:01:43 I have made the request to generate https://www.w3.org/2022/01/04-auto-minutes.html ted 20:04:24 s/@@report/we have clarification from W3C's lawyer, encouraging us to publish VSSo as a Business Group report to have clear IP. we can publish a FPWD in the WG at the same time/ 20:06:20 s/@@Inago/Ted: nearby I learned thanks to Daniel's encouragement that Inago (sp?) has implemented VSS/VISS and presumably will VSSo for AV AI in Project Arrow, an EV/AV startup effort. They want to bring their work to this group and open source portions/ 20:07:21 s/@@EV startups/COVESA+W3C has focused more on traditional OEM and we should also be working to bring in the EV startups into the conversation/ 20:09:08 s/@@voice_brief_history/… we are running out of time but related to going after the cloud guys for VSS in the cloud they are also the companies behind the biggest voice engines being used in vehicles, we want them using VSS descriptions (in native languages) where possible imho/ 20:09:09 I have made the request to generate https://www.w3.org/2022/01/04-auto-minutes.html ted 21:04:08 Present+ Peter 21:04:18 I have made the request to generate https://www.w3.org/2022/01/04-auto-minutes.html ted 21:05:45 s|create an -> https://tag.w3.org/explainers/ Explainer and perhaps update -> W3C Auto page https://www.w3.org/auto/ after|create an -> https://tag.w3.org/explainers/ Explainer| 21:05:47 I have made the request to generate https://www.w3.org/2022/01/04-auto-minutes.html ted 21:08:39 regrets+ Erik 21:08:41 I have made the request to generate https://www.w3.org/2022/01/04-auto-minutes.html ted