Hubbry Logo
Ontology engineeringOntology engineeringMain
Open search
Ontology engineering
Community hub
Ontology engineering
logo
8 pages, 0 posts
0 subscribers
Be the first to start a discussion here.
Be the first to start a discussion here.
Ontology engineering
Ontology engineering
Ontology engineering
View on Wikipedia
from Wikipedia
Example of a constructed MBED Top Level Ontology based on the nominal set of views[1]

In computer science, information science and systems engineering, ontology engineering is a field which studies the methods and methodologies for building ontologies, which encompasses a representation, formal naming and definition of the categories, properties and relations between the concepts, data and entities of a given domain of interest. In a broader sense, this field also includes a knowledge construction of the domain using formal ontology representations such as OWL/RDF. A large-scale representation of abstract concepts such as actions, time, physical objects and beliefs would be an example of ontological engineering.[2] Ontology engineering is one of the areas of applied ontology, and can be seen as an application of philosophical ontology. Core ideas and objectives of ontology engineering are also central in conceptual modeling.

Ontology engineering aims at making explicit the knowledge contained within software applications, and within enterprises and business procedures for a particular domain. Ontology engineering offers a direction towards solving the inter-operability problems brought about by semantic obstacles, i.e. the obstacles related to the definitions of business terms and software classes. Ontology engineering is a set of tasks related to the development of ontologies for a particular domain.

— Line Pouchard, Nenad Ivezic and Craig Schlenoff, [3]

Automated processing of information not interpretable by software agents can be improved by adding rich semantics to the corresponding resources, such as video files. One of the approaches for the formal conceptualization of represented knowledge domains is the use of machine-interpretable ontologies, which provide structured data in, or based on, RDF, RDFS, and OWL. Ontology engineering is the design and creation of such ontologies, which can contain more than just the list of terms (controlled vocabulary); they contain terminological, assertional, and relational axioms to define concepts (classes), individuals, and roles (properties) (TBox, ABox, and RBox, respectively).[4] Ontology engineering is a relatively new field of study concerning the ontology development process, the ontology life cycle, the methods and methodologies for building ontologies,[5][6] and the tool suites and languages that support them. A common way to provide the logical underpinning of ontologies is to formalize the axioms with description logics, which can then be translated to any serialization of RDF, such as RDF/XML or Turtle. Beyond the description logic axioms, ontologies might also contain SWRL rules. The concept definitions can be mapped to any kind of resource or resource segment in RDF, such as images, videos, and regions of interest, to annotate objects, persons, etc., and interlink them with related resources across knowledge bases, ontologies, and LOD datasets. This information, based on human experience and knowledge, is valuable for reasoners for the automated interpretation of sophisticated and ambiguous contents, such as the visual content of multimedia resources.[7] Application areas of ontology-based reasoning include, but are not limited to, information retrieval, automated scene interpretation, and knowledge discovery.

Languages

[edit]
Further information: ontology language

An ontology language is a formal language used to encode the ontology. There are a number of such languages for ontologies, both proprietary and standards-based:

  • Common logic is ISO standard 24707, a specification for a family of ontology languages that can be accurately translated into each other.
  • The Cyc project has its own ontology language called CycL, based on first-order predicate calculus with some higher-order extensions.
  • The Gellish language includes rules for its own extension and thus integrates an ontology with an ontology language.
  • IDEF5 is a software engineering method to develop and maintain usable, accurate, domain ontologies.
  • KIF is a syntax for first-order logic that is based on S-expressions.
  • Rule Interchange Format (RIF), F-Logic and its successor ObjectLogic combine ontologies and rules.
  • OWL is a language for making ontological statements, developed as a follow-on from RDF and RDFS, as well as earlier ontology language projects including OIL, DAML and DAML+OIL. OWL is intended to be used over the World Wide Web, and all its elements (classes, properties and individuals) are defined as RDF resources, and identified by URIs.
  • OntoUML is a well-founded language for specifying reference ontologies.
  • SHACL (RDF SHapes Constraints Language) is a language for describing structure of RDF data. It can be used together with RDFS and OWL or it can be used independently from them.
  • XBRL (Extensible Business Reporting Language) is a syntax for expressing business semantics.

Methodologies and tools

[edit]

In life sciences

[edit]

Life sciences is flourishing with ontologies that biologists use to make sense of their experiments.[9] For inferring correct conclusions from experiments, ontologies have to be structured optimally against the knowledge base they represent. The structure of an ontology needs to be changed continuously so that it is an accurate representation of the underlying domain.

Recently, an automated method was introduced for engineering ontologies in life sciences such as Gene Ontology (GO),[10] one of the most successful and widely used biomedical ontology.[11] Based on information theory, it restructures ontologies so that the levels represent the desired specificity of the concepts. Similar information theoretic approaches have also been used for optimal partition of Gene Ontology.[12] Given the mathematical nature of such engineering algorithms, these optimizations can be automated to produce a principled and scalable architecture to restructure ontologies such as GO.

Open Biomedical Ontologies (OBO), a 2006 initiative of the U.S. National Center for Biomedical Ontology, provides a common 'foundry' for various ontology initiatives, amongst which are:

and more

See also

[edit]

References

[edit]

Further reading

[edit]
[edit]
Revisions and contributorsEdit on WikipediaRead on Wikipedia

Ontology engineering

View on Grokipedia
from Grokipedia
Ontology engineering is the discipline of systematically designing, developing, maintaining, and evaluating ontologies, which are formal, explicit specifications of shared conceptualizations representing the entities, properties, relationships, and constraints within a specific domain of knowledge. These ontologies serve as foundational artifacts for enabling semantic interoperability, knowledge sharing, and automated reasoning in fields such as the Semantic Web, artificial intelligence, and data integration. Unlike traditional database schemas or conceptual models like UML, ontologies emphasize logical consistency, reusability across applications, and machine-readable semantics, often implemented using standardized languages such as OWL (Web Ontology Language). The field emerged in the 1990s, drawing from philosophical ontology and knowledge representation traditions, with significant momentum gained through the Semantic Web vision articulated by Tim Berners-Lee and colleagues in 2001. Early milestones include the development of Description Logics (DLs) in the mid-1980s, which provided the formal basis for ontology languages, and the W3C's standardization of OWL in 2004, followed by OWL 2 in 2009 to enhance expressivity and profiling options. Over the past decade, ontology engineering has evolved with increased adoption in domains like biomedicine—exemplified by the Gene Ontology project launched in 2000 for gene product annotation—and finance, such as the Financial Industry Business Ontology (FIBO). Community efforts, including the Open Biomedical Ontologies (OBO) Foundry established in 2007, have promoted best practices for interoperability and reusability. At its core, ontology engineering encompasses methodologies ranging from top-down approaches that start with foundational ontologies like DOLCE or BFO to establish high-level categories, bottom-up methods that derive concepts from existing data sources or thesauri, and middle-out strategies that balance both for iterative refinement. Key processes include competency questions to define scope, modularization for manageability, and validation techniques like OntoClean to ensure meta-property constraints such as rigidity and unity. Tools such as Protégé, with over 360,000 users, facilitate editing, reasoning, and visualization, while ontology design patterns (ODPs) promote reuse and quality assurance. Reasoning services, powered by DL reasoners like HermiT or ELK, support tasks such as class subsumption, consistency checking, and instance classification under the Open World Assumption. Notable applications span knowledge graphs like DBpedia (with approximately 6 million entities) and Wikidata (over 119 million entities as of 2025), cultural heritage projects such as Europeana, and clinical standards like the International Classification of Diseases (ICD-11). Despite advancements, challenges persist, including the steep learning curve of OWL, low ontology reuse rates (under 9% in biomedicine), and difficulties in alignment, evolution, and integration with emerging technologies like knowledge graphs and explainable AI. Future directions emphasize user-friendly interfaces through human-computer interaction (HCI) collaboration, automated ontology learning via natural language processing and large language models, and enhanced standards like ISO 21127:2023 for conceptual schema representation.

