- From: Streif, Rudolf <rstreif@partner.jaguarlandrover.com>
- Date: Thu, 28 Jun 2018 16:17:54 -0700
- To: T Guild <ted@w3.org>
- Cc: public-automotive <public-automotive@w3.org>, Fulup Le Foll <fulup@iot.bzh>
- Message-ID: <CANpGCGKWCKeV=qYzVXVXFPsrQfv5c=kCJjsoD5vOkJwPcU=P8A@mail.gmail.com>
Could somebody please explain this table to me? VISSViWi Filtering on node (not possible on several nodes or branches) Describe a protocol Access restrictions to signals Ability to specify custom signals Use high level development languages RESTful HTTP calls One big Server that handle requests Stateless Filtering Filtering, sorting Static signals tree not extensible [VSS <https://github.com/GENIVI/vehicle_signal_specification>] Use JSON objects to communicate Use of AMB ? Identification of resources may be a bit heavy going using UUID Use of Websocket What are the categories that are compared here? :rjs On Tue, Jun 26, 2018 at 7:54 AM, Ted Guild <ted@w3.org> wrote: > As the W3C Auto Working Group is exploring a v2 drawing from VISS and > RSI (ViWi) we were pointed at write-ups done comparing them by AGL. > > I was hoping Fulup can join us for an upcoming call and in the meantime > encourage a wider read by the WG. Please provide reactions and > questions in this mail thread. > > http://docs.automotivelinux.org/docs/apis_services/en/dev/ > reference/signaling/architecture.html#query-and-filtering-language > > http://docs.automotivelinux.org/docs/apis_services/en/dev/ > reference/signaling/high-viwi-architecture.html > > -- > Ted Guild <ted@w3.org> > W3C Automotive Lead > http://www.w3.org > > > -- *Rudolf J Streif* System Architect Oregon Software Technology Center *M:* +1.619.631.5383 *E:* 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 Jaguar Land Rover Limited, Abbey Road, Whitley, Coventry CV3 4LF, UK Registered in England No: 1672070 CONFIDENTIALITY NOTICE: This e-mail message including attachments, is intended only for the person to whom it is addressed & may contain confidential information. Any unauthorised review; use, disclosure or distribution is prohibited. If you are not the intended recipient, please contact the sender by reply e-mail and destroy all copies of the original message.
Received on Thursday, 28 June 2018 23:18:20 UTC