-
Notifications
You must be signed in to change notification settings - Fork 282
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
Relaxed requirements for JSON resume #482
Comments
Changes and non-changes
Non-change: In my opinion, a resume without the candidate's name probably should not be considered a resume.
Change:
Change:
Non-change: Emails are so ubiquitous today that it's hard to imagine a situation where the resume without email would make sense.
Change:
Change: P.S. WORK IN PROGRESS |
I had similar thoughts just yesterday jsonresume/jsonresume.org#118 Will have a think and leave some thoughts later today |
While drafting a new schema, I realized that |
Yeah omission and additives should be fine. |
Then my use case doesn't need any changes to the schema. Sorry for bothering you! |
Awesome @JohnScience I am about to give some love to the schema repo, so let me know if you reach any other hurdles and we will try to sort out a solution. You will likely outgrow the schema, but we are very much in support of super/sub sets. There is also the |
At Searchless, we were planning to use JSON schema standard but found out that its requirements are too strict for conversion from regular resume to JSON resume.
The current schema
rejects the following substandard "JSON resume" for multiple reasons:
It was generated by our in-house tools from https://careers.yorku.ca/files/2017/04/Sample-Resume-1st-Year-No-Work-Experience.pdf. There are many problems with it.
If we run the checks of https://www.jsonschemavalidator.net/ against it, we'll see that there are 20 errors.
What's the main problem?
null
s are necessary to represent real-world resumes. However, the schema technically does not allow fornull
values.I propose to also have the "relaxed" variant of JSON resume schema with values permitting
null
s.The text was updated successfully, but these errors were encountered: