Presentation is loading. Please wait.

Presentation is loading. Please wait.

DCMI Making Metadata Work Integrating taxonomies with ESCO and applying the ISO25964 SKOS extensions Presentation for a workshop of the ISKO-UK, IRSG and.

Similar presentations


Presentation on theme: "DCMI Making Metadata Work Integrating taxonomies with ESCO and applying the ISO25964 SKOS extensions Presentation for a workshop of the ISKO-UK, IRSG and."— Presentation transcript:

1 DCMI Making Metadata Work Integrating taxonomies with ESCO and applying the ISO25964 SKOS extensions Presentation for a workshop of the ISKO-UK, IRSG and DCMI joint meeting by johan.de-smedt@tenforce.comagis.papantoniou@tenforce.com 2014-06-23Integrating taxonomies with ESCO1 ESCO: European Skills, Competences and Occupations ISO 25964 : Standard for mono lingual and multilingual thesauri SKOS : W3C semantic scheme for simple knowledge Organization Systems http://www.iskouk.org/events/metadata_June_2014.htm

2 ESCO main reference ESCO https://ec.europa.eu/esco/home European Skills, Competences and Occupations DG Employment, Social Affairs and Inclusion and DG Education and Culture of the European Commission develop ESCO in collaboration with stakeholders and with the European Centre for the Development of Vocational Training (Cedefop). An H2020 initiative. DG Employment, Social Affairs and InclusionDG Education and Culture European Centre for the Development of Vocational Training (Cedefop) EC: European Commission DG: directorate general H2020: Horizon 2020, EC programme for Research and Innovation 2014-06-23Integrating taxonomies with ESCO2

3 ESCO objective 2014-06-23Integrating taxonomies with ESCO3 EU: European Union CV: curriculum Vitae JV: Job Vacancy/Posting Provide the EU with a set of cross boarder multi-lingual vocabularies to facilitate EU job market transparency by using the ESCO thesauri as a hub for translating and encoding CV and Job Postings. A set of thesauri/taxonomies (three “pillars”): Occupations Skills and competences Qualifications (certifications) Semantic relationships between concepts of the three pillars Occupations and Skills/Competences: essential and optional skills for an Occupation Occupations and Qualifications: Qualifications required for an Occupation Qualifications an Skills/Competences: Skills asserted by a Qualification (certificate)

4 ESCO Current Status ESCO versions Version 0 is currently published Version 1 is currently ongoing and will make partial upgrades (v0.1, v0.2 …) until v1 is established (from end 2013 until early 2017). Version 0.1 is targeted for publication on 2015-02. Improvements for 3 sectors: Agriculture, Forestry and Fishery; Hospitality and tourism; Veterinary 2014-06-23Integrating taxonomies with ESCO4

5 ESCO v0 on the Web Home https://ec.europa.eu/esco/home https://ec.europa.eu/esco/home 2014-06-23Integrating taxonomies with ESCO5

6 ESCO v0 Example Home 2014-06-23Integrating taxonomies with ESCO6 Occupations

7 ESCO v0 Example Home 2014-06-23Integrating taxonomies with ESCO7 Occupations Navigate ISCO-08 occupation groups hierarchy till occupation level Only alphabetic sorting at occupation level

8 ESCO v0 Example Home 2014-06-23Integrating taxonomies with ESCO8 Occupations Navigate ISCO-08 occupation groups hierarchy till occupation level Occupation detail

9 Graphical representation of the v0 model 2014-06-23Integrating taxonomies with ESCO99

10 ESCO v0 drawbacks Data model No methodological support for integrating with other relevant KOS EQF, FoET, NACE, NUTS, … ISCO 88 Classification systems used by (national) Public Employment Services (PES): E.g. ROME/FR, … Proprietary extension for lay-out and organization No use of thesaurus array for grouping, sorting and structuring lower levels Unqualified use of skos:related Lack of planning for versioning support Content One preferred hierarchy (ISCO 08) ISCO 08 taxonomy is not the ideal, nor the unique for occupation organization system No handling of gender specific labels “Waiter” and “Waitress” No standard framework for detailing the level of Qualification (e.g. EQF) or its subject Area of expertise (e.g. FoET) Accessibility Only a portal with download services but no service API, no LOD, no SPARQL end-point EC: European Commission ILO: International Labour organization EQF: EC European Qualification Framework FoET: UNESCO Fields of Education an Training ISCO: ILO Occupation codes NACE: Eurostat economic activity sector coding NUTS: Eurostat EU region codes ROME/FR: Occupation codes extended for France KOS: Knowledge Organization System LOD: Linked Open Data SPARQL: (Graph) query language 2014-06-23Integrating taxonomies with ESCO10

