<?xml version="1.0" encoding="UTF-8"?>
<TEI xml:space="preserve" xmlns="http://www.tei-c.org/ns/1.0" 
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" 
xsi:schemaLocation="http://www.tei-c.org/ns/1.0 https://raw.githubusercontent.com/kermitt2/grobid/master/grobid-home/schemas/xsd/Grobid.xsd"
 xmlns:xlink="http://www.w3.org/1999/xlink">
	<teiHeader xml:lang="en">
		<fileDesc>
			<titleStmt>
				<title level="a" type="main">Assessing Candidate Ontologies for Reuse</title>
			</titleStmt>
			<publicationStmt>
				<publisher/>
				<availability status="unknown"><licence/></availability>
			</publicationStmt>
			<sourceDesc>
				<biblStruct>
					<analytic>
						<author role="corresp">
							<persName><forename type="first">Reham</forename><surname>Alharbi</surname></persName>
							<email>r.alharbi@liverpool.ac.uk</email>
							<affiliation key="aff0">
								<orgName type="institution">University of Liverpool</orgName>
								<address>
									<postCode>L69 3BX</postCode>
									<settlement>Liverpool</settlement>
									<country key="GB">UK</country>
								</address>
							</affiliation>
						</author>
						<title level="a" type="main">Assessing Candidate Ontologies for Reuse</title>
					</analytic>
					<monogr>
						<imprint>
							<date/>
						</imprint>
					</monogr>
					<idno type="MD5">42D2DC5262EED0A6510A831A871CCB1B</idno>
				</biblStruct>
			</sourceDesc>
		</fileDesc>
		<encodingDesc>
			<appInfo>
				<application version="0.7.2" ident="GROBID" when="2023-03-24T14:31+0000">
					<desc>GROBID - A machine learning software for extracting information from scholarly documents</desc>
					<ref target="https://github.com/kermitt2/grobid"/>
				</application>
			</appInfo>
		</encodingDesc>
		<profileDesc>
			<abstract>
<div xmlns="http://www.tei-c.org/ns/1.0"><p>Ontology reuse is a complex process that requires the support of methodologies and tools to minimise errors and keep the ontologies consistent. Although many efforts have investigated ontology reuse for different tasks and purposes, this body of work does not seem to translate to practice. The goal of this research is a comprehensive "Ontology Reusability Assessment", that builds on and extends the current state of the art. In this paper, we describe this overall aim and two preliminary results: 1) a community questionnaire to gain an insight on the gap between theory and practice, and 2) a case study to see if it is possible to identify similar functional requirements across different domains.</p></div>
			</abstract>
		</profileDesc>
	</teiHeader>
	<text xml:lang="en">
		<body>
