You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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
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?
The text was updated successfully, but these errors were encountered:
philbarker
added a commit
to philbarker/schemaorg
that referenced
this issue
Oct 2, 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?
The text was updated successfully, but these errors were encountered: