[Question] Impact of changing `$id` of SchemaStore schemas (_not_ `catalog-schema.json`)

[hyperupcall]

Hey all,

Most of you probably are aware that at SchemaStore, we recently changed our hosting from something custom to GitHub Pages. As a part of that canonical URLs were updated from json.schemastore.org/<schema>.json to www.schemastore.org/<schema>.json. Naturally, there are redirects that redirect the json subdomain to the www subdomain.

There has been thoughts about transitioning the $id from something like, say, json.schemastore.org/ava.json to www.schemastore.org/ava.json. And, making all the $ids consistent (some link to rawgithubusercontent or don't have a .json extension). We won't be changing the $id of catalog-schema.json anytime soon especially in light of the recent incident. But I wanted to determine if/how this would affect the project in any other way.

To that point, I checked the code that caused #799, and I'm not amazing at Rust, but it didn't look like an error from JSON Schema specific validation, but instead a custom value check specific to the catalog-schema.json schema. Many schemas get refactored quite a bit, so it's not always guaranteed that JSON Schemas always have a particular JSON Schema pointer fragment, or that certain properties have certain values. Not to long ago, most schemas did not even have an $id property, so if we've able to further improve the consistency and quality of schemas without breakage that would be great!.