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

It seems to me that both sides are making good points: 1.) @adamroach is saying that if users want to use the careOf field, they shouldn't have to figure out how to shoehorn it into one of the other fields (e.g. recipient). But this is mostly on a user level, not a spec level. 2.) @andyst is saying that careOf doesn't belong in the spec itself and it seems that there is strong support for that being true.

I think that both use cases can be accommodated. It's already true that the form fields that users see do not necessarily reflect what is in the underlying spec (e.g. most residents of the US would not know what to fill in on a region field, they would expect to see "State"). So I think we can remove "careOf" from the actual specification, and let it be an example of localizing a form.

So as an implementation decision, the browser could show a form that looked like:

```
<form>
 
  <label>Recipient name:</label>
  <input type="text" name="recipient-name" />

  <label>careOf</label>
  <input type="text" name="care-of" />

</form>
```

But when the address gets normalized to the underlying spec format, it would look like:

```
{
  "recipient": "Zach Koch \n careOf Alice Bob"
}
```

Or something like that anyway. :)

-- 
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-246827451