11 ESCO v1 approach to handling ESCO v0 drawbacks Data model No methodological support for integrating with other relevant KOS EQF, FoET, NACE, NUTS, … ISCO 88 Classification systems used by (national) Public Employment Services (PES): E.g. ROME/FR, … Proprietary extension for lay-out and organization No use of thesaurus array for grouping, sorting and structuring lower levels Unqualified use of skos:related Lack of planning for versioning support Content One preferred hierarchy (ISCO 08) ISCO 08 taxonomy is not the ideal, nor the unique for occupation organization system No handling of gender specific labels “Waiter” and “Waitress” No standard framework for detailing the level of Qualification (e.g. EQF) or its subject Area of expertise (e.g. FoET) Accessibility Only a portal with download services but no service API, no LOD, no SPARQL end-point EC: European Commission ILO: International Labour organization EQF: EC European Qualification Framework FoET: UNESCO Fields of Education an Training ISCO: ILO Occupation codes NACE: Eurostat economic activity sector coding NUTS: Eurostat EU region codes ROME/FR: Occupation codes extended for France KOS: Knowledge Organization System LOD: Linked Open Data SPARQL: (Graph) query language 2014-06-23Integrating taxonomies with ESCO11

12 ESCO v1 General Concept Relationship Guideline (1/3) Use SKOS broader, narrower, and the transitive closures only for hierarchy in a pillar. Add group-membership relation esco:memberOfGroup 2014-06-23Integrating taxonomies with ESCO12

13 Remarks on iso-thes:broaderInstantial and iso-the:broaderGeneric (both not transitive) As iso-thes:broaderInstantial only can describe the member to leaf-group relationship, a general member – group relationship requires a dedicated memberOfGroup property. The sub-property relation: iso-thes:broaderInstantial o skos:broaderTransitive SubPropertyOf esco:memberOfGroup obviously does not work in case the ancestor hierarchy is not a hierarchy of nested groups. Nested groups or classes cannot be captured fully with iso-thes:broaderGeneric because, as it is a sub-property of (the 1 step) skos:broader, the relation cannot be set among (e.g.) the 2-step group 5 and group 513 (on the previous slide). Therefore, similar to the need for a memberOfGroup property complementing skos:broaderInstantial a transitive subGroupOf property would be needed to complement iso-thes:broaderGeneric. The general property chain would then be: iso-thes:broaderInstantial o x:subGroupOf SubPropertyOf esco:memberOfGroup 2014-06-23Integrating taxonomies with ESCO13 SKIP

14 ESCO v1 approach to handling ESCO v0 drawbacks Data model No methodological support for integrating with other relevant KOS EQF, FoET, NACE, NUTS, … ISCO 88 Classification systems used by (national) Public Employment Services (PES): E.g. ROME/FR, … Proprietary extension for lay-out and organization No use of thesaurus array for grouping, sorting and structuring lower levels Unqualified use of skos:related Lack of planning for versioning support Content One preferred hierarchy (ISCO 08) ISCO 08 taxonomy is not the ideal, nor the unique for occupation organization system No handling of gender specific labels “Waiter” and “Waitress” No standard framework for detailing the level of Qualification (e.g. EQF) or its subject Area of expertise (e.g. FoET) Accessibility Only a portal with download services but no service API, no LOD, no SPARQL end-point EC: European Commission ILO: International Labour organization EQF: EC European Qualification Framework FoET: UNESCO Fields of Education an Training ISCO: ILO Occupation codes NACE: Eurostat economic activity sector coding NUTS: Eurostat EU region codes ROME/FR: Occupation codes extended for France KOS: Knowledge Organization System LOD: Linked Open Data SPARQL: (Graph) query language 2014-06-23Integrating taxonomies with ESCO14

