Parser Output

Output Overview🔗︎

Default Sections🔗︎

By default, the resume parser will output the following sections:

Section Type	Description
Contact Info	The Contact Info section represents all contact related information such as name, phone number, address, etc.
Objective	Job Objective that was found in the resume
Position History	A list of all of the positions held by the candidate including employer, dates, descriptions, and a user area with metadata
Education	A list of all education related information including school type, school name, degree type, etc...
Licenses & Certifications	A list of all certifications and licenses found in the resume
Skills	A list of all of the skills found in the enabled sections of the resume. Output includes skill name, total months of use, last used date, where it was found in the document, and information about the taxonomy.
Languages	Includes information about the language the document was written in as well as the languages that a candidate can write/speak/read
Personal Information	This section includes date of birth, gender, mother tongue, nationality, visa, etc...
Training	A list of trainings specified in the resume
Achievements	A list of the achievements specified by the candidate
Associations	A list of the associations specified by the candidate along with their role
References	A list of references specified in the resume including contact info if specified
Hobbies	Outputs the text found pertaining to hobbies

Optional Sections🔗︎

There is very rarely a reason to parse for this data. If you don't have a specific use-case for this data, don't enable these sections.
Don't expect this data to be accurate. Expect this data to give you a sense that this person has a lot of speaking engagements, or this candidate has a lot of patents, or none at all. Don't expect this to give usable data to go find a publication in the library of congress.

By default, the resume parser won't output the following sections, but they can be enabled with a configuration setting that's documented in the configuration options link:

Section Type	Description
Patents	A list of patents specified in the document
Publications	A list of publications specified in the document
Speaking Engagements	A list of speaking engagements specified in the document
Security Credentials	A list of security credentials specified in the document
Military History	A list of military history specified in the document

Contact Info🔗︎

The Parser does not standardize addresses. Address standardization services are available, including for example the Google Maps API, that can take the Parser's contact info fields and standardize/geocode the data.

Contact Methods🔗︎

Each ContactMethod element allows one of each of the following sub-elements:

Use
Location
WhenAvailable
Telephone
Mobile
Fax
Pager
TTYTDD
InternetEmailAddress
InternetWebAddress
PostalAddress

If a resume contains more than one of the same type of these items, such as two Telephone numbers, then they must be reported in a separate ContactMethod object. For example:

"ContactMethod": [
    {
        "Use": "personal",
        "Location": "onPerson",
        "WhenAvailable": "anytime",
        "Mobile": {
        "FormattedNumber": "(858) 353-6553"
        }
    },
    {
        "Use": "business",
        "Location": "office",
        "Telephone": {
        "FormattedNumber": "(858) 678-8765"
        }
    },
    {
        "Use": "personal",
        "Location": "onPerson",
        "WhenAvailable": "anytime",
        "InternetEmailAddress": "missmadams@yahoo.com"
    },
    {
        "Use": "personal",
        "Location": "onPerson",
        "WhenAvailable": "anytime",
        "InternetEmailAddress": "missmadams@tdiff.com"
    },
    {
        "Use": "twitterHandle",
        "Location": "onPerson",
        "WhenAvailable": "anytime",
        "InternetWebAddress": "@twitQueen"
    }   
]

Phone Numbers🔗︎

The Parser outputs phone numbers in one of two forms: Formatted or Structured. Unfortunately, a single number cannot be represented in both forms in the current schema, so you must choose which to use. By default, the Parser only outputs FormattedNumber elements.

Textkernel provides the config string setting OutputFormat.TelcomNumber.Style to control the phone number output format. This setting accepts the following values:

OutputFormat.TelcomNumber.Style = Raw

OutputFormat.TelcomNumber.Style = Formatted

OutputFormat.TelcomNumber.Style = Structured

Raw (default)🔗︎

Output the number in a FormattedNumber element exactly as it appeared in the original document.

"Telephone": {
    "FormattedNumber": "(858) 678-8765"
}

Formatted🔗︎

