Re: VISS / ViWi contrast and review at AGL

I read the blog and here is my understanding of the table.

Category VISS ViWi
Filtering & Aggregation support Filtering on node (not possible on several
nodes or branches) Describe a protocol (provides a way for multiple node
filtering and aggregation)
Privacy Model (Private vs Public) Access restrictions to signals Ability to
specify custom signals
Data Exchange method between W3C Server and Native OS/Platform Use high
level development languages
RESTful HTTP calls
W3C Server Deployment Model One big Server that handle requests Stateless
Additional Filtering options Filtering Filtering, sorting
Post deployment extensibility Static signals tree not extensible [VSS] Use
JSON objects to communicate
Ease of "Resource" (as in URI) resolution
(how to resovle a 'GET' to an actual resource) Use of AMB ? Identification
of resources may be a bit heavy going using UUID
Incomplete - Maybe Transport layer protocol? Use of Websocket
Sincerely,
Sanjeev BA


On Fri, Jun 29, 2018 at 8:19 AM Streif, Rudolf <
rstreif@partner.jaguarlandrover.com> wrote:

> 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.
>
>