- From: Rob Sanderson via GitHub <sysbot+gh@w3.org>
- Date: Sun, 12 Jun 2016 14:25:40 +0000
- To: public-annotation@w3.org
On reflection, I think this is a normative change. Implementations would need to change their behavior to look for https:// rather than http://. This would affect all existing clients, as the conformsTo list was also part of the CG work, and the entries haven't changed. As the use of the URIs is just as identifiers, and they redirect to HTTPS, I would suggest following the specification and using HTTP like the spec suggests. Otherwise you're creating interoperability problems for no reason. Given we're in feature freeze, I'm tagging `wontfix`. Sorry! -- GitHub Notification of comment by azaroth42 Please view or discuss this issue at https://github.com/w3c/web-annotation/issues/296#issuecomment-225437893 using your GitHub account
Received on Sunday, 12 June 2016 14:25:43 UTC