<?xml version="1.0" encoding="UTF-8"?>
<TEI xml:space="preserve" xmlns="http://www.tei-c.org/ns/1.0" 
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" 
xsi:schemaLocation="http://www.tei-c.org/ns/1.0 https://raw.githubusercontent.com/kermitt2/grobid/master/grobid-home/schemas/xsd/Grobid.xsd"
 xmlns:xlink="http://www.w3.org/1999/xlink">
	<teiHeader xml:lang="en">
		<fileDesc>
			<titleStmt>
				<title level="a" type="main">Debugging classical ontologies using defeasible reasoning tools (extended abstract)</title>
			</titleStmt>
			<publicationStmt>
				<publisher/>
				<availability status="unknown"><licence/></availability>
			</publicationStmt>
			<sourceDesc>
				<biblStruct>
					<analytic>
						<author>
							<persName><forename type="first">Simone</forename><surname>Coetzer</surname></persName>
							<email>scoetzer50@gmail.com</email>
							<affiliation key="aff0">
								<orgName type="department">CAIR</orgName>
								<orgName type="institution">Stellenbosch Univ</orgName>
								<address>
									<country key="ZA">South Africa</country>
								</address>
							</affiliation>
						</author>
						<author>
							<persName><forename type="first">Katarina</forename><surname>Britz</surname></persName>
							<email>abritz@sun.ac.za</email>
							<affiliation key="aff0">
								<orgName type="department">CAIR</orgName>
								<orgName type="institution">Stellenbosch Univ</orgName>
								<address>
									<country key="ZA">South Africa</country>
								</address>
							</affiliation>
						</author>
						<title level="a" type="main">Debugging classical ontologies using defeasible reasoning tools (extended abstract)</title>
					</analytic>
					<monogr>
						<imprint>
							<date/>
						</imprint>
					</monogr>
					<idno type="MD5">85FFC4CBBCF1C73882BE519B520D0B78</idno>
				</biblStruct>
			</sourceDesc>
		</fileDesc>
		<encodingDesc>
			<appInfo>
				<application version="0.7.2" ident="GROBID" when="2023-03-24T10:24+0000">
					<desc>GROBID - A machine learning software for extracting information from scholarly documents</desc>
					<ref target="https://github.com/kermitt2/grobid"/>
				</application>
			</appInfo>
		</encodingDesc>
		<profileDesc>
			<abstract/>
		</profileDesc>
	</teiHeader>
	<text xml:lang="en">
		<body>
