Re: [w3c/payment-request] Editorial: Define a concept for converting and validating .data (PR #977)

@stephenmcgruer commented on this pull request.



> @@ -155,6 +155,15 @@ <h2>
         for payment. Concretely, a payment handler defines:
       </p>
       <dl>
+        <dt>
+          <dfn>Steps to convert and validate payment method data</dfn>
+        </dt>
+        <dd>
+          How a <a>payment method</a> [=converted to an IDL value|converts=] and

Ack, I agree. Coming back to this, I've split conversion and validation back out, and also made them idempotent (i.e., no normalization). This means that SPC will have to continue to normalize in step 5 of https://w3c.github.io/secure-payment-confirmation/#sctn-steps-to-check-if-a-payment-can-be-made, but I think that's fine. (And I very much agree with your concerns about overstepping).

Please take another look :)

-- 
Reply to this email directly or view it on GitHub:
https://github.com/w3c/payment-request/pull/977#discussion_r911036453
You are receiving this because you are subscribed to this thread.

Message ID: <w3c/payment-request/pull/977/review/1024888634@github.com>