Output the number in a FormattedNumber element in a normalized format, if possible; otherwise fallback to Raw. US/Canadian phone numbers are normalized to this format: (NNN) NNN-NNNN, or (NNN) NNN-NNNN x NNN when an extension is included.

"Telephone": {
    "FormattedNumber": "(858) 678-8765"
}

Structured🔗︎

Output in the multi-element structured format, if possible; otherwise fallback to Formatted.

"Telephone": {
    "InternationalCountryCode": "1",
    "AreaCityCode": "858",
    "SubscriberNumber": "678-8765"
}

The Formatted and Structured settings currently only apply to US/Canadian numbers. Due to the hugely varied colloquial formats of phone numbers in other countries, we have been unable to reliably normalize the number parts. As a consequence, even if you set the style to Structured , you will still get some FormattedNumber elements in the output, so your code will need to handle both cases.

Normalize Region🔗︎

By default, the Parser reports the Region as it was detected in the document. When this setting is turned on ( OutputFormat.NormalizeRegions = True), the parser normalizes Region values to the standard postal abbreviations. For example, 'Texas' to 'TX'. This setting currently only applies to US states and Canadian provinces.

Position History🔗︎

Job Categories🔗︎

The following type of output is always generated for each PositionHistory element:

"JobCategory": [
    {
        "TaxonomyName": "Skills taxonomy",
        "CategoryCode": "Information Technology → Internet",
        "Comments": "Information Technology describes 79% of this job"
    },
    {
        "TaxonomyName": "Job Level",
        "CategoryCode": "Executive (VP, Dept Head)"
    }
]

For Job Level , the CategoryCode is one of the following values, based on the length of experience and job titles:

Low Level
Entry Level
Experienced (non-manager)
Senior (more than 5 years experience)
Manager
Senior Manager (more than 5 years management experience)
Executive (VP, Dept. Head)
Senior Executive (President, C-level)

Stripping Out Reported Data from Jobs🔗︎

By default, the PositionHistory/Description element includes the descriptive text that is related to a particular PositionHistory element, but not including the portion which contains the title, company, location and date. If you want the Description element to have all of the text associated with a position, including the parsed data points, then set this option to false.

See below that the default behavior strips this text from the “Description” node:

    Technical Difference        October 2004 - Current
    Director of Web Applications Development

While this works well for most resumes, it can cause problems with some resumes that do not have all the data points together. Some data may be buried far away from other data, or at the end of the description, and in such cases, more data will be stripped out than expected, leaving an incomplete Description.

Strip Parsed Data🔗︎

OutputFormat.StripParsedDataFromPositionHistoryDescription = true - Default Value

