<!DOCTYPE article PUBLIC "-//NLM//DTD JATS (Z39.96) Journal Archiving and Interchange DTD v1.0 20120330//EN" "JATS-archivearticle1.dtd">
<article xmlns:xlink="http://www.w3.org/1999/xlink">
  <front>
    <journal-meta />
    <article-meta>
      <title-group>
        <article-title>Study of the Discovery and Redundancy of Link Keys Between Two RDF Datasets Based on Partition Pattern Structures</article-title>
      </title-group>
      <contrib-group>
        <contrib contrib-type="author">
          <string-name>NaciraAbbas</string-name>
          <xref ref-type="aff" rid="aff0">0</xref>
          <xref ref-type="aff" rid="aff2">2</xref>
        </contrib>
        <contrib contrib-type="author">
          <string-name>AlexandreBazin</string-name>
          <xref ref-type="aff" rid="aff0">0</xref>
          <xref ref-type="aff" rid="aff3">3</xref>
        </contrib>
        <contrib contrib-type="author">
          <string-name>Jérôme David</string-name>
          <email>Jerome.David@inria.fr</email>
          <xref ref-type="aff" rid="aff0">0</xref>
          <xref ref-type="aff" rid="aff1">1</xref>
        </contrib>
        <contrib contrib-type="author">
          <string-name>Amedeo Napoli</string-name>
          <email>Amedeo.Napoli@loria.fr</email>
          <xref ref-type="aff" rid="aff0">0</xref>
          <xref ref-type="aff" rid="aff2">2</xref>
        </contrib>
        <aff id="aff0">
          <label>0</label>
          <institution>Published in Pablo Cordero</institution>
          ,
          <addr-line>Ondrej Kridlo (Eds.): The 16</addr-line>
        </aff>
        <aff id="aff1">
          <label>1</label>
          <institution>Université Grenoble Alpes</institution>
          ,
          <addr-line>Inria, CNRS, Grenoble INP, LIG, F-38000 Grenoble</addr-line>
          ,
          <country country="FR">France</country>
        </aff>
        <aff id="aff2">
          <label>2</label>
          <institution>Université de Lorraine</institution>
          ,
          <addr-line>CNRS, Inria, Loria, F-54000 Nancy</addr-line>
          ,
          <country country="FR">France</country>
        </aff>
        <aff id="aff3">
          <label>3</label>
          <institution>Université de Montpellier</institution>
          ,
          <addr-line>CNRS, LIRMM, F-34095 Montpellier</addr-line>
          ,
          <country country="FR">France</country>
        </aff>
      </contrib-group>
      <abstract>
        <p>A link key between two RDF datasets 1 and  2 is a set of pairs of properties allowing to identify pairs of individuals 1 and  2 through an identity link such axs1 owl ∶ sameAs x2. In this paper, relying on and extending previous work, we introduce an original formalization of link key discovery based on the framework of Partition Pattern Structurepsps(). Our objective is to study and evaluate the redundancy of link keys based on the fact thatowl:sameAs is an equivalence relation. In thpeps concept lattice, every concept has an extent representing a link key candidate and an intent representing a partition of instances into sets of equivalent instances. Experiments show three main results. Firstly redundancy of link keys is not so significant in real-world datasets. Nevertheless, the link key discovery approach based on pps returns a reduced number of non redundant link key candidates when compared to a standard approach. Moreover, thepps-based approach is eficient and returns link keys of high quality.</p>
      </abstract>
    </article-meta>
  </front>
  <body>
    <sec id="sec-1">
      <title>1. Introduction</title>
      <p>
        In this paper, we are interested in data interlinking whose objective is to discover identity
links across two RDF datasets over the web of data1,[
        <xref ref-type="bibr" rid="ref2 ref3">2, 3</xref>
        ]. The same real world entity
can be represented in two RDF datasets by diferent subjects in RDF triples having the form
(subject, property, object). Then, for cleaning data and providing data of better quality,
it is meaningful to detect such identities. There are both numerical and logical approaches
for discovering these identities. For example, interlinking methods have been implemented in
systems such as LIMES [
        <xref ref-type="bibr" rid="ref4">4</xref>
        ] and SILK [
        <xref ref-type="bibr" rid="ref5">5</xref>
        ]. These systems use link specifications, i.e. rules that
declare whether two IRIs should be linked. Link specifications can also be specified by users or
learned from data6[
        <xref ref-type="bibr" rid="ref7 ref8">, 7, 8</xref>
        ].
      </p>
      <p>In particular, link keys which are under investigation in this paper are special kinds of
rules allowing to infer identity links between two RDF datasets. More formally, a link key
is composed of two sets of pairs of properties({(  ,   )} , {( 
′
,  ′)} ) associated with a pair of
classes( 1,  2). Then, whenever an instance1 of class 1 has the same (non empty) set of
values as an instanc e1 of class 2, i.e.   ( 1) =   ( 1) for all pairs of properties in the first set
(universal quantification), and shares at least one value for all pairs of properties in the second
set (existential quantification), i.e. ′( 1) ∩  ′( 1) ≠ ∅, then  1 and  1 denote the same entity, i.e.,
an owl:sameAs relation can be established betwee n1 and  1. More concretely, the expression
k=({(designation,title)},{(designation,title),(creator,author)}, (Book,Novel))
states that whenever an instance of classBook has the same non empty values for the property
designation as an instance of the classNovel for title, and that  and  share at least one
value for the propertiescreator and author, then  and  denote the same entity aowl:sameAs
link can be established betweenand  .</p>
      <p>
        Link keys are not provided with the datasets and algorithms are designed for automatically
discovering such link keys9,[
        <xref ref-type="bibr" rid="ref10 ref11">10, 11</xref>
        ]. Given two RDF datasets, these algorithms reduce the
search space and focus on the discovery of “link key candidates” instead of checking every
combination of pairs of properties and pairs of classes. The notion of a link key candidate
–made precise below– involves maximality and closure. Following this line, natural links were
established in 1[
        <xref ref-type="bibr" rid="ref11">0, 11</xref>
        ] between link key discovery and Formal Concept Analysis (FC1A2][).
