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

I'm sympathetic to that argument. I wrote it like this for two reasons:

1. It was awkward to find the words to say "if a spec says to convert it, then do, and also if a spec has `steps to validate the converted data`, do those too."
2. For SPC, I was actually hoping to normalize the data as part of 'conversion' (see what is currently step 5 of https://w3c.github.io/secure-payment-confirmation/#sctn-steps-to-check-if-a-payment-can-be-made), which means that it takes on a meaning beyond the basic WebIDL meaning.

I'm happy to poke at the wording here myself, but interested in your thoughts on #2 :). (A reasonable counter-argument is to point out that we're likely to move away from the PR API for SPC anyway, and so it shouldn't be bent to make SPC work better!)

-- 
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/pull/977#discussion_r754630634