Introduction

The Semantic Web produces many vocabularies and ontologies to represent and annotate any kind of data. However, those ontologies are spread out, in different formats, of different size, with different structures and from overlapping domains. The scientific community has always been interested in designing common platforms to list and sometime host and serve ontologies, align them, and enable their (re)use (Ding and Fensel, 2001;Hartmann et al., 2009;D'Aquin and Noy, 2012;, 1995). These platforms range from simple ontology listings or libraries with structured metadata, to advanced repositories (or portals) which feature a variety of services for multiple types of semantic resources (ontologies, vocabularies, terminologies, taxonomies, thesaurus) such as browse/search, visualization, metrics, recommendation, or annotation. In this paper, we will focus on ontology repositories, they allow to address important questions:

If you have built an ontology, how do you let the world know and share it? How do you connect your ontology to the rest of the semantic world? If you need an ontology, where do you go to get it? How do you know whether an ontology is any good? If you have data to index, how do you find the most appropriate ontology for your data? If you look for data, how may the semantics of ontologies help you locate them? More generally, ontology repositories help "ontology users" to deal with ontologies without managing them or engaging in the complex and long process of developing them.

However, with big number of ontologies new problems have raised such as describing, selecting, evaluating, trusting, and interconnecting them. From our experience working first on the US National Center for Biomedical Ontologies (NBCO) BioPortal, the most widely adopted biomedical ontology repository and later on the SIFR BioPortal, a specific sub-portal to address the French biomedical community and AgroPortal, an ontology repository for agronomy, we review and discuss six challenges in designing such platforms: 1. Metadata & selection. Ultimately, ontology repositories are made to share and reuse ontologies. But which ontology should I reuse? With too many different and overlapping ontologies, properly describing them with metadata and facilitate their identification and selection becomes and important issue.

We believe, as any other data, ontologies must be FAIR. 2. Multilingualism. We live in a multilingual world, so are the concepts and entities from this world. The Semantic Web offers now tools and standards to develop multilingual and lexically rich ontologies. Repositories must be able to deal with multiple languages also. 3. Ontology alignment. No conceptualization is an island. It is now commonly agreed data interoperability cannot be achieved by means of a single common ontology for a domain, and interlinking ontologies is the way forward. But the more ontologies are being produced, the more the need for ontology alignment becomes important. 4. Ontology-based services. On reason to adopt Semantic Web standards and use ontology repositories is to benefit from multiple services for -and based on-ontologies. No one likes to reimplement something already existing and that can be generalized to another ontology just by dropping it in a repository. The portfolio of services for ontologies available in repositories should then grows. 5. Annotations and linked data. Ontologies and vocabularies are the backbone of semantically rich data (Linked Open Data, knowledge bases, etc.) as they are used to semantically annotate and interlink datasets.

It is also important to facilitate semantic indexing, search and data access directly from the repositories.

Scalability & interoperability.

The community of ontology developers and users is growing both horizontally (i.e., new domains) and vertically (i.e., new adopters inside a domain). Ontology repositories shall therefore scale to high number of ontologies, while facilitating their alignments, and when multiple repositories are created, they must be interoperable. In the following, we will detail these challenges and briefly describe/point to results obtained in the context of our multiple ontology repository projects. In some sense, this article is an index of 10-years of published research in the domain of ontology repositories. We do not report hereafter all related work for each challenge neither we claim to have addressed them all. However, we believe our results illustrate potential solutions to move forward in that domain of research.

Background

Ontology libraries & repositories

With the growing number of ontologies developed, ontology libraries and repositories have always been of interest in the Semantic Web community. Ding and Fensel (2001) introduced the notion of ontology library and presented a review of libraries at that time: "A library system that offers various functions for managing, adapting and standardizing groups of ontologies. It should fulfill the needs for re-use of ontologies. In this sense, an ontology library system should be easily accessible and offer efficient support for reusing existing relevant ontologies and standardizing them based on upper-level ontologies and ontology representation languages." The terms "collection", "listing" or "registries" are also used to describe ontology libraries. All correspond to systems that help reuse or find ontologies by simply listing them (e.g., DAML or DERI listings) or by offering structured metadata to describe them (e.g., FAIRSharing, BARTOC). But those systems do not support any services beyond description, especially based on the content of the ontologies. Hartmann et al., (2009) introduced the concept of ontology repository, with advanced features such as search, browsing, metadata management, visualization, personalization, and mappings and an application programming interface to query their content/services: "A structured collection of ontologies (…) by using an Ontology Metadata Vocabulary. References and relations between ontologies and their modules build the semantic model of an ontology repository. Access to resources is realized through semantically-enabled interfaces applicable for humans and machines. Therefore, a repository provides a formal query language." By the end of the 2000's, the topic was of high interest as illustrated by the 2010ORES workshop (d'Aquin et al., 2010) or the 2008 On-tologySummit. 1 The Open Ontology Repository Initiative (Baclawski and Schneider, 2009) was a collaborative effort to develop a federated infrastructure of ontology repositories. At that time, the effort already reused the NCBO technology (Whetzel and Team, 2013) that was the most advanced open source technology for managing ontologies but not yet packaged in an "virtual appliance" as it is today. More recently the effort also studied OntoHub (Till et al., 2014) technology for generalization but the OOR initiative is now discontinued.

