- From: marqh via GitHub <sysbot+gh@w3.org>
- Date: Mon, 22 Jul 2019 14:02:00 +0000
- To: public-sdwig@w3.org
Hello @cportele I am interested in: > * Identifiers should be HTTPS URIs and encouraging a bit more information/discussion about it, if I may. Is this ticket an appropriate place for this? There is widespread use of HTTP identifiers. Many existing vocabularies are published as HTTP URIs A cursory search reveals some fairly recent debate on the issue, such as * https://www.w3.org/blog/2016/05/https-and-the-semantic-weblinked-data/ * https://stackoverflow.com/questions/44883339/preferring-https-iris-on-the-semantic-web * https://lists.w3.org/Archives/Public/semantic-web/2017Jul/0042.html I wonder whether this issue has a degree of nuance which is not well covered by: > Identifiers should be HTTPS URIs e.g.: * how strong is 'should'? * is this different for new vocabularies not yet published and vocabularies in use? * is it advisable / strongly advisable to ensure that http://{thing} and https://{thing} resolve to the same thing? (This is critical for me, more important than 'use https now') * what happens if the https URI returns a security violation (It happens: I guess many of us have experienced this, as a resource requestor and as a service maintainer) If the target for this statement is a Best Practice guide, I wonder whether some nuanced commentary would be really valuable? thank you marqh -- GitHub Notification of comment by marqh Please view or discuss this issue at https://github.com/w3c/sdw/issues/1085#issuecomment-513804249 using your GitHub account
Received on Monday, 22 July 2019 14:02:02 UTC