Re: [w3c/browser-payment-api] Write-up proposal for shipping address fields (#6)

Via email @rsolomakhin said:

> We have two proposals at the moment:

> 1. OASIS xAL based names: regionCode, administrativeArea, locality, etc.
> 2. IETF ECML based names: countryCode, stateProvince, city, etc.

> I've been working with OASIS names in Chrome, but changing to IETF would not be a big deal for Chrome.

We need to get some finality on this to allow implementers to start experimenting with the API.

As long as they cater for all jurisdictional peculiarities (which seems likely as they are both international standards) I'd recommend we use whatever the browser vendors are most familiar with as this will allow them to leverage the stored addresses they already have to streamline this data collection process.

I also assume that the vendors feel comfortable with rendering an appropriate input control for different jurisdicitions and mapping this back to this standardized return format.

## PROPOSAL

We have heard that **OASIS xAL** based names are already used by one browser vendor so I propose we standardize on these and PR is submitted to the API spec that expresses this format using WebIDL.

---
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/6#issuecomment-212904856