Skip to content

Commit 7435bcb

Browse files
committed
$ref no longer effects other properties in the same object.
Updated phrasing to align with current wording. Resolves #514 and #523
1 parent c46c7da commit 7435bcb

File tree

1 file changed

+10
-6
lines changed

1 file changed

+10
-6
lines changed

jsonschema-core.xml

Lines changed: 10 additions & 6 deletions
Original file line numberDiff line numberDiff line change
@@ -955,15 +955,19 @@
955955

956956
<section title='Schema References With "$ref"' anchor="ref">
957957
<t>
958-
The "$ref" keyword is used to reference a schema, and provides the ability to
959-
validate recursive structures through self-reference.
958+
The "$ref" keyword can be used to reference a schema which is to be applied to the
959+
current instance location. "$ref" is an applicator key word, applying the referred
960+
schema to the instance.
960961
</t>
961-
<t>
962-
An object schema with a "$ref" property MUST be interpreted as a "$ref" reference.
963-
The value of the "$ref" property MUST be a URI Reference.
962+
+ <t>
963+
+ The value of the "$ref" property MUST be a string which is a URI Reference.
964964
Resolved against the current URI base, it identifies the URI of a schema to use.
965-
All other properties in a "$ref" object MUST be ignored.
966965
</t>
966+
<t>
967+
As the value of "$ref" is a URI Reference, this allows the posibility to externalise or
968+
+ shard a schema across multiple files, and provides the ability to validate recursive structures
969+
+ through self-reference.
970+
+ </t>
967971
<t>
968972
The URI is not a network locator, only an identifier. A schema need not be
969973
downloadable from the address if it is a network-addressable URL, and

0 commit comments

Comments
 (0)