Accreditation

Can be used to specify: - the agent that was primarily responsible for the accreditation - the date the accreditation was formally approved - a review date or expiry date - related documents with additional information about the accreditation or used standards and procedures in the assessment and quality assurance of the qualificationThe accreditation class is used to specify information related to the accreditation, monitoring and quality assurance of a qualification and/or awarding body

• Class

Additional note

• ObjectProperty

association from

The resource being described (the resource the association starts from e.g. a qualification). This property entails the inverse property http://data.europa.eu/esco/model#hasAssociation.

• FunctionalProperty
• ObjectProperty

Association object

The generic class of extended directed associative relationships from a resource to a semantic asset.This class relates a qualification to a node from another established framework or classification system. This allows to specify metadata on the association: - The relationship type (describing the semantics of the association) is given by the dcterms:type property using a skos:Concept from the controlled vocabulary <http://data.europa.eu/esco/concept-scheme/association-type>. - The framework and/or classification system to which the related semantic asset belongs is given by the esco:targetFramework property. - The resource being described (the resource the association starts from e.g. a qualification) is given by esco:isAssociationFor and the associated resource by esco:target."@en; rdfs:comment "Used to express a learning outcome of a qualification as a relation from a qualification to an ESCO skill, competence or knowdledge (see <http://data.europa.eu/esco/association-type#learning-outcome>)."@en; rdfs:comment "Used to related a qualification to an occupation from an international, national or regional occupation classification system (see <http://data.europa.eu/esco/association-type#related-occupation>)."@en; rdfs:comment "Used to link a qualification to a international, national or regional qualification framework level (see <http://data.europa.eu/esco/association-type#qf-level>)."@en; rdfs:comment "List of properties: - dcterms:type (0..1) - dcterms:description (0..n) - dcterms:issued (0..1) - esco:targetFramework (1..1) - esco:isAssociationFor (1..1) - esco:target (0..1) - esco:targetDescription (0..n) - esco:targetNotation(0..n) - esco:targetName(0..n) - esco:targetURL (0..1)

• Class

association to

The associated resource. Refers to a node (e.g. a skos:Concept) in another established framework (e.g. a skill or occupation from the ESCO classification, a skill or occupation from the national classification system, the qualification level according the national qualification framework,…).

• FunctionalProperty
• ObjectProperty

association type

The class of association types used in the metadata schema. The relations from a qualification to other semantic assets (nodes from other semantic frameworks and or classification systems) are 'typed relations'. The different association types and their semantics in the metadata schema are SKOS Concepts that are part of a taxonomy managed by the metadata schema (see <http://data.europa.eu/esco/concept-scheme/association-type>)

• Class

Awarding Bodies Concept Scheme

• Concept Scheme
• Instance

Awarding activity

An awarding activity represents an activity related to the awarding of a qualification. It is used to specify an awarding body, a country or region where the qualification is awarded and optionally an awarding period.

• Class

Awarding body

"Additional properties defined by the QMS are: - dcterms:spatial (0..1) main site locationAn awarding body is an institution, organization or company that is recognised (official or otherwise) for issuing qualifications (certificates, diplomas or titles) and formally recognising the learning outcomes (knowledge, skills and/or competences) of an individual, following an assessment and validation procedure.For the minimal set of properties on an AwardingBody see usage note http://xmlns.com/foaf/0.1/Agent.

• Class

awarding body (descriptive)

An awarding body provided using a descriptive text. A more precise definition of an awarding body known by ESCO can be given using http://data.europa.eu/esco/model#hasAwardingBody

• DatatypeProperty

belongs to ISCO Group with code

The direct hierarchical broader ISCO concept of the (subject) ESCO occupation. The 'direct' (or one step) relationship is to be understood in terms of extending the ISCO taxonomy the (object) concept belongs to. The ISCO concept may be of any ISCO version. The ISCO version can be determined by the inScheme property on the ISCO concept and the version information on the ISCO concept scheme (referenced by the object - i.e. by the ISCO concept).

• ObjectProperty

broader instance

The Leaf Group the (subject) ESCO member concept (Skill or Occupation or Qualification) belongs to. Only member properties having a Leaf Group type as broader concept must have this property, Specializations of member concepts (like Faceted Concepts) do not have this property.

• ObjectProperty

can have work context

The possible working context of the (subject) occupation.

• ObjectProperty

Competence sub-type

Sub-Typing of a Skill Concept: - Skill/Competence - Knowledge

• Class

compound term

A compound equivalence label for the subject concept. The subject concept is a Simple ESCO concept used as a component of a Faceted ESCO concept (i.e. a compound concept). The label of this faceted concept is a compound term (i.e. a split non preferred term) and the value of esco:plusUF (i.e. a UF++). There can be any number of compound terms per language and per faceted concept.

• ObjectProperty

Concept scheme (ESCO pillar)

The ESCO concept schemes (pillars) The "current" ESCO scheme and historic versions of the ESCO scheme will be instances of this class. Typically, these support poly-hierarchy. The ISCO representations that are the backbone of at least one ESCO version (v0) also will be represented by this concept scheme. Typically these do not have poly-hierarchy. Provenance information that may be added: - rightsHolder: the owner (http://purl.org/dc/terms/rightsHolder) - required - publishing status: (http://purl.org/iso25964/skos-thes#status) - required - creator : the author (http://purl.org/dc/terms/creator) - required - contributor : modifier (http://purl.org/dc/terms/contributor) - required - modified : last modification date (http://purl.org/dc/terms/modified) - required

• Class

constructed from ESCO concept

The unique (simple) ESCO concept used to construct the (subject) faceted ESCO concept. Example (started): Simple concept Teacher is specialized to identify teacher at different education levels. - The simple (member) occupation is: "Teacher" - Assume we have a classification of the levels of education (e.g. "primary school", "high school", "university") - The constructed faceted (member) concepts that will be: "primary school teacher", "high school teacher" and "university teacher" (this last one occasionally re-labeled as "university professor") - Each of the constructed faceted (member) concepts will indicate the "teacher" also as a skos:broader concept. - Each of the constructed faceted (member) concepts will indicate the "teacher" as the esco:constructedFrom concept. Example (completed): Nesting facets - Teacher of a subject at a school level - Assume we have a classification of subjects of education (e.g. "mother tongue", "mathematics", "theorethical quantum mechanics"). Two facet groups are created for this facet (education subject): 1) Facet Group: Basic Education Subjects (with "mother tongue", "mathematics") 2) Facet Group: Advanced Education Subjects (with "mother tongue", "mathematics", "theorethical quantum mechanics") - The faceted concepts of the 'started' part of the example ("primary school teacher", "high school teacher", "university teacher") can be further specialized with the 'Basic Education Subjects' or 'Advanced Education Subjects'. - The resulting constructed facets can be "high school teacher mathematics", "university teacher mathematics", "university teacher theorethical quantum mechanics", ... - The skos:broader for the new faceted concepts are: 1) for "university teacher mathematics" and for "university teacher theorethical quantum mechanics" : "university teacher" 2) for "high school teacher mathematics" : "high school teacher" 3) ... - Each of these (more) specialized faceted concepts all have the (simple) ESCO occupation "Teacher" as value for esco:constructedFrom

