Migrate to vecorel.org

Author: m-mohr

README.md

@@ -4,8 +4,8 @@ As Vecorel is targeting multiple encodings, there's no single solution for valid
 We must define our own validation vocabulary, based on the Vecorel SDL [data types](datatypes.md).
 Nevertheless, Vecorel SDL can be translated into JSON Schema.
 
-- Schema identifier: <https://vecorel.github.io/sdl/v0.2.0/schema.json>
-- [Metaschema](https://vecorel.github.io/sdl/v0.2.0/schema.json) (as JSON Schema)
+- Schema identifier: <https://vecorel.org/sdl/v0.2.0/schema.json>
+- [Metaschema](https://vecorel.org/sdl/v0.2.0/schema.json) (as JSON Schema)
 
 ## Vocabulary
 

schema/schema.json

@@ -1,12 +1,12 @@
 {
   "$schema": "https://json-schema.org/draft/2020-12/schema",
-  "$id": "https://vecorel.github.io/sdl/v0.2.0/schema.json",
+  "$id": "https://vecorel.org/sdl/v0.2.0/schema.json",
   "type": "object",
   "required": ["$schema", "properties"],
   "properties": {
     "$schema": {
       "type": "string",
-      "const": "https://vecorel.github.io/sdl/v0.2.0/schema.json"
+      "const": "https://vecorel.org/sdl/v0.2.0/schema.json"
     },
     "required": {
       "type": "array",