<div xmlns="http://www.tei-c.org/ns/1.0"><head n="1">Introduction</head><p>Ontologies are explicit specifications of conceptualised domains shared by a community of users, and play a significant role in conceptual data modelling and AI <ref type="bibr" target="#b3">[4]</ref>. In the context of ontology engineering, reusing existing knowledge models is largely recognised as a key factor in the development of ontologies that are both cost-effective and of higher quality, by reusing components that have previously and independently been validated <ref type="bibr" target="#b13">[14]</ref>. Despite this, ontology reuse does not seem a consolidated practice <ref type="bibr" target="#b7">[8]</ref>: for instance, an analysis of 377 biomedical ontologies in BioPortal 1 concluded that reuse was very limited (&lt;5%) <ref type="bibr" target="#b8">[9]</ref>.</p><p>From state of the art reviewed, it is clear that some ontologies are reused more than others, possibly because they documented when compared with others <ref type="bibr" target="#b12">[13]</ref>. One of the aspects affecting the reusability of an ontology is the perception of its quality with respect to some evaluation criteria. However, although much work has addressed the evaluation of the quality of ontologies from the perspective of reuse, there are no definitive principles and practices, and especially, there is no practical mechanism for providing developers with a qualitative and quantitative assessment of reusability.</p><p>The PhD research presented in this paper, currently in its second year, aims to develop a comprehensive framework for assessing ontologies for reuse, capturing the requirements for reusing an ontology, identifying the modalities of reuse, the ontology features, and any additional information that ontology engineers need to be aware of when selecting a candidate ontology to reuse.</p><p>To achieve this objective, we analysed state of the art in a top-down and bottom-up manner: we reviewed the current literature on the theory of ontology reuse, whilst we compiled a questionnaire aimed at ontology practitioners to identify mismatches between theory and common practices.</p><p>In parallel with the questionnaire, we also started investigating how ontological requirements can help determine whether an ontology can be reused for a given purpose. Competency questions (CQs), the natural language questions outlining the scope of knowledge represented by an ontology and assisting in its development and maintenance <ref type="bibr" target="#b22">[23]</ref>, are often seen as a way of expressing functional ontological requirements that can be used to promote ontology reuse and that facilitate the identification of patterns that implement such requirements <ref type="bibr" target="#b5">[6]</ref>. Our approach aims to contribute a qualitative estimator of the reusability of a given design pattern. We illustrate this through a case study that developes an ontology for the role game Dungeons and Dragons (DnD) <ref type="foot" target="#foot_1">2</ref> . In the case study we objectively assess the similarity between the DnD ontological requirements and those of candidate ontologies to reuse or of design patterns that could be reused.</p><p>This paper reports our preliminary results on these two directions of research. We start by defining the problem statement Section 2. In Section 3 we discuss state of the art on how ontology engineers/developers make use of known definitions and measures in reuse. We present the methodology Section 4, the questionnaire and its preliminary results in Section 5, and in Section 6 we present the case study assessing the similarity between ontological requirements. Finally, in Section 7 we conclude and discuss future research directions.</p></div>
<div xmlns="http://www.tei-c.org/ns/1.0"><head n="2">Problem statement</head><p>Ontology reuse is one of the fundamental phases in all ontology design methodologies, and it is deemed as crucial because it allows developing ontologies by saving effort and by reusing ontological fragments that have been independently validated <ref type="bibr" target="#b11">[12]</ref>. However, a number of reasons can hamper the effective reuse of existing ontologies:</p><p>(i) possible deficiencies in the ontology's documentation make it difficult to find all the ontologies suitable for reuse <ref type="bibr" target="#b10">[11]</ref>; (ii) the lack of a standard way to verify the accuracy of CQs against an ontology typically results in misconceptions in determining the reusability of a candidate ontology <ref type="bibr" target="#b22">[23]</ref>; (iii) the lack of standardisation in designing an ontology through reuse can introduce future errors, for example, by failing to keep track of changes in the reused ontologies <ref type="bibr" target="#b7">[8]</ref>; (iv) insufficient information about the requirements that ontology engineers aim to satisfy when assessing candidate ontologies for reuse <ref type="bibr" target="#b10">[11,</ref><ref type="bibr" target="#b7">8]</ref> These research questions lead to the definition of the following four objectives that this research aims to address: A 1: Identify the reasons that hamper reuse (RQ 1.1) A 2: Develop methods for reusing an ontology by identifying: the requirements for reusing an ontology (RQ 1.1), and the ontology features and additional information that ontology engineers need to know to make an informed decision (RQ 1.3, RQ 1.4). A 3: Develop mechanisms to assess the reusability of an ontology against the requirements identified and summarise them into an assessment metric (RQ 1.1, RQ 1.2). A 4: Evaluate the proposed methodology and metrics with the community to estimate the prospective level of uptake (RQ 1).</p><p>From reviewing the extensive state of the art on ontology reuse, we have established that reuse is based on the ability to determine the scope and the purpose for which an ontology is built. Therefore, we start our investigation from the analysis of the role that CQs play to express ontology requirements, and we investigate whether the semantic similarity between CQs can be used as an indicator of reusability of a candidate ontology, which could be used to determine an initial set of reusable ontologies to be selected by ontology developers.</p></div>
<div xmlns="http://www.tei-c.org/ns/1.0"><head n="3">Related work</head><p>In selecting the literature to review to investigate our research questions we also included ontology evaluation papers, as the quality of an ontology is an influential factor in determining whether to reuse an ontology. The literature review provides us with a set of widely used metrics and techniques that determine the ontology quality from different perspectives, even though these efforts are not always explicitly tailored to the task of ontology reuse. Furthermore, whilst several metrics have been proposed to support ontology reuse, few efforts have attempted to assess how ontology reuse theories affect development practices <ref type="bibr" target="#b7">[8]</ref>, which is the aim of this research.</p><p>The assessment method we aim to develop as part of this PhD combines these metrics to understand the thinking behind ontology selection and reuse, with a particular interest in the practical way of assessing the reusability of an ontology. Our assessment metric is based on the combination of four main aspects: schema metrics, instance metrics, community and social metrics, and documentation metrics:</p><p>Schema metrics <ref type="bibr" target="#b20">[21,</ref><ref type="bibr" target="#b18">19,</ref><ref type="bibr" target="#b12">13]</ref>: pertain to the quality of the design of the ontology schema.This can be assessed by indicating the richness, width, depth, and inheritance of an ontology schema.</p><p>Instance Metrics <ref type="bibr" target="#b20">[21,</ref><ref type="bibr" target="#b18">19,</ref><ref type="bibr" target="#b12">13]</ref>: evaluate the way an ontology is populated. The placement and distribution of instance data can indicate the effectiveness of the ontology design and the knowledge represented by the ontology. Metrics related to Community and Social aspects <ref type="bibr" target="#b10">[11,</ref><ref type="bibr" target="#b19">20]</ref>: capture the several social and community aspects that can affect the quality of an ontology in the evaluation process. Metrics Related to Documentation <ref type="bibr" target="#b10">[11,</ref><ref type="bibr" target="#b6">7,</ref><ref type="bibr" target="#b19">20]</ref>: determine whether an ontology includes some specification of the requirements, for instance the Ontology Requirement Specification Document or CQs.</p><p>In addition to identifying these metrics, we also used the literature review to guide us in preparing a questionnaire aimed at ontology practitioners that validates the importance of the identified measures in common practices. The literature review also includes studies that investigate functional ontological requirements <ref type="bibr" target="#b1">[2]</ref> and how these are represented by means of CQs, since these fundamental in defining the scope of an ontology. For example, an analytical study presented by <ref type="bibr" target="#b15">[16]</ref> included a list of 30 methodologies to build ontologies that start by defining CQs.</p><p>The purposes of many studies of ontological functional requirements can be categorised into: (i) ontology evaluation, by evaluating CQs over an ontology to check whether knowledge is entailed <ref type="bibr" target="#b0">[1,</ref><ref type="bibr" target="#b1">2]</ref>, or measuring the quality and accuracy of the knowledge encoded in the ontology <ref type="bibr" target="#b14">[15,</ref><ref type="bibr" target="#b2">3]</ref>. (ii) ontology verification, by comparing an ontology against the ontological requirements to ensure that an ontology is built correctly <ref type="bibr" target="#b17">[18]</ref>. (iii) methodology definition, by defining a methodology that could consistently drive the ontology engineers in developing an ontology from scratch. This by using a goal modelling approach (Tropos process) to capture, model and reason CQs <ref type="bibr" target="#b17">[18]</ref>. (iv) analysis of CQs, by analysing the structure of CQs and proposing some popular linguistic patterns that can be reused to specify requirements <ref type="bibr" target="#b9">[10,</ref><ref type="bibr" target="#b22">23,</ref><ref type="bibr" target="#b14">15,</ref><ref type="bibr" target="#b2">3]</ref>. (v) CQs formalisation, by automatically fromulating CQs in a controlled natural language based on CQs patterns <ref type="bibr" target="#b9">[10]</ref>, and producing a glossary of terms for each domain <ref type="bibr" target="#b21">[22]</ref>.</p><p>All these studies can improve the requirement specification activity by identifying possible problems in the definition of requirements <ref type="bibr" target="#b5">[6]</ref>. Our contribution proposes the assessment of the similarity between requirements to decide on the reusability of an ontology.</p></div>
<div xmlns="http://www.tei-c.org/ns/1.0"><head n="4">Methodology</head><p>This section introduces the different methodologies used for investigating the main research question, and its sub-questions. RQ 1.1 3 has been addressed by a systematic review to determine the challenges to ontology reuse. We have then validated the identified challenges with a qualitative study through an online questionnaire aimed at ontology developers (Section 5), that assesses the extent to which these challenges hamper reuse, and therefore addresses both RQ 1.2<ref type="foot" target="#foot_3">4</ref> and RQ 1.3 <ref type="foot" target="#foot_4">5</ref> . Based on the survey's initial analysis, we recognised the importance of ontological requirements, and added two further sub-questions: RQ 1.4<ref type="foot" target="#foot_5">6</ref> and RQ 1.5 <ref type="foot" target="#foot_6">7</ref> , whose aim investigates the feasibility of (semi-) automatic similarity assessment of requirements. We conduct a case study (Section 6) that develops a Dungeons and Dragons (DnD)ontology covering the different characters and the possible relationships between the resources of the game. The ontology development is divided in three phases, and is described in Section 6: 1) analysis of the DnD requirements by identifying concepts and relationships that are relevant in the domain; 2) implementation of the requirements using CLaRO <ref type="bibr" target="#b9">[10]</ref>, a template-based Controlled Natural Language resource to author CQs; and 3) identification of similar requirements in the CORAL curated data set <ref type="bibr" target="#b5">[6]</ref> of ontological requirements. In order to assess the similarity between requirements and CQs we adopted the BERTSimilarity method <ref type="bibr" target="#b4">[5]</ref>, that allows us to compute the similarity between complete requirements, taking into account their grammatical structure. Wordnet was also used to account for entity and propriety synonyms.</p><p>The overall assessment mechanism(RQ 1) is meant as a summary of the measures for reusing an ontology. It is intended to be a visual graphical summary for all reasons that justify why an ontology can be reused, and thus a visual representation of the ontology reusability with respect to the requirements defined by an ontology developer.</p></div>
<div xmlns="http://www.tei-c.org/ns/1.0"><head n="5">The reuse questionnaire</head><p>The review of state of the art has highlighted the existence of a gap between theory and practice. However, it is not clear what are the barriers to a more extensive uptake of the practice: it is essential, therefore, to go back to the community, and elicit the information directly from ontology developers.</p><p>We designed an online questionnaire to understand how ontologists and knowledge engineers in different domains search for, evaluate, and select an ontology for reuse. The questionnaire was disseminated during the period March to November 2020 through personal contacts, and relevant mailing lists and conferences (e.g. the 19th International Semantic Web Conference). In total, 54 eligible respondents participated in this study, but we excluded respondents who classed themselves as having no ontology engineering experience.</p><p>The analysis of the answers to the questionnaire is intended to inform how each metric contributes to the assessment mechanism, based on how much the respondents consider a given metric when deciding whether to reuse an ontology.</p><p>The initial findings can be accessed here <ref type="foot" target="#foot_7">8</ref> . The results are still being analysed; however, it is worth noting that a large proportion of respondents (95%) indicates that they are likely or very likely to consider any ontology documentation, including CQs, when deciding reuse. These results are the basis for the DnD case study, presented in Sectionn 6.</p></div>
<div xmlns="http://www.tei-c.org/ns/1.0"><head n="6">Case Study: Developing Dungeon and Dragons through reuse</head><p>CQs are often used as a starting point in the ontology development process and capture the functional requirements of the ontology. It is, therefore plausible to consider first the reuse of ontologies that have similar functional requirements to the ontology being developed. In order to verify this hypothesis, we devised an experiment where we develop an ontology for the role game Dungeons and Dragons (DnD)<ref type="foot" target="#foot_8">9</ref> using the NeOn methodology <ref type="bibr" target="#b16">[17]</ref> and reusing other ontologies from disparate domains do not bear an immediate similarity with the DnD one. The underlying idea is that there could be ontologies that cover different domains from the one of the ontology being designed, but that could still provide terms or patterns that can be reused because their semantics are similar to those in the domain of interest. For instance, the notion of a boss in an organisation can be considered similar to the one of a dungeon master in the game. Therefore, we aim to assess whether the similarity between requirements can be used as an indicator of the reusability of an ontology. We verify this hypothesis by desining a case study, where we use the Corpus of Ontological Requirements Annotated with Lexico-syntactic patterns, CORAL <ref type="bibr" target="#b5">[6]</ref>, as a repository of requirements to be matched. CORAL is an openly available corpus of 834 ontological requirements extracted from ontologies modelling different domains, including video games, buildings and terrains and business organisation. We chose to model DnD because its rules and roles in the games are potentially similar to the requirements in CORAL.</p><p>We worked with a domain expert and we identified 45 CQs for DnD, which then were analysed through natural language processing to the main terms of interest, using the vocabulary agnostic patterns proposed by <ref type="bibr" target="#b22">[23]</ref>. We then tested those terms against CORAL, and we identified five candidate ontologies to reuse (SAREF4ENV, OneM2M, SAREF, SAREF4BLD and OntoDT) <ref type="bibr" target="#b7">[8]</ref> with 38 requirements matching the DnD CQs. The remaining 7 CQs from DnD remained unmatched. We then applied question relevance methods, investigated by the question answering community, to detect duplicate CQs and measure the similarity between requirements 10 . The underlying hypothesis in this case study is that the similarity scores between requirements can indicate the reusability of the part of the ontology modelling the requirement. For example, in DnD, we ask, "What does a campaign have?". The corresponding requirement in CLARO is "An organisation has users", and we notice that one is a generalised form of the other(that indicate an implicit relationship). We use WordNet (a large lexical database of English) and apply the Wu-Palmer Similarity<ref type="foot" target="#foot_10">11</ref> to asses how similar the word senses of the terms used in the requirements are and the relative position of Synsets in the hypernym tree. This shows that some terms in CLARO are more general than the ones in DnD, and therefore we could reuse the pattern used to define the corresponding CQs in CLARO in DnD.</p><p>The ability to start selecting and identifing the relevant ontologies by analysing requirements has a clear potential and is worht exploring further. Applying this methodology to ontology repositories like BioPortal could enable ontology developers to identify ontologies to reuse or to model some of their requrements.</p></div>
<div xmlns="http://www.tei-c.org/ns/1.0"><head n="7">Conclusion and Future work</head><p>We argued that despite the many community efforts, and reuse being a key step in ontology development, the practice is not yet widespread. Therefore this PhD research aims to identify the barriers to a more extensive uptake of the practice and proposes an "Ontology Reusability Assessment" to provide an objective assessment to guide the reuse of an ontology. As part of this effort we sought feedback from the community through an online questionnaireaimed at understanding how ontologists and knowledge engineers select an ontology to reuse.</p><p>From an initial analysis of the responses we identified that the ability to analyse and match CQs is a potential good indicator of the reusability of an ontology. Choosing the reuse of a candidate ontology by exploring the similarity between a set of given requirements and those documenting existing ontologies could facilitate and support their reuse. As a next step, we aim to identify linguistic features in the requirements that can be an indication of whether an ontology could be reused. The proposed mechanism for reuse will be then presented back to the community for evaluation. An evaluation study including expert ontologist and community members will ensure that the reuse assessment is both practical and relevant.</p></div><figure xmlns="http://www.tei-c.org/ns/1.0" xml:id="fig_0"><head></head><label></label><figDesc>. The current PhD research aims to answer the following main research question: "RQ 1: To what extent and what methods can suppport ontology developers assess qualitatively or quantitatively the reusability of an ontology? " This research question can be further decomposed in the following subsidiary questions: RQ 1.1: Why ontology developers do not reuse existing ontologies? RQ 1.2: When is an ontology good for reuse from the community point of view? RQ 1.3: What methods can be used to assess the reusability of an ontology? RQ 1.4: To what extent identifying similar requirements could indicate the reusability of a target ontology? RQ 1.5: What are the linguistic features in the requirements that can indicate ontology reusability?</figDesc></figure>
			<note xmlns="http://www.tei-c.org/ns/1.0" place="foot" xml:id="foot_0">Proceedings of the Doctoral Consortium at ISWC 2021 -ISWC-DC 2021</note>
			<note xmlns="http://www.tei-c.org/ns/1.0" place="foot" n="2" xml:id="foot_1">A fantasy tabletop role-playing game, https://dnd.wizards.com/ Proceedings of the Doctoral Consortium at ISWC 2021 -ISWC-DC 2021</note>
			<note xmlns="http://www.tei-c.org/ns/1.0" place="foot" n="3" xml:id="foot_2">Why ontology developers do not reuse existing ontologies? Proceedings of the Doctoral Consortium at ISWC 2021 -ISWC-DC 2021</note>
			<note xmlns="http://www.tei-c.org/ns/1.0" place="foot" n="4" xml:id="foot_3">When is an ontology good for reuse from the community point of view?</note>
			<note xmlns="http://www.tei-c.org/ns/1.0" place="foot" n="5" xml:id="foot_4">What methods can be used to assess the reusability of an ontology?</note>
			<note xmlns="http://www.tei-c.org/ns/1.0" place="foot" n="6" xml:id="foot_5">To what extent identifying similar requirements could indicate the reusability of a target ontology?</note>
			<note xmlns="http://www.tei-c.org/ns/1.0" place="foot" n="7" xml:id="foot_6">What are the linguistic features in the requirements that can indicateontology reusability?</note>
			<note xmlns="http://www.tei-c.org/ns/1.0" place="foot" n="8" xml:id="foot_7">https://ralharbi9.wixsite.com/reham-alharbi?uid=b3768c75-e033-45c8-88ae-8b6fb426f701</note>
			<note xmlns="http://www.tei-c.org/ns/1.0" place="foot" n="9" xml:id="foot_8"><ref type="bibr" target="#b8">9</ref> https://dnd.wizards.com/articles/features/basicrules</note>
			<note xmlns="http://www.tei-c.org/ns/1.0" place="foot" n="10" xml:id="foot_9"><ref type="bibr" target="#b9">10</ref> https://medium.com/@drcjudelhi/bert-fine-tuning-on-quora-question-pairs-b48277787285</note>
			<note xmlns="http://www.tei-c.org/ns/1.0" place="foot" n="11" xml:id="foot_10">https://wordnet.princeton.edu/ Proceedings of the Doctoral Consortium at ISWC 2021 -ISWC-DC 2021</note>
		</body>
		<back>
			<div type="references">

				<listBibl>

