Re: Proposal for Remote Procedure Call extensions to VISS.

Hi Magnus,

Thank you for opening this up and letting us take a look, we've been
curious since you introduced it on a call earlier.

To try to quell possible confusion, we are not proposing killing off
Gen2 work and starting over every time something is introduced,
including WAMP. We are learning and leveraging where possible after
careful consideration.

VISS (Gen1) is in production use with a couple auto manufacturers and I
am most interested in hearing about experiences and limitations in
influencing choices going forward with both VISS and Gen2.

VISS is at Candidate Recommendation, should be ready to graduate once
the underlying VSS versioning is worked out to the next and final
stage. It is possible we consider reworking it or probably better
having a second document extending it as some may remain invested in
VISS for a period of time before considering switching to Gen2. 

The needs that encouraged JLR to use RPC should be held up against Gen2
and may influence it.

Encourage people to read in the repo and Magnus to consider what
needs/issues/experiences he can discuss in the abstract on a future
group call.

On Thu, 2020-02-06 at 23:44 +0000, Magnus Feuer wrote:
> All,
> 
> We have been exploring an extended VISS protocol that allows for
> remote procedure calls to be invoked over the same websocket that
> today runs signal pub/sub.  
> Since we believe this extension may be of use to the wider community,
> we would like to explore the possibility of expanding the W3C
> standard accordingly.
> 
> The proposal, and a working sample implementation, can be found at:
> 
> https://github.com/PDXostc/viss-rpc
> 
> All is open sourced under MPLv2.
> 
> This is in no way a completed spec. Things such as nested arguments
> (structs) and callbacks missing, so questions, proposals, and
> criticism would be much appreciated. 
> 
> If we come to an agreement that this is the right way forward I will
> make sure that JLR matures code and documentation as needed to
> integrate them into the W3C standard.
> 
> Regards,
> 
> /Magnus F.
> 
> -------------------
> System Architect Manager
> Jaguar Land Rover
> 
> Email: mfeuer1@jaguarlandrover.com 
> Mobile: +1 949 294 7871
> 
> 
> 
> Jaguar Land Rover North America, LLC
> 1450 NW 18th Ave, Portland, OR 97209
> -------------------
> 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 Automotive Lead
https://www.w3.org/auto