Skip to content
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

How to link JobPostings to formal definitions of competencies #2322

philbarker opened this issue Aug 13, 2019 · 0 comments · Fixed by #2354


Copy link

@philbarker philbarker commented Aug 13, 2019

Increasingly sets of competencies for jobs and occupations are being formally defined in frameworks (see for example the National Initiative for Cybersecurity Education (NICE) Cybersecurity Workforce Framework). These may be available in human readable documents and as linked data. It should be possible to link JobPostings to these. Competencies are often classed by type, for example as: knowledge, skills, abilities, tasks that can be performed, attitudes, etc.

After discussion in the TalentSignal W3C Community Group, we suggest that the skills property can be used point to competencies of any type, and that information about the competency may be provided as a DefinedTerm.

So we suggest a redefinition of skills:
skills: A statement of knowledge, skill, ability, task or any other assertion expressing a competency that is desired or required to fulfill this role or in this occupation.
Expected types: DefinedTerm, Text, URL

There are examples on the TalentSignal wiki page.

This would mirror how competencies are handled by EducationalOccupationalCredential. An alternative would be extend the domain of competencyRequired so that it can be used on JobPostings and Occupation, but skills seems well established in use.

Any thoughts?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
None yet
1 participant
You can’t perform that action at this time.