• ObjectProperty

containing group

The ESCO Group (pillar) concept containing the subject ESCO concept as a member.

• ObjectProperty

Country

Relevant standards for country locations are documented under the super class: http://data.europa.eu/esco/model#Location

• Class

country code (A2)

ISO 3166 country code - A2

• DatatypeProperty

country code (A3)

ISO 3166 country code - A3

• DatatypeProperty

defines structure for

• ObjectProperty

division characteristic

The ESCO facet group the thesaurus array is being built from. When an ESCO concept is specialized by a facet group, the ESCO thesaurus introduces that set (or branch) of specializations with a Thesaurus.Array. Example: The occupation "Teacher" can be specialized by 'education level' or by 'education subject'. At concept development time this is typically specified with respective esco:facet properties, one identifying the facet-group for education level, anoher identifying the facet-group holding the instructed subject areas. At concept publication time, each specializing facet will be represented as an iso-thes:ThesaurusArray having as members the (compound) faceted concepts. For each ESCO thesaurus array this property (esco:hasDivisionCharacteristic) recalls the FacetGroup it was created for. Note: Complementary to esco:hasDivisionCharacteristic the iso-thes:superOrdinate identifies the ESCO member concept used to create the faceted concepts that are members of the thesaurus array.

• ObjectProperty

Document

• Class

duration

• Datatype

eCF30

• Datatype

ECTS credit points

The ECTS credit points assigned to a qualification

• DatatypeProperty

EQF2012

• Datatype

ESCO Concept