Fundamentals

Definition and Scope

Ontology engineering is the systematic process of developing, maintaining, and evolving ontologies to explicitly represent domain knowledge for computational use. An ontology itself is defined as a formal, explicit specification of a conceptualization, encompassing the objects, concepts, and entities presumed to exist in some area of interest, along with their properties and interrelations. This engineering discipline focuses on creating structured, logic-based knowledge representations that are machine-readable and reusable across applications. The primary objectives of ontology engineering include enhancing interoperability between heterogeneous information systems, facilitating semantic integration of data from diverse sources, and enabling automated reasoning to infer new knowledge or validate consistency. By providing a shared vocabulary and formal constraints, it supports precise knowledge sharing and reduces ambiguity in data exchange, particularly in distributed environments like the Semantic Web. Ontologies enable modeling of domain-specific concepts, allowing for accurate data retrieval and analysis in various fields. Ontology engineering differs from knowledge engineering in its emphasis on formal, logic-based structures optimized for computational inference, whereas knowledge engineering encompasses broader activities like informal knowledge acquisition from experts and diverse representation techniques without strict formalization. While both aim to capture expertise for intelligent systems, ontology engineering prioritizes explicit axioms and machine-interpretable semantics to support automated processes. Core components of an ontology include classes (representing concepts or categories), properties (such as object properties for relations between classes and data properties for attributes), relations (defining how classes interact), instances (specific examples of classes), and axioms (logical rules or constraints that govern the ontology). These elements form a knowledge base typically divided into a TBox (terminological knowledge about classes and properties) and an ABox (assertional knowledge about instances). Within computer science, information science, and systems engineering, the scope of ontology engineering extends to applications such as knowledge representation, data integration, and semantic query answering, yielding benefits like improved data sharing across silos and enhanced decision-making through inferential capabilities. It plays a crucial role in fields requiring precise semantic modeling, including artificial intelligence and database systems, where ontologies promote consistency and scalability in knowledge management.

Historical Development

The roots of ontology engineering trace back to ancient philosophy, particularly Aristotle's work in the Categories, where he outlined a foundational classification of entities into ten fundamental types, such as substance, quantity, and quality, to systematically describe what exists in the world. This approach laid the groundwork for ontological inquiry as a means of categorizing reality. In the 20th century, analytic philosophy further advanced these ideas, with Willard Van Orman Quine's 1948 paper "On What There Is" introducing the concept of ontological commitment, which posits that a theory's commitments to entities are determined by the variables it quantifies over in first-order logic, influencing later computational interpretations of existence and representation. The emergence of ontology engineering in artificial intelligence began in the 1970s and 1980s, driven by the need for structured knowledge representation in expert systems. During this period, frame-based systems, proposed by Marvin Minsky in his 1974 paper "A Framework for Representing Knowledge," provided a method to organize knowledge into reusable structures that capture stereotyped situations and their attributes, facilitating reasoning in early AI applications. A seminal project in this era was the Cyc initiative, launched in 1984 by Douglas Lenat at the Microelectronics and Computer Technology Corporation, which aimed to encode a vast common-sense knowledge base to enable machine understanding of everyday concepts, marking an early large-scale effort in manual ontology construction. The 1990s marked a pivotal shift toward ontology engineering in the context of the semantic web, with Tom Gruber's 1993 paper "A Translation Approach to Portable Ontology Specifications" defining an ontology as "an explicit specification of a conceptualization," emphasizing its role in enabling shared understanding across systems. Key U.S. Defense Advanced Research Projects Agency (DARPA) initiatives, such as the 1990 Summer Ontology Project and the later DARPA Agent Markup Language (DAML) program in the late 1990s, promoted reusable ontologies for knowledge sharing and integration in distributed AI systems. This momentum culminated in the World Wide Web Consortium's (W3C) standardization of the Web Ontology Language (OWL) in 2004, providing a formal framework for web-based ontologies that built on RDF and supported advanced reasoning. Post-2000, the field saw significant growth, particularly in biomedical domains, exemplified by the Gene Ontology project initiated in 1998 but expanding rapidly after 2000 to standardize gene function annotations across species. The early 2000s also witnessed the formal establishment of the ontology engineering community, with dedicated surveys and methodologies emerging around 2006 to address systematic development processes.

Formal Foundations

Ontology Languages and Standards

