Re: VISS / ViWi contrast and review at AGL

Could somebody please explain this table to me?

Filtering on node (not possible on several nodes or branches) Describe a
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
<>] 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?


On Tue, Jun 26, 2018 at 7:54 AM, Ted Guild <> 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.
> reference/signaling/architecture.html#query-and-filtering-language
> reference/signaling/high-viwi-architecture.html
> --
> Ted Guild <>
> W3C Automotive Lead

*Rudolf J Streif*
System Architect
Oregon Software Technology Center

*M:* +1.619.631.5383

UK: G/26/2 G02 Building 523, Engineering Centre, Gaydon, Warwick, CV35 ORR
US: 1419 NW 14th Ave, Portland, OR 97209 |

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