Indeed, FCA appeared as a suitable framework for the discovery of link key candidates, which
are then evaluated thanks to appropriate quality measure9s].[
      </p>
      <p>
        Given two RDF datasets, FCA is applied in 1[0] to a binary table where rows correspond
to pairs of individuals and columns to pairs of properties. The intent of a resulting concept
corresponds to a link key candidate, which remains to be validated thanks to suitable quality
measures. The extent of the concept includes the potential identity links between individuals. A
generalization of the former approach is proposed i1n1[], which is based on pattern structures
[
        <xref ref-type="bibr" rid="ref13">13</xref>
        ] and which takes into account diferent pairs of classes at the same time in the discovery of
link keys.
      </p>
      <p>Actually, “good” link key candidates over two RDF datasets have to generate diferent and
maximal link sets, i.e., a mapping between individuals which is “close to a bijection”. However
it appears that two diferent link key candidates may generate the same link set when the link
set is considered as a partition w.r.t. thoewl:sameAs equivalence relation. This means that
these two link key candidates present a certain redundancy, and then they can be considered as
equivalent and merged in a way to be defined. This redundancy can be detected thanks to the
properties ofowl:sameAs as an equivalence relation, i.e. reflexivity, symmetry, and transitivity.
Then, the owl:sameAs relation generates partitions among pairs of individuals that can be used
for reducing the number of potential link key candidates. Indeed, two candidates relying on
the same partition are considered as redundant and can be merged. However, we do not have
a concrete idea of the importance of such redundancy and we should find a way to measure
it. This is one objective of this paper to try to materialize this redundancy and to measure its
importance.</p>
      <p>For doing so, taking inspiration from the work carried out i1n4][on the discovery of
functional dependencies, we provide a formalization of link key discovery based on “partition
pattern structures”p(ps), which allow us to take into account sets of equivalent individuals
w.r.t. owl:sameAs as partitions. Then, a pattern concept represents a link key candidate and
the related partition induced by the candidate. This approach is able to retrieve all link key
candidates as a set of “non redundant” link keys. Moreover, this link key discovery process
based on pps is operational and origin1a.lActually, this is the first time that the characteristics
of owl:sameAs as an equivalence relation are considered, and that the related partitions of pairs
of individuals are directly used for defining link key candidates. Thanksptpos, we are able to
define redundancy of link key candidates and we also introduce a new measure based on the size
of partitions for evaluating the quality of the discovered candidates. Finally, the experiments
proposed in the last part of this paper provide three main results. Firstly, the redundancy of link
keys in real-world datasets appears to be not so significant. Nevertheless, the current link key
discovery approach based onpps is eficient and returns a reduced number of non redundant
link key candidates. Moreover, thpisps-based approach returns link keys of very high quality
when compared to competitors.</p>
      <p>The summary of the paper is as follows. Sectio2npresents some basics about link keys. Then
the discovery of non-redundant link keys based on pattern structures and partition pattern
structures is made precise in Sectio3n. A running example illustrates all these constructions.
New quality measures related to non redundant link keys are defined in Secti4o.nFinally,
experiments in Section5 show the capability and eficiency of the pps-based approach in link
key discovery.</p>
    </sec>
    <sec id="sec-2">
      <title>2. Preliminaries</title>
      <sec id="sec-2-1">
        <title>2.1. RDF Data</title>
        <p>This section introduces the basic definitions relative to data interlinking with link keys. We
recall what an RDF dataset is and then we introduce two forms of link keys, namely link key
expressions and link key candidates.</p>
        <p>Definition 1 (RDF Dataset). Let  denote a set of IRIs, i.e., “Internationalized Resource Identifiers”,
 a set of blank nodes, i.e., “anonymous resources”, and  a set of literals, i.e., “string values”.</p>
        <p>An RDF dataset is a set of triples (, , ) ∈ ( ∪ ) ×  × ( ∪  ∪ ) .</p>
        <p>Let  be an RDF dataset,() = { | ∃ ,  (, , ) ∈ } denotes the set of individual identifiers,
() = { | ∃ ,  (, , ) ∈ } the set of property identifiers, and () = { | ∃  (, rdf:type, ) ∈
} the set of class identifiers.</p>
        <p>Moreover, () = { | ∃  (, rdf:type, ) ∈ } denotes the set of instances of ∈ () while
() = { | (, , ) ∈ } denotes the set of objects –or values– associated wit hthrough property
 .</p>
        <p>An identity link is an RDF triple of the for(m, owl:sameAs, ) stating that the IRIs and 
are referring to the same entity, alternativelaynd  are denoting the same individual.
Example 1. In Figure1, the RDF datasets  1 and  2 include( 1) = { 1,  2,  3,  4} and ( 2) =
{ 1,  2,  3,  4} as sets of property identifiers, and( 1) = { 1} and ( 2) = { 2} as class identifiers.
In addition, ( 1) = { 1,  2,  3,  4,  5} and  ( 2) = { 1,  2,  3,  4,  5} denote respectively the sets of
instances of class1 and class 2. Finally, considering subjec3t and property 2, the related set
of objects or the “value” of 3 for property 2 is  2( 3) = { 8,  9}.
1The present paper extends a short preliminary version published1i5n].[
with instances of class 1 while on the right-hand side the dataset 2 is populated with instances of
class 2.</p>
      </sec>
      <sec id="sec-2-2">
        <title>2.2. Link Keys</title>
        <p>Link keys are logical constructions allowing to infer identity links between instances of two
classes lying in two RDF datasets. In the following we introduce two syntactic definitions of
link keys, namely “link key expressions” and “link key candidates”. A definition of a link key
and its semantics using Description Logics interpretation is proposed 1in6].[ However, in this
paper we will stick to these two syntactic definitions for the sake of simplicity.</p>
        <p>Intuitively, alink key expression  = (,  , (</p>
        <sec id="sec-2-2-1">
          <title>1,  2)) is composed of two sets of pairs of</title>
          <p>properties, i.e. ,
and   , where</p>
          <p>is based on equality and  on non empty intersection, while
links are generated between instances of class1esand  2. More formally we have:
Definition 2 (Link key expression.) Let  1 and  2 be two RDF datasets,  = (,  , (
1,  2)) is a
link key expressionover  1 and  2 if   ⊆  (
1) ×  (
2),  ⊆  
,  1 ∈ (
1) and  2 ∈ (
2).</p>
          <p>The set of links generated by  is denoted by ()
and includes a set of pairs of instances
(, ) ∈  (</p>
          <p>1) ×  ( 2) satisfying:
(i) for all (, ) ∈ 
(ii) for all (, ) ∈   ⧵ 
, () = ()</p>
          <p>and () ≠ ∅ ,
, () ∩ () ≠ ∅</p>
          <p>.</p>
          <p>The number of link key expressions may be exponential w.r.t. the number of properties. To
reduce the search space, algorithms for link key discovery only consider “link key candidates”,
i.e., link key expressions which generate at least one link and which are “maximal” among the
set of link key expressions.</p>
          <p>PS objects (g)
The pattern structure related to dataset s 1 and  2 given in Fig. 1.</p>
          <p>Definition 3 (Link key candidate.) A link key expression  1 = ( 1,   1, ( 1,  2)) is a link key
candidateif:
(i) (</p>
          <p>1) ≠ ∅,
(ii) there does not exist another link key expression  2 = ( 2,   2, ( 1,  2)) over  1 and  2 such
that  1 ⊂  2,   1 ⊂   2, and ( 1) = ( 2).</p>
        </sec>
        <sec id="sec-2-2-2">
          <title>For example, consider the expressio ns1 and  2:</title>
          <p>(i)  1 = ({( 1,  1)}, {( 1,  1), ( 2,  2)}, ( 1,  2)),
(ii)  2 = ({( 1,  1)}, {( 1,  1)}, ( 1,  2)).</p>
        </sec>
        <sec id="sec-2-2-3">
          <title>The related link sets ar(e 1</title>
          <p>) = ( 2</p>
          <p>) = {( 3,  3)}. Then  1 and  2 are both link key expressions
but only 1 is a link key candidate as it is maximal on the link {s(e t3,  3)} while 2 is not.</p>
          <p>
            The set of link key expressions is denoted blyke, the set of link key candidates bylkc, and
we have that lkc ⊆ lke. The definition of link key candidates is based on the idea of maximality
which involves a certain form of closure. This gave rise to a number of papers studying the
potential relations existing between Formal Concept Analysis (FC12A])[and the discovery of
link keys 9[
            <xref ref-type="bibr" rid="ref10">, 10</xref>
            ]. Following the same line, we make precise in the next section two ways of
discovering link key candidates based on two extensions of FCA, pattern structu1r3e,s1[
            <xref ref-type="bibr" rid="ref7">7</xref>
            ] and
partition pattern structures1[
            <xref ref-type="bibr" rid="ref4">4</xref>
            ].
          </p>
        </sec>
      </sec>
    </sec>
    <sec id="sec-3">
      <title>3. From Link Keys to Non Redundant Link Keys</title>
      <sec id="sec-3-1">
        <title>3.1. Discovering Link Keys with Pattern Structures</title>
        <p>
          In this section we shortly recall how pattern structures can be used in the discovery of link
keys (details can be read in1[
          <xref ref-type="bibr" rid="ref1 ref18">1, 18</xref>
          ]). For the sake of simplicity and readability, we rely on a
motivating example. Then we show how “Partition Pattern Structure1s”4,[19] allow to discover
the so-called “non-redundant link key candidates” denotednarslkc.
        </p>
        <p>Example 2. Let us consider the pattern structurlekps = (, (, ⊓), )
displayed in Table1. All
details for buildinglkps and the associated pattern concept lattice are given i1n1][. In the
rows (“PS objects”), includes pairs of related instances, i.(e .,,   ) with   ∈  ( 1) and   ∈  ( 2),

which correspond to the objects olfkps. The set of potential description(s, ⊓) includes all
possible pairs of properties preceded either b∀yor ∃. For the sake of simplicity, the⊓ operator
corresponds here to set intersection.</p>
        <p>1
{( 4,  5), ( 5,  4)}
 1 = {∀( 4,  4), ∃( 4,  4)}</p>
        <p>2
{( 4,  4), ( 5,  5)}
 2 = {∀( 3,  3), ∃( 3,  3)}</p>
        <p>The mapping  relates a pair of instance(s, ) ∈  ( 1) ×  ( 2) to a description as follows: (i)
(, ) includes∀(, ) whenever() = () and () ≠ ∅ , (ii) (, ) includes∃(, ) whenever
() ∩ () ≠ ∅ . Actually, such descriptions correspond to link key expressions w.r.t. the pairs
of classes( 1,  2). In this work, we only consider the pair of clas se1sand  2, while dealing with
several pairs of classes is explained i1n1][.</p>
        <p>Based on Fig. 1, the description of( 1,  1) is given by{∃( 1,  1), ∃( 2,  2)} because  1( 1) ∩
 1( 1) ≠ ∅ and  2( 1) ∩  2( 1) ≠ ∅, while( 2,  1) = {∃( 1,  1)} because  1( 2) ∩  1( 1) ≠ ∅.
Then, ( 1,  1) ⊓ ( 2,  1) = {∃( 1,  1)} and thus ( 2,  1) ⊑ ( 1,  1). This can be read in the
pattern concept lattice displayed in Fi2gw.here the pattern concept 5 is subsumed by the
pattern concept 4, i.e., the intent{∃( 1,  1)} of  4 is included in the inten{t∃( 1,  1), ∃( 2,  2)}
of  5, while the extent{( 1,  1), ( 2,  2), ( 3,  3)} of  5 is included in the extent o f 4 which is
{( 1,  1), ( 2,  1), ( 2,  2), ( 3,  3)}.</p>
        <p>In this way, the set of all pattern concepts is organized within the pattern concept lattice in
Fig. 2. Moreover, all link key candidates are lying in the intents of the pattern concepts.</p>
      </sec>
      <sec id="sec-3-2">
        <title>3.2. Discovering Non Redundant Link Keys with Partition Pattern Structures</title>
        <p>3.2.1. Motivation: sameAs is an Equivalence Relation.</p>
        <p>Having a careful look at Fig2., one can verify that more compact link keys could be designed.
For example, in the extent o f 3, {( 1,  1), ( 1,  2), ( 2,  2), ( 3,  3)}, the three first pairs have a non
empty intersection when considered in a particular order, i1.ei.s, shared by{( 1,  1), ( 1,  2)} and
 2 is shared by{( 1,  2), ( 2,  2)}. Actually there exists a potentiaolwl:sameAs –or simplysameAs–
relation between the elements in such pairs. Being an equivalence relastiaomneA,s generates an
equivalence class. Hence, we can “merge” some of these pairs in such an equivalence class. For
example( 1,  1) and ( 1,  2) can be merged, i.e.,a1 sameAs b1 and a1 sameAs b2 yieldb1 sameAs b2
(symmetry and transitivity osfameAs). Moreover( 1,  2) and ( 2,  2) can be merged because
a1 sameAs b2 and a2 sameAs b2 yielda1 sameAs a2. Finally, froma1 sameAs a2 and a1 sameAs b1 it
comes a2 sameAs b1. Then a1, a2, b1, b2, are in the same equivalence class w.rs.ta.meAs.</p>
        <p>Two important facts should be noticed: (i) the linak2 sameAs b1, absent in 3 but present
in  4, is inferred from the extent o f 3 thanks to the properties ofsameAs while in the same
way a1 sameAs b2 could be inferred in 4, (ii) the equivalence clas{s( 1,  1,  2,  2)} which can
be built in 3 and as well in 4, allows us to merge the link keys in3 and  4 because they
have now the “same extent”. Relying on this observation, we define an equivalence relation
over the extents of pattern concepts as follows.</p>
        <p>Let us consider two RDF datasets 1 and  2, a link key , two classes 1 and  2, and the
set of instances =  ( 1) ∪  ( 2). Given  0 and   ∈  , there exists achain of sameAs
relations between 0 and   if there exists a sequence of elements 1,  2, … ,  −1 such that
x0 sameAs x1, x1 sameAs x2, … , xn−1 sameAs xn holds, where the symmetry ofsameAs may be
used. Then, we define a relation between 0 and   in  w.r.t. the link key , denoted as
 0 ≃   , if there exists a chain of sameAs relations between 0 and   . It can be checked
that ≃ is an equivalence relation assameAs itself is an equivalence relation. For example,
( 3)/≃∃( 2, 2) = {( 1,  1,  2,  2), ( 3,  3)} where ( 3) denotes the extent of 3. In the
same way, ( 4)/≃∃( 1, 1) = {( 1,  1,  2,  2), ( 3,  3)}. Then the two link keys∃( 1,  1) and
∃( 2,  2) can be “identified” or “merged” because they have the same equivalence classes.</p>
        <p>As a consequence, one may obtain more comparable sets of linked elements and thus minimize
the number of possible link key candidates. Moreover, it can be noticed that an equivalence class
determines a partition within the set of instances under study (singletons if any are omitted
here).
3.2.2. The design of a PPS for “Non Redundant Link Keys”.</p>
        <p>
          Hereafter, one main objective is to build a specific pattern structure where concepts are
related to unique equivalence classes and yield “non redundant link key candidates” denoted as
nrlkc. Here “non redundant” means any two elements ninrlkc are associated with diferent
equivalence classes. In addition, an equivalence class corresponds to a partition of the set of
instances. Accordingly, we define a “partition pattern structurep”p(s) based on descriptions
which are partitions and used to discover non redundant link key candidates. Indeed, in such
a pps, objects in the rows correspond to pairs of properties and descriptions correspond to
partitions. An example ofpps is proposed in [
          <xref ref-type="bibr" rid="ref14">14</xref>
          ] wherepps are introduced for mining functional
dependencies.
        </p>
        <p>Accordingly, we define a partition pattern structure over class e1s and  2 as a triple
(lkc, (( ), ⊓  ), ) such as:
• lkc is the set of all link key candidates w.r.t. class1esand  2 which are given by a pattern
concept lattice (as displayed in Fig2.).</p>
        <p>• (( ), ⊓  ) is the set of potential descriptions or partitions an⊓d is the “meet” of
two partitions.</p>
        <p>•  maps a link key candidat e to the partition / ≃  , which is the quotient set of w.r.t.≃ .</p>
        <p>As it can be seen in Table2, pps objects are the link key candidates already computed and lying
in the intents of the pattern concept lattice. This means that link key candidates will compose
pps-concept extents, while partitions involving elements are declared in the descriptions and
thus will composepps-concept intents. Moreover, partitions reduced to a singleton are omitted
in the descriptions of thepps objects.</p>
        <p>Let us examine a concrete example opfps based on the pattern structure given in
Table1. For  3, we have ( 3) = {( 1,  1), ( 1,  2), ( 2,  2), ( 3,  3)} and  ( 3) = {∃( 2,  2)}.
The related partition,( 3)/≃∃( 2, 2) = {( 1,  1,  2,  2), ( 3,  3)}, where singletons are
omitted, is associated with row 3 ({∃( 2,  2)}) in Table2 . In the same way, considering 4
and {∃( 1,  1)}, ( 4)/≃∃( 1, 1) is associated with row 4 ({∃( 1,  1)}) in Table2. Moreover,
( 4)/≃∃( 1, 1) = {( 1,  1,  2,  2), ( 3,  3)} and is equal to( 3)/≃∃( 2, 2). As already
observed, 3 and  4 are inducing the same partition and can be “merged”. The othpeprs objects,
namely 1,  2,  5, and  6, are obtained from the corresponding pattern concepts in F2igi.n the
same way. Finally, thepps over classe s1 and  2 related to the dataset s 1 and  2 is displayed
in Table2.</p>
        <p>
          The meet –or similarity– operation used to compare the rows in tphpes corresponds to the
meet of two partitions 1 and  2 over  and is denoted by 1 ⊓  2. This meet
operation is classically defined as the intersection of the respective equivalence classes, also
known as the “coarsest common refinement of the two partitions” (see1[
          <xref ref-type="bibr" rid="ref4">4</xref>
          ]). For example the
meet ( 4) ⊓ ( 5) is given by {( 1,  1,  2,  2), ( 3,  3)} ⊓ {( 1,  1), ( 2,  2), ( 3,  3)} which
yields the partition{( 1,  1), ( 2,  2), ( 3,  3)}. In particular, this means tha(t 4) ⊓ ( 5) = ( 5)
and thus that ( 5) ⊑ ( 4).
        </p>
        <p>Based on this meet operation, thepps concept lattice is constructed and shown in Fi3g. .The
extent of apps concept includes the and the  parts of a link key candidat(e,  , ( 1,  2)) inlkc.
For example, the intent of 6 is {( 3,  3)} and its extent is 6, i.e., {∀( 1,  1), ∃( 1,  1), ∃( 2,  2)}.
As all elements in the extents of thpeps concept lattice, 6 is an element ofnrlkc, i.e., a non
redundant link key candidate. Moreov er6, corresponds to a closed set and thus verifies
maximality, and it is non redundant w.r.t. the partition in the associated intent, i.e., no other link key
candidate induces the same partition.
3.2.3. Discussion: From LKC to NRLKC.</p>
        <p>We now discuss what is gained in relying on pattern structures and then on partition pattern
structures. Actually, the discovery of link key candidatleksc() is based on the construction of
the pattern concept lattice. Then the construction of tphpes concept lattice yielding the non
redundant link key candidates should be considered as a “refinement” where equivalent link key
candidates, i.e., link key candidates inducing the same partition, are merged. For example, both
concepts 3 and  4 in Fig. 2 are merged into a single concept 34 in Fig. 3. The resulting
pps concept lattice is of smaller size and more concise as link key candidates in the concept
extents are non redundant.</p>
        <p>The relations existing betweelnkc and nrlkc can be characterized as follows. By construction,
nrlkc ⊆ lkc as the discovery of non redundant link keys is based olknc, i.e., the link key
candidates lying in the intents of concepts in the pattern concept lattice. Then, the candidates
which have the same equivalence classes w.r.t. thseameAs relation are merged to produce the
non redundant link key candidates innrlkc. Thus, it comes thatnrlkc ⊆ lkc and that |nrlkc |
≤ |lkc | (where |X| denotes the cardinality of set X). In other words, a non redundant link key
candidate is always a link key candidate while the converse is not true.</p>
        <p>The definition of nrlkc allows us to introduce a new quality measure for evaluating and
validating non redundant link key candidates. In the next section we make precise this new
quality measure and we discuss the benefits related to the discovery of non redundant link key
candidates.
{|(, ) ∈ }</p>
        <p>and  2() = {|(, ) ∈ }
The discriminability of  is () =
.</p>
        <p>(|
1()|, | 2()|) .</p>
        <p>||</p>
      </sec>
    </sec>
    <sec id="sec-4">
      <title>4. Quality Measures for Non Redundant Link Key Candidates</title>
      <p>Not all link key candidates are eligible to be final link keys. Some candidates can be too general or
related to noise in the data and thus they may generaotewl:sameAs links which are not correct or
have a bad quality. For example the link key candida(t{e}, {(country,country)}, (Person,Human))
states that two individuals (subjects) sharing the same country represent the same person, and
this is obviously not true. The candidat(e{}, {(name,title)}, (Person,Book)) may be discovered
by chance and will generate non correct links as well.</p>
      <p>
        An ideal link key candidate should be “correct” and “complete”, and specific “quality measures”
are defined for assessing these properties. In a supervised setting, when a set of reference links
is available, the correctness of a link key candidate is measured thanks to “precision” and the
completeness thanks to “recall”. In an unsupervised setting as this is the case here, the measures
of “coverage” and “discriminability” are defined over the set of links directly generated by a link
key candidate [
        <xref ref-type="bibr" rid="ref9">9</xref>
        ]. The global quality of a link key candidate is then estimated thanks to the
harmonic mean of these two measures.
      </p>
      <p>The coverage of a set  of links over 1 and  2 is  (, 
1,  2) =</p>
      <p>where 1() =
| 1() ∪  2()|
| ( 1) ∪  ( 2)|

Link Key Candidates</p>
      <p>Singleton Partition</p>
      <p>1
 1{∀( 4, 4),∃( 4, 4)}
{( 4, 5),( 5, 4)}</p>
      <p>2
 2{∀( 3, 3),∃( 3, 3)}
{( 4, 4),( 5, 5)}</p>
      <p>6
{( 3, 3)}
 6{∀( 1, 1),∃( 1, 1),∃( 2, 2)}
 7
∅</p>
      <p>5</p>
      <p>Coverage and discriminability evaluate how close a set of links is to a total, respectively
bijective, mapping. Coverage is maximum when all instances of the considered classes are
linked to at least another instance, while discriminability is maximum when instances are linked
to at most one instance.
key candidate 34 = { 3,  4} interpreted as “3 or  4”.</p>
      <p>In the present setting, we are interested in the “redundancy” of link key candidates, and we
would like to evaluate the quality of “non redundant” candidates. A link key candidaiste
said to be “redundant” in ⊆</p>
      <p>lkc if there exists another link key candidaℎte∈  such that
 /≃  =  /≃ ℎ, i.e.,  generates the same partition asℎ. This is the case in the running example
for the link key candidates3 and  4. One main consequence of detecting redundancy is to
reduce the number of candidates by merging candidates inducing the same partition. Then,
since≃ 3 and ≃ 4 induce the same partition, 3 and  4 are merged into a non redundant link
Accordingly, we introduce the new quality measur()e
that is compliant with the
semantics ofsameAs and defined w.r.t. the partition associated with the equivalence relatio≃n :
{ ∈  /≃  | || &gt; 1 } | where =  ( 1) ∪  ( 2) and  /≃  is the quotient set of w.r.t.</p>
      <p>3
) = (</p>
      <p>4) = |{( 1,  1,  2,  2), ( 3,  3)}| = 2. The lower bound o f()