Ontology engineering relies on standardized languages to formally represent knowledge structures, ensuring interoperability and machine readability across systems. The Resource Description Framework (RDF) serves as a foundational model for this purpose, defining data as directed graphs composed of triples in the form of subject-predicate-object statements. This graph-based approach allows for flexible representation of relationships between resources, identified by URIs, and supports the integration of heterogeneous data sources without a fixed schema. RDF 1.1, published in 2014, provides the current specification with enhancements such as support for named graphs and improved internationalization. Building upon RDF, the Web Ontology Language (OWL) provides a more expressive framework for defining ontologies, enabling the specification of classes, properties, and axioms with precise semantics. OWL was standardized by the W3C in 2004, with OWL 2 published in 2009 to address limitations in expressivity and performance. OWL 2 defines two main semantics: OWL 2 DL, which supports description logic constructs while maintaining computational decidability for automated reasoning; and OWL 2 Full, which allows unrestricted use of RDF vocabulary but at the cost of potential undecidability. Additionally, OWL 2 includes three tractable profiles—OWL 2 EL for existential expressivity in large ontologies, OWL 2 QL for query answering via database technologies, and OWL 2 RL for rule-based implementations—optimized for efficiency in specific applications. Beyond OWL, several other languages facilitate ontology representation, particularly for rule-based and logic-intensive extensions. Common Logic (CL), defined in ISO/IEC 24707, offers a family of first-order logic dialects for interchanging knowledge across systems, emphasizing modular and extensible syntax. The Knowledge Interchange Format (KIF) provides a predicate calculus-based language for sharing knowledge among disparate programs, with declarative semantics that avoid procedural implications. F-Logic extends frame-based systems with logic programming features, supporting rule-based ontology definitions through stratified negation and inheritance mechanisms. Standards bodies play a crucial role in governing these languages and their implementations. The W3C oversees RDF and OWL specifications, ensuring web compatibility, while ISO standardizes broader logic frameworks like Common Logic. The OBO Foundry coordinates domain-specific ontologies, particularly in biomedicine, by enforcing principles such as adherence to shared syntax and serialization standards. Serialization formats like Turtle, a compact textual syntax for RDF graphs, and N-Triples, a line-based format for simple triple encoding, are defined by W3C to promote data exchange. A key distinction in ontology languages lies in their expressivity trade-offs. OWL 2 DL achieves decidability through syntactic restrictions aligned with description logics, enabling sound and complete automated reasoning. In contrast, OWL 2 Full's unrestricted RDF integration leads to undecidability, as it permits constructs that exceed the decidable fragment of first-order logic.

Representation Formalisms

Description logics (DLs) provide the mathematical and logical foundations for representing ontologies in ontology engineering, offering a decidable fragment of first-order logic tailored for knowledge representation. DLs model domain knowledge through concepts (interpreted as unary predicates or sets of individuals), roles (binary predicates or relations between individuals), and axioms that define relationships such as subsumption. The family of DLs, particularly the ALC (Attributative Language with Complements) subfamily, serves as the cornerstone for expressive ontology languages. ALC includes basic constructors such as intersection (⊓\sqcap), which combines concepts into their logical conjunction; union (⊔\sqcup), representing disjunction; negation (¬\neg), for complementation; universal quantification (∀R.C\forall R.C), restricting all role fillers to concept CC; and existential quantification (∃R.C\exists R.C), requiring at least one role filler in CC. These constructors enable precise definitions of complex concepts while maintaining computational tractability. Formally, an ontology in DLs is often defined as a tuple O=(C,R,A,I)O = (C, R, A, I), where CC denotes the set of concepts, RR the set of roles, AA the set of axioms (including general concept inclusions C⊑DC \sqsubseteq D and role inclusions), and II the set of individuals with assertions linking them to concepts and roles. Semantics are provided by interpretations I=(ΔI,⋅I)\mathcal{I} = (\Delta^\mathcal{I}, \cdot^\mathcal{I}), where ΔI\Delta^\mathcal{I} is a non-empty domain and concepts map to subsets of ΔI\Delta^\mathcal{I}, while roles map to binary relations on ΔI×ΔI\Delta^\mathcal{I} \times \Delta^\mathcal{I}. For instance, the intersection constructor satisfies (C⊓D)I=CI∩DI(C \sqcap D)^\mathcal{I} = C^\mathcal{I} \cap D^\mathcal{I}, ensuring set-theoretic consistency. This structure supports the separation of terminological knowledge (TBox axioms in AA) from assertional knowledge (ABox involving II). DLs like ALC form the basis for standards such as OWL 2 DL, which corresponds to the more expressive SROIQ(D) logic. Reasoning in DLs relies on tableau algorithms, which construct models (tableaux) by systematically expanding an initial ABox through non-deterministic rules that enforce concept and role constraints. These algorithms apply expansion rules for constructors, such as the ⊓\sqcap-rule (branching to satisfy both subconcepts) and ∃\exists-rule (introducing successors), while clash detection identifies contradictions like an individual in both a concept and its negation. Tableau methods are sound, preserving satisfiability from the initial to expanded ABox, and complete, as blocking techniques (e.g., pair-wise or subset blocking) ensure termination by preventing infinite expansions in cyclic models. For expressive DLs like SROIQ(D), underlying OWL 2 DL, reasoning tasks such as concept satisfiability and subsumption are NEXP-complete, reflecting the added complexity from features like transitive roles (S), role hierarchies (H), nominals (O), inverse roles (I), and datatypes (D). Despite this worst-case complexity, optimizations like caching and rule ordering enhance practical efficiency. Extensions to basic DLs address limitations in modeling dynamic or uncertain domains. Hybrid logics augment DLs with nominals (singleton concepts) and binders (state variables for referencing individuals), enabling more flexible ontology representations while preserving decidability in restricted forms; for example, adding nominals to ALC yields ALCO, which supports extensional class definitions common in ontologies. Temporal DLs incorporate linear-time operators (e.g., "always" □\Box or "eventually" ◊\Diamond) to capture evolving knowledge in dynamic ontologies, such as business processes, with decidable fragments like TUALC\mathcal{T}_\text{U}\text{ALC} achieving EXPTIME complexity for satisfiability over bounded traces. Probabilistic extensions, such as ALCp^p, integrate probability bounds (e.g., C1[p1,p2]C2C_1 [p_1, p_2] C_2 for conditional probabilities) to handle uncertainty, ensuring consistency through non-empty probabilistic models and enabling inferences like range refinement under statistical assumptions. In contrast to full first-order logic (FOL), which offers unrestricted expressivity but is undecidable for satisfiability, DLs are carefully restricted fragments that ensure decidability. ALC, for instance, embeds into the two-variable fragment of FOL (FO2_2), which is NEXPTIME-complete, but avoids features like arbitrary quantifier nesting or function symbols that lead to undecidability. While FOL supports full predicate expressivity, DLs prioritize tailored constructors and optimized reasoning, trading some generality for computational feasibility in ontology applications.

Development Methodologies

Engineering Processes

