. "1.0"^^ . "2014-10-23"^^ . "The ontology of the taxonomy \"European Skills, Competences, qualifications and Occupations\".\n\nThe ontology considers three ESCO pillars (or taxonomy) and 2 registers.\nThe three pillars are:\n- Occupation\n- Skill (and competences)\n- Qualification\n\nFor the construction and use of the ESCO pillars, the following modelling artefacts are used:\n- Facetting support to specialize ESCO pillar concepts based on bussiness relevant Concept Groups (e.g. species, languages, ...)\n- Conept Groups, Thesaurus array and Compound terms (as detailed in ISO 25964) to organize faceted concepts\n- SKOS mapping properties to relate ESCO pillar concepts to concepts in other (external) taxonomies (e.g. FoET, ISCO88 and ISCO08. More mappings can be added in the future.)\n- Tagging ESCO pillar concepts by other (external) taxonomies (NUTS, EQF, NACE, ...)\n- Capture gender specifics on the labels of the ESCO pillar concepts\n- Rich ESCO concept relationships holding a description and other specific characteristics of the relation between two ESCO pillar concepts.\n\nESCO maintains two additional registers:\n- Awarding Body\n- Work Context\nAwarding Bodies typically are referenced by ESCO qualifications.\nOccupations can have one or more work context."@en . . . . "The ESCO ontology"@en . "Johan De Smedt (TenForce)" . "Martin Le Vrang (DG-EMPL, Approver)" . "Massimiliano Molinari (DG-EMPL, Reviewer)" . "Agis Papantoniou (TenForce)" . "Pieter Fannes (TenForce)" . "2014-04-08"^^ . . "sorting string"@en . . . "true"^^ . "2014-04-08"^^ . "2014-04-08"^^ . "proposed"^^ . "The formatted string used to establish sorting among concepts.\nDeprecated by use of skos:OrderedCollection and iso-thes:subordinateArray"@en . . . . "ISCO88 Code"@en . "2013-06-27"^^ . "2013-12-03"^^ . "true"^^ . "Deprecated with Model version 1."@en . "ESCO v0 -> ESCO v1 must create http://data.europa.eu/esco/model#memberOfISCOGroup (esco:memberOfISCOGroup a sub-property of skos:broadMatch) based on the detailed list of ISCO codes.\nRead also change note on: http://data.europa.eu/esco/ConceptScheme/ISCO2008\n\nEsco v0 has 4761 statements."@en . "The parent ISCO 88 codes of a specific occupation.\nThe format is ''[,]*''^^xsd:string\n\ne.g ''3139,3131''^^xsd:string means the occupation has 2 parent occupation groups in isco88. One with iscocode 3139 and one with iscocode 3131"@en . . . . . . "ESCO expiration note"@en . "2013-12-03"^^ . "true"^^ . "A note documenting an expiry period or date"@en . "Deprecated with Model version 1."@en . "ESCO v0 -> ESCO v1.\nShould be part of http://www.w3.org/2004/02/skos/core#definition.\nAn expiration period typically should be given formaly by the \"xsd:duration\" typed property http://data.europa.eu/esco/model#expirationPeriod\n\nESCO v0 has expiration notes on 3 qualifications (also having a definition). These expiration notes need to be appended to the respective definition note.by:\n- add two line breaks\n- add the expiration note.\nThe formal property esco:expirationPeriod needs to be set manually to express a duration."@en . . . . . "regultated profession note"@en . "2014-08-26"^^ . . . "proposed" . "The subject occupation is regulated according the description in the note. The note typically contains a hyperlink."@en . . . "has awarding body"@en . "2013-06-27"^^ . "2013-06-27"^^ . "released" . "The institutiution, organisation or company that issues the (subject) qualification (certification)."@en . . . . . "can have work context"@en . "2014-08-10"^^ . "2014-08-10"^^ . "proposed" . "The possible working context of the (subject) occupation."@en . . . . . "has EQF Level"@en . "2013-06-27"^^ . "2013-06-27"^^ . "The level (as specified by the European Qualification Framework) applicable to the subject qualification."@en . "released" . . . . . "has FoET Code"@en . "2013-12-03"^^ . "2013-12-03"^^ . "proposed" . "A tagging concept identifying the Field of Education Code as specified by the UNESCO Institute for Statistics (UIS)."@en . . . . . "has label role"@en . "2013-12-03"^^ . "2013-12-03"^^ . "A tagging concept providing the gender specific typing of an ESCO label.\nEach ESCO label can have\n- at most 1 label that is standard male and zero or more labels that are male\n- at most 1 label that is standard female and zero or more labels that are female\n- any label that is not male or female is considered neutral\n- a male respectively female preferred label is the standard male respectively standard female label\n"@en . "proposed" . . . . . . "has ESCO relationship type"@en . "2014-04-16"^^ . "2014-04-16"^^ . "A tagging concept detailing the type of the (subject) ESCO relationship"@en . "proposed" . . . . . . "has NACE code"@en . "2013-12-03"^^ . "2013-12-03"^^ . "A tagging concept using the NACE codes to specify the industry sector of the tagged subject."@en . "proposed" . . . . . "isco label"@en . "2013-12-03"^^ . "There may be at most 1 iscoLabel per language for any OcupationGroup."^^ . "true"^^ . "Generalized and replaced by: http://data.europa.eu/esco/model#originalLabel\n\nESCO v0 -> ESCO v1 (read also change note on: http://data.europa.eu/esco/ConceptScheme/ISCO2008)\nThe ESCOv1 (= v0.0) concepts (that are a copy of ISCO2008 concepts) should keep existing label in ESCOv0 and iscoLabel is removed.\nThe ISCO2008 concepts should keep the preferred label (per language) the property esco:iscoLabel is replaced by the property esco:originalLabel (http://data.europa.eu/esco/model#originalLabel)\n\nConversion needs to convert the existing ISCO labels in two ways: \n- as esco:iscoLabel which MAY NOT be modified (READ-ONLY) \n- as xl:label where ESCO can overrule the terminology from ISCO to conform to SKOS label requirements."@en . "The ISCO label of an occupation group.\nProvided in case the preferred label has been replaced by an esco specific one.\n\nTypically this can happen in order not to have duplicate preferred labels in the ESCO thesaurus."@en . "rejected" . "Deprecated with Model version 1."@en . . . . . . "editorial note"@en . "2013-06-27"^^ . "2013-12-03"^^ . "true"^^ . "Deprecated with Model version 1."@en . "The deprecated note must be transferred.\n- either be part of the definition (http://www.w3.org/2004/02/skos/core#definition) of the subject\n- or be part of the ESCO relationship (see http://data.europa.eu/esco/model#Relationship) providing the description of the subject.\n\nESCOv0 -> ESCOv\nESCO v0 has two (subject) Qualification concepts with a learningOutcome Note (and no definition note).\nOn conversion to ESCOv1 model, these should be replaced by a http://www.w3.org/2004/02/skos/core#definition"@en . "a note documenting the learning outcomes."@en . . . . "location"@en . "2013-06-27"^^ . "2013-06-27"^^ . "The Country or region the subject is associated with.\nTypically a tagging concept."@en . "released" . . . . . "original label"@en . "2013-12-03"^^ . "2013-12-03"^^ . "There may be at most 1 originalLabel per language for any Concept."^^ . "proposed" . "The original label of a concept of a support taxonomy.\nProvided in case the preferred label has been replaced by an ESCO specific one.\n\nTypically used on arguable names for exceptional concepts like 'Country'"@en . . . . . "skill type"@en . "2013-12-03"^^ . "2013-12-03"^^ . "Type of competence (a tagging concept)"@en . "proposed" . . . . . . "skill reuseability level"@en . "2014-06-05"^^ . "2014-06-05"^^ . "Reuseability level of a skill"@en . . "proposed" . . . . . . "Contributor"@en . "2013-12-03"^^ . "2013-12-03"^^ . "An entity responsible for making contributions to the resource."@en-us . "Examples of a Contributor include a person, an organization, or a service."@en-us . . . . "Date Created"@en . "2013-12-03"^^ . "2013-12-03"^^ . "Date of creation of the resource."@en . . . . "Author"@en . "2013-12-03"^^ . "2013-12-03"^^ . "An entity primarily responsible for making the resource."@en-us . "Examples of a Creator include a person, an organization, or a service."@en-us . . . . . "Description"@en . "2013-12-03"^^ . "2013-12-03"^^ . "An account of the resource.\nDescription may include but is not limited to: an abstract, a table of contents, a graphical representation, or a free-text account of the resource."@en . . . . "Date Issued"@en . "2013-12-03"^^ . "2013-12-03"^^ . "Date of formal issuance (e.g., publication) of the resource."@en-us . . . . "Date Modified"@en . "2013-12-03"^^ . "2013-12-03"^^ . "Date on which the resource was changed."@en . . . . "owner"@en . "Rights Holder"@en-us . "2013-12-03"^^ . "2013-12-03"^^ . "A person or organization owning or managing rights over the resource."@en-us . . . . "subject"@en-us . "2013-12-03"^^ . "2013-12-03"^^ . "The topic of the resource."@en-us . "This term is intended to be used with non-literal values as defined in the DCMI Abstract Model (http://dublincore.org/documents/abstract-model/). As of December 2007, the DCMI Usage Board is seeking a way to express this intention with a formal range declaration."@en-us . "Typically, the subject will be represented using keywords, key phrases, or classification codes. Recommended best practice is to use a controlled vocabulary. To describe the spatial or temporal topic of the resource, use the Coverage element."@en-us . . . "model axiom or term status"@en . "2013-12-05"^^ . "2013-12-05"^^ . "proposed"^^ . . . . . . . . . . . . . . . . . . . . "thesaurus concept and label publaction status type"^^ . _:genid1 . _:genid3 _:genid2 . _:genid2 . _:genid2 . _:genid5 _:genid4 . _:genid4 "obsolete"^^ . _:genid5 . _:genid2 _:genid5 . _:genid7 _:genid6 . _:genid3 _:genid7 . _:genid6 . _:genid6 . _:genid9 _:genid8 . _:genid8 "released"^^ . _:genid9 . _:genid6 _:genid9 . _:genid11 _:genid10 . _:genid7 _:genid11 . _:genid10 . _:genid10 . _:genid13 _:genid12 . _:genid12 "to be reviewed"^^ . _:genid13 . _:genid10 _:genid13 . _:genid11 . _:genid1 _:genid3 . _:genid1 . "2013-12-05"^^ . "list of status values used for managing ESCO release status.\nOn creation of a concept or label, the default state is \"to be reviewed\"\nOn deprecation of a concept the concept state becomed \"obsolete\"\nWhen a wrongly deprecated concept is revived, the state becomes \"to be reviewed\"\nWhen the thesaurus is published, the statuss becomes \"released\"\n\nAll state changes are system managed."@en . "proposed" . . . "thesaurus concept and label editorial status type"^^ . _:genid14 . _:genid16 _:genid15 . _:genid15 . _:genid15 . _:genid18 _:genid17 . _:genid17 "prepared"^^ . _:genid18 . _:genid15 _:genid18 . _:genid20 _:genid19 . _:genid16 _:genid20 . _:genid19 . _:genid19 . _:genid22 _:genid21 . _:genid21 "proposed"^^ . _:genid22 . _:genid19 _:genid22 . _:genid24 _:genid23 . _:genid20 _:genid24 . _:genid23 . _:genid23 . _:genid26 _:genid25 . _:genid25 "approved"^^ . _:genid26 . _:genid23 _:genid26 . _:genid24 . _:genid14 _:genid16 . _:genid14 . "2013-12-05"^^ . "list of status values used for managing ESCO vocabulary changes.\nThe editorial status is only managed by a human with the role of taxonomy editor.\n\nOn creation, the default status is \"prepared\". The label or concept is considered not final.\nWhen finalizing the business releaavance and the related editorial review process, the status can be set to \"proposed\".\nAfter a formal validation process by the business, the status can be set to approved.\nWhen a review considers the label or concept not relevant any more, the publication status is (automatically) set to \"obsolete\" by the relevant deprecation action.\n"@en . "proposed" . . . "term status type"^^ . _:genid27 . _:genid29 _:genid28 . _:genid28 . _:genid28 . _:genid31 _:genid30 . _:genid30 "approved"^^ . _:genid31 . _:genid28 _:genid31 . _:genid33 _:genid32 . _:genid29 _:genid33 . _:genid32 . _:genid32 . _:genid35 _:genid34 . _:genid34 "prepared"^^ . _:genid35 . _:genid32 _:genid35 . _:genid37 _:genid36 . _:genid33 _:genid37 . _:genid36 . _:genid36 . _:genid39 _:genid38 . _:genid38 "proposed"^^ . _:genid39 . _:genid36 _:genid39 . _:genid41 _:genid40 . _:genid37 _:genid41 . _:genid40 . _:genid40 . _:genid43 _:genid42 . _:genid42 "rejected"^^ . _:genid43 . _:genid40 _:genid43 . _:genid45 _:genid44 . _:genid41 _:genid45 . _:genid44 . _:genid44 . _:genid47 _:genid46 . _:genid46 "released"^^ . _:genid47 . _:genid44 _:genid47 . _:genid49 _:genid48 . _:genid45 _:genid49 . _:genid48 . _:genid48 . _:genid51 _:genid50 . _:genid50 "to be reviewed"^^ . _:genid51 . _:genid48 _:genid51 . _:genid49 . _:genid27 _:genid29 . _:genid27 . "2013-12-05"^^ . "list of status values used for managing ESCO ontology changes."@en . "proposed" . . . "has facet"@en . "2013-12-03"^^ . "2014-04-16"^^ . "proposed"^^ . "A faceted ESCO concept (e.g.) is a compound concept constructed from an ESCO pillar concept and one or more facets.\nThe typical example is the (foreign) language skills.\n- The ESCO concept is the skill: foreign language expertise.\nThe facets are:\n - the specific language of the expertise (en, fr, el, bg, nl ... )\n - the skill levels defined by CEFR (writing, understanding interactively, ...)."@en . . . . . "compound term"@en . "2014-02-18"^^ . "2014-02-18"^^ . "A compound equivalence label for the subject concept.\nThe subject concept is a Simple ESCO concept used as a component of a Faceted ESCO concept (i.e. a compound concept).\nThe 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++).\nThere can be any number of compound terms per language and per faceted concept."@en . "proposed" . . . . _:genid52 . _:genid53 . _:genid52 _:genid53 . _:genid53 . _:genid52 . . "broader instance"@en . "2013-06-27"^^ . "2013-06-27"^^ . "released"^^ . "The Leaf Group the (subject) ESCO member concept (Skill or Occupation or Qualification) belongs to.\nOnly 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."@en . . . . . . . . "from ESCO concept"@en . . "2013-12-03"^^ . "2013-12-03"^^ . "proposed"^^ . "The ESCO concept the (subject) relationship starts from (see http://data.europa.eu/esco/model#Relationship)."@en . . . . . . "has group member"@en . "2013-12-03"^^ . "2013-12-03"^^ . "released"^^ . "Identifies the member Concept of the (subject) Group concept."@en . . . . . . . "specializing facet"@en . "2013-12-03"^^ . "2014-02-03"^^ . "proposed"^^ . "The facet concept group, a group of concepts used to expand:\n- the subject (ESCO) concept\n or\n- all the members concepts of the subject Collection\nto build ESCO (compound) faceted concepts.\n\nAn ESCO concept may have different aspects or facets that can specialize the ESCO concept.\nA well known example is the (foreign) language skills.\n- the main aspect of the (foreign) language skill is the identification of the foreign language\n The specialized concepts thus constructed are:\n - (foreign) language skill Albanian,\n - (foreign) labguage skill Bulgarian,\n - ...\n- 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, ...)\n\nThe 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:\n- first by language then by language skill level\n or\n- first by language skill level then by language\nBoth navigation hierarchies ultimatly hold the same set of (compound) faceted concepts (e.g. \"(foreign) language skill\" \"writing\" \"Bulgarian\".\nIn general:\n- concept\n- - <concept by facet group 1>\n- - - [concept + facet group 1 member]\n- - - - <[concept + facet group 1 member] by facet group 2>\n- - - - - [concept + facet group 1 member + facet group 2 member]\n- - - - - ... (other facet group 2 members)\n- - - ... (other facet group 1 members)\n- - <concept by facet group 2>\n- - - [concept + facet group 2 member]\n- - - - <[concept + facet group 2 member] by facet group 1>\n- - - - - [concept + facet group 2 member + facet group 1 member]\n- - - - - ... (other facet group 1 members)\n- - - ... (other facet group 2 members)"@en . . _:genid54 . _:genid55 . _:genid56 . _:genid55 _:genid56 . _:genid56 . _:genid54 _:genid55 . _:genid54 . . . . "constructed from ESCO concept"@en . "2014-02-03"^^ . "2014-02-03"^^ . "proposed"^^ . "The unique (simple) ESCO concept used to construct the (subject) faceted ESCO concept.\n\nExample (started): Simple concept Teacher is specialized to identify teacher at different education levels.\n- The simple (member) occupation is: \"Teacher\"\n- Assume we have a classification of the levels of education (e.g. \"primary school\", \"high school\", \"university\")\n- The constructed faceted (member) concepts that will be:\n \"primary school teacher\", \"high school teacher\" and \"university teacher\" (this last one occasionally re-labeled as \"university professor\")\n- Each of the constructed faceted (member) concepts will indicate the \"teacher\" also as a skos:broader concept.\n- Each of the constructed faceted (member) concepts will indicate the \"teacher\" as the esco:constructedFrom concept.\n\nExample (completed): Nesting facets - Teacher of a subject at a school level\n- Assume we have a classification of subjects of education (e.g. \"mother tongue\", \"mathematics\", \"theorethical quantum mechanics\").\n Two facet groups are created for this facet (education subject):\n 1) Facet Group: Basic Education Subjects (with \"mother tongue\", \"mathematics\")\n 2) Facet Group: Advanced Education Subjects (with \"mother tongue\", \"mathematics\", \"theorethical quantum mechanics\")\n- The faceted concepts of the 'started' part of the example (\"primary school teacher\", \"high school teacher\", \"university teacher\")\n can be further specialized with the 'Basic Education Subjects' or 'Advanced Education Subjects'.\n- The resulting constructed facets can be \"high school teacher mathematics\", \"university teacher mathematics\", \"university teacher theorethical quantum mechanics\", ...\n- The skos:broader for the new faceted concepts are:\n 1) for \"university teacher mathematics\" and for \"university teacher theorethical quantum mechanics\" : \"university teacher\"\n 2) for \"high school teacher mathematics\" : \"high school teacher\"\n 3) ... \n- Each of these (more) specialized faceted concepts all have the (simple) ESCO occupation \"Teacher\" as value for esco:constructedFrom"@en . . . . . . "If:\n- FC esco:constructedFrom SC\n- FC esco:plusUF UF\n- lang(UF/xl:literalForm) = L\n- SC xl:prefLabel PLsc\n- lang(PLsc/xl:literalForm) = L\nThen\n- PLsc iso-thes:plusUFTerm UF\n- UF iso-thes:plusUseTerm PLsc"^^ . . "containing group"@en . "2013-06-27"^^ . "2013-06-27"^^ . "released"^^ . "The ESCO Group (pillar) concept containing the subject ESCO concept as a member."@en . . . . . _:genid57 . _:genid58 . _:genid57 _:genid58 . _:genid58 . _:genid57 . _:genid59 . _:genid60 . _:genid59 _:genid60 . _:genid61 . _:genid60 _:genid61 . _:genid61 . _:genid59 . . "belongs to ISCO Group with code"@en . "2013-12-03"^^ . "2013-12-03"^^ . "proposed"^^ . "The direct hierarchical broader ISCO concept of the (subject) ESCO occupation.\nThe 'direct' (or one step) relationship is to be understood in terms of extending the ISCO taxonomy the (object) concept belongs to.\n\nThe 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)."@en . . . . "narrower instance"@en . "2013-06-27"^^ . "2013-06-27"^^ . "released"^^ . "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.\n\nThe (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."@en . . . . . . . . . "competence"@en . "2013-12-03"^^ . "2014-08-10"^^ . "proposed"^^ . "The ESCO skill/competence related to (or asserted by) the subject ESCO qualification.\nI.e. when asserted on a subject qualification, the related competence is a learning outcome of that qualification."@en . . . . . . "has optional skill"@en . "2013-12-03"^^ . "2013-12-03"^^ . "proposed"^^ . "The ESCO skill or competence that is relevant (but optional) for the subject occuption."@en . . . _:genid62 . _:genid63 . _:genid64 . _:genid63 _:genid64 . _:genid64 . _:genid62 _:genid63 . _:genid62 . . . "is optional skill for"@en . "2014-08-10"^^ . "2014-08-10"^^ . "proposed"^^ . "The inverse of esco:relatedOptionalSkill."@en . . . . . _:genid65 . _:genid66 . _:genid67 . _:genid66 _:genid67 . _:genid67 . _:genid65 _:genid66 . _:genid65 . . "has essential skill"@en . "2013-12-03"^^ . "2013-12-03"^^ . "proposed"^^ . "The ESCO skill or competence that is essential for the subject occupation or skill."@en . . . _:genid68 . _:genid69 . _:genid70 . _:genid69 _:genid70 . _:genid70 . _:genid68 _:genid69 . _:genid68 . . . "is essential skill for"@en . "2014-08-10"^^ . "2014-08-10"^^ . "proposed"^^ . "The inverse of esco:relatedEssentialSkill."@en . . . . . _:genid71 . _:genid72 . _:genid73 . _:genid72 _:genid73 . _:genid73 . _:genid71 _:genid72 . _:genid71 . . "qualification"@en . "2013-12-03"^^ . "2013-12-03"^^ . "proposed"^^ . "The ESCO qualification (certification) that is required for the subject occupation or skill."@en . . . _:genid74 . _:genid75 . _:genid76 . _:genid75 _:genid76 . _:genid76 . _:genid74 _:genid75 . _:genid74 . . . "legally required qualification"@en . "2013-12-03"^^ . "2013-12-03"^^ . "proposed"^^ . "The ESCO qualification (certification) that is legally required for the subject occupation or skill.\nDetails for the requirements must be given in the relationship description.\n\nOccasionally, 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).\nIn case the legal requirement is region specific, the relationship:\n- should detail the restriction in the relation description\n- could be tagged with a location or NUTS code (see http://data.europa.eu/esco/model#location)"@en . . . . . _:genid77 . _:genid78 . _:genid79 . _:genid78 _:genid79 . _:genid79 . _:genid77 _:genid78 . _:genid77 . . . "has ESCO relationship"@en . "2013-12-03"^^ . "2013-12-03"^^ . "proposed"^^ . "The detailed (typed, annotated and documented) ESCO relationship (see http://data.europa.eu/esco/model#Relationship) for the subject ESCO concept.\n\nThe relationship identifies a related ESCO concept.\nThe relationship properties provide formal semantics to the ESCO concept relationship."@en . . . . . . . . . "has ESCO relationship list"@en . "2014-10-23"^^ . "2014-10-23"^^ . "proposed"^^ . "The ordered set of relationships starting at the subject ESCO pillar concept.\n\nFor any resource, every item in the list given as the value of the\n esco:hasRelationshipList property is also a value of the esco:hasRelationship property."@en . . . . . . . . "division characteristic"@en . "2014-03-07"^^ . "2014-03-07"^^ . "proposed"^^ . "The ESCO facet group the thesaurus array is being built from.\n\nWhen an ESCO concept is specialized by a facet group, the ESCO thesaurus introduces that set (or branch) of specializations with a Thesaurus.Array.\n\nExample: The occupation \"Teacher\" can be specialized by 'education level' or by 'education subject'.\nAt 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.\nAt concept publication time, each specializing facet will be represented as an iso-thes:ThesaurusArray having as members the (compound) faceted concepts.\nFor each ESCO thesaurus array this property (esco:hasDivisionCharacteristic) recalls the FacetGroup it was created for.\n\nNote: 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."@en . . . . . . . "replaced by"@en . "2013-12-03"^^ . "2013-12-03"^^ . "proposed"^^ . "Typical for a deprecated concept that has been replaced by one or more other concepts.\n\nShould be made a sub-property of, or be replaced by: http://purl.org/dc/terms/isReplacedBy"@en . . . . . . "transitive replaced by"@en . . "2014-05-30"^^ . "2014-05-30"^^ . "proposed"^^ . "Typical for a chain of changes and deprecations of a concept over different versions."@en . . . . . "transitively replaces"@en . . "2014-05-30"^^ . "2014-05-30"^^ . "proposed"^^ . "Typical for a chain of deprecated concepts that replaces one or more other concepts over more than one version."@en . . . . . . "replaces"@en . "2013-12-17"^^ . "2013-12-17"^^ . "proposed"^^ . "Typical for a deprecated concept that replaces one or more other concepts.\n\nShould be made a sub-property of, or be replaced by: http://purl.org/dc/terms/replaces"@en . . . . . . . "supported language"@en . "2013-06-27"^^ . "2013-12-03"^^ . "released"^^ . "Denotes a description of the languages supported by the (subject) concept scheme.\nRequired for ESCO taxonomy or thesauri."@en . . . . . "to ESCO concept"@en . "2013-12-03"^^ . "2014-02-03"^^ . "proposed"^^ . "The ESCO concept referred by the (subject) ESCO relationship.\nThe esco:Relationship gives a more elaborate semantic description of related ESCO concepts. These related concepts are identied by the esco:Relationship propertief\n- esco:isRelationshipFor\n- esco:refersConcept\nFurther semantics are provided by\n- a relationshipt type\n- a description\n- .. (other possible extensions)"@en . . . . . "has top member"@en . "2013-12-03"^^ . "2013-12-03"^^ . "proposed"^^ . "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.\nThe top may be concepts as well as collections."@en . . . . "undefined"@en . "2013-12-03"^^ . "released"^^ . "true"^^ . "Deprecated with Model version 1."@en . "ESCOv0 has 102K undefined relations.\nThese cannot be inherited in v1 as occupations are redefined - maybe after merging a decision needs to be taken:\n- make relatedOptionalSkill\n- make relatedEssentialSkill\n- remove the related:undefined."@en . "undefined skill is a skill that has no optional, recommended or required property assigned to it."@en . . . . . "undefined skill of"@en . "2013-12-03"^^ . "http://data.europa.eu/esco/model"^^ . "released"^^ . "true"^^ . "Deprecated with Model version 1."@en . "ESCOv0 has 102K undefined relations. See http://data.europa.eu/esco/model#undefined."@en . . . . "stable"^^ . "member"@en . "Indicates a member of a Group"@en . . . . . . "nickname"@en . "testing"^^ . "A short informal nickname characterising an agent (includes login identifiers, IRC and other chat nicknames)."@en . . "name"@en . "testing"^^ . "A name for an agent."@en . . . . "personal mailbox"@en . "stable"^^ . "A personal mailbox, ie. an Internet mailbox associated with exactly one owner, the first owner of this mailbox. This is a 'static inverse functional property', in that there is (across time and change) at most one individual that ever has any particular value for foaf:mbox.\n\nThe used URI format is according http://tools.ietf.org/html/rfc6068: \"mailto:...@...\""@en . . . . . "phone"@en . "testing"^^ . "A phone, specified using fully qualified tel: URI scheme \"tel:+##...##\" - see http://www.ietf.org/rfc/rfc2806.txt."@en . . . . "homepage"@en . "stable"^^ . "A homepage"@en . . . . . . "editorial status"@en . "2014-07-03"^^ . "2014-07-03"^^ . "proposed"^^ . "The business or editorial status of a concept or label"@en . . _:genid80 . _:genid81 . _:genid82 . _:genid81 _:genid82 . _:genid82 . _:genid80 _:genid81 . _:genid80 . . . "true"^^ . "awarding body (descriptive)"@en . "2013-12-03"^^ . "2013-12-03"^^ . "proposed"^^ . "An awarding body provided using a descriptive text.\nA more precise definition of an awarding body known by ESCO can be given using http://data.europa.eu/esco/model#hasAwardingBody"@en . . . . . "qualification expiration period"@en . "2013-06-27"^^ . "released"^^ . "Period how long a qualification is valid.\n\nExample: 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."@en . . . . . "has poly-hierarchy"@en . . "2013-06-27"^^ . "2013-12-03"^^ . "released"^^ . "true: Indicates wether a ESCO thesaurus/taxonomy supports poly-hierarchy. Not present or false indicate mono-hierarchy."@en . . . . . "is indirectly included"@en . . "2013-12-03"^^ . "2013-12-03"^^ . "proposed"^^ . "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.\n\nCould also be applied (if unambiguous) to skills and occupations.\n\nAssertion (to 'true') is required in case external contribution must be affirmed."@en . . . . "is transversal"@en . "true"^^ . . "2013-12-03"^^ . "2013-12-03"^^ . "proposed"^^ . "Typical to indicate that a concept (like a skill) is not job or sector specific. It is cross sector.\n\nMay also be applied (if unambiguous) to qualifications and occupations.\n\nAssertion (to 'true') is required in case transversality must be affirmed.\n\nSkill re-usability levels can be tagged in case the level implies transversal scope of the skills having the re-usability level."@en . _:genid83 . _:genid84 . _:genid85 . _:genid84 _:genid85 . _:genid85 . _:genid83 _:genid84 . _:genid83 . . . "country code (A2)"@en . "2013-06-27"^^ . "2013-06-27"^^ . "released"^^ . "ISO 3166 country code - A2"@en . . . . . "country code (A3)"@en . "2013-06-27"^^ . "2013-06-27"^^ . "released"^^ . "ISO 3166 country code - A3"@en . . . . . . "language"@en . "2013-06-27"^^ . "2013-06-27"^^ . "released"^^ . "The language of the subject resource."@en . "ESCO v0 -> ESCO v1 literals having XMLLiteral parsetype are now coded as pllain literal with mark-up escaped. Hence the standard RDF language tagging of literals can be used.\nsee http://data.europa.eu/esco/model#noteLiteral"@en . . . . "true"^^ . "note text"@en . "2013-06-27"^^ . "2013-06-27"^^ . "Embedded hyperlinks need to be parsed and validated on import.\nContent needs to be XHTML validated on import."^^ . "http://data.europa.eu/esco/model#language"^^ . "released"^^ . "An xml literal taking a plain text or xhtml.body.type content type.\n\nThe property typically allows to validate the content of a SKOS note (or any of its SKOS sub-properties).\nNotes are then provided as blank nodes with this property and with the ESCO language property.\n\nThe motivations for this complex approach are:\n- Provides structure content (XML literal) according a format that can be validated.\n- xml:lang and rdf:parseType=\"Literal\" can not be provided on the same property."@en . . . . "reference language"@en . "2013-06-27"^^ . "2013-06-27"^^ . "released"^^ . "Reference language for a concept.\n\nTypically 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.)\n\nIn 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."@en . . . . . "relevant URL"@en . "2013-06-27"^^ . "2013-06-27"^^ . "released"^^ . "A web site that is relevant for the subject (any modelled class, including an ESCO concept or term).\n\nSuch URL may be part literal content value of a description, a definition or a scope note.\nA relevant URI may be language specific (hence the range is literal)."@en . . . _:genid86 . _:genid87 . _:genid88 . _:genid87 _:genid88 . _:genid88 . _:genid86 _:genid87 . _:genid86 . . "Identifier"@en . "2013-06-27"^^ . "2013-12-03"^^ . "released"^^ . "An unambiguous reference to the resource within a given context.\n\nRecommended best practice is to identify the resource by means of a string conforming to a formal identification system.\n\nESCO note:\nESCO formats identiefers using\n{qualifier}:{identifier}\n\n{qualifier} is one of:\nCEFR: Common European Framework of Reference for Languages: Learning, Teaching, Assessment\nEQF: European Qualifications Framework identifer\nISCED 2013 FoET: UNESCO ISCED 2013/FoET identifier for \nESCO-CTC: Esco tool CTC\nESCO ITM: ESCO TMS tool (ITM - from Mondeca)\nESCO-TM: Esco tool for Text Mining\nISO 3166-1.A2: 2 character ISO 3166 country code\nISO 3166-1.A3: 3 character ISO 3166 country code\nISO 3166-1.num: Numeric ISO 3166 country identifier\nISO 639.1: The ISO 639-1 code (2 characters)\nISO 639.2T: The ISO 639-2 terminological code (3 characters)\nISO 639.2B: The ISO 639-2 bibliographic code (3 characters)\nISO 639.3: The ISO 639-3 code (3 characters) \u2013 typical for use on sign languages\nNACE rev 2: NACE rev 2 industry sector identifiers\nNUTS 2008: The NUTS classification (Nomenclature of territorial units for statistics) is a hierarchical system for dividing up the economic territory of the EU"@en . . . "stable"^^ . "Agent (foaf)"@en . "An agent (eg. person, group, software or physical artifact).\n\nAgent characteristics used by ESCO:\n- The (full and formal) name of the agent (required) - see http://xmlns.com/foaf/0.1/name\n- The short name or nickname of the agent (optional) - see http://xmlns.com/foaf/0.1/nick\n- The phone number(s) of the agent (optional) - see http://xmlns.com/foaf/0.1/phone\n- The home page of the agent (optional) - see http://xmlns.com/foaf/0.1/homepage\n- The e-mail of the agent (optional) - see http://xmlns.com/foaf/0.1/mbox\n\nSome Agent may represent groups. Group members are listed using http://xmlns.com/foaf/0.1/member\n"@en . . . . "stable"^^ . "Person"@en . "A person."@en . . . . . . "stable"^^ . "Organization"@en . "An organization."@en . . . . . "stable"^^ . "Group"@en . "A class of Agents.\nGroup members are listed using http://xmlns.com/foaf/0.1/member"@en . . . "Awarding body"@en . . _:genid89 . _:genid89 . _:genid89 . _:genid89 . . "2013-06-27"^^ . "2013-06-27"^^ . "released"^^ . "The class of awarding bodies registered by ESCO.\n\nAn ESCO registered awarding body is an official or otherwise recognized institution, organization or company that is issuing formal certificates of competence. Some of these certificates are registered as ESCO qualifications (see http://data.europa.eu/esco/model#Qualification). The relationship between an esco:Qualification and an esco:AwardingBody is given by http://data.europa.eu/esco/model#hasAwardingBody.\n\nThe geo-location(s) of an awarding body is given by http://data.europa.eu/esco/model#location"@en . . . . "Work context"@en . . . _:genid90 . _:genid90 . _:genid90 . _:genid90 . "2014-08-10"^^ . "2014-08-10"^^ . "released"^^ . "The class of work contexts registered by ESCO\nA work context iIdentifies types of business, environmental conditions, types of product, etc.\nESCO manages and organizes work context in the concept scheme: http://data.europa.eu/esco/ConceptScheme/WorkContext/cs\n"@en . . . "ESCO pillar Concept"@en . . _:genid91 . _:genid91 . _:genid91 "1"^^ . _:genid91 . . . . . . "2013-06-27"^^ . "2013-12-03"^^ . "http://data.europa.eu/esco/model"^^ . "released"^^ . "The class of ESCO pillar concepts.\n\nESCO pillar concepts are divided in tree semantic classes: esco:Occupation, esco:Skill and esco:Qualification, each organized in a dedicated ConceptScheme.\n\nAll concepts are specializations of skos:Concept and are structured using the skos semantic relationships.\n- 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).\n- sub-properties of skos:related are used to express special relations among ESCO pillar concepts. (e.g. http://data.europa.eu/esco/model#isEssentialSkillFor)\n- sub-properties of the DCMI dcterms:subject capture codified characteristics of ESCO concepts (e.g. http://data.europa.eu/esco/model#hasNACECode, http://data.europa.eu/esco/model#skillType).\n\nThe skos:broader and skos:narrower concepts are the prime concepts organizing hierarchy among ESCO pillar concepts.\nThe hierarchical structure is modelled according three classes\n- 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.\n- esco:LeafGroupConcept (see http://data.europa.eu/esco/model#LeafGroupConcept) - the lowest top level concept, a special esco:GroupConcept.\n- esco:MemberConccept (see http://data.europa.eu/esco/model#MemberConcept) - the concepts used for coding or annotating CV and Job Postings.\n\nThe ESCO concepts are also divided according their analytical structure. There are two sub-classes:\n- simple concepts (see http://data.europa.eu/esco/model#SimpleConcept) and\n- compound concepts (see http://data.europa.eu/esco/model#FacetedConcept).\n\nA 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.\n\nAmong hierarchical related ESCO pillar concepts the following inheritance rules apply\n- the ESCO relationships from any broader transitive concept are inherited with the following restrictions\n in case a relationship with the same skill is typed as well essential as optional, only the essential skill relationship is inherited\n in case a relationship with the same qualification is typed as well required as legally required, only the legally required qualification relationship is inherited\n- 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.\n\nThe ESCO concepts are specializations of skos:Concepts and use skos:note specializations (see http://www.w3.org/2004/02/skos/core#note).\n- the skos:definition gives the full description of the ESCO concept.\n- the skos:scopeNote is the practical instruction for when to apply the ESCO concept.\n- the skos:historyNote gives a system log of significant versioned changes to the ESCO concept.\n- the skos:changeNote gives the human provided documentation for ESCO concept version modifications.\n\nCharacteristics:\n- 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,\n- Any ESCO concept may refer relevant hyperlinked sources of reference or of information. See http://data.europa.eu/esco/model#relevantURL.\n\nEach ESCO pillar concept may hold provenance and audit metadata:\n- rightsHolder: the owner (http://purl.org/dc/terms/rightsHolder) - optional\n- editorial status (http://data.europa.eu/esco/model#editorialStatus) - required\n- publishing status (http://purl.org/iso25964/skos-thes#status) - required\n- creator : the author (http://purl.org/dc/terms/creator) - optional\n- contributor : modifier (http://purl.org/dc/terms/contributor) - required\n- modified : last modification date (http://purl.org/dc/terms/modified) - required"@en . . . . . . . . . . . . . . _:genid92 . _:genid93 . _:genid92 _:genid93 . _:genid93 . _:genid92 . _:genid94 . _:genid95 . _:genid94 _:genid95 . _:genid96 . _:genid95 _:genid96 . _:genid96 . _:genid94 . . "Concept scheme (ESCO pillar)"@en . . "2013-06-27"^^ . "2013-12-03"^^ . "http://data.europa.eu/esco/model"^^ . "The ESCO concept schemes (pillars)\n\nThe \"current\" ESCO scheme and historic versions of the ESCO scheme will be instances of this class. Typically, these support poly-hierarchy.\n\nThe 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.\nAs of ESCO v1 though, ISCO is not a part anymore of the ESCO hierarchy. However, the ESCO v0 part corresponding to ISCO08 will be maintained a a separate versioned taxonomy.\nESCO v1 occupations will be mapped (see http://data.europa.eu/esco/model#memberOfISCOGroup a sub-property of http://www.w3.org/2004/02/skos/core#broadMatch) to ISCO (level 4) concepts.\n\nProvenance information that may be added:\n- rightsHolder: the owner (http://purl.org/dc/terms/rightsHolder) - required\n- publishing status: (http://purl.org/iso25964/skos-thes#status) - required\n- creator : the author (http://purl.org/dc/terms/creator) - required\n- contributor : modifier (http://purl.org/dc/terms/contributor) - required\n- modified : last modification date (http://purl.org/dc/terms/modified) - required"@en . . . . . . . "Country"@en . . "2013-06-27"^^ . "2013-12-03"^^ . "released"^^ . "Relevant standards for country locations are documented under the super class: http://data.europa.eu/esco/model#Location"@en . . . "Level (European Qualification Framework)"@en . . "2013-06-27"^^ . "2013-12-03"^^ . "proposed"^^ . "The EQF levels have been published as recommendation by the EU Publication office under CELEX number 32008H0506(01)\n See http://publications.europa.eu/resource/celex/32008H0506%2801%29"@en . "URI of ESCO copy of EQF will need to be updated in order to get LOD properly working from ESCO platform."@en . . . . "Facet concept group"@en . . "2013-12-03"^^ . "2013-12-03"^^ . "proposed"^^ . "A Facet concept group (i.e. an instance of the class esco:FacetConceptGroup) is a sub-set of concepts from a facet.\nA facet is a supporting taxonomy for ESCO. Examples are:\n- Languages\n- Species\n- Tools\n\nAn (instance of the) esco:FacetConceptGroup is a sub-set of concepts from a facet.\nEach esco:FacetConceptGroup is defined by the ESCO concept scheme http://data.europa.eu/esco/ConceptScheme/FacetConceptGroups.\nThe typical use of an esco:FacetConceptGroup is to specialize one or more ESCO pillar concepts. (see http://data.europa.eu/esco/model#facet).\nThe specialization creates narrower (or transitive narrower) concepts of the specialized ESCO pillar concept.\nEach specialization is a Faceted (or compound) concept (with type http://data.europa.eu/esco/model#FacetedConcept) having as component concepts:\n- the ESCO pillar object being specialized and\n- one member concept from the facet group.\n\nAn ESCO pillar concept is either an esco:SimpleConcept or an esco:FacetedConcept \n\nAn ESCO concept can be specialized in different ways using different Facet concept groups\n\nThe Facet concept group may be structured:\n- members of an esco:FacetConceptGroup can have hierarchical relationships (skos:broader and skos:narrower) among its member concepts.\n 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.\n See also skos:topMember.\n- an esco:FacetConceptGroup can be an oredered collection.\n In this case, the order among the spicialized concepts constructed with this facet group will mirror the order of the facet group.\n- an esco:FacetConceptGroup can have different sub-collections (i.e. have skos:member that are a skos:Collection and an iso-thes:ThesaurusArray).\n Collections only serve to organize the constructed faceted concepts such that the faceted concepts\n that are specializations based on the structured Facet concept group are organized by thesaurus arrays\n that each mirror an original thesaurus array of the Facet concept group.\n\nExample: the language FacetConceptGroup can have as members\n- the (possibly ordered) collection of spoken languages\n having as members the language concepts\n- the (possibly ordered) collection of sign languages\n having as members the sign language concepts\n\nThe name of the facet group is given by skos:prefLabel"@en . . . . . . _:genid97 . _:genid97 . _:genid97 . _:genid97 . . "Group of overlapping skills"@en . . "2014-08-10"^^ . "2014-08-10"^^ . "proposed"^^ . "The class of collections of overlapping esco:Skill concepts. All skills within one collection of overlapping skills have overlapping semantics with each other.\n\nThe collection has a name using http://www.w3.org/2004/02/skos/core#prefLabel .\n\nAs 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."@en . . _:genid98 . _:genid98 . _:genid98 . _:genid98 . . . "FoET code"@en . . "2013-12-03"^^ . "2013-12-03"^^ . "proposed"^^ . "The class of ISCED 2013/FoET classificaton code (International Standard Classification of Education: Fields of Education and Training 2013)\n\nThe Fields of Education and Training have been submitted to the UNESCO Conference - session 37 - Paris.\nThe version submitted for resolution is available from: http://unesdoc.unesco.org/images/0022/002218/221863e.pdf\n\nOther original source references:\n- http://www.uis.unesco.org/Education/Documents/isced-37c-fos-review-222729e.pdf\n- http://www.uis.unesco.org/EDUCATION/Pages/international-standard-classification-of-education.aspx"@en . . . . . "Group concept"@en . . _:genid99 . _:genid99 . _:genid99 . _:genid99 . _:genid100 . _:genid100 . _:genid100 "1"^^ . _:genid100 . . "2013-06-27"^^ . "2013-12-03"^^ . "released"^^ . ""@en . "Concepts\n 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.\n \nTypically these group concepts are NOT used in CV or job postings, but serve organization, reporting and statiscal purposes.\nThe member concepts of group concepts are used for coding or annotating CV or job postings.\n\nA Group concept typically will be\n- in the upper levels of an ESCO pillar (or concept schema)\n- in an external concept schema (e.g. ISCO)"@en . . . "ESCO pillar concept Label"@en . . "2013-06-27"^^ . "2013-12-03"^^ . "http://data.europa.eu/esco/model"^^ . "released"^^ . "The class of labels used on esco pillar Concepts.\n\nCharacteristics\n- An ESCO label may be motivated by relevant original sources. These sources are referenced uising http://data.europa.eu/esco/model#relevantURL\n- An ESCO label typically gets label roles detailing the gender specific characteristics of the label (see http://data.europa.eu/esco/model#hasLabelRole)\n\nProvenance information that may be added:\n- rightsHolder: the owner (http://purl.org/dc/terms/rightsHolder) - optional\n- editorial status (http://data.europa.eu/esco/model#editorialStatus) - optional\n- workflow status (http://data.europa.eu/esco/flow#status) - required\n- creator : the author (http://purl.org/dc/terms/creator) - optional\n- contributor : modifier (http://purl.org/dc/terms/contributor) - required\n- modified : last modification date (http://purl.org/dc/terms/modified) - required"@en . . . . . . . . "Label role"@en . "http://data.europa.eu/esco/model"^^ . _:genid101 . _:genid101 . _:genid101 . _:genid101 . . "2013-06-27"^^ . "2013-12-03"^^ . "proposed"^^ . "Allows to capture one or more particular characteristics of a name.\n\nExample usage: Gender related terms.\n- ESCO concepts may get a gender neutral term as preferred label. The gender specific terms are provided as alternate labels.\n- Relevant use cases: \n - concept look-up based on gender specific term\n - Job posting generation with gender neutral terms\n - CV generation with gender specific terms"@en . . "ESCO relationship type"@en . "http://data.europa.eu/esco/model"^^ . "The class of the types of ESCO relations.\nThe concepts having this type are managed in the small SKOS taxonomy (see http://data.europa.eu/esco/ConceptScheme/RelationshipType)."@en . _:genid102 . _:genid102 . _:genid102 . _:genid102 . . "2014-04-16"^^ . "2014-04-16"^^ . "proposed"^^ . . "Language"@en . . _:genid103 . _:genid103 . _:genid103 "1"^^ . _:genid103 . "2013-06-27"^^ . "2013-12-03"^^ . "http://data.europa.eu/esco/model"^^ . "released"^^ . "The class of language concepts. \nEach language is \n- labeled using skos:prefLabel in all of the other languages and \n- identified using the ESCO esco:language property (value = ISO 2-char language code). \n\nThe class provides the set of languages that can be in use in the thesaurus. \nTwo ESCO concept schemes provide language concepts:\n- http://data.europa.eu/esco/ConceptScheme/ISO639/cs - all languages of ISO 639-1 and ISO 639-2\n- http://data.europa.eu/esco/ConceptScheme/ISO639-3/cs - all sign languages listed in ISO 639-3\n\nThe esco:ConceptScheme identifies the languages actually used via its property esco:supportedLanguage."@en . . "Leaf-group concept"@en . . "2013-06-27"^^ . "2013-06-27"^^ . "released"^^ . "A Group (or aggregation) concept, having no sub-groups anymore.\n\nNarrower concepts only can be members (or narrower instances) of the group concept.\nThe specialization http://data.europa.eu/esco/model#narrowerInstance of skos:narrower is used to identify the top level members of the group."@en . . . . "Location"@en . . "2013-06-27"^^ . "2013-12-05"^^ . "proposed"^^ . "A teritorial area like a federation, a country, a region, a jurisdiction area.\n\nStandards useful for locations and regions:\n- ISO 3166\n- NUTS - http://epp.eurostat.ec.europa.eu/portal/page/portal/nuts_nomenclature/introduction (extends ISO 3166 with sub-regions)\n- geonames - http://www.geonames.org/ (includes ISO 3166)\n- EU publication Office - http://publications.europa.eu/mdr/authority/country/index.html"@en . . . "Member concept" . . _:genid104 . _:genid104 . _:genid104 . _:genid104 . "2013-06-27"^^ . "2013-06-27"^^ . "released"^^ . "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.\nExample: A particular occupation, not a group of occupations.\nThese concepts in general have\n- (1) a http://data.europa.eu/esco/model#broaderInstance relationship to http://data.europa.eu/esco/model#LeafGroupConcept\n- (2) one or more http://data.europa.eu/esco/model#memberOfGroup relationships to http://data.europa.eu/esco/model#GroupConcept\nHowever, 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."@en . . . . . "NACE code"@en . . "2013-12-05"^^ . "2013-12-05"^^ . "Industry sector code NACE rev2\n\nThe 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\nThe 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.\nESCO keeps a SKOS compliant copy of NACE codes. These are organized in the concept scheme http://data.europa.eu/esco/ConceptScheme/NACErev2/cs"@en . . . . . "Occupation"@en . . _:genid105 . _:genid105 . _:genid105 . _:genid105 . . . "2013-06-27"^^ . "2013-06-27"^^ . "released"^^ . "2013-06-27\nAn Occupation that is a MemberConcept:\n- Initially coming from the Occupations listed by the Swedisch PES in tab of file Taxonomy 3 - Taxonomy db DB 20 l-corr.xls.\nAn Occupation that is a GroupConcept:\n- Initially coming from the file ISCO '88 codes 25l.xls"@en . "The class of ESCO Occupation concepts. An Occuaption is an ESCO pillar concept (see http://data.europa.eu/esco/model#Concept).\nOccupation have an broader match relation to an ISCO level 4 code (see http://data.europa.eu/esco/model#memberOfISCOGroup).\n\nCharacteristics of an Occupation:\n- The relevant industry sector for an occupation is given by the Eurostat NACE codes (see http://data.europa.eu/esco/model#hasNACECode)\n- The different Work context applicable for an occupation (see http://data.europa.eu/esco/model#hasWorkContext).\n\nAn occupation may be related to\n- esco:Skill (see http://data.europa.eu/esco/model#relatedEssentialSkill and http://data.europa.eu/esco/model#relatedOptionalSkill)\n- esco:Qualification (see http://data.europa.eu/esco/model#relatedQualification and http://data.europa.eu/esco/model#relatedLegallyRequiredQualification)\n\nOccupations having a legal or other regulations in a specific region\n- 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)\n- could identify such a region with the location property (see http://data.europa.eu/esco/model#location)\n\nESCO Occupations are maintained in the ESCO concept scheme http://data.europa.eu/esco/ConceptScheme/ESCO_Occupations."@en . . . . . . . . "Qualification" . . _:genid106 . _:genid106 . _:genid106 "1"^^ . _:genid106 . _:genid106 . _:genid107 . _:genid107 . _:genid107 . _:genid107 . . "2013-06-27"^^ . "2013-06-27"^^ . "released"^^ . "The class of ESCO qualifications.\nAn ESCO qualification is an ESCO concepts of the ESCO qualification pillar.\n\nA qualification is an official or formal certificaton of one or more aquired skills or competences (i.e the learning outcomes - see http://data.europa.eu/esco/model#relatedCompetence).\n\nAn qualification may be related to\n- esco:Skill (see http://data.europa.eu/esco/model#relatedEssentialSkill and http://data.europa.eu/esco/model#relatedOptionalSkill)\n- esco:Occupation (see http://data.europa.eu/esco/model#relatedQualification and http://data.europa.eu/esco/model#relatedLegallyRequiredQualification)\nThe property http://data.europa.eu/esco/model#hasRelationship details the relationships (see http://data.europa.eu/esco/model#Relationship)\n\nCharacteristics of a qualification\n- The certificate is issued by an awarding body (see http://data.europa.eu/esco/model#hasAwardingBody).\n- The level of the qualification may be expressed according the European Qualification Framework (see http://data.europa.eu/esco/model#hasEQFLevel).\n- The subject area of the qualification may be expressed according the UNESCO Institute of Statistics standard for the Fields of Education and Training (FoET - ISCED, see http://data.europa.eu/esco/model#hasFoETCode)\n- The property http://data.europa.eu/esco/model#expirationPeriod indicates the qualification is limited for a period of time. Such a limitation may be provided in a descriptive way using the qualification description (see http://www.w3.org/2004/02/skos/core#definition)\n- The value 'true' of the boolean flag http://data.europa.eu/esco/model#isIndirect indicates the Qualifications is not managed by ESCO but represented by ESCO based on an external source (e.g. national qualifications)."@en . . . . "ESCO concepts Relationship"@en . _:genid108 . _:genid108 . _:genid108 . _:genid108 "1"^^ . _:genid108 . _:genid109 . _:genid109 . _:genid109 . _:genid109 "1"^^ . _:genid109 . "2013-12-03"^^ . "2014-08-10"^^ . "approved"^^ . "The class of directed relationships between two ESCO Pillar concepts (e.g. between an esco:Occupation and an esco:Qualification).\n\nThe relationship:\n- starts from the ESCO concept identified by http://data.europa.eu/esco/model#isRelationshipFor.\n- 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)\n- ends in the ESCO concept identified by http://data.europa.eu/esco/model#refersConcept.\n- is typed by the tagging property http://data.europa.eu/esco/model#hasRelationshipType.\nA relationship may be industry sector or location specific. This can be acieved by tagging the relationship using esco:hasNACECode or esco:location respectively."@en . . . . . . . "Faceted ESCO concept"@en . . "2014-02-03"^^ . "2014-02-03"^^ . "proposed"^^ . "The class of compound ESCO pillar concepts.\nA 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')\n\nAn ESCO concept is either a faceted concept or a simple concept (see http://data.europa.eu/esco/model#SimpleConcept).\n\nAn 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).\nA specializing facet is a group of concepts with a common characteristic (e.g. the group of music instruments).\nThe specialization makes a compound of the ESCO concept and of one concept of each of its related specializing facets.\n\n- During the editorial phase, one or more faceted concepts may be created ad hoc by the ESCO taxonomists.\n- 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.\n- Each faceted concept is the specialization (i.e. the skos:narrowerTransitive) of an ESCO simple concept (see http://data.europa.eu/esco/model#constructedFrom)\n- All facet componets (i.e. the facet values) of the faceted conept are given by the property http://data.europa.eu/esco/model#hasFacet \n\nUniqueness rule: \nTwo instances of esco:FacetedConcept are the same if and only if both instances\n- refer the same simple ESCO concept using http://data.europa.eu/esco/model#constructedFrom\n- refer the same set of components (facet values) using http://data.europa.eu/esco/model#hasFacet\n\nThe faceted concept inherits certain characteristics from the Simple Concept it is constructed from:\n- the ESCO pillar type (Occupation, Skill or Qualification) of its simple concept it is constructed from (see esco:constructedFrom).\n- the memberOfISCOGroup of the occasional Occupation it is constructed from\n- the skillType and the skillReuseLevel of the occasional Skill it is constructed from\nFurther, inheritance rules apply as on ESCO concepts (see http://data.europa.eu/esco/model#Concept)."@en . "\nThe preferred label of a Faceted concept need not be persisted in the editorial system. It may be automatically constructed on publishing as follows:\n {FacetedConcept prefLabel} := {SimpleConcept prefLabel} + ': ' + {facet prefLabel} ( ' / ' + {facet prefLabel} ) *\n where facet prefLabels are ordered alhabetically.\n The (gender related) label roles are inherited from the prefered label of the SimplConcept.\nOccasionally the automated pref label will be overruled by a compound label."@en . _:genid110 . _:genid110 . _:genid110 . _:genid110 "1"^^ . _:genid110 . _:genid111 . _:genid111 . _:genid111 . _:genid111 "1"^^ . _:genid111 . . . . "Simple ESCO concept"@en . . "2014-02-03"^^ . "2014-02-03"^^ . "proposed"^^ . "The class of simple ESCO concepts.\n\nA simple ESCO concept is not decomposed into components (for compound ESCO concepts see http://data.europa.eu/esco/model#FacetedConcept).\nA 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."@en . . . . . "ESCO concept used for sector breakdown."@en . "true"^^ . . "2014-02-03"^^ . "2014-02-03"^^ . "proposed"^^ . "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.\nIt is not an industry sector, but it may be tagged with NACE codes.\n\nThis notion is specifically used for organizing the ESCO thesaurus creation (cfr. ESCO v1 methdology and SREF groups)."@en . . . "Skill"@en . . _:genid112 . _:genid112 . _:genid112 . _:genid112 . _:genid113 . _:genid113 . _:genid113 . _:genid113 "1"^^ . _:genid113 . "2013-06-27"^^ . "2013-12-03"^^ . "released"^^ . "2013-06-27:\nA Skill that is a MemberConcept:\n- Initially (i.e. ESCOv0) coming from the Swedisch PES Skills tab in file Taxonomy 3 - Taxonomy db DB 20 l-corr.xls.\n- Initially (i.e. ESCOv0) linked as related concepts to leaf occupation groups as described in ISCO_SKILLS.xls.\nA Skill that is a GroupConcept:\n- Is created by ESCO"@en . "A skill may also be an informal recognition of a competence.\nThe recognition typically is obtained by experience, practice or informal tests."@en . "The class of ESCO Skill concepts.\n\nESCO skills are sub-typed (e.g. to differentiate between knowledge and competence).\nThis sub-typing is modelled using the concept scheme http://data.europa.eu/esco/ConceptScheme/SkillCompetenceType and its concept class http://data.europa.eu/esco/model#SkillCompetenceType\n\nESCO skills are organized in accordance with their applicable re-use (potential) across the sectoral breakdown of occupations.\nDetails are provided by https://ec.europa.eu/esco/escopedia/-/escopedia/Cross-sector_skills_and_competences?resetLanguage=true&newLanguage=en.\nThis organization is modelled using the concept scheme http://data.europa.eu/esco/ConceptScheme/SkillReuseLevel and its concept class http://data.europa.eu/esco/model#SkillReuseLevel\nESCO 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.\n\nCharacteristics\n- An ESCO skill sub-type is given by http://data.europa.eu/esco/model#skillType\n- An ESCO skill re-use level is given by http://data.europa.eu/esco/model#skillReuseLevel\n\nAn ESCO Skill may be related to other ESCO concepts.\n- 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\n- Optional related concepts of class esco:Skills are indicated http://data.europa.eu/esco/model#isOptionalSkillFor and http://data.europa.eu/esco/model#relatedOptionalSkill\n- Related qualifications are given by http://data.europa.eu/esco/model#relatedQualification\n- Occupations a skill is essential for are concepts of type esco:Occupation indicated by http://data.europa.eu/esco/model#isEssentialSkillFor\n- Occupations a skill is optional for are concepts of type esco:Occupation indicated by http://data.europa.eu/esco/model#isEssentialSkillFor\nThe property http://data.europa.eu/esco/model#hasRelationship details the relationships (see http://data.europa.eu/esco/model#Relationship)"@en . . . . . . "Competence sub-type"@en . . _:genid114 . _:genid114 . _:genid114 . _:genid114 . . "2013-12-03"^^ . "2013-12-03"^^ . "Sub-Typing of a Skill Concept:\n- Skill/Competence\n- Knowledge"@en . . "Skill reuse level"@en . _:genid115 . _:genid115 . _:genid115 . _:genid115 . . "2014-06-05"^^ . "2013-06-05"^^ . "Re-usability level of a Skill or competence.\nDetails 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\")\n \nThe concept hierarchy in the Skill Reuse Level concept scheme (http://data.europa.eu/esco/ConceptScheme/SkillReuseLevel) must detail the allowed skill hierarchy.\nA skill with re-use level A can only be a broader of a skill with reuse level B if either of the following holds:\n- reuse level A = reuse level B\n- reuse level A is a broader transitive of reuse level B.\nA skill can have at most one re-use level (see http://data.europa.eu/esco/model#Skill)."@en . . . "Agent (DCMI)"@en . "2008-01-14"^^ . "2013-12-03"^^ . "A resource that acts or has the power to act."@en-us . "Examples of Agent include person, organization, and software agent."@en-us . . . "All ESCO published taxonomies.\n- either external but having a skossified clone on the ESCO platform, \n- or constructed within ESCO\nThese concept schemes have as base URI: http://data.europa.eu/esco/ConceptScheme/\n\nA skossified clone will only be maintained for external taxonomies that are not available as LOD."@en . "By ESCO: Captures the compound terms established by the ESCO taxonomists."@en . . "By ESCO: Not directly set by ESCO applications, but inferred from the range of skos-xl:pref:Label or iso-thes:plusUse."@en . "By ESCO: Not directly set by ESCO applications, but inferred from the range of skos-xl:alt:Label."@en .