<?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">Constraint Reuse in DL-Lite Core with Arbitrary Number Restrictions</title>
			</titleStmt>
			<publicationStmt>
				<publisher/>
				<availability status="unknown"><licence/></availability>
			</publicationStmt>
			<sourceDesc>
				<biblStruct>
					<analytic>
						<author>
							<persName><forename type="first">Marco</forename><forename type="middle">A</forename><surname>Casanova</surname></persName>
							<email>casanova@inf.puc-rio.br</email>
							<affiliation key="aff0">
								<orgName type="department">Department of Informatics</orgName>
								<orgName type="institution">PUC-Rio -Rio de Janeiro</orgName>
								<address>
									<settlement>RJ</settlement>
									<country key="BR">Brazil</country>
								</address>
							</affiliation>
						</author>
						<author>
							<persName><forename type="first">Karin</forename><forename type="middle">K</forename><surname>Breitman</surname></persName>
							<affiliation key="aff0">
								<orgName type="department">Department of Informatics</orgName>
								<orgName type="institution">PUC-Rio -Rio de Janeiro</orgName>
								<address>
									<settlement>RJ</settlement>
									<country key="BR">Brazil</country>
								</address>
							</affiliation>
						</author>
						<author>
							<persName><forename type="first">Antonio</forename><forename type="middle">L</forename><surname>Furtado</surname></persName>
							<email>furtado@inf.puc-rio.br</email>
							<affiliation key="aff0">
								<orgName type="department">Department of Informatics</orgName>
								<orgName type="institution">PUC-Rio -Rio de Janeiro</orgName>
								<address>
									<settlement>RJ</settlement>
									<country key="BR">Brazil</country>
								</address>
							</affiliation>
						</author>
						<author>
							<persName><forename type="first">Vânia</forename><forename type="middle">M P</forename><surname>Vidal</surname></persName>
							<email>vvidal@lia.ufc.br</email>
							<affiliation key="aff1">
								<orgName type="department">Department of Computing</orgName>
								<orgName type="institution">Federal University of Ceará -Fortaleza</orgName>
								<address>
									<region>CE</region>
									<country key="BR">Brazil</country>
								</address>
							</affiliation>
						</author>
						<author>
							<persName><forename type="first">José</forename><forename type="middle">A F</forename><surname>De Macêdo</surname></persName>
							<email>jose.macedo@lia.ufc.br</email>
							<affiliation key="aff1">
								<orgName type="department">Department of Computing</orgName>
								<orgName type="institution">Federal University of Ceará -Fortaleza</orgName>
								<address>
									<region>CE</region>
									<country key="BR">Brazil</country>
								</address>
							</affiliation>
						</author>
						<author>
							<persName><forename type="first">Eveline</forename><forename type="middle">R</forename><surname>Sacramento</surname></persName>
							<email>esacramento@inf.puc-rio.br</email>
							<affiliation key="aff0">
								<orgName type="department">Department of Informatics</orgName>
								<orgName type="institution">PUC-Rio -Rio de Janeiro</orgName>
								<address>
									<settlement>RJ</settlement>
									<country key="BR">Brazil</country>
								</address>
							</affiliation>
							<affiliation key="aff2">
								<orgName type="institution">Ceará State Foundation of Meteorology and Water Resources</orgName>
								<address>
									<settlement>Fortaleza</settlement>
									<region>CE</region>
									<country key="BR">Brazil</country>
								</address>
							</affiliation>
						</author>
						<title level="a" type="main">Constraint Reuse in DL-Lite Core with Arbitrary Number Restrictions</title>
					</analytic>
					<monogr>
						<imprint>
							<date/>
						</imprint>
					</monogr>
					<idno type="MD5">CCFDAC10A08E8721B948E75B3EA02C8F</idno>
				</biblStruct>
			</sourceDesc>
		</fileDesc>
		<encodingDesc>
			<appInfo>
				<application version="0.7.2" ident="GROBID" when="2023-03-24T19:37+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>
			<textClass>
				<keywords>
					<term>constraints</term>
					<term>DL-Lite Core</term>
					<term>Description Logics</term>
				</keywords>
			</textClass>
			<abstract>
<div xmlns="http://www.tei-c.org/ns/1.0"><p>The process of reusing an ontology involves two issues: (1) selecting a set of terms from the ontology vocabulary; and (2) using the ontology constraints to derive those that apply to such terms. The first issue corresponds to the familiar practice of importing namespaces. This paper proposes to address the second issue by introducing a set of operations over ontologies, treated as theories and not just as vocabularies. It discusses how to compute the operations for a class of ontologies built upon DL-Lite core with arbitrary number restrictions. Finally, for this class of ontologies, the paper addresses the question of minimizing the set of constraints which results from an operation.</p></div>
			</abstract>
		</profileDesc>
	</teiHeader>
	<text xml:lang="en">
		<body>