The class of ESCO pillar concepts. ESCO pillar concepts are divided in tree semantic classes: esco:Occupation, esco:Skill and esco:Qualification, each organized in a dedicated ConceptScheme. All concepts are specializations of skos:Concept and are structured using the skos semantic relationships. - skos:mappingRelation is used to relate ESCO concepts to similar concepts in other concept schemes (e.g. ISCO-08 or ROME). The mapping to ISCO has particular business relevance and uses a special mapping sub-property (see http://data.europa.eu/esco/model#Occupation and http://data.europa.eu/esco/model#memberOfISCOGroup). - sub-properties of skos:related are used to express special relations among ESCO pillar concepts. (e.g. http://data.europa.eu/esco/model#isEssentialSkillFor) - sub-properties of the DCMI terms:subject capture codified characteristics of ESCO concepts (e.g. http://data.europa.eu/esco/model#hasNACECode, http://data.europa.eu/esco/model#skillType). The skos:broader and skos:narrower concepts are the prime concepts organizing hierarchy among ESCO pillar concepts. The hierarchical structure is modelled according three classes - esco:GroupConcept (see http://data.europa.eu/esco/model#GroupConcept) - the top level concepts, only used for strucutring. These concepts typically are not relevant for annotating CV or job postings. - esco:LeafGroupConcept (see http://data.europa.eu/esco/model#LeafGroupConcept) - the lowest top level concept, a special esco:GroupConcept. - esco:MemberConccept (see http://data.europa.eu/esco/model#MemberConcept) - the concepts used for coding or annotating CV and Job Postings. The ESCO concepts are also divided according their analytical structure. There are two sub-classes: - simple concepts (see http://data.europa.eu/esco/model#SimpleConcept) and - compound concepts (see http://data.europa.eu/esco/model#FacetedConcept). A concept specialized by faceted concepts holds the labels of each of the faceted concepts in the property http://data.europa.eu/esco/model#plusUF. These labels are not synonyms or alternate labels. Among hierarchical related ESCO pillar concepts the following inheritance rules apply - the ESCO relationships from any broader transitive concept are inherited with the following restrictions in case a relationship with the same skill is typed as well essential as optional, only the essential skill relationship is inherited in case a relationship with the same qualification is typed as well required as legally required, only the legally required qualification relationship is inherited - the occasional tagging of the faceted concept (with NUTS, NACE, FoET, ISCO, SkillType, SkillReuseLevel ... codes) must be equal or more specific (specialized) than the code of any of its broader transitive ESCO concepts. The ESCO concepts are specializations of skos:Concepts and use skos:note specializations (see http://www.w3.org/2004/02/skos/core#note). - the skos:definition gives the full description of the ESCO concept. - the skos:scopeNote is the practical instruction for when to apply the ESCO concept. - the skos:historyNote gives a system log of significant versioned changes to the ESCO concept. - the skos:changeNote gives the human provided documentation for ESCO concept version modifications. Characteristics: - At the time of publication, the ESCO concepts are available in Icelandic and the official languages of the European Union, except Irish. Per release, actual languages covered are provided by esco:supportedLanguage. Some concepts are originally developped in a reference language. This particular language is indicated by http://data.europa.eu/esco/model#referenceLanguage, - Any ESCO concept may refer relevant hyperlinked sources of reference or of information. See http://data.europa.eu/esco/model#relevantURL. Each ESCO pillar concept may hold provenance and audit metadata: - rightsHolder: the owner (http://purl.org/dc/terms/rightsHolder) - optional - required - publishing status (http://purl.org/iso25964/skos-thes#status) - required - creator : the author (http://purl.org/dc/terms/creator) - optional - contributor : modifier (http://purl.org/dc/terms/contributor) - required - modified : last modification date (http://purl.org/dc/terms/modified) - required

• Class

ESCO Occupations Concept Scheme

• Concept Scheme
• Instance

ESCO Qualifications Concept Scheme

• Concept Scheme
• Instance

ESCO Relationship Types Concept Scheme

• Concept Scheme
• Instance

ESCO Skills Concept Scheme

• Concept Scheme
• Instance

ESCO Structure

A structure defines a tagging relationship between one or more conceptschemes and an ESCO pillar. The structure identifies the predicate used for the relationship between an esco:MemberConcept and a skos:Concept that is part of the linked conceptscheme(s).

• Class

ESCO concept Label

The class of labels used on esco Concepts. Characteristics - An ESCO label may be motivated by relevant original sources. These sources are referenced uising http://data.europa.eu/esco/model#relevantURL - An ESCO label typically gets label roles detailing the gender specific characteristics of the label (see http://data.europa.eu/esco/model#hasLabelRole) Provenance information that may be added: - rightsHolder: the owner (http://purl.org/dc/terms/rightsHolder) - optional - optional - workflow status (http://data.europa.eu/esco/flow#status) - required - creator : the author (http://purl.org/dc/terms/creator) - optional - contributor : modifier (http://purl.org/dc/terms/contributor) - required - modified : last modification date (http://purl.org/dc/terms/modified) - required

• Class

ESCO concept used for sector breakdown.

A sector breakdown concept can be used in the Occupation and in the Skill/Competences pillar to organize navigation. As such, it may be related (or characterize) a group of occupations as well as a group of skills. It is not an industry sector, but it may be tagged with NACE codes. This notion is specifically used for organizing the ESCO thesaurus creation (cfr. ESCO v1 methdology and SREF groups).

• Class

ESCO concepts Relationship

The class of directed relationships between two ESCO Pillar concepts (e.g. between an esco:Occupation and an esco:Qualification). The relationship: - starts from the ESCO concept identified by http://data.europa.eu/esco/model#isRelationshipFor. - is detailed using a descriptive text (http://purl.org/dc/terms/description). This description may contain reference to external sources (see http://data.europa.eu/esco/model#relatedLegallyRequiredQualification) - ends in the ESCO concept identified by http://data.europa.eu/esco/model#refersConcept. - is typed by the tagging property http://data.europa.eu/esco/model#hasRelationshipType. A relationship may be industry sector or location specific. This can be acieved by tagging the relationship using esco:hasNACECode or esco:location respectively.

• Class

ESCO expiration note

• AnnotationProperty

ESCO relationship type

The class of the types of ESCO relations. The concepts having this type are managed in the small SKOS taxonomy (see http://data.europa.eu/esco/model#RelationshipType).

• Class

editorial note

a note documenting the learning outcomes.

• AnnotationProperty

entry requirement

Entry requirements are structured into categories such as work experience, pre-assessment or a specific qualification. - The category of an entry requirement is given by dcterms:type property using a skos:Concept from the controlled vocabulary <http://data.europa.eu/esco/concept-scheme/entryrequirement-category>. - The requirement level expresses the necessity. It is given by the esco:requirementLevel property using a skos:Concept from the controlled voabulary <http://data.europa.eu/esco/concept-scheme/entryrequirement-level>. The generic class for entry requirements of a qualification. For example a requirement to enter the programme that leads to a qualification, or to access the examination or certification process, such as a prior (professional) experience or a specific qualification.

• Class

Esco extension

This class denotes concepts of non-EU relevance separate from the usual scope of ESCO.

• Class

expiry period

The validity period of a qualification. The period for which a qualification is valid, after it is issued to an individual.

• DatatypeProperty

Facet concept group

A Facet concept group (i.e. an instance of the class esco:FacetConceptGroup) is a sub-set of concepts from a facet. A facet is a supporting taxonomy for ESCO. Examples are: - Languages - Species - Tools An (instance of the) esco:FacetConceptGroup is a sub-set of concepts from a facet. The typical use of an esco:FacetConceptGroup is to specialize one or more ESCO pillar concepts. (see http://data.europa.eu/esco/model#facet). The specialization creates narrower (or transitive narrower) concepts of the specialized ESCO pillar concept. Each specialization is a Faceted (or compound) concept (with type http://data.europa.eu/esco/model#FacetedConcept) having as component concepts: - the ESCO pillar object being specialized and - one member concept from the facet group. An ESCO pillar concept is either an esco:SimpleConcept or an esco:FacetedConcept An ESCO concept can be specialized in different ways using different Facet concept groups The Facet concept group may be structured: - members of an esco:FacetConceptGroup can have hierarchical relationships (skos:broader and skos:narrower) among its member concepts. If this is the case, the hierarchical structure among the specialized concepts constructed with this facet group will mirror the hierarchy of the facet group. See also skos:topMember. - an esco:FacetConceptGroup can be an oredered collection. In this case, the order among the spicialized concepts constructed with this facet group will mirror the order of the facet group. - an esco:FacetConceptGroup can have different sub-collections (i.e. have skos:member that are a skos:Collection and an iso-thes:ThesaurusArray). Collections only serve to organize the constructed faceted concepts such that the faceted concepts that are specializations based on the structured Facet concept group are organized by thesaurus arrays that each mirror an original thesaurus array of the Facet concept group. Example: the language FacetConceptGroup can have as members - the (possibly ordered) collection of spoken languages having as members the language concepts - the (possibly ordered) collection of sign languages having as members the sign language concepts The name of the facet group is given by skos:prefLabel

• Class

FacetConceptGroups

• Concept Scheme
• Instance

Faceted ESCO concept

The class of compound ESCO pillar concepts. A compound concept is a concept that is broken down in a set of mare basic component concepts (e.g. a pianist is a 'musician' performing on a 'piano') An ESCO concept is either a faceted concept or a simple concept (see http://data.europa.eu/esco/model#SimpleConcept). An ESCO faceted (or compound) concept is the specialization of an ESCO concept that identifies one or more specialization facets (see http://data.europa.eu/esco/model#facet). A specializing facet is a group of concepts with a common characteristic (e.g. the group of music instruments). The specialization makes a compound of the ESCO concept and of one concept of each of its related specializing facets. - During the editorial phase, one or more faceted concepts may be created ad hoc by the ESCO taxonomists. - During the ESCO publishing phase all possible faceted concepts are generated by the publication process. The process adds the possible compound conepts that were not created by the (human) taxonomist. - Each faceted concept is the specialization (i.e. the skos:narrowerTransitive) of an ESCO simple concept (see http://data.europa.eu/esco/model#constructedFrom) - All facet componets (i.e. the facet values) of the faceted conept are given by the property http://data.europa.eu/esco/model#hasFacet Uniqueness rule: Two instances of esco:FacetedConcept are the same if and only if both instances - refer the same simple ESCO concept using http://data.europa.eu/esco/model#constructedFrom - refer the same set of components (facet values) using http://data.europa.eu/esco/model#hasFacet The faceted concept inherits certain characteristics from the Simple Concept it is constructed from: - the ESCO pillar type (Occupation, Skill or Qualification) of its simple concept it is constructed from (see esco:constructedFrom). - the memberOfISCOGroup of the occasional Occupation it is constructed from - the skillType and the skillReuseLevel of the occasional Skill it is constructed from Further, inheritance rules apply as on ESCO concepts (see http://data.europa.eu/esco/model#Concept).

• Class

FoET code

The class of ISCED 2013/FoET classificaton code (International Standard Classification of Education: Fields of Education and Training 2013) The Fields of Education and Training have been submitted to the UNESCO Conference - session 37 - Paris. The version submitted for resolution is available from: http://unesdoc.unesco.org/images/0022/002218/221863e.pdf Other original source references: - http://www.uis.unesco.org/Education/Documents/isced-37c-fos-review-222729e.pdf - http://www.uis.unesco.org/EDUCATION/Pages/international-standard-classification-of-education.aspx

• Class

FoET2013

• Datatype

from ESCO concept

The ESCO concept the (subject) relationship starts from (see http://data.europa.eu/esco/model#Relationship).

• FunctionalProperty
• ObjectProperty

Group concept

Concepts of this type are aggregations. The property http://data.europa.eu/esco/model#hasGroupMember gives the members concepts of the group. The member concepts have type http://data.europa.eu/esco/model#MemberConcept. These member concepts are skos:narrowerTransitive spcializations of the group concept. Among GroupConcept, the skos:broader/skos:narrower is like a super-group/sub-group relation meaning that all members of the (narrower) sub-group also are members of the (broader) super-group. Typically these group concepts are NOT used in CV or job postings, but serve organization, reporting and statiscal purposes. The member concepts of group concepts are used for coding or annotating CV or job postings. A Group concept typically will be - in the upper levels of an ESCO pillar (or concept schema) - in an external concept schema (e.g. ISCO)

• Class

Group of overlapping skills

The class of collections of overlapping esco:Skill concepts. All skills within one collection of overlapping skills have overlapping semantics with each other. The collection has a name using http://www.w3.org/2004/02/skos/core#prefLabel . As clarifications about the overlapping emerge, a decision from ESCO editorial team may instruct to merge some or all of the member concepts of this collection or to relate its members in another way.

• Class

has EQF Level

The level (as specified by the European Qualification Framework) applicable to the subject qualification.

• ObjectProperty

has ESCO relationship

The detailed (typed, annotated and documented) ESCO relationship (see http://data.europa.eu/esco/model#Relationship) for the subject ESCO concept. The relationship identifies a related ESCO concept. The inverse relations of esco:refersConcept and of esco:isRelationshipFor entail the property esco:hasRelationship. The relationship properties provide formal semantics to the ESCO concept relationship.

• InverseFunctionalProperty
• ObjectProperty

has ESCO relationship list

The ordered set of relationships starting at the subject ESCO pillar concept. For any resource, every item in the list given as the value of the esco:hasRelationshipList property is also a value of the esco:hasRelationship property.

• ObjectProperty

has ESCO relationship type

A tagging concept detailing the type of the (subject) ESCO relationship

• ObjectProperty

has FoET Code

A tagging concept identifying the Field of Education Code as specified by the UNESCO Institute for Statistics (UIS).

• ObjectProperty

has NACE code

A tagging concept using the NACE codes to specify the industry sector of the tagged subject.

• ObjectProperty

has accreditation

• ObjectProperty

has association

The detailed (typed, annotated and documented) association (see http://data.europa.eu/esco/model#AssociationObject) from a resource (e.g. a qualification) to a node in an other established framework. The association identifies a related semantic asset from another established framework. The inverse relation of esco:isAssociationFor entails the property esco:hasAssociation.Used to express a learning outcome of a qualification as a relation from a qualification to an ESCO skill, competence or knowdledge.Used to link a qualification to a qualification framework level.Used to related a qualification to an occupation from a national, regional or international occupation classification system.

• InverseFunctionalProperty
• ObjectProperty

has awarding activity

an awarding activity of a qualification

• ObjectProperty

has awarding body

The institutiution, organisation or company that issues the (subject) qualification (certification).

• ObjectProperty

has code list

• ObjectProperty

has coded property

• ObjectProperty

has entry requirement

an entry requirement of a qualification

• ObjectProperty

has essential skill

The ESCO skill or competence that is essential for the subject occupation or skill.

• ObjectProperty

has facet

A faceted ESCO concept (e.g.) is a compound concept constructed from an ESCO pillar concept and one or more facets. The typical example is the (foreign) language skills. - The ESCO concept is the skill: foreign language expertise. The facets are: - the specific language of the expertise (en, fr, el, bg, nl ... ) - the skill levels defined by CEFR (writing, understanding interactively, ...).

• ObjectProperty

has group member

Identifies the member Concept of the (subject) Group concept.

• ObjectProperty

has label role

A tagging concept providing the gender specific typing of an ESCO label. Each ESCO label can have - at most 1 label that is standard male and zero or more labels that are male - at most 1 label that is standard female and zero or more labels that are female - any label that is not male or female is considered neutral - a male respectively female preferred label is the standard male respectively standard female label

• ObjectProperty

has learning outcome

The ESCO skill/competence related to (or asserted by) the subject ESCO qualification. I.e. when asserted on a subject qualification, the related competence is a learning outcome of that qualification.

• ObjectProperty

has optional skill

The ESCO skill or competence that is relevant (but optional) for the subject occuption.

• ObjectProperty

has poly-hierarchy

true: Indicates wether a ESCO thesaurus/taxonomy supports poly-hierarchy. Not present or false indicate mono-hierarchy.

• DatatypeProperty

has recognition

• ObjectProperty

has top concept list

The ordered set of top concepts of the subject conceptscheme. For any resource, every item in the list given as the value of the esco:hasTopConceptList property is also a value of the skos:hasTopConcept property.

• ObjectProperty

has top member

Typically specified in case the subject collection is a concept group having a hierarchical representation (hierarchy based on broader/narrower). The referenced concepts are the hierarchical entry points of the concept group hierarchy. The top may be concepts as well as collections.

• ObjectProperty

ISC008

• Datatype

ISCED FoET Code

A tagging concept identifying the ISCED 2013 FoET classification code (Field of Education Code). It is used to indicate the thematic area of a qualification.

• ObjectProperty

ISCO88

• Datatype

ISCO88 Code

The parent ISCO 88 codes of a specific occupation. The format is ''<code>[,<code>]*''^^xsd:string e.g ''3139,3131''^^xsd:string means the occupation has 2 parent occupation groups in isco88. One with iscocode 3139 and one with iscocode 3131

• ObjectProperty

is a learning outcome of

The inverse of esco:relatedCompetence.

• ObjectProperty

is essential skill for

The inverse of esco:relatedEssentialSkill.

• ObjectProperty

is indirectly included

True: Indicates the subject concept (like a qualification) is not directly managed by ESCO. instead the concept is loaded into ESCO when it is provided by an external (typical national) body or agent. Could also be applied (if unambiguous) to skills and occupations. Assertion (to 'true') is required in case external contribution must be affirmed.

• DatatypeProperty

is legally required qualification for

The inverse of esco:relatedLegallyRequiredQualification

• ObjectProperty

is optional skill for

The inverse of esco:relatedOptionalSkill.

• ObjectProperty

is partial qualification

Default value is 'false'^^xsd:boolean Indicates whether a qualification is a full qualification or part of another qualification. In the latter, the qualification is only obtained as a formal outcome of a “broader” qualification of which it is part.

• DatatypeProperty

is qualification for

The inverse of esco:relatedQualification.

• ObjectProperty

is transversal

Typical to indicate that a concept (like a skill) is not job or sector specific. It is cross sector. May also be applied (if unambiguous) to qualifications and occupations. Assertion (to 'true') is required in case transversality must be affirmed. Skill re-usability levels can be tagged in case the level implies transversal scope of the skills having the re-usability level.

• DatatypeProperty

isco label

The ISCO label of an occupation group. Provided in case the preferred label has been replaced by an esco specific one. Typically this can happen in order not to have duplicate preferred labels in the ESCO thesaurus.

• AnnotationProperty

Label Role

• Concept Scheme
• Instance

Label role

Allows to capture one or more particular characteristics of a name. Example usage: Gender related terms. - ESCO concepts may get a gender neutral term as preferred label. The gender specific terms are provided as alternate labels. - Relevant use cases: - concept look-up based on gender specific term - Job posting generation with gender neutral terms - CV generation with gender specific terms

• Class

Language

The class of language concepts. Each language is - labeled using skos:prefLabel in all of the other languages and - identified using the ESCO esco:language property (value = ISO 2-char language code). The class provides the set of languages that can be in use in the thesaurus. Two ESCO concept schemes provide language concepts: - http://data.europa.eu/esco/model#ISO639 - all languages of ISO 639-1 and ISO 639-2 - http://data.europa.eu/esco/model#ISO639-3 - all sign languages listed in ISO 639-3 The esco:ConceptScheme identifies the languages actually used via its property esco:supportedLanguage.

• Class

language

QMS usage: The range must be a rdfs:Literal typed as xsd:language.The ISO 639-1 code of the language (2-char language code) in which a text is available.The language of the subject resource.

• DatatypeProperty

Leaf-group concept

A Group (or aggregation) concept, having no sub-groups anymore. Narrower concepts only can be members (or narrower instances) of the group concept. The specialization http://data.europa.eu/esco/model#narrowerInstance of skos:narrower is used to identify the top level members of the group.

• Class

legally required qualification

The ESCO qualification (certification) that is legally required for the subject occupation or skill. Details for the requirements must be given in the relationship description. Occasionally, such a description must hold a hyperlink to the relevant professions database (e.g. http://ec.europa.eu/internal_market/qualifications/regprof/index.cfm?action=profession&id_profession=12142). In case the legal requirement is region specific, the relationship: - should detail the restriction in the relation description - could be tagged with a location or NUTS code (see http://data.europa.eu/esco/model#location)

• ObjectProperty

Level (European Qualification Framework)

The EQF levels have been published as recommendation by the EU Publication office under CELEX number 32008H0506(01) See http://publications.europa.eu/resource/celex/32008H0506%2801%29

• Class

license

• AnnotationProperty

Location

A teritorial area like a federation, a country, a region, a jurisdiction area. Standards useful for locations and regions: - ISO 3166 - NUTS - http://epp.eurostat.ec.europa.eu/portal/page/portal/nuts_nomenclature/introduction (extends ISO 3166 with sub-regions) - geonames - http://www.geonames.org/ (includes ISO 3166) - EU publication Office - http://publications.europa.eu/mdr/authority/country/index.html

• Class

location

The Country or region the subject is associated with. Typically a tagging concept.

• ObjectProperty

Member concept

Concepts of this class are specifically used to be referenced in CV or job postings. Typically these concepts are at the more specialized levels of the hierarchy. Example: A particular occupation, not a group of occupations. These concepts in general have However, some Member concept may be specializations of other ones. In general these specializations will not comply to (1). General group membership within ESCO pillars is provided by esco:memberOfGroup.

• Class

MemberConcept

• Class

NACE code

Industry sector code NACE rev2 The NACE codes are published in http://epp.eurostat.ec.europa.eu/cache/ITY_OFFPUB/KS-RA-07-015/EN/KS-RA-07-015-EN.PDF The RDF version is available from: http://ec.europa.eu/eurostat/ramon/rdfdata/nace_r2.rdf - Note, this is not SKOS but can be made SKOS compliant. ESCO keeps a SKOS compliant copy of NACE codes. These are organized in the concept scheme http://data.europa.eu/esco/model#NACErev2

• Class

NACEr2 code

• Datatype

NACEr2 section

• Datatype

NUTS regionCode

• Datatype

narrower instance

The ESCO concepts (occupation, skill or qualification) that are immediate (one step) narrower concepts of the (subject) leaf group. These narrower concepts are top level (member) concepts of the subject leaf concept group. The (subject) leaf group may have more members, not provided by its esco:narrowerInstance properties. Typically, these other members are specializations (e.g. faceted concepts) of the top level members of the (subject) leaf concept group.

• ObjectProperty

Node Literal

• DatatypeProperty

node literal

Free text metadata fields, such as the description, a historical or additional note of a qualification can contain a plain text or a XHTML fragment as literal value. By using a NodeLiteral both the datatype of the literal as the language can be specified.The class used to specify Literals that can have both a datatype and a language tag

• Class

note text

An xml literal taking a plain text or xhtml.body.type content type. The property typically allows to validate the content of a SKOS note (or any of its SKOS sub-properties). Notes are then provided as blank nodes with this property and with the ESCO language property. The motivations for this complex approach are: - Provides structure content (XML literal) according a format that can be validated. - xml:lang and rdf:parseType="Literal" can not be provided on the same property.

• DatatypeProperty

Occupation

The class of ESCO Occupation concepts. An Occuaption is an ESCO pillar concept (see http://data.europa.eu/esco/model#MemberConcept). Characteristics of an Occupation: - The relevant industry sector for an occupation is given by the Eurostat NACE codes (see http://data.europa.eu/esco/model#hasNACECode) - The different Work context applicable for an occupation (see http://data.europa.eu/esco/model#hasWorkContext). An occupation may be related to - esco:Skill (see http://data.europa.eu/esco/model#relatedEssentialSkill and http://data.europa.eu/esco/model#relatedOptionalSkill) - esco:Qualification (see http://data.europa.eu/esco/model#AssociationObject) Occupations having a legal or other regulations in a specific region - must identify these regulations in the occupation definition (and refer the professional DB stating that regulation - e.g. http://ec.europa.eu/internal_market/qualifications/regprof/index.cfm?action=profession&id_profession=12142) - could identify such a region with the location property (see http://data.europa.eu/esco/model#location).

• Class

Organization

• Class

original label

The original label of a concept of a support taxonomy. Provided in case the preferred label has been replaced by an ESCO specific one. Typically used on arguable names for exceptional concepts like 'Country'

• AnnotationProperty

page

• ObjectProperty

plusUse

Property

• Class

publisher

• AnnotationProperty

Qualification

A qualification is a formal outcome of an assessment and validation process, which is obtained when a competent body determines that an individual has achieved learning outcomes to given standards.List of properties on a qualification defined by the QMS application profile: - adms:identifier (1..n) - esco:referenceLanguage (0..n) - skos:prefLabel (1..n) - skos:altLabel (0..n) - skos:definition (0..n) - dcterms:description (1..n) - esco:hasISCED-FCode (1..n) - esco:hasAssociation (0..n) - esco:hasECTSCreditPoints (0..1) - esco:volumeOfLearning (0..1) - esco:isPartialQualification (0..1) - esco:waysToAcquire (0..n) - esco:expiryPeriod (0..n) - esco:hasRecognition (0..n) - esco:hasAwardingActivity (0..n) - esco:hasAccreditation (0..n) - foaf:homepage (0..n) - dcat:landingPage (0..n) - esco:supplementaryDoc (0..n) - dcterms:issued (1..1) - dcterms:modified (1..1) - skos:changeNote (0..1) - skos:historyNote (0..1) - esco:additionalNote (0..n) - dcterms:replaces (0..n) - dcterms:isReplacedBy (0..n) - iso-thes:status (0..1) - dcterms:creator (0..1) - dcterms:rightsHolder (0..1) - dcterms:publisher (1..1)

• Class

qualification

The ESCO qualification (certification) that is required for the subject occupation or skill.

• ObjectProperty

qualification expiration period

Period how long a qualification is valid. Example: a qualification for aircraft pilot may be subject to hours flight and/or testing within a specified period in order to pro-long the qualification.

• DatatypeProperty

Recognition

The recognition class is used to specify information related to the formal recognition of a qualification and/or awarding body. It is used to model a national or regional authority that formally recognises a qualification and/or a certain awarding body

• Class

Reference language

QMS usage: The ISO 639-1 code of the language (2-char language code) in which information about the qualification is provided. This language will be used as the default reference language for the qualification.QMS usage: The range must be a rdfs:Literal typed as xsd:language.Reference language for a concept. Typically set when the concept is first loaded with PT in (at least) 1 language. (If multiple but not all languages are provided, the reference language must be uniquely set to one of the loaded languages.) In case the concept needs to be shown or translated in a new language (not having a PT yet), the label in the reference language is shown.

• DatatypeProperty

regultated profession note

The subject occupation is regulated according the description in the note. The note typically contains a hyperlink.

• AnnotationProperty

relevant URL

A web site that is relevant for the subject (any modelled class, including an ESCO concept or term). Such URL may be part literal content value of a description, a definition or a scope note. A relevant URI may be language specific (hence the range is literal).

• DatatypeProperty

replaced by

Typical for a deprecated concept that has been replaced by one or more other concepts.

• ObjectProperty
• TransitiveProperty

replaces

Typical for a deprecated concept that replaces one or more other concepts.

• ObjectProperty
• TransitiveProperty

requirement level

Refers to a skos:Concept that indicates the requirement level of a certain entry requirement. It indicates the necessity of the entry requirement

• ObjectProperty

Resource

• Class

review date

• DatatypeProperty

rule

• AnnotationProperty

Simple ESCO concept

The class of simple ESCO concepts. A simple ESCO concept is not decomposed into components (for compound ESCO concepts see http://data.europa.eu/esco/model#FacetedConcept). A simple concept may be further specialized by faceted concepts. The facets used for this specialization are represented by the property http://data.europa.eu/esco/model#facet.

• Class

Skill

The class of ESCO Skill concepts. ESCO skills are sub-typed (e.g. to differentiate between knowledge and competence). This sub-typing is modelled using the concept class http://data.europa.eu/esco/model#SkillCompetenceType Concept class for organization is http://data.europa.eu/esco/model#SkillReuseLevel ESCO skills with a different re-use applicability across sectors can be put in a hierarchical relation (skos:broader and skos:narrower) in acordance with the rules detailed by http://data.europa.eu/esco/model#SkillReuseLevel. Characteristics - An ESCO skill sub-type is given by http://data.europa.eu/esco/model#skillType - An ESCO skill re-use level is given by http://data.europa.eu/esco/model#skillReuseLevel An ESCO Skill may be related to other ESCO concepts. - Essential related concepts of class esco:Skills are indicated by http://data.europa.eu/esco/model#isEssentialSkillFor and http://data.europa.eu/esco/model#relatedEssentialSkill - Optional related concepts of class esco:Skills are indicated http://data.europa.eu/esco/model#isOptionalSkillFor and http://data.europa.eu/esco/model#relatedOptionalSkill - Occupations a skill is essential for are concepts of type esco:Occupation indicated by http://data.europa.eu/esco/model#isEssentialSkillFor - Occupations a skill is optional for are concepts of type esco:Occupation indicated by http://data.europa.eu/esco/model#isEssentialSkillFor The property http://data.europa.eu/esco/model#hasRelationship details the relationships (see http://data.europa.eu/esco/model#Relationship)

• Class

Skill Competence Type

• Concept Scheme
• Instance

Skill reuse level

Re-usability level of a Skill or competence. Details are provided by the ESCOpedia article on Cross-sector skills and competences (see https://ec.europa.eu/esco/escopedia/-/escopedia/Cross-sector_skills_and_competences?resetLanguage=true&newLanguage=en") A skill with re-use level A can only be a broader of a skill with reuse level B if either of the following holds: - reuse level A = reuse level B - reuse level A is a broader transitive of reuse level B. A skill can have at most one re-use level (see http://data.europa.eu/esco/model#Skill).

• Class

skill reuseability level

Reuseability level of a skill

• ObjectProperty

skill type

Type of competence (a tagging concept)

• ObjectProperty

SkillReuseLevels

• Concept Scheme
• Instance

sorting string

The formatted string used to establish sorting among concepts. Deprecated by use of skos:OrderedCollection and iso-thes:subordinateArray

• AnnotationProperty

specializing facet

The facet concept group, a group of concepts used to expand: - the subject (ESCO) concept or - all the members concepts of the subject Collection to build ESCO (compound) faceted concepts. An ESCO concept may have different aspects or facets that can specialize the ESCO concept. A well known example is the (foreign) language skills. - the main aspect of the (foreign) language skill is the identification of the foreign language The specialized concepts thus constructed are: - (foreign) language skill Albanian, - (foreign) labguage skill Bulgarian, - ... - the (main) facet (e.g. a set of languages) occasional is extended by (sub-) facets that can be added. E.g. a (sub-) facet of language (skill) are the specialized levels defined by CEFR writing, understanding interactively, ...) The relationship between facet groups (in the example above "language" and "CEFR language skill level" can be made 2-way (from "language" to "language skill level" and the inverse). In addition, the "(foreign) language skill" can have as facet (i.e. be specialized) by as well "language" as by "CEFR language skill level". As a result, the ESCO concept "(foreign) language skill" can be specialized in two different ways: - first by language then by language skill level or - first by language skill level then by language Both navigation hierarchies ultimatly hold the same set of (compound) faceted concepts (e.g. "(foreign) language skill" "writing" "Bulgarian". In general: - concept - - &lt;concept by facet group 1&gt; - - - [concept + facet group 1 member] - - - - &lt;[concept + facet group 1 member] by facet group 2&gt; - - - - - [concept + facet group 1 member + facet group 2 member] - - - - - ... (other facet group 2 members) - - - ... (other facet group 1 members) - - &lt;concept by facet group 2&gt; - - - [concept + facet group 2 member] - - - - &lt;[concept + facet group 2 member] by facet group 1&gt; - - - - - [concept + facet group 2 member + facet group 1 member] - - - - - ... (other facet group 1 members) - - - ... (other facet group 2 members)

• ObjectProperty

status

• AnnotationProperty

subject

• ObjectProperty

supplementary doc

• ObjectProperty

supported language

Denotes a description of the languages supported by the (subject) concept scheme. Required for ESCO taxonomy or thesauri.

• ObjectProperty

Target URL

The URL of a node in another established framework.

• DatatypeProperty

Target description

A free-text description of a node in another established framework.

• DatatypeProperty

target framework

The framework to which the resource being described is associated. It is the framework that describes the target resource (the associated resource) (e.g. ESCO classification system, national qualification framework system,..). It is recommended that the target framework is denoted by a known resource (e.g. a adms:Asset, a dcat:Dataset, a conceptscheme)

• FunctionalProperty
• ObjectProperty

Target name

The name or value of a node in another established framework.

• DatatypeProperty

target notation

• DatatypeProperty

The ESCO ontology

The ontology of the taxonomy European Skills, Competences, qualifications and Occupations.

• Ontology

thesaurus concept and label publication status type

list of status values used for managing ESCO release status. On creation of a concept or label, the default state is "to be reviewed" On deprecation of a concept the concept state becomed "obsolete" When a wrongly deprecated concept is revived, the state becomes "to be reviewed" When the thesaurus is published, the statuss becomes "released" All state changes are system managed.

• Datatype

to ESCO concept

The ESCO concept referred by the (subject) ESCO relationship. The esco:Relationship gives a more elaborate semantic description of related ESCO concepts. These related concepts are identied by the esco:Relationship propertief - esco:isRelationshipFor - esco:refersConcept Further semantics are provided by - a relationshipt type - a description - .. (other possible extensions)

• FunctionalProperty
• ObjectProperty

transitive replaced by

Typical for a chain of changes and deprecations of a concept over different versions.

• ObjectProperty

transitively replaces

Typical for a chain of deprecated concepts that replaces one or more other concepts over more than one version.

• ObjectProperty