Ontology engineering processes provide structured approaches to the systematic development, refinement, and maintenance of ontologies, ensuring they meet domain-specific requirements while supporting interoperability and scalability. These processes typically follow lifecycle models that emphasize iteration, collaboration, and validation to address the complexity of knowledge representation. Seminal methodologies have emerged to guide practitioners in transforming informal domain knowledge into formal, computable structures. One foundational methodology is METHONTOLOGY, introduced in 1997, which outlines a lifecycle based on evolving prototypes divided into five main phases: specification, where the ontology's purpose, scope, and explicit assumptions are defined; conceptualization, involving the organization of knowledge into abstract models such as hierarchies and taxonomies; formalization, where these models are expressed using semi-formal or formal representations; implementation, translating the formal model into a specific ontology language; and maintenance, encompassing updates and corrections to ensure ongoing relevance. This approach draws from software engineering principles to treat ontology development as an engineering discipline rather than an ad hoc art. Building on such foundations, the NeOn Methodology, developed through an EU-funded project from 2006 to 2010, extends lifecycle support to networked and collaborative ontology engineering. It adopts a scenario-based framework that tailors processes to specific contexts, such as reusing existing ontologies or integrating distributed knowledge sources in team environments, thereby facilitating the construction of ontology networks. The methodology includes guidelines for scheduling activities across the lifecycle, emphasizing adaptability for large-scale, interdisciplinary projects. A widely referenced practical guide is Ontology Development 101, published in 2001, which proposes a seven-step process for beginners: determining the domain and scope via competency questions; considering reuse of existing ontologies; enumerating important terms; defining classes and the class hierarchy; defining properties of classes; defining facets of slots (properties); and creating instances. This iterative process encourages incremental building and testing, starting from core concepts and expanding outward. Across these methodologies, ontology lifecycles incorporate iterative refinement to accommodate evolving domain knowledge, version control mechanisms to track changes and manage dependencies, and evaluation metrics focused on consistency (ensuring no logical contradictions within the ontology) and coherence (verifying the ontology's alignment with domain knowledge through techniques like competency questions). Such aspects promote reliability, with consistency checks often involving automated reasoning to detect contradictions, and coherence evaluations comparing the ontology against competency questions. Key principles guiding these processes include the use of competency questions to elicit precise requirements—what specific queries the ontology must support—to define scope and validate coverage from the outset. Additionally, a middle-out development strategy balances top-down (starting from broad categories) and bottom-up (from specific instances) approaches by prioritizing central, domain-relevant concepts first, then extending to abstractions and details, which enhances modularity and eases integration with reuse techniques like modular ontology design. Recent developments include LLM-based approaches for automated ontology drafting and collaborative engineering, enhancing efficiency in knowledge elicitation and alignment (as of 2025).

Reuse and Integration Techniques

Ontology reuse strategies enable the efficient construction of new ontologies by leveraging existing ones, particularly upper-level or foundational ontologies such as DOLCE (Descriptive Ontology for Linguistic and Cognitive Engineering) and BFO (Basic Formal Ontology), which provide generic conceptual structures applicable across domains. Extension involves adding domain-specific concepts and axioms to an upper ontology while preserving its core structure, allowing for specialization without altering foundational elements. Subsetting, conversely, extracts relevant portions of an upper ontology to focus on a narrower scope, reducing complexity and ensuring alignment with specific requirements. Merging combines multiple upper ontologies or fragments to create a unified representation, often requiring resolution of overlapping concepts to avoid redundancy. These strategies are integral to methodologies like NeOn, which outline scenarios for reusing ontological resources in network-based engineering. Alignment techniques address semantic heterogeneity between ontologies by establishing correspondences between entities, facilitating integration. Entity matching commonly employs string similarity measures, such as Levenshtein distance or Jaro-Winkler, to compare lexical labels and identifiers. Structural analysis extends this by examining relational patterns, like subclass hierarchies or property connections, to infer alignments based on graph isomorphism or subgraph matching. Semantic embedding techniques incorporate external knowledge sources, such as WordNet, to capture contextual meanings through synset mappings and hypernym relations, enhancing accuracy for ambiguous terms. These methods are often combined in hybrid approaches to balance precision and recall, as surveyed in comprehensive ontology matching frameworks. Modularization techniques partition large ontologies into manageable modules to support reuse and maintenance, promoting scalability in engineering processes. Extraction creates modules by selecting subgraphs centered on specific concepts or axioms, ensuring logical consistency through criteria like locality preservation. Pruning removes irrelevant elements from an ontology while retaining core semantics, often guided by relevance metrics to minimize information loss. Merging modules assembles them into a cohesive whole, adhering to principles like ontology double articulation, which ensures bidirectional logical connections between modules without introducing inconsistencies. These partitioning approaches, rooted in formal semantics, enable distributed development and targeted reuse. Tools for ontology integration, such as AgreementMaker, automate mapping tasks by integrating multiple alignment techniques into a unified workflow. AgreementMaker employs a weighted combination of lexical, structural, and semantic matchers to generate entity correspondences, supporting large-scale ontologies through efficient algorithms. Its effectiveness is evaluated using precision (correct mappings among proposed ones) and recall (proposed mappings among true ones) against gold standard references from benchmarks like the Ontology Alignment Evaluation Initiative (OAEI). For instance, AgreementMaker has demonstrated strong performance in OAEI tracks, such as ranking highly in the anatomy task. Challenges in ontology integration arise from heterogeneity in representational choices and axiom structures, complicating seamless merging. Heterogeneity resolution requires reconciling differences in naming conventions, granularity, and modeling paradigms across source ontologies, often demanding manual intervention for ambiguous cases. Conflict detection focuses on identifying inconsistent axioms post-integration, such as contradictory subclass relations or property constraints, using reasoning tools to verify coherence. These issues can propagate errors in downstream applications, underscoring the need for systematic frameworks that prioritize logical consistency during reuse.

Tools and Technologies

Editing and Building Tools

Ontology engineering relies on specialized software environments that facilitate the creation, modification, and maintenance of ontologies, enabling users to define classes, properties, and relationships in a structured manner. These tools typically provide graphical user interfaces (GUIs) to abstract the underlying formalisms, making ontology development accessible to domain experts without deep programming knowledge. Prominent examples include both open-source and commercial platforms that support standards like OWL and RDF, with varying emphases on collaboration, scalability, and integration. Protégé, developed by Stanford University since 2002, is a widely adopted open-source ontology editor that supports OWL 2 and provides extensive plugin architecture for tasks such as visualization of class hierarchies and collaborative editing through WebProtégé. The tool was updated to version 5.6.8 in September 2025, enhancing stability and macOS compatibility. It allows users to build ontologies via intuitive forms for defining axioms, individuals, and annotations, while supporting import and export in formats like OWL/XML and RDF/XML. The tool's plugin ecosystem enables extensions for specific needs, such as diagrammatic representations using tools like OWLviz, enhancing usability for complex ontology structures. TopBraid Composer, an enterprise-grade tool from TopQuadrant, offers advanced editing capabilities for RDF and OWL ontologies, including integrated SPARQL querying and SHACL-based validation to ensure data quality during development. It features a robust GUI for managing large-scale semantic models, with support for modular ontology design and automation through scripting in SPARQL and Java. As part of the TopBraid EDG platform, it emphasizes enterprise deployment, handling interconnected knowledge graphs with high performance. Open-source alternatives include the NeOn Toolkit, a legacy tool from the EU-funded NeOn project (2007–2013) designed for networked ontology development, which supported collaborative workflows across distributed teams and integrated multiple ontology languages like OWL and F-Logic for reuse in modular environments. Another option is VocBench, a web-based editor focused on SKOS vocabularies and OWL ontologies, providing multilingual support for thesaurus management and concept scheme editing in collaborative settings. These tools prioritize accessibility for vocabulary-centric tasks, such as defining skos:Concept hierarchies and broader/narrower relations. Common features across these tools include graphical interfaces for visualizing and editing class hierarchies, asserting properties on instances, and handling relationships like subclassOf or objectPropertyDomain. They support import/export in standard formats such as OWL/XML, Turtle, and RDF/XML, facilitating interoperability with other semantic technologies. Many incorporate version control and diff tools to track changes in ontology evolution. In comparisons, tools like Protégé excel in usability for domain experts due to their intuitive drag-and-drop interfaces and extensive tutorials. Conversely, enterprise tools such as TopBraid Composer demonstrate superior scalability for large ontologies, supporting efficient querying and editing over massive datasets in production environments, though at the cost of a steeper learning curve for non-technical users. Open-source options like NeOn and VocBench balance usability and scalability for collaborative, mid-sized projects, particularly in networked or vocabulary-focused scenarios. These editing tools often serve as front-ends in broader reasoning workflows, where ontologies are loaded into inference engines for consistency checking. Recent advancements include tools leveraging large language models (LLMs) for ontology engineering tasks, such as DeepOnto, a Python package released in 2023 that supports ontology alignment, completion, and other deep learning-based operations.