<biblStruct xml:id="b0">
	<monogr>
		<title level="m" type="main">Verifying description logic ontologies based on competency questions and unit testing</title>
		<author>
			<persName><forename type="first">C</forename><surname>Bezerra</surname></persName>
		</author>
		<author>
			<persName><forename type="first">F</forename><surname>Freitas</surname></persName>
		</author>
		<imprint>
			<date type="published" when="2017">2017</date>
			<biblScope unit="page" from="159" to="164" />
		</imprint>
	</monogr>
</biblStruct>

<biblStruct xml:id="b1">
	<monogr>
		<title level="m" type="main">Evaluating ontologies with competency questions</title>
		<author>
			<persName><forename type="first">C</forename><surname>Bezerra</surname></persName>
		</author>
		<author>
			<persName><forename type="first">F</forename><surname>Freitas</surname></persName>
		</author>
		<author>
			<persName><forename type="first">F</forename><surname>Santana</surname></persName>
		</author>
		<imprint>
			<date type="published" when="2013">2013</date>
			<biblScope unit="volume">3</biblScope>
			<biblScope unit="page" from="284" to="285" />
		</imprint>
	</monogr>
</biblStruct>

<biblStruct xml:id="b2">
	<monogr>
		<title level="m" type="main">Cqchecker: a tool to check ontologies in owl-dl using competency questions written in controlled natural language</title>
		<author>
			<persName><forename type="first">C</forename><surname>Bezerra</surname></persName>
		</author>
		<author>
			<persName><forename type="first">F</forename><surname>Santana</surname></persName>
		</author>
		<author>
			<persName><forename type="first">F</forename><surname>Freitas</surname></persName>
		</author>
		<imprint>
			<date type="published" when="2014">2014</date>
			<biblScope unit="volume">12</biblScope>
			<biblScope unit="page">4</biblScope>
		</imprint>
	</monogr>