<div xmlns="http://www.tei-c.org/ns/1.0"><head n="1">Introduction</head><p>We introduce a set of concepts and procedures that promote constraint reuse in ontology design. We start by introducing a set of operations on ontologies that create new ontologies, including their constraints, out of other ontologies. Such operations extend the idea of namespaces to take into account constraints and treat ontologies as theories. Then, we concretely show how to compute the operations when the ontologies are built upon DL-Lite core with arbitrary number restrictions <ref type="bibr" target="#b2">[3]</ref>. We refer to such ontologies as lightweight ontologies. Finally, for lightweight ontologies, we show how to minimize the set of constraints.</p><p>The development in the paper adopts the machinery to handle constraints developed in <ref type="bibr" target="#b5">[6]</ref> <ref type="bibr" target="#b6">[7]</ref> <ref type="bibr" target="#b7">[8]</ref>, which uses DL-Lite core with arbitrary number restrictions <ref type="bibr" target="#b2">[3]</ref>. Previous work by the authors <ref type="bibr" target="#b6">[7]</ref> introduced the equivalent of the projection operation, but considered neither the other operations nor the question of optimizing the representation of the resulting ontologies.</p><p>The paper is organized as follows. Section 2 presents the formal definition of the operations. Section 3 shows how to compute the operations for lightweight ontologies. Section 4 addresses the question of minimizing the set of constraints that result from an operation. Finally, Section 5 contains the conclusions.</p></div>
<div xmlns="http://www.tei-c.org/ns/1.0"><head n="2">A Formal Framework 2.1 A Brief Review of Basic Concepts</head><p>The definition of the operations depends only on the notion of theory, which we introduce in the context of Description Logic (DL) <ref type="bibr" target="#b3">[4]</ref>.</p><p>A DL language L is characterized by a vocabulary V, consisting of a set of atomic concepts, a set of atomic roles, and the bottom concept . The sets of concept descriptions and role descriptions of V depend on the specific description logic. An inclusion of V is an expression of the form u ⊑ v, where u and v both are concept descriptions or both are role descriptions.</p><p>An interpretation s of V consists of a nonempty set  s , the domain of s, and an interpretation function, also denoted s, with the usual definition <ref type="bibr" target="#b3">[4]</ref>. We use s(u) to indicate the value that s assigns to an expression u of V.</p><p>Let  be an inclusion of V and  be a set of inclusions of V. We say that: s satisfies  or s is a model of , denoted s ⊨ , iff s(u)  s(v); s satisfies or s is a model of , denoted s ⊨ , iff s satisfies all inclusions in  ;  logically implies , denoted  ⊨  , iff any model of  satisfies  ;  is satisfiable or consistent iff there is a model of  ;  is strongly consistent iff  is consistent and  does not logically imply A ⊑ , for some atomic concept A.</p><p>The theory of a set  of inclusions of V, denoted [], is the set of all inclusions of V which are logical consequences of .</p><p>We are specially interest in DL-Lite core with arbitrary number restrictions <ref type="bibr" target="#b2">[3]</ref>, denoted</p><formula xml:id="formula_0">N core Lite - DL</formula><p>. The sets of basic concept descriptions, concept descriptions and role descriptions in this case are defined as follows:</p><p> If P is an atomic role, then P and P  (inverse role) are role descriptions  If u is an atomic concept or the bottom concept, and p is a role description, then u and ( n p) (at-least restriction, where n is a positive integer) are basic concept descriptions and also concept descriptions</p><formula xml:id="formula_1"> If u is a concept description, then u (negated concept) is a concept description For N core Lite - DL</formula><p>, an inclusion of V is an expression of one of the forms u ⊑ v or u ⊑ v, where u and v both are basic concept descriptions. That is, an inclusion may contain a negated concept only on the right-hand side and it may not involve role descriptions.</p><p>We use the following abbreviations: "⊤" for "" (universal concept), "p" for "( 1 p)" (existential quantification), "( n p)" for "( n+1 p)" (at-most restriction) and "u | v" for "u ⊑ v" (disjunction). By an unabbreviated expression we mean an expression that does not use such abbreviations.</p><p>Finally, an ontology is a pair O=(V,) such that V is a finite vocabulary, whose atomic concepts and atomic roles are called the classes and properties of O, respectively, and  is a finite set of inclusions of V, called the constraints of O. A lightweight ontology is an ontology whose constraints are inclusions of</p><formula xml:id="formula_2">N core Lite - DL</formula><p>. From this point on, we will use the terms class, property and constraint instead of atomic concept, atomic role and inclusion, whenever reasonable.</p></div>
<div xmlns="http://www.tei-c.org/ns/1.0"><head n="2.2">Definition of the Operations</head><p>We define the following operations over ontologies.</p><formula xml:id="formula_3">Definition 1: Let O 1 = (V 1 , 1 ) and O 2 = (V 2 , 2 ) be two ontologies, W be a subset of V 1 and  be a set of constraints over V 1 . (i) The selection of O 1 = (V 1 , 1 ) for , denoted [](O 1 ), returns the ontology O S = (V S , S ), where V S = V 1 and  S =  1  . (ii) The projection of O 1 = (V 1 , 1 ) over W, denoted [W](O 1 )</formula><p>, returns the ontology O P = (V P , P ), where V P = W and  P is the set of constraints in</p><formula xml:id="formula_4">[ 1 ] that use only symbols in W. (iii) The union of O 1 = (V 1 , 1 ) and O 2 = (V 2 , 2 ), denoted O 1  O 2 , returns the on- tology O U = (V U , U ), where V U = V 1  V 2 and  U =  1   2 . (iv) The intersection of O 1 = (V 1 , 1 ) and O 2 = (V 2 , 2 ), denoted O 1  O 2 , returns the ontology O N = (V N , N ), where V N = V 1  V 2 and  N = [ 1 ]  [ 2 ]. (v) The difference of O 1 = (V 1 , 1 ) and O 2 = (V 2 , 2 ), denoted O 1  O 2 , returns the ontology O D = (V D , D ), where V D = V 1 and  D = [ 1 ]  [ 2 ].</formula><p>Note that selections can be defined as unions. We also observe that the ontology that results from each operation is unique. However, the set of constraints of the resulting ontology is not necessarily minimal, a point elaborated in Section 4.</p></div>
<div xmlns="http://www.tei-c.org/ns/1.0"><head n="2.3">An Example</head><p>The Music Ontology (MO) <ref type="bibr" target="#b10">[11]</ref> provides concepts and properties to describe artists, albums, tracks, performances, arrangements, etc. on the Semantic Web. It is used by several Linked Data sources, including MusicBrainz and BBC Music. The Music Ontology RDF schema uses terms from the Friend of a Friend (FOAF) <ref type="bibr" target="#b4">[5]</ref> and the XML Schema (XSD) vocabularies, among others. We adopt the prefixes "mo:", "foaf:" and "xsd:" to respectively refer to these vocabularies.</p><p>Figure <ref type="figure" target="#fig_0">1</ref> shows the class hierarchies of MO rooted at classes foaf:Agent and foaf:Person. Let us focus on this fragment of MO.</p><p>We first recall that FOAF has two constraints, informally formulated as follows:  each person has at most one name  foaf:Person and foaf:Organization are disjoint classes Let V 1 be the following set of terms from the FOAF and the XSD vocabularies: V 1 ={ foaf:Agent, foaf:Person, foaf:Group, foaf:Organization, foaf:name, xsd:string } Let V 2 contains the rest of the terms that appear in Figure <ref type="figure" target="#fig_0">1</ref>: V 2 ={ mo:MusicArtist, mo:CorporateBody, mo:SoloMusicArtist, mo:MusicGroup, mo:Label, mo:member_of Finally, we construct O 0 =(V 0 , 0 ), the ontology that corresponds to Figure <ref type="figure" target="#fig_0">1</ref>, in two different, albeit equivalent ways:</p><formula xml:id="formula_5">} Let O 1 =(V 1 , 1 ) be the projection [V 1 ](FOAF) of FOAF over V 1 . Let O 2 =(V 2 , 2 ) be such that  2 contains just the inclusions over V 2 shown in</formula><formula xml:id="formula_6">(1) O 0 = [ 5 ]( [V 1 ](FOAF)  O 2 ) , using the selection operation (2) O 0 = (( [V 1 ](FOAF)  O 2 )  O 5 ) ,</formula></div>
<div xmlns="http://www.tei-c.org/ns/1.0"><head>eliminating the selection operator</head><p>We stress that the expression of the right-hand side of Eq. ( <ref type="formula">1</ref>) (or Eq. ( <ref type="formula">2</ref>)) provides an explanation of how O 0 is constructed from FOAF and additional terms and constraints. </p></div>
<div xmlns="http://www.tei-c.org/ns/1.0"><head n="3.">Computing the Operations over Lightweight Ontologies</head></div>
<div xmlns="http://www.tei-c.org/ns/1.0"><head n="3.1">Constraint Graphs</head><p>This section introduces the concept of constraint graphs, which leads to procedures to compute the operations over lightweight ontologies.</p><p>We say that the complement of a basic concept description e is e, and vice-versa. If c is a concept description, then c denotes the complement of c.</p><p>Let  be a set of (unabbreviated) inclusions and  be a set of (unabbreviated) concept descriptions. The notion of constraint graphs <ref type="bibr" target="#b5">[6]</ref> captures the structure of sets of constraints.</p></div>
<div xmlns="http://www.tei-c.org/ns/1.0"><head>Definition 2:</head><p>The labeled graph g(,)=(,,) that captures  and , where  labels each node with a concept description, is defined as follows:</p><p>(i) For each concept description e that occurs on the right-or left-hand side of an inclusion in , or that occurs in , there is exactly one node in  labeled with e. If necessary, the set of nodes is augmented with new nodes so that:</p><p>(a) For each atomic concept C, there is one node in  labeled with C. (b) For each atomic role P, there is one node in  labeled with (1 P) and one node labeled with (1 P  ).</p><p>(ii) If there is a node in  labeled with a concept description e, then there must be exactly one node in  labeled with e . (iii) For each inclusion e ⊑ f in , there is an arc (M,N) in , where M and N are the nodes labeled with e and f, respectively.</p><p>(iv) If there are nodes M and N in  labeled with (m p) and (n p), where p is either P or P  and m&lt;n, then there is an arc (N,M) in . (v) If there is an arc (M,N) in , where M and N are the nodes labeled with e and f respectively, then there is an arc (K,L) in , where K and L are the nodes labeled with f and e , respectively. (vi) These are the only nodes and arcs of g().  Definition 3: The labeled graph G(,)=(,,) that represents  and , where  labels each node with a set of concept descriptions, is defined from g(,) by collapsing each strongly connected component of g(,) into a single node labeled with the descriptions that previously labeled the nodes in the strongly connected component. When  is the empty set, we simply write G() and say that the graph represents .  If a node K of G(,) is labeled with e, then K denotes the node labeled with e , and K→M indicates that there is a path in G(,) from K to M. Definition 4: Let G(,)=(,,) be the labeled graph that represents  and . We say that a node K of G(,) is a -node with level n, for a non-negative integer n, iff one of the following conditions holds: (i) K is is a -node with level 0 iff a. K is labeled with , or b. there are nodes M and N, not necessarily distinct from K, and a basic concept description h such that M and N are labeled with h and h, and K→M and K→N. (ii) K is is a -node with level n+1 iff a. There is a -node M of level n, distinct from K, such that K→M, and M is the -node with the smallest level such that K→M, or b. K is labeled with a minCardinality constraint of the form (1 P) (or of the form (1 P  )) and there is a -node M of level n, distinct from K, such that M is labeled with (1 P  ) (or with (1 P)), and M is the -node with the smallest level labeled with (1 P  ) or (1 P).  Definition 5: Let G(,)=(,,) be the labeled graph that represents  and . Let K be a node of G(,). We say that K is a -node iff K is a -node with level n, for some non-negative integer n. We also say that K is a ⊤-node iff K is a -node.   <ref type="table">2</ref>. Figure <ref type="figure" target="#fig_4">3</ref> depicts the graph G( 0 ) that represents  0 (using unabbreviated constraints). </p></div>
<div xmlns="http://www.tei-c.org/ns/1.0"><head>Table 2. Constraints of the ontology in</head></div>
<div xmlns="http://www.tei-c.org/ns/1.0"><head n="3.2">Computing the Operations</head><formula xml:id="formula_7">Let O 1 =(V 1 , 1 )</formula><p>and O 2 =(V 2 , 2 ) be two lightweight ontologies and W be a subset of V 1 .</p><p>We say that</p><formula xml:id="formula_8">O 1 =(V 1 , 1 ) and O 2 =(V 2 , 2 ) are equivalent iff V 1 =V 2 and [ 1 ]=[ 2 ]. Given O 1 =(V 1 , 1 )</formula><p>and W, procedure Projection (in Figure <ref type="figure">4</ref>) generates  2 , based on the representation graph of  1 , so that O 2 =(W, 2 ) is equivalent to the projection of</p><formula xml:id="formula_9">O 1 =(V 1 , 1 ) over W.</formula><p>Based on Theorem 1, Projection generates all constraints that involve only symbols in W and that are logical consequences of  1 . However, it avoids generating both e ⊑ f and f ⊑ e , which are equivalent. We note that Projection is non-deterministic since the set of constraints generated depends on the order that the for-loop selects pairs of nodes of G( 1 ), which is not unique.</p><p>The above argument can be generalized into a correctness proof of the Projection procedure, in the following sense. Let  1 /W denote the set of formulas that use only classes and properties in W and that are logically implied by  1 .</p><formula xml:id="formula_10">Theorem 2: Let O 1 =(V 1 , 1 )</formula><p>be an ontology and W be a subset of V 1 . Let  2 be the set of constraints which Projection outputs for  1 and W. Then,  2 is logically equivalent to  1 /W.  Procedures to compute the selection, union, intersection and difference of ontologies can be likewise defined. </p></div>
<div xmlns="http://www.tei-c.org/ns/1.0"><head n="4.">Optimizing the Representation of Lightweight Ontologies</head><p>The procedures that implement each of the operations return a set of constraints that may contain redundancies, since they work with the transitive closure of the constraint graph (c.f. the procedure in Figure <ref type="figure">4</ref>). Therefore, an interesting question immediately arises: How to minimize the set of constraints of a lightweight ontology (output by one such procedure)? We argue that this question is equivalent to finding the minimum equivalent graph (MEG) of a graph G, defined as the graph G' with the minimum set of edges such that the transitive closures of G and G' are equal. This problem has a polynomial solution for acyclic graphs and is known to be NP-hard for strongly connected graphs <ref type="bibr" target="#b0">[1]</ref>[9] <ref type="bibr" target="#b9">[10]</ref>.</p><p>Let O 1 =(V 1 , 1 ) be a lightweight ontology and G( 1 )=(,,) be the constraint graph for  1 . In what follows, we outline how construct a new set of constraints,  2 , such that  2 is a minimal set and  1 and  2 are tautologically equivalent.</p><p>Recall that G( 1 ) is acyclic and that each node of G( 1 ) is labeled with a set of expressions that are equivalent.</p><p>Since G( 1 ) is acyclic, we may construct a MEG G'=(,',) of G( 1 )=(,,) in polynomial time <ref type="bibr">[1][9]</ref>. The nodes of G' are those of G, with the same labels as in G. The procedure adopted to construct a MEG of a graph has to be modified to also drop an arc (M,N), if the arc ) M N ( , connecting the dual nodes of M and N is dropped. This modification is necessary to preserve the characteristics of constraint graphs (see Definitions 2 and 3). Then, for each arc (M,N) in ', select an expression e that labels M and an expression f that labels N, and add the constraint e ⊑ f to  2 .</p><p>The apparent problem lies in the expressions that label each node of G( 1 ). Indeed, by Definition 3, G( 1 ) is defined from g( 1 ) by collapsing each strongly connected component of g( 1 ) into a single node labeled with the expressions that previously labeled the nodes in the strongly connected component. Thus, we would have to construct a MEG, G", of each strongly connected component of g( 1 ) and generate a set of constraints from G" as before. However, constructing a MEG of a strongly connected graph is NP-hard, as indicated before.</p><p>Recall that, for any two expressions e and f that label the same node of G( 1 ), we have that  1 logically implies e  f. From the point of view of an economical ontology description, for each strongly connected component g( 1 ), we suggest to construct a minimal set of equivalences which are tautologically equivalent to the inclusions that correspond to the arcs of g( 1 ). But this new problem is equivalent to constructing a spanning tree T of each strongly connected component of g( 1 ), which can be done in polynomial time. Then, for each edge {M,N} of T, add e  f to  2 , where e labels M and f labels N in g( 1 ). If T has k nodes, we generate k-1 equivalences.</p><p>The final set of constraints,  2 , contains a minimal set of inclusions, which correspond to arcs of G', and a minimal set of equivalences, which correspond to the edges of spanning trees of the strongly connected components of g( 1 ). Finally, by construction,  1 and  2 will be tautologically equivalent.</p></div>
<div xmlns="http://www.tei-c.org/ns/1.0"><head n="5">Conclusions</head><p>In this paper, we introduced a set of concepts and procedures that promote constraint reuse in ontology design. We defined a set of operations that extend the idea of namespaces to take into account constraints and that treat ontologies as theories. We showed how to compute the operations when the ontologies are built upon DL-Lite core with arbitrary number restrictions. For such ontologies, we also showed how to minimize the set of constraints.</p><p>As for current work, from a formal perspective, we are extending the results to a more expressive variant of DL-Lite core, considered in <ref type="bibr" target="#b7">[8]</ref>, which supports a restricted form of role hierarchy. From a practical perspective, we have implemented a tool that accepts lightweight ontologies, described in OWL, and offers an interface to apply the operations to create new ontologies. We are also designing a tool to extract constraints from a Linked Data source S by combining the information in the VoiD document <ref type="bibr" target="#b1">[2]</ref> of the source, if any, with a probing technique. The tool explores the idea of the operations introduced in this paper both to compute the constraints that apply to S and to document them in an extension of the VoiD vocabulary.</p></div><figure xmlns="http://www.tei-c.org/ns/1.0" xml:id="fig_0"><head>Figure 1 :</head><label>1</label><figDesc> 2 ={ mo:SoloMusicArtist ⊑ mo:MusicArtist, mo:MusicGroup ⊑ mo:MusicArtist, mo:Label ⊑ mo:CorporateBody } Then, most of Figure 1 is captured by the union O 3 =(V 3 , 3 ) of O 1 and O 2 . The rest of Figure 1 is obtained by the selection [ 5 ](O 3 ) of O 3 , where  5 ={ mo:SoloMusicArtist ⊑ foaf:Person, mo:MusicGroup ⊑ foaf:Group, mo:CorporateBody ⊑ foaf:Organization, (1 mo:member_of) ⊑ foaf:Person, (1 mo:member_of  ) ⊑ foaf:Group } where the last two constraints indicate that the domain and range of mo:member_of are foaf:Person and foaf:Group, respectively.</figDesc></figure>
<figure xmlns="http://www.tei-c.org/ns/1.0" xml:id="fig_1"><head>Fig. 1 .</head><label>1</label><figDesc>Fig.1. The class hierarchies of MO rooted at classes foaf:Agent and foaf:Person.</figDesc></figure>
<figure xmlns="http://www.tei-c.org/ns/1.0" xml:id="fig_2"><head>Theorem 1 Theorem 1 .Example 1 :</head><label>111</label><figDesc>shows how to test logical implication for Let  be a set of that  is of the form e  f and let  = {e, f}. Then,    iff one of the following conditions holds:(i) The node of G(,) labeled with e is a -node; or (ii) The node of G(,) labeled with f is a ⊤-node; or (iii)There is a path in G(,) from the node labeled with e to the node labeled with f. The fragment of the Music Ontology shown in Figure1is formalized as the ontology O 0 =(V 0 , 0 ), where V 0 = { foaf:Agent, foaf:Person, foaf:Group, foaf:Organization, mo:MusicArtist, mo:CorporateBody, mo:SoloMusicArtist, mo:MusicGroup, mo:Label, mo:member_of, foaf:name, xsd:string } and the set of constraints  0 shown in Table</figDesc></figure>
<figure xmlns="http://www.tei-c.org/ns/1.0" xml:id="fig_3"><head>Figure 1 .</head><label>1</label><figDesc>(1 foaf:name) ⊑ foaf:Person (1 foaf:name  ) ⊑ xsd:string (1 mo:member_of) ⊑ foaf:Person (1 mo:member_of  ) ⊑ foaf:Group mo:MusicArtist ⊑ foaf:Agent foaf:Group ⊑ foaf:Agent foaf:Organization ⊑ foaf:Agent mo:SoloMusicArtist ⊑ foaf:Person mo:SoloMusicArtist ⊑ mo:MusicArtist mo:MusicGroup ⊑ mo:MusicArtist mo:MusicGroup ⊑ foaf:Group mo:CorporateBody ⊑ foaf:Organization mo:Label ⊑ mo:CorporateBody foaf:Person ⊑ foaf:Organization foaf:Person ⊑ (2 foaf:name)</figDesc></figure>
<figure xmlns="http://www.tei-c.org/ns/1.0" xml:id="fig_4"><head>Fig. 3 .</head><label>3</label><figDesc>Fig. 3. The graph G( APO ) representing the constraints of APO.</figDesc></figure>
<figure xmlns="http://www.tei-c.org/ns/1.0" xml:id="fig_5"><head>Projection( V1 ,endFig. 4 .</head><label>V14</label><figDesc>Fig. 4. Procedure Projection.</figDesc></figure>
		</body>
		<back>
			<div type="references">

				<listBibl>

<biblStruct xml:id="b0">
	<analytic>
		<title level="a" type="main">The Transitive Reduction of a Directed Graph</title>
		<author>
			<persName><forename type="first">A</forename><forename type="middle">V</forename><surname>Aho</surname></persName>
		</author>
		<author>
			<persName><forename type="first">M</forename><forename type="middle">R</forename><surname>Garey</surname></persName>
		</author>
		<author>
			<persName><forename type="first">J</forename><forename type="middle">D</forename><surname>Ullman</surname></persName>
		</author>
	</analytic>
	<monogr>
		<title level="j">SIAM J. Comp</title>
		<imprint>
			<biblScope unit="volume">1</biblScope>
			<biblScope unit="issue">2</biblScope>
			<biblScope unit="page" from="131" to="137" />
			<date type="published" when="1972">1972</date>
		</imprint>
	</monogr>
</biblStruct>

<biblStruct xml:id="b1">
	<analytic>
		<title level="a" type="main">Describing Linked Datasets with the VoID Vocabulary</title>
		<author>
			<persName><forename type="first">K</forename><surname>Alexander</surname></persName>
		</author>
		<author>
			<persName><forename type="first">R</forename><surname>Cyganiak</surname></persName>
		</author>
		<author>
			<persName><forename type="first">M</forename><surname>Hausenblas</surname></persName>
		</author>
		<author>
			<persName><forename type="first">J</forename><surname>Jun Zhao</surname></persName>
		</author>
		<ptr target="http://www.w3.org/TR/void/" />
	</analytic>
	<monogr>
		<title level="m">W3C Interest Group Note</title>
				<imprint>
			<date type="published" when="2011-03-03">03 March 2011</date>
		</imprint>
	</monogr>
</biblStruct>

<biblStruct xml:id="b2">
	<analytic>
		<title level="a" type="main">The DL-Lite family and relations</title>
		<author>
			<persName><forename type="first">A</forename><surname>Artale</surname></persName>
		</author>
		<author>
			<persName><forename type="first">D</forename><surname>Calvanese</surname></persName>
		</author>
		<author>
			<persName><forename type="first">R</forename><surname>Kontchakov</surname></persName>
		</author>
		<author>
			<persName><forename type="first">M</forename><surname>Zakharyaschev</surname></persName>
		</author>
	</analytic>
	<monogr>
		<title level="j">J. of Artificial Intelligence Research</title>
		<imprint>
			<biblScope unit="volume">36</biblScope>
			<biblScope unit="page" from="1" to="69" />
		</imprint>
	</monogr>
</biblStruct>

<biblStruct xml:id="b3">
	<analytic>
		<title level="a" type="main">Basic Description Logics</title>
		<author>
			<persName><forename type="first">F</forename><surname>Baader</surname></persName>
		</author>
		<author>
			<persName><forename type="first">W</forename><surname>Nutt</surname></persName>
		</author>
	</analytic>
	<monogr>
		<title level="m">The Description Logic Handbook: Theory, Implementation and Applications</title>
				<editor>
			<persName><forename type="first">F</forename><surname>Baader</surname></persName>
		</editor>
		<editor>
			<persName><forename type="first">D</forename><surname>Calvanese</surname></persName>
		</editor>
		<editor>
			<persName><forename type="first">D</forename><forename type="middle">L</forename><surname>Mcguiness</surname></persName>
		</editor>
		<editor>
			<persName><forename type="first">D</forename><surname>Nardi</surname></persName>
		</editor>
		<editor>
			<persName><forename type="first">P</forename><forename type="middle">F</forename><surname>Patel-Schneider</surname></persName>
		</editor>
		<meeting><address><addrLine>UK</addrLine></address></meeting>
		<imprint>
			<publisher>Cambridge U. Press</publisher>
			<date type="published" when="2003">2003</date>
			<biblScope unit="page" from="43" to="95" />
		</imprint>
	</monogr>
</biblStruct>

<biblStruct xml:id="b4">
	<monogr>
		<title level="m" type="main">FOAF Vocabulary Specification 0.98</title>
		<author>
			<persName><forename type="first">D</forename><surname>Brickley</surname></persName>
		</author>
		<author>
			<persName><forename type="first">L</forename><surname>Miller</surname></persName>
		</author>
		<imprint>
			<date type="published" when="2010-08">August 2010</date>
		</imprint>
	</monogr>
	<note>Namespace Document 9. Marco Polo Edition</note>
</biblStruct>

<biblStruct xml:id="b5">
	<analytic>
		<title level="a" type="main">Revising the Constraints of Lightweight Mediated Schemas</title>
		<author>
			<persName><forename type="first">M</forename><forename type="middle">A</forename><surname>Casanova</surname></persName>
		</author>
		<author>
			<persName><forename type="first">T</forename><surname>Lauschner</surname></persName>
		</author>
		<author>
			<persName><forename type="first">L</forename><forename type="middle">A P P</forename><surname>Leme</surname></persName>
		</author>
		<author>
			<persName><forename type="first">K</forename><forename type="middle">K</forename><surname>Breitman</surname></persName>
		</author>
		<author>
			<persName><forename type="first">A</forename><forename type="middle">L</forename><surname>Furtado</surname></persName>
		</author>
		<author>
			<persName><forename type="first">V</forename><forename type="middle">M P</forename><surname>Vidal</surname></persName>
		</author>
	</analytic>
	<monogr>
		<title level="j">Data &amp; Knowledge Engineering</title>
		<imprint>
			<biblScope unit="volume">69</biblScope>
			<biblScope unit="page" from="1274" to="1301" />
			<date type="published" when="2010">2010</date>
		</imprint>
	</monogr>
</biblStruct>

<biblStruct xml:id="b6">
	<analytic>
		<title level="a" type="main">The Role of Constraints in Linked Data</title>
		<author>
			<persName><forename type="first">M</forename><forename type="middle">A</forename><surname>Casanova</surname></persName>
		</author>
		<author>
			<persName><forename type="first">K</forename><forename type="middle">K</forename><surname>Breitman</surname></persName>
		</author>
		<author>
			<persName><forename type="first">A</forename><forename type="middle">L</forename><surname>Furtado</surname></persName>
		</author>
		<author>
			<persName><forename type="first">V</forename><forename type="middle">M P</forename><surname>Vidal</surname></persName>
		</author>
		<author>
			<persName><forename type="first">J</forename><forename type="middle">A F</forename><surname>Macêdo</surname></persName>
		</author>
	</analytic>
	<monogr>
		<title level="m">Proceedings of the Confederated International Conferences: CoopIS, DOA-SVI, and ODBASE 2011, Part II</title>
		<title level="s">Lecture Notes in Computer Science</title>
		<meeting>the Confederated International Conferences: CoopIS, DOA-SVI, and ODBASE 2011, Part II<address><addrLine>Heidelberg</addrLine></address></meeting>
		<imprint>
			<publisher>Springer</publisher>
			<date type="published" when="2011">2011</date>
			<biblScope unit="page" from="781" to="799" />
		</imprint>
	</monogr>
</biblStruct>

<biblStruct xml:id="b7">
	<analytic>
		<title level="a" type="main">An Efficient Proof Procedure for a Family of Lightweight Database Schemas</title>
		<author>
			<persName><forename type="first">M</forename><forename type="middle">A</forename><surname>Casanova</surname></persName>
		</author>
		<author>
			<persName><forename type="first">K</forename><forename type="middle">K</forename><surname>Breitman</surname></persName>
		</author>
		<author>
			<persName><forename type="first">A</forename><forename type="middle">L</forename><surname>Furtado</surname></persName>
		</author>
		<author>
			<persName><forename type="first">V</forename><forename type="middle">M P</forename><surname>Vidal</surname></persName>
		</author>
		<author>
			<persName><forename type="first">J</forename><forename type="middle">A F</forename><surname>Macêdo</surname></persName>
		</author>
	</analytic>
	<monogr>
		<title level="m">Conquering Complexity</title>
				<editor>
			<persName><forename type="first">G</forename><surname>Michael</surname></persName>
		</editor>
		<editor>
			<persName><forename type="first">Lorcan</forename><surname>Hinchey</surname></persName>
		</editor>
		<editor>
			<persName><surname>Coyle</surname></persName>
		</editor>
		<meeting><address><addrLine>London</addrLine></address></meeting>
		<imprint>
			<publisher>Springer</publisher>
			<date type="published" when="2012">2012</date>
		</imprint>
	</monogr>
</biblStruct>

<biblStruct xml:id="b8">
	<analytic>
		<title level="a" type="main">An Algorithm for Finding a Minimal Equivalent Graph of a Digraph</title>
		<author>
			<persName><forename type="first">H</forename><forename type="middle">T</forename><surname>Hsu</surname></persName>
		</author>
	</analytic>
	<monogr>
		<title level="j">Journal of the Association for Computing Machinery</title>
		<imprint>
			<biblScope unit="volume">22</biblScope>
			<biblScope unit="issue">1</biblScope>
			<biblScope unit="page" from="11" to="16" />
			<date type="published" when="1975">1975</date>
		</imprint>
	</monogr>
</biblStruct>

<biblStruct xml:id="b9">
	<analytic>
		<title level="a" type="main">Approximating the Minimum Equivalent Digraph</title>
		<author>
			<persName><forename type="first">S</forename><surname>Khuller</surname></persName>
		</author>
		<author>
			<persName><forename type="first">B</forename><surname>Raghavachari</surname></persName>
		</author>
		<author>
			<persName><forename type="first">N</forename><surname>Young</surname></persName>
		</author>
	</analytic>
	<monogr>
		<title level="j">SIAM Journal on Computing</title>
		<imprint>
			<biblScope unit="volume">24</biblScope>
			<biblScope unit="issue">4</biblScope>
			<biblScope unit="page" from="859" to="872" />
			<date type="published" when="1995">1995</date>
		</imprint>
	</monogr>
</biblStruct>

<biblStruct xml:id="b10">
	<analytic>
		<title level="a" type="main">Music Ontology Specification</title>
		<author>
			<persName><forename type="first">Y</forename><surname>Raimond</surname></persName>
		</author>
		<author>
			<persName><forename type="first">F</forename><surname>Giasson</surname></persName>
		</author>
		<ptr target="http://purl.org/ontology/mo/(RDF/XML,Turtle" />
	</analytic>
	<monogr>
		<title level="m">Specification Document -28</title>
				<imprint>
			<date type="published" when="2010-11">November 2010</date>
		</imprint>
	</monogr>
	<note>Latest version</note>
</biblStruct>

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