W3C home > Mailing lists > Public > public-talent-signal@w3.org > July 2019

[Talent-Signal] relating competencies to job postings

From: Phil Barker <phil.barker@pjjk.co.uk>
Date: Wed, 3 Jul 2019 12:24:09 +0100
To: "public-talent-signal@w3.org" <public-talent-signal@w3.org>
Message-ID: <6c1fabb8-49a2-59ac-5a4d-f7a678f795e4@pjjk.co.uk>
Hello all,

I know that many of you are about start a holiday; and after that I will 
be on vacation. So this may not be the best time to start a 
conversation, but I want to post this now to see what I come back to...

One of the issues we have listed is how to refer skills requirements to 
competency definitions in a standard framework.

I have drafted on the wiki a straw man for a simple way of doing this 
[1] with minimal change to what currently exists in schema.org. It 
requires only that the expected type for one property be changed.

   "@context": "http://schema.org/",
   "@type": "JobPosting",
   "title": "Junior software developer",
   "skills": {
     "@type": "Definedterm",
     "termCode": "K0016",
     "description": "Knowledge of computer programming principles",
     "inDefinedTermSet": {
       "@type": "DefinedTermSet",
       "name": "National Initiative for Cybersecurity Education (NICE) Cybersecurity Workforce Framework",
       "url": "https://doi.org/10.6028/NIST.SP.800-181",
       "publisher": {
         "@type": "Organization",
         "name": "National Institute of Standards and Technology"
       "datePublished": "2017-08"

Points to note / consider

* this doesn't attempt to fully describe the competency, that's the job 
of the framework. Furthermore this approach is pretty much agnostic to 
the format used to represent the framework--I mean, it would be nice if 
a linked-data friendly format were used and we can then link properly to 
its @id but this example is a pdf.

* is there any other key information that is required to identify the 
competence being referred to?

* I've used the existing schema.org property skills to cover a 
competency that is defined as 'knowledge'. I know the KSA approach to 
competencies, but also that other aspects can be added 
(tools/technologies, attitudes) an other approaches taken. Can we live 
with lumping these together under the label skills, or do we have to 
look into creating a property with a different name? We will be somewhat 
constrained by existing schema.org usage. Also I think that trying to 
separate out the different aspects of competence would cause 
difficulties when implemented in the non-specialist schema.org context. 
Remember, the competence framework is where the information should be 
provided about what aspect of competence (knowledge, skill or ability) 
is being referred to.

Best wishes to all celebrating the 4 July.




Phil Barker <http://people.pjjk.net/phil>. http://people.pjjk.net/phil
CETIS LLP <https://www.cetis.org.uk>: a cooperative consultancy for 
innovation in education technology.
PJJK Limited <https://www.pjjk.co.uk>: technology to enhance learning; 
information systems for education.

CETIS is a co-operative limited liability partnership, registered in 
England number OC399090
PJJK Limited is registered in Scotland as a private limited company, 
number SC569282.
Received on Wednesday, 3 July 2019 11:24:36 UTC

This archive was generated by hypermail 2.4.0 : Friday, 17 January 2020 17:33:34 UTC