</biblStruct>

<biblStruct xml:id="b3">
	<analytic>
		<title level="a" type="main">Modular reuse of ontologies</title>
		<author>
			<persName><forename type="first">Cuenca</forename><surname>Grau</surname></persName>
		</author>
		<author>
			<persName><forename type="first">B</forename><surname>Horrocks</surname></persName>
		</author>
		<author>
			<persName><forename type="first">I</forename><surname>Kazakov</surname></persName>
		</author>
		<author>
			<persName><forename type="first">Y</forename><surname>Sattler</surname></persName>
		</author>
		<author>
			<persName><forename type="first">U</forename></persName>
		</author>
	</analytic>
	<monogr>
		<title level="j">Theory and practice</title>
		<imprint>
			<biblScope unit="volume">31</biblScope>
			<biblScope unit="page" from="273" to="318" />
			<date type="published" when="2008">2008</date>
		</imprint>
	</monogr>
</biblStruct>

<biblStruct xml:id="b4">
	<monogr>
		<title level="m" type="main">Bert: Pre-training of deep bidirectional transformers for language understanding</title>
		<author>
			<persName><forename type="first">J</forename><surname>Devlin</surname></persName>
		</author>
		<author>
			<persName><forename type="first">M</forename><forename type="middle">W</forename><surname>Chang</surname></persName>
		</author>
		<author>
			<persName><forename type="first">K</forename><surname>Lee</surname></persName>
		</author>
		<author>
			<persName><forename type="first">K</forename><surname>Toutanova</surname></persName>
		</author>
		<imprint>
			<date type="published" when="2019">2019</date>
		</imprint>
	</monogr>
