- From: makxdekkers via GitHub <sysbot+gh@w3.org>
- Date: Fri, 29 May 2020 16:21:44 +0000
- To: public-dxwg-wg@w3.org
> The [Australian Government Linked Data WG](http://www.linked.data.gov.au) will likely switch from HTTP to HTTPS for all PID URIs within a couple of months. As far as I am concerned, 'switching' from HTTP to HTTPS for PIDs really means you're minting new URIs and breaking the persistence of these HTTP URIs. You could of course make the statement, as I have seem some people do: "HTTP and HTTPS URIs are equivalent". That may be the case but identifier `http://somedomain/something` is different (for character-by-character compare) from `https://somedomain/something`. So if you are comparing identifiers, you will need a piece of software that says "_if the strings are not the same but the fifth character is an 's' and the rest is the same, treat them as the same_", or maybe even "_compare the strings after '//'_", or have statements like `http://somedomain/something owl:sameAs https://somedomain/something`. So what if a new protocol comes along, and it is decided that HTTPS was not such good idea after all, are users of the PIDs going to be forced to change their compare routines again and again? Where's the persistence in that? -- GitHub Notification of comment by makxdekkers Please view or discuss this issue at https://github.com/w3c/dxwg/issues/1213#issuecomment-636062362 using your GitHub account
Received on Friday, 29 May 2020 16:21:46 UTC