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