A Method to Convert Thesauri to SKOS
This page supplements a paper that describes a method to convert thesauri to SKOS
The results of the case studies presented in that paper are published here. The cases concern conversions of three thesauri: IPSV, GTAA and MeSH.
Case Study 1: IPSVThis case study concerns the UK Integrated Public Service Vocabulary.
Integrated Public Service Vocabulary (IPSV) © Crown copyright. We wish to encourage the re-use of the IPSV. It may be downloaded by individuals and organisations for incorporation in products and services that are made available to others without requiring a licence or payment of fees. Anyone who includes the IPSV in a product or service should ensure that they do not alter the data or its presentation in any way that damages the integrity of the IPSV. We shall not be liable for any losses due to errors or omissions in the IPSV. In addition esd-toolkit requires that the data is not used in a derogatory manner or in a misleading context. The source of the material must be acknowledged as esd-toolkit and the title referring to Integrated Public Sector Vocabulary should appear on all documents and must be included when being reproduced as part of other publications or services.
The last three files together form the complete conversion of IPSV-XML to SKOS. They should be loaded together into RDFS software.
Conversion program seems to work on the draft IPSV-XML V2.00, but not tested extensively.
Case 2: GTAACopyright notice: GTAA is copyright of the Netherlands Institue for Sound and Vision. We only present a sample of the actual instances because of copyright restrictions.
This conversion program is written in Perl, not in Prolog.
The last three files together form the complete conversion of GTAA to SKOS. They should be loaded together into RDFS software.
Case 3: MeSH
Updated files, 9 feb 2007
An error was discovered in the Prolog program, causing omission of statments (URI, rdf:type, skos:Concept) for some descriptors. The following files are updated:
The last five files together form the complete conversion of GTAA to SKOS. They should be loaded together into RDFS software. One can choose not to load meshdata.rdf if one is only interested in the descriptor hierarchy.