Reasoning and Validation Tools

Reasoning and validation tools in ontology engineering enable the inference of implicit knowledge from explicit axioms and the assessment of ontology quality through automated analysis. These tools leverage description logics (DLs) underlying languages like OWL to perform tasks such as consistency checking, subsumption computation, and classification, ensuring ontologies are logically sound and free from structural errors. HermiT is a Java-based OWL 2 reasoner employing a hypertableau calculus, a variant of tableau-based algorithms optimized for nondeterministic expansions and model caching to handle OWL DL inferences efficiently. It supports key reasoning services including ontology consistency checking, entailment verification, and class/property classification, often outperforming traditional tableau reasoners on complex ontologies with thousands of axioms. FaCT++ is an open-source C++ reasoner implementing tableau-based procedures for OWL 2 DL, focusing on optimized absorption and automation techniques to compute subsumption hierarchies and detect unsatisfiable concepts. It excels in classification tasks for large-scale ontologies, providing entailment support through modular decomposition of axioms to reduce computational overhead. Pellet serves as a comprehensive OWL 2 DL reasoner with tableau expansion for consistency checking and incremental reasoning capabilities, extending to rule-based inference via integration with SWRL for deriving new facts from horn-like rules alongside DL axioms. This allows validation of ontology coherence while incorporating procedural knowledge, such as deriving class memberships from property assertions. For structural validation, OOPS! (Ontology Pitfall Scanner) automates the detection of common modeling errors in OWL ontologies, including circular hierarchies where cyclic subclass relationships violate acyclic assumptions, as well as inconsistencies like multiple inheritance paths leading to logical paradoxes. It evaluates over 40 pitfalls categorized by severity, providing remediation suggestions based on best practices. OntoMetric facilitates quality assessment through metric computation, measuring aspects like coverage by evaluating the ratio of defined concepts to total entities and relationship density to gauge completeness relative to domain requirements. This tool supports comparative analysis across ontology versions or peers, emphasizing semantic richness without exhaustive enumeration. Performance optimizations in these tools often target tractable DL fragments, such as the OWL 2 EL profile based on EL++, which admits polynomial-time reasoning for subsumption and consistency via completion rules that avoid exponential blowup in existential restrictions and conjunctions. Integration of reasoners into development environments occurs via standardized APIs, such as the OWL API in Protégé, allowing seamless embedding of HermiT or Pellet for on-the-fly inference during ontology authoring without separate invocation. Newer reasoners, such as Whelk (introduced around 2024), support combined OWL EL+RL reasoning, enabling efficient inference for biological and other large-scale ontologies.

Applications

In Life Sciences

Ontology engineering in the life sciences involves developing structured knowledge representations tailored to biomedical and biological domains, facilitating data integration, annotation, and analysis across diverse datasets. These ontologies address the complexity of biological systems by standardizing terminology for genes, proteins, diseases, and clinical concepts, enabling precise querying and inference in research and healthcare applications. Key examples include the Gene Ontology (GO) and SNOMED CT, which exemplify domain-specific adaptations through hierarchical structures and formal axioms. The Gene Ontology (GO), initiated in 1998 by the Gene Ontology Consortium, provides a controlled vocabulary to describe gene and gene product attributes across organisms. It is organized into three independent branches: molecular function, which captures activities such as catalytic or binding activities at the molecular level; biological process, encompassing series of molecular events like signaling or metabolic pathways; and cellular component, denoting locations such as organelles or supramolecular complexes. This structure supports functional annotation of over 1.6 million gene products from 5,495 species (as of October 2025), promoting interoperability in genomic databases. SNOMED CT (Systematized Nomenclature of Medicine—Clinical Terms) serves as a comprehensive clinical terminology ontology designed for healthcare interoperability, representing clinical information such as diagnoses, procedures, and observations. It encompasses over 375,000 unique concepts, organized hierarchically with formal definitions based on description logics, allowing for consistent encoding in electronic health records across more than 80 countries. This scale enables detailed clinical documentation and supports automated decision-making in patient care systems. Engineering approaches in life sciences ontologies emphasize automation and rigor to handle vast biomedical literature and ensure conceptual accuracy. Automated term extraction from scientific texts using natural language processing (NLP) techniques identifies candidate concepts and relations, as seen in pipelines that process PubMed abstracts to populate ontology hierarchies semi-automatically. Quality assurance incorporates logical axioms, such as disjointness constraints, to prevent overlaps between classes—for instance, ensuring that certain cellular components remain mutually exclusive—and detect inconsistencies during ontology maintenance. These methods, including description logic-based checks, enhance the formal validity of ontologies like GO. Recent developments include integration of ontologies with large language models for automated ontology learning and expansion in biomedicine. A prominent case study is the OBO Foundry, a collaborative initiative establishing principles for building orthogonal ontologies in biology that cover distinct domains without redundancy. Core principles include openness for community contributions, orthogonality to minimize overlap (e.g., separating anatomy from phenotype ontologies), and adherence to formal syntax like OWL for interoperability. This framework has coordinated over 100 ontologies, fostering reuse and integration in model organism databases. The impact of these ontologies is evident in enabling semantic queries across large-scale resources, such as UniProt and PubMed. In UniProt, GO annotations allow federated queries to retrieve proteins by function or process, integrating data from multiple species for comparative genomics. Similarly, tools like GO2PUB expand PubMed searches using GO hierarchies, improving retrieval of relevant literature on gene functions through inheritance-based term expansion. Methodologies like METHONTOLOGY have been adapted for bio-ontologies to guide specification and evaluation phases.

