Abstract
The reuse of ontologies is critical to their value as a means of knowledge representation. Unfortunately, reuse also still poses a considerable challenge for the ontological community. One reason for this is the lack of a formal definition of reuse. How can we attempt to perform or even assist this sort of ontology design, if we have no clear understanding of what constitutes reuse, and what does not? In this work we aim to remedy this situation by providing a formal definition of the concepts of reuse and reusability: a metatheory of ontology reuse. Beyond providing a clear understanding of these concepts, part of the resulting definition is a characterization of the operations of reuse that can be leveraged to determine how a given ontology(s) may be reused to satisfy some specified requirements. This serves not only to provide direction for the task of reuse, but also to assess the implications of reusing an ontology(s). Collectively, the solutions presented in this paper provide an important foundation for ontology reuse.
Keywords
Introduction
There exist many approaches to reuse, formalized to various degrees, and yet there is no clear definition of what it means to develop an ontology via reuse, and precisely what this entails. This hinders the support we can provide, and the development of the field as a whole. How can we talk about or develop tools/techniques for reuse if we don’t necessarily share the same understanding? There are a variety of alternative approaches to knowledge representation, and part of what sets ontologies apart is that they provide a knowledge representation that is not only unambiguous but adaptable, shareable, and reusable. However, if ontologies are not reused with care, these benefits may be (intentionally or not) discounted. Worse still, if the benefits are mistakenly assumed, they may give rise to inconsistencies or unintended semantics. While there are certainly other aspects of reuse to consider, such as the search for and selection of an ontology to reuse, this work focuses solely on the task of reusing a particular ontology(s) after it has been chosen.
Motivation
The term ontology reuse can be used to describe the repeated implementation of a single ontology, e.g. with different software applications. It also describes the use of existing axioms as input for an ontology engineering activity; while examples of ontologies being imported or otherwise referenced in the design of other ontologies are readily found throughout the community, the meaning of reuse in this sense is not clear. There are those who might view reuse as being restricted to cases where the entire ontology is reused (i.e. imported) in the engineering process. Others might relax this requirement and allow for a less complete import, so long as all of the relevant semantics are included. Beyond this, we also find cases wherein an ontology is reused, but then modified in some way because it is “not quite right” for the requirements.
Consider for example, the reuse of a very large and well-known ontology such as the Semantic Sensor Network Ontology (SSN),1
It is clear that the open view of reuse we have advocated allows for the introduction of serious issues in the absence of a formal definition. Specifically, there may be instances where an ontology is said to be reused, but its semantics are in some way changed.
In cases where only part of an ontology is reused, and perhaps even modified, the relationship between the original ontology and the ontology resulting from this is unclear. This lack of clarity is an important, though perhaps sometimes subtle complication for any future use of the resulting ontology. To illustrate this, let us consider the following simple example: Alice is designing an OWL ontology to represent aspects of her local transit system. The W3C time ontology (OWL-Time)3
How can some future user of Alice’s ontology know that an Interval cannot have a non-zero duration, and avoid any possible issues that might arise due to this? Only by careful inspection. A user with previous experience with OWL-Time would, understandably but incorrectly, assume an understanding of the semantics of time in Alice’s ontology without a detailed review of the axioms. This goes beyond impacting users’ understanding of the ontology but may also impact future efforts to integrate and align ontologies. This is a simple example for demonstration purposes, however it should be clear that similar, more complex scenarios could arise in practice. In such cases the changes made and the implications for the semantics may not be readily apparent. A well-defined metatheory provides the language to precisely specify any changes in order to avoid confusions and complications that might otherwise arise. It may be tempting to argue that such scenarios should simply not be documented as reuse. However, the original ontology and its manifestation in the new ontology will still share some semantics; to conceal reuse would have the undesirable effect of sacrificing all information regarding this shared semantics. Important information regarding the provenance of the axioms, and credit to the original sources would also be lost.
As alluded to in the previous example, a formal account of ontology reuse also plays a key role in characterizing the shareability of ontologies among systems. If two people claim that their own ontologies reuse the same ontology, there is some expectation that they will agree on the intended semantics of the terminology as axiomatized by the reused ontology. However, this is not the case when the ontology is being reused in different ways. Consider the example of reusing the DOLCE Ontology (Gangemi et al., 2002) – is the entire ontology being reused, or only some module? The latter case allows each person to use different axioms for concepts and relations that are outside of the modules being reused. Even if the two people are reusing the same modules, they may extend DOLCE in different ways – for example, one person may simply add new subclasses of existing classes in DOLCE while the other may provide additional axioms constraining the constitution relation. Without a formal characterization of reuse, we cannot make the distinctions that are required in this example.
Situations such as these raise a key question: What does it mean if one ontology is said to have reused another? What can we infer from this? To remedy this, we propose a metatheory of reuse; we characterize the ways in which it can occur and their implications. This provides a clear and precise understanding of reuse, and serves as a tool with which we can speak precisely about different instances of reuse.
We address these issues with several contributions. In Section 3 we derive a well-founded, formal definition for reuse from the notion of intended models. Through this definition, we define detailed reuse operations that completely characterize all possible cases of reuse. The properties of these operations are explored in Section 4. In Section 5 we discuss the implications of the metatheory; in particular, we describe how it may be applied to determine what operations were performed on any ontology that was reused. The definition provides a concrete understanding of what it means to reuse an ontology (or ontologies), as well as the necessary concepts to describe reuse at an effective level of detail. This serves to improve both our understanding of reuse and our ability to support it. This paper extends previous work by Katsumi and Grüninger (2016) with detailed results and an improved presentation of definitions. The reader is advised that a glossary of some relevant logical terms is provided for reference at the end of this paper.
Related work
Currently, we find no formal definition of ontology reuse accepted or even proposed within the community. Nearly all work pertaining to the task of reuse assumes some implicit definition of the reuse of an ontology; no effort is made, formal or otherwise, to provide further clarification of precisely what this entails. An exception to this is found in the sort of definition presented by Bontas et al. (2005), where the authors describe reuse as: …the process in which available (ontological) knowledge is used as input to generate new ontologies.
A similar, implicit definition may be found when reviewing the guidelines for reuse presented by Fernández-López et al. (2012), where the authors’ customizing activity (Activity 2) accounts for a wide range of loosely defined operations (pruning, enriching, translating, and adapting the selected ontology). Without any justification or precise definition of what these operations entail, it appears as though the authors also consider reuse to include any scenario in which an available ontology is used as an input in the development of a new one. Attempting to extract an implicit definition from other existing guidelines only reinforces that this vague definition is generally accepted by the community.
At best, we find that some more specific, related, and sometimes overlapping subtypes of reuse have been defined, such as merging and alignment (Noy and Musen, 1999), integration (Pinto and Martins, 2001; Gangemi et al., 1998), modular or ‘safe’ reuse (Grau et al., 2008), and the application of ontology patterns (Falbo et al., 2013). Even with the provision of examples and guidelines, these implicit definitions remain either vague or isolated to a specific type of reuse. No existing work has provided a concrete understanding of precisely what is, and what is not ontology reuse.
Defining reuse
In ontology design, we are attempting to create a set of axioms that captures some intended semantics of a set of concepts. Reuse is often conceptualized as a special case of design; intuitively, it refers to the task of taking some existing ontology(s) and manipulating it in some way in order to satisfy the design requirements. This observation is supported by existing, informal definitions of reuse.
In addition, there is an implicit condition which is often not stated as it is perhaps assumed as common sense – reuse can only be performed on a reusable ontology. To illustrate this with an example, consider the development of a finance ontology. It would be possible to take some existing anatomy ontology, and through some series of operations create the required finance ontology. However, if no remnants of the anatomy ontology are preserved in the finance ontology then we would not really want to consider such behaviour to be reuse. In fact, in such a case we may as well have developed the finance ontology from scratch. While manipulating an existing ontology is certainly a necessary part of reuse, it is not sufficient to define reuse. In order to define reuse, we first consider the notion of reusability in more detail and produce a formal definition. Following this, we define the different possible reuse operations, by which an ontology may be manipulated. The combination of the classification of operations and the condition of reusability will form the definition of reuse that we present here.
It is important to note that the work that follows is restricted in that it does not consider any signature translations of the ontology to be reused; in other words, we assume that the theories to be reused are axiomatized in the required signature, where applicable. This assumption is made in order to simplify the presentation of the definition, and while this may seem to be an oversimplification it is in fact quite reasonable. If an ontology has been selected for reuse, then the developer must at least implicitly observe some mappings between its signature and those of the requirements. It is then simple enough to satisfy the assumption of a shared signature through the application of these mappings between the signatures of the candidate and required theories. A straightforward process to accomplish this has in fact been suggested in previous work by Katsumi and Grüninger (2017). The definition presented here also assumes that no language translations are required; in other words the reused ontology(s) are in the same logical language as the ontology being developed. While not ideal, this is the norm in the current state and therefore a reasonable assumption to make.
Although we discuss the addition or removal of axioms, we view a theory as a set of sentences closed under logical implication. This is important to keep in mind while reviewing the material in the sections that follow.
A note on intended models. The foundation of our understanding of reusability is based on what we refer to as intended models. Before proceeding with our definition in the following section, it is important that we clarify some misconceptions and common questions about this concept.
This approach is unrealistic because you can’t possibly know all of the intended models; and if you have the intended models, then why are you developing the ontology? The role of intended models is to illustrate the concept of the explicit and implicit requirements that reside in the mind of the developer. We do not claim to have a complete characterization of the intended models, but these models exist in within the developer’s mind nonetheless. Some intended models may be partially characterized by rough axioms or competency questions: requirements that the developer is able to formalize to aid in his or her design. Others may only be revealed upon the developer’s recognition of some error: a model that the axioms allow that he recognizes as something undesirable, or conversely a model that he expects to be true in his theory but finds is precluded by the axioms. What if you can’t axiomatize them? From a practical standpoint, we are focused on ontologies in first-order logic and OWL, therefore for our purposes we consider only elementary classes of models. In general, the intended models dictate the required logical language; while there certainly are classes of models that cannot be axiomatized in, say first-order logic, if these are in fact the required (intended) models, this simply signifies that FOL is not the appropriate language.
Reusability
A perspective on the goal of ontology design is that its aim is to develop a set of axioms that captures the intended models. It follows that to satisfy the requirements with existing theories, we should be reusing theories that in some way characterize one or more of the different domains of conceptual coverage. As discussed, a key distinction between reuse and traditional development is that with the concept of reuse there is an implicit constraint on the acceptable (re-) design of the axioms. Simply put, if we claim that some ontology(s) has been reused, we expect and in fact should require that some remnants of the original ontology remain in the resulting ontology. For any ontology T that is reused to satisfy a developer’s intended models (we denote these
Note that we consider an ontology to be equivalent the logical closure of its set of axioms, i.e. a theory. We therefore use the term subtheory in the usual way in reference to an ontology (a theory), to refer to some weaker ontology, i.e. a ‘sub-ontology’.

If the ontology is weaker than required, the intended models (the dark shaded area) will only map to some of the models of its axiomatization. This and subsequent figures are adaptations of the depiction of intended models, originally from Guarino et al. (2009).
On the other hand,

If the ontology is stronger than required, the intended models (the dark shaded area) will map to models of a subtheory its axiomatization.

If the ontology is incomparable to the required ontology, the intended models (the dark shaded area) will only map to some of the models of a subtheory of its axiomatization.

Intuitively, if an ontology is reusable for some required ontology, we expect to find some part of it in the resulting ontology.
An additional factor to account for is that the class of intended models may characterize one or many different domains. For example, consider the design of an enterprise ontology:
Here, we extend the usual meaning of a reduct (denoted by
The reduct of a class of models
Collecting all of these observations, we can refine our intuitions to say more specifically that if an ontology T is reusable to satisfy
T is reusable for
There is a mapping
As an example, suppose each of the structures in
It is straightforward to extend this definition to apply to a collection of ontologies; the same intuition applies:
For a set of ontologies,
The notion of reusability can be captured similarly, from the perspective of the theories’ axiomatizations. Note that owing to our definition of an ontology being the logical closure of a set of axioms, the ⊆ symbol denotes a subtheory as opposed to simply a subset of axioms. We use
A set of ontologies
⇒
By Definition 3, if the set of ontologies some some
Since we are assuming that the mapping does not alter the signature of the models (in this simplified presentation we assume that no logic- or signature-translations are required), observe that we must have:
⇐
For each
While it is tempting to interpret Theorem 1 as a definition of reuse, it would be inaccurate to do so. Certainly, for any ontology that has been reused, we expect that it must have been reusable and thus we expect the results of reuse are captured by Theorem 1. In fact, the theorem captures the basic intuition of reuse that motivated the definition of reusability: in order for design to qualify as reuse, we expect some remnants of the original ontology(s) to remain. However, reusability is a necessary but not sufficient condition for reuse. There is an extralogical condition that must be accounted for in order to completely capture what it means to reuse an ontology. Unlike reusability, reuse is not a static property between theories; reuse refers to an act that is performed with some existing theories, in the design of an ontology. Simply because an ontology is reusable for some intended models does not mean it will or has been reused to axiomatize those models.
Informally, reuse is the act of applying some operations to a given, reusable ontology(s), such that the final result axiomatizes the intended models. To formally define reuse, these operations must be completely identified and defined. While various approaches to reuse, such as ontology fusion, merging, and extension, have been identified in varying degrees of detail in the current state, none of these approaches have been defined with respect to a complete definition of reuse; in some cases they have not been defined formally at all. Here, we provide a precise definition for a set of operations that completely covers the possible approaches to reuse. The terms used here should be interpreted independently of those that have been identified in the literature. No relationships should be inferred or assumed due to a similarity of terms or descriptions.
There are 4 distinct reuse operations by which an ontology may be manipulated for reuse:
The first two operations address the sort of do-nothing operation, and the operation to remove axioms from an ontology. Extension and combination are operations to add axioms to an ontology; the way that this occurs depends on the source of the axioms – they could be new axioms, created during design by the ontology developer, or they could be existing axioms, reused from some other ontology. It is important to make this distinction because these differences affect the way in which reuse is carried out. If the axioms were reused from another ontology, the design work is minimal, however if they are new axioms then the developer must have invested some time to design them from-scratch. This distinction between these two types of axiom addition also has potential implications for the shareability of the resulting theory. If the additional axioms were reused from some other ontology it may indicate that shareability will also be supported with this ontology; at the very least it indicates that shareability is something that should be considered and addressed in the metadata. We formalize this distinction by considering whether the additional axioms may be found in some repository. If axioms are added to one ontology (by reuse of axioms) from another ontology, then a combination has occurred. Otherwise, the addition is simply an extension of the ontology with additional axioms. We make reference to a single repository for simplicity, however it is straightforward to see that the definition and subsequent results also apply for any number of repositories or other sources of ontologies.

Intuition behind the specialized extraction operations.

Intuition behind the specialized extension operations, where
For each of these general operations (with the exception of
For the definitions that follow, let
The
Extraction refers to the reuse of an ontology via a removal of some of the original axioms, where the removed theory is denoted by
The
We identify the following three specializations of the extraction operation:
Domain Extraction: an entire domain (set of concepts) is completely extracted from the original ontology.
The
Note that T conservatively extends
Examples of domain extraction are quite common, and are closely related to the idea of extracting and reusing a maximal module
Weakening Extraction: the semantics of the original ontology are weakened by the operation while its scope remains the same.
The
Note that T non-conservatively extends
Residue Extraction: the residue of the theory is extracted. The term residue is used in the formal, logical sense as defined in the Glossary.
The
Note that T conservatively extends
Examples of residue extraction arise from reuse with weakly reducible ontologies, which have nonempty residues. The time interval ontologies discussed by Gruninger and Ong (2011) are the axiomatization of different ontological commitments for time intervals proposed by Van Benthem (1983). Applying the
Observe the specialized operations are completely distinct in that no one specialized operation may be defined in terms of either of the other specialized operations.
Extension refers to the reuse of an ontology via the creation and introduction of new axioms, denoted by
Let
The
Thus
We identify the following three specializations of the extension operation:
Domain Extension: the original ontology is extended via a new set of axioms
Let
The
Note that
One can consider the PSL-Core Ontology8
to be a domain extension of the timepoint ontologyStrengthening Extension: the original ontology is extended via a new set of axioms
Let
The
Note that
Strengthening extension is often found when reuse of one theory leads to unintended models. For example, the central result of work by Muñoz and Grüninger (2016) is the verification of a nonconservative extension of SUMO-Time; that is, SUMO-Time was extended to a new ontology
Residue Extension: the original ontology is extended via a new set of axioms
Let
The
Note that
Examples of residue extension can be seen in the Periods Hierarchy11
of COLORE, particularly between the two ontologiesObserve that the specialized operations are completely distinct in that no one specialized operation may be defined in terms of either of the other specialized operations.
Combination is the reuse of an ontology
Let
The
We identify the following three specializations of the combination operation:
Domain Combination: The original ontology T is combined with another ontology
Let
The
Note that
Domain combination arises most prominently with reducible theories and the design of upper ontologies using the sideways approach (Grüninger et al., 2014, 2017), in which generic ontologies in domains such as time, process, mereotopology, and physical objects are combined.
Strengthening Combination: The original ontology T is combined with another ontology
Let
The
Note that
Residue Combination: The original ontology T is combined with another ontology
Let
The
Note that
Again, consider the definition of reuse – this time based on the reuse operations that have just been defined. Such a definition appeals to our intuition: reuse is the application of some set of reuse operations; however the act of reuse cannot be defined via these operations alone. It is not the case that any set of these operations corresponds to an act of reuse. For example, consider a scenario in which we extract a subtheory from some existing ontology, extend it with some new axioms, and then perhaps extract a subtheory again, such that no remnants of the original theory remain. This violates a key condition for reuse that is captured in the definition for reusability. We cannot have such possibilities included within the definition of reuse. To completely define what we mean by reuse, we must incorporate both the logical conditions identified previously and the extralogical conditions of the operations performed. Reuse is defined as the act of performing some set of operations on some existing ontology(s)
Note that we use the term ontology in a broad sense – this work includes the possibility that
some set of reuse operations applied to
The sections that follow explore the ramifications of this definition and the transparency it provides for the task of reuse.
The metatheory of reuse defines specialized operations with a precision such that their effect on the preservation of semantics of the original theory is clear. It also provides a foundation upon which we may identify and prove useful properties about the operations; several such properties are presented in the following sections.
Commutativity
While it is intuitive to consider reuse as the application of a sequence of these operations, so long as an ontology or set of ontologies
The operations for reuse are commutative.
To illustrate this, we consider each pairing of reuse operations and show that either order of application produces the same results. It is clear that like-operations will achieve the same result in any order, therefore we consider only pairings of different operations. It is straightforward to see that this then extends to any series of operation applications.
Consider the application of as_is to some T, followed by extraction of some By definition, Similar to above, from the definition of as_is the result is trivial. Similar to above, from the definition of as_is the result is trivial. Consider the application of extraction of some Consider It is straightforward to see that the removal of any subtheory of T (i.e. an extraction) results in a subtheory of T: Now, say we add some theory to the extraction of T and to T. It is straightforward to see that the extraction, with some addition, will also be a subtheory of T, with the same addition, so that Likewise, any subtheory that we remove from both sides cannot affect this relationship; at most we can reduce Now, consider It is straightforward to see that any extension of T subsumes T itself: This subsumption relationship will be maintained, with the possibility of equivalence, should any subtheory be removed from both sides: Again, any subtheory added to both sides will maintain the subsumption relationship will be maintained. Adding Since we have shown: The result is the same as above, except instead of It is trivial to see that:
Observe that there are not only different possible sequences but in fact many different sets of operations that achieve the same result. Such sets may be differentiated through redundant or unnecessary operations. For example, consider repeated applications of extension and extraction operations that add and remove the same axioms. This may seem bizarre, but consider a design scenario where one approach is attempted, only to find it does not have the desired effect and it is therefore undone or modified in a subsequent step. In some instances, it may be useful to distinguish those operations that are necessary to achieve the reuse of a particular theory(s) for some
A Let
Each reuse operation may be completely defined by its specialized operations. In other words, there exists no instance of reuse that cannot be described by some combination of specialized reuse operations. The proofs for each general reuse operation follow.
Domain extraction, weakening extraction, and weakening domain extraction are the only ways in which reuse via extraction can occur.
Let By definition, if Let Let By definition, if
For any T,
For any T, Let Let Let By definition, if Therefore, we have:
Domain combination, strengthening combination, and strengthening domain combination are the only ways in which reuse via combination can occur.
The proof for this lemma follows precisely the same form as the proof for Lemma 2 with the minor distinction that rather than
The reuse operations defined not only help to identify the sorts of manipulations that may be performed, they provide a complete characterization of the possible ways in which an ontology(s) may be reused; through this they provide concrete examples of what is, and what is not reuse.
Let
Assume the theorem is false. Then we must have some
There are 2 possible cases: reuse of a single theory or reuse of multiple theories.
By definition, if T is reused for
There exists a
It is straightforward to see that in this case one of the following 4 situations must be true:
There exists a T reused for There exists a Therefore the assumption cannot hold in this situation as it corresponds to reuse of T via extraction of some There exists a The assumption cannot hold in this situation as it corresponds to reuse of T via extraction of some There exists a This cannot hold as it corresponds to reuse of T via extension with some This cannot hold as it corresponds to as_is reuse of T for
Therefore when
In order to reuse multiple theories, the combination operation must be applied at some point, to collect all of the theories
Again, by Theorem 1:
There exists a
Consider all n theories collectively, let
Let
Let
By Theorem 3, for any ontology or set of ontologies By Lemma 1 any By Lemma 2 any By Lemma 3 any
Therefore, for any ontology or set of ontologies
Theorem 4 confirms that our definition of reuse operations has in fact covered all cases of reuse.
The metatheory presented in this paper provides a formal foundation for the task of ontology reuse. In order for ontology development to move toward becoming an engineering discipline, concepts like reuse and its operations must be clearly understood and defined. Here, we consider the implications of this work; in particular, the improved understanding and the opportunities for reuse support that it provides for reuse.
Documenting ontology reuse
For any ontology, either during or post-reuse, it is important that the developer understand – and be able to communicate – precisely what reuse operations must be or were applied. This is valuable both in providing guidance for reuse, and also in assessing precisely how a particular ontology was reused. The metatheory of ontology reuse provides a language with which a developer may communicate the operations that were performed during reuse, and as a result, specify the relationship between the new and the reused ontology(s). Extraction, extension and combination may be performed in several distinct ways, each of which has a different intuition and impact on the resulting ontology. The specializations of the reuse operations are based on a more precise identification of these changes to the original ontology. Not only does this provide more detailed guidance with respect to the required operations, it allows for a more detailed analysis of the implications of any given reuse scenario. The identification of these operations facilitates recognition of the relationships between concepts in the original ontology(s) and the resulting ontology being developed via reuse. Most notably, this supports the identification of shareability that is attained or lost for concepts in the new ontology. If applied to consider the operations required to axiomatize some approximation of the required theory (a set of competency questions, for example), the identification of necessary specialized operations may also be used as a sort of look-ahead. In the same way that the operations provide valuable documentation post-reuse, a priori their approximation serves to inform developers of the implications that a reuse operation on some ontology will have on its semantics, and consequently the resulting shareability that can be expected. The result serves to provide information about the shareability between the resulting ontology and the reused theories. In effect, it enables us to give a useful answer the question: What does it mean if one ontology is said to have reused another?
It is our hope that the reuse operations be applied and annotated by ontology developers as a means of documenting reuse. Failing this, the metatheory of reuse also provides a means of explicitly identifying or specifying how a given ontology(s) was reused. Not only does there exist some set of operations to axiomatize the intended models, we can in fact leverage the definitions to determine precisely what operations were required. This result comes about by way of the proof for Theorem 3. The proof illustrates the straightforward identification of the required, general operations to axiomatize some
Beyond semantic requirements
The analysis of necessary operations described above only considers required changes to the models of the ontology being reused. In practice, it may be the case that axioms that are added or removed during the course of reuse are logical consequences of the theory and have no impact on its underlying models. Such cases are included in the definitions of the appropriate reuse operations, however they cannot be identified by considering the intended models. This is because these cases are motivated by extra-logical requirements. The addition or removal of such axioms may be motivated by usability considerations; for example, a developer may add several axioms which are intended simply to make the theory more easily understandable. Alternatively, axioms are sometimes added or removed to achieve improvements in automated reasoner performance. While these cases were not explicitly addressed in the definition of reuse, they are included in the definition of the operations. It is worth noting however, that with only knowledge of the intended models, we cannot recognize when such operations have been or will be required.
Other operations on ontologies
The reader may note that the notion of ontology operations itself is not novel. Work on ontology algebras, belief revision, and the Distributed Ontology Language (DOL) standard have particular resonance. We review each of these areas here and discuss the relationship to this work. It is critical to note that the novelty of the current work is not in the identification of the operations themselves, rather, the contribution we make is the way in which we interpret these operations, in the context of a metatheory of ontology reuse. The perspective we take in defining these operations is such that they serve to both prescribe how an ontology can be reused to satisfy a given set of requirements, and to assess what the implications of this reuse will be on the resulting ontology.
Ontology algebras
The ontology algebra presented by Mitra and Wiederhold (2004), Wiederhold (1994) are designed to support ontology integration, thus the resulting operations focus on composing ontologies when global consistency is not feasible. We observe that similarities are evident between the operators defined in this work and the reuse operations we identify here. In particular, the combination and extraction operations may be captured by operators defined for ontology algebras. A major distinction here is that the role of the algebra operators is to support the integration ontologies, thus their attention is on the combinations of ontologies. The intersection and difference operators defined for the ontology algebra do not correspond to any of the reuse operations we define here, as these distinctions are not relevant for our purposes; nor do the algebras define any sorts of extension operations, as their focus is on the combination of existing theories, not the addition of new axioms.
Belief revision and the AGM framework
The reader may also have noticed similarities between the identified operations and the well-known AGM Framework for belief revision by Alchourrón et al. (1985), Gärdenfors (2003). It defines operations, or ways in which beliefs can change. The notion of revising a set of beliefs to resolve inconsistencies is thus one of particular importance. In the context of ontologies, the AGM Framework may be considered as a tool to approach ontology evolution (Flouris et al., 2006).
Conceptually, the extraction, extension, and combination operations could all be described in the AGM Framework, albeit without the sorts of distinctions that are made between the specializations. On the other hand, there are belief revision operations such as revision and consolidation that do not correspond to any of the reuse operations defined here. Again, a major distinction is that the purpose of these operations is to update the belief set and arrive at a consistent set of beliefs, whereas the reuse operations are manipulating existing ontology(s) in order to arrive at a specific end result.
DOL
The Distributed Ontology Language (DOL) (Mossakowski et al., 2012), has been designed in response to the OntoIOP request for proposal (Neuhaus, 2013) to address the challenge of interoperability for heterogeneous formal representations. The DOL project considers not only ontologies, but ‘specifications and MDE [Model-Driven Engineering] models’ in a variety of languages, and is focused not on reuse but on integration and interoperability. While the scope of this project is much broader and not quite aligned with the work presented here, we find that the ‘structuring language for OMS’ provided by DOL corresponds in a way to the concept of reuse operations. A key distinction is that the language in DOL defines constructs, which are meant to describe the structure of theories and how they relate to one another, as opposed to the definition of operations here which represents a manipulation performed on a given ontology.
Each of the reuse operations defined here may be expressed by some DOL construct. However certain distinctions such as the difference between the original and resulting signature that are made when considering operations in the context of reuse, are not captured by these constructs as they are simply not relevant when defining metalogical relationships between theories. As mentioned, the DOL constructs provide a means of describing the structure of an ontology such that we can understand its relationship to other ontologies. The concept of an ‘original’ (reused) ontology, or even the source of axioms (another ontology, or created by the developer) make little sense from this perspective.
Extending the definition of reuse
The definition of reuse presented in this paper is subject to two major assumptions that are made to simplify its presentation: we assume that no translations of an ontology’s signature or language are performed as part of reuse. While justifiable, there exists practical motivation to consider a more general definition of reuse that does not make these assumptions. Different terminology may be more or less appropriate in different domains, so it is possible that some modifications to the signature may sometimes be required, and it would be reasonable to still recognize such behaviour as reuse. Furthermore, Grüninger and Katsumi (2012) present an approach wherein ontologies from the same domain are reused in ontologies for parthood, periods of time, as well as subactivities, by applying translations to the signature. By considering reuse with signature translations, a seemingly unrelated theory may in fact provide precisely the required semantics that are required. This approach greatly expands the pool of potential candidates, thus encouraging reuse and increasing the possibility of finding an appropriate ontology.
Including the possibility of translation between languages is a more challenging task, however it has the potential to be tremendously beneficial for the development of ontologies. Translation of ontologies in different logical languages both expands the candidates for reuse, and allows developers to take advantages of the strengths and weaknesses of different languages and communities. For example, development of a FOL ontology might take advantage of the widespread application and use of OWL ontologies, whereas as in our earlier example OWL ontologies may take advantage of the rigorous definitions that are more typical of FOL ontologies. In forthcoming work, we shall present an extended definition of reuse that builds on the work presented here to capture the possibility of reuse with translations of an ontology’s signature and language.
Conclusion
Although ontology reuse is widely recognized as a critical aspect of ontology design and application, the principles and practice of reuse remains underdeveloped because no definition of reuse or complete characterization of operations to achieve reuse has been proposed. The metatheory of reuse presented in this paper is a novel contribution that provides the logical foundations for ontology reuse. While there are certainly other challenges that present barriers for the reuse of ontologies, the work presented in this paper takes steps towards the goal of reuse becoming a more principled and effective means of ontology design by developing definitions for the concepts of reuse and reusability that are not only formal but functional. We have presented a precise set of reuse operations that, in any possible case, can be applied to an ontology in order to satisfy some specified semantic requirements. Not only are the operations capable of providing valuable guidance for reuse, perhaps more crucially they provide a means of assessing and understanding the implications of a given instance of reuse.
This work provides the necessary metatheory to support ontology reuse, but in the absence of tools to support such solutions, their adoption is not guaranteed. The availability of tool support to implement this metatheory would be an invaluable contribution towards simplifying and improving the practice of reuse. We hope that future work will look towards the adoption of the approach to reuse presented here in a more user-friendly medium, perhaps integrated with existing ontology design tools.
Of particular interest for the task of ontology reuse are the relationships identified between the reuse operations and the constructs specified in DOL. The correspondences that we have identified present an opportunity to extend implementation of this work to capture any resulting ontologies in the DOL terminology. For example, it will be straightforward to translate the necessary reuse operations to axiomatize the intended models from some
Footnotes
Definitions for relevant logical terminology
Here we include definitions for the logical terms employed in this work for the reader’s reference.
