Re: [w3c/browser-payment-api] Currency amount (#101)

@adrianhopebailie,

> On that basis I have edited the PR to revert to "value" instead of "amount" and request that the editors merge the PR as is (which reflects the previous consensus of the group and a minor terminology change...

I don't consider it a minor terminology change (for the reasons stated in this thread); the consensus of the group and the resolution was to use "amount". If it had said "value", it wouldn't have gotten my vote. See the use of "amount" in: https://github.com/w3c/webpayments/issues/57

In any case, I'm not going to raise an objection that gets in the way of FPWD here, but we should accurately reflect the consensus of the group. We can then debate changing it further. As I said, I'm "ok" with "amount" (it got my vote), because I think it's "sufficiently specific" in this case. But if "amount" is problematic here, I would propose "monetaryValue" rather than the ultra-generic "value".

It's true that I have a general concern that we're being too cavalier in how we go about naming terms in data that is intended to be transported as JSON and shared between various actors (user agents, Payment Apps, etc). Often we end up picking pretty good terms incidentally anyway -- but we should be more deliberate in respecting best practices like the Rule of Least Power.

I don't have any other specific terms that I believe need further bikeshedding right now, but I do hope people will be more mindful of this and if there are other terms that need addressing I (and hopefully others) will bring them up in separate issues in the future.

---
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/pull/101#issuecomment-204642461