Re: [w3c/payment-request] Add payerGivenName + payerFamilyName to PaymentAddress (#480)

@marcoscaceres 
Thank u for telling me this discussion here.

I am native Japanese speaker.
I know there are deep-rooted problems there.

I don't want to consider about the meaning / structure of the name.
Indeed, I think simple specification is good too.

But, In Japan almost all people's names are represented in Kanji character like '山田太郎'.
The name '山田太郎' is composed from family-name '山田' and given-name '太郎'.
Some younger people write it as '山田 太郎' so that we can distinguish which one is the family-name.
But it is not formal representation, Japanese text-book always represent full-name like '山田太郎' without space delimiter.

In-Japan, family is important because family-registration by the law.
Though younger people do not think so anymore.
But there is a long long history and legal system.
These system had introduced from China about a thousand year ago.
So, I think It is common problem in Asian countries.
In Japan, different family-names in a single family is also not allowed by the law.

Some people might wonder what is a problem.
Single full-name fields is enough?
No, because In Japan, almost all system require family-name and given-name. Especially, delivery carrier's system require these fields separatedly.
I can't explain reasonable reason why they use these fields separatedly.
But they uses, and almost all people don't care because it is a common-sence.

Here is an example implementation of Google contacts.
![Screenshot from 2020-08-09 02-10-26](https://user-images.githubusercontent.com/1128403/89739518-5f8cef00-dabc-11ea-83ef-b0b31af0836e.png)

And when I enter these fields, and save it single full-name field is automatically generated like below.
![Screenshot from 2020-08-10 03-26-04-2](https://user-images.githubusercontent.com/1128403/89739590-bdb9d200-dabc-11ea-850f-52c1b65dbabe.png)

I think Google and Apple doing well in this area.
I know it is hard work to defining these feature in standard specification

But i'm glad if I can pass paymentOption object like `{requiredPayerNameFields: ['familyName', 'givenName', 'phoneticFamilyName', 'phoneticGivenName']}`.
Also need to consider about `shippingAddress` too.
In Japan, it is enough. I don't need to require 'middleName' or 'phoneticMiddleName' though other people who uses another locale has diefferent requirements.

Sorry for the long text, and thank you for reading my opinion.

-- 
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/payment-request/issues/480#issuecomment-671089588