In Semantic Web and Knowledge Graphs

Ontology engineering plays a pivotal role in the Semantic Web by providing the schema layer that structures RDF data, enabling the principles of Linked Data through standardized vocabularies like RDFS and OWL. These ontologies define classes, properties, and relationships, allowing machines to interpret and infer new knowledge from distributed datasets represented as triples (subject-predicate-object). For example, RDFS extends RDF with basic schema elements such as rdfs:subClassOf for hierarchical organization, while OWL adds advanced constructs like owl:TransitiveProperty to support complex reasoning and entailment over web-scale data. This formalization facilitates the interlinking of datasets, promoting a web of machine-readable information where inference engines can derive implicit facts, such as subclass relationships or property domains, from explicit RDF statements. In knowledge graphs, ontology engineering involves designing schemas to integrate and populate vast, heterogeneous data sources, often drawing from unstructured text. DBpedia exemplifies this approach, where a crowd-sourced ontology with 768 classes and over 3,000 properties serves as the schema for extracting structured entities and relations from Wikipedia articles and infoboxes using natural language processing techniques. The extraction process populates the graph with billions of RDF triples (approximately 9.5 billion), enabling queries via SPARQL and linking to other Linked Open Data resources. Similarly, the Google Knowledge Graph leverages ontology-inspired schemas, incorporating types from schema.org to organize entities like people, places, and events extracted from web sources, enhancing search results with contextual inferences. Key techniques in this domain include lightweight ontologies for broad applicability and extensions for specialized dimensions. Schema.org, developed collaboratively by major search engines, functions as a lightweight ontology with over 800 types and 1,500 properties, allowing web publishers to annotate content using simple markup formats like JSON-LD or RDFa without heavy formal semantics. This approach supports rapid schema design for everyday web data, focusing on core domains such as CreativeWork and Organization to improve discoverability. For more advanced needs, YAGO incorporates temporal and spatial extensions into its ontology, anchoring facts to time intervals and geographic coordinates extracted from Wikipedia and GeoNames, resulting in a knowledge base with approximately 49 million entities and 109 million facts (as of 2024). A prominent case study is Wikidata, which employs an upper-level ontology to integrate structured data across Wikipedia's multilingual articles, representing knowledge as semantic triples with items, properties, and values. This ontology enables the reconciliation of diverse sources, supporting complex queries like lineage tracing or population statistics, and serves over 119 million entities (as of August 2025) through APIs compatible with Semantic Web tools. By centralizing structured data from Wikimedia projects, Wikidata facilitates cross-language data federation, allowing inferences that bridge linguistic and cultural gaps in global knowledge representation. Recent trends include enhanced use of Wikidata in AI-driven knowledge graphs for real-time data integration. The application of ontologies in knowledge graphs yields significant benefits, particularly in enhancing search precision, recommendation systems, and data federation. In search engines, ontological schemas enable semantic matching beyond keywords, delivering contextually relevant results—such as disambiguating entities via types and relations—which improves user experience in platforms like Google Search. For recommendations, the structured relationships in graphs power personalized suggestions in e-commerce, like Amazon's product graphs, by inferring user preferences through entity linkages. Data federation across silos is streamlined, as ontologies provide a common schema for integrating disparate sources in social platforms, reducing redundancy and enabling scalable analytics without proprietary data movement.

Key Challenges

Ontology engineering faces several persistent technical and practical obstacles that hinder the development and deployment of effective knowledge representations. These challenges span from computational limitations to socio-technical issues, impacting the reliability and adoption of ontologies in diverse domains. Addressing them requires a balance between theoretical rigor and practical implementation, often leveraging automated tools for partial mitigation. Scalability remains a core issue in ontology engineering, particularly when handling large-scale ontologies comprising millions of concepts and relations. For instance, reasoning over ontologies expressed in expressive description logics (DLs), such as SHOIN(D), incurs exponential time complexity due to the inherent computational demands of satisfiability checking and inference tasks, which can become prohibitive for real-world applications with vast axiom sets. In domains like healthcare, where ontologies must integrate massive datasets from genomics and electronic health records, static structures struggle to scale efficiently, necessitating modular designs to manage growing data volumes while preserving performance. Biomedical ontologies, such as the Gene Ontology with 39,354 terms (as of October 2025), exemplify this, where continuous integration pipelines are employed to handle interdependencies, yet full reasoning remains resource-intensive. Interoperability barriers arise from semantic drift and vocabulary mismatches, complicating the alignment and integration of ontologies across domains. Semantic drift occurs as concepts evolve over ontology versions, leading to gradual shifts in meaning that undermine mappings and reuse; for example, changes in concept extensions or intentions can result in up to 25-31% term overlap but less than 9% actual reuse in biomedical contexts. These mismatches manifest in hierarchical misalignments and terminological heterogeneity, as seen in standards like SNOMED CT and HL7 FHIR, where disparate representations of the same domain knowledge impede seamless data exchange without extensive manual reconciliation. Automated alignment techniques, while helpful, often fail to fully resolve these drifts, exacerbating silos in multi-ontology environments. Maintenance overhead poses significant challenges due to the dynamic nature of domains, requiring ontologies to evolve in response to new knowledge or requirements while minimizing disruption. Ontology evolution involves detecting changes from sources like usage logs or external corpora, suggesting modifications, validating them for consistency, and assessing impacts on dependent systems—a process that is resource-intensive and lacks standardized change languages, leading to high manual effort. In practice, tools like Protégé facilitate versioning, but propagating updates across modular or distributed ontologies incurs substantial storage and communication costs, particularly when ensuring backward compatibility with applications and queries. This overhead deters widespread adoption, as seen in Semantic Web projects where fragmented evolution strategies increase long-term costs without automated mechanisms for propagation. Quality assurance in ontology engineering is complicated by the need to detect redundancies, inconsistencies, and incompleteness without relying solely on exhaustive manual reviews. Redundant hierarchical relations, such as multiple paths between concepts in is-a structures, can inflate ontology size and degrade inference accuracy; for example, the SNOMED CT ontology contains hundreds of such redundancies that automated tools like FEDRR can identify in seconds using dynamic programming. Inconsistencies, including logical contradictions from evolving axioms, further compromise trustworthiness, with reasoners providing partial automated detection but struggling at scale due to DL complexity. Incompleteness assessments remain subjective, often requiring domain-specific metrics to evaluate coverage, yet current methods fall short of comprehensive validation, leading to persistent quality gaps in large ontologies like the Gene Ontology. Human factors introduce additional hurdles, particularly in balancing ontology expressivity with usability for non-experts in collaborative settings. The steep learning curve of formalisms like OWL and tools like Protégé alienates domain specialists without technical backgrounds, resulting in modeling errors and low adoption rates in team-based development. Collaborative ontology engineering demands intuitive interfaces for non-experts to contribute without deep semantic knowledge, yet existing methodologies often prioritize expressivity over accessibility, leading to usability issues such as cumbersome annotation processes and poor support for iterative feedback. In distributed environments, these factors amplify coordination challenges, where mismatched expertise levels hinder consensus on concept definitions and alignments. Reasoners and simpler design patterns offer some mitigation by automating consistency checks, allowing focus on conceptual contributions.

