-
-
Notifications
You must be signed in to change notification settings - Fork 320
Update to 10.4 "Output Structure" #825
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
Conversation
Per the following issue: json-schema-org#824
To be clear, there's not a typo in the text. This is about |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
These are informal errors intended for the prose explanation of the output, not errors as they would be generated by an implementation. It's fine for them to have semantic information about the schema.
"Vertices" is probably left over from an earlier draft of this section while I wrote it.
@Relequestual what's the process for changes like these? Does this go into a "draft 2019-12” or whatever the next minor iteration is?
Interesting case here. Later in 10.4.2, we give the BASIC output with the error "Expected at least 3 items but found 2". Maybe the mentioned error message was simply not sanity checked. |
In terms of "what's the process", let's open a new issue and get it defined properly =] |
@gregsdennis I tried really hard to get all of the example lines within the limits of the IETF text rendering format, or at least down to only giving specification build warnings instead of errors. I'm fairly certain I changed it to "points" to save a few letters and must have missed "vertices" here. |
@Relequestual @gregsdennis the process is to tag these things with the appropriate milestone, which would be draft-08-patch1. Which I've been doing as appropriate since 2019-09 was published. See also the big table at https://json-schema.org/specification-links.html which records milestones along with every other type of version thingy we use. |
I think two is the magic number here... |
Per the following issue: #824