[Fwd: Re: RPC protocols and the path forward.]

Forwarding to public-automotive, public-automotive-request used to
subscribe/unsubscribe to the list (for those not in the database for
the group)

Ted Guild <ted@w3.org>
W3C Automotive Lead

Forwarded message 1

  • From: Tobias Oberstein <tobias.oberstein@crossbario.com>
  • Date: Mon, 28 Sep 2020 23:12:14 +0200
  • Subject: Re: RPC protocols and the path forward.
  • To: ted@w3.org, public-automotive-request@w3.org
  • Message-ID: <fd447254-ce35-c94b-4454-c59537742a08@crossbario.com>
> Tobias offered to give this group an overview of WAMP and to take a
> look at our Gen2 effort to give his thoughts on how they may possibly
> merge.
> https://w3c.github.io/automotive/spec/Gen2_Core.html
> https://w3c.github.io/automotive/spec/Gen2_Transport.html

fwiw, I've looked through these 2 specs (and the VSS). anticipating the 
actual wamp presentation, here are my first thoughts on mapping vss/gen2 
to wamp specifically:


but an outright mapping as I understood is not necessarily a goal. 
anyways, might be useful nevertheless ..


a naive question though:

did anyone actually ever implement a working prototype 

did 2 independent prototypes ever talk to each other?

did anyone put on an app developer hat and scrutinized whether the API 
and all that "feels right" (for an app developer)?

^ as in: "rough consensus PLUS working code" ;)

IMO spec authors should both be the first implementors and the first 
users. to make sure, the stuff actually works and fits needs.

Received on Tuesday, 29 September 2020 10:59:38 UTC