Not really. I think #10 is somewhat redundant because the **algorithms** are already defined in the various JWT, JWE specs. This concerns mapping response data to claims because JWT's contain claims, not just a raw JSON object. The example suggests that each data element in the response will be stored as a claim. Another approach would be a single claim that contains the whole response as a single JSON encoded object. Different payment method specs could define their own approach to this OR we could register a standard claim identifier(s) (there is a registry for these) which maybe favours the latter approach. -- 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-393357838
Received on Thursday, 31 May 2018 00:03:15 UTC