Skip to content

Output Formatting #679

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
handrews merged 14 commits into from
Dec 28, 2018
Merged

Output Formatting #679

Changes from 1 commit
Commits
Show all changes
14 commits
Select commit Hold shift + click to select a range
cc8957f
Add 'output formatting' markdown composition as working medium
gregsdennis Nov 18, 2018
2a4b28b
Add exceedingly large verbose output as separate file
gregsdennis Nov 18, 2018
6571b06
Add composition to spec XML
gregsdennis Nov 18, 2018
59f9ff0
updated per @Anthropic's suggestions :+1:
gregsdennis Nov 30, 2018
cf7a6e0
addressed most of @handrews's comments
gregsdennis Dec 5, 2018
fd1b00d
removed composition file; added output schema
gregsdennis Dec 6, 2018
df63510
clarified requirements around implementation support
gregsdennis Dec 7, 2018
06cd268
addressed some wording concerns
gregsdennis Dec 7, 2018
5504ffc
added comment for relative pointers in output formatting
gregsdennis Dec 10, 2018
32c624b
Updated language around format support requirements
gregsdennis Dec 18, 2018
fb312cc
Set support requirements per conversation in slack
gregsdennis Dec 21, 2018
02295dc
better wording for output
gregsdennis Dec 25, 2018
063fbe2
a bit more wordsmithing around output requirements
gregsdennis Dec 27, 2018
235c54a
Merge branch 'master' into draft-08-output-formatting
handrews Dec 28, 2018
File filter

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
Prev Previous commit
Next Next commit
addressed some wording concerns
  • Loading branch information
@gregsdennis
gregsdennis committed Dec 7, 2018
commit 06cd2689f18bb6d6059a73e10c57bc3800fbc968
6 changes: 3 additions & 3 deletions jsonschema-core.xml
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -2127,8 +2127,8 @@
section for the requirements of each format.
<list>
<t>
Flag - A boolean which simply indicates whether the schema was
validated.
Flag - A boolean which simply indicates the overall validation result
with no further details.
</t>
<t>
Basic - Provides validation information in a flat list structure.
Expand Down Expand Up @@ -2168,7 +2168,7 @@
<t>
The relative location of the validating keyword that follows the validation
path. The value MUST be expressed as a JSON Pointer, and it MUST include
"$ref" or "$recursiveRef" segments for any reference jumps.
any by-reference applicators such as "$ref" or "$recursiveRef".
</t>
<figure>
<artwork>
Expand Down