Skip to content

Commit ab4eb1d

Browse files
feat: add glossary term for Anchor (#680)
* feat: add glossary term for Anchor * update: redefine anchor term and add URI example * update: add editorial suggestions to anchor definition. Co-authored-by: Jason Desrosiers <[email protected]> --------- Co-authored-by: Jason Desrosiers <[email protected]>
1 parent 9b27076 commit ab4eb1d

File tree

1 file changed

+6
-0
lines changed

1 file changed

+6
-0
lines changed

pages/learn/glossary.md

+6
Original file line numberDiff line numberDiff line change
@@ -128,6 +128,12 @@ Said more plainly, whether a particular value is a subschema or not depends on i
128128

129129
Subschemas may themselves contain sub-subschemas, though colloquially one generally uses the term "subschema" regardless of the level of nesting, further clarifying which larger schema is the parent schema whenever needed.
130130

131+
132+
### anchor
133+
134+
An anchor identifies the location of a subschema within a JSON document. By applying an anchor to a subschema using the `$anchor` keyword, the subschema becomes identifiable via a plain-name URI string containing the value of the `$anchor` property starting with a `#` character. An example of a plain-name URI is `https://example.com/schemas/vehicle#owners` identifying the `owners` subschema within the `vehicle` JSON document. An anchor is also a shorter alternative to using a JSON Pointer for identifying a subschema.
135+
136+
<!-- TODO: add reference to JSON pointer term as a see more. -->
131137
### tooling
132138

133139
A JSON Schema tool (or colloquially "tooling") is any software application or library for working with or evaluating schemas in some way.

0 commit comments

Comments
 (0)