DOCSLIB.ORG

Skosprovider Documentation Release 0.7.0

Total Page：16

File Type：pdf, Size：1020Kb

Download full-text PDF Read full-text
Skosprovider Documentation Release 0.7.0 Skosprovider Documentation Release 0.7.0 Koen Van Daele Feb 19, 2020 Contents 1 Introduction 1 1.1 Other providers..............................................1 1.2 Deviations from SKOS..........................................2 1.3 Support..................................................2 2 Usage 3 3 Development 7 4 API Documentation 9 4.1 Skos module...............................................9 4.2 Providers module............................................. 14 4.3 Registry module............................................. 24 4.4 Uri module................................................ 27 4.5 JsonLd module.............................................. 28 4.6 Exceptions module............................................ 29 4.7 Utils module............................................... 29 5 History 31 5.1 0.7.0 (2020-01-19)............................................ 31 5.2 0.6.1 (2017-07-16)............................................ 31 5.3 0.6.0 (2016-08-09)............................................ 32 5.4 0.5.3 (2015-06-24)............................................ 32 5.5 0.5.2 (2015-03-02)............................................ 32 5.6 0.5.1 (2015-03-02)............................................ 32 5.7 0.5.0 (2014-12-18)............................................ 33 5.8 0.4.2 (2014-10-16)............................................ 33 5.9 0.4.1 (2014-10-15)............................................ 33 5.10 0.4.0 (2014-10-02)............................................ 33 5.11 0.3.0 (2014-05-14)............................................ 34 5.12 0.2.1 (2013-12-06)............................................ 34 5.13 0.2.0 (2013-05-16)............................................ 34 5.14 0.1.3 (2013-03-22)............................................ 34 5.15 0.1.2 (2013-02-07)............................................ 35 5.16 0.1.1 (2012-12-11)............................................ 35 5.17 0.1.0................................................... 35 i 6 Glossary 37 7 Indices and tables 39 Python Module Index 41 Index 43 ii CHAPTER 1 Introduction Skosprovider provides an interface that can be included in an application to allow it to talk to different SKOS vocabu- laries. These vocabularies could be defined locally or accessed remotely through webservices. Adhering to this interface in you application decouples your application and the actual thesaurus. This makes unit testing easy because it allows you to swap a remote and a local implementation. It also makes it easy to switch from a simple, static implementation based on a csv file to a more complete implementation using your relation database of choice. One of the main goals of this project is to be able to build an application that can use thesauri or vocabularies without knowing upfront what these might be or where they might come from. This could be for an application that allows cataloguing things, but where it can be expected that different instances will require different thesauri or would need to be able to talk to existing vocabulary systems. Some sample providers are present in this package. The skosprovider.providers.DictionaryProvider uses a simple python dict as the datastore. It can be considered the reference implementation for the skosprovider.providers.VocabularyProvider interface. Most likely you will want to implement a provider for your own SKOS, vocabulary or thesaurus system. 1.1 Other providers Currently the following other providers exist: • Skosprovider_sqlalchemy: An implementation of the VocabularyProvider interface with a SQLAlchemy backend. This allows using a RDBMS for reading, but also writing, SKOS concepts. • Skosprovider_rdf: An implementation of the VocabularyProvider interface with a RDFLib backend. This allows using a SKOS RDF file as the source for a provider, but also dumping a skosprovider to a SKOS RDF file. • Skosprovider_atramhasis: The AtramhasisProvider lets you interact with an Atramhasis instance. • Skosprovider_getty: An implemenation of the VocabularyProvider against the Linked Open Data vo- cabularies published by the Getty Research Institute at http://vocab.getty.edu such as the Art and Architecture Thesaurus (AAT) and the Thesaurus of Geographic Names (TGN). 1 Skosprovider Documentation, Release 0.7.0 • Skosprovider_heritagedata: An implementation of the VocabularyProvider against the vocabularies pub- lished by EH, RCAHMS and RCAHMW at heritagedata.org. There also exists a library to integrate Skosprovider with Pyramid at pyramid_skosprovider. This allows you to embed a set of REST services in a Pyramid application that expose SKOSproviders as JSON services that can be consumed by eg. Javascript clients or other clients. For those who are looking to build a vocabulary, there’s also Atramhasis, an online SKOS vocabulary editor that builds upon this library and others. Atramhasis can function as the central SKOS registry for an organisation looking to manage its own thesauri and other controlled vocabularies. It provides a public website that allows people to browse you vocabularies and a private interface that allows vocabulary editors to create, edit and delete concepts and collections. By using other Skosproviders Atramhasis can import concepts and collections from other thesauri, saving you the trouble of having to write your own controlled vocabulary from scratch. 1.2 Deviations from SKOS In a few places we’ve deviated a bit from the SKOS standard: • While SKOS technically allows for things like a broader/narrower relation between concepts in different con- ceptschemes, Skosprovider assumes that all hierarchical or associative relations should be between concepts in the same conceptscheme. For relations between concepts in different schemes, the SKOS mapping proper- ties (skos:mappingRelation, skos:closeMatch, skos:exactmatch, . ) should be used. These are supported by Skosprovider since version 0.4.0. • The SKOS standard allows a concept that is marked as a topConcept to have a broader concept. Skosprovider expects that the concepts returned by the skosprovider.providers.VocabularyProvider. get_top_concepts() do not have any broader concepts. • The SKOS ontology ony describes a SKOS:member predicate to indicate that a collection has certain mem- bers. There’s an implicit reverse side to this relation (eg. a concept is a member of a collection). We’ve standardised this on the member_of property that’s available on a skosprovider.skos.Concept and a skosprovider.skos.Collection. • SKOS provides no way for specifying where in a hierarchy a skosprovider.skos.Collection should be placed. Since this is a fairly standard requirement for most thesauri, we have implemented this by looking at the SKOS-THES specification. We have borrowed the skosprovider.skos.Concept. subordinate_arrays and skosprovider.skos.Collection.superordinates properties from this specification. In effect, it turns a SKOS Collection that has one or more superordinates into a The- saurusArray. Since 0.7.0 it’s possible to explicitly state if the member of a collection that has a superordinate concept should be seen as narrower concepts of that superordinate concept with the skosprovider.skos. Collection.infer_concept_relations. By default this is set to True. If you want to model a col- lection that does not contain narrower concepts of it’s superordinate, set it to False. This will mainly stop search expansion using the skosprovider.providers.VocabularyProvider.expand() method. 1.3 Support If you have questions regarding Skosprovider, feel free to contact us. Any bugs you find or feature requests you have, you can add to our issue tracker. If you’re unsure if something is a bug or intentional, or you just want to have a chat about this library or SKOS in general, feel free to join the Atramhasis discussion forum. While these are separate software projects, they are being run by the same people and they integrate rather tightly. 2 Chapter 1. Introduction CHAPTER 2 Usage The basic idea of Skosprovider is very much about the idea of loose coupling, allowing two pieces of software to talk to each other while having as little knowledge of each other as possible. In this case, software A (eg. a webapp) can make use of 1 or more thesauri, controlled vocabularies, authority files and other vocabularies without have to no the details of the vocabularies. This has been achieved by defining an interface of the most common operations needed to integrate an vocabulary in an application. It’s complex and rich enough to allow for most operations that an application might need. And of course, in special cases you might consider expanding the interface. If you do so, please let us know. Your needs might be similar to someone else’s needs and might warrant an extension to the interface. While the interface is very clear on the operations supported and the data it shoudl receive from the provider, it makes not statement whatsoever about the format the data should be in when the provider receives it. So, while a client knows that each provider has a method to find a concept by an id and what this method will return, the client does not need to know where the provider goes to find this concept. One provider might look this up in a CSV file, another one in a database and yet another one through a webservice. In a way, the provider transforms the data from the source format to a common view of the SKOS data model. Because of this, the only part where the different providers are different is when instantiating the provider, since they need to be configured
Load more