is 1 since  generates at least one link. The upper bound (is| (
achieved when determines a 1-1 mapping. Moreover, pSize can be normalized i n(t)o =
1)|, | ( 2)|) and this is
()/| / ≃</p>
      <p>|. Then (
this time singletons are counted.</p>
      <p>3) = 2/6 as  / ≃  3 = {( 1,  1,  2,  2), ( 3,  3),  4,  4,  5,  5}, where</p>
      <p>The normalized measure() evaluates how close are1 and  2 w.r.t. ≃ , and is maximal
when all instances are linked. However, this is not always satisfactory, especially when the
cardinalities of the two classes significantly difer (i.e., classes are not balanced). Then, it is
more accurate to maximize the measure as soon as all instances of one class are linked as
follows: () = ()/(| ( 1)/≃ |, | ( 2)/≃ |) (also known as the “Szymkiewicz–Simpson
partition coeficient”). For example, ( 3) = 2/4 with:
( 3) = |{( 1,  1,  2,  2), ( 3,  3)}|/(|{( 1,  2),  3,  4,  5}|, |{( 1,  2),  3,  4,  5}|).</p>
    </sec>
    <sec id="sec-5">
      <title>5. Experiments</title>
      <sec id="sec-5-1">
        <title>5.1. Datasets and experimental settings</title>
        <p>We run experiments on DB-Yago datasets provided in20[]. These datasets are used by the
