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

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

From: Rouslan Solomakhin <rouslan@google.com>
Date: Fri, 2 Sep 2016 14:21:55 -0700
Message-ID: <CAMMzaWFm4btU=KBzBMZPQDxQ=N7yrpaa-2RW6jzB=ZDJDjnSVQ@mail.gmail.com>
To: r12a <ishida@w3.org>
Cc: Steven Atkin <atkin@us.ibm.com>, www-international@w3.org, Web Payments Working Group <public-payments-wg@w3.org>
On Fri, Sep 2, 2016 at 9:56 AM, r12a <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 ?


> 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.
Received on Friday, 2 September 2016 21:22:27 UTC

This archive was generated by hypermail 2.3.1 : Friday, 2 September 2016 21:22:28 UTC