Skip to content

align path terminology in the text with the renamings made for the output #1264

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 1 commit into from
Aug 21, 2022
Merged

align path terminology in the text with the renamings made for the output #1264

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
16 changes: 8 additions & 8 deletions jsonschema-core.xml
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -679,7 +679,7 @@
which processing begins, even if it is not a schema resource root.
The path from this root schema to any particular keyword (that
includes any "$ref" and "$dynamicRef" keywords that may have
been resolved) is considered the keyword's "validation path."
been resolved) is considered the keyword's "evaluation path."
</t>
<t>
Lexical and dynamic scopes align until a reference keyword
Expand All @@ -698,7 +698,7 @@
when reporting errors and collected annotations, as it may be possible
to revisit the same lexical scope repeatedly with different dynamic
scopes. In such cases, it is important to inform the user of the
dynamic path that produced the error or annotation.
evaluation path that produced the error or annotation.
</t>
</section>
<section title="Keyword Interactions">
Expand Down Expand Up @@ -930,12 +930,12 @@
The instance location to which it is attached, as a JSON Pointer
</t>
<t>
The schema location path, indicating how reference keywords
The evaluation path, indicating how reference keywords
such as "$ref" were followed to reach the absolute schema location.
</t>
<t>
The absolute schema location of the attaching keyword, as a IRI.
This MAY be omitted if it is the same as the schema location path
This MAY be omitted if it is the same as the evaluation path
from above.
</t>
<t>
Expand Down Expand Up @@ -1016,11 +1016,11 @@
author to write descriptions that work when combined in this way.
</t>
<t>
The application can use the schema location path to determine which
The application can use the evaluation path to determine which
values are which. The values in the feature's immediate "enabled"
property schema are more specific, while the values under the re-usable
schema that is referenced to with "$ref" are more generic. The schema
location path will show whether each value was found by crossing a
schema that is referenced to with "$ref" are more generic. The evaluation
path will show whether each value was found by crossing a
"$ref" or not.
</t>
<t>
Expand Down Expand Up @@ -3605,7 +3605,7 @@ https://example.com/schemas/common#/$defs/count/minimum
scope before following the reference.
</t>
<t>
At this point, the dynamic path is
At this point, the evaluation path is
"#/$ref/properties/children/items/$dynamicRef", with a dynamic scope
containing (from the outermost scope to the innermost):
<list style="numbers">
Expand Down