approaches to which we compare our results in the last series of experiments. They have been
rewritten into Terse RDF Triple Language (Turtle) which is a syntax for expressing RDF data
[21]. They are derived from DBpedia and Yago and organized into nine tasks. One particular
task consists in finding links between instances of a class in DBpedia and instances of a class in
Yago, e.g., db:Actor and yago:Actor. A set of reference links (i.eo.w,l:sameAs links) denoted
by   is provided for each task. The statistics of DB-Yago datasets are given in Tab3l.e</p>
        <p>
          Experiments were run on a MacBook Pro 2018 with Intel Core i7-8850H@2,6 GHz, 16GB
of RAM. The link key candidates are provided by a tool callLeidnkex2 in which we have
implemented thelkps algorithm i.e. the link key discovery algorithm based on pattern structures
proposed in [
          <xref ref-type="bibr" rid="ref11">11</xref>
          ]. A basic text normalization consisting in removing diacritics, tokenizing and
sorting the resulting bag of tokens is performed.
        </p>
      </sec>
      <sec id="sec-5-2">
        <title>5.2. Redundancy of Link Key Candidates is not so Significant</title>
        <p>In Table3, column l|kc| represents the number of link key candidates discoveredlbkyps
algorithm while columnnr|lkc| represents the number of non redundant link key candidates.
In most of the tasks, we can observe thatn|rlkc| is equal to l|kc|, except for the tasksActor
and Film where |nrlkc| is lower thanl|kc| by 1% and by 5% respectively. This means that,
in general, link key candidates produce diferent partitions and only a few are redundant. By
contrast, if redundancy does not significantly reduce the number of link key candidates, it gives
a good idea of the compactness of partitions related to link key candidates.</p>
        <p>Nevertheless, even if redundancy is not so significant, we decided to compare the quality
