...
- W3C Blog post "HTTPS and the Semantic Web/Linked Data", 20 May 2016 (gist: keep writing “http:” and trust in infrastructure and software to advance)
- Harry Halpin: "Semantic Insecurity: Security and the Semantic Web", October 2017
More observations/inquiries results
- (gist: switch now to https it's not too late yet and the web will be more secure immediately)
- 2017 "The use of https: IRIs on the semantic web" thread on semantic-web@w3.org (about https in vocabulary URI schemes in particular, gist: strong tendency to go for https)
- Discussion 2015 in the W3C Web Annotation Working Group (gist: some statements for "never to use https URIs as identifiers" but discussion closed down for other, formal reasons)
- W3C Design Issues, Tim Berners-Lee "Web Security - TLS Everywhere, not https: URIs", 2015 (gist: the "s" breaks the web, use HTTPS but don't change the URI prefix)
- Wikidata has a 301 redirect from http to https URIs in place but retains http URIs as "Concept URIs", i.e. in RDF data. Discussion page of the Wikidata community 2017-2018 (gist status January 2019: no change to https URIs, just a 301 redirect. Possibly more due to the fact that the discussion subsided rather than an active decision)
More observations/inquiries results
- Wikidata has a 301 redirect from http to https URIs in place but retains http URIs as "Concept URIs", i.e. in RDF data.
- schema.org vocabulary retains http in the URIs, has a 301 redirect from http to https URIs and a triple in the RDF data connecting the two with schema:sameAs, e.g.
schema:CreativeWork schema:sameAs <https://schema.org/CreativeWork>
. (https://schema.org/CreativeWork.ttl, Status 2019-02-01)