[w3c/browser-payment-api] Change “MUST…to be valid” to just “are required” (#236)

There are several instances in the spec of this pattern:

> The following fields MUST be included in a FOO for it to be valid

One problem with those as normative statements is that the spec doesn’t explicitly define what ”to be valid” means or what must happen if an instance of something is found to not be “valid”.

But it doesn’t really matter because those statements are anyway just redundant with the requirements that are already normatively specified in the associated WebIDL definitions.

For example, [the WebIDL for PaymentCurrencyAmount](https://w3c.github.io/browser-payment-api/#paymentcurrencyamount) already normatively specifies the `currency` & `value` fields as `required`, so the normative statement after it that “The following fields must be supplied for a `PaymentCurrencyAmount` to be valid“ is redundant with what’s specified in the WebIDL.

So this PR replaces those redundant normative “The following fields MUST be included in a FOO for it to be valid:” instances with just the non-normative “The following fields are required:”
You can view, comment on, or merge this pull request online at:

  https://github.com/w3c/browser-payment-api/pull/236

-- Commit Summary --

  * Change “MUST…to be valid” to just “are required”

-- File Changes --

    M index.html (8)

-- Patch Links --

https://github.com/w3c/browser-payment-api/pull/236.patch
https://github.com/w3c/browser-payment-api/pull/236.diff

-- 
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/browser-payment-api/pull/236