Re: [w3c/browser-payment-api] Request to remove 'careOf' field from the PaymentAddress interface (#244)

I'm sympathetic to the issues you describe regarding interfacing with existing libraries.

The fact remains that users must make use of c/o in certain circumstances (I sent Zach a reference to USPS guidelines referring to some of these circumstances, but can't find them at the moment). We can either push the complexity of shoehorning the c/o value into some appropriate place to the user (which is confusing and frustrating for the user), or we can require applications to perform this mapping (e.g., by appending "c/o Name" to the name fields, or prepending it to the company fields).

So, we're really discussing whether to push this complexity on to users, or to push it onto app developers. At which point I would turn to <https://www.w3.org/TR/html-design-principles/#priority-of-constituencies> to break the tie.

-- 
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/244#issuecomment-245611761