In parallel, there have been effort do index any Semantic Web data online (including ontologies) and offer search engines such as Swoogle and Watson (Ding et al., 2004;D'Aquin et al., 2007). We cannot talk about ontology library or repositories for those "Semantic Web indexes", even if they support some features of ontology libraries or repositories (e.g., search).

In the biomedical or agronomic domains there are several standards and/or ontology libraries such as FAIRSharing (fairsharing.org) (McQuilton et al., 2016), the FAO's VEST Registry (aims.fao.org/vest-registry), and the agINFRA linked data vocabularies (vocabularies.aginfra.eu). They usually register ontologies and provide a few metadata attributes about them. However, because they are registries not especially focused on vocabularies and ontologies, they do not support the level of features that an ontology repository offers. In the biomedical domain, the OBO Foundry (Smith et al., 2007) is a reference community effort to help the biomedical and biological communities build their ontologies with an enforcement of design and reuse principles that have made the effort very successful. The OBO Foundry Web application (http://obofoundry.org) is not an ontology repository per se, but relies on other 1 http://ontolog.cim3.net/wiki/OntologySummit2008.html applications that pull their data from the foundry, such as the NCBO BioPortal (Noy et al., 2009), OntoBee (Ong et al., 2016), the EBI Ontology Lookup Service (Côté et al., 2006) and more recently AberOWL (Hoehndorf et al., 2015). In addition, there exist other ontology libraries and repository efforts unrelated to biomedicine, such as the Linked Open Vocabularies (Vandenbussche et al., 2014), OntoHub (Till et al., 2014), and the Marine Metadata Initiative's Ontology Registry and Repository (Rueda et al., 2009). More recently, the SIFR BioPortal (Jonquet et al., 2016a) prototype was created at University of Montpellier to build a French Annotator and experiment multilingual issues in BioPortal (Jonquet et al., 2015). The same university is also developing AgroPortal, an ontology repository for agronomy and neighboring domains such as food, plant sciences and biodiversity (Jonquet et al., 2017a).

D'Aquin and Noy, ( 2012) and Naskar and Dutta, (2016) provided the latest reviews of ontology repositories. In Table 1, we provide a nonexhaustive -but quite rich-list of ontology libraries, repositories and Web indexes available today. 1. Non-exhaustive list of ontology libraries, repositories and Web indexes available today. We also included some known "technology" that can be reused to setup an ontology library. Blue cells are projects in biomedicine and health sciences. A * identifies ontology repositories which reuse(d) NCBO technology.

Ontology libraries

Focus on the NCBO BioPortal: a "one stop shop" for biomedical ontologies

In the biomedical domain, BioPortal (http://bioportal.bioontology.org) (Noy et al., 2009), developed by the National Center for Biomedical Ontologies (NBCO) at Stanford is a wellknown open repository for biomedical ontologies originally spread out over the Web and in different formats. There are +650 public ontologies in this collection as of end 2017. By using the portal's features, users can browse, search, visualize and comment on ontologies both interactively through a Web interface, and programmatically via Web services. Within BioPortal, ontologies are used to develop an annotation workflow (Jonquet et al., 2009) that indexes several biomedical text and data resources using the knowledge formalized in ontologies to provide semantic search features that enhance information retrieval experience (Jonquet et al., 2011). The NCBO BioPortal functionalities have been progressively extended in the last 12 years, and the platform has adopted Semantic Web technologies (e.g., ontologies, mappings, metada-ta, notes, and projects are stored in an RDF2 triple store) (Salvadores et al., 2013).

An important aspect is that NCBO technology (Whetzel and Team, 2013) is domainindependent and open source. A BioPortal virtual appliance3 is available as a server machine embedding the complete code and deployment environment, allowing anyone to set up a local ontology repository and customize it. The NCBO virtual appliance is quite regularly reused by organizations which need to use services like the NCBO Annotator but have to process sensitive data in house e.g., hospitals. Via the virtual appliance, NCBO technology has already been adopted for different ontology repositories in related domains and was also originally chosen as foundational software of the OOR Initiative (Baclawski and Schneider, 2009). The MMI Ontology Registry and Repository (Rueda et al., 2009) used it as its backend storage system for over 10 years, and the Earth Sciences Information Partnership earth and environmental semantic portal (Pouchard L. Huhns M., 2012) was deployed several years ago. We are also currently working on the SIFR Bi-oPortal (Jonquet et al., 2016a) and AgroPortal (Jonquet et al., 2017a) projects described hereafter.

Two collaborative ontology repository projects

In the context of our projects, to avoid building new ontology repositories from scratch, we have considered which of the previous technologies are reusable. While most of them are "open source," only the NCBO BioPortal 4 and OLS 5 are really meant for reuse, both in their construction, and with their documentation provided. Although we cannot know all the applications of other technologies, the visibly frequent reuse of the NCBO technology definitively confirmed it is a good candidate for reuse when building a new ontology repository. Also, of the two candidate technologies, we believe NCBO technology implements the highest number of required features in our projects (Jonquet et al., 2017a).

SIFR BioPortal

In the context of the Semantic Indexing of French Biomedical Data Resources (SIFR) project, we have developed the SIFR BioPortal (http://bioportal.lirmm.fr) (Jonquet et al., 2016a), an open platform to host French biomedical ontologies and terminologies based on the technology developed by the NCBO. The portal facilitates use and fostering of terminologies and ontologies which were only developed in French or translated from English resources and are not well served in the English-focused NCBO BioPortal. As of today, the portal contains 25 public ontologies and terminologies (+ 6 private ones) that cover multiple areas of biomedicine, such as the French versions of standards terminologies (e.g., MeSH, MedDRA, ATC, ICD-10) but also multilingual ontologies. In this later cases, we use the NCBO BioPortal as a source repository -so users do not have to upload their multilingual ontologies twice-and only parse and index the French content on the SIFR BioPortal.

The original motivation in building the SIFR BioPortal was to develop the SIFR Annotator (http://bioportal.lirmm.fr/annotator) to address the lack of out-of-the-shelve openly and easily accessible semantic annotation system for French (Jonquet et al., 2016a;Tchechmedjiev et al., 2017a). The service is originally based on the NCBO Annotator [8], a Web service allowing scientists to utilize available biomedical ontologies for annotating their datasets automatically, but was significantly enhanced and customized for French. The annotator service processes raw textual descriptions, tags them with relevant biomedical ontology concepts and returns the annotations to the users in several formats such as JSON-LD, RDF or BRAT.

AgroPortal: a vocabulary and ontology repository for agronomy

We have been reusing the NCBO BioPortal technology to design AgroPortal, an ontology reposi-tory for agronomy, food, plant sciences, and biodiversity (http://agroportal.lirmm.fr) (Jonquet et al., 2016c;Jonquet et al., 2017a). AgroPortal, is an advanced prototype featuring all BioPortal services and new ones implemented to address the requirements of the agronomy community. The platform currently hosts 77 ontologies among which 50 are not present in any comparable repository. We have identified 93 other candidate ontologies that will be loaded in the future to complement this valuable resource.

Challenges, propositions and results

In the following sections, we describe some challenges we identified by working on ontology repository and exchanging with our user communities. In each case, we describe a few results obtained on the relevant topic.

Metadata & selection

The first questions we ask ourselves when entering a bookstore are often: "Where is the book I am looking for?" or "Which book will I discover and pick up today?" The same questions are true for ontology libraries. To address them, we need better description of the ontologies, with precise and harmonized metadata and we need also means to facilitate the identification and selection of the ontologies of interest. Ontologies serve to make data FAIR (Wilkinson et al., 2016), ontology repositories shall serve to make ontologies FAIR.

As any resources, ontologies, vocabularies and terminologies need to be described with relevant metadata to facilitate their identification and selection. However, none of the existing metadata vocabularies can completely meet this need if taken independently. Indeed, some metadata properties are intrinsic to the ontology (name, license, description); others, such as community feedbacks, or relations to other ontologies are typically information that an ontology library shall capture, populate and consolidate to facilitate the ontology landscape comprehension (e.g., selection of an ontology).

In Jonquet et al., (2017b), we have reviewed the most standard and relevant vocabularies (23 totals) currently available to describe metadata for ontologies (such as Dublin Core, Ontology Metadata Vocabulary, VoID, etc.) as well as the different metadata implementation in multiple ontology libraries or repositories. We have then built a new metadata model for AgroPortal. The repository now parses 346 standard properties that could be used to describe different aspects of ontologies: intrinsic descriptions, people, date, relations, content, metrics, community, administration, and access. We use them to populate a model of 127 properties implemented in the portal and harmonized for all the ontologies. We have spent a significant amount of time to edit the metadata of the ontologies with the goal to facilitate the comprehension of the agronomical ontology landscape by displaying diagrams and charts about all the ontologies on the portal. We have now a specific page (http://agroportal.lirmm.fr/landscape) dedicated to visualizing the ontology landscape in Ag-roPortal that facilitates analysis of the repository content. The landscape page helps to figure out what are some of the main domain of interests as well as common development practices when creating an ontology in agronomy.

In Dutta et al., (2017), we have generalized our work done within AgroPortal to propose a new Metadata vocabulary for Ontology Description and publication, called MOD (https://github.com/sifrproject/MOD-Ontology). MOD 1.2 is defined in OWL and consists of 19 classes and 88 properties most of them to describe the mod:Ontology object. MOD 1.2 may serve as (i) a vocabulary to be used by ontology developers to annotate and describe their ontologies, or (ii) an explicit OWL ontology to be used by ontology libraries to offer semantic descriptions of ontologies as linked data. MOD 1.2 is an initiative which attempts to overcome some of the limitations of the Ontology Metadata Vocabulary (Suarez-Figueroa et al., 2005) but is still a temporary proposition that will be discussed in the next months within the Research Data Alliance recently re-configured Vocabulary & Semantic Services Interest Group. 6Automatic ontology selection or recommendation has been a subject of interest to facilitate ontology reuse (Sabou et al., 2006)(Butt et al., 2016). The number and variety of ontologies in certain domains is now so large that choosing one for an annotation task or for designing a specific application is quite cumbersome.

In Martinez-Romero et al., (2017), we developed the NCBO Ontology Recommender. This service suggests relevant ontologies from the repository for annotating text data. The new rec-ommendation approach evaluates the relevance of an ontology to biomedical text data according to four different criteria: (1) the extent to which the ontology covers the input data; (2) the acceptance of the ontology in the community; (3) the level of detail of the ontology classes that cover the input data; and (4) the specialization of the ontology to the domain of the input data. This new version of a service originally released in 2010 (Jonquet et al., 2010) combines the strengths of its predecessor with a range of adjustments and new features that improve its reliability and usefulness. Because it is integrated in the NCBO technology, the Recommender is already available within the SIFR BioPortal and AgroPortal. We shall note that these services do not yet rely on the new metadata model previously cited.

Multilingualism

Scientific discoveries that could be made with help of ontologies to annotate, integrate, mine and search data, are often limited by the availability of ontology-based tools and services only for one natural language, usually English, for which there exist the most ontologies. Recently, ontology localization, i.e., "the process of adapting an ontology to a concrete language and culture community" (Cimiano et al., 2010), has become very important in the ontology development lifecycle, but when efforts are made to properly represent lexical (e.g., using Lemon (McCrae et al., 2011)) or multilingual information (e.g., using LexOMV (Montiel-Ponsoda et al., 2007) or Lemon translation module (Gracia et al., 2014)) are made, it is rarely leveraged by ontology libraries and repositories. In the future, we need ontology repositories to entirely support interface and content internationalization (i.e., both displaying user interfaces (e.g., menu names, help, etc.) in different languages and displaying their content (e.g., ontology labels, mappings, etc.) in different languages) and be multilingual by enabling a complete use of their functionalities and services for multilingual ontologies or monolingual ontologies linked one another.

In Jonquet et al., (2015), we presented a roadmap for addressing the issues of dealing with multilingual or monolingual ontologies in the NCBO BioPortal, which takes English as primary language. We proposed a set of representations to support multilingualism in the portal and to enable a complete use of the functionalities and services for any kind of ontologies and data: (i) Representation of natural language property for an ontology; (ii) Representation of translation relations between ontologies; (iii) Representation of the distinction between ontologies with multilingual content i.e., multilingual and mono lingual ontologies; (iv) Representation of multilingual mappings. Those aspects have been addressed now within MOD and/or the new AgroPortal metadata model previously cited. In addition, in Annane et al., (2016b), we reconciled more than 228K mappings between ten English ontologies hosted on NCBO BioPortal and their French translations hosted on the SIFR BioPortal. The next big step is now to internationalize the portal.

Ontology alignment

Ontologies, or other semantic resources, will inevitably overlap in coverage. Therefore, the need for ontology alignment. This need has been explicitly expressed by almost all our partner organizations in biomedicine, agronomy or ecology. Surprisingly, it seems there is a gap between the state-of-theart results obtained at each edition of the Ontology Alignment Evaluation Initiative (OAEIhttp://oaei.ontologymatching.org) and the day-today reality of ontology developers. Tools are often hardly reusable, and results cannot be easily reproduced outside of the benchmarking effort. Another key role of ontology repositories is to store mappings (or alignments) between ontologies. Ontology repositories shall support the extraction, generation, validation, evaluation, storage and retrieval of mappings between the ontologies they host. Automatic mapping generation within ontology repositories shall go beyond simple lexical or ID-based approaches 7 and state-ofthe-art tools shall be incorporated within repositories. An equivalent effort, such as the one made to harvest ontologies, must be made to harvest the mappings between these ontologies and describe them with metadata and provenance information to facilitate trust and reuse. 7 To the best of our knowledge, only the NCBO technology automatically computes ontology alignments when ontologies are hosted within the portal. The portal automatically creates some mappings when two classes share the same identifiers properties, or when they share a common normalized preferred label or synonym. Although basic lexical mapping approaches can be inaccurate and should be used with caution (Faria et al., 2014;Pathak and Chute, 2009), they usually work quite well to interconnect ontologies (Ghazvinian et al., 2009).

In Ghazvinian et al., (2009), we have analyzed the mappings automatically generated within Bi-oPortal and what they tell us about the ontologies themselves, the structure of the ontology repository, and the ways in which the mappings can help in the process of ontology design and evaluation. This study demonstrated the value of having a mapping repository goes beyond ontology-toontology alignment, but concretely helps analyze the structures, dependencies and overlap of ontologies in the same domain. A similar, more recent study about ontology terms reuse have been done by Kamdar et al. (Kamdar et al., 2017). In Annane et al., (2016a), we have also demonstrated that existing mappings between ontologies can also be used to improve ontology alignment methods based on background knowledge; in other words, a centralized mapping repository will also be an excellent resource to curate and generate new mappings.

Generic ontology-based services

Ontology repositories offer a large span of services: file hosting, versioning, search and browse content, visualization, metrics, notes, mapping, etc. These services are 'generic' if they are domain independent i.e., not specific to a domain, group of ontologies, specific format or design principles. It is important that ontology repositories continue to enhance ontology-based services and offer new generic ones to enlarge the spectrum of possible use of ontologies. Using standard formats such as OWL or SKOS has facilitated the development of a wide range of tools and services for semantic resources. The challenge is now to package them inside ontology repositories and keep vertical quality (i.e., one ontology) while enabling quantitative horizontal use.

One important use of ontologies is for annotating and indexing text data (Spasic et al., 2005;Handschuh and Staab, 2003). Therefore, we often see aside of ontology repositories, ontology-based annotation services. For instances, BioPortal has the NCBO Annotator (Jonquet et al., 2009), OLS had Whatizit (Rebholz-Schuhmann et al., 2008) and now moved to ZOOMA, HeTOP had FMTI (Sakji et al., 2010) and UMLS has Met-aMap (Aronson, 2001). Hereafter, we focus on services for text data (annotation & terminology extraction).

In Lossio-Ventura et al., (2014), we presented BioTex, a Web application that implements state-of-the-art measures for automatic extraction of biomedical terms from English and French free text. The application includes a new methodology for automatic term extraction mixing linguistic, statistical, graph and Web-based approaches that have been demonstrated quite efficient (Lossio-Ventura et al., 2015). Among other use of BioTex, we have shown it can be part of an ontology enrichment workflow that could be highly valuable for ontology developers (Lossio-Ventura et al., 2016). However, this work has not yet been incorporated within an ontology repository technology.

In Tchechmedjiev et al.,(2017), we present multiple enhancement to the semantic annotation workflow that we have developed on top of the NCBO Annotator and when building a French version of the service. Some of these new functionalities are particularly relevant to process electronic health records. These new features include: annotation scoring (Melzi and Jonquet, 2014), additional output formats (for evaluation and integration with standard clinical systems), clinical context detection (negation, experiencer and temporality through the integration of the Neg-Ex/ConText algorithm) (Abdaoui et al., 2017), coarse-grained entity type annotations (using UMLS Semantic Groups, e.g., anatomy, disorders, devices).

Annotations and Linked Data

Data integration and semantic interoperability enable new scientific discoveries that could be made by merging different currently available data. These is one major reason for adopting ontologies. They are used to design semantic indexes of data and linked open datasets that could be used for various type of cross datasets studies (Handschuh and Staab, 2003;Bizer et al., 2009). Ontology repositories must facilitate indexing/annotation, search and access to semantically described, interoperable, actionable, open, rich linked data directly from the within the repositories. Working with big data represents a set of challenges for ontology repositories when designing these semantic indexes: scalability, consistency, completeness in a context where both ontologies and data constantly evolve. In addition, cross ontologies semantics and indexed data consistency shall be checked by ontology repositories using OWL reasoning.

In Jonquet et al., (2011), we have built the NCBO Resource Index, an ontology-based index of more than twenty heterogeneous biomedical resources (later extended to 50) included within Bi-oPortal. Directly when browsing the ontologies or using a dedicated search engine, users can discover datasets of interest. The indexing relied on the NCBO Annotator workflow and used the semantics that the ontologies encode, such as synonyms, class hierarchies, and the mappings between ontologies, to improve the search experience. The Resource Index, was a tentative developed before 2010 that did not rely neither on big data technologies and did not followed linked open data principles. Both were in their infancies at that time. More recently, in agronomy, we have followed new efforts such as AgroLD project (Venkatesan et al., 2015) to build a database of resources described in RDF, and annotated with ontologies. We are currently working on the interoperation of AgroLD and AgroPortal.

Scalability & interoperability

In 2007, Swoogle claimed to "Search over 10.000 ontologies". Today, a simple Google Search for "filetype:owl" returns around 34K results. The NCBO BioPortal, which is generally considered has the biggest ontology repository (not library) contains +650 ontologies as of end of 2017. More and more vocabularies are being developed and hosted by the LOV platform. Multiple domain specific ontology repository efforts have started often inspired by results in the biomedical domain and usually by reusing NCBO technology (e.g., MMI OOR, AgroPortal, ESIPPortal). The more ontologies and ontology repositories are being developed, the more scalability and interoperability issues become important. Some ontologies are useful to different communities and shall then be hosted in multiple repositories e.g., domain ontologies such as the Gene Ontology (Ashburner et al., 2000), or the Environment Ontology (Buttigieg et al., 2013). Because no repository will host them all, ontology repositories have to offer a certain level of interoperability to ensure their users that they will not have to work with multiple web applications and programming interfaces if their ontologies of interest are not all hosted by the same repositories. As previously explained standard ontology metadata is a crucial aspect to achieve this.

In Jonquet et al., ;Jonquet et al., (2016b), our projects described Section 2.3, we have been particularly careful in not redeveloping features and functionalities that to our knowledge were already available. We have designed and implemented two advanced prototype ontology repositories for the French biomedical community and for the agronomy domain. Our choice to reuse the NCBO technology was justified by the large spectrum of features and services, but in addition our motivation was: (i) to avoid re-developing tools that have already been designed and extensively used and contribute to long term support of the commonly used technology; and (ii) to offer the same tools, services and formats to different but still interconnected communities, to facilitate the interface and interaction between their domains (agro, bio, health (French)). Relying on the same original technology enhance both technical reuse (for example, enabling queries to either systems with the same code), and semantic reuse. Then, we have developed new functionalities -as previously described-while keeping our systems backward compatible with the original technology to facilitate a convergence of the efforts. We strongly believe that sharing the technology is the best way to guaranty long term support and development by engaging different ontology practitioners and communities all around the world with their respective funding and supporting schemes. Also, sharing the technology is the best way to make ontology repositories interoperable. As explained in Tchechmedjiev et al.,(2017), all of the new features implemented (e.g., NCBO Annotator + or the new Recommender) are available across any other NCBO based platform at minimum cost.

Conclusions

In this paper, we have presented our vision on challenges and issues in building ontology repositories. We have illustrated our thoughts with results obtained over the last 10 years within our projects in biomedicine and agronomy. By adopting NCBO technology, we inherit some advantages and inconvenients but we can now contribute to this field of research with concrete use cases, communities and outcomes. NCBO-based ontology repositories adopted a vision where multiple semantic resources are made available in a common place (though not combined and consistency checked), and cast to a common model. While doing so, the repositories arguably limits the full power of ontologies -which has been a recurrent criticism-constraining their use to fea-tures supported by the common model. We see two general scenarios of use for these repositories:

The repositories provide basic ontology library services for users with a "vertical need" -those who want to do very precise things (e.g., reasoning, using specific relations) using only suitable ontologies (developed by the same communities and in the same format). Such users may just use the repositories as libraries to find and download ontologies, and work in their own environment.

The repositories provide many ontologybased services to users with "horizontal needs" -those who wants to work with a wide range of ontologies and vocabularies useful in their domain but developed by different communities, overlapping and in different formats. Such users greatly appreciate the unique endpoints (Web application and programmatic for REST and SPARQL queries) offered by the repositories under a simplified common model. In this position paper, we have unfortunately not covered all related work on the cited challenges and we have certainly skipped other important challenges: semantic consistency, ontology evaluation, visualization, community feedback. But we offered a short summary of multiple various contributions on ontology repository and ontologybased service research. In the future, we will continue our efforts to address the identified challenges (and others), while continue to offer to various scientific communities the means to share and leverage their ontologies or semantic resources and enable new science in their fields.