Some personally identifiable information missing. Can I add them?

[gee-forr]

Hi all,

I love this concept, thank you!!! For this schema to work in a South African context, there are a few things missing. South African employment requires street addresses as well as (and this might freak you out): Race.

This is because we are still in the midst of Black Economic Empowerment, and Employment Equity post apartheid.

If you don't mind, I'd like to add these fields as optional parts to the schema.

Let me know, and I'll issue a PR.

[thomasdavis]

Hey Gabriel, We are a bit overwhelmed right now to reply fully to issues. Though I was thinking, our process for schema modifications would be to have a bit of discussion and throwing ideas around before submitting the pull request just so we don't waste anyones time.

For example, Race might have to be an array of strings =D ['Indiginous', 'Chinese', 'European'] for myself =D

On Mon, Jul 7, 2014 at 3:50 PM, Gabriel Fortuna notifications@github.com wrote:

Hi all,

I love this concept, thank you!!! For this schema to work in a South African context, there are a few things missing. South African employment requires street addresses as well as (and this might freak you out): Race.

This is because we are still in the midst of Black Economic Empowerment, and Employment Equity post apartheid.

If you don't mind, I'd like to add these fields as optional parts to the schema.

Let me know, and I'll issue a PR.

— Reply to this email directly or view it on GitHub https://github.com/jsonresume/resume-schema/issues/13.

Thomas Davis http://thomasdav.is

VP of Tech - Earbits - http://earbits.com Co-founder - Cdnjs - http://cdnjs.com Founder - Backbone Tutorials - http://backbonetutorials.com

[gee-forr]

Of course! You're right.

I also forgot, some kind of ID number is required. This would have to be an object thought... some e.g

{
type: 'SSN',
value: '123456-7890'
}

and

{
    type: 'UK Passport',
    value: '98765-4321'
}

[stp-ip]

Additionally I would love optional fields such as: "birthdate", "birthplace"

[aloisdg]

For the subject of race, I will link this conversation (cc @DandyDev).

[stp-ip]

@aloisdg as per #193 A warning as description is added and the more personal information is located in a special object. We could add another warning, which themes could pick up more easily probably, but haven't thought of one.

[osg]

@gee-forr From a US perspective (I don't know if "SSN" is used in other countries), a SSN is a highly protected number. Therefore, absolutely -1 on prompting the CV writer to include their SSN:

{ type: 'SSN', value: '123456-7890' }

For any non-security-clearance position, that information is provided to the employer after a resume/CV is provided, and often after an offer has been signed.

[osg]

@gee-forr Also, I have never provided a passport number on a resume. In what places and/or situations is this a requirement?

[smalik]

Some of this stuff is illegal to ask for in the U.S.

On Sep 12, 2015, at 2:58 AM, Ursula Kallio notifications@github.com wrote:

@gee-forr From a US perspective (I don't know if SSN is used in other countries), a SSN is a highly protected number. Therefore, absolutely -1 on prompting the CV writer to include their SSN:

{ type: 'SSN', value: '123456-7890' }

For any non-security-clearance position, that information is provided to the employer after a resume/CV is provided, and often only after an offer has been signed.

— Reply to this email directly or view it on GitHub.

[gee-forr]

@opensourcegrrrl thanks for the clarification... I was merely using SSN as an example. In ZA, we require an ID number, or passport number as part of an application. I was under the assumption that an SSN was equivalent to that.

[gee-forr]

@smalik - yeah - I totally get that. However, in ZA, it's normal to ask for this information.

[osg]

This is a great argument for internationalization and localization. :)

[wayneamurphy]

-∞ for SSN as a required field, as others have suggested it is not allowed to accept non-public information like that in North America.

I agree about the need for I18N focus, but I will also ask the question about when a potential needs to know something? For places that want to know the race, or some other characteristic like gender identification (aka other than the traditional 2 choices), or military experience - do they need to know that eventually, or would you be immediately filtered out if not specified on the resume up front?

[thomasdavis]

The project has evolved to be ambiguous when considering localization and internalization.

Everything is largely contingent on themes, and everything else can be supplemented via new packages and the top level meta property.