- From: Marcos Cáceres <notifications@github.com>
- Date: Mon, 03 Apr 2017 20:18:37 -0700
- To: w3c/browser-payment-api <browser-payment-api@noreply.github.com>
- Cc: Subscribed <subscribed@noreply.github.com>
Received on Tuesday, 4 April 2017 03:19:11 UTC
> I know! I sympathize, but this argument comes up in every group that is developing technical documentation related to payments. That kinda makes my point tho. If it's already known to cause confusion, we should avoid it. What we could do is say at the start of the spec: "In this spec, we avoid the use of the common terms 'payer' and 'payee' because they are known to cause confusion: we instead use **merchant** in place of 'payee' and 'end user' in place of 'payer'. " or something like that. > It's standard terminology that we SHOULD adopt to be consistent with others. But I, and probably others, don't want to be Googling for which is which every time we read the spec. Let's be rebels and use something different! 🏍 😎 -- You are receiving this because you are subscribed to this thread. Reply to this email directly or view it on GitHub: https://github.com/w3c/browser-payment-api/issues/493#issuecomment-291382714
Received on Tuesday, 4 April 2017 03:19:11 UTC