extract propertyDependencies

.gitignore

@@ -4,6 +4,7 @@ jsonschema-*.txt
 relative-json-pointer.html
 relative-json-pointer.pdf
 relative-json-pointer.txt
+extensions/*.html
 
 # For the Python enviornment
 .venv

README.md

@@ -25,9 +25,11 @@ Labels are assigned based on [Sensible Github Labels](https://github.com/Releque
 ## Authoring and Building
 
 ### Specification
-To build the spec files to HTML from the Markdown sources, run `npm run build`.
-You can also build each individually with `npm run build-core` and `npm run
-build-validation`.
+To build the spec files to HTML from the Markdown sources, run `npm run
+build-all`.
+You can also build each individually with `npm run build -- filename.md`
+(Example: `npm run build -- jsonschema-core.md`). You can also use wildcards to
+build multiple specs at the same time: `npm run build -- jsonschema-*.md`.
 
 The spec is built using [Remark](https://remark.js.org/), a markdown engine with
 good support for plugins and lots of existing plugins we can use.

extensions/propertyDependencies.md

@@ -0,0 +1,67 @@
+# JSON Schema Extension: The `propertyDependencies` Keyword
+
+## Abstract
+
+The `propertyDependencies` keyword is a more friendly way to select between two
+or more schemas to validate an instance against than is currently supported by
+JSON Schema.
+
+## Status
+
+**Current Status**: EXPERIMENTAL
+
+This extension is in the early stages of development. Changes, including
+breaking changes, are possible. At this stage, it's recommended that
+implementations disable this keyword by default.
+
+This extension has been
+[proposed](https://github.com/json-schema-org/json-schema-spec/blob/main/proposals/propertyDependencies.md)
+for inclusion as a standard keyword in the JSON Schema specification.
+
+## Note to Readers
+
+The issues list for this extension can be found at
+<https://github.com/json-schema-org/json-schema-spec/issues?q=is%3Aissue+propertydependencies>.
+
+For additional information, see <https://json-schema.org/>.
+
+To provide feedback, use this issue tracker or any of the communication methods
+listed on the homepage.
+
+## Table of Contents
+
+## Conventions and Terminology
+
+All conventions and terms used and defined by the [JSON Schema Core
+specification](../jsonschema-core.html) also apply to this document.
+
+## Extension
+
+This document adds the `propertyDependencies` keyword to the
+`https://json-schema.org/vocab/applicator` [applicator
+vocabulary](../jsonschema-core.html#applicatorvocab).
+
+### `propertyDependencies`
+
+This keyword specifies subschemas that are evaluated if the instance is an
+object and contains a certain property with a certain string value.
+
+This keyword's value MUST be an object. Each value in the object MUST be an
+object whose values MUST be valid JSON Schemas.
+
+If the outer object key is a property in the instance and the inner object key
+is equal to the value of that property, the entire instance must validate
+against the schema. Its use is dependent on the presence and value of the
+property.
+
+Omitting this keyword has the same behavior as an empty object.
+
+## [Appendix] Change Log
+
+* [October 2023] Created
+
+## Champions
+
+| Champion                   | Company | Email                | URI                              |
+|----------------------------|---------|----------------------|----------------------------------|
+| Jason Desrosiers           | Postman | <[email protected]> | <https://github.com/jdesrosiers> |

jsonschema-core.md

@@ -1655,7 +1655,7 @@ User-Agent: product-name/5.4.1 so-cool-json-schema/1.0.2 curl/7.43.0
 Clients SHOULD be able to make requests with a "From" header so that server
 operators can contact the owner of a potentially misbehaving script.
 
-## A Vocabulary for Applying Subschemas
+## A Vocabulary for Applying Subschemas {#applicatorvocab}
 
 This section defines a vocabulary of applicator keywords that are RECOMMENDED
 for use as the basis of other vocabularies.
@@ -1793,7 +1793,7 @@ successfully validates against its subschema. Implementations MUST NOT evaluate
 the instance against this keyword, for either validation or annotation
 collection purposes, in such cases.
 
-##### `dependentSchemas`
+##### `dependentSchemas` {#dependent-schemas}
 
 This keyword specifies subschemas that are evaluated if the instance is an
 object and contains a certain property.
@@ -1807,21 +1807,6 @@ property.
 
 Omitting this keyword has the same behavior as an empty object.
 
-##### `propertyDependencies`
-
-This keyword specifies subschemas that are evaluated if the instance is an
-object and contains a certain property with a certain string value.
-
-This keyword's value MUST be an object. Each value in the object MUST be an
-object whose values MUST be valid JSON Schemas.
-
-If the outer object key is a property in the instance and the inner object key
-is equal to the value of that property, the entire instance must validate
-against the schema. Its use is dependent on the presence and value of the
-property.
-
-Omitting this keyword has the same behavior as an empty object.
-
 ### Keywords for Applying Subschemas to Child Instances
 
 Each of these keywords defines a rule for applying its subschema(s) to child