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

@stephenmcgruer commented on this pull request.



> +          An IDL type that defines the data the <a>payment method</a> expects
+          to receive in the {{PaymentMethodData/data}} member of the
+          {{PaymentMethodData}}. If not specified for a given payment method,
+          no conversion to IDL is done and the payment method will receive
+          {{PaymentMethodData/data}} as JSON.

Done.

> +          How a <a>payment method</a> validates the {{PaymentMethodData/data}}
+          member of the {{PaymentMethodData}}, after it is converted to the
+          <a>payment method additional data type</a>. If not specified for a
+          given payment method, no validation is done.

Done.

> @@ -855,10 +880,11 @@ <h2>
               "ECMASCRIPT#sec-json.parse">JSON-parsing</a> the second element
               in the |paymentMethod| tuple.
               </li>
-              <li>If required by the specification that defines the
-              |identifier|, then [=converted to an IDL value|convert=] |data|
-              to an IDL value of the type specified there. Otherwise,
-              [=converted to an IDL value|convert=] to {{object}}.
+              <li>If the specification that defines the |identifier| specifies a
+              <a>payment method additional data type</a>, then [=converted to an

Done.

> @@ -148,6 +148,30 @@ <h2>
         method.
         </li>
       </ul>
+      <p>
+        A payment method defines:
+      </p>
+      <dl>
+        <dt>
+          <dfn>Payment Method additional data type</dfn>

Done.

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

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