W3C home > Mailing lists > Public > public-payments-wg@w3.org > September 2016

Re: i18n-ISSUE-214: Improper use of languageCode

From: Nick Shearer <nshearer@apple.com>
Date: Sat, 03 Sep 2016 10:29:15 +0100
Message-id: <A4349CCA-BFC1-4D5A-A726-EC30A43156D4@apple.com>
Cc: r12a <ishida@w3.org>, Steven Atkin <atkin@us.ibm.com>, www-international@w3.org, Web Payments Working Group <public-payments-wg@w3.org>
To: Rouslan Solomakhin <rouslan@google.com>

> On Sep 2, 2016, at 10:21 PM, Rouslan Solomakhin <rouslan@google.com <mailto:rouslan@google.com>> wrote:
> On Fri, Sep 2, 2016 at 9:56 AM, r12a <ishida@w3.org <mailto:ishida@w3.org>> wrote:
> But looking at those examples (which are of course US-centric)
> Sorry about the US-centricity of these examples. This is a problem of many APIs.
> i don't see fields for the level of detail such as `dependentLocality` or `careof`. I wonder how one decides what is the appropriate level of detail.
> This is a problem that is not yet solved. The balance is determined by the needs of your use case. If your use case is "printing a label for a package", then freeform multiline text is OK. If you care only about border-crossing tariffs, then you care only about the source and destination country, placing the rest of the fields into freeform multiline blob. In case of "dependentLocality", this is something that we have observed being used outside of US. For example, Shanghai is such a huge city that a street name and number is not sufficient to uniquely identify an address. So "dependentLocality" is used here to specify a district within Beijing.
> If you are interested in talking about "careOf", can you provide your opinion on https://github.com/w3c/browser-payment-api/issues/244 <https://github.com/w3c/browser-payment-api/issues/244> ?
> Do zip codes in the US not identify the location better than city names?
> In general, zip codes in US are more granular than cities.

There are some cases where the ZIP is not sufficient for calculating taxation rates, because two distinct cities or areas may both have some area inside a specific ZIP.
Received on Saturday, 3 September 2016 09:30:10 UTC

This archive was generated by hypermail 2.3.1 : Saturday, 3 September 2016 09:30:11 UTC