</biblStruct>

<biblStruct xml:id="b5">
	<monogr>
		<title level="m" type="main">Coral: a corpus of ontological requirements annotated with lexico-syntactic patterns</title>
		<author>
			<persName><forename type="first">A</forename><surname>Fernández-Izquierdo</surname></persName>
		</author>
		<author>
			<persName><forename type="first">M</forename><surname>Poveda-Villalón</surname></persName>
		</author>
		<author>
			<persName><forename type="first">R</forename><surname>García-Castro</surname></persName>
		</author>
		<imprint>
			<date type="published" when="2019">2019</date>
			<biblScope unit="page" from="443" to="458" />
		</imprint>
	</monogr>
</biblStruct>

<biblStruct xml:id="b6">
	<monogr>
		<title level="m" type="main">Methodological guidelines for reusing general ontologies</title>
		<author>
			<persName><forename type="first">M</forename><surname>Fernández-López</surname></persName>
		</author>
		<author>
			<persName><forename type="first">A</forename><surname>Gómez-Pérez</surname></persName>
		</author>
		<author>
			<persName><forename type="first">M</forename><forename type="middle">C</forename><surname>Suárez-Figueroa</surname></persName>
		</author>
		<imprint>
			<date type="published" when="2013">2013</date>
			<biblScope unit="volume">86</biblScope>
			<biblScope unit="page" from="242" to="275" />
		</imprint>
	</monogr>
