- From: Shane McCarron <notifications@github.com>
- Date: Wed, 10 Aug 2016 06:55:38 -0700
- To: w3c/browser-payment-api <browser-payment-api@noreply.github.com>
Received on Wednesday, 10 August 2016 13:56:33 UTC
The spec currently has normative references to two W3C specifications that are not under our control and may not be mature when we want to proceed down the Recommendation track. [POWERFUL-FEATURES] is a reference to the Secure Contexts spec. I have no concerns about our requiring secure contexts, but we should not have a normative reference to this spec unless we are certain it will be mature. An informative reference may be sufficient. [WEBIDL] First we are referring to WebIDL level 1... there are features in level 2 that are pretty interesting, but level 2 is far behind on the W3C Rec Track. In any case, we should be certain we are not using any level 2 features. Also, we should be using their recommended text about IDL Fragment Definitions as defined in https://www.w3.org/TR/WebIDL-1/#referencing . Finally, we should be sure that WEBIDL is on pace to be at least a PR when we proceed to Rec or we will potentially be delayed waiting for that spec to mature. --- 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
Received on Wednesday, 10 August 2016 13:56:33 UTC