Re: [w3c/browser-payment-api] Normative References (#227)

I've updated the spec to refer to WebIDL-2, since we are actually using some newer WebIDL capabilities. I'm not too worried about this normative reference - we have been moving API specifications with IDL dependencies to Recommendation for a while despite dependencies on WebIDL-1, which is in the process of transitioning to Proposed Rec. I anticipate that we will need to follow the same processes for WebIDL-2.

The spec already used the language for a conforming user agent (the second part of the #referencing) link. I compared this to other API specifications and this seems sufficient. If you want to add more, please propose specific text.

I updated the [POWERFUL-FEATURES] reference to [SECURE-CONTEXTS] now that SpecRef supports this name. I also changed this to an informative reference since the only mention of "secure context" is in a note (except for the `[SecureContext]` attribute, which is defined in WebIDL.

I hope #259 resolves this issue. If you don't believe so then please reopen and provide concrete text that we can add to close it.

-- 
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/issues/227#issuecomment-247521820