Re: Charter bug: The NASCAR/WAYF problem

On 2014-12-02 14:20, David Ezell wrote:
> Anders Rundgren wrote:
>> The charter doesn't mention the NASCAR/WAYF problem
> Chaals wrote wrote:
>>> The tasks that the Interest Group will undertake include:
>>>
>>> Identification of problems, barriers and challenges that currently exists or may appear in the domain of Web >>Payments...
>> Seems to be adequate, given that it is a clearly recognised problem.
> More to the point, the charter mentions examples of problems, but gives instructions as above.  Just because something doesn't appear as an example doesn't mean it's out of scope.  Considering any payment use case is within the scope of the charter.

Although I don't have full information here, I have a feeling that for example Apple Pay and Google Wallet didn't address this problem because they didn't have to.  We are in another situation which is why I'm raising a warning flag here.

Anders

>
> So I don't see a charter bug.
>
> Best regards,
> David
>
>
>
> -----Original Message-----
> From: Anders Rundgren [mailto:anders.rundgren.net@gmail.com]
> Sent: Tuesday, December 02, 2014 3:41 AM
> To: Web Payments CG; public-webpayments-comments@w3.org
> Subject: Charter bug: The NASCAR/WAYF problem
>
> The charter doesn't mention the NASCAR/WAYF problem:
> http://www.w3.org/2014/04/payments/webpayments_charter.html
>
> Unfortunately it's a core issue for *distributed* web-payments.
>
> To date all efforts coming up with a standard for finding out where your home-base is have (in practice) failed.
>
> Cheers,
> Anders
>
>
>
> ________________________________
> This electronic message, including attachments, is intended only for the use of the individual or company named above or to which it is addressed. The information contained in this message shall be considered confidential and proprietary, and may include confidential work product. If you are not the intended recipient, please be aware that any unauthorized use, dissemination, distribution or copying of this message is strictly prohibited. If you have received this email in error, please notify the sender by replying to this message and deleting this email immediately.

Received on Tuesday, 2 December 2014 14:05:33 UTC