Emerging Developments

Recent advancements in ontology engineering have increasingly incorporated large language models (LLMs) for automated ontology learning, enabling the extraction of concepts, relations, and axioms from unstructured text sources. A notable example is the NeOn-GPT pipeline, introduced in 2024, which integrates the structured NeOn methodology with LLMs to translate natural language descriptions into formal ontology representations, facilitating semi-automated schema generation and reducing manual effort in domain-specific ontology development. This approach was highlighted in the LLMs4OL 2024 challenge, the first dedicated evaluation of LLMs for ontology learning tasks, demonstrating improved accuracy in concept extraction from diverse datasets compared to traditional rule-based methods. This progress continued with the second LLMs4OL challenge at ISWC 2025, further evaluating LLMs for ontology learning tasks. Hybrid approaches combining ontologies with graph neural networks (GNNs) have emerged to support dynamic knowledge graphs, allowing for real-time updates and inference over evolving data structures. For instance, neuro-symbolic frameworks leverage GNNs for embedding learning while preserving ontological constraints, enabling scalable reasoning in enterprise knowledge graphs without sacrificing interpretability. These methods address scalability challenges by iteratively refining graph representations through symbolic reasoning, as seen in approaches like ReasonKGE, which corrects inconsistent predictions in knowledge graph embeddings. Advances in ontology modularization have benefited from AI-assisted alignment techniques using embeddings, particularly post-2020 developments with models like BERT. The BERTMap system, for example, fine-tunes BERT on textual ontology elements to predict entity matches in both unsupervised and semi-supervised settings, achieving higher precision in aligning large-scale ontologies than classical string-based matchers. This embedding-driven modularization supports the decomposition and reuse of ontology components, enhancing interoperability in distributed systems. Emerging trends include ontology-based explainable AI (XAI), where ontologies provide structured vocabularies to generate human-interpretable explanations for AI decisions. Ontologies serve multiple roles in XAI, such as defining explanation scopes and anchoring post-hoc interpretations to domain knowledge, as explored in surveys on semantic-based XAI applications in manufacturing. Additionally, federated learning integrated with ontologies enables privacy-preserving knowledge sharing by aligning distributed models through shared ontological schemas without exchanging raw data. Frameworks like ontology-guided federated unlearning use knowledge distillation to remove sensitive information while maintaining model utility across institutions. Recent milestones from the ESWC 2024 conference underscore LLM pipelines for ontology engineering, including end-to-end workflows for automated term extraction and axiom generation. Furthermore, integrations with vector databases enhance semantic search over ontological knowledge graphs by combining graph traversals with vector similarity queries, as in hybrid RAG systems that boost retrieval accuracy for complex queries.