</biblStruct>

<biblStruct xml:id="b7">
	<analytic>
		<title level="a" type="main">Why are ontologies not reused across the same domain?</title>
		<author>
			<persName><forename type="first">M</forename><surname>Fernández-López</surname></persName>
		</author>
		<author>
			<persName><forename type="first">M</forename><surname>Poveda-Villalón</surname></persName>
		</author>
		<author>
			<persName><forename type="first">M</forename><forename type="middle">C</forename><surname>Suárez-Figueroa</surname></persName>
		</author>
		<author>
			<persName><forename type="first">A</forename><surname>Gómez-Pérez</surname></persName>
		</author>
	</analytic>
	<monogr>
		<title level="j">Journal of Web Semantics</title>
		<imprint>
			<biblScope unit="volume">57</biblScope>
			<biblScope unit="page">100492</biblScope>
			<date type="published" when="2019">2019</date>
		</imprint>
	</monogr>
</biblStruct>

<biblStruct xml:id="b8">
	<analytic>
		<title level="a" type="main">A systematic analysis of term reuse and term overlap across biomedical ontologies</title>
		<author>
			<persName><forename type="first">M</forename><forename type="middle">R</forename><surname>Kamdar</surname></persName>
		</author>
		<author>
			<persName><forename type="first">T</forename><surname>Tudorache</surname></persName>
		</author>
		<author>
			<persName><forename type="first">M</forename><forename type="middle">A</forename><surname>Musen</surname></persName>
		</author>
	</analytic>
	<monogr>
		<title level="j">Semantic web</title>
		<imprint>
			<biblScope unit="volume">8</biblScope>
			<biblScope unit="issue">6</biblScope>
			<biblScope unit="page" from="853" to="871" />
			<date type="published" when="2017">2017</date>
		</imprint>
	</monogr>
