Re: Web Payments Task Force

On Tue, 2017-06-20 at 11:40 -0700, Streif, Rudolf wrote:
> Thank you, Ted.

Thank you for the feedback Rudi.

> Looks good overall. My questions/suggestions:
> 1.2 Topics
> What would be the difference between Tolls and Road Usage?

They are essentially the same and could be collapsed. The mechanism
should be the be same but at least in London is based on OCR instead of
NFC that most tolls use.

https://en.wikipedia.org/wiki/London_congestion_charge

Usage model also varies in that it is time dependent (peak vs off-peak
traffic hours) and as I understand different for electric vehicles not
contributing to the city smog. These may just be treated as conditional
discounts and when the amount is zero the driver should not be
bothered.

I collapsed into a single line.

> Add "Retail PoS (drive through)" to the list (while similar to
> fuel/charge there might be differences in the infrastructure)

Agree with this and discussed these with Ian.

added: Retail Point of Sale (POS) (such as "drive-thru")


Auth is already being taken care of as part of a security initiative in
Web Payments. For shared vehicles we need to think about possibly
storing multiple payment profiles securely on vehicle or retrieve from
cloud and in some cases ensure some are automatically removed when car
is rebooted. That might indeed be distinctly different use case from
what Web Payments WG is working on solving.

s/Intermittent Connectivity/Connectivity/ and using connectivity from
merchant is a possible solution depending on whether the vehicle is
traveling at speed or stationary. The other thought on solution is
making a promise to pay instead of the actual realtime payment which is
how some toll/usage is done presently.

added: Automated payments (e.g., delegation of authority to the vehicle
to make payments)

below related Driver Distractability for broader H2M -> M2M

> Add "Authentication/Authorization" (it kind of goes with "shared
> vehicles" but that is more generic, also includes authorized
> automatic (M2M) payments)
> "Intermittent Connectivity" should be broader "Connectivity" as there
> could potentially be different connectivity solutions used to connect
> to a PoS
> Use case differentiation between H2M and M2M (web payments would
> typically be H2M with human interaction, many vehicle payment use
> cases could be eventually be M2M and fully automated as long as
> authorized
> 
> Thanks,
> :rjs
> 
> On Tue, Jun 20, 2017 at 10:37 AM, Ted Guild <ted@w3.org> wrote:
> > Ian Jacobs (W3C Web Payments Lead, who presented remotely during
> > our
> > F2F) and I have drafted a description of an automotive web payments
> > task force:
> > 
> >  https://www.w3.org/2017/06/automotive-web-payments.html
> > 
> > He shared this with the Web Payments Interest Group teleconference
> > on
> > Monday and we did not have time to discuss on our WG call today. It
> > is
> > a BG item but figured we can share on a WG call.
> > 
> > Feedback and expressions of interest very welcome,
> > 
> > --
> > Ted Guild <ted@w3.org>
> > W3C Systems Team
> > http://www.w3.org
> > 
> > 
> 
> 
> -- 
> Rudolf J Streif
> System Architect - Open Source Initiative
> Open Source Technology Centre
> 
> M: +1.619.631.5383
> Email:  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
> -------------------
> 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 Systems Team
http://www.w3.org