Re: [w3c/payment-request] Add phonetic name as one of `PaymentAddress` properties (#837)

I appreciate your work on improving PaymentRequest API.

In Japan, almost all names are represented in Kanji Character.
And, there is no rule to leaving space between family name and given name though some people do.
So, it is difficult to distinguish which is the family name or given name parts in problematically.

So Japanese EC sites has `familyName` and `givenName` fiels sepratedly.
These complex form reducing conversion ratio.
So, I think it makes sence adding those fields in PaymentRequest API especially in Japan.

I wonder if consider about adding `family Name`, `givenName`, `middleName`, `phonetic FamilyName`, `phoneticGivenName`, `phoneticMiddleName` fields separately.

Please tell me if I need to make a another issue for this.

Note: Proprietary ApplePay API implementation has `familyName` and `givenName` fields separatedly for paymentAddress and shippingAddres. I'm not sure about any other locale implementation. But it seems there is no 'middleName' fields.
But it is not a problem because almost all Japanese people has no middle name and almost all EC sites in Japan has no fields corresponding to `middleName`.

-- 
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/837#issuecomment-670956802