W3C home > Mailing lists > Public > public-automotive@w3.org > July 2016

Re: [auto-wg] minutes - 5 July 2016

From: Kazuyuki Ashimura <ashimura@w3.org>
Date: Wed, 6 Jul 2016 12:41:02 +0900
Message-ID: <CAJ8iq9V8P4vHsjUAPSwuJPNQa-noNosvFwNWUKJFWGd9++75Mg@mail.gmail.com>
To: Shinjiro Urata <shinjiro.urata@access-company.com>
Cc: public-automotive <public-automotive@w3.org>
On Wed, Jul 6, 2016 at 10:13 AM, Shinjiro Urata <
shinjiro.urata@access-company.com> wrote:

> Dear Kaz Ashimura-san
>
> I think part of @@@ is my comment.
>
> My comment was something like
> ===
> su: I understand one big theme in F2F's scope of work is VSS discussion
> and prototyping.
> Then we should do something about conventional (JavaScript API style )
> Vehicle API
>  to make it a W3C recommendation? What work is left?
> ===
>

Thanks a lot, Urata-san!

The minutes have been updated accordingly:
  https://www.w3.org/2016/07/05-auto-minutes.html

Thanks,

Kazuyuki




> Best regards,
> Shinjiro
>
>
> 2016-07-06 9:55 GMT+09:00 Kazuyuki Ashimura <ashimura@w3.org>:
>
>> available at:
>>   https://www.w3.org/2016/07/05-auto-minutes.html
>>
>> also as text below.
>>
>> Sorry but my connection was very unstable today and I missed
>> several points (e.g., the topic marked with "@@@"). So your
>> clarification is very welcome.
>>
>> Note that I've just added "Contribution" sub section to the Portland f2f
>> agenda wiki at:
>>
>> https://www.w3.org/auto/wg/wiki/Main_Page#July_26-28.2C_2016_in_Portland.2C_OR
>>
>> Please add your own topics with your name as well :)
>>
>> Thanks,
>>
>> Kazuyuki
>>
>> ---
>>    [1]W3C
>>
>>       [1] http://www.w3.org/
>>
>>                                - DRAFT -
>>
>>                              Automotive WG
>>
>> 6 Jul 2016
>>
>> Attendees
>>
>>    Present
>>           Paul, Kaz, Rudi, Joonhyung, Urata, Wonsuk, Hashimoto,
>>           Song_Li, Hirabayashi
>>
>>    Regrets
>>           Peter
>>
>>    Chair
>>           Paul, Rudi
>>
>>    Scribe
>>           kaz
>>
>> Contents
>>
>>      * [2]Topics
>>          1. [3]Today's agenda
>>          2. [4]Portland F2F
>>      * [5]Summary of Action Items
>>      __________________________________________________________
>>
>> Today's agenda
>>
>>    pb: f2f, spec, security, OCF/OMA, etc.
>>    ... Peter is not available today
>>
>>    pb: got question from Sanjeev about where to put codes on the
>>    GitHub
>>
>> Portland F2F
>>
>>    rs: looking at the wiki page now
>>
>>    ->
>>    [6]https://www.w3.org/auto/wg/wiki/Main_Page#July_26-28.2C_2016
>>    _in_Portland.2C_OR Portland f2f wiki
>>
>>       [6]
>> https://www.w3.org/auto/wg/wiki/Main_Page#July_26-28.2C_2016_in_Portland.2C_OR
>>
>>    rs: goes through the f2f agenda wiki
>>    ... architecture tree diagram
>>    ... Sanjeev working on integration OCF's IoTivity
>>    ... hackathon is one of the efforts during the f2f
>>    ... we can build concrete agenda based on the wiki description
>>    ... Kevin wrote some code for WebSocket
>>
>>    pb: (checks the attendees)
>>
>>    rs: will put some more ideas on the agenda wiki
>>    ... people can also add their topics
>>
>>    -> [7]https://www.w3.org/2002/09/wbs/1/auto201607/results f2f
>>    registrants
>>
>>       [7] https://www.w3.org/2002/09/wbs/1/auto201607/results
>>
>>    ka: we should add a subsection "Contribution" to the agenda
>>    wiki
>>    ... and all the attendees are encouraged to add their
>>    contributions to that sub section :)
>>
>>    rs: goes through the registration results
>>
>>    pb: is Kevin registered?
>>
>>    rs: Kevin and Adam said they would get registered right after
>>    getting approval
>>    ... but not registered yet
>>
>>    pb: what about Powell?
>>    ... Dave Jensen?
>>
>>    rs: not yet
>>    ... Sanjeev either
>>
>>    (Kaz disconnected...)
>>
>>    @@@
>>
>>    su: we should show JS library
>>    ... also should finalize the spec, e.g., by the end of this
>>    year
>>
>>    pb: maybe would make sense to break up the group for topics
>>
>>    rs: one of what we want to do is API spec
>>    ... would make sense to have JS library
>>    ... also websocket interface
>>
>>    su: what is needed to make the JS api spec a W3C Rec?
>>    ... not much work remaining
>>    ... but want to clarify what to do
>>
>>    pb: implementation experience
>>    ... test suite, etc.
>>
>>    ka: right
>>    ... for CR transition, we need tests, test suite,
>>    implementation report template
>>    ... and comment disposition
>>    ... but we can use github issue list for comment disposition
>>    ... can summarize the procedure in Portland
>>
>>    all: ok
>>
>>    wl: need to see the gap between the JS api and the service
>>    interface
>>
>>    su: right
>>    ... another point is how to deal with "Zone"
>>
>>    wo: how about gathering issues
>>    ... I'll send an email to the group list
>>    ... we can discuss the issues during the f2f in Portland
>>
>>    ka: would like to make a brief report from the ITU-T's ITS
>>    workshop on July 4-5 during the Portland meeting
>>
>>    pb: everybody, please put all your ideas for the f2f to the
>>    wiki
>>
>>    rs: anybody have any update for today?
>>
>>    jh: participated in the TTC/ITU-T conference in Japan on July
>>    4-5
>>    ... Kaz, did you make any report about that?
>>
>>    ka: briefly mentioned that during this call
>>    ... and would make a detailed report in Portland
>>
>>    pb: anything else?
>>
>>    (none)
>>
>>    rs: ok
>>    ... will send another reminder for the f2f
>>    ... there is 3 weeks before the meeting
>>
>>    [ adjourned ]
>>
>> Summary of Action Items
>>
>>    [End of minutes]
>>      __________________________________________________________
>>
>>
>>     Minutes formatted by David Booth's [8]scribe.perl version
>>     1.128 ([9]CVS log)
>>     $Date: 2016/07/06 00:44:50 $
>>
>>       [8] http://dev.w3.org/cvsweb/~checkout~/2002/scribe/scribedoc.htm
>>       [9] http://dev.w3.org/cvsweb/2002/scribe/
>>
>>
>
> .




-- 
Kaz Ashimura, W3C Staff Contact for Auto, WoT, TV, MMI and Geo
Tel: +81 3 3516 2504
Received on Wednesday, 6 July 2016 03:42:13 UTC

This archive was generated by hypermail 2.3.1 : Tuesday, 24 October 2017 18:52:51 UTC