of the resulting sets of candidates measured wit h and the results of competitors, namely
keys and conditional keys as they are studied in20[].</p>
      </sec>
      <sec id="sec-5-3">
        <title>5.3. Non Redundant Candidates, Classical Keys and Conditional Keys</title>
        <p>The  measure is used to evaluate and select the best link key candidates, –in this experiment
the link key candidate ranked first– in every task listed in Tab3l.eThen, we compare recall,
precision, and F-measure of the links generated by the best link key candidates selected by
2Linkex is available online at https://gitlab.inria.fr/moex/linkex.
|lkc|
 against interlinking approaches providing classical keys and conditional keys as reported
in [20].</p>
        <p>In Figure4 we can observe that: (i) recall of link keys is significantly better than recall of
classical and conditional keys, (ii) precision of classical and conditional keys is slightly better
than precision of link keys in most of the tasks, (iii) F-measure is much higher for selected link
key candidates than for classical and conditional keys.</p>
        <p>Link keys have a better recall because they are more flexible than classical keys, i.e., a link
key is not necessarily a pair of keys and an instance of cl a1ssmay be linked to many instances
of class 2.</p>
        <p>For summarizing, it can be concluded that considering the best link key candidates selected
by  will ensure a higher interlinking quality compared to classical and conditional keys. We
also observe that the best link key according to discriminability and coverage is the same that
the best non redundant link key selected thanks to . Actually, theActor dataset makes an
exception: the link key candidate selected with obtains an F-measure of0.95 contrasting
the score of0.34 obtained with coverage and discriminability. In addition, contrasting key-based
approaches, link key discovery does not require any prior knowledge such as property or class
alignments.
|nrlkc| time</p>
      </sec>
    </sec>
    <sec id="sec-6">
      <title>6. Synthesis and Conclusion</title>
      <p>This paper introduces a formalization of link key discovery based on partition pattern structures
