Ontology(IT): Difference between revisions
Ontolog Forum
(__TOC__) |
(TOC and headers done) |
||
| Line 1: | Line 1: | ||
This document is a collection of definitions from different sources. | This document is a collection of definitions from different sources. | ||
AND MUST BE MOVED TO [https://ontologforum.com/index.php/Ontology(IT) <u>https://ontologforum.com/index.php/Ontology(IT)</u>] | |||
'''DiU''' - definition is unattainable. This means we have a URL to the source description, but not the definition itself! | '''DiU''' - definition is unattainable. This means we have a URL to the source description, but not the definition itself! | ||
| Line 9: | Line 11: | ||
'''PID''' - person ID. There are two person roles: presenting his own definition xor presenting a reference to the source of the definition. | '''PID''' - person ID. There are two person roles: presenting his own definition xor presenting a reference to the source of the definition. | ||
'''bref''' - bibliographic reference. If not full, it keeps "???". | |||
Every definition has a unique ID and is a separate unit of knowledge. If the definition is personal, | Every definition has a unique ID and is a separate unit of knowledge. If the definition is personal, "!" follows after the ID. | ||
If there is no direct link to the source in the form of a URL, the ID of the person who provided the definition is provided to ask. If the person created the definition himself, the definition's ID is followed by | If there is no direct link to the source in the form of a URL, the ID of the person who provided the definition is provided to ask. If the person created the definition himself, the definition's ID is followed by "!". | ||
End letter | End letter "G" in definition ID means that the definition is IN GENERAL i.e. not only for IT. | ||
'''General abbr''' | '''General abbr''' | ||
| Line 23: | Line 25: | ||
__TOC__ | __TOC__ | ||
== goto == | |||
Collector, please visit: | Collector, please visit: | ||
| Line 29: | Line 31: | ||
-DOL, TLO | -DOL, TLO | ||
-every onto language or family: DL, OWL2, CL, [http://hets.eu/ hets.eu] | -every onto language or family: DL, OWL2, CL, [http://hets.eu/ <u>hets.eu</u>] | ||
Points has been visited see [https://docs.google.com/document/d/1N6vKV2FUly17U-gS7Sgzc67BxZUZz7h7mr6GJC9KexU/edit?tab=t.0#heading=h.jdhizuclqahi IT-ontology DEFINITIONs] | Points has been visited see [https://docs.google.com/document/d/1N6vKV2FUly17U-gS7Sgzc67BxZUZz7h7mr6GJC9KexU/edit?tab=t.0#heading=h.jdhizuclqahi <u>IT-ontology DEFINITIONs</u>] | ||
<span id="rules-to-keep-collection-and-discussion"></span> | |||
== Rules to keep collection and discussion == | |||
see [https://docs.google.com/document/d/1LbLgXo02Qc5UBK29wDYRpbnTCQwfnQ9ZHikU_KDZFro/edit?tab=t.0 DEFINITIONs. rules & tasks] | see [https://docs.google.com/document/d/1LbLgXo02Qc5UBK29wDYRpbnTCQwfnQ9ZHikU_KDZFro/edit?tab=t.0 <u>DEFINITIONs. rules & tasks</u>] | ||
<span id="distinguishing-properties"></span> | |||
== Distinguishing properties == | |||
Here we collect various ways to distinguish whether a KB is an ontology. And any useful ideas. | Here we collect various ways to distinguish whether a KB is an ontology. And any useful ideas. | ||
<span | <span id="version1ja2"></span> | ||
=== +$+VERSION#1(JA)[https://groups.google.com/d/msgid/ontolog-forum/CAG%3D%3DwTdnUH7L9PRKyDcKAchQU1V1_Hcth1G8%2BXt-rfL%3DZtdFfg@mail.gmail.com?utm_medium=email&utm_source=footer <u>2</u>] === | |||
9. Reiterating criteria clearly | 9. Reiterating criteria clearly | ||
Based on ISO and ontology engineering literature, we can state: | |||
A knowledge base becomes an ontology when: | |||
<ol style="list-style-type: decimal;"> | |||
<li></li> | |||
<li><blockquote><p>Its vocabulary explicitly defines domain classes and relations (Gruber 1993; Studer et al. 1998).</p></blockquote></li> | |||
<li><blockquote><p>Its assertions are intended as domain axioms expressing ontological commitment (Guarino 1998).</p></blockquote></li> | |||
<li><blockquote><p>The representation language has formal declarative semantics independent of execution strategy (Tarski 1956; OWL 2 Direct Semantics 2012).</p></blockquote></li> | |||
<li><blockquote><p>Inference derives from logical consequence under that semantics (Baader et al. 2003).</p></blockquote></li></ol> | |||
< | That does not require Hermit.<br /> | ||
It does not exclude Prolog.<br /> | |||
It does require logical formalization. | |||
< | The disagreement here is not about ISO being wrong.<br /> | ||
It is about ISO defining a superset category. | |||
Ontology, in the semantic-technology sense, is a stricter subclass of knowledge base. | |||
<span id="related-terms"></span> | |||
== related terms == | |||
=== conceptualization === | |||
"A body of formally represented knowledge is based on a conceptualization: the objects, concepts, and other entities that are presumed to exist in some area of interest and the relationships that hold them (Genesereth & Nilsson, 1987). A conceptualization is an abstract, simplified view of the world that we wish to represent for some purpose. Every knowledge base, knowledge-based system, or knowledge-level agent is committed to some conceptualization, explicitly or implicitly." [https://www.researchgate.net/publication/285158664_A_Translation_Approach_to_Formal_Ontologies <u>TG</u>] | |||
<span id="formal-language"></span> | |||
=== formal language === | |||
AS: Chris Mungall has ontology on Python. Some Prolog programs are not ontology. | AS: Chris Mungall has ontology on Python. Some Prolog programs are not ontology. | ||
<span id="formal-vocabulary"></span> | |||
=== formal vocabulary === | |||
see in [https://docs.google.com/document/d/1N6vKV2FUly17U-gS7Sgzc67BxZUZz7h7mr6GJC9KexU/edit?tab=t.0#heading=h.6miig72wu0rq IT-ontology DEFINITIONs] | see in [https://docs.google.com/document/d/1N6vKV2FUly17U-gS7Sgzc67BxZUZz7h7mr6GJC9KexU/edit?tab=t.0#heading=h.6miig72wu0rq <u>IT-ontology DEFINITIONs</u>] | ||
=== model === | |||
see in [https://docs.google.com/document/d/1N6vKV2FUly17U-gS7Sgzc67BxZUZz7h7mr6GJC9KexU/edit?tab=t.0#heading=h.6miig72wu0rq IT-ontology DEFINITIONs] | see in [https://docs.google.com/document/d/1N6vKV2FUly17U-gS7Sgzc67BxZUZz7h7mr6GJC9KexU/edit?tab=t.0#heading=h.6miig72wu0rq <u>IT-ontology DEFINITIONs</u>] | ||
<span id="ontological-commitment"></span> | |||
=== ontological commitment === | |||
see in [https://docs.google.com/document/d/1N6vKV2FUly17U-gS7Sgzc67BxZUZz7h7mr6GJC9KexU/edit?tab=t.0#heading=h.6miig72wu0rq IT-ontology DEFINITIONs] | see in [https://docs.google.com/document/d/1N6vKV2FUly17U-gS7Sgzc67BxZUZz7h7mr6GJC9KexU/edit?tab=t.0#heading=h.6miig72wu0rq <u>IT-ontology DEFINITIONs</u>] | ||
=== theory === | |||
, logical see in [https://docs.google.com/document/d/1N6vKV2FUly17U-gS7Sgzc67BxZUZz7h7mr6GJC9KexU/edit?tab=t.0#heading=h.6miig72wu0rq IT-ontology DEFINITIONs] | , logical see in [https://docs.google.com/document/d/1N6vKV2FUly17U-gS7Sgzc67BxZUZz7h7mr6GJC9KexU/edit?tab=t.0#heading=h.6miig72wu0rq <u>IT-ontology DEFINITIONs</u>] | ||
<span id="discussion"></span> | |||
== DISCUSSION == | |||
<span id="ja2-it-ontology-intended-to"></span> | |||
=== (JA)[https://groups.google.com/g/ontolog-forum/c/x_WyrRsN7Q4/m/idjVyyQyAQAJ <u>2</u>] IT-ontology intended to… === | |||
3. On Contradiction and Completeness | 3. On Contradiction and Completeness | ||
You raise an important philosophical question: | |||
< | <blockquote>Is the IT-ontology complete and non-contradictory knowledge about the domain? | ||
</blockquote> | |||
My answer is: no. | |||
An IT-ontology is not complete knowledge. It is not guaranteed consistent in practice. It is not a total theory of a domain. | |||
It is a '''formalized conceptual model''' intended to: | |||
< | <ul> | ||
<li><blockquote><p>Constrain interpretation,</p></blockquote></li> | |||
<li><blockquote><p>Enable logical consequence,</p></blockquote></li> | |||
<li><blockquote><p>Make commitments explicit.</p></blockquote></li></ul> | |||
It may be incomplete.<br /> | |||
It may contain modeling errors.<br /> | |||
It may require revision. | |||
So I would not define IT-ontology as “complete knowledge.” | |||
I would define it as: | |||
< | <blockquote>A formally specified conceptualization expressed in a representation language with explicit semantics. | ||
</blockquote> | |||
It is closer to a theory schema than to a complete theory. | |||
Your formulation — “a theory or model for theory” — is actually very close to how ontology engineers think about it. | |||
< | <span id="ja1-topics-around"></span> | ||
=== (JA)[https://groups.google.com/d/msgid/ontolog-forum/CAG%3D%3DwTdnUH7L9PRKyDcKAchQU1V1_Hcth1G8%2BXt-rfL%3DZtdFfg@mail.gmail.com?utm_medium=email&utm_source=footer <u>1</u>] topics around === | |||
"That is why ontology engineers distinguish: | |||
< | <ul> | ||
<li><blockquote><p>Vocabulary (classes, properties)</p></blockquote></li> | |||
<li><blockquote><p>Axioms (subsumption, equivalence, restrictions)</p></blockquote></li> | |||
<li><blockquote><p>Rules (SWRL, production rules, etc.)</p></blockquote></li></ul> | |||
They are not the same category. | |||
'''( | <ul> | ||
<li><blockquote><p>Baader et al., ''The Description Logic Handbook'' (2003), distinguish TBox (terminological axioms: classes, subsumption, properties) from ABox (assertions about individuals), and separate these from rule systems.</p></blockquote></li></ul> | |||
< | <ul> | ||
<li><blockquote><p>The W3C OWL 2 Structural Specification (2012) clearly distinguishes class axioms and property axioms from rule extensions such as SWRL.</p></blockquote></li></ul> | |||
" | |||
"So ontology status does not depend on Hermit accessibility. | |||
It depends on whether the representation language has well-defined declarative semantics. | |||
<ul> | |||
<li><blockquote><p>The OWL 2 Direct Semantics (W3C Recommendation, 2012) provides a model-theoretic semantics independent of any specific reasoner.</p></blockquote></li> | |||
<li><blockquote><p>Description logic semantics are formally defined in Baader et al. (2003).</p></blockquote></li></ul> | |||
<ul> | |||
<li><blockquote><p>The model-theoretic tradition originates with Tarski (1956), ''Logic, Semantics, Metamathematics''.</p></blockquote></li></ul> | |||
" | |||
"Some Prolog KBs can function as ontologies. | |||
But many do not. | |||
Why? Because they often: | |||
<ul> | |||
<li><blockquote><p>Mix domain knowledge with control strategy</p></blockquote></li> | |||
<li><blockquote><p>Use procedural constructs (cuts, ordering effects)</p></blockquote></li> | |||
<li><blockquote><p>Lack explicit ontological commitments (identity criteria, typing discipline, subsumption structure)</p></blockquote></li></ul> | |||
A clean, purely declarative first-order theory encoded in Prolog syntax could absolutely count as an ontology. | |||
A heuristic expert system implemented in Prolog typically would not. | |||
< | So the issue is not “Prolog vs OWL.”<br /> | ||
It is declarative domain theory vs procedural problem-solving system. | |||
< | <ul> | ||
<li><blockquote><p>Mix domain knowledge with control strategy (Lloyd 1987).</p></blockquote></li> | |||
<li><blockquote><p>Depend on operational features such as ordering and cut (Kowalski 1979).</p></blockquote></li></ul> | |||
Lack explicit ontological commitments in the sense articulated by Guarino (1998). | |||
" | |||
"So again, the distinction hinges on logical formalization, not file format. | |||
Hets (Mossakowski, Maeder & Lüttich, 2007, TACAS) is grounded in institution theory (Goguen & Burstall, 1992 | |||
" | |||
"An ontology in IT is a formal artifact with explicit semantics. | |||
A conceptual model written in English may describe an ontology.<br /> | |||
It is not an ontology artifact until formalized. | |||
This is the same distinction between: | |||
<ul> | |||
<li><blockquote><p>Mathematical truth</p></blockquote></li> | |||
<li><blockquote><p>A formal proof in a specified logical system</p></blockquote></li></ul> | |||
Ontology engineering operates in the latter space. | |||
< | <ul> | ||
<li><blockquote><p>Noy & McGuinness (2001), ''Ontology Development 101'', emphasize formal class and property specification.</p></blockquote></li></ul> | |||
< | <ul> | ||
<li><blockquote><p>Smith (2003), “Ontology,” in ''Blackwell Guide to the Philosophy of Computing and Information'', distinguishes philosophical ontology from computational ontology artifacts.</p></blockquote></li></ul> | |||
" | |||
< | <span id="classification-notes"></span> | ||
=== Classification notes === | |||
< | <span id="consolidated-decision-base-definition-for-it-ontology"></span> | ||
=== Consolidated Decision: Base Definition for IT-ontology === | |||
(AS)Starter: formal ontology is a [https://docs.google.com/document/d/19gzOI6eiFgYcOBkmWNEE1iyov5gQejwqaAdXu9siT3g/edit?tab=t.0 <u>KB</u>] where knowledge is fully structured and formalized as much as possible. | |||
< | <span id="ja-ontology-is-a-knowledge-base-but-not-every-knowledge-base-is-an-ontology"></span> | ||
=== (JA) “Ontology is a knowledge base, but not every knowledge base is an ontology” === | |||
[https://groups.google.com/d/msgid/ontolog-forum/CAG%3D%3DwTdnUH7L9PRKyDcKAchQU1V1_Hcth1G8%2BXt-rfL%3DZtdFfg@mail.gmail.com?utm_medium=email&utm_source=footer <u>URL</u>] <'''AS''':text has hints to definition sources> | |||
This is not a rhetorical move. It is a distinction established in the ontology engineering community. | |||
The differentiator is not: | |||
<ul> | |||
<li><blockquote><p>Whether inference occurs</p></blockquote></li> | |||
<li><blockquote><p>Whether rules exist</p></blockquote></li> | |||
<li><blockquote><p>Whether a reasoner like Hermit can process it</p></blockquote></li></ul> | |||
The differentiator is whether the artifact is a formal specification of a conceptualization, not merely a rule-based problem-solving system. | |||
This distinction appears in: | |||
< | <ul> | ||
<li><blockquote><p>Gruber (1993)</p></blockquote></li> | |||
<li><blockquote><p>Guarino (1998)</p></blockquote></li> | |||
<li><blockquote><p>Studer, Benjamins & Fensel (1998)</p></blockquote></li> | |||
<li><blockquote><p>The W3C OWL specifications</p></blockquote></li></ul> | |||
The key issue is ontological commitment, not computational accessibility. | |||
<ul> | |||
<li><blockquote><p>Gruber (1993), “A Translation Approach to Portable Ontology Specifications,” ''Knowledge Acquisition''.</p></blockquote></li> | |||
<li><blockquote><p>Studer, Benjamins & Fensel (1998), “Knowledge Engineering: Principles and Methods,” ''Data & Knowledge Engineering''.</p></blockquote></li></ul> | |||
<ul> | |||
<li><blockquote><p>Guarino (1998), “Formal Ontology in Information Systems,” FOIS 1998.</p></blockquote></li></ul> | |||
<span id="collection"></span> | |||
== COLLECTION == | |||
<span id="grb93"></span> | |||
=== GRB93 === | |||
An ontology is an explicit specification of a conceptualization. | An ontology is an explicit specification of a conceptualization. | ||
[https://tomgruber.org/writing/ontolingua-kaj-1993/ URL] '''PID''':TG '''bref''':Thomas R. Gruber. A Translation Approach to Portable Ontology Specifications. Knowledge Acquisition, 5(2):199-220, 1993. | [https://tomgruber.org/writing/ontolingua-kaj-1993/ '''<u>URL</u>'''] '''PID''':TG '''bref''':Thomas R. Gruber. A Translation Approach to Portable Ontology Specifications. Knowledge Acquisition, 5(2):199-220, 1993. | ||
<span id="js2000"></span> | |||
=== JS2000 === | |||
A catalog of the types of things that are assumed to exist in a domain of interest D from the perspective of a person who uses a language L for the purpose of talking about [the domain] D. | A catalog of the types of things that are assumed to exist in a domain of interest D from the perspective of a person who uses a language L for the purpose of talking about [the domain] D. | ||
'''URL''': | '''URL''':??? '''PID''':[[#js-john-sowa|<u>JS</u>]] '''bref''': John F. Sowa, "Knowledge Representation - Logical, Philosophical, and Computational Foundations", 2000, P.492. | ||
< | <span id="comments"></span> | ||
==== Comments ==== | |||
AS:from [https://wiki.iaoa.org/index.php/Edu:Ontology IAOAcat][4] | AS:from [https://wiki.iaoa.org/index.php/Edu:Ontology <u>IAOAcat</u>][4] | ||
<span id="bl04"></span> | |||
=== BL04 === | |||
The catalogue of concepts (constants, relations, functions, etc.) used to represent knowledge about a problem domain. | The catalogue of concepts (constants, relations, functions, etc.) used to represent knowledge about a problem domain. | ||
'''URL''': | '''URL''':??? '''PID''':NA '''bref''': (p.44, "KNOWLEDGE REPRESENTATION AND REASONING" by Ronald J. Brachman and Hector J. Levesque (2004)) | ||
< | <span id="comments-1"></span> | ||
==== Comments ==== | |||
AS:from [https://wiki.iaoa.org/index.php/Edu:Ontology IAOAcat][5] | AS:from [https://wiki.iaoa.org/index.php/Edu:Ontology <u>IAOAcat</u>][5] | ||
<span id="sksc06"></span> | |||
=== SKSC06 === | |||
An ontology is a representational artifact, comprising a taxonomy as proper part, whose representational units are intended to designate some combination of universals, defined classes, and certain relations between them.[https://scholar.google.com/scholar_url?url=https://link.springer.com/article/10.1186/gb-2005-6-5-r46&hl=ru&sa=T&oi=gsr-r&ct=res&cd=0&d=16751037037460356545&ei=dlKtad7EJqqtieoPjb_p6QE&scisig=AFtJQiwhACheRjpf7pzpfYa-w_rt 13] | An ontology is a representational artifact, comprising a taxonomy as proper part, whose representational units are intended to designate some combination of universals, defined classes, and certain relations between them.[https://scholar.google.com/scholar_url?url=https://link.springer.com/article/10.1186/gb-2005-6-5-r46&hl=ru&sa=T&oi=gsr-r&ct=res&cd=0&d=16751037037460356545&ei=dlKtad7EJqqtieoPjb_p6QE&scisig=AFtJQiwhACheRjpf7pzpfYa-w_rt <sup><u>13</u></sup>] | ||
[http://ontology.buffalo.edu/bfo/Terminology_for_Ontologies.pdf URL] '''PID''':NA '''bref''': p.61(5) Smith, B., Kusnierczyk, W., Schober, D., Ceusters, W. Towards a Reference Terminology for Ontology Research and Development in the Biomedical Domain. KR-MED 2006 “Biomedical Ontology in Action”. November 8, 2006, Baltimore, Maryland, USA. | [http://ontology.buffalo.edu/bfo/Terminology_for_Ontologies.pdf '''<u>URL</u>'''] '''PID''':NA '''bref''': p.61(5) Smith, B., Kusnierczyk, W., Schober, D., Ceusters, W. Towards a Reference Terminology for Ontology Research and Development in the Biomedical Domain. KR-MED 2006 “Biomedical Ontology in Action”. November 8, 2006, Baltimore, Maryland, USA. | ||
<span id="zng98"></span> | |||
=== (Z)NG98 === | |||
An ontology is a logical theory accounting for the ''intended meaning'' of a formal vocabulary<sup>12</sup>, i.e. its ''ontological commitment'' to a particular ''conceptualization'' of the world. The intended models of a logical language using such a vocabulary are constrained by its ontological commitment. An ontology indirectly reflects this commitment (and the underlying conceptualization) by approximating these intended models. | An ontology is a logical theory accounting for the ''intended meaning'' of a formal vocabulary<sup>12</sup>, i.e. its ''ontological commitment'' to a particular ''conceptualization'' of the world. The intended models of a logical language using such a vocabulary are constrained by its ontological commitment. An ontology indirectly reflects this commitment (and the underlying conceptualization) by approximating these intended models. | ||
<sup>12</sup> Not necessarily this formal vocabulary will be part of a logical language: for example, it may be a protocol of communication between agents. | <sup>12</sup> Not necessarily this formal vocabulary will be part of a logical language: for example, it may be a protocol of communication between agents. | ||
[http://www.loa.istc.cnr.it/old/Papers/FOIS98.pdf URL] '''PID''':[[# | [http://www.loa.istc.cnr.it/old/Papers/FOIS98.pdf '''<u>URL</u>'''] '''PID''':[[#ng-nicola-guarino|<u>NG</u>]] '''bref''': p(5) in Guarino, N. (1998). Formal ontology and information systems. In Guarino, N., editor, Proceedings of Formal Ontology in Information Systems (FOIS’98), Frontiers in Artificial intelligence and Applications, pages 3-15. Amsterdam: IOS Press. | ||
< | <span id="comments-2"></span> | ||
==== Comments ==== | |||
<AS:This definition is not in a normal form, for example: "i.e." must be eliminated, description of models is not a part of definition, etc. BUT the text cited is a NG's way to define, as he wrote: "With these clarifications, we come up to the following definition, which refines Gruber’s definition by making clear the difference between an ontology and a conceptualization:" In such a case we need to get a "normal" or '''canonical form''' of definition.> | |||
<span id="webont03"></span> | |||
=== WebONT03 === | |||
In the contest of this work, we refer to what is sometimes called a | In the contest of this work, we refer to what is sometimes called a "structural" ontology -- a machine readable set of definitions that create a taxonomy of classes and subclasses and relationships between them. | ||
[https://www.w3.org/2001/sw/WebOnt/charter URL] PID:WWW | [https://www.w3.org/2001/sw/WebOnt/charter <u>URL</u>] PID:WWW | ||
< | <span id="canonical-form"></span> | ||
==== [https://docs.google.com/document/d/1LbLgXo02Qc5UBK29wDYRpbnTCQwfnQ9ZHikU_KDZFro/edit?tab=t.0#heading=h.qv41al5m2ame <u>canonical form</u>] ==== | |||
Ontology is a machine readable set of definitions that create a taxonomy of classes and subclasses and relationships between them. | Ontology is a machine readable set of definitions that create a taxonomy of classes and subclasses and relationships between them. | ||
< | <span id="comments-3"></span> | ||
==== Comments ==== | |||
''' | '''JA''':In the context of OWL (Web Ontology Language) an ontology is equivalent to a Description Logic knowledge base. (Horrocks, I., Patel-Schneider, P. F., and van Harmelen, F. From SHIQ and RDF to OWL: The making of a web ontology language. Journal of Web Semantics, 2003, 1(1):7. ([http://www.cs.man.ac.uk/~horrocks/Publications/download/2003/HoPH03a.pdf <u>paper</u>]) | ||
'''AS''':In this paper it's supposed that we know what ontology is. Paper has a URL to [https://docs.google.com/document/d/1N6vKV2FUly17U-gS7Sgzc67BxZUZz7h7mr6GJC9KexU/edit?tab=t.0#heading=h.m2e4832wh4d <u>IT-ontology DEFINITIONs</u>] | |||
<span id="wikip"></span> | |||
=== WIKIP === | |||
(1)an ontology encompasses a representation, formal naming, and definitions of the categories, properties, and relations between the concepts, data, or entities that pertain to one, many, or all [https://en.wikipedia.org/wiki/Domain_of_discourse domains of discourse]. | (1)an ontology encompasses a representation, formal naming, and definitions of the categories, properties, and relations between the concepts, data, or entities that pertain to one, many, or all [https://en.wikipedia.org/wiki/Domain_of_discourse <u>domains of discourse</u>]. | ||
(2)an ontology is a way of showing the properties of a subject area and how they are related, by defining a set of terms and relational expressions that represent the entities in that subject area. | (2)an ontology is a way of showing the properties of a subject area and how they are related, by defining a set of terms and relational expressions that represent the entities in that subject area. | ||
[https://en.wikipedia.org/wiki/Ontology_ | [https://en.wikipedia.org/wiki/Ontology_(information_science) <u>URL</u>] | ||
< | <span id="comments-4"></span> | ||
==== Comments ==== | |||
Citation: | Citation:"In [https://en.wikipedia.org/wiki/Information_science information science], an '''ontology''' encompasses a representation, formal naming, and definitions of the categories, properties, and relations between the concepts, data, or entities that pertain to one, many, or all [https://en.wikipedia.org/wiki/Domain_of_discourse domains of discourse]. More simply, an ontology is a way of showing the properties of a subject area and how they are related, by defining a set of terms and relational expressions that represent the entities in that subject area." | ||
+get defs from [https://en.wikipedia.org/wiki/Ontology_ | +get defs from [https://en.wikipedia.org/wiki/Ontology_(information_science)#Formal_ontology <u>https://en.wikipedia.org/wiki/Ontology_%28information_science%29#Formal_ontology</u>] | ||
+see also [https://en.wikipedia.org/wiki/Formal_ontology https://en.wikipedia.org/wiki/Formal_ontology] | +see also [https://en.wikipedia.org/wiki/Formal_ontology <u>https://en.wikipedia.org/wiki/Formal_ontology</u>] | ||
<span id="ja-group-of-definitions"></span> | |||
== JA group of definitions == | |||
AS:JA must consolidate all his definitions in one. Part of these definitions are descriptions, maybe all of them. And only JA can do this consolidation. | AS:JA must consolidate all his definitions in one. Part of these definitions are descriptions, maybe all of them. And only JA can do this consolidation. | ||
| Line 320: | Line 365: | ||
For example consider we think that JA004 is the consolidation then we reason: | For example consider we think that JA004 is the consolidation then we reason: | ||
If JA004 then JA001. | If JA004 then JA001. | ||
etc. | etc. | ||
If X is a | If X is a knowledge base whose artifacts constitute explicit axioms about domain entities and relations, expressed in a language with formal declarative semantics. | ||
THEN | |||
X is a formal semantic model enabling logical inference. | |||
<span id="ja001"></span> | |||
=== JA001! === | |||
Ontology – formal semantic model enabling logical inference. | |||
[https://groups.google.com/d/msgid/ontolog-forum/CAG%3D%3DwTd%3DMPKG1E0u9hfYpBDYhZ3xN_Mggj-MUe_-En-M%2BtdkBg | [https://groups.google.com/d/msgid/ontolog-forum/CAG%3D%3DwTd%3DMPKG1E0u9hfYpBDYhZ3xN_Mggj-MUe_-En-M%2BtdkBg@mail.gmail.com?utm_medium=email&utm_source=footer '''<u>URL</u>'''] '''PID''':JA | ||
<span id="ja002"></span> | |||
=== JA002! === | |||
An ontology in IT is a formal artifact with explicit semantics. | An ontology in IT is a formal artifact with explicit semantics. | ||
[https://groups.google.com/d/msgid/ontolog-forum/CAG%3D%3DwTdnUH7L9PRKyDcKAchQU1V1_Hcth1G8%2BXt-rfL%3DZtdFfg | [https://groups.google.com/d/msgid/ontolog-forum/CAG%3D%3DwTdnUH7L9PRKyDcKAchQU1V1_Hcth1G8%2BXt-rfL%3DZtdFfg@mail.gmail.com?utm_medium=email&utm_source=footer '''<u>URL</u>'''] '''PID''':JA | ||
''' | |||
< | <span id="ja003"></span> | ||
=== JA003! === | |||
A formally specified conceptualization expressed in a representation language with explicit semantics. | |||
< | [https://groups.google.com/g/ontolog-forum/c/x_WyrRsN7Q4/m/idjVyyQyAQAJ '''<u>URL</u>'''] '''PID''':JA | ||
< | <span id="comments-5"></span> | ||
==== Comments: ==== | |||
<AS:See also [[#ja2-it-ontology-intended-to|<u>here</u>]].> | |||
< | <span id="ja004-as"></span> | ||
=== JA004! AS:🏅 === | |||
A knowledge base whose artifacts constitute explicit axioms about domain entities and relations, expressed in a language with formal declarative semantics. | |||
''' | [https://groups.google.com/g/ontolog-forum/c/x_WyrRsN7Q4/m/idjVyyQyAQAJ '''<u>URL</u>'''] '''PID''':JA | ||
< | <span id="ja005"></span> | ||
=== JA005! === | |||
IT ontology "is a formally encoded artifact with defined semantics". | |||
[https://groups.google.com/g/ontolog-forum/c/x_WyrRsN7Q4/m/idjVyyQyAQAJ '''<u>URL</u>'''] '''PID''':JA | |||
<span id="person-ids"></span> | |||
== Person IDs == | |||
in ABC order. | in ABC order. | ||
<span id="as-alex-shkotin"></span> | |||
=== AS Alex Shkotin === | |||
[ | [mailto:ashkotin@acm.org <u>Alex Shkotin</u>] | ||
Independent Computer Scientist | |||
[https://www.linkedin.com/in/ashkotin/ <u>Linkedin</u>] ∘ [https://www.researchgate.net/profile/Alex-Shkotin <u>RGate</u>] ∘ [https://mipt.academia.edu/AlexShkotin <u>Academia.edu</u>] | |||
[https://ontologforum.com/ <u>Ontolog</u>] BoT | |||
<span id="bl-ben-lutkevich"></span> | |||
=== BL Ben Lutkevich === | |||
[https://www.techtarget.com/contributor/Ben-Lutkevich <u>https://www.techtarget.com/contributor/Ben-Lutkevich</u>] | |||
< | <span id="ja-john-antill"></span> | ||
=== JA John Antill === | |||
MS KM, MCKM, CKS IA & KT, KCS | |||
MS AI Student at Purdue | |||
256-541-1229 | |||
[mailto:djanteater@gmail.com <u>djanteater@gmail.com</u>] | |||
<span id="js-john-sowa"></span> | |||
=== JS John Sowa === | |||
[https://ontologforum.com/index.php/JohnSowa <u>https://ontologforum.com/index.php/JohnSowa</u>] | |||
<span id="kb-ken-baclawski"></span> | |||
=== KB Ken Baclawski === | |||
[https://ontologforum.com/index.php/KenBaclawski <u>https://ontologforum.com/index.php/KenBaclawski</u>] | |||
< | <span id="ng-nicola-guarino"></span> | ||
=== NG Nicola Guarino === | |||
(1998)National Research Council, LADSEB-CNR, Corso Stati Uniti 4, I-35127 Padova, Italy. guarino@ladseb.pd.cnr.it | |||
<span id="tg-thomas-gruber"></span> | |||
=== TG Thomas Gruber === | |||
[ | [https://www.researchgate.net/profile/Thomas-Gruber-10 <u>https://www.researchgate.net/profile/Thomas-Gruber-10</u>] | ||
[ | [[File:vertopal_e3dcf0d2d79e4a57a828e871a0b6a6e7/media/image1.png|495x455px]] | ||
[https://tomgruber.org/writing/ontolingua-kaj-1993/ <u>https://tomgruber.org/writing/ontolingua-kaj-1993/</u>] | |||
<span id="appendix-a.-collections-used"></span> | |||
== Appendix A. Collections used == | |||
<span id="terms-for-central-general-notionsiaoa"></span> | |||
=== Terms for Central General Notions(IAOA) === | |||
[https://wiki.iaoa.org/index.php/Edu:Term_List https://wiki.iaoa.org/index.php/Edu:Term_List] | [https://wiki.iaoa.org/index.php/Edu:Term_List <u>https://wiki.iaoa.org/index.php/Edu:Term_List</u>] | ||
<span id="towards-a-reference-terminology-for-ontology-research-and-development-in-the-biomedical-domain"></span> | |||
=== Towards a Reference Terminology for Ontology Research and Development in the Biomedical Domain === | |||
[http://ontology.buffalo.edu/bfo/Terminology_for_Ontologies.pdf http://ontology.buffalo.edu/bfo/Terminology_for_Ontologies.pdf] | [http://ontology.buffalo.edu/bfo/Terminology_for_Ontologies.pdf <u>http://ontology.buffalo.edu/bfo/Terminology_for_Ontologies.pdf</u>] | ||
Revision as of 15:59, 22 March 2026
This document is a collection of definitions from different sources.
AND MUST BE MOVED TO https://ontologforum.com/index.php/Ontology(IT)
DiU - definition is unattainable. This means we have a URL to the source description, but not the definition itself!
DB - database.
KB - knowledge base.
PID - person ID. There are two person roles: presenting his own definition xor presenting a reference to the source of the definition.
bref - bibliographic reference. If not full, it keeps "???".
Every definition has a unique ID and is a separate unit of knowledge. If the definition is personal, "!" follows after the ID.
If there is no direct link to the source in the form of a URL, the ID of the person who provided the definition is provided to ask. If the person created the definition himself, the definition's ID is followed by "!".
End letter "G" in definition ID means that the definition is IN GENERAL i.e. not only for IT.
General abbr
ITSM - IT Service Management refers to the entire lifecycle of designing, delivering, managing, and optimizing IT services for users. URL:???
goto
Collector, please visit:
-DOL, TLO
-every onto language or family: DL, OWL2, CL, hets.eu
Points has been visited see IT-ontology DEFINITIONs
Rules to keep collection and discussion
see DEFINITIONs. rules & tasks
Distinguishing properties
Here we collect various ways to distinguish whether a KB is an ontology. And any useful ideas.
+$+VERSION#1(JA)2
9. Reiterating criteria clearly
Based on ISO and ontology engineering literature, we can state:
A knowledge base becomes an ontology when:
Its vocabulary explicitly defines domain classes and relations (Gruber 1993; Studer et al. 1998).
Its assertions are intended as domain axioms expressing ontological commitment (Guarino 1998).
The representation language has formal declarative semantics independent of execution strategy (Tarski 1956; OWL 2 Direct Semantics 2012).
Inference derives from logical consequence under that semantics (Baader et al. 2003).
That does not require Hermit.
It does not exclude Prolog.
It does require logical formalization.
The disagreement here is not about ISO being wrong.
It is about ISO defining a superset category.
Ontology, in the semantic-technology sense, is a stricter subclass of knowledge base.
conceptualization
"A body of formally represented knowledge is based on a conceptualization: the objects, concepts, and other entities that are presumed to exist in some area of interest and the relationships that hold them (Genesereth & Nilsson, 1987). A conceptualization is an abstract, simplified view of the world that we wish to represent for some purpose. Every knowledge base, knowledge-based system, or knowledge-level agent is committed to some conceptualization, explicitly or implicitly." TG
formal language
AS: Chris Mungall has ontology on Python. Some Prolog programs are not ontology.
formal vocabulary
see in IT-ontology DEFINITIONs
model
see in IT-ontology DEFINITIONs
ontological commitment
see in IT-ontology DEFINITIONs
theory
, logical see in IT-ontology DEFINITIONs
DISCUSSION
(JA)2 IT-ontology intended to…
3. On Contradiction and Completeness
You raise an important philosophical question:
Is the IT-ontology complete and non-contradictory knowledge about the domain?
My answer is: no.
An IT-ontology is not complete knowledge. It is not guaranteed consistent in practice. It is not a total theory of a domain.
It is a formalized conceptual model intended to:
Constrain interpretation,
Enable logical consequence,
Make commitments explicit.
It may be incomplete.
It may contain modeling errors.
It may require revision.
So I would not define IT-ontology as “complete knowledge.”
I would define it as:
A formally specified conceptualization expressed in a representation language with explicit semantics.
It is closer to a theory schema than to a complete theory.
Your formulation — “a theory or model for theory” — is actually very close to how ontology engineers think about it.
(JA)1 topics around
"That is why ontology engineers distinguish:
Vocabulary (classes, properties)
Axioms (subsumption, equivalence, restrictions)
Rules (SWRL, production rules, etc.)
They are not the same category.
Baader et al., The Description Logic Handbook (2003), distinguish TBox (terminological axioms: classes, subsumption, properties) from ABox (assertions about individuals), and separate these from rule systems.
The W3C OWL 2 Structural Specification (2012) clearly distinguishes class axioms and property axioms from rule extensions such as SWRL.
"
"So ontology status does not depend on Hermit accessibility.
It depends on whether the representation language has well-defined declarative semantics.
The OWL 2 Direct Semantics (W3C Recommendation, 2012) provides a model-theoretic semantics independent of any specific reasoner.
Description logic semantics are formally defined in Baader et al. (2003).
The model-theoretic tradition originates with Tarski (1956), Logic, Semantics, Metamathematics.
"
"Some Prolog KBs can function as ontologies.
But many do not.
Why? Because they often:
Mix domain knowledge with control strategy
Use procedural constructs (cuts, ordering effects)
Lack explicit ontological commitments (identity criteria, typing discipline, subsumption structure)
A clean, purely declarative first-order theory encoded in Prolog syntax could absolutely count as an ontology.
A heuristic expert system implemented in Prolog typically would not.
So the issue is not “Prolog vs OWL.”
It is declarative domain theory vs procedural problem-solving system.
Mix domain knowledge with control strategy (Lloyd 1987).
Depend on operational features such as ordering and cut (Kowalski 1979).
Lack explicit ontological commitments in the sense articulated by Guarino (1998).
"
"So again, the distinction hinges on logical formalization, not file format.
Hets (Mossakowski, Maeder & Lüttich, 2007, TACAS) is grounded in institution theory (Goguen & Burstall, 1992
"
"An ontology in IT is a formal artifact with explicit semantics.
A conceptual model written in English may describe an ontology.
It is not an ontology artifact until formalized.
This is the same distinction between:
Mathematical truth
A formal proof in a specified logical system
Ontology engineering operates in the latter space.
Noy & McGuinness (2001), Ontology Development 101, emphasize formal class and property specification.
Smith (2003), “Ontology,” in Blackwell Guide to the Philosophy of Computing and Information, distinguishes philosophical ontology from computational ontology artifacts.
"
Classification notes
Consolidated Decision: Base Definition for IT-ontology
(AS)Starter: formal ontology is a KB where knowledge is fully structured and formalized as much as possible.
(JA) “Ontology is a knowledge base, but not every knowledge base is an ontology”
URL <AS:text has hints to definition sources>
This is not a rhetorical move. It is a distinction established in the ontology engineering community.
The differentiator is not:
Whether inference occurs
Whether rules exist
Whether a reasoner like Hermit can process it
The differentiator is whether the artifact is a formal specification of a conceptualization, not merely a rule-based problem-solving system.
This distinction appears in:
Gruber (1993)
Guarino (1998)
Studer, Benjamins & Fensel (1998)
The W3C OWL specifications
The key issue is ontological commitment, not computational accessibility.
Gruber (1993), “A Translation Approach to Portable Ontology Specifications,” Knowledge Acquisition.
Studer, Benjamins & Fensel (1998), “Knowledge Engineering: Principles and Methods,” Data & Knowledge Engineering.
Guarino (1998), “Formal Ontology in Information Systems,” FOIS 1998.
COLLECTION
GRB93
An ontology is an explicit specification of a conceptualization.
URL PID:TG bref:Thomas R. Gruber. A Translation Approach to Portable Ontology Specifications. Knowledge Acquisition, 5(2):199-220, 1993.
JS2000
A catalog of the types of things that are assumed to exist in a domain of interest D from the perspective of a person who uses a language L for the purpose of talking about [the domain] D.
URL:??? PID:JS bref: John F. Sowa, "Knowledge Representation - Logical, Philosophical, and Computational Foundations", 2000, P.492.
Comments
AS:from IAOAcat[4]
BL04
The catalogue of concepts (constants, relations, functions, etc.) used to represent knowledge about a problem domain.
URL:??? PID:NA bref: (p.44, "KNOWLEDGE REPRESENTATION AND REASONING" by Ronald J. Brachman and Hector J. Levesque (2004))
Comments
AS:from IAOAcat[5]
SKSC06
An ontology is a representational artifact, comprising a taxonomy as proper part, whose representational units are intended to designate some combination of universals, defined classes, and certain relations between them.13
URL PID:NA bref: p.61(5) Smith, B., Kusnierczyk, W., Schober, D., Ceusters, W. Towards a Reference Terminology for Ontology Research and Development in the Biomedical Domain. KR-MED 2006 “Biomedical Ontology in Action”. November 8, 2006, Baltimore, Maryland, USA.
(Z)NG98
An ontology is a logical theory accounting for the intended meaning of a formal vocabulary12, i.e. its ontological commitment to a particular conceptualization of the world. The intended models of a logical language using such a vocabulary are constrained by its ontological commitment. An ontology indirectly reflects this commitment (and the underlying conceptualization) by approximating these intended models.
12 Not necessarily this formal vocabulary will be part of a logical language: for example, it may be a protocol of communication between agents.
URL PID:NG bref: p(5) in Guarino, N. (1998). Formal ontology and information systems. In Guarino, N., editor, Proceedings of Formal Ontology in Information Systems (FOIS’98), Frontiers in Artificial intelligence and Applications, pages 3-15. Amsterdam: IOS Press.
Comments
<AS:This definition is not in a normal form, for example: "i.e." must be eliminated, description of models is not a part of definition, etc. BUT the text cited is a NG's way to define, as he wrote: "With these clarifications, we come up to the following definition, which refines Gruber’s definition by making clear the difference between an ontology and a conceptualization:" In such a case we need to get a "normal" or canonical form of definition.>
WebONT03
In the contest of this work, we refer to what is sometimes called a "structural" ontology -- a machine readable set of definitions that create a taxonomy of classes and subclasses and relationships between them.
URL PID:WWW
canonical form
Ontology is a machine readable set of definitions that create a taxonomy of classes and subclasses and relationships between them.
Comments
JA:In the context of OWL (Web Ontology Language) an ontology is equivalent to a Description Logic knowledge base. (Horrocks, I., Patel-Schneider, P. F., and van Harmelen, F. From SHIQ and RDF to OWL: The making of a web ontology language. Journal of Web Semantics, 2003, 1(1):7. (paper)
AS:In this paper it's supposed that we know what ontology is. Paper has a URL to IT-ontology DEFINITIONs
WIKIP
(1)an ontology encompasses a representation, formal naming, and definitions of the categories, properties, and relations between the concepts, data, or entities that pertain to one, many, or all domains of discourse.
(2)an ontology is a way of showing the properties of a subject area and how they are related, by defining a set of terms and relational expressions that represent the entities in that subject area.
Comments
Citation:"In information science, an ontology encompasses a representation, formal naming, and definitions of the categories, properties, and relations between the concepts, data, or entities that pertain to one, many, or all domains of discourse. More simply, an ontology is a way of showing the properties of a subject area and how they are related, by defining a set of terms and relational expressions that represent the entities in that subject area."
+get defs from https://en.wikipedia.org/wiki/Ontology_%28information_science%29#Formal_ontology
+see also https://en.wikipedia.org/wiki/Formal_ontology
JA group of definitions
AS:JA must consolidate all his definitions in one. Part of these definitions are descriptions, maybe all of them. And only JA can do this consolidation.
Presumably every of five his current definitions must be derived from consolidated.
For example consider we think that JA004 is the consolidation then we reason:
If JA004 then JA001.
etc.
If X is a knowledge base whose artifacts constitute explicit axioms about domain entities and relations, expressed in a language with formal declarative semantics.
THEN
X is a formal semantic model enabling logical inference.
JA001!
Ontology – formal semantic model enabling logical inference.
URL PID:JA
JA002!
An ontology in IT is a formal artifact with explicit semantics.
URL PID:JA
JA003!
A formally specified conceptualization expressed in a representation language with explicit semantics.
URL PID:JA
Comments:
<AS:See also here.>
JA004! AS:🏅
A knowledge base whose artifacts constitute explicit axioms about domain entities and relations, expressed in a language with formal declarative semantics.
URL PID:JA
JA005!
IT ontology "is a formally encoded artifact with defined semantics".
URL PID:JA
Person IDs
in ABC order.
AS Alex Shkotin
Independent Computer Scientist
Linkedin ∘ RGate ∘ Academia.edu
Ontolog BoT
BL Ben Lutkevich
https://www.techtarget.com/contributor/Ben-Lutkevich
JA John Antill
MS KM, MCKM, CKS IA & KT, KCS
MS AI Student at Purdue
256-541-1229
JS John Sowa
https://ontologforum.com/index.php/JohnSowa
KB Ken Baclawski
https://ontologforum.com/index.php/KenBaclawski
NG Nicola Guarino
(1998)National Research Council, LADSEB-CNR, Corso Stati Uniti 4, I-35127 Padova, Italy. guarino@ladseb.pd.cnr.it
TG Thomas Gruber
https://www.researchgate.net/profile/Thomas-Gruber-10
File:Vertopal e3dcf0d2d79e4a57a828e871a0b6a6e7/media/image1.png
https://tomgruber.org/writing/ontolingua-kaj-1993/
Appendix A. Collections used
Terms for Central General Notions(IAOA)
https://wiki.iaoa.org/index.php/Edu:Term_List
Towards a Reference Terminology for Ontology Research and Development in the Biomedical Domain
http://ontology.buffalo.edu/bfo/Terminology_for_Ontologies.pdf
