specify full schema URL in index.json

1 files changed, 11 insertions, 11 deletions

diff --git a/index.json b/index.json
index c8dcf9a..1c8ed0b 100644
--- a/index.json
+++ b/index.json
@@ -24,26 +24,17 @@
 
 // Unknown object properties will be ignored. This is for compatibility with
 // possible future revisions of the format.
-
-// Various kinds of objects contain version information. Version is always an
-// array of integers, with major version number being the first array item. When
-// applicable, a version is accompanied by a revision field which contains a
-// positive integer. If versions specified by arrays of different length need to
-// be compared, the shorter array gets padded with zeroes on the right. This
-// means that for example version 1.3 could be given as both [1, 3] and
-// [1, 3, 0, 0] (aka 1.3.0.0) and either would mean the same.
-
 {
     // Once our index.json schema changes, this field's value will change. Our
     // software will be able to handle both current and older formats thanks to
     // this information present in every index.json file. Schemas that differ by
     // the first (major) number are always incompatible (e.g. a Hydrilla builder
     // instance released at the time of 1.2 being the most recent schema version
-    // will not understand version 2.0).
+    // will not understand version 2.1).
     // Schemas that are backwards-compatible will have the same major number
     // and might differ by the second (minor) version number. The third (patch)
     // and subsequent numbers are being ignored right now.
-    "source_schema_version": [1],
+    "$schema": "https://hydrilla.koszko.org/schemas/package_source-1.schema.json",
 
     // Used when referring to this source package. Should be consize, unique
     // (among other source package names) and can only use a restricted set of
@@ -93,6 +84,15 @@
 	    // allowed to contain arbitrary unicode characters (within reason!).
 	    "long_name": "Hello Apple",
 
+	    // Item definitions contain version information. Version is
+	    // represented as an array of integers, with major version number
+	    // being the first array item. In case of resources, version is
+	    // accompanied by a revision field which contains a positive
+	    // integer. If versions specified by arrays of different length need
+	    // to be compared, the shorter array gets padded with zeroes on the
+	    // right. This means that for example version 1.3 could be given as
+	    // both [1, 3] and [1, 3, 0, 0] (aka 1.3.0.0) and either would mean
+	    // the same.
 	    // Different versions (e.g. 1.0 and 1.3) of the same resource can be
 	    // defined in separate index.json files. This makes it easy to
 	    // accidently cause an identifier clash. To help detect it, we