Controlled value spaces from entities such as ONet and HR Open Standards should be modeled as RDF using W3C's Simple Knowledge Organization System [SKOS]. I have illustrated use of SKOS below with a single ONet concept--"Logistics Manager". Note that SKOS is comprised of two straight forward classes: skos:ConceptScheme and skos:Concept. Each concept declares itself to be a member of the concept scheme via the propertyskos:inScheme. Most ONet concept schemes are flat enumerations. However, where there is hierarchical structures, SKOS provides two properties for relating broader and narrower concepts --skos:broader and skos:narrower...pretty simple but powerful.
SKOS is also extensible using any RDF property. To illustrate, I used jdx:jobTitle to add an array of example job titles from ONet for the concept "Logistics Manager". With the exception of the ONet concept schemes --"knowledge", "skills", "abilities"-- all enumerations in ONet can be locally encoded using SKOS. Code lists from HR Open Standards can also be encoded using SKOS.
Note the use of the property jdx:source to create a digital thread that links this SKOS concept back to the ONet source.
Controlled value spaces from entities such as ONet and HR Open Standards should be modeled as RDF using W3C's Simple Knowledge Organization System [SKOS]. I have illustrated use of SKOS below with a single ONet concept--"Logistics Manager". Note that SKOS is comprised of two straight forward classes:
skos:ConceptScheme
andskos:Concept
. Each concept declares itself to be a member of the concept scheme via the propertyskos:inScheme
. Most ONet concept schemes are flat enumerations. However, where there is hierarchical structures, SKOS provides two properties for relating broader and narrower concepts --skos:broader
andskos:narrower
...pretty simple but powerful.SKOS is also extensible using any RDF property. To illustrate, I used
jdx:jobTitle
to add an array of example job titles from ONet for the concept "Logistics Manager". With the exception of the ONet concept schemes --"knowledge", "skills", "abilities"-- all enumerations in ONet can be locally encoded using SKOS. Code lists from HR Open Standards can also be encoded using SKOS.Note the use of the property
jdx:source
to create a digital thread that links this SKOS concept back to the ONet source.