Skip to content

Navigation Menu

Sign in
Appearance settings

Search code, repositories, users, issues, pull requests...

Provide feedback

We read every piece of feedback, and take your input very seriously.

Saved searches

Use saved searches to filter your results more quickly

Sign up
Appearance settings

Update output schema to describe new structure #1285

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.

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
gregsdennis merged 1 commit into main from gregsdennis-update-output-schema
Oct 17, 2022

Conversation

Copy link
Member

@gregsdennis gregsdennis commented Sep 8, 2022
edited
Loading

Updates the output schema file to match the new structure as described by the specification. Follow-up to #1249.

I've tested this against the example output in the spec.

Resolves #949

"type": "string",
"format": "json-pointer"
},
"absoluteKeywordLocation": {
"schemaLocation": {
"type": "string",
"format": "uri"
Copy link
Member

@karenetheridge karenetheridge Sep 11, 2022

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Shouldn't this be iri now?

Copy link
Member

@karenetheridge karenetheridge Sep 11, 2022

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

ah I see you're already on it, re the other PR about uri->iri changes.

gregsdennis reacted with thumbs up emoji
Copy link
Member Author

@gregsdennis gregsdennis Oct 17, 2022

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I'm going to push this forward as I can't wait on your PR any longer. It needs to be rebased anyway.

"$ref": "#/$defs/outputUnitArray"
}
},
"required": [ "valid", "nested" ]
Copy link
Member

@karenetheridge karenetheridge Sep 11, 2022

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Why does the 'basic' format contain 'nested'? My understanding was that basic is still a flat structure.

Copy link
Member Author

@gregsdennis gregsdennis Sep 11, 2022
edited
Loading

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Basic is an object with only valid and nested at the root. The rest is normal output units in the nested array.

{
 "valid": true,
 "nested": [ <flat list> ]
}

This provides the overall validation result at the root and a flat list. It's the same as 2020-12, except that the location properties aren't required at the root (because they're always just / and redundant).

@gregsdennis gregsdennis marked this pull request as ready for review October 17, 2022 01:12
@gregsdennis gregsdennis merged commit 9665007 into main Oct 17, 2022
@gregsdennis gregsdennis deleted the gregsdennis-update-output-schema branch October 17, 2022 20:48
Copy link
Member

Shouldn't this have gone into draft-next, not main?

Copy link
Member Author

@karenetheridge draft-next was merged some time ago.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Reviewers

@karenetheridge karenetheridge karenetheridge left review comments

+1 more reviewer

@handrews handrews handrews approved these changes

Reviewers whose approvals may not affect merge requirements
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

Successfully merging this pull request may close these issues.

Some inconsistencies in output schema

AltStyle によって変換されたページ (->オリジナル) /