15 ESCO v1 General Concept Relationship Guideline (2/3) Use skos:mappingRelation (e.g. broadMatch and relatedMatch) for relations between (statement subject and object) concepts both in different concept schemes or pillars each representing Occupations, Skills or Qualifications or their grouping ancestors. For mapping into other classification systems, use Mapping (e.g. skos:exactMatch, skos:broadMatch, … ) to KOS with overlapping domains ISCO-88, ISCO-08, ROME/FR, … 2014-06-23Integrating taxonomies with ESCO15 ILO: International Labour organization ISCO-88: 1988 ILO Occupation codes ISCO-08: 2008 ILO Occupation codes ROME/FR: Occupation codes extended for France KOS: Knowledge Organization System

16 ESCO v1 Enhancements Mapping relationships 2014-06-23Integrating taxonomies with ESCO16 Accuracy is sometimes problematic - different scope of concepts in different concept schemes

17 ESCO v1 approach to handling ESCO v0 drawbacks Data model No methodological support for integrating with other relevant KOS EQF, FoET, NACE, NUTS, … ISCO 88 Classification systems used by (national) Public Employment Services (PES): E.g. ROME/FR, … Proprietary extension for lay-out and organization No use of thesaurus array for grouping, sorting and structuring lower levels Unqualified use of skos:related Lack of planning for versioning support Content One preferred hierarchy (ISCO 08) ISCO 08 taxonomy is not the ideal, nor the unique for occupation organization system No handling of gender specific labels “Waiter” and “Waitress” No standard framework for detailing the level of Qualification (e.g. EQF) or its subject Area of expertise (e.g. FoET) Accessibility Only a portal with download services but no service API, no LOD, no SPARQL end-point EC: European Commission ILO: International Labour organization EQF: EC European Qualification Framework FoET: UNESCO Fields of Education an Training ISCO: ILO Occupation codes NACE: Eurostat economic activity sector coding NUTS: Eurostat EU region codes ROME/FR: Occupation codes extended for France KOS: Knowledge Organization System LOD: Linked Open Data SPARQL: (Graph) query language 2014-06-23Integrating taxonomies with ESCO17

18 Tagging possibility – NACE hierarchy 2014-06-23Integrating taxonomies with ESCO18

19 ESCO v1 General Concept Relationship Guideline (3/3) Use dct:subject for assigning metadata characterizing ESCO concepts NACE codes, FoET codes, … ESCO v1 makes an occupation group hierarchy as a sector breakdown. The occupation group scope can be detailed by one or more NACE codes Use dct:subject to tag an occupation group with the applicable industry sector codes NACE rev 2; others can be used when applicable Other applications: Use tagging to classify skills and qualifications Allow for tagging of Skills and Qualifications with FoET Sector specific skills (NACE), skill typing, label typing EQF of qualification (certification) level 2014-06-23Integrating taxonomies with ESCO19 EC: European Commission dct: Dublin Core terms EQF: EC European Qualification Framework FoET: UNESCO Fields of Education an Training NACE: Eurostat economic activity sector coding

20 ESCO v1 Enhancements Tagging – approach Recall ESCO v0 to ESCO v1 migration path (see ESCO status - Version v01 planning)ESCO status - Version v01 planning Improvements for 3 sectors: Agriculture, Forestry and Fishery; Hospitality and tourism; Veterinary ESCO editorial teams are organized by sectors (as above) defining occupation groups per sector 2014-06-23Integrating taxonomies with ESCO20

21 ESCO v1 Tagging Occupations with one or more dct:subject ranging over NACE codes 2014-06-23Integrating taxonomies with ESCO21

22 ESCO v1 approach to handling ESCO v0 drawbacks Data model No methodological support for integrating with other relevant KOS EQF, FoET, NACE, NUTS, … ISCO 88 Classification systems used by (national) Public Employment Services (PES): E.g. ROME/FR, … Proprietary extension for lay-out and organization No use of thesaurus array for grouping, sorting and structuring lower levels Unqualified use of skos:related Lack of planning for versioning support Content One preferred hierarchy (ISCO 08) ISCO 08 taxonomy is not the ideal, nor the unique for occupation organization system No handling of gender specific labels “Waiter” and “Waitress” No standard framework for detailing the level of Qualification (e.g. EQF) or its subject Area of expertise (e.g. FoET) Accessibility Only a portal with download services but no service API, no LOD, no SPARQL end-point EC: European Commission ILO: International Labour organization EQF: EC European Qualification Framework FoET: UNESCO Fields of Education an Training ISCO: ILO Occupation codes NACE: Eurostat economic activity sector coding NUTS: Eurostat EU region codes ROME/FR: Occupation codes extended for France KOS: Knowledge Organization System LOD: Linked Open Data SPARQL: (Graph) query language 2014-06-23Integrating taxonomies with ESCO22