</biblStruct>

<biblStruct xml:id="b9">
	<monogr>
		<title level="m" type="main">Claro: a controlled language for authoring competency questions</title>
		<author>
			<persName><forename type="first">C</forename><forename type="middle">M</forename><surname>Keet</surname></persName>
		</author>
		<author>
			<persName><forename type="first">Z</forename><surname>Mahlaza</surname></persName>
		</author>
		<author>
			<persName><forename type="first">M</forename><forename type="middle">J</forename><surname>Antia</surname></persName>
		</author>
		<imprint>
			<date type="published" when="2019">2019</date>
			<biblScope unit="page" from="3" to="15" />
		</imprint>
	</monogr>
</biblStruct>

<biblStruct xml:id="b10">
	<analytic>
		<title level="a" type="main">Miro: guidelines for minimum information for the reporting of an ontology</title>
		<author>
			<persName><forename type="first">N</forename><surname>Matentzoglu</surname></persName>
		</author>
		<author>
			<persName><forename type="first">J</forename><surname>Malone</surname></persName>
		</author>
		<author>
			<persName><forename type="first">C</forename><surname>Mungall</surname></persName>
		</author>
		<author>
			<persName><forename type="first">R</forename><surname>Stevens</surname></persName>
		</author>
	</analytic>
	<monogr>
		<title level="j">Journal of biomedical semantics</title>
		<imprint>
			<biblScope unit="volume">9</biblScope>
			<biblScope unit="issue">1</biblScope>
			<biblScope unit="page">6</biblScope>
			<date type="published" when="2018">2018</date>
		</imprint>
	</monogr>
</biblStruct>

<biblStruct xml:id="b11">
	<monogr>
		<author>
			<persName><forename type="first">N</forename><forename type="middle">F</forename><surname>Noy</surname></persName>
		</author>
		<author>
			<persName><forename type="first">D</forename><forename type="middle">L</forename><surname>Mcguinness</surname></persName>
		</author>
		<title level="m">Ontology development 101: A guide to creating your first ontology</title>
				<imprint>
			<date type="published" when="2001">2001</date>
		</imprint>
	</monogr>
</biblStruct>

<biblStruct xml:id="b12">
	<monogr>
		<title level="m" type="main">Ontology selection ranking model for knowledge reuse</title>
		<author>
			<persName><forename type="first">J</forename><surname>Park</surname></persName>
		</author>
		<author>
			<persName><forename type="first">S</forename><surname>Oh</surname></persName>
		</author>
		<author>
			<persName><forename type="first">J</forename><surname>Ahn</surname></persName>
		</author>
		<imprint>
			<date type="published" when="2011">2011</date>
			<biblScope unit="volume">38</biblScope>
			<biblScope unit="page" from="5133" to="5144" />
		</imprint>
	</monogr>
</biblStruct>

<biblStruct xml:id="b13">
	<monogr>
		<title level="m" type="main">Reusing ontology design patterns in a context ontology network</title>
		<author>
			<persName><forename type="first">M</forename><surname>Poveda-Villalón</surname></persName>
		</author>
		<author>
			<persName><forename type="first">M</forename><forename type="middle">C</forename><surname>Suárez-Figueroa</surname></persName>
		</author>
		<author>
			<persName><forename type="first">A</forename><surname>Gómez-Pérez</surname></persName>
		</author>
		<imprint>
			<date type="published" when="2010">2010</date>
			<biblScope unit="page" from="35" to="52" />
		</imprint>
	</monogr>
</biblStruct>

<biblStruct xml:id="b14">
	<monogr>
		<title level="m" type="main">Towards competency question-driven ontology authoring</title>
		<author>
			<persName><forename type="first">Y</forename><surname>Ren</surname></persName>
		</author>
		<author>
			<persName><forename type="first">A</forename><surname>Parvizi</surname></persName>
		</author>
		<author>
			<persName><forename type="first">C</forename><surname>Mellish</surname></persName>
		</author>
		<author>
			<persName><forename type="first">J</forename><forename type="middle">Z</forename><surname>Pan</surname></persName>
		</author>
		<author>
			<persName><forename type="first">K</forename><surname>Van Deemter</surname></persName>
		</author>
		<author>
			<persName><forename type="first">R</forename><surname>Stevens</surname></persName>
		</author>
		<imprint>
			<date type="published" when="2014">2014</date>
			<biblScope unit="page" from="752" to="767" />
		</imprint>
	</monogr>
</biblStruct>

<biblStruct xml:id="b15">
	<monogr>
		<author>
			<persName><forename type="first">A</forename><surname>Soares</surname></persName>
		</author>
		<title level="m">Towards ontology-driven information systems: Guidelines to the creation of new methodologies to build ontologies</title>
				<imprint>
			<date type="published" when="2009">2009</date>
		</imprint>
	</monogr>
