Mappings are good. :-) The usual practice for JWT claims is to define atomic entities (e.g., phone_number, given_name). This enables re-use (in fact, we might want to re-use some of the OAuth fields). Might other specs want to reuse cardNumber and cardSecurityCode and such? -- 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/webpayments-crypto/issues/13#issuecomment-394498381
Received on Monday, 4 June 2018 21:02:59 UTC