23 Example of gender specific labels Requirement CV are gender specific JP are gender neural Solution Coding uses concept Rendering filters application specific label 2014-06-23Integrating taxonomies with ESCO 23 CV: Curriculum Vitae / Resume JP: Job Posting / Vacancy

24 ESCO v1 approach to handling ESCO v0 drawbacks Data model No methodological support for integrating with other relevant KOS EQF, FoET, NACE, NUTS, … ISCO 88 Classification systems used by (national) Public Employment Services (PES): E.g. ROME/FR, … Proprietary extension for lay-out and organization No use of thesaurus array for grouping, sorting and structuring lower levels Unqualified use of skos:related Lack of planning for versioning support Content One preferred hierarchy (ISCO 08) ISCO 08 taxonomy is not the ideal, nor the unique for occupation organization system No handling of gender specific labels “Waiter” and “Waitress” No standard framework for detailing the level of Qualification (e.g. EQF) or its subject Area of expertise (e.g. FoET) Accessibility Only a portal with download services but no service API, no LOD, no SPARQL end-point EC: European Commission ILO: International Labour organization EQF: EC European Qualification Framework FoET: UNESCO Fields of Education an Training ISCO: ILO Occupation codes NACE: Eurostat economic activity sector coding NUTS: Eurostat EU region codes ROME/FR: Occupation codes extended for France KOS: Knowledge Organization System LOD: Linked Open Data SPARQL: (Graph) query language 2014-06-23Integrating taxonomies with ESCO24

