json-api · bradjones1 · Jul 5, 2024 · Jul 5, 2024 · Jul 5, 2024 · Jul 5, 2024
diff --git a/.gitignore b/.gitignore
@@ -29,3 +29,5 @@ Gemfile.lock
 # Ignore the node_modules directory
 
 /node_modules
+
+/yarn.lock
diff --git a/CONTRIBUTING.md b/CONTRIBUTING.md
@@ -28,7 +28,7 @@ npm install
 Then you can run the schema validator by running one of the following commands :
 
 `
-node ./_schemas/scripts/validator.js
+node ./schemas/scripts/validator.js
 `
 
 or
@@ -40,5 +40,5 @@ npm run test-schema
 This script validates all test files against all available versions of the specification.
 Some options can be used :
 - `--verbose` : allows more verbose output.
-- `-f relative-path` : the relative path of the only file to test. For example : `npm run test-schema -- -f _schemas/1.0/response/valid/with_success/complete.json`
+- `-f relative-path` : the relative path of the only file to test. For example : `npm run test-schema -- -f schemas/1.0/response/valid/with_success/complete.json`
 - `-v version` : the version of the specification to use to test the files. For example : `npm run test-schema -- -v 1.0`
diff --git a/_schemas/1.0/schema_update_relationship.json b/_schemas/1.0/schema_update_relationship.json
diff --git a/faq/index.md b/faq/index.md
@@ -6,7 +6,7 @@ show_sidebar: true
 
 ## <a href="#what-is-the-meaning-of-json-apis-version" id="what-is-the-meaning-of-json-apis-version" class="headerlink"></a> What is the meaning of JSON:API's version?
 
-Now that JSON:API has reached a stable version 1.0, it will always be
+Following JSON:API's first stable version (1.0), it will always be
 backwards compatible using a _never remove, only add_ strategy.
 
 A version is maintained in order to:
@@ -81,14 +81,15 @@ don’t can be easily [worked around](/recommendations/#patchless-clients).
 
 ## <a href="#is-there-a-json-schema-describing-json-api" id="is-there-a-json-schema-describing-json-api" class="headerlink"></a> Is there a JSON Schema describing JSON:API?
 
-Yes, you can find the JSON Schema definition at
-[http://jsonapi.org/schema](http://jsonapi.org/schema). This schema is as
-restrictive as possible, but has flexibility to be extended within your
-documentation. Validation will not yield false negatives, but could yield false
-positives for the sake of flexibility.
+Yes, you can find the response JSON Schema definition for version 1.0 at
+[`https://jsonapi.org/schema`](http://jsonapi.org/schema). (An update for
+version 1.1 is [under development](https://github.com/json-api/json-api/issues/1672).)
+
+[Additional schemas](/schemas/1.0/) are provided for requests creating and
+updating resources or updating relationships.
 
 You can find more information about the JSON Schema format at
-[http://json-schema.org](http://json-schema.org).
+[https://json-schema.org](https://json-schema.org).
 
 ## <a href="#resource-collections-returned-as-arrays" id="resource-collections-returned-as-arrays" class="headerlink"></a> Why are resource collections returned as arrays instead of sets keyed by ID?
 

diff --git a/package.json b/package.json
@@ -6,6 +6,6 @@
     "readdirp": "^3.6.0"
   },
   "scripts": {
-    "test-schema": "node -i _schemas/scripts/validator.js"
+    "test-schema": "node -i schemas/scripts/validator.js"
   }
 }
diff --git a/schema b/schema
@@ -0,0 +1,5 @@
+{
+  "$id": "https://jsonapi.org/schema",
+  "$comment": "JSON:API JSON Schema. This well-known schema URI references versioned JSON Schemas. JSON:API versions are always backwards-compatible.",
+  "$ref": "https://jsonapi.org/schemas/1.0/schema.json"
+}
diff --git a/schemas/1.0/index.md b/schemas/1.0/index.md
@@ -0,0 +1,10 @@
+---
+layout: page
+title: JSON Schemas for specification version 1.0
+show_sidebar: false
+---
+
+* [Response schema](./schema.json)
+* [Create Resource (`POST`)](./schema_create_resource.json)
+* [Update Resource (`PATCH`)](./schema_create_resource.json)
+* [Update Relationship (`PATCH`)](./schema_update_relationship.json)
Original file line number	Diff line number	Diff line change
Expand Up		@@ -29,3 +29,5 @@ Gemfile.lock
		# Ignore the node_modules directory

		/node_modules

		/yarn.lock