</biblStruct>

<biblStruct xml:id="b16">
	<monogr>
		<title level="m" type="main">NeOn Methodology for building ontology networks: specification, scheduling and reuse</title>
		<author>
			<persName><forename type="first">M</forename><forename type="middle">C</forename><surname>Suárez-Figueroa</surname></persName>
		</author>
		<imprint>
			<date type="published" when="2010">2010</date>
		</imprint>
	</monogr>
	<note type="report_type">Ph.D. thesis</note>
</biblStruct>

<biblStruct xml:id="b17">
	<monogr>
		<title level="m" type="main">First attempt towards a standard glossary of ontology engineering terminology</title>
		<author>
			<persName><forename type="first">M</forename><forename type="middle">C</forename><surname>Suarez-Figueroa</surname></persName>
		</author>
		<author>
			<persName><forename type="first">A</forename><surname>Gómez-Pérez</surname></persName>
		</author>
		<imprint>
			<date type="published" when="2008">2008</date>
			<biblScope unit="page" from="1" to="16" />
		</imprint>
	</monogr>
</biblStruct>

<biblStruct xml:id="b18">
	<monogr>
		<title level="m" type="main">Characterizing quality of knowledge on semantic web</title>
		<author>
			<persName><forename type="first">K</forename><surname>Supekar</surname></persName>
		</author>
		<author>
			<persName><forename type="first">C</forename><surname>Patel</surname></persName>
		</author>
		<author>
			<persName><forename type="first">Y</forename><surname>Lee</surname></persName>
		</author>
		<imprint>
			<date type="published" when="2004">2004</date>
			<biblScope unit="page" from="472" to="478" />
		</imprint>
	</monogr>
</biblStruct>

<biblStruct xml:id="b19">
	<monogr>
		<title level="m" type="main">The role of community and social metrics in ontology evaluation: An interview study of ontology reuse</title>
		<author>
			<persName><forename type="first">M</forename><surname>Talebpour</surname></persName>
		</author>
		<author>
			<persName><forename type="first">M</forename><forename type="middle">D</forename><surname>Sykora</surname></persName>
		</author>
		<author>
			<persName><forename type="first">T</forename><surname>Jackson</surname></persName>
		</author>
		<imprint>
			<date type="published" when="2017">2017</date>
			<biblScope unit="page" from="119" to="127" />
		</imprint>
	</monogr>
</biblStruct>

<biblStruct xml:id="b20">
	<monogr>
		<author>
			<persName><forename type="first">S</forename><surname>Tartir</surname></persName>
		</author>
		<author>
			<persName><forename type="first">I</forename><forename type="middle">B</forename><surname>Arpinar</surname></persName>
		</author>
		<author>
			<persName><forename type="first">M</forename><surname>Moore</surname></persName>
		</author>
		<author>
			<persName><forename type="first">A</forename><forename type="middle">P</forename><surname>Sheth</surname></persName>
		</author>
		<author>
			<persName><forename type="first">B</forename><surname>Aleman-Meza</surname></persName>
		</author>
		<title level="m">Ontoqa: Metric-based ontology quality analysis</title>
				<imprint>
			<date type="published" when="2005">2005</date>
		</imprint>
	</monogr>
</biblStruct>

<biblStruct xml:id="b21">
	<monogr>
		<title level="m" type="main">A tagger for glossary of terms extraction from ontology competency questions</title>
		<author>
			<persName><forename type="first">D</forename><surname>Wisniewski</surname></persName>
		</author>
		<author>
			<persName><forename type="first">A</forename><surname>Lawrynowicz</surname></persName>
		</author>
		<imprint>
			<date type="published" when="2019">2019</date>
			<biblScope unit="page" from="181" to="185" />
		</imprint>
	</monogr>
</biblStruct>

<biblStruct xml:id="b22">
	<analytic>
		<title level="a" type="main">Analysis of ontology competency questions and their formalizations in sparql-owl</title>
		<author>
			<persName><forename type="first">D</forename><surname>Wiśniewski</surname></persName>
		</author>
		<author>
			<persName><forename type="first">J</forename><surname>Potoniec</surname></persName>
		</author>
		<author>
			<persName><forename type="first">A</forename><surname>Lawrynowicz</surname></persName>
		</author>
		<author>
			<persName><forename type="first">C</forename><forename type="middle">M</forename><surname>Keet</surname></persName>
		</author>
	</analytic>
	<monogr>
		<title level="m">Proceedings of the Doctoral Consortium at ISWC 2021 -ISWC-DC 2021</title>
				<meeting>the Doctoral Consortium at ISWC 2021 -ISWC-DC 2021</meeting>
		<imprint>
			<date type="published" when="2019">2019</date>
			<biblScope unit="volume">59</biblScope>
			<biblScope unit="page">100534</biblScope>
		</imprint>
	</monogr>
</biblStruct>

				</listBibl>
			</div>
		</back>
	</text>
</TEI>