25 Extending and Structuring ESCO v1 Provide for dynamic sector specific extensions and specializations Tooling, knowledge, location, … characteristics Can be modelled as facets Structural organization is partially facilitated based on ISO-25964 (http://purl.org/iso25964/skos-thes)http://purl.org/iso25964/skos-thes Thesaurus Array of sibling concepts, Concept group, Compound terms 2014-06-23Integrating taxonomies with ESCO25

26 Example of faceting approach Language groups Language usage groups 2014-06-23Integrating taxonomies with ESCO26

27 Example of faceting approach 2014-06-23Integrating taxonomies with ESCO27 The “ConceptGroup” Languages Provides a “Languages” facet to the “Foreign language” skill The group can be extended as needed, depending business target The concept group is a subset of concepts from a language taxonomy (based on ISO 639) The “ConceptGroup” Language usages Provides a “Language usages” facet to the “Foreign language” skill The group can be extended as needed, depending business target The concept group is a subset of concepts from the Common European Reference Framework for languages (CERF)

28 2014-06-23Integrating taxonomies with ESCO28

29 Labels for compound (or faceted) concepts 2014-06-23Integrating taxonomies with ESCO29 The musician

30 Compound Concept versus Compound Term 2014-06-23Integrating taxonomies with ESCO30

31 Compound Concepts (faceted concepts) Compound concept or Faceted concept Compound concepts are not provided for by the ISO 25964 OWL. Hence the ESCO specific concepts esco:constructedFrom esco:hasFacet Compound terms and compound equivalence The use ISO 25964 compound equivalence is not the appropriate choice Compound terms as provided by ISO 25964 are intended for virtual concepts i.e. concepts not actually present in the taxonomy The ESCO approach does not require for compound concepts to be generated but allows it. Therefore these compound concepts are not (always) virtual. The better alternative is: Directly use SKOS labels on the compound or faceted concepts Derive relationships between component concept labels and compound concept labels from the compound (faceted) concept construct. 2014-06-23Integrating taxonomies with ESCO31 SKIP

32 Thesaurus Array Organization (1/2) 2014-06-23Integrating taxonomies with ESCO32 Concept: Foreign language Relationships between facet groups: facet group language usage is a facet for all members of facet group facet group spoken languages. No demo – still building this Facet 1: Language Facet group spoken languages: can be combined with language usage (en, fr, de, it, es, …) Facet group sign languages: cannot be combined with language usage (sign language [sgn]) ====================================================== Facet 2: Language usage Facet group language usage: all language usage concepts

33 Organization (2/2) 2014-06-23Integrating taxonomies with ESCO33 No demo – still building this

34 ESCO v1 approach to handling ESCO v0 drawbacks Data model No methodological support for integrating with other relevant KOS EQF, FoET, NACE, NUTS, … ISCO 88 Classification systems used by (national) Public Employment Services (PES): E.g. ROME/FR, … Proprietary extension for lay-out and organization No use of thesaurus array for grouping, sorting and structuring lower levels Unqualified use of skos:related Lack of planning for versioning support Content One preferred hierarchy (ISCO 08) ISCO 08 taxonomy is not the ideal, nor the unique for occupation organization system No handling of gender specific labels “Waiter” and “Waitress” No standard framework for detailing the level of Qualification (e.g. EQF) or its subject Area of expertise (e.g. FoET) Accessibility Only a portal with download services but no service API, no LOD, no SPARQL end-point EC: European Commission ILO: International Labour organization EQF: EC European Qualification Framework FoET: UNESCO Fields of Education an Training ISCO: ILO Occupation codes NACE: Eurostat economic activity sector coding NUTS: Eurostat EU region codes ROME/FR: Occupation codes extended for France KOS: Knowledge Organization System LOD: Linked Open Data SPARQL: (Graph) query language 2014-06-23Integrating taxonomies with ESCO34

35 ESCO Efforts for Accessibility Service API based on REST/JSON Can be locally applied and integrated in http based applications LOD API with RDF/XML, N3, Turtle, JSON-LD distribution formats Central ESCO deployment SPARQL end-point for all ESCO content and versioning 2014-06-23Integrating taxonomies with ESCO35 SKIP

36 Problems and Conclusions (1/2) Top level array organization The ISO 25964 OWL does not hold a top level array organization. This could easily be remedied by allowing skos:ConceptScheme to be in the domain of iso- thes:subordinateArray Concept groups holding hierarchies Neither ISO 25964 nor SKOS provide for properties to detail the top members of a group. Though this could be inferred, a “topMember” list is very efficient. The benefit of skos:memberList (rdf:List) for sorting concepts and arrays Avoids the need of a sorting key. Such a key may be problematic (e.g. poly-hierarchy) 2014-06-23Integrating taxonomies with ESCO36

37 Problems and Conclusions (2/2) When mapping concepts in different skos:ConceptScheme, the rdfs:subPropertyOf between skos:mappingRelation (skos:broadMatch, skos:narrowMatch) properties and the respective skos:semanticRelation (skos:broader, skos:narrower) properties Typically gets problematic as it makes a dependency between the hierarchies in the different concept schemes Proposal Make the mentioned property hierarchy not a required part of SKOS or SKOS-XL, but give them as a possible SKOS extension. 2014-06-23Integrating taxonomies with ESCO37

38 Versioning – ideas for next steps Dataset versioning based DCAT (http://www.w3.org/TR/vocab-dcat/),http://www.w3.org/TR/vocab-dcat/ ADMS (https://joinup.ec.europa.eu/asset/adms/home) for dataset and resource versioninghttps://joinup.ec.europa.eu/asset/adms/home Publication Office of the EU Concept and Label versioning PROV-O (http://www.w3.org/TR/prov-o/), ADMShttp://www.w3.org/TR/prov-o/ skos-history (https://github.com/jneubert/skos-history)https://github.com/jneubert/skos-history Versioning ontology for thesaurus or dataset versions https://github.com/JohanDS/Dataset-versioning--for-KOS-data-sets 2014-06-23Integrating taxonomies with ESCO38 EU: European Union ADMS: Asset Description Metadata Schema DCAT: Data Catalog Vocabulary PROV-O: The PROV(enance) Ontology SKIP

39 Versioning taxonomy publications and taxonomy dependencies 2014-06-23Integrating taxonomies with ESCO39 SKIP Per thesaurus, one dataset with fixed URI manages the taxonomy dataset releases, LOD access i.e. the VersionHistorySet Each thesaurus dataset release is detailed by a DCAT dataset record i.e the VersionHistoryRecord A released thesaurus dataset holds an identifier (a URI) for its VersionHistoryRecord and to the VersionHistorySet

40 Thank you Q&A 2014-06-23Integrating taxonomies with ESCO40


Download ppt "DCMI Making Metadata Work Integrating taxonomies with ESCO and applying the ISO25964 SKOS extensions Presentation for a workshop of the ISKO-UK, IRSG and."

Similar presentations


Ads by Google