Re: Vehicle Signal Specification

On Fri, 2016-05-20 at 12:55 +0000, Volker Fricke wrote:
> Hi Rudolf and all,
> 
> I like the concept of deriving the vehicle signals from GENVI VSS
> towards W3C auto runtime. 
> 
> I guess from W3C perspective collaboration with GENVI is quite
> important for this close integration within the vehicle. But I guess
> we should also promote the W3C auto runtime to other in-vehicle
> platforms, like QNX and others, right? 

Hi Volker,

I very much agree.  While we have great interactions with Genivi, in
order for standards to be successful they need broader perspective.

QNX was engaged quite some time ago but has since fallen off and may
still lurk and monitor these discussions.  Last I spoke with them they
were a mix of HTML5 and QT, partially implementing our earlier work.
Now that we are switching to a service approach I will reach out to
them again as it is beneficial to both front end platforms.

A few of us had a call with Auto Grade Linux earlier this week about
getting more involved in W3C, VSS and their start of an effort around
web sockets/service.  It went favorably and hopefully will progress
further.

If anyone has contacts with those involved in other platforms we should
be trying to engage, please introduce me to them.
 
> This would mean, that the REST server interface between the W3C auto
> runtime with JS has to be implemented by the other in-vehicle
> platforms 
> 
> Mit freundlichen Grüßen / Kind regards
> 
> Volker Fricke
> 
> Technical Relations Executive, Connected Vehicle, eMobility, C-ITS
> IBM Technical Relations Europe
> 
> Member of IBM Technical Expert Council Central Region - An affiliate
> of IBM Academy of Technology and Gesellschaft für Informatik e.V.
> Phone: +49-7031-16-2174  IBM Deutschland Management &
> Business Support GmbH 
> Mobile: +49-177-2886289  IBM Allee 1
> Email: vfricke@de.ibm.com  71139 Ehningen
> LinkedIn Twitter  Germany
> IBM Deutschland Management & Business Support GmbH / Vorsitzende des
> Aufsichtsrats: Martin Jetter
> Geschäftsführung: Martina Koederitz (Vorsitzende), Susanne Peter,
> Norbert Janzen, Dr. Christian Keller, Ivo Koerner, Markus Koerner
> Sitz der Gesellschaft: Ehningen / Registergericht: Amtsgericht
> Stuttgart, HRB 24938
> 
> 
> 
> 
> 
> From:        "Streif, Rudolf" <rstreif@jaguarlandrover.com>
> To:        public-automotive <public-automotive@w3.org>
> Cc:        Magnus Feuer <mfeuer1@jaguarlandrover.com>
> Date:        19.05.2016 01:17
> Subject:        Vehicle Signal Specification
> 
> 
> 
> Colleagues:
> 
> We have been discussion the Vehicle Signal Specification (VSS) as the
> basis for the data structure for our new web services approach to
> provide access to vehicle data and allow control of various vehicle
> functions from a managed runtime, web runtime, and/or web browser:
> 
> 
> (The slide is from a deck I presented at the Future Connected Cars
> Conference in Santa Clara last week.)
> 
> We have now published the first iteration of the VSS on GitHub [1]
> for review and commenting. The specification is modeled after actual
> signals from CAN bus databases used by JLR. The current iteration
> contains about 180 signals which we expect will grow to about 500
> signals with the coming iterations.
> 
> You can easily see that because of the sheer number of signals and
> controls, a dynamic approach for the API based on services and JSON
> data structures makes very much sense.
> 
> The hierarchical approach with signal paths also naturally lends to
> grouping of signals which is important for subscription.
> 
> For example a door has multiple signals:
> body.door.0.left.locked
> body.door.0.left.open
> body.door.0.left.child_lock
> body.door.0.left.window_position
> body.door.0.left.curtain_position
> You can now group signals using wildcards:
> body.door.0.left.*       (all signals of the left door of the first
> row)
> body.door.0.*            (all signals of all doors of the first row)
> body.door.*              (all signals for all doors)
> body.*                   (all body signals)      
> And equally using "in between" wildcards:
> body.door.0.*.open       (open status of all doors in the first row)
> body.door.*.left.open    (open status of all doors on the left side
> of the vehicle)
> body.door.*.*.open       (open status of all doors on all sides of
> the vehicle)
> body.*.*.*.open          (open status of anything that provides it
> e.g. doors, hood, trunk, moon roof, filler cap, ...)
> 
> We invite your feedback and consideration.
> 
> Best regards,
> :rjs
> 
> [1] https://github.com/GENIVI/vehicle_signal_specification
> 
> 
> -- 
> 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.
> 
> 
-- 
Ted Guild <ted@w3.org>
W3C Systems Team
http://www.w3.org