<div xmlns="http://www.tei-c.org/ns/1.0"><p>Ontologies provide knowledge engineers with the ability to represent and encode knowledge in a formal language so that it can be processed or 'reasoned over' by a computer <ref type="bibr" target="#b6">[7]</ref>. Notable benefits include the ability to source new knowledge by making statements that are implicitly deduced explicitly available to the end-user, to classify individuals or instances and to check the addition of new knowledge for logical consistency <ref type="bibr" target="#b0">[1]</ref>.</p><p>Given the nature and goal of ontologies, a successful application of ontologies relies on (1) representing as much relevant domain knowledge accurately (2) while maintaining logical consistency. As the successful implementation of a real-world ontology is likely to contain many concepts and intricate relationships between the concepts, it is necessary to follow a methodology for debugging the ontology <ref type="bibr" target="#b4">[5]</ref>. A myriad of ontology debugging approaches (some of them instantiated in tools) have been developed to help the knowledge engineer pinpoint the cause of logical inconsistencies and rectify them in a strategic way <ref type="bibr" target="#b5">[6,</ref><ref type="bibr" target="#b2">3,</ref><ref type="bibr" target="#b3">4]</ref>. Usually, a Model-Based Diagnosis approach is followed to debug the ontology: this involves finding the diagnosis which contains all minimal conflict sets; the diagnosis is then presented to the knowledge engineer who will need to amend the axioms by modifying or deleting certain axioms; once the ontology has been amended, it is again checked whether an inconsistency is present -if it is, the process is repeated <ref type="bibr" target="#b4">[5]</ref>.</p><p>Although most ontology debugging approaches localise the faulty axioms, they do not (to date) provide recommendations on how logical inconsistencies can be resolved by weakening (instead of deleting) faulty axioms. We propose a theoretical methodology for weakening faulty axioms in a strategic way using defeasible reasoning tools. Our methodology draws from Rodler's <ref type="bibr" target="#b4">[5]</ref> interactive ontology debugging approach which not only localises faulty axioms but provides the knowledge engineer with a strategic way of resolving them by presenting the root cause inconsistencies first. We are extending this approach by suggesting that through the use of defeasible reasoning techniques, a methodology can be created to systematically find conflict resolution recommendations.</p><p>Importantly, our goal is not to convert a classical ontology to a defeasible ontology -therefore we do not use defeasible reasoning support through, for example, the computation of rational closure. Rather, we use the definition of exceptionality of a concept, which is central to the semantics of defeasible DLs, and the associated algorithm (as can be found in <ref type="bibr" target="#b1">[2]</ref>) to determine the extent of a concept's exceptionality (their ranking); then, starting with the statements containing the most general concepts (the least exceptional concepts) weakened versions of the original statements are constructed; this is done until all inconsistencies have been resolved. Consider how this methodology can be applied to the following set of statements in an example ontology:</p><formula xml:id="formula_0">U ser ¬∃AccessT o.Conf identialInf o Staf f U ser Staf f ∃AccessT o.Conf identialInf o BlackListedStaf f Staf f BlackListedStaf f ¬∃AccessT o.Conf identialInf o</formula><p>When running the ranking algorithm, the concept 'User' is the most general exceptional concept; the concept 'Staff' is more exceptional than the concept of 'User'. Starting with the least exceptional concept, 'User', we then weaken statements containing this concept on the left hand side of the axiom by using a conjunction between the current concept under investigation and the negation of the concept associated with it on the next level of exceptionality (Staff) -in this phase, the ontology is transformed as follows:</p><formula xml:id="formula_1">U ser ¬Staf f ¬∃AccessT o.Conf identialInf o Staf f U ser Staf f ∃AccessT o.Conf identialInf o BlackListedStaf f Staf f BlackListedStaf f ¬∃AccessT o.Conf identialInf o</formula><p>The ranking of all concepts is again calculated and the first exceptional concept, 'User' has now been resolved. Then, we move onto the next concept, Staff, which is now the most general exceptional concept. The same kind of transformation is performed on axioms containing 'Staff' on the left hand side (with the exclusion of axioms containing one of the previous exceptional statements on the right hand side):</p><formula xml:id="formula_2">U ser ¬Staf f ¬∃AccessT o.Conf identialInf o Staf f U ser Staf f ¬BlackListedStaf f ∃AccessT o.Conf identialInf o BlackListedStaf f Staf f BlackListedStaf f ¬∃AccessT o.Conf identialInf o</formula><p>The forward-looking goal of this research is to provide a methodological foundation which could, in future, lead to the development and implementation of an inconsistency resolution recommender tool that is fully integrated with the ontology development environment.</p></div>		</body>
		<back>
			<div type="references">

				<listBibl>

<biblStruct xml:id="b0">
	<analytic>
		<title level="a" type="main">Description Logics</title>
		<author>
			<persName><forename type="first">F</forename><surname>Baader</surname></persName>
		</author>
		<author>
			<persName><forename type="first">I</forename><surname>Horrocks</surname></persName>
		</author>
		<author>
			<persName><forename type="first">U</forename><surname>Sattler</surname></persName>
		</author>
	</analytic>
	<monogr>
		<title level="m">Handbook On Ontologies</title>
				<editor>
			<persName><forename type="first">S</forename><surname>Staab</surname></persName>
		</editor>
		<editor>
			<persName><forename type="first">R</forename><surname>Studer</surname></persName>
		</editor>
		<meeting><address><addrLine>Berlin</addrLine></address></meeting>
		<imprint>
			<publisher>Springer-Verlag</publisher>
			<date type="published" when="2004">2004</date>
			<biblScope unit="volume">1</biblScope>
			<biblScope unit="page" from="3" to="28" />
		</imprint>
	</monogr>
</biblStruct>