"PositionHistory": [
    {
        "@positionType": "directHire",
        "@currentEmployer": "true",
        "Title": "Director of Web Applications Development",
        "OrgName": {
        "OrganizationName": "Technical Difference"
        },
        ...,
        "Description": "• Add new technology to website to manage leads, increase response time and provide pertinent information...",
    }

Include Parsed Data🔗︎

OutputFormat.StripParsedDataFromPositionHistoryDescription = false

"PositionHistory": [
    {
        "@positionType": "directHire",
        "@currentEmployer": "true",
        "Title": "Director of Web Applications Development",
        "OrgName": {
        "OrganizationName": "Technical Difference"
        },
        ...,
        "Description": "Technical Difference Solana Beach, California\tOctober 2004 - Current Director of Web Applications Development • Add new technology to website to manage leads, increase response time and provide pertinent information...",
    }

Reformat PositionHistory Description🔗︎

By default, the PositionHistory/Description element retains as much of the original formatting as possible. For example:

• Add new technology to website to manage leads, increase response time and provide pertinent information to new customers.
• Convert current HRIS from VB to ASP to create complete web based solution.
• Added custom encryption coding to SQL and ASP web applications.
• Designed custom applicant tracking ASP program for large client.
• Designed customer support application to receive requests/files from clients, divert to appropriate support staff, and track issue from open to resolve.

When this settings is enabled (OutputFormat.ReformatPositionHistoryDescription = True) the Parser will remove blank lines, split long paragraphs into separate lines, and other reformatting techniques intended to place each achievement on a separate line. Example:

Add new technology to website to manage leads, increase response time and provide pertinent information to new customers.

Convert current HRIS from VB to ASP to create complete web based solution.

Added custom encryption coding to SQL and ASP web applications.

Designed custom applicant tracking ASP program for large client.

Designed customer support application to receive requests/files from clients, divert to appropriate support staff, and track issue from open to resolve.

Prefer Shorter Position Titles🔗︎

By default, this setting is turned off and the parser reports position titles exactly as they are found in the document. When true (OutputFormat.PreferShorterPositionTitles = True), titles may be truncated if the additional phrase does not include Job words. For example, VICE PRESIDENT, INFORMATION SYSTEMS would be reported as just VICE PRESIDENT if this switch is set to true.

Position History User Area🔗︎

UserArea elements throughout the schema are populated with Textkernel generated metadata. These sections are documented in this document and defined in the SovrenResumeExtensions.xsd file.

The UserArea content for PositionHistory elements is located at Resume.StructuredXMLResume.EmployerOrg.PositionHistory.UserArea.sov:PositionHistoryUserArea. This is what a typical PositionHistoryUserArea element looks like:

"sov:PositionHistoryUserArea": {
    "sov:Id": "POS-1",
    "sov:CompanyNameProbabilityInterpretation": {
        "@internalUseOnly": "SP",
        "#text": "Confident"
    },
    "sov:PositionTitleProbabilityInterpretation": {
        "@internalUseOnly": "TT",
        "#text": "Confident"
    },
    "sov:NormalizedOrganizationName": "Technical Difference",
    "sov:NormalizedTitle": "Director of Web Applications Development",
    "sov:Subtitles": {
        "sov:Subtitle": [
        "Director"
        ]
    }
}

Id🔗︎

Id is a unique identifier assigned to each PositionHistory. Competency elements list the identifier of each PositionHistory element they were found within. The format of the identifier is POS-#, where # is a number that starts at 1 for the first PositionHistory and increments by 1 for each subsequent PositionHistory.

CompanyNameProbabilityInterpretation🔗︎

CompanyNameProbabilityInterpretation represents the degree of certainty that the OrganizationName element value is accurate. The following scale is used:

Value	Recommended Actions
VeryUnlikely	Recommend Discarding
Unlikely	Recommend Discarding
Probable	Recommend Review
Confident	No Action Needed

The Parser only reports names having a probability of 'Probable' or 'Confident', thus if the CompanyNameProbabilityInterpretation is 'Unlikely' or 'VeryUnlikely', then the OrganizationName will not be reported.

PositionTitleProbabilityInterpretation🔗︎

PositionTitleProbabilityInterpretation represents the degree of certainty that the Title element value is accurate. This value uses the same scale described above for CompanyNameProbabilityInterpretation.

IsSelfEmployed🔗︎

IsSelfEmployed is true when this is a self-employed position; otherwise it is false.

SelfEmploymentPhrase🔗︎

When IsSelfEmployed is true, SelfEmploymentPhrase contains the exact text from the resume that indicates this is a self-employed position.

NumberOfEmployeesSupervised🔗︎

NumberOfEmployeesSupervised is the number of employees that the candidate supervised in this position.

NormalizedOrganizationName🔗︎

The normalized OrganizationName.

NormalizedTitle🔗︎

The normalized PositionTitle.

Subtitles🔗︎

Any number of subtitles that could be used to categorize the position title. These are useful for grouping positions that have similar titles into buckets for searching and matching.

Bullets🔗︎

When OutputFormat.CreateBullets = true in the config string, the UserArea will include a "bullet" based interpretation of the Description text in which each significant sentence/line/paragraph is reported as a separate sov:Bullet element. This can be useful when transforming the output into a standard resume document format and you want each major point to be a bullet.

The type attribute of each sov:Bullet element is one of the following values:

creativeTerm: Bullet text contains one of the phrases from the CREATIVE_ACTION_WORDS data list (such as “implemented”, “initiated”, and “developer on”).
sentence: This is the default when the type is not creativeTerm.

Here is an example of the output with this feature turned on:

"sov:PositionHistoryUserArea": {
    "sov:Id": "POS-1",
    ...,
    "sov:Bullets": {
        "sov:Bullet": [
        {
            "@type": "sentence",
            "#text": "Add new technology to website to manage leads, increase response time and provide pertinent information to new customers"
        },
        {
            "@type": "sentence",
            "#text": "Convert current HRIS from VB to ASP to create complete web based solution"
        },
        {
            "@type": "sentence",
            "#text": "Added custom encryption coding to SQL and ASP web applications"
        },
        {
            "@type": "creativeTerm",
            "#text": "Designed custom applicant tracking ASP program for large client"
        },
        {
            "@type": "creativeTerm",
            "#text": "Designed customer support application to receive requests/files from clients, divert to appropriate support staff, and track issue from open to resolve"
        }
        ]
    }
}

Education🔗︎

Info

There are no configuration options for this section type. Here is an explanation of the output.

Degrees🔗︎

The Parser reports the level of education in the degreeType field of the Degree element.

These values are not very global-friendly, but the Parser does normalize all degrees to one of these pre-defined degreeTypes. This list is sorted, as well as possible, by increasing level of education. Although, there are certainly ambiguities from one discipline to another, such as whether professional is above or below masters Here are the possible values:

specialeducation
some high school or equivalent
ged
secondary
high school or equivalent
certification
vocational
some college
HND/HNC or equivalent
associates
international
bachelors
some post-graduate
masters
intermediategraduate
professional
postprofessional
doctorate
postdoctorate

School Types🔗︎

"EducationHistory": {
    "SchoolOrInstitution": [
        {
        "@schoolType": "university",
        "School": [
            {
            "SchoolName": "California State University"
            }
        ],
        ...
        }
    ],
    ...
}

The Parser uses an enum with the following values to represent school type:

UNSPECIFIED
lowerSchool
highschool
secondary
trade
community
college
university
professional
vocational

Degree User Area🔗︎

The Parser outputs additional metadata for the degree section. These sections are documented in this document and defined in the SovrenResumeExtensions.xsd file.

The UserArea content for Degree elements is located at Resume.StructuredXMLResume.EducationHistory.Degree.UserArea.sov:DegreeUserArea. This is what a typical DegreeUserArea element looks like:

"sov:DegreeUserArea": {
    "sov:Id": "DEG-1",
    "sov:Graduated": false,
    "sov:NormalizedGPA": "0.915",
    "sov:NormalizedDegreeName": "BSc",
    "sov:NormalizedDegreeType": "BSc"
}

Id🔗︎

Id is a unique identifier assigned to each Degree. Competency elements list the identifier of each Degree element they were found within. The format of the identifier is DEG-#, where # is a number that starts at 1 for the first Degree and increments by 1 for each subsequent Degree.

Graduated🔗︎

Graduated is a Boolean value that indicates whether the degree was completed. It is not always safe to assume that just because a degree is listed it was completed, and there is usually not enough information to determine graduation status from the resume itself, but some candidates do report that they didn’t finish (or haven’t yet finished) the degree. Possible values:

Element is not output, indicating that the Parser has no information.
false: Indicating that the degree was not completed or the candidate is still pursuing the degree.
true: Indicates that the degree was completed.

NormalizedGPA🔗︎

NormalizedGPA is a decimal value that is output only when a GPA has been provided. This value is normalized from 0.0 to 1.0, with 1.0 being the top mark, so that all GPAs across all scales can be compared, taking into account different min/max values and whether high or low numbers are ranked higher. For example:

USA degree with GPA of 3.5 / 4.0 = 0.875
German degree with 1.5 / 6.0 = 0.916

Licenses & Certifications🔗︎

Info

There are no configuration options for this section type. Here is an explanation of the output.

Licenses and certifications are reported in LicenseOrCertification elements found within Resume.StructuredXMLResume.LicensesAndCertifications.

"LicensesAndCertifications": {
    "LicenseOrCertification": [
        {
            "Name": "Project Management Professional",
            "Description": "certification; found in CERTIFICATIONS",
            "EffectiveDate": {
                "FirstIssuedDate": {
                "YearMonth": "2020-09"
                }
            }
        }
    ]
}

Name🔗︎

The name or phrase that describes the license or certification. This value is not standardized or mapped to any pre-defined list.

Description🔗︎

This element reports additional information about the license or certification. It is one of the following values, where the text in square brackets is conditionally output depending on the context:

license[; found in LICENSES][; matched to list]
certification[; found in CERTIFICATIONS][; matched to list]

The “found in LICENSES” note indicates that the license was found when parsing the text of a LICENSES section.

The “found in CERTIFICATIONS” note indicates that the certification was found when parsing the text of a CERTIFICATIONS section.

The “matched to list” note indicates that the license was found anywhere within the text of the resume/CV based on matching a specific keyword, key phrase, or pattern as defined in one of the Parser’s data lists.

EffectiveDate.FirstIssuedDate🔗︎

The date of the license or certification, if any.

EffectiveDate.ValidFrom & EffectiveDate.ValidTo🔗︎

The effective date range, if any.

Skills🔗︎

Where To Look For Skills🔗︎

By default, the parser looks in the following sections for skills:

Section Type	Config String To Turn Section Off
Achievements	`Coverage.FindSkillsInAchievements = False`
Certifications	`Coverage.FindSkillsInCertifications = False`
Cover Letter	`Coverage.FindSkillsInCoverLetter = False`
Education	`Coverage.FindSkillsInEducationHistory = False`
Executive Summary	`Coverage.FindSkillsInExecutiveSummary = False`
Languages	`Coverage.FindSkillsInLanguages = False`
Licenses	`Coverage.FindSkillsInLicenses = False`

Also Report These As Skills🔗︎

By default, the parser doesn't report any of these data types as skills. To report any of the following data types as skills refer to the config string value in the table.

Section Type	Config String To Report Data Type as Skill
Position Titles	`Coverage.AddPositionTitlesToSkills = True`
Languages	`Coverage.AddLanguagesToSkills = True`
Licenses & Certifications	`Coverage.AddCertificationsAndLicensesToSkills = True`

Skills Taxonomy Output🔗︎

This section contains the skill/competency data in the Textkernel-preferred format. You may prefer to consume this data rather than the data in the Competencies section or use a combination of both. Note that both sections contain the same data, only the format is different.

"sov:SkillsTaxonomyOutput": {
    "sov:TaxonomyRoot": [
        {
            "@name": "Sovren",
            "sov:Taxonomy": [
                {
                    "@name": "Information Technology",
                    "@id": "10",
                    "@percentOfOverall": "80",
                    "sov:Subtaxonomy": [
                        {
                            "@name": "Programming",
                            "@id": "204",
                            "@percentOfOverall": "23",
                            "@percentOfParentTaxonomy": "29",
                            "sov:Skill": [
                                {
                                    "@name": "APPLICATIONS DEVELOPMENT",
                                    "@id": "021803",
                                    "@existsInText": "true",
                                    "@totalMonths": "191",
                                    "@lastUsed": "2020-09-09",
                                    "@whereFound": "Found in WORK HISTORY; POS-1"
                                },
                                {
                                    "@name": "CODING",
                                    "@id": "013739",
                                    "@existsInText": "true",
                                    "@totalMonths": "191",
                                    "@lastUsed": "2020-09-09",
                                    "@whereFound": "Found in WORK HISTORY; POS-1"
                                },
                                {
                                    "@name": "HTML",
                                    "@id": "019115",
                                    "@existsInText": "true",
                                    "@whereFound": "Found in WORK HISTORY"
                                },
                                {
                                    "@name": "JAVASCRIPT",
                                    "@id": "025394",
                                    "@existsInText": "true",
                                    "@whereFound": "Found in WORK HISTORY"
                                },
                                {
                                    "@name": "PHP",
                                    "@id": "004736",
                                    "@existsInText": "true",
                                    "@whereFound": "Found in WORK HISTORY"
                                },
                                {
                                    "@name": "VBSCRIPT",
                                    "@id": "010438",
                                    "@existsInText": "true",
                                    "@whereFound": "Found in WORK HISTORY"
                                },
                                {
                                    "@name": "XML",
                                    "@id": "011476",
                                    "@existsInText": "true",
                                    "@whereFound": "Found in WORK HISTORY"
                                }
                            ]
                        }
                    ]
                }
            ],
            ...
        }
    ]
}

As you can see above, this view of the skills is structured in the hierarchical manner that matches the Taxonomy > Subtaxonomy > Skill > Child Skill structure that the parser understands. By default, there will only be one TaxonomyRoot, "Sovren".

The following table lists the elements and attributes associated with each of the elements above.

Element.Attribute	Meaning
*.name	Name of the root data list/taxonomy/subtaxonomy/skill.
(Taxonomy	Subtaxonomy).id
(Taxonomy	Subtaxonomy).percentOfOverall
Subtaxonomy.percentOfParentTaxonomy	The weight of a specific subtaxonomy (and its children) divided by the weight of its parent taxonomy, expressed as a percentage. The sum of all percentOfParent values for all siblings (subtaxonomies with the same parent) equals 100%.
(Skill	ChildSkill).existsInText
(Skill	ChildSkill).whereFound
(Skill	ChildSkill).lastUsed
(Skill	ChildSkill).totalMonths
Skill.childrenLastUsed	Most recent date that any of the skill's children were used.
Skill.childrenTotalMonths	Sum of all the ChildSkill.totalMonths (accounting for overlaps) for all of this skill's children.

Languages & Locales🔗︎

The Parser includes a language and locale analyzer that is able to accurately detect all supported Parser languages and can detect and set most supported locales based on an analysis of language, phone numbers, and email addresses. It is NEVER necessary or advisable to manually override the Parser's language detection, and it is rarely advisable to override the Parser's locale detection.

For a listing of languages and regions supported, you can refer here.

So, when might it be advisable to override the default locale detection? In some cases, you may be certain that you are parsing a CV from a particular locale and you want to ensure that the Parser "knows" about that locale even if the CV does not have any information on it that would readily tell it that it is from that locale (for example, if the CV contains no contact info).

Here is an example: if you are processing CVs in or from Australia, Australia uses a four-digit postal code. You may desire to set Culture.DefaultCountryCode = AU in the config string. This will give better results on a few Australian CVs that lack enough contact info for the Parser to detect that the CV contains Australian locale data. HOWEVER, a side effect is that, when that switch is "on" and a non-Australian CV is parsed, the Parser may erroneously report Australian contact info rather than the correct locale's contact info. For instance:

John Smith
Suite 404
3017 Sydney
Dallas, TX 75225

This is actually a USA address, and will possibly be reported by the Parser as being an address in postal code 3017 in Sydney, Australia rather than at 3017 Sydney Street in Dallas, Texas, USA in postal code 75225.

Our general recommendation is that only the following locale switches are advisable to set "on", and then only when the CV is almost certain to contain that locale’s data:

Set Culture.DefaultCountryCode = IN if you are parsing in India
Set Culture.DefaultCountryCode = AU if parsing in Australia or New Zealand (you can use either AU or NZ) and you have Australian or New Zealand locale CVs
Set Culture.DefaultCountryCode = ZA if you are parsing in South Africa

Again, setting these switches assumes that you really have a CV flow that is almost completely from those regions.

Please note that the Parser always outputs a "CountryCode" every time it reports any location information. Unfortunately, it is not always possible to accurately determine the correct country code (Boston, UK or Boston, USA?), so at times the Parser must make an educated guess since it is required by that standard to report a CountryCode.

Personal Information🔗︎

The PersonalInformation element contains a variety of information that is commonly used in some cultures and not in other cultures such as the United States. The parser will output the following data fields:

Ancestor (FathersName and MothersMaidenName)
Availability
Birthplace
DateOfBirth
DrivingLicense
FamilyComposition
Gender
Hukou (HukouCity and HukouArea)
Location (CurrentLocation and PreferredLocation)
MaritalStatus
MessagingAddresses
MotherTongue
NationalIdentityNumber
Nationality
Passport
Politics
Salary (CurrentSalary and RequiredSalary)
Visa

Some of the personal information can be inferred from other information within the resume. For example, Gender may be inferred from “Mr.” being part of the name.

Here is a sample PersonalInformation element containing every element that is supported:

"sov:PersonalInformation": {
    "sov:DateOfBirth": {
        "@inferred": "false",
        "#text": "1977-10-20"
    },
    "sov:Birthplace": "Los Angeles, CA",
    "sov:Nationality": {
        "@inferred": "false",
        "#text": "US"
    },
    "sov:NationalIdentities": {
        "sov:NationalIdentity": [
        {
            "sov:NationalIdentityNumber": "111-22-3333",
            "sov:NationalIdentityPhrase": "SSN"
        }
        ]
    },
    "sov:Gender": {
        "@inferred": "false",
        "#text": "Female"
    },
    "sov:MaritalStatus": {
        "@inferred": "false",
        "#text": "Married"
    },
    "sov:DrivingLicense": "CA-123123123",
    "sov:CurrentLocation": "Solana Beach, CA",
    "sov:PreferredLocation": "Boston, MA",
    "sov:WillingToRelocate": "Yes",
    "sov:FamilyComposition": "Family Composition: Husband and 2 children",
    "sov:FathersName": "John Adams, II",
    "sov:MothersMaidenName": "Angela Harris",
    "sov:Availability": "Immediate, with 2 weeks notice",
    "sov:VisaStatus": "Green Card, expires march 2022",
    "sov:PassportNumber": "US-456456456",
    "sov:CurrentSalary": {
        "@currency": "USD",
        "#text": "100000.00"
    },
    "sov:RequiredSalary": {
        "@currency": "USD",
        "#text": "110000.00"
    },
    "sov:HukouCity" : "湛江市",
    "sov:HukouArea" : "海南",
    "sov:MessagingAddress" : {
        "@type": "ICQ",
        "#text": "john3@adams.com"
    },
    "sov:MotherTongue": "en"
}

DateOfBirth🔗︎

Date of birth in yyyy-MM-dd format. If the optional inferred attribute (Boolean) is true then the DateOfBirth was inferred from an Age using the following formula: [RevisionDate] - [Age years] - [6 months]

Birthplace🔗︎

Freeform text that identifies the candidate’s place of birth.

Nationality🔗︎

Freeform text that identifies the candidate’s country of citizenship. If the optional inferred attribute (Boolean) is true then the Nationality was inferred rather than explicitly stated.

NationalIdentities🔗︎

Zero or more NationalIdentity elements.

NationalIdentityNumber🔗︎

Country-specific national identity number. In order to prevent false positives, the Parser requires that the numbers be in specific formats. If numbers are not being reported, it may be due to the number being in an unsupported format. We will continue adding support for new formats, so please submit any examples to support@textkernel.com.

NationalIdentityPhrase🔗︎

An optional phrase associated with the NationalIdentityNumber to help identify it.

NationalIdentityType🔗︎

Currently only “DNI” or “NIE” if issued by Spain.

Gender🔗︎

Male or Female. If the optional inferred attribute (Boolean) is true then the Gender was inferred from the name affix, marital status, national identity number, given name, or some other means. To customize the inference by given name, customize the MALE_GIVEN_NAMES and FEMALE_GIVEN_NAMES data lists.

MaritalStatus🔗︎

Married, Single, Divorced, Separated, or Unknown. If the optional inferred attribute (Boolean) is true then the MaritalStatus was inferred from the name affix, family composition, national identity number, or some other means.

DrivingLicense🔗︎

Freeform text that identifies the candidate’s license to drive. May include a license number, type, qualifications, restrictions or any other explanation.

CurrentLocation🔗︎

Freeform text that identifies the candidate’s current location(s), if specifically stated as such. This value is NOT derived from the contact information postal address.

PreferredLocation🔗︎

Freeform text that identifies the candidate’s preferred location(s).

WillingToRelocate🔗︎

One of the following values indicating the candidate’s willingness to relocate: Yes, No, or Unknown.

FamilyComposition🔗︎

Freeform text that describes the candidate’s family, such as spouse and children.

FathersName🔗︎

Freeform text that identifies the name of the candidate’s father.

MothersMaidenName🔗︎

Freeform text that identifies the maiden name of the candidate’s mother.

Availability🔗︎

Freeform text that describes when the candidate is available to work.

VisaStatus🔗︎

Freeform text that describes the candidate’s current visa status, expiry date, etc.

PassportNumber🔗︎

Freeform text that identifies the candidate’s passport number, expiry date, etc.

CurrentSalary🔗︎

The candidate’s current salary expressed as a monetary amount. The element value is a number. The type attribute is a 3-letter ISO 4217 currency code. For a complete list of codes, search the web for "ISO 4217 currency codes". This element does not specify whether the monetary amount is annually, monthly, or hourly, however that information can usually be inferred from the value.

RequiredSalary🔗︎

The salary the candidate expects for any new position, expressed as a monetary amount. The element value is a number. The type attribute is a 3-letter ISO 4217 currency code. For a complete list of codes, search the web for "ISO 4217 currency codes". This element does not specify whether the monetary amount is annually, monthly, or hourly, however that information can usually be inferred from the value.

HukouCity🔗︎

Name of City for Chinese household registration (hukou record).

HukouArea🔗︎

Area/Province for Chinese household registration (hukou record).

MessagingAddress🔗︎

Zero or more MessagingAddress elements. The type attribute identifies the messaging system, such as ICQ, MESSENGER, QQ, etc. The element value is the candidate’s address within that messaging system.

MotherTongue🔗︎

The mother tongue (also known as primary language, native language, or first language) of the candidate. The value is one of the ISO 639-1 codes. For example: Dutch (nl), English (en), French (fr), or the special value Invariant/Unknown (iv).

Training🔗︎

The Parser will report training elements that are found in the document. For example, this text appearing within a Position Description will also be reported in the Training element of the UserArea as shown in the box below:

Training:
Project Management Professional, Project Management Institute, 2004-2005
Microsoft Visual Basic .NET, 2001

"sov:TrainingHistory": {
    "sov:Text": "Project Management Professional, Project Management Institute, 2004-2005 Microsoft Visual Basic .NET, 2001",
    "sov:Training": [
      {
        "sov:Type": "Unknown",
        "sov:TrainingName": null,
        "sov:Qualifications": {
          "sov:Qualification": [
            "Project Management Professional"
          ]
        },
        "sov:Entity": null,
        "sov:Description": "Project Management Professional, Project Management Institute, 2004-2005",
        "sov:StartDate": {
          "Year": "2004"
        },
        "sov:EndDate": {
          "Year": "2005"
        }
      },
      {
        "sov:Type": "Unknown",
        "sov:TrainingName": null,
        "sov:Entity": null,
        "sov:Description": "Microsoft Visual Basic .NET, 2001",
        "sov:EndDate": {
          "Year": "2001"
        }
      }
    ]
  }

Each distinct item of training is reported as an Item element within Training.

Type🔗︎

Reserved for future use.

TrainingName🔗︎

Reserved for future use.

Qualifications🔗︎

Any text within Description that is recognized as a qualification (such as DDS), degree (such as B.S.), or a certification (such as Project Management Professional). Each qualification is listed separately.

Entity🔗︎

Name of school or company

Description🔗︎

All of the text associated with this training item.

StartDate🔗︎

Start date of this training item.

EndDate🔗︎

End date of this training item.

Patents/Publications/Speaking Engagements🔗︎

When parsing of Patents, Publications, and Speaking Engagements is enabled, by setting Coverage.PatentsPublicationsAndSpeakingEvents = True in the config string, these sections may be reported.

These sections are impossible to parse at a granular level with any meaningful accuracy. Do not use this data except perhaps as an indicator that the document contains such sections.