Re: RSI call 2017-08-30

Thanks Rudi.

While you might be on the next RSI call on Wednesday (6pm PDT) I doubt
we'll have Patrick Bartsch at 3am CET. I want to discuss with you two
the rationale for RSI keeping paths to four (if I recall correctly)
levels, performance or other issues in expanding it and whether the VSS
tree can be restructured somewhat to reduce the depth. It would be
tremendous if we can get these aligned or at least greatly simplify any
mapping between them.

Perhaps we can have this on the agenda for 20 September RSI if 8am PDT
isn't too early. Any materials giving perspective that Patrick can send
in advance would be helpful. I believe he is going to raise a GH issue
and perhaps pull request to add a JSON structure to RSI draft.

https://github.com/w3c/automotive-bg/issues

On Wed, 2017-09-06 at 09:25 -0700, Streif, Rudolf wrote:
> Hi Ted et all,
> 
> Thank you. This sounds good.
> 
> Unfortunately, we won't be able to get much of Magnus Feuer's
> attention for VSS because he's extremely busy with another project.
> However, while Magnus started VSS, I have been the official
> maintainer for it pretty much from the beginning. Let's talk what we
> want to accomplish.
> 
> :rjs
> 
> On Tue, Sep 5, 2017 at 6:16 PM, Ted Guild <ted@w3.org> wrote:
> > Last week Patrick Bartsch, Patrick Luennemann, Philippe Robin and I
> > were on the RSI call. Below are some brief notes. 
> > 
> > The next call is scheduled later today for the Asia/Europe friendly
> > time. We had a WG call that just ended and surveying the Asian
> > contingency present it seems only Wonsuk may attend. We might want
> > to
> > look at refining the schedule based on attendance.
> > 
> > There has been some evolutions inside of VW, of particular note
> > which
> > Patrick B will create as issues on github are a JSON structure that
> > brings it closer to VSS and a new security model.
> > 
> > They still have are trying to keep the depth of the path limited
> > (four
> > levels if I recall correctly) compared to VSS' tree structure. We
> > should meet with Magnus Feuer from JLR who has been the primary
> > curator
> > of Genivi VSS to see whether and how much restructuring would make
> > sense, reasons for keeping depth limited etc.
> > 
> > We want more editors from more organizations involved in RSI.
> > 
> > VW might be able to open up more domains, eg notifications after
> > they
> > see this advancing.
> > 
> > Desire to move RSI along as a spec, in particular the protocol
> > piece
> > followed by the domains. We can publish it as a Business Group
> > Report
> > which is referenceable and a lighter weight spec, not a full W3C
> > Recommendation. We need to recharter the Working Group by the end
> > of
> > the year for RSI, LBS and any other domains we feel we can take on
> > at
> > this point.
> > 
> > 
> > --
> > Ted Guild <ted@w3.org>
> > W3C Systems Team
> > http://www.w3.org
> 
> 
> 
> -- 
> Rudolf J Streif
> System Architect - Open Source Initiative
> Open Source Technology Centre
> 
> M: +1.619.631.5383
> Email:  rstreif@partner.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.
> 
-- 
Ted Guild <ted@w3.org>
W3C Systems Team
http://www.w3.org