-
-
Notifications
You must be signed in to change notification settings - Fork 164
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
Create a JSON Schema Glossary Page or Site #266
Comments
maybe out of scope? maybe include as links
|
I like the idea of the glossary, but what would this give us that the "definitions" section of the spec doesn't? |
Right now we only really have a few things in that section, so there's definitely a lot more (obviously things all defined scattered lower in the spec). But the main thing I think is to target it to a non-implementer -- the vast majority of our users I suspect would be very intimidated by the spec document and haven't read it, they're just consumers of JSON Schema. The spec's a technical document -- kind of like how we have the Understanding JSON Schema tutorial for the same reason. |
@notEthan added yours to the list! Thanks. |
I'm all for this! |
Doing so should hopefully now allow farming out additional entries. Refs: json-schema-org/community#199.
^^ there's an initial PR just adding the page with an intro and 2 entries to get us started. I think once someone reviews / merges that, we then simply each start grabbing stuff from the list -- probably if you grab an entry, mark it in the issue description here so others know you're working on it, and then add your PR number when you send one (which GH will then cross off when the PR is merged). |
Doing so should hopefully now allow farming out additional entries. Refs: json-schema-org/community#199.
In the process of creating a drafts for |
@benjagm I'd love to take up |
Thanks a lot @vickywane ! Please go ahead |
Just created PR #668. To add the sections of |
I will be submitting PR for |
Hi can I take up |
Thanks a lot. Please go ahead. |
Thanks a lot. Please go ahead! |
Hello! 👋 This issue has been automatically marked as stale due to inactivity 😴 It will be closed in 180 days if no further activity occurs. To keep it active, please add a comment with more details. There can be many reasons why a specific issue has no activity. The most probable cause is a lack of time, not a lack of interest. Let us figure out together how to push this issue forward. Connect with us through our slack channel : https://json-schema.org/slack Thank you for your patience ❤️ |
This is a long term issue. We'll keep it open. |
@benjagm I am working on Any information regarding this subject matter would be helpful to me. |
Thanks a lot for working on this @umarbshehu. My advice is to start with the available definition of JSON Pointer and do a research in the JSON Schema specification to understand the relative JSON pointer and provide your description avoiding repeating the same wording used in the spec. |
It'd be nice if we had a glossary of terms -- a page, in not very technical jargon, which explains common terminology used by us in conversation, and which could be linked to by other pages or people in order to answer questions like "what is a vocabulary" in a succinct way.
Here are two examples of glossaries I've contributed to or used heavily which may be decent examples of the concept:
EDIT: The page has been published at https://json-schema.org/learn/glossary.html
To help, just grab any of the entries below which don't already exist on the page, and share that you're working on them!
List of Terms to Define
The text was updated successfully, but these errors were encountered: