Re: Cheching the schedule of FPWD for vehicle signal server spec

Thank you, Wonsuk. So do I. I am not yet familiar with the processes. What
is next?

Thank you,
:rjs

On Mon, Oct 10, 2016 at 5:18 PM, 이원석 <wonsuk.lee@etri.re.kr> wrote:

> Chairs.
>
> I support to publish the FPWD for vehicle signal server spec with current
> editor’s draft!
>
>
>
> Cheers,
>
> Wonsuk.
>
>
>
> *From:* Streif, Rudolf [mailto:rstreif@jaguarlandrover.com]
> *Sent:* Tuesday, October 11, 2016 1:00 AM
> *To:* Peter Winzell <Peter.Winzell@melcogot.com>
> *Cc:* 이원석 <wonsuk.lee@etri.re.kr>; public-automotive <
> public-automotive@w3.org>
>
> *Subject:* Re: Cheching the schedule of FPWD for vehicle signal server
> spec
>
>
>
> Colleagues,
>
>
>
> Did we come to a consensus and are we ready to move forward with the FPWD?
>
>
>
> Thank you,
>
> Rudi
>
>
>
> On Thu, Oct 6, 2016 at 3:35 PM, Streif, Rudolf <
> rstreif@jaguarlandrover.com> wrote:
>
> I ran into a gotcha. I wanted to suggest some edits and based them on the
> rawgit page at http://rawgit.com/w3c/automotive/master/vehicle_
> data/vehicle_information_service.html. This page shows the master branch
> of https://github.com/w3c/automotive. However, the latest changes and
> commits were submitted to the gh-pages branch. This needs to be resolved
> probably by merging gh-pages into master.
>
>
>
> I forked the repo and created a pull request for my suggestions:
>
>    - commit c2bb7655eb47566204dfdcabb00d47136a94ae46
>    In general the use of the word "will" should be avoided unless it
>    actually refers to an event bound to happen in the future. Instead present
>    tense should be used. I learned that from the copy editor of my book.
>    - commit ccf8b93723ff8a5687ead89d6455ce1bee14a5c4
>    Use actual VSS signal paths in examples.
>    - commit 00a371fdb26f93b87f989de20c7174c068bccca2
>    The specification purposely does not specify the authorization token
>    format and structure as well as methods used to secure the token. That
>    is part of the provieder-specific implementation so that providers can
>    choose their preferred formats and methods. However, the
>    specification'
>    was lacking a recommnendation of what a meaningful token should
>    contain.
>
> These three commits contain my recommendations to be included before FPWD.
> However, my approval for FPWD is not contingent on them to be merged.
>
>
>
> Cheers,
>
> Rudi
>
>
>
>
>
>
>
> On Wed, Oct 5, 2016 at 10:28 PM, Peter Winzell <Peter.Winzell@melcogot.com>
> wrote:
>
> Hi Wonsuk and Rudi!
>
> I am ok with publishing as I said to Kevin yesterday.
>
>
>
> Br
>
> Peter Winzell
>
>
>
> *From:* 이원석 [mailto:wonsuk.lee@etri.re.kr]
> *Sent:* Thursday, October 6, 2016 7:25 AM
> *To:* Streif, Rudolf
> *Cc:* public-automotive
> *Subject:* RE: Cheching the schedule of FPWD for vehicle signal server
> spec
>
>
>
> Rudi.
>
> CfC doesn’t need to have a phone call. Typically an email is as usual for
> this. It’s an official process for gathering feedbacks from WG members
> whether they think current editor’s draft is enough to be published
> official W3C FPWD. Refer to [1]. It’s example for CfC from System
> Applications WG. We can use a same sentence with small changes like
> specification name, duration, etc.
>
>
>
> Anyway I think it would be great if you or peter would send the CfC email
> to the group!
>
> Thanks!
>
>
>
> [1] https://lists.w3.org/Archives/Public/public-sysapps/2014Oct/0030.html
>
>
>
> Kind regards,
>
> Wonsuk.
>
>
>
> *From:* Streif, Rudolf [mailto:rstreif@jaguarlandrover.com]
> *Sent:* Wednesday, October 05, 2016 9:39 PM
> *To:* 이원석 <wonsuk.lee@etri.re.kr>
> *Cc:* public-automotive <public-automotive@w3.org>
> *Subject:* Re: Cheching the schedule of FPWD for vehicle signal server
> spec
>
>
>
> Hi Wonsuk,
>
> I am out of the office today, Wednesday October 5. Friday would work best
> for me for a short telco.
>
> Thank you,
> Rudi
>
>
>
> On Oct 4, 2016 6:59 PM, "이원석" <wonsuk.lee@etri.re.kr> wrote:
>
> Hi. All.
>
> In the last TPAC meeting we had a consensus to publish the FPWD for
> vehicle signal server spec at 11th October. Because we really want to do
> this before GENIVI AMM meeting in Burlingame. To achieving this, we need to
> have CfC(Call for Consensus) process for the spec as soon as possible.
>
>
>
> Chairs! (Paul, Rudi and Peter)
>
> I guess it would be perfect if you do this with short term CfC today or
> tomorrow!
>
>
>
> Thanks!
>
>
>
> Kind regards,
>
> Wonsuk.
>
> =========================================
>
> *이 원 석** (Wonsuk, Lee) / *Senior Researcher, Ph.D
>
> *한국전자통신연구원 표준연구센터**(Protocol Engineering Center, ETRI)*
>
> Mobile: +82-10-5800-3997   Office: +82-42-860-6104
>
> E-mail: *wonsuk.lee@etri.re.kr <wonsuk.lee@etri.re.kr>*
>
> *http://www.wonsuk73.com/ <http://www.wonsuk73.com/>*, twitter: @wonsuk73
>
> =========================================
>
>
>
>
>
>
>
>
>
> --
>
> *Rudolf J Streif*
>
> System Architect - Open Source Initiative
>
> Open Source Technology Centre
>
>
>
> *M:* +1.619.631.5383
>
> *Email:*  rstreif@jaguarlandrover.com
>
>
> UK: G/26/2 G02 Building 523, Engineering Centre, Gaydon, Warwick, CV35 ORR
>
> US: 1419 NW 14th Ave, Portland, OR 97209
>
> jaguar.com | landrover.com
>
> -------------------
> Business Details:
> Jaguar Land Rover Limited
> Registered Office: Abbey Road, Whitley, Coventry CV3 4LF
>
> Registered in England No: 1672070
>
>
> This e-mail and any attachments contain confidential information for a
> specific individual and purpose.  The information is private and privileged
> and intended solely for the use of the individual to whom it is addressed.
> If you are not the intended recipient, please e-mail us immediately.  We
> apologise for any inconvenience caused but you are hereby notified that any
> disclosure, copying or distribution or the taking of any action in reliance
> on the information contained herein is strictly prohibited.
>
> This e-mail does not constitute an order for goods or services unless
> accompanied by an official purchase order.
>
>
>
>
>
>
>
> --
>
> *Rudolf J Streif*
>
> System Architect - Open Source Initiative
>
> Open Source Technology Centre
>
>
>
> *M:* +1.619.631.5383
>
> *Email:*  rstreif@jaguarlandrover.com
>
>
> UK: G/26/2 G02 Building 523, Engineering Centre, Gaydon, Warwick, CV35 ORR
>
> US: 1419 NW 14th Ave, Portland, OR 97209
>
> jaguar.com | landrover.com
>
> -------------------
> Business Details:
> Jaguar Land Rover Limited
> Registered Office: Abbey Road, Whitley, Coventry CV3 4LF
>
> Registered in England No: 1672070
>
>
> This e-mail and any attachments contain confidential information for a
> specific individual and purpose.  The information is private and privileged
> and intended solely for the use of the individual to whom it is addressed.
> If you are not the intended recipient, please e-mail us immediately.  We
> apologise for any inconvenience caused but you are hereby notified that any
> disclosure, copying or distribution or the taking of any action in reliance
> on the information contained herein is strictly prohibited.
>
> This e-mail does not constitute an order for goods or services unless
> accompanied by an official purchase order.
>
>
>



-- 
*Rudolf J Streif*
System Architect - Open Source Initiative
Open Source Technology Centre

*M:* +1.619.631.5383
*Email:*  rstreif@jaguarlandrover.com



UK: G/26/2 G02 Building 523, Engineering Centre, Gaydon, Warwick, CV35 ORR
US: 1419 NW 14th Ave, Portland, OR 97209
jaguar.com | landrover.com
-------------------
Business Details:
Jaguar Land Rover Limited
Registered Office: Abbey Road, Whitley, Coventry CV3 4LF
Registered in England No: 1672070

This e-mail and any attachments contain confidential information for a
specific individual and purpose.  The information is private and privileged
and intended solely for the use of the individual to whom it is addressed.
If you are not the intended recipient, please e-mail us immediately.  We
apologise for any inconvenience caused but you are hereby notified that any
disclosure, copying or distribution or the taking of any action in reliance
on the information contained herein is strictly prohibited.

This e-mail does not constitute an order for goods or services unless
accompanied by an official purchase order.