Loterre (acronym for Linked open terminology resources) is a platform for exposing and sharing multidisciplinary and multilingual scientific terminology. Based on a triplestore, it complies with open and linked data (LOD) web standards and FAIR principles, which aim to make data Easy to find, Accessible, Interoperable and Reusable. →

The terminology available in Loterre can meet the needs of text-mining, semantic annotation, information retrieval or translation. Access to the resources sotred in Loterre is open to all, with the subsequent use of each one being linked to the license that governs it. →

Loterre gives access to scientific terminology resources and allows: to browse them to search them via a search engine, a SPARQL endpoint and an API to download them in several formats Loterre also offers online services, the content of which is detailed in the “Loterre services” paragraph of this page. →

Loterre is not restricted to Inist terminological resources. It offers its services to other producers of terminological data, provided they have requested the service using the proposition form. Interested producers are invited to read the Loterre Charter. →

The FAIR principles (Findability, Accessibility, Interoperability, Reusability) applicable to the scientific data were developed by Force11 and published by Wilkinson et al. in 2016 (The FAIR Guiding Principles for scientific data management and stewardship). The steps involved in FAIRification have been explained by GO FAIR. These principles form a guide to good practice for the management and reuse of data and metadata by both machines and humans. However, they do… →

Loterre aims to comply with the principles of LOD (Linked Open Data) as presented in 2006 by W3C (Tim Berners-Lee): terminology resources are considered here as organized sets of terms (designating concepts) that are freely accessible via semantic web technologies. Linked Data or “web of linked data” is based on 4 basic rules: Identify each resource (or concept) by a URI (Uniform Resource Identifier) Use HTTP URIs (dereferenceable) to access… →