- From: Jörn Hees <j_hees@cs.uni-kl.de>
- Date: Thu, 27 Apr 2017 20:17:41 +0200
- To: Linking Open Data <public-lod@w3.org>
> On 27 Apr 2017, at 16:57, Stephane Fellah <fellahst@gmail.com> wrote: > > Please keep in mind that in the context of Linked Data, the use of HTTP scheme in URI is just fine and actually recommended, as URI should be considered only as globally unique names identifying a concept. Naming and addressing are two different things. Here the excellent blog for Norman Walsh that explains the difference. https://norman.walsh.name/2006/07/25/namesAndAddresses. +1 ... but also throwing HSTS in the mix... As others said: if you can, don't change the URIs, they are identifiers, try not to break simple syntactic equivalence checks! Instead serve them under http prefix, redirect requests with HSTS header to https, where you serve the old docs (with the old http URIs). On client side however, be aware that you can't assume that all hosters get this right: URIs, IRIs, http, https, relative URIs, basenames, protocol independent URIs, xml-escaping, utf8, ..., even most of us will have done it wrong in some place. For new things let's hope https stays alive for a while... Or just not take it so seriously if old things break? ;) Best, Jörn
Received on Thursday, 27 April 2017 18:18:12 UTC