Re: [w3c/webpayments-method-identifiers] [SECURE-CONTEXTS] should be a normative rather than informative reference (#29) from Marcos Cáceres on 2017-04-27 (public-webpayments-specs@w3.org from April 2017)

From: Marcos Cáceres <notifications@github.com>
Date: Wed, 26 Apr 2017 20:34:36 -0700
To: w3c/webpayments-method-identifiers <webpayments-method-identifiers@noreply.github.com>
Cc: Subscribed <subscribed@noreply.github.com>
Message-ID: <w3c/webpayments-method-identifiers/issues/29/297602316@github.com>

I don't think we actually want this link at all. It's used for "Potentially Trustworthy URLs", which leads to: 

> If origin’s scheme is either "https" or "wss", return "Potentially Trustworthy".

And I don't think we want people using "wss://" URLs for identifiers. We might as well just do a scheme is "https" check instead.  

-- 
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/webpayments-method-identifiers/issues/29#issuecomment-297602316

Received on Thursday, 27 April 2017 03:35:35 UTC