schema: added $id properties to schemas

Added `$id` properties to schemas to experiment with implications, as
discussed in #561.

There's no need to change $ref due to how URI resolution works in
JSON Schema 2020-12; in short we only need to declare the full URI when
we're referencing schemas that aren't going to be co-located (so
basically, if we want to borrow someone elses' schema for something).

One thing I am thinking about is how the canonical schemas are really
the "compiled" schemas, and how not every schema is compiled. Currently,
if these schemas are compiled then the id for the compiled schemas would
lead to the uncompiled schemas. This seems wrong to me, and bears some
thinking about.

Author: mrshll1001

schema/accessibility.json

@@ -1,4 +1,5 @@
 {
+    "$id": "https://raw.githubusercontent.com/openreferral/specification/refs/heads/3.2/schema/accessibility.json",
     "name": "accessibility",
     "path": "accessibility.csv",
     "description": "The details of the arrangements for access to locations for people who have disabilities.",

schema/address.json

@@ -1,4 +1,5 @@
 {
+    "$id": "https://raw.githubusercontent.com/openreferral/specification/refs/heads/3.2/schema/address.json",
     "name": "address",
     "path": "addresses.csv",
     "description": "The addresses of locations where organizations operate.",

schema/attribute.json

@@ -1,4 +1,5 @@
 {
+  "$id": "https://raw.githubusercontent.com/openreferral/specification/refs/heads/3.2/schema/attribute.json",
   "name": "attribute",
   "path": "attributes.csv",
   "description": "A link between a service and one or more classifications that describe the nature of the service provided.",

schema/contact.json

@@ -1,4 +1,5 @@
 {
+    "$id": "https://raw.githubusercontent.com/openreferral/specification/refs/heads/3.2/schema/contact.json",
     "name": "contact",
     "path": "contacts.csv",
     "description": "The details of the named contacts for services and organizations.",

schema/cost_option.json

@@ -1,4 +1,5 @@
 {
+    "$id": "https://raw.githubusercontent.com/openreferral/specification/refs/heads/3.2/schema/cost_option.json",
     "name": "cost_option",
     "path": "cost_options.csv",
     "description": "The costs of a service at certain points in time. This is an LGA Extension. This object provides a structured version of the text information contained in the 'fees' field of the 'service' object.",

schema/funding.json

@@ -1,4 +1,5 @@
 {
+    "$id": "https://raw.githubusercontent.com/openreferral/specification/refs/heads/3.2/schema/funding.json",
     "name": "funding",
     "path": "funding.csv",
     "description": "The sources of funding for a service or organization.",

schema/language.json

@@ -1,4 +1,5 @@
 {
+    "$id": "https://raw.githubusercontent.com/openreferral/specification/refs/heads/3.2/schema/language.json",
     "name": "language",
     "path": "languages.csv",
     "description": "The languages that are spoken at locations or services. This does not include languages which can only be used with interpretation.",

schema/location.json

@@ -1,4 +1,5 @@
 {
+    "$id": "https://raw.githubusercontent.com/openreferral/specification/refs/heads/3.2/schema/location.json",
     "name": "location",
     "path": "locations.csv",
     "description": "The locations where organizations operate. Locations may be virtual, and one organization may have many locations.",

schema/metadata.json

@@ -1,4 +1,5 @@
 {
+    "$id": "https://raw.githubusercontent.com/openreferral/specification/refs/heads/3.2/schema/metadata.json",
     "name": "metadata",
     "path": "metadata.csv",
     "description": "A record of the changes that have been made to the data in order to maintain provenance information.",
@@ -117,4 +118,4 @@
         "resource_id",
         "resource_type"
     ]
-}
+}

schema/organization.json

@@ -1,4 +1,5 @@
 {
+  "$id": "https://raw.githubusercontent.com/openreferral/specification/refs/heads/3.2/schema/organization.json",
   "name": "organization",
   "path": "organizations.csv",
   "description": "The details about each organization delivering services. Each service should be linked to the organization responsible for its delivery. One organization may deliver many services.",