<biblStruct xml:id="b1">
	<analytic>
		<title level="a" type="main">A KLM perspective on defeasible reasoning for description logics</title>
		<author>
			<persName><forename type="first">K</forename><surname>Britz</surname></persName>
		</author>
		<author>
			<persName><forename type="first">G</forename><surname>Casini</surname></persName>
		</author>
		<author>
			<persName><forename type="first">T</forename><surname>Meyer</surname></persName>
		</author>
		<author>
			<persName><forename type="first">I</forename><surname>Varzinczak</surname></persName>
		</author>
	</analytic>
	<monogr>
		<title level="m">Description Logic, Theory Combination, and All That. Essays Dedicated to Franz Baader on the Occasion of His 60th Birthday</title>
				<editor>
			<persName><forename type="first">C</forename><surname>Lutz</surname></persName>
		</editor>
		<editor>
			<persName><forename type="first">U</forename><surname>Sattler</surname></persName>
		</editor>
		<editor>
			<persName><forename type="first">C</forename><surname>Tinelli</surname></persName>
		</editor>
		<editor>
			<persName><forename type="first">A.-Y</forename><surname>Turhan</surname></persName>
		</editor>
		<editor>
			<persName><forename type="first">F</forename><surname>Wolter</surname></persName>
		</editor>
		<imprint>
			<date type="published" when="2019">2019</date>
			<biblScope unit="page" from="147" to="173" />
		</imprint>
	</monogr>
</biblStruct>

<biblStruct xml:id="b2">
	<analytic>
		<title level="a" type="main">A General Diagnosis Method for Ontologies</title>
		<author>
			<persName><forename type="first">G</forename><surname>Friedrich</surname></persName>
		</author>
		<author>
			<persName><forename type="first">K</forename><surname>Schekotykhin</surname></persName>
		</author>
	</analytic>
	<monogr>
		<title level="m">Proceedings of the 4th International Semantic Web Conference</title>
				<meeting>the 4th International Semantic Web Conference<address><addrLine>ISWC</addrLine></address></meeting>
		<imprint>
			<date type="published" when="2005">2005. 2005</date>
		</imprint>
	</monogr>
</biblStruct>

<biblStruct xml:id="b3">
	<analytic>
		<title level="a" type="main">Finding all Justifications of OWL DL Entailments, The Semantic Web</title>
		<author>
			<persName><forename type="first">A</forename><surname>Kalyanpur</surname></persName>
		</author>
		<author>
			<persName><forename type="first">B</forename><surname>Parsia</surname></persName>
		</author>
		<author>
			<persName><forename type="first">M</forename><surname>Horridge</surname></persName>
		</author>
		<author>
			<persName><forename type="first">E</forename><surname>Sirin</surname></persName>
		</author>
	</analytic>
	<monogr>
		<title level="m">6th International Semantic Web Conference</title>
				<imprint>
			<date type="published" when="2007">2007</date>
		</imprint>
	</monogr>
</biblStruct>

<biblStruct xml:id="b4">
	<monogr>
		<title level="m" type="main">Interactive Debugging of Knowledge Bases</title>
		<author>
			<persName><forename type="first">P</forename><surname>Rodler</surname></persName>
		</author>
		<imprint>
			<date type="published" when="2015">2015</date>
		</imprint>
		<respStmt>
			<orgName>Alpen-Adria University Klagenfurt</orgName>
		</respStmt>
	</monogr>
	<note type="report_type">PhD thesis</note>
</biblStruct>

<biblStruct xml:id="b5">
	<analytic>
		<title level="a" type="main">Debugging Incoherent Terminologies</title>
		<author>
			<persName><forename type="first">S</forename><surname>Schlobach</surname></persName>
		</author>
		<author>
			<persName><forename type="first">Z</forename><surname>Huang</surname></persName>
		</author>
		<author>
			<persName><forename type="first">R</forename><surname>Cornet</surname></persName>
		</author>
		<author>
			<persName><forename type="first">F</forename><surname>Harmelen</surname></persName>
		</author>
	</analytic>
	<monogr>
		<title level="j">Journal of Automated Reasoning</title>
		<imprint>
			<biblScope unit="volume">39</biblScope>
			<biblScope unit="page" from="317" to="349" />
			<date type="published" when="2007">2007</date>
		</imprint>
	</monogr>
</biblStruct>

<biblStruct xml:id="b6">
	<analytic>
		<title level="a" type="main">Knowledge Engineering: Principles and Methods</title>
		<author>
			<persName><forename type="first">R</forename><surname>Studer</surname></persName>
		</author>
		<author>
			<persName><forename type="first">V</forename><forename type="middle">R</forename><surname>Benjamins</surname></persName>
		</author>
		<author>
			<persName><forename type="first">D</forename><surname>Fensel</surname></persName>
		</author>
	</analytic>
	<monogr>
		<title level="j">Data and Knowledge Engineering</title>
		<imprint>
			<biblScope unit="volume">25</biblScope>
			<biblScope unit="page" from="161" to="197" />
			<date type="published" when="1998">1998</date>
		</imprint>
	</monogr>
</biblStruct>

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