References

  1. https://people.cs.uct.ac.za/~mkeet/files/OEbook.pdf
  2. https://tomgruber.org/writing/definition-of-ontology.pdf
  3. https://www.semantic-web-journal.net/system/files/swj2313.pdf
  4. https://www.w3.org/TR/owl2-overview/
  5. https://www.obofoundry.org/
  6. https://www.wikidata.org/wiki/Wikidata:Statistics
  7. https://lod-cloud.net/dataset/dbpedia
  8. https://www.iso.org/standard/85100.html
  9. https://www.semantic-web-journal.net/system/files/swj3864.pdf
  10. https://www.w3.org/TR/owl2-syntax/
  11. https://plato.stanford.edu/entries/aristotle-categories/
  12. https://rintintin.colorado.edu/~vancecd/phil375/Quine.pdf
  13. https://dl.acm.org/doi/10.1145/219717.219745
  14. https://tomgruber.org/writing/ontolingua-kaj-1993.pdf
  15. https://onlinelibrary.wiley.com/doi/10.1609/aimag.v41i2.5295
  16. https://www.w3.org/TR/owl-features/
  17. http://geneontology.org/docs/introduction-to-go
  18. https://inria.hal.science/inria-00072192/document
  19. https://www.w3.org/TR/rdf11-concepts/
  20. https://www.w3.org/TR/owl2-profiles/
  21. https://www.iso.org/standard/66249.html
  22. http://logic.stanford.edu/publications/genesereth/kif.pdf
  23. https://www3.cs.stonybrook.edu/~kifer/TechReports/ontologies-rules-flogic.pdf
  24. https://www.w3.org/OWL/
  25. https://obofoundry.org/
  26. https://www.w3.org/TR/turtle/
  27. https://www.w3.org/TR/n-triples/
  28. https://www.w3.org/TR/owl2-direct-semantics/
  29. https://www.w3.org/TR/owl2-rdf-based-semantics/
  30. https://www.inf.unibz.it/~franconi/dl/course/dlhb/dlhb-02.pdf
  31. https://www.sciencedirect.com/topics/computer-science/description-logics
  32. https://www.cs.ox.ac.uk/people/ian.horrocks/Publications/download/2005/Horr05c.pdf
  33. https://lat.inf.tu-dresden.de/~baader/Talks/Tableaux2000.pdf
  34. https://www.sciencedirect.com/science/article/pii/S1571066107002393
  35. https://www.researchgate.net/publication/2454779_Temporal_Description_Logics
  36. https://arxiv.org/abs/1302.6817
  37. https://www.cosc.brocku.ca/Faculty/Winter/JoRMiCS/Vol1/PDF/v1n11.pdf
  38. https://oa.upm.es/5484/1/METHONTOLOGY_.pdf
  39. https://aaai.org/papers/0005-ss97-06-005-methontology-from-ontological-art-towards-ontological-engineering/
  40. https://oeg.fi.upm.es/index.php/en/completedprojects/8-neon/index.html
  41. https://www.iospress.com/node15242/books/neon-methodology-for-building-ontology-networks-specification-scheduling-and-reuse
  42. https://protege.stanford.edu/publications/ontology_development/ontology101.pdf
  43. https://nemo.inf.ufes.br/wp-content/papercite-data/pdf/use_of_competency_questions_in_ontology_engineering__a_survey_2023.pdf
  44. https://oa.upm.es/5480/1/Overview_Of_Methodologies.pdf
  45. https://www.frontiersin.org/journals/big-data/articles/10.3389/fdata.2025.1676477/full
  46. https://www.semantic-web-journal.net/system/files/swj2650.pdf
  47. https://www.researchgate.net/publication/225197394_The_Use_of_Foundational_Ontologies_in_Ontology_Development_An_Empirical_Assessment
  48. https://www.mitre.org/sites/default/files/pdf/04_1175.pdf
  49. https://www.scitepress.org/Papers/2014/50271/50271.pdf
  50. https://www.researchgate.net/publication/49911337_NeOn_Methodology_for_Building_Ontology_Networks_a_Scenario-based_Methodology
  51. https://www.mecs-press.org/ijmecs/ijmecs-v7-n11/IJMECS-V7-N11-8.pdf
  52. https://www.researchgate.net/publication/358843439_A_Review_on_Ontology_Modularization_Techniques_-_A_Multi-Dimensional_Perspective
  53. https://pmc.ncbi.nlm.nih.gov/articles/PMC3101570/
  54. https://research-archive.stem.open.ac.uk/stemra-data/uploads/sites/136/2025/03/Chapter-15.pdf
  55. http://www.vldb.org/pvldb/vol2/vldb09-1003.pdf
  56. https://www.researchgate.net/publication/221466014_Using_AgreementMaker_to_align_ontologies_for_OAEI_2010
  57. https://hal.science/hal-03136348v1/document
  58. https://pmc.ncbi.nlm.nih.gov/articles/PMC8352153/
  59. https://jbiomedsem.biomedcentral.com/articles/10.1186/s13326-021-00246-0
  60. https://protege.stanford.edu/
  61. https://research-archive.stem.open.ac.uk/neon-toolkit/
  62. https://protege.stanford.edu/software.php
  63. https://topbraidcomposer.org/html/What_is_TopBraid_Composer.htm
  64. https://www.topquadrant.com/
  65. https://vocbench.uniroma2.it/
  66. https://topbraidcomposer.org/html/
  67. https://www.researchgate.net/publication/311100273_Comparison_of_Ontology_Editors
  68. https://www.semantic-web-journal.net/content/deeponto-python-package-ontology-engineering-deep-learning-0
  69. http://www.cs.ox.ac.uk/boris.motik/pubs/hmw12HermiT.pdf
  70. https://ceur-ws.org/Vol-432/owled2008eu_submission_12.pdf
  71. http://owl.cs.manchester.ac.uk/tools/list-of-reasoners/
  72. http://www.cs.ox.ac.uk/people/bernardo.cuencagrau/publications/PelletDemo.pdf
  73. https://github.com/stardog-union/pellet
  74. https://www.semantic-web-journal.net/system/files/swj989.pdf
  75. https://ceur-ws.org/Vol-1684/paper19.pdf
  76. https://lat.inf.tu-dresden.de/research/papers/2004/Brandt-ECAI-2004.pdf
  77. https://protegewiki.stanford.edu/wiki/ProtegeReasonerAPI
  78. https://drops.dagstuhl.de/entities/document/10.4230/TGDK.2.2.7
  79. https://www.nature.com/articles/ng0500_25
  80. http://geneontology.org/
  81. https://www.snomed.org/what-is-snomed-ct
  82. https://bioportal.bioontology.org/ontologies/SNOMEDCT
  83. https://pmc.ncbi.nlm.nih.gov/articles/PMC2990796/
  84. https://pmc.ncbi.nlm.nih.gov/articles/PMC3900201/
  85. http://obofoundry.org/principles/fp-010-collaboration.html
  86. http://obofoundry.org/
  87. https://pmc.ncbi.nlm.nih.gov/articles/PMC3531094/
  88. https://pmc.ncbi.nlm.nih.gov/articles/PMC3599846/
  89. https://www.worldscientific.com/doi/full/10.1142/S0219649222500563
  90. https://aidanhogan.com/docs/ldmgmt.pdf
  91. https://www.sciencedirect.com/science/article/pii/B9780127999579000031
  92. https://www.dbpedia.org/
  93. https://link.springer.com/chapter/10.1007/978-3-540-76298-0_52
  94. https://developers.google.com/knowledge-graph
  95. https://schema.org/docs/schemas.html
  96. https://yago-knowledge.org/downloads/yago-4-5
  97. https://journals.sagepub.com/doi/10.1177/20563051231195552
  98. https://www.ontotext.com/blog/knowledge-graphs-101-the-story-and-benefits-behind-the-hype/
  99. https://www.inf.unibz.it/~calvanese/teaching/11-12-kro/lecture-notes/KRO-2-dls.pdf
  100. https://www.frontiersin.org/journals/digital-health/articles/10.3389/fdgth.2025.1668385/full
  101. https://semantic-web-journal.net/system/files/swj2252.pdf
  102. http://geneontology.org/stats.html
  103. https://www.sciencedirect.com/science/article/abs/pii/S1570826818300258
  104. https://www.researchgate.net/publication/256649114_Ontology_evolution_A_process-centric_survey
  105. https://pmc.ncbi.nlm.nih.gov/articles/PMC5057496/
  106. https://www.researchgate.net/publication/233944481_Collaborative_Ontology_Engineering_A_Survey
  107. https://www.researchgate.net/publication/232118222_Semantic_Enrichment_by_Non-Experts_Usability_of_Manual_Annotation_Tools
  108. https://2024.eswc-conferences.org/wp-content/uploads/2024/05/77770034.pdf
  109. https://arxiv.org/html/2409.10146v1
  110. https://www.nfdi4datascience.de/news/2025/202505_llms4ol/
  111. https://ceur-ws.org/Vol-3659/IJCKG_2023_WS2.pdf
  112. https://www.techrxiv.org/doi/full/10.36227/techrxiv.175303720.01590298/v1
  113. https://dl.acm.org/doi/10.1007/978-3-030-88361-4_24
  114. https://www.researchgate.net/publication/361774593_BERTMap_A_BERT-Based_Ontology_Alignment_System
  115. https://www.researchgate.net/publication/376262293_On_the_Multiple_Roles_of_Ontologies_in_Explainable_AI
  116. https://dl.acm.org/doi/10.1007/s10845-023-02304-z
  117. https://asmedigitalcollection.asme.org/computingengineering/article/25/1/011006/1208542/Ontology-Guided-Data-Sharing-and-Federated-Quality
  118. https://www.mdpi.com/1999-5903/17/8/335
  119. https://arxiv.org/html/2408.04948v1
Add your contribution
Related Hubs
User Avatar
No comments yet.