Looks cool, although it looks a bit U.S.-centric and techie-centric.
Other people have mentioned the firstName/lastName problem and the region/state ambiguity. I'll mention a few more items that might be helpful if you really want this to become a worldwide standard:
1. In some countries, it is not only legal but also customary for employers to ask for, and job seekers to include, various demographic information about themselves that would be considered discriminatory in the U.S. For example, sex/gender, date of birth, marriage status, and family details. It would be good to define such fields in the schema but leave them optional. Or define a catch-all field where anyone can add any key-value pair.
1-1. Don't forget the full street address, including the postal code!
1-2. Citizenship. This is very important for companies that might need to sponsor your visa and/or geeen card.
1-3. In some countries, it is customary to include a photograph of yourself in your resume. Perhaps this could take the form of a "photo" field that takes a URL.
1-4. There needs to be a field where you can write down an alternate expression of your name. Many Korean names can be written in either Hangul or Hanja. Most Japanese names are written in Kanji, but often accompanied by Hiragana to help the reader pronounce them properly. A lot of employers in these countries require both forms.
2. Since this is going to be electronically processed, perhaps it would be a good idea to include the ticker code for publicly traded companies in one's employment history? GOOG is much easier to search for than variations of "Google", "Google Inc.", etc.
3. The publications schema will need to be significantly expanded if you want scientists and other academics to even consider using this. Take a look at how academic publications are cited. At the very least, there needs to be a field to specify the type of publication, e.g. book, ebook, edited book, journal article, newspaper article, conference presentation, workshop presentation, blog post, website, etc. There should also be a "doi" field for scientific and other academic publications.
3-1. The education schema needs a "summary" field, just like the employment schema.
4. Some employers prefer to get the content of the reference from the referee him/herself, rather than having the applicant include it in the resume. (Otherwise, the applicant could modify the content.) So you need fields to put the email address (to contact the referee) and a URL (to grab the content of the reference) in the references field. Oh, and don't forget the referee's employer and title/position. Those things matter.
4-1. Bonus points if the content of the reference can be authenticated with the referee's PGP key.
4-2. Extra bonus points if the entire resume can be authenticated with the applicant's PGP key, to prevent hiring agencies from messing with the content.
Excellent feedback and you've set the bar high which is good! I don't have the time to reply to each point at the moment but will definitely copy it over to the issue tracker.
Other people have mentioned the firstName/lastName problem and the region/state ambiguity. I'll mention a few more items that might be helpful if you really want this to become a worldwide standard:
1. In some countries, it is not only legal but also customary for employers to ask for, and job seekers to include, various demographic information about themselves that would be considered discriminatory in the U.S. For example, sex/gender, date of birth, marriage status, and family details. It would be good to define such fields in the schema but leave them optional. Or define a catch-all field where anyone can add any key-value pair.
1-1. Don't forget the full street address, including the postal code!
1-2. Citizenship. This is very important for companies that might need to sponsor your visa and/or geeen card.
1-3. In some countries, it is customary to include a photograph of yourself in your resume. Perhaps this could take the form of a "photo" field that takes a URL.
1-4. There needs to be a field where you can write down an alternate expression of your name. Many Korean names can be written in either Hangul or Hanja. Most Japanese names are written in Kanji, but often accompanied by Hiragana to help the reader pronounce them properly. A lot of employers in these countries require both forms.
2. Since this is going to be electronically processed, perhaps it would be a good idea to include the ticker code for publicly traded companies in one's employment history? GOOG is much easier to search for than variations of "Google", "Google Inc.", etc.
3. The publications schema will need to be significantly expanded if you want scientists and other academics to even consider using this. Take a look at how academic publications are cited. At the very least, there needs to be a field to specify the type of publication, e.g. book, ebook, edited book, journal article, newspaper article, conference presentation, workshop presentation, blog post, website, etc. There should also be a "doi" field for scientific and other academic publications.
3-1. The education schema needs a "summary" field, just like the employment schema.
4. Some employers prefer to get the content of the reference from the referee him/herself, rather than having the applicant include it in the resume. (Otherwise, the applicant could modify the content.) So you need fields to put the email address (to contact the referee) and a URL (to grab the content of the reference) in the references field. Oh, and don't forget the referee's employer and title/position. Those things matter.
4-1. Bonus points if the content of the reference can be authenticated with the referee's PGP key.
4-2. Extra bonus points if the entire resume can be authenticated with the applicant's PGP key, to prevent hiring agencies from messing with the content.