Recommended publications
  • ISO/TC46 (Information and Documentation) Liaison to IFLA
    ISO/TC46 (Information and Documentation) liaison to IFLA Annual Report 2015 TC46 on Information and documentation has been leading efforts related to information management since 1947. Standards1 developed under ISO/TC46 facilitate access to knowledge and information and standardize automated tools, computer systems, and services relating to its major stakeholders of: libraries, publishing, documentation and information centres, archives, records management, museums, indexing and abstracting services, and information technology suppliers to these communities. TC46 has a unique role among ISO information-related committees in that it focuses on the whole lifecycle of information from its creation and identification, through delivery, management, measurement, and archiving, to final disposition. *** The following report summarizes activities of TC46, SC4, SC8 SC92 and their resolutions of the annual meetings3, in light of the key-concepts of interest to the IFLA community4. 1. SC4 Technical interoperability 1.1 Activities Standardization of protocols, schemas, etc. and related models and metadata for processes used by information organizations and content providers, including libraries, archives, museums, publishers, and other content producers. 1.2 Active Working Group WG 11 – RFID in libraries WG 12 – WARC WG 13 – Cultural heritage information interchange WG 14 – Interlibrary Loan Transactions 1.3 Joint working groups 1 For the complete list of published standards, cfr. Appendix A. 2 ISO TC46 Subcommittees: TC46/SC4 Technical interoperability; TC46/SC8 Quality - Statistics and performance evaluation; TC46/SC9 Identification and description; TC46/SC 10 Requirements for document storage and conditions for preservation - Cfr Appendix B. 3 The 42nd ISO TC46 plenary, subcommittee and working groups meetings, Beijing, June 1-5 2015.
    [Show full text]
  • National Standardization Plan 2019-2022
    FINAL APRIL 2020 NATIONAL STANDARDIZATION PLAN 2019-2022 Table of Contents 1 Introduction ............................................................................................................................................................. 2 2 Background ............................................................................................................................................................. 4 3 Methodology ............................................................................................................................................................ 4 3.1 Economic Priorities (Economic Impact Strategy) ................................................................................ 5 3.2 Government Policy Priorities ............................................................................................................ 12 3.3 Non-Economic Priorities (Social Impact Strategy) ............................................................................ 14 3.4 Stakeholders requests (Stakeholder Engagement Strategy) ............................................................. 15 3.5 Selected Sectors of Standardization and Expected Benefits ............................................................. 16 3.5.2 Benefits of Selected Sectors and Sub-Sectors of Standardization ................................................ 17 4 Needed Human and Financial Resources and Work Items Implementation Plan............................................ 19 4.1 Human Resources by Type of Work Item and Category ...................................................................
    [Show full text]
  • On the Composition of ISO 25964 Hierarchical Relations (BTG, BTP, BTI)
    View metadata, citation and similar papers at core.ac.uk brought to you by CORE provided by Springer - Publisher Connector Int J Digit Libr (2016) 17:39–48 DOI 10.1007/s00799-015-0162-2 On the composition of ISO 25964 hierarchical relations (BTG, BTP, BTI) Vladimir Alexiev1 · Antoine Isaac2 · Jutta Lindenthal3 Received: 12 January 2015 / Revised: 29 July 2015 / Accepted: 4 August 2015 / Published online: 20 August 2015 © The Author(s) 2015. This article is published with open access at Springerlink.com Abstract Knowledge organization systems (KOS) can use In addition, we relax some of the constraints assigned to the different types of hierarchical relations: broader generic ISO properties, namely the fact that hierarchical relationships (BTG), broader partitive (BTP), and broader instantial apply to SKOS concepts only. This allows us to apply them (BTI). The latest ISO standard on thesauri (ISO 25964) to the Getty Art and Architecture Thesaurus (AAT), where has formalized these relations in a corresponding OWL they are also used for non-concepts (facets, hierarchy names, ontology (De Smedt et al., ISO 25964 part 1: thesauri for guide terms). In this paper, we present extensive examples information retrieval: RDF/OWL vocabulary, extension of derived from the recent publication of AAT as linked open SKOS and SKOS-XL. http://purl.org/iso25964/skos-thes, data. 2013) and expressed them as properties: broaderGeneric, broaderPartitive, and broaderInstantial, respectively. These Keywords Thesauri · ISO 25964 · BTG · BTP · BTI · relations are used in actual thesaurus data. The composition- Broader generic · Broader partitive · Broader instantial · ality of these types of hierarchical relations has not been AAT investigated systematically yet.
    [Show full text]
  • Do Tratamento À Organização Da Informação Reflexões Sobre Concepções, Perspectivas E Tendências
    Do tratamento à Organização da Informação Reflexões sobre concepções, perspectivas e tendências Maria Graça Simões Gercina Ângela de Lima COORDENAÇÃO IMPRENSA DA UNIVERSIDADE DE COIMBRA COIMBRA UNIVERSITY PRESS Esta obra apresenta uma reflexão teórica e histórica sobre as noções clássicas de tratamento da informação e de organização da informação, com base na esfera epistemológica da organização do conhecimento. É Composta de oito capítulos que discorrem sobre (1) as variações terminológicas produzidas na Ciência e no Ensino Brasileiro e Português, (2) a discussão de aspectos teórico-conceituais da organização e representação da informação e a sua correlação com os aspectos práticos que envolvem os ambientes informacionais digitais; (3) o delineamento conceitual inerente à representação da informação feito a partir da discussão da catalogação como confluência de aspectos descritivos, temáticos, contextuais e de acesso à informação de modo que a interconexão entre eles esteja assegurada; (4) as diferentes perspectivas teóricas e metodológicas sobre a modelagem de domínios aplicados à elaboração de ferramentas de representação e recuperação de informação, no contexto das redes eletrônicas de informação e comunicação; (5) a identificação e exploração dos aspectos da variação terminológica na produção científica sobre Organização da Informação relativos aos termos Análise Documentária e Análise de Assunto; (6) as aplicações de representação de recurso informacional, os contextos e processos onde as inovações derivadas da ciência da computação, da inteligência artificial, da área de processamento de linguagem natural e de novas plataformas de bancos de dados têm transformado o contexto de produção de documentos, de sistemas de organização do conhecimento, de métodos de exploração semântica e de visualização.
    [Show full text]
  • Conception of a Workflow for the Semi-Automatic Construction of a
    Conception of a Workflow for the Semi-automatic Construction of a ... 217 Conception of a Workflow for the Semi-automatic Construction of a Thesaurus for the German Printing Industry Anette Siebenkäs, Bernd Markscheffel Technische Universität Ilmenau Fachgebiet Informations- und Wissensmanagement Helmholtzplatz 3 (Oeconomicum), 98693 Ilmenau, Germany {anette.siebenkaes, bernd.markscheffel}@tu-ilmenau.de Abstract During the BMWI granted project “Print-IT”, the need of a thesaurus based uniform and consistent language for the German printing industry became evident. In this paper we introduce a semi-automatic construction approach for such a thesaurus and present a workflow which supports users to generate thesaurus typical information structures from relevant digitalized resources with the help of common IT-tools. Keywords: Information organization, Information retrieval, Thesauri 1 Introduction In Germany, the printing industry is largely based on small and medium- sized enterprises (SME) (bvdm 2012) which can benefit from networks to use synergy effects including their target groups. Therefore, a research pro- ject named “Print-IT” granted by BMWI was established. The project part- ners are TU Ilmenau, HTWK Leipzig, SID Leipzig and several SME’s of the printing industry. Main aim of this project was to build an integration plat- In: F. Pehar/C. Schlögl/C. Wolff (Eds.). Re:inventing Information Science in the Networked Society. Proceedings of the 14 th International Symposium on Information Science (ISI 2015), Zadar, Croatia, 19 th —21 st May 2015. Glückstadt: Verlag Werner Hülsbusch, pp. 217—229. 218 Session 3: Information/Data Retrieval, Visualization and Mapping form where SME’s can provide order- or product-specific goods and services (Eine, Stelzer 2014).
    [Show full text]
  • The ISO 25964 Data Model for the Structure of an Information Retrieval Thesaurus
    Leonard Will - Willpower Information, Enfield, UK The ISO 25964 Data Model for the Structure of an Information Retrieval Thesaurus Abstract International standard ISO 25964-1:2011 – Thesauri for information retrieval, includes a detailed data model for thesaurus structure. It is intended to provide a rigorous presentation of the elements and relationships which will not only clarify and standardise the varying and conflicting interpretations which exist but which can also be implemented consistently in automated systems. It makes a clear distinction between concepts and the terms which are used to label them, and includes other features that may be present in a thesaurus, such as compound equivalence, arrays and node labels, concept groups, notes and version history. Introduction The recently-published international standard, ISO 25964-1:2011 – Thesauri for informa- tion retrieval, presents a data model for thesaurus structure which is more extensive than any published previously. The model is shown in Figure 1, using UML conventions (Object Management Group, 2007). Previous thesaurus standards are summarised by Dextre Clarke and Zeng (2011), so they will not be discussed here other than to note that they did not provide a model for the structure of thesaurus data. The new model is intended to provide a rigorous presentation of the entities and relationships which will not only clarify and standardise the varying and conflicting interpretations which exist but which can also be implemented consistently in automated systems. The SKOS (Simple Knowledge Organization System) format (W3C, 2009) is designed to present KOS data in a format that is suitable for machine inferencing and particularly for use in the Semantic Web.
    [Show full text]
  • Using the Thesaurus to Develop It Inquiry Systems
    Journal of Theoretical and Applied Information Technology 10 th April 2016. Vol.86. No.1 © 2005 - 2016 JATIT & LLS. All rights reserved . ISSN: 1992-8645 www.jatit.org E-ISSN: 1817-3195 USING THE THESAURUS TO DEVELOP IT INQUIRY SYSTEMS FEDOTOV A.M. 1, TUSUPOV J.A. 2, SAMBETBAYEVA M.A. 2, SAGNAYEVA S.K. 2, BAPANOV A.A. 2, NURGULZHANOVA A.N. 3, YERIMBETOVA A.S. 2 1Institute of Computational Technologies, Siberian Branch of the RAS, Novosibirsk, Russian Federation 2L.N. Gumilyov Eurasian National University, Astana, Kazakhstan 3 M.Tynyshpaev Kazakh Academy of Transport and Communications, Almaty, Kazakhstan E-mail: [email protected], [email protected], [email protected], [email protected], [email protected] ABSTRACT The article describes the standards of thesauruses, as well as their possible usage in scientific and educational information systems. The authors compare the various approaches to the description of the data schema based on the object model. Particular attention is paid to SKOS and Zthes data schemes, and the second one has been selected for implementation. The study also considered the work with dictionaries of key terms used for the organization and classification of information resources. Keywords: Z39.50, data schema, SKOS, Zthes, MARC, VDEX, MODS, information system, electronic library, dictionary, directory, database, information retrieval thesaurus, metadata. 1. INTRODUCTION the necessary documents, the systematization and classification of documents in accordance with the The development of information technology in task. In order to satisfy information needs of general, as well as in the field of communication today's users, support for complex retrieval and information processing, in particular, has led functions and classification of the information are to the emergence of fundamentally new required, as well as viewing of the resources by opportunities for organizing virtually all the phases categories (headings) and by dictionary-classifiers.
    [Show full text]
  • GVP LOD: ONTOLOGIES and SEMANTIC REPRESENTATION Vladimir Alexiev, Data and Ontology Group, Ontotext Corp
    GVP LOD: ONTOLOGIES AND SEMANTIC REPRESENTATION Vladimir Alexiev, Data and Ontology Group, Ontotext Corp CIDOC Congress, Dresden, Germany 2014-09-05: International Terminology Working Group: full version (HTML, PDF, slideshare) 2014-09-09: Getty special session: short version (HTML, PDF, slideshare) Press O for overview, H for help. Proudly made in plain text with reveal.js, org-reveal, org-mode and emacs. TABLE OF CONTENTS Getty Vocabularies LOD GVP Vocabulary Data External Ontologies GVP Semantic Representation TGN Specifics: Concept-Place Duality Inference Documentation GVP LOD Usage GETTY VOCABULARIES LOD http://vocab.getty.edu Art and Architecture Thesaurus (AAT): released Feb 2014 Thesaurus of Geographic Names (TGN): released Aug 2014 Work continues with: Unified List of Artist Names (ULAN) Cultural Object Names Authority (CONA) Getty Museum data AATA bibliography Museum and CONA are more complex, involves LIDO/CDWA-lite XML to CIDOC CRM (RDF) CULTURAL HERITAGE LOD Working at the center. (Shows thesauri only, not yet CONA/Museum data) ONTOTEXT SCOPE OF WORK Semantic/ontology development: http://vocab.getty.edu/ontology Contributed to ISO 25964 ontology (latest standard on thesauri). Provided implementation experience, suggestions and fixes Complete mapping specification Help implement R2RML scripts working off Getty's Oracle database, contribution to Perl implementation (RDB2RDF), R2RML extension (rrx:languageColumn) Work with a wide External Reviewers group (people from OCLC, Europeana, ISO 25964 working group, etc) GraphDB (OWLIM) semantic repository. Enterprise Edition (clustered for high- availability) Semantic application development (customized Forest user interface) and tech consulting SPARQL 1.1 compliant endpoint: http://vocab.getty.edu/sparql Comprehensive documentation (100 pages): http://vocab.getty.edu/doc Lots of sample queries, including charts, geographic queries, etc Per-entity export files, explicit/total data dumps.
    [Show full text]
  • El Lenguaje Del Patrimonio.Indb
    Ministerio de Educación, Cultura El lenguaje y Deporte sobre el patrimonio Estándares documentales para la descripción y gestión de colecciones eLP El lenguaje sobre el patrimonio Estándares documentales para la descripción y gestión de colecciones Catálogo de publicaciones del Ministerio: www.mecd.gob.es Catálogo general de publicaciones oficiales: publicacionesoficiales.boe.es Edición 2016 MINISTERIO DE EDUCACIÓN, CULTURA Y DEPORTE Edita: © SecretarÍA GENERAL TÉCnica Subdirección General de Documentación y Publicaciones © De los textos y las fotografías: sus autores NIPO (electrónico): 030-16-459-0 ÍNDICE Pág. Prólogo .................................................................................................................................................................. 6 Un vocabulario común para un patrimonio diverso: el proyecto de tesauros del patrimonio cultural de España del Ministerio de Educación, Cultura y Deporte ....................... 7 María Carrillo Tundidor Presentation RKD terminologies, RKDartists, Iconclass and (the Dutch) AAT ................................. 15 Reem Weda Normas y estándares para la elaboración de tesauros de patrimonio cultural .................................. 29 Javier García Marco Los tesauros en la web semántica: SKOS y la norma ISO 25964 .......................................................... 47 Juan Antonio Pastor Sánchez El control terminológico en el Museo Arqueológico Nacional: evolución histórica, situación actual y perspectivas de futuro ..................................................................................................
    [Show full text]
  • English and an Associated Supplementary Information Object May Carry the Same Text in German
    S-100 Edition 4.0.0 December 201 S-100 – Part 0 Overview Part 0 - Overview S-100 Edition 4.0.0 December 2018 Page intentionally left blank Part 0 - Overview S-100 Edition 4.0.0 December 2018 Contents Foreword ........................................................................................................................................... i Introduction ...................................................................................................................................... iii 0-1 Scope ........................................................................................................................................ 1 0-2 Abbreviations used in this publication ....................................................................................... 1 0-3 Objectives of S-100 ................................................................................................................... 2 0-4 S-100 Parts ................................................................................................................................ 3 0-4.1 Profiles ............................................................................................................................. 4 0-4.2 Part 1 – Conceptual Schema Language ......................................................................... 4 0-4.3 Part 2 – Management of IHO Geospatial Information Registers ..................................... 4 0-4.4 Part 2a – Feature Concept Dictionary Registers............................................................. 5 0-4.5
    [Show full text]
  • English and an Associated Supplementary Information Object May Carry the Same Text in German
    © Copyright International Hydrographic Organization (2017) Certain parts of the text of this document refer to or are based on the standards of the International Organization for Standardization (ISO). The ISO standards can be obtained from any ISO member and from the Web site of the ISO Central Secretariat at: www.iso.org Certain parts of the text of this document are also based on other material subject to specific copyright notice and licence terms which are inserted in the relevant parts. Permission to copy and distribute this document is hereby granted provided that this notice and any specific notice, when applicable, are retained on all copies, and that the IHO, the ISO and any other copyright holder are credited when the material is used to form other copyright policies. INTERNATIONAL HYDROGRAPHIC ORGANIZATION S-100 – UNIVERSAL HYDROGRAPHIC DATA MODEL Edition 3.0.0, April 2017 Publication S-100 Published by the International Hydrographic Organization 4b, quai Antoine 1er B.P. 445 - MC 98011 MONACO Cedex Principauté de Monaco Telefax: (377) 93.10.81.40 E-mail: [email protected] Web: http://www.iho.int Page intentionally left blank S-100 Edition 3.0.0 April 2017 S-100 – Part 0 Overview Part 0 - Overview S-100 Edition 3.0.0 April 2017 Page intentionally left blank Part 0 - Overview S-100 Edition 3.0.0 April 2017 Contents Foreword i Introduction ....................................................................................................................................... ii 0-1 Scope .......................................................................................................................................
    [Show full text]
  • Towards the Reuse of Standardized Thesauri Into Ontologies
    Towards the reuse of standardized thesauri into ontologies Elena Cardillo1, Antonietta Folino2, Roberto Trunfio2, Roberto Guarasci2 1 Institute for Informatics and Telematics, Italian National Research Council, Pisa, Italy 2 Laboratorio di Documentazione (LabDoc), University of Calabria, Rende, Italy [email protected] {antonietta.folino,roberto.trunfio,roberto.guarasci}@unical.it Abstract. One of the main holdbacks towards a wide use of ontologies is the high building cost. In order to reduce this effort, reuse of existing Knowledge Organization Systems (KOSs), and in particular thesauri, is a valuable and much cheaper alternative to build ontologies from scratch. In the literature tools to support such reuse and conversion of thesauri as well as re-engineering pat- terns already exist. However, few of these tools rely on a sort of semi-automatic reasoning on the structure of the thesaurus being converted. Furthermore, pat- terns proposed in the literature are not updated considering the new ISO 25964 standard on thesauri. This paper introduces a new application framework aimed to convert thesauri into OWL ontologies, differing from the existing approaches for taking into consideration ISO 25964 compliant thesauri and for applying completely automatic conversion rules. Keywords: Thesauri; Ontology; Knowledge Organization System; Conversion Framework; ISO 25964; OWL. 1 Introduction Nowadays, Knowledge Organization Systems (KOSs) (e.g. thesauri, taxonomies, ontologies, classification systems) are assuming a key role in knowledge and infor- mation management. Even though a KOS can be used as a standalone application, to take benefit of its features it is generally integrated in larger information systems (search engines, content management systems, etc.). Thus, in the literature a consoli- dated issue is the interoperability of different KOSs for a cost-effective exchange of structured information.
    [Show full text]