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

> I don't believe the actual data consumed by libaddressinput has any explicit license (https://groups.google.com/forum/#!msg/libaddressinput-discuss/kvhArVA2KEQ/jnz1qvEyPR8J)

That is correct.

> so it's not as permissive as the client library makes out. 

Sorry about that.

> I would love to see that data released and/or the license position clarified.

 I will prod the data maintainers to put a proper license on it.

> [not] available in a public dump

The (unlicensed) data is available for browsing from https://i18napis.appspot.com/address. Chrome loads the same data in bulk from https://i18napis.appspot.com/ssl-aggregate-address/, for example, the California data is in https://i18napis.appspot.com/ssl-aggregate-address/data/US/CA. 

Keep in mind that i18napis.appspot.com does not have an SLI. Do not rely on it being there all the time or supporting unlimited QPS.

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