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

I don't have a problem with this *specific* change.  Two comments:

First, we should carefully identify requirements on the user vs. requirements on the implementor.  When writing tests, we want to focus on the requirements on the implementor.  Arguably, requirements on anyone other than the implementor in a spec are sort of useless.  But we seem to do it, so...

Second, I note that a lot of specs seem to rely upon the WebIDL to define things it was never meant to do.  Prose that explains the *why* of the interface is just as important as the structured WebIDL that defines the *what* of the interface.  So, while this particular data is not important in that we are not losing the "why" of these parameters, let's try to keep it in mind.

Thanks for listening!

-- 
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#issuecomment-239540648