- From: Winzell, Peter <peter.winzell@volvocars.com>
- Date: Mon, 21 Oct 2019 19:00:38 +0000
- To: "public-automotive@w3.org" <public-automotive@w3.org>
- CC: "ted@w3.org" <ted@w3.org>
- Message-ID: <E2D0A8C5-9664-4D4E-85E2-E6A09536EF07@volvocars.com>
Agenda proposal: 1. Decide on Base Document: * Gen2 as is * Clean new document * VIWI submission * VSS 1. Pr #309 * Authentication and Authorization chapter in CORE doc created via input from VIWI. TRANSPORT doc updated to match current VSS modelling We don’t seem to have finalized which base doc to use. Its pressing since we also have a pull request pending on Gen2 document. Feel free to add agenda items . Br Peter Winzell From: "Winzell, Peter" <peter.winzell@volvocars.com> Date: Monday, October 7, 2019 at 2:11 PM To: "public-automotive@w3.org" <public-automotive@w3.org> Cc: "ted@w3.org" <ted@w3.org> Subject: Agenda Hi All! Tomorrows agenda : 1. Reschedule of WG meeting 1. Here and back again I have had an idea that we perhaps should try I more “agile” approach to the spec work going forward. My proposal would then to for a first “sprint” (don’t really think spring is an appropriate term for our group but in lack of anything better) Focusing on : 1. Adding HTTP to VISS(REST) * This sprint we would limit our self to adding the HTTP protocol and APIS (GET,SET,…)to the spec. 1. Reviewing VISS authorization/authentication of tokens and compare that to VIWI * What is missing in VISS and what can should be added. The gate criteria to move on to the next “sprint” would be to have these items added into the spec with full group consensus. I think we could benefit from working on the spec one sprint at a time. Then when we feel that the spec is ready we submit. 1. Other VSS addtions (and/or how we should view VSS versions) * Vectors * Anything else… 1. Use Cases * First responder case Joakim S. * … Please feel to add items to the agenda. /pw
Received on Monday, 21 October 2019 19:01:52 UTC