Name: resume-schema
Owner: JSON Resume
Description: JSON-Schema is used here to define and validate our proposed resume json
Created: 2014-06-20 13:17:53.0
Updated: 2018-01-19 22:16:53.0
Pushed: 2018-01-07 08:54:42.0
Homepage: http://jsonresume.org
Size: 1968
Language: HTML
GitHub Committers
User | Most Recent Commit | # Commits |
---|
Other Committers
User | Most Recent Commit | # Commits |
---|
Standard, Specification, Schema
We are still currently un-versioned, some core changes are being pushed out, and a version 0.0.0 will be released following Semantic Versioning 2.0.0 best practices. We will be experimenting with a migration.js
system, where each change below will be represented with a function that can update an older version of resume.json
to the newer versions.
There will be a learning curve for the next few months as to how the ecosystem will revolve around versions.
To keep things simple, JSON Resume tools are only expected to react to major version changes, everything will follow suit only after we reach version 1.0.0
. The process for patches and fixes will be informal, and we will try to make everything work for major versions.
languages
was added - Dicussions - Commithobbies
was renamed to interests
volunteer
was added - Discussion - Commitsummary
was added to awards
- Discussion - Commitsummary
was added to publications
- Discussion - Commitbio
was renamed to basics
- Discussion - Commitprofiles
was changed to a type array instead of an object - Discussion - Commitaddress
and postalCode
were added to location
- Discussion - CommitawardDate
was changed to date
- Discussion - Commitwebsites
was changed to website
, changed from object into string - Discussion - CommitcountryCode
conforms to ISO standard - Discussion - Commitregion
replaced state
as the default - Discussion - Commitpicture
was added to the bio
object - Discussion - Commitgpa
was added to education
objects - Discussion - Commitemail
and phone
were changed from objects into strings - Discussion - CommitfirstName
and lastName
were merged into name
- Discussion - CommitEveryone working on the early stages of the project should join our gitter channel gitter.im/jsonresume/public.
install --save resume-schema
To use
resumeSchema = require('resume-schema');
meSchema.validate({ name: "Thomas" }, function (err, report) {
(err) {
console.error('The resume was invalid:', err);
return;
nsole.log('Resume validated successfully:', report);
More likely
fs = require('fs');
resumeSchema = require('resume-schema');
resumeObject = JSON.parse(fs.readFileSync('resume.json', 'utf8'));
meSchema.validate(resumeObject);
The JSON Resume schema is available from:
ire('resume-schema').schema;
We encourage anyone who's interested in participating in the formation of this standard, to join us on Gitter, and/or to join the discussions here on GitHub. Also feel free to fork this project and submit new ideas to add to the JSON Resume Schema standard. To make sure all formatting is kept in check, please install the EditorConfig plugin for your editor of choice.
JSON Resume Schema adheres to Semantic Versioning 2.0.0. If there is a violation of this scheme, report it as a bug. Specifically, if a patch or minor version is released and breaks backward compatibility, that version should be immediately yanked and/or a new version should be immediately released that restores compatibility. Any change that breaks the public API will only be introduced at a major-version release. As a result of this policy, you can (and should) specify any dependency on JSON Resume Schema by using the Pessimistic Version Constraint with two digits of precision.