Skip to content

Editorial: fix obsolete RFC reference and phrasing #3

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
clemensv merged 1 commit into from
Jun 8, 2026
+5 −5
Merged

Editorial: fix obsolete RFC reference and phrasing #3

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
10 changes: 5 additions & 5 deletions draft-vasters-json-structure-validation.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -28,7 +28,7 @@ author:

normative:
RFC2119:
RFC4646:
RFC5646:
RFC8174:
JSTRUCT-CORE:
title: "JSON Structure Core"
Expand Down Expand Up @@ -405,8 +405,8 @@ Example:

### `has` {#has}

The `has` keyword validates that an object or map has at least one (property)
value that matches the schema. The schema MUST be of type `object`.
The `has` keyword validates that an object or map has at least one value
that matches the schema. The schema MUST be of type `object`.

Example:

Expand Down Expand Up @@ -441,8 +441,8 @@ Example:
## Enabling the Extensions {#enabling-the-extensions}

Validation extensions can be enabled in a schema or
meta-schema by adding the `JSONSchemaValidation` key to the `$uses`
clause when referencing the extended meta-schema:
meta-schema by adding `JSONSchemaValidation` to the `$uses`
array when referencing the extended meta-schema:

~~~ json
{
Expand Down
Loading