(pps). This approach allows to discover the sentrlkc of link key candidates which are not
redundant w.r.t. theowl:sameAs equivalence relation, while still being correct and complete. In
addition, new appropriate quality measures are proposed.</p>
      <p>Practically, we observe in experiments that the redundancy of link key candidates in public
datasets is rather rare. Nevertheless, the experiments and the associated results show that
link key based onpps obtain better F-measure values than two other key-based approaches to
data-interlinking.</p>
      <p>Among the perspectives, a first one is to consolidate the theory and practice of link key
discovery based onpps introduced and detailed in this paper. A second and very important
direction of investigation is related to the discovery of “fuzzy link keys”. We make the hypothesis
that the redundancy of link key candidates is rather rare because we are using the crisp equality
operator when we are building the link key candidates. Instead, in considering the discovery of
link key candidates as depending on a similarity relation, i.e., reflexive and symmetric –also
called a tolerance relation– rather than on an equality, then we could propose a formalization
of fuzzy link key candidates in the spirit of approximate-matching dependencies as they are
studied in [19]. We could also expect much more diferences between crisp and fuzzy link key
candidates. In addition, a reduction of the size of the concept lattice relatednrtolkc could also
be investigated thanks to similarities between partitions.
Link Keys in an LKPS Concept Lattice, in: A. Braud, A. Buzmakov, T. Hanika, F. L. Ber
(Eds.), Proceedings of the 16th International Conference on Formal Concept Analysis
(ICFCA), Lecture Notes in Computer Science 12733, Springer, 2021, pp. 243–251.
[19] J. Baixeries, V. Codocedo, M. Kaytoue, A. Napoli, Characterizing Approximate-Matching
Dependencies in Formal Concept Analysis with Pattern Structures, Discrete Applied
Mathematics 249 (2018) 18–27.
[20] D. Symeonidou, L. Galárraga, N. Pernelle, F. Saïs, F. M. Suchanek, VICKEY: Mining
Conditional Keys on Knowledge Bases, in: Proceedings of 16th International Semantic
Web Conference (ISWC), LNCS 10587, Springer, 2017, pp. 661–677.
[21] D. Beckett, T. Berners-Lee, E. Prud’hommeaux, G. Carothers, RDF 1.1 Turtle, W3C
Recommendation, W3C, 2014.https://www.w3.org/TR/turtle./</p>
    </sec>
  </body>
  <back>
    <ref-list>
      <ref id="ref1">
        <mixed-citation>
          [1]
          <string-name>
            <given-names>A.</given-names>
            <surname>Ferrara</surname>
          </string-name>
          ,
          <string-name>
            <given-names>A.</given-names>
            <surname>Nikolov</surname>
          </string-name>
          ,
          <string-name>
            <given-names>F.</given-names>
            <surname>Scharfe</surname>
          </string-name>
          ,
          <article-title>Data Linking for the Semantic Web</article-title>
          ,
          <source>International Journal of Semantic Web and Information Systems</source>
          <volume>7</volume>
          (
          <year>2011</year>
          )
          <fpage>46</fpage>
          -
          <lpage>76</lpage>
          .
        </mixed-citation>
      </ref>
      <ref id="ref2">
        <mixed-citation>
          [2]
          <string-name>
            <given-names>P.</given-names>
            <surname>Christen</surname>
          </string-name>
          ,
          <article-title>Data Matching - Concepts and Techniques for Record Linkage</article-title>
          , Entity Resolution, and Duplicate Detection, Springer,
          <year>2012</year>
          .
        </mixed-citation>
      </ref>
      <ref id="ref3">
        <mixed-citation>
          [3]
          <string-name>
            <given-names>M.</given-names>
            <surname>Nentwig</surname>
          </string-name>
          ,
          <string-name>
            <given-names>M.</given-names>
            <surname>Hartung</surname>
          </string-name>
          , A.
          <string-name>
            <surname>-C. Ngonga Ngomo</surname>
            ,
            <given-names>E.</given-names>
          </string-name>
          <string-name>
            <surname>Rahm</surname>
          </string-name>
          ,
          <article-title>A survey of current Link Discovery frameworks</article-title>
          ,
          <source>Semantic Web Journal</source>
          <volume>8</volume>
          (
          <year>2017</year>
          )
          <fpage>419</fpage>
          -
          <lpage>436</lpage>
          .
        </mixed-citation>
      </ref>
      <ref id="ref4">
        <mixed-citation>
          [4]
          <string-name>
            <given-names>A. N.</given-names>
            <surname>Ngomo</surname>
          </string-name>
          , S. Auer, LIMES
          <article-title>- A Time-Eficient Approach for Large-Scale Link Discovery on the Web of Data</article-title>
          , in: T. Walsh (Ed.),
          <source>Proceedings of the 22nd International Joint Conference on Artificial Intelligence (IJCAI)</source>
          ,
          <source>IJCAI/AAAI</source>
          ,
          <year>2011</year>
          , pp.
          <fpage>2312</fpage>
          -
          <lpage>2317</lpage>
          .
        </mixed-citation>
      </ref>
      <ref id="ref5">
        <mixed-citation>
          [5]
          <string-name>
            <given-names>J.</given-names>
            <surname>Volz</surname>
          </string-name>
          ,
          <string-name>
            <given-names>C.</given-names>
            <surname>Bizer</surname>
          </string-name>
          ,
          <string-name>
            <given-names>M.</given-names>
            <surname>Gaedke</surname>
          </string-name>
          , G. Kobilarov,
          <string-name>
            <surname>Silk - A Link Discovery</surname>
          </string-name>
          <article-title>Framework for the Web of Data</article-title>
          , in: C. Bizer,
          <string-name>
            <given-names>T.</given-names>
            <surname>Heath</surname>
          </string-name>
          ,
          <string-name>
            <given-names>T.</given-names>
            <surname>Berners-Lee</surname>
          </string-name>
          ,
          <string-name>
            <surname>K.</surname>
          </string-name>
          Idehen (Eds.),
          <source>Proceedings of the WWW2009 Workshop on Linked Data on the Web (LDOW)</source>
          ,
          <source>CEUR Workshop Proceedings 538</source>
          ,
          <year>2009</year>
          .
        </mixed-citation>
      </ref>
      <ref id="ref6">
        <mixed-citation>
          [6]
          <string-name>
            <given-names>R.</given-names>
            <surname>Isele</surname>
          </string-name>
          ,
          <string-name>
            <given-names>C.</given-names>
            <surname>Bizer</surname>
          </string-name>
          ,
          <article-title>Active learning of expressive linkage rules using genetic programming</article-title>
          ,
          <source>Journal of web semantics 23</source>
          (
          <year>2013</year>
          )
          <fpage>2</fpage>
          -
          <lpage>15</lpage>
          .
        </mixed-citation>
      </ref>
      <ref id="ref7">
        <mixed-citation>
          [7]
          <string-name>
            <given-names>A. N.</given-names>
            <surname>Ngomo</surname>
          </string-name>
          ,
          <string-name>
            <given-names>K.</given-names>
            <surname>Lyko</surname>
          </string-name>
          ,
          <article-title>EAGLE: Eficient Active Learning of Link Specifications Using Genetic Programming</article-title>
          , in: E. Simperl,
          <string-name>
            <given-names>P.</given-names>
            <surname>Cimiano</surname>
          </string-name>
          ,
          <string-name>
            <given-names>A.</given-names>
            <surname>Polleres</surname>
          </string-name>
          , Ó. Corcho, V. Presutti (Eds.),
          <source>Proceedings of the 9th Extended Semantic Web Conference (ESWC, Lecture Notes in Computer Science 7295</source>
          , Springer,
          <year>2012</year>
          , pp.
          <fpage>149</fpage>
          -
          <lpage>163</lpage>
          .
        </mixed-citation>
      </ref>
      <ref id="ref8">
        <mixed-citation>
          [8]
          <string-name>
            <given-names>A. N.</given-names>
            <surname>Ngomo</surname>
          </string-name>
          ,
          <string-name>
            <given-names>K.</given-names>
            <surname>Lyko</surname>
          </string-name>
          ,
          <article-title>Unsupervised learning of link specifications: deterministic vs. non-deterministic</article-title>
          , in: P. Shvaiko,
          <string-name>
            <given-names>J.</given-names>
            <surname>Euzenat</surname>
          </string-name>
          ,
          <string-name>
            <given-names>K.</given-names>
            <surname>Srinivas</surname>
          </string-name>
          ,
          <string-name>
            <given-names>M.</given-names>
            <surname>Mao</surname>
          </string-name>
          , E. Jiménez-Ruiz (Eds.),
          <source>Proceedings of the 8th International Workshop on Ontology Matching (at ISWC)</source>
          ,
          <source>CEUR Workshop Proceedings 1111</source>
          ,
          <year>2013</year>
          , pp.
          <fpage>25</fpage>
          -
          <lpage>36</lpage>
          .
        </mixed-citation>
      </ref>
      <ref id="ref9">
        <mixed-citation>
          [9]
          <string-name>
            <given-names>M.</given-names>
            <surname>Atencia</surname>
          </string-name>
          ,
          <string-name>
            <given-names>J.</given-names>
            <surname>David</surname>
          </string-name>
          ,
          <string-name>
            <given-names>J.</given-names>
            <surname>Euzenat</surname>
          </string-name>
          ,
          <article-title>Data interlinking through robust linkkey extraction</article-title>
          ,
          <source>in: Proceedings of ECAI</source>
          ,
          <year>2014</year>
          , pp.
          <fpage>15</fpage>
          -
          <lpage>20</lpage>
          .
        </mixed-citation>
      </ref>
      <ref id="ref10">
        <mixed-citation>
          [10]
          <string-name>
            <given-names>M.</given-names>
            <surname>Atencia</surname>
          </string-name>
          ,
          <string-name>
            <given-names>J.</given-names>
            <surname>David</surname>
          </string-name>
          ,
          <string-name>
            <given-names>J.</given-names>
            <surname>Euzenat</surname>
          </string-name>
          ,
          <string-name>
            <given-names>A.</given-names>
            <surname>Napoli</surname>
          </string-name>
          ,
          <string-name>
            <given-names>J.</given-names>
            <surname>Vizzini</surname>
          </string-name>
          ,
          <article-title>Link key candidate extraction with relational concept analysis</article-title>
          ,
          <source>Discrete applied mathematics 273</source>
          (
          <year>2020</year>
          )
          <fpage>2</fpage>
          -
          <lpage>20</lpage>
          .
        </mixed-citation>
      </ref>
      <ref id="ref11">
        <mixed-citation>
          [11]
          <string-name>
            <given-names>N.</given-names>
            <surname>Abbas</surname>
          </string-name>
          ,
          <string-name>
            <given-names>J.</given-names>
            <surname>David</surname>
          </string-name>
          ,
          <string-name>
            <given-names>A.</given-names>
            <surname>Napoli</surname>
          </string-name>
          ,
          <article-title>Discovery of Link Keys in RDF Data Based on Pattern Structures: Preliminary Steps</article-title>
          , in: F. J.
          <string-name>
            <surname>Valverde-Albacete</surname>
            ,
            <given-names>M.</given-names>
          </string-name>
          Trnecka (Eds.),
          <source>Proceedings of the International Conference on Concept Lattices and Their Applications (CLA)</source>
          ,
          <source>CEUR Workshop Proceedings 2668</source>
          ,
          <year>2020</year>
          , pp.
          <fpage>235</fpage>
          -
          <lpage>246</lpage>
          .
        </mixed-citation>
      </ref>
      <ref id="ref12">
        <mixed-citation>
          [12]
          <string-name>
            <given-names>B.</given-names>
            <surname>Ganter</surname>
          </string-name>
          ,
          <string-name>
            <given-names>R.</given-names>
            <surname>Wille</surname>
          </string-name>
          ,
          <source>Formal Concept Analysis: Mathematical Foundations</source>
          , Springer,
          <year>1999</year>
          .
        </mixed-citation>
      </ref>
      <ref id="ref13">
        <mixed-citation>
          [13]
          <string-name>
            <given-names>B.</given-names>
            <surname>Ganter</surname>
          </string-name>
          ,
          <string-name>
            <given-names>S. O.</given-names>
            <surname>Kuznetsov</surname>
          </string-name>
          , Pattern Structures and Their Projections, in: H. S. Delugach, G. Stumme (Eds.),
          <source>Proceedings of the International Conference on Conceptual Structures (ICCS), Lecture Notes in Computer Science 2120</source>
          , Springer,
          <year>2001</year>
          , pp.
          <fpage>129</fpage>
          -
          <lpage>142</lpage>
          .
        </mixed-citation>
      </ref>
      <ref id="ref14">
        <mixed-citation>
          [14]
          <string-name>
            <given-names>J.</given-names>
            <surname>Baixeries</surname>
          </string-name>
          ,
          <string-name>
            <given-names>M.</given-names>
            <surname>Kaytoue</surname>
          </string-name>
          ,
          <string-name>
            <given-names>A.</given-names>
            <surname>Napoli</surname>
          </string-name>
          ,
          <article-title>Characterizing functional dependencies in formal concept analysis with pattern structures</article-title>
          ,
          <source>Annals of Mathematics and Artificial Intelligence</source>
          <volume>72</volume>
          (
          <year>2014</year>
          )
          <fpage>129</fpage>
          -
          <lpage>149</lpage>
          .
        </mixed-citation>
      </ref>
      <ref id="ref15">
        <mixed-citation>
          [15]
          <string-name>
            <given-names>N.</given-names>
            <surname>Abbas</surname>
          </string-name>
          ,
          <string-name>
            <given-names>A.</given-names>
            <surname>Bazin</surname>
          </string-name>
          ,
          <string-name>
            <given-names>J.</given-names>
            <surname>David</surname>
          </string-name>
          ,
          <string-name>
            <given-names>A.</given-names>
            <surname>Napoli</surname>
          </string-name>
          ,
          <article-title>Non-Redundant Link Keys in RDF Data: Preliminary Steps</article-title>
          ,
          <source>in: Proceedings of the FCA4AI Workshop at IJCAI, CEUR Workshop Proceedings 2972</source>
          ,
          <year>2021</year>
          , pp.
          <fpage>125</fpage>
          -
          <lpage>130</lpage>
          .
        </mixed-citation>
      </ref>
      <ref id="ref16">
        <mixed-citation>
          [16]
          <string-name>
            <given-names>M.</given-names>
            <surname>Atencia</surname>
          </string-name>
          ,
          <string-name>
            <given-names>J.</given-names>
            <surname>David</surname>
          </string-name>
          ,
          <string-name>
            <given-names>J.</given-names>
            <surname>Euzenat</surname>
          </string-name>
          ,
          <article-title>On the relation between keys and link keys for data interlinking</article-title>
          ,
          <source>Semantic Web Journal</source>
          <volume>12</volume>
          (
          <year>2021</year>
          )
          <fpage>547</fpage>
          -
          <lpage>567</lpage>
          .
        </mixed-citation>
      </ref>
      <ref id="ref17">
        <mixed-citation>
          [17]
          <string-name>
            <given-names>M.</given-names>
            <surname>Kaytoue</surname>
          </string-name>
          ,
          <string-name>
            <given-names>S. O.</given-names>
            <surname>Kuznetsov</surname>
          </string-name>
          ,
          <string-name>
            <given-names>A.</given-names>
            <surname>Napoli</surname>
          </string-name>
          ,
          <string-name>
            <given-names>S.</given-names>
            <surname>Duplessis</surname>
          </string-name>
          ,
          <article-title>Mining Gene Expression Data with Pattern Structures in Formal Concept Analysis</article-title>
          ,
          <source>Information Sciences 181</source>
          (
          <year>2011</year>
          )
          <fpage>1989</fpage>
          -
          <lpage>2001</lpage>
          .
        </mixed-citation>
      </ref>
      <ref id="ref18">
        <mixed-citation>
          [18]
          <string-name>
            <given-names>N.</given-names>
            <surname>Abbas</surname>
          </string-name>
          ,
          <string-name>
            <given-names>A.</given-names>
            <surname>Bazin</surname>
          </string-name>
          ,
          <string-name>
            <given-names>J.</given-names>
            <surname>David</surname>
          </string-name>
          ,
          <string-name>
            <given-names>A.</given-names>
            <surname>Napoli</surname>
          </string-name>
          ,
          <article-title>Sandwich: An Algorithm for Discovering Relevant</article-title>
        </mixed-citation>
      </ref>
    </ref-list>
  </back>
</article>