Use HTTPS for schema links

[adamquaile]

No description provided.

[handrews]

@adamquaile thanks for the PR!

For the meta-schemas, the URIs, including the scheme, serve primarily as identifiers and only secondarily as locators. For the next draft, I want them to be exclusively identified and available over HTTPS (which was only available to json-schema.org recently for absurdly complicated historical reasons documented elsewhere).

@Relequestual @awwright changing these links doesn't change the $id in the meta-schemas, but does kind of imply that the https: locations are canonical-ish. Is this OK?

[Relequestual]

Yeah I don't see any issue with this. Please go ahead.

[awwright]

Ideally we'd be able to specify access/security requirements in DNS without changing the URIs/URLs. It's doubtful this is going to be widely supported in the near future. The only other concern is breakage. In theory clients will be able to understand it's the same resource, just at different URIs. In practice, they don't do this either. Go ahead if you don't see a major problem, though.

…

On Fri, Sep 28, 2018, 01:39 Ben Hutton ***@***.***> wrote: Yeah I don't see any issue with this. Please go ahead. — You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub <#239 (comment)>, or mute the thread <https://github.com/notifications/unsubscribe-auth/AAatDbieWYj7Tk8mQN7jHGe6VIITZukBks5ufeBQgaJpZM4W6O1v> .

[Anthropic]

Given approvals above, I don't see any reason to delay this, if someone reports an issue we can look at it further then if it happens.