W3C home > Mailing lists > Public > public-automotive@w3.org > December 2017

Re: Remainder of the year (was Re: Proposed call schedule change)

From: Ted Guild <ted@w3.org>
Date: Mon, 04 Dec 2017 10:12:19 -0500
Message-ID: <1512400339.2918.10.camel@w3.org>
To: "Gavigan, Kevin" <kgavigan@jaguarlandrover.com>
Cc: public-automotive <public-automotive@w3.org>
On Mon, 2017-12-04 at 14:01 +0000, Gavigan, Kevin wrote:
> Hi Ted,
> 
> >> .It would be nice to wrap up the outstanding issue for VISS by
> email.
> 
> Following the discussions with the TAG Group etc. is there a
> preferred form of words e.g. a paragraph that captures the consensus
> well.

We didn't come up with explicit wording but I tried to come up with the
start of phrasing in the minutes directly as I cleaned them up. 


[OEM can even ship the static conf for a given vehicle as part of an
app package manifest]

[vehicle should handle discovery but may ship or handle via
implementation specific (or discovered on app install) configuration]

https://www.w3.org/2017/11/06-auto-minutes.html#item05

You suggestion works, here is a tweak using should and may with wwwivi
as example so it can stay in the rest of the spec.

Implementations that support additional devices or multiple services
should provide discovery [through mDNS]. Alternatively location of VIS
Server instance on the local vehicle network may be handled by
configuration, either as part of a package manifest or by consulting a
registry on application install. The wwwivi hostname in this
specification is used an example.

I'm inclined not to specify mDNS and leave discovery vague for now
which is why I put that in []. We can refine it with examples later,
especially if we get experience with it.

> If not, would the following be suitable?
> 
> "The implementer will specify the mechanism that is used to locate
> the VIS Server instance on the local vehicle network. This could, for
> example,  be via a Discovery mechanism or based on configuration
> settings."
> 
> Thanks and regards,
> 
> Kev
> 
> Kevin Gavigan BSc, MSc, PhD, MCP, MCTS
> Software Architect
> Connected Infotainment
> Electrical, Electronic and Software Engineering (EESE)
> Jaguar Land Rover
> 
> Mobile: 07990 084866
> Email: kgavigan@jaguarlandrover.com
> 
> Office address:
> GO03/057 • Building 523, Gaydon • Maildrop: (G03)
> Jaguar Land Rover • Banbury Road • Gaydon • Warwick • CV35 0RR
> 
> On 1 December 2017 at 16:18, Ted Guild <ted@w3.org> wrote:
> > Next week I will be in Europe and our WG call would be 2am local
> > time.
> > As a result those calls have had low attendance which is part of
> > the
> > appeal to this new schedule. 
> > 
> > I am canceling next week's WG call. I would be nice to wrap up the
> > outstanding issue for VISS by email.
> > 
> > Since there have been no comments from those who were not at the
> > F2F to
> > the proposed schedule, I am interpreting silence as consent and
> > will
> > work on WebEx coordinates, reminders and such.
> > 
> > The BG is scheduled to meet next on the 12 December. I will be in
> > Detroit but available.
> > 
> > https://www.w3.org/community/autowebplatform/wiki/Main_Page#Meeting
> > s
> > 
> > The next WG call would be on the 19th of December although some are
> > likely starting their holidays. I am traveling overnight (redeye
> > flight) and that morning but unless there are flight delays can
> > make
> > it.
> > 
> > https://www.w3.org/auto/wg/wiki/Main_Page#3rd_Tuesday_of_Every_Mont
> > h_.28US_and_Europe_friendly_times.29
> > 
> > What probably makes the most sense is to have the 12th BG meeting
> > be
> > the last of the year and to allow for WG topics to be included.
> > 
> > On Tue, 2017-11-28 at 17:03 -0500, Ted Guild wrote:
> > > At the F2F meeting there was a proposal to change our call
> > cadence
> > > and
> > > time. There was a agreement with the attendees but want
> > acceptance
> > > from
> > > the broader group.
> > >
> > > Starting with the New Year, January 2018, the Auto WG should
> > start
> > > meeting weekly instead of twice a month. It should rotate so as
> > to be
> > > accommodating to various time zones. There are uncomfortable
> > times in
> > > each of the major timezones covered and it is expected people may
> > opt
> > > out of attending those, instead relying on minutes, email and
> > > subsequent meetings.
> > >
> > > Tuesdays 
> > >
> > > CEST: 6am / 3pm / 11pm
> > >
> > > EDT: 12am / 9am / 5pm
> > >
> > > PDT: 9pm / 6am / 2pm
> > >
> > > BST: 5am* / 2pm / 10pm
> > >
> > > JST & KST: 1pm / 10pm / 6am
> > >
> > > An automated reminder will be sent and ideally the Chairs and I
> > will
> > > settle on an agenda that can be sent in advance so people can
> > decide
> > > if
> > > they want to stay up late/get up early for a particular call. 
> > >
> > > If a particular meeting is canceled then that time is skipped for
> > > that
> > > rotation and does not carry over to the following week since that
> > > would
> > > complicate how some may configure their calendars.
> > >
> > > When we discussed we also felt it would make sense to have the
> > > Business
> > > Group call, currently at a fixed time on the second Tuesday of
> > the
> > > month, immediately follow the Working Group call. The combined
> > > Business
> > > and Working Group meeting would have a total duration of one hour
> > and
> > > thirty minutes. The time would generally be divided evenly but
> > can
> > > take
> > > into consideration whether a topic for one may need more
> > discussion.
> > >
> > --
> > Ted Guild <ted@w3.org>
> > W3C Systems Team
> > http://www.w3.org
> 
> 
-- 
Ted Guild <ted@w3.org>
W3C Systems Team
http://www.w3.org
Received on Monday, 4 December 2017 15:12:36 UTC

This archive was generated by hypermail 2.3.1 : Monday, 4 December 2017 15:12:37 UTC