Skip to content

markdown errata #1428

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 3 commits into from
Sep 10, 2023
Merged

markdown errata #1428

Changes from 1 commit
Commits
Show all changes
3 commits
Select commit Hold shift + click to select a range
8ab3d25
found some errata in the output sections
gregsdennis Aug 27, 2023
5ee5bdd
adjust for line length
gregsdennis Aug 28, 2023
c13033f
add closing brace
gregsdennis Sep 4, 2023
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: 4 additions & 6 deletions jsonschema-core.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -2079,7 +2079,7 @@ consumers will need to properly interpret validation results.
### Format

JSON Schema output is defined using the JSON Schema data instance model as
described in section 4.2.1. Implementations MAY deviate from this as supported
described in [Instance Data Model](#data-model). Implementations MAY deviate from this as supported
by their specific languages and platforms, however it is RECOMMENDED that the
output be convertible to the JSON format defined herein via serialization or
other means.
Expand All @@ -2092,8 +2092,7 @@ section for the requirements of each format.
- *Flag*: A boolean which simply indicates the overall validation result with no
further details.
- *List*: Provides validation information in a flat list structure.

Hierarchical: Provides validation information in a hierarchical structure that
- *Hierarchical*: Provides validation information in a hierarchical structure that
follows the evaluation paths generated while processing the schema.

An implementation MUST provide the "flag" format and SHOULD provide at least one
Expand Down Expand Up @@ -2283,7 +2282,6 @@ For these examples, the following schema and instances will be used.
}
```


```json "Failing instance"
{
"foo": {"foo-prop": "not 1", "other-prop": false},
Expand Down Expand Up @@ -2324,9 +2322,9 @@ allows their users to craft their own messages.

The passing instance will produce the following annotations:

- The keyword `title` evaluated at `` by following the path `` will produce
- The keyword `title` evaluated at the instance root by the root schema will produce
`"root"`.
- The keyword `properties` evaluated at `` by following the path `` will produce
- The keyword `properties` evaluated at instance root by the root schema will produce
`["foo", "bar"]`.
- The keyword `title` evaluated at `/properties/foo` by following the path
`/properties/foo` will produce `"foo-title"`.
Expand Down