<!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>Single-Focus Broadening Navigation in Concept Lattices</article-title>
      </title-group>
      <contrib-group>
        <contrib contrib-type="author">
          <string-name>CSIR Meraka Computer Science Division</string-name>
          <xref ref-type="aff" rid="aff0">0</xref>
        </contrib>
        <aff id="aff0">
          <label>0</label>
          <institution>Stellenbosch University</institution>
          ,
          <country country="ZA">South Africa</country>
        </aff>
      </contrib-group>
      <fpage>32</fpage>
      <lpage>43</lpage>
      <abstract>
        <p>Formal concept analysis has been used to support information retrieval tasks in many domains, in particular the traditional \by keyword" document search with a conjunctive query interpretation. However, support for exploratory search or browsing needs new navigation algorithms that allow users (i) to continuously update the current query and (ii) to broaden as well as re ne the result set. In this paper we investigate a step-wise navigation algorithm that supports both broadening and re nement operations. Our navigation operations maintain some useful algebraic properties. We motivate our approach on a dataset of wine reviews, which contains di erent facets of information.</p>
      </abstract>
      <kwd-group>
        <kwd>Information Retrieval</kwd>
        <kwd>exploratory search</kwd>
        <kwd>step-wise navigation</kwd>
        <kwd>broadening navigation</kwd>
        <kwd>Formal Concept Analysis</kwd>
      </kwd-group>
    </article-meta>
  </front>
  <body>
    <sec id="sec-1">
      <title>Introduction</title>
      <p>
        Formal concept analysis has been used to support information retrieval (IR) [
        <xref ref-type="bibr" rid="ref1 ref2">1,
2</xref>
        ] tasks in many domains [
        <xref ref-type="bibr" rid="ref3 ref4">3, 4</xref>
        ] and to implement di erent IR algorithms. The
traditional approach [
        <xref ref-type="bibr" rid="ref5">5</xref>
        ] to IR using formal concept analysis views the documents
as objects and their associated meta-data and extracted terms as attributes. The
concept lattice is then computed from these document contexts. Each concept's
intent represents a possible query (interpreted as the conjunction of all
corresponding terms), with the extent forming the set of retrieved documents [
        <xref ref-type="bibr" rid="ref5">5</xref>
        ].
      </p>
      <p>
        One particular IR task, and the one that we are interested in, is exploratory
search [
        <xref ref-type="bibr" rid="ref6">6</xref>
        ] or browsing [
        <xref ref-type="bibr" rid="ref7 ref8">7, 8</xref>
        ]. It is aimed at familiarizing the user with the
underlying data through serendipitous navigation, and so complements the traditional,
direct keyword lookup-based document retrieval. Browsing is supported in graph
structures by moving from vertex to vertex where each vertex represents the
current query [
        <xref ref-type="bibr" rid="ref7">7</xref>
        ]. Therefore, in order to implement browsing with concept lattices,
we need a step-wise navigation algorithm that allows users (i) to incrementally
update the current query and (ii) to restrict (i.e., move down in the lattice) as
well as broaden (i.e., move up in the lattice) the result set. In this paper we
focus on such step-wise navigation algorithms and in particular a broadening
navigation approach.
      </p>
      <p>
        Concept lattices can in principle be navigated directly, by following the
subconcept relation to move from one concept to another concept in its direct
neighborhood [
        <xref ref-type="bibr" rid="ref7">7</xref>
        ]. However, this only allows for small navigation steps and thus
restricts the serendipitous nature of the browsing operation and becomes
impractical for large lattices. Instead, we aim at large step navigation algorithms
that allow users to select and deselect arbitrary attributes and rely on the meet
and join operations to move between concepts [
        <xref ref-type="bibr" rid="ref9">9</xref>
        ].
      </p>
      <p>Large-step navigation algorithms should ideally satisfy a number of
properties that ensure that their behavior is transparent to users. First, they should
be Markovian, i.e., rely only on the current query concept and the new selection
(or de-selection) to determine the next concept as result of the navigation step.
This means that users do not need to remember the navigation history in order
to understand the results. Second, they should be Abelian, i.e., the order of the
navigation steps should have no e ect on the next navigation result. This allows
users a certain degree of freedom in how they navigate through the underlying
document collection. Finally, they should have the single focus property, i.e.,
each query result can be represented by a single concept in the lattice. If the
concept lattices constructed from the document contexts were Boolean lattices
then these properties would follow automatically; however, this is not the case
for most document collections.</p>
      <p>
        If we follow a purely conjunctive query interpretation (i.e., consider all query
terms to be connected by the AND operator), we can use the lattice's meet
operation as implementation of the AND operator [
        <xref ref-type="bibr" rid="ref10">10</xref>
        ] in a document-term concept
lattice. Moreover, the navigation algorithm is then by construction Markovian
and Abelian, and has the single focus property. However, this does not
provide us with disjunctive queries, or, with any broadening navigation operations.
We therefore investigate broadening navigation approaches that maintain only
a single focus concept.
      </p>
      <p>It remains unclear what exactly constitutes broadening navigation, and there
are several di erent operations that extend the query result and can be
considered as \broadening".</p>
      <p>
        { We can de-select a previously selected term; under a purely conjunctive query
interpretation the new focus is then computed as the meet of the introducing
concepts of the remaining terms (although Lindig [
        <xref ref-type="bibr" rid="ref11">11</xref>
        ] has described an
optimized implementation). Note that the new focus has not necessarily been
visited during the previous navigation steps (so de-selection is not always an
undo operation), but it is a super-concept of the old focus, and conjunctive
navigation with selection and de-selection is still Markovian and Abelian.
{ We can use a separate concept to represent each argument of an OR operator;
the result of such a disjunctive query is then the union of all corresponding
extents [
        <xref ref-type="bibr" rid="ref12">12</xref>
        ]. However, this disjunctive navigation gives up the single focus
property and is no longer Abelian, since the order of AND and OR operators
matters.
{ We can also retrieve or insert a query concept [
        <xref ref-type="bibr" rid="ref13">13</xref>
        ] into the lattice, where
the query concept's intent contains the current search terms and retrieve the
{country}
      </p>
      <p>{review text}
USA</p>
      <p>South Africa Fruity Berry
wine-bottle1 X
wine-bottle2
wine-bottle3 X
wine-bottle4</p>
      <p>X
X</p>
      <p>X
X</p>
      <p>X
X
X</p>
      <p>{varietal}
Cabernet
Sauvignon Merlot Pinotage
X
X</p>
      <p>X</p>
      <p>X</p>
      <p>
        parents of the query concept (called the query generator ), as a generalization
[
        <xref ref-type="bibr" rid="ref14">14</xref>
        ]. Additionally, more children of the query generator can be included to
broaden the results further. These are referred to as cousin concepts [
        <xref ref-type="bibr" rid="ref14">14</xref>
        ].
{ We can use the lattice's join operation as a generalization operation; if the
generalized concepts are determined by objects (rather than attributes) this
is also known as object-based navigation [
        <xref ref-type="bibr" rid="ref15">15</xref>
        ]. This navigation has the single
focus property by construction, and is still Markovian and Abelian (when
it is not mixed with re nement operations, otherwise lattice distributivity
is also required to ensure the Abelian property), but does not implement
the Boolean OR operation: due to the closure operations in the lattice
construction, the extent of the new focus typically contains additional objects.
This could be seen as a feature [
        <xref ref-type="bibr" rid="ref15">15</xref>
        ] but in contexts where the attributes
represent di erent categories or facets [
        <xref ref-type="bibr" rid="ref16">16</xref>
        ] this is prone to overgeneralization.
Overgeneralization refers to the focus moving too high in the lattice
(possibly to top) which would result in a decrease of precision for the query's
results. In particular, if we have functional facets (where each object can
have only a single attribute for a given category, such as year of birth), the
join will e ectively cancel the selected attributes from this category. The
join operation is thus unsuited as an intuitive generalization operation. We
therefore investigate an alternative generalization operation that makes use
of only subsets of the extents of the attribute concepts of the selected items,
in order to provide a more intuitive broadening navigation.
      </p>
      <p>
        Our approach is motivated from navigation in a dataset of wine reviews
extracted from [
        <xref ref-type="bibr" rid="ref17">17</xref>
        ]. The full dataset contains over 16000 objects. However, we
use a small example of the dataset in order to make the drawing of the concept
lattices feasible. For each wine bottle we have as attributes, the winery, the
vintage, the reviewer, the review year as well as the location and keywords
extracted from the reviews. We use individual wine bottles as objects in the
context and assign all other elds as the attributes. Figure 1 provides an example
of the constructed context for this dataset. This dataset contains functional
facets, such as the country, where each wine bottle can originate from only one
country.
      </p>
      <p>In this paper we provide a brief overview of information retrieval tasks and
navigation in concept lattices (Section 2). We then illustrate our re nement
selection and de-selection approach (Section 3) where the de-selection operation
reverses a re nement selection. We de ne a single-focus boolean OR navigation
operator, followed in Section 5 by an intuitive generalization operation which
prevents the full object set in the lattice from being returned. Additionally in
Section 5 we discuss an approach for nding similar objects within the concept
lattice.
2</p>
    </sec>
    <sec id="sec-2">
      <title>Information Retrieval and Navigation using Concept</title>
    </sec>
    <sec id="sec-3">
      <title>Lattices</title>
      <p>There have been many approaches to supporting information retrieval tasks
using concept lattices, some of which extend to disjunctive queries and broadening
approaches.</p>
      <p>
        Codocedo et al. [
        <xref ref-type="bibr" rid="ref14">14</xref>
        ] propose an information retrieval approach using
concept lattices where queries are answered using the cousin concepts of the query
concept. The query concept is inserted into (or identi ed in) the concept lattice
with a placeholder object and all the attributes that form a part of the current
query [
        <xref ref-type="bibr" rid="ref13">13</xref>
        ]. The superconcept of the query concept is then referred to as the query
generator. The cousin concepts of the query concept refer to the subconcepts of
the query generator. The cousin concepts and the query generator are used to
implement a broadening approach in the concept lattice [
        <xref ref-type="bibr" rid="ref14">14</xref>
        ]. The query's result
is then returned as the union of the cousin concepts' extents.
      </p>
      <p>
        Ferre [
        <xref ref-type="bibr" rid="ref18">18</xref>
        ] uses a navigation technique where a generalization is similar to
our de-selection (it does not need to take place in any particular order) and
deselection refers only to removing the last selected item (e.g., an undo operation).
      </p>
      <p>
        Godin et al. [
        <xref ref-type="bibr" rid="ref8">8</xref>
        ] described an iterative retrieval algorithm which maintains
a focus concept whose extent is the retrieval result. Initially, the focus is the
lattice's top element; in each iteration the user moves it to an adjacent concept,
by adding (removing) an attribute (not) in the intent of a concept directly above
(below) the current focus. However, this navigation style is too incremental,
because the focus can move only one level at a time, and too constrained, because
the user can only choose attributes from the intents of the directly adjacent
concepts, and has no indication which choices are hidden behind paths not taken.
      </p>
      <p>
        Lindig [
        <xref ref-type="bibr" rid="ref9">9</xref>
        ] introduced a semi-constrained navigation algorithm where, the
focus can be re ned by selecting any attribute from any concept (except ?) below
the focus, provided the attribute is not already in the focus' intent. The focus is
then updated by computing its meet with the attribute concept. A restriction on
selectable attributes prevents navigation into dead ends, and ensures that each
query re nement also re nes the query results.
      </p>
      <p>
        Fischer [
        <xref ref-type="bibr" rid="ref15">15</xref>
        ] exploited the duality of concept lattices and introduced
objectbased navigation; here, selection of an object not in the focus' extent is a
widening step that is implemented via the join.
      </p>
      <p>
        Lindig [
        <xref ref-type="bibr" rid="ref11">11</xref>
        ] uses object-based navigation to implement relevance feedback ;
selecting an object in the focus' extent selects all attributes in the intent of its
object concept.
3
      </p>
    </sec>
    <sec id="sec-4">
      <title>Re nement Selection and Deselection</title>
      <p>Re nement operations in the lattice can be computed using the meet operation.
For step-wise navigation, we maintain a current focus concept at each navigation
step. The focus can be re ned with a new selection by calculating the meet of
the current focus and the attribute concept of the new selection.</p>
      <p>Additionally, items available for selection can be restricted to those that have
a non-bottom meet with the focus, ensuring that a selection never returns an
empty extent.</p>
      <p>Because of the duality in the lattice, we might expect that the de-selection
(removing a previously selected item) can be implemented by the join (least
upper bound) operation, however this is not the case. Intuitively the de-selection
of the most recently selected item should return the focus concept to its previous
position, undoing the selection. However, computing the join of the focus with
the attribute concept of the new de-selection will cause all previous selections to
be removed, except the attribute we are de-selecting, which is counterintuitive.
Therefore, in order to reverse a single selection operation we need to recompute
the focus as the meet in the lattice from all still-selected items.</p>
      <p>
        Our de-selection performs essentially the same operation as illustrated by
Lindig [
        <xref ref-type="bibr" rid="ref11">11</xref>
        ], although Lindig optimizes this operation by making use of the search
path in order to compute the new focus concept. Note that de-selections do not
always need to take place in the same order as the initial selections. The
deselection operation can return a focus which has not been visited during the
previous navigation steps. De-selection is therefore not only an undo operation.
4
      </p>
    </sec>
    <sec id="sec-5">
      <title>Boolean Disjunctive Selection</title>
      <p>The meet operation in the lattice satis es conjunction between selected items.
The meet of the attribute concept of item a ( (a)) AND the attribute concept
of item b ( (b)), results in a concept whose intent contains both items a AND
b. However, boolean OR navigation, where an attribute must only apply to at
least one object is not supported by either the meet or join operations.</p>
      <p>
        Priss [
        <xref ref-type="bibr" rid="ref12">12</xref>
        ] makes use of a boolean disjunctive query operation which returns
the union of the extents of the concepts that are retrieved for each of the items
in the query when selected individually. This approach requires more than one
focus to generate the query's result.
      </p>
      <p>
        Codocedo et al.'s approach [
        <xref ref-type="bibr" rid="ref14">14</xref>
        ] (illustrated in Figure 4) does not implement
a purely disjunctive query operation as the query generators are not necessarily
the attribute concepts of the items selected for the disjunctive query.
      </p>
      <p>In our approach (Figure 3) we alter the underlying context table in order to
support the disjunctive navigation and maintain the single-focus property. By
updating the underlying context we are able to support further navigation steps
(re nements or generalizations) and maintain the disjunctive queries using only
a single focus concept.</p>
      <p>
        In order to compute the boolean OR of two items, a and b, we merge the
items in the underlying context table into a new attribute a OR b. We compute
the introducing concept of the newly created merged item ( (a or b)) as the new
focus. Our approach therefore returns the same query results as those that would
be obtained in [
        <xref ref-type="bibr" rid="ref12">12</xref>
        ] for a single disjunctive query with no consequent navigation
steps.
      </p>
      <p>Figures 2 and 3 illustrate our approach. Figure 2 shows the initial concept
lattice generated from the unaltered context. However, if we select item \Cabernet
Sauvignon", the focus will be the meet of &gt; and the attribute concept of
\Cabernet Sauvignon" (resulting in the attribute concept of \Cabernet Sauvignon").
Selecting \Merlot" for a boolean OR operation, the context will be updated to
add the combination of the two attributes to the context and the updated lattice
will appear as in Figure 3.</p>
      <p>The join of the focus and the attribute concept of \Merlot" would return
the top concept in the lattice and our result-set would contain wines of other
varietals (such as \Pinotage") which is undesirable. By using the boolean OR
operation we are able to retrieve all wines that are only of the \Merlot" OR
\Cabernet Sauvignon" varietals and the attributes which these wines possess.</p>
      <p>
        Note that this approach is similar to the use of conceptual scales in the
concept lattice [
        <xref ref-type="bibr" rid="ref20">20</xref>
        ] for multi-valued attributes (such as prices). However, instead
of using pre-de ned scales, our scale is generated automatically when the user
makes a boolean OR selection of an item in the dataset. The scale is therefore
interactively created and we update the context on-the- y.
5
      </p>
    </sec>
    <sec id="sec-6">
      <title>Broadening Navigation Approach</title>
      <p>The join operation supports broadening navigation, however, if the extents of
both concepts are large then the join is likely to overgeneralize and can result in
the top concept (&gt;) thereby losing all previous navigation steps and resulting in
a low precision for the constructed query.</p>
      <p>In order to support a broadening selection, that does not overgeneralize and
return a concept with a large extent (and little or no common attributes)
resulting in a low precision, we compute the join from only a subset of the objects in
the full extents of the two concept selections. If the join of the two concepts is
not &gt; then we return their join, otherwise we recompute the join after removing
one or more objects, until the join does not result in the top concept.
5.1</p>
      <p>Generating Candidate Focus Concepts
Our broadening approach results in an updated focus that shows attributes
which are common to some of the objects in the current focus and some of the
objects in the attribute concept of the new item ( (b)) selected for broadening.</p>
      <p>For example, in our wine review dataset if we select winery a for re nement
and then broaden on winery b, our updated focus will show which wine
characteristics (text from reviews etc.) are common to some bottles produced at
winery b and some bottles produced at winery a. The join would reveal only
characteristics that are common to all wine bottles from winery a and winery
b, and since the set of all bottles from winery a and winery b it is likely to be
large, the join risks navigating to top (&gt;).</p>
      <p>If the join does not return &gt;, we return the join concept as the new focus,
otherwise we traverse the lattice with a top-down depth- rst approach using
the focus as starting point. For each new concept in this traversal we then also
perform a top-down depth- rst traversal starting at (b). We compute the join
of every concept derived from these iterations as candidate focus concepts for
the next navigation step as shown in Algorithm 1.</p>
      <p>Note that the amount of candidate focus concepts could be large and
therefore we need to select a new focus from this pool in order to maintain only a
single focus.
5.2</p>
      <p>Selecting a new Focus Concept from the Candidate Focus
Concepts
We choose a single focus from the generated set of candidate focus concepts. If
a join for the previous focus (a = (A; B)) and the introducing concept of the
selection (b = (C; D)) that is not the top concept in the lattice exists then we
return the join concept, otherwise if the join results in the top concept then we
want to return the highest concept (with the largest extent) such that at least
one object from concept (a) is present and at least one object from concept (b)
is contained in the extent.
Data: Current focus concept f, and attribute concept of selected item b, (b)
Result: Focus concept candidates for broadening navigation
iterator = top down traversal starting at f
while iterator.next is not null do
f subset = iterator.next
inner iterator = top down traversal starting at (b)
while inner iterator.next is not null do</p>
      <p>(b) subset = iterator.next
concept = join of (b) subset and f subset
add concept to candidate focus concepts
end
end
Algorithm 1: Computing candidate focus concepts for our broadening
navigation operation. Join operations are computed using only a subset of the
objects in the extents of the attribute concepts of the selections.</p>
      <p>We therefore return the concept (c = (E; F )) which results in the highest
score where the score is computed as
score = jEj jAj jCj where jAj &gt; 0 and jCj &gt; 0.</p>
      <p>Our broadening operation therefore generalizes as much as possible without
losing all previous selections and navigation steps and removing all previous
navigation steps (navigating to &gt;).
6</p>
    </sec>
    <sec id="sec-7">
      <title>Finding Similar Objects</title>
      <p>Another method of generalizing from a single object in the dataset is to nd a
group of related or similar objects. To nd objects that are similar to a selected
object in the dataset we introduce a more like this operation. For example, if we
want to nd bottles of wine that are similar to a bottle that we have previously
tried (i.e. generalize from a single wine bottle), we can apply the more like this
operation to shift our focus to a concept that contains similar bottles, without
the user needing to be aware of any of the attributes of the wine.</p>
      <p>All concepts in the lattice in which the object of interest appears in the
extent can be considered to present similar objects. However, in multi-faceted
data, we are interested in nding a similarity between the objects in comparable
facets (e.g, wine bottle 1's origin and wine bottle 2's origin). We also restrict the
operation to returning results from only a single concept in the lattice so that all
subsequent navigation steps can continue after a more like this' generalization
operation.</p>
      <p>Since not all facets can be used to compare objects, for example being
reviewed by the same wine reviewer may not imply that two wine bottles are
similar, we use only relevant facets (such as the wine review text and varietal)
to compare objects. Various objects in the lattice will be similar across di erent
dimensions. We look at descriptors from relevant facets of the object that are
introduced lower in the lattice (are more speci c) and include as many of these
as possible in the meet calculation to derive the new focus. However, if speci c
terms result in the meet returning only the original object of interest then we
remove these terms in order to move the focus up and generate a larger extent.</p>
      <p>
        Calculating the size of the extent of the attribute concept can provide a
kind of TF/IDF [
        <xref ref-type="bibr" rid="ref21">21</xref>
        ] measure for the attribute in the entire corpus of objects.
If the extent of an attribute concept is large, then the objects in that extent
are unlikely to be very similar, since the attribute can be considered to be less
speci c as it applies to a large portion of the corpus.
      </p>
      <p>
        Figure 5 provides an example of our approach to nding similar objects. Wine
bottle 2 (indicated in red) is the object of interest. The introducing concepts of
the attributes of wine bottle 2 (berry, south africa, fruity, cabernet sauvignon)
are indicated in blue. The meet of all three of these concepts would lead only to
wine-bottle 2. Therefore the concept with the smallest extent is removed from the
meet set rst in order to move the focus up. Since concepts 1 and 2 both have an
equal extent size, we use the size of the intent in order to decide which concept to
remove from the meet calculation. Concept 1 provides two introducing attributes
and so we remove concept 2 from the meet set. The meet of concepts 1 and 3
returns only wine bottle 2 (providing no similar wine bottles) and so concept 1 is
subsequently removed from the meet set, leaving only concept 3. Therefore, wine
bottles 3 and 4 are considered similar to wine bottle 2 in our approach because
according to their reviews they all share avors of \berry". Although bottle 1
can also be considered similar to wine bottle 2 as they both share attribute
(\Merlot"), our approach favors the more general concept (concept 3) so that
the updated focus has a larger extent, including more similar objects.
There have been many applications of concept lattices in the information
retrieval domain [
        <xref ref-type="bibr" rid="ref22">22</xref>
        ], for example, the FaIR [
        <xref ref-type="bibr" rid="ref12">12</xref>
        ] and Credo systems [
        <xref ref-type="bibr" rid="ref5">5</xref>
        ].
      </p>
      <p>
        The FaIR information retrieval system [
        <xref ref-type="bibr" rid="ref12">12</xref>
        ] combines a lattice-based
thesaurus approach with boolean queries. The lattice-based thesaurus is used to
generate the query language. Terms from each facet are separated into di erent
lattices, unlike in our approach where the term and the facet name are used to
represent a term in a single lattice. The thesaurus is used to add synonyms to
the lattice so that queries with a wider vocabulary can be handled.
      </p>
      <p>
        Credo [
        <xref ref-type="bibr" rid="ref5">5</xref>
        ] facilitates the exploration of web search results. Index terms from
each retrieved search result are extracted from the documents. Credo supports
re nement of the search results by selecting additional terms. Initially the
presented information is derived from the lattice's top element and possible re
nements are presented to the user. These re nement terms can then be selected to
display a more speci c set of search results and re ne the initial query. Credo
only includes support for re nement navigation.
8
      </p>
    </sec>
    <sec id="sec-8">
      <title>Conclusions</title>
      <p>In this paper we have discussed step-wise re nement and broadening navigation
approaches in concept lattices that maintain the single focus property. We have
developed a broadening navigation algorithm that makes use of subsets of the
extents of two concepts in order to prevent the join from resulting in the top
concept in the lattice. We have modi ed the disjunctive navigation technique
to allow only a single focus concept to be stored and used to generate the
results of the disjunctive query, allowing consequent broadening and re nement
navigation steps to take place. We have discussed re nement navigation in
concept lattices and our de-selection operation which is able to reverse re nement
selections and does not restrict the order of the de-selection operation. Our
navigation approaches can be used to facilitate exploratory search in large concept
lattices and allow subsequent re nement, broadening and boolean OR navigation
operations to take place.</p>
    </sec>
    <sec id="sec-9">
      <title>Acknowledgments References</title>
      <p>This research is funded in part by a STIAS Doctoral Scholarship, CAIR-SU and
NRF Grant 93582.</p>
    </sec>
  </body>
  <back>
    <ref-list>
      <ref id="ref1">
        <mixed-citation>
          1.
          <string-name>
            <surname>Salton</surname>
            ,
            <given-names>G.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>McGill</surname>
            ,
            <given-names>M.J.</given-names>
          </string-name>
          :
          <article-title>Introduction to Modern Information Retrieval. McGrawHill, Inc</article-title>
          ., New York, NY, USA (
          <year>1986</year>
          )
        </mixed-citation>
      </ref>
      <ref id="ref2">
        <mixed-citation>
          2.
          <string-name>
            <surname>Rijsbergen</surname>
            ,
            <given-names>C.J.V.</given-names>
          </string-name>
          :
          <article-title>Information Retrieval. 2nd edn</article-title>
          . Butterworth-Heinemann, Newton, MA, USA (
          <year>1979</year>
          )
        </mixed-citation>
      </ref>
      <ref id="ref3">
        <mixed-citation>
          3.
          <string-name>
            <surname>Poelmans</surname>
            ,
            <given-names>J.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Ignatov</surname>
            ,
            <given-names>D.I.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Viaene</surname>
            ,
            <given-names>S.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Dedene</surname>
            ,
            <given-names>G.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Kuznetsov</surname>
            ,
            <given-names>S.O.</given-names>
          </string-name>
          , et al.:
          <article-title>Text mining scienti c papers: A survey on fca-based information retrieval research</article-title>
          . In: ICDM. Volume
          <volume>7377</volume>
          ., Springer (
          <year>2012</year>
          )
          <volume>273</volume>
          {
          <fpage>287</fpage>
        </mixed-citation>
      </ref>
      <ref id="ref4">
        <mixed-citation>
          4.
          <string-name>
            <surname>Poelmans</surname>
            ,
            <given-names>J.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Ignatov</surname>
            ,
            <given-names>D.I.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Kuznetsov</surname>
            ,
            <given-names>S.O.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Dedene</surname>
          </string-name>
          , G.:
          <article-title>Formal concept analysis in knowledge processing: A survey on applications</article-title>
          .
          <source>Expert Syst. Appl</source>
          .
          <volume>40</volume>
          (
          <issue>16</issue>
          ) (
          <year>2013</year>
          )
          <volume>6538</volume>
          {
          <fpage>6560</fpage>
        </mixed-citation>
      </ref>
      <ref id="ref5">
        <mixed-citation>
          5.
          <string-name>
            <surname>Carpineto</surname>
            ,
            <given-names>C.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Romano</surname>
            ,
            <given-names>G.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Bordoni</surname>
            ,
            <given-names>F.U.</given-names>
          </string-name>
          :
          <article-title>Exploiting the potential of concept lattices for information retrieval with credo</article-title>
          .
          <source>J. UCS</source>
          <volume>10</volume>
          (
          <issue>8</issue>
          ) (
          <year>2004</year>
          )
          <volume>985</volume>
          {
          <fpage>1013</fpage>
        </mixed-citation>
      </ref>
      <ref id="ref6">
        <mixed-citation>
          6.
          <string-name>
            <surname>Marchionini</surname>
          </string-name>
          , G.:
          <article-title>Exploratory search: from nding to understanding</article-title>
          .
          <source>Communications of the ACM</source>
          <volume>49</volume>
          (
          <issue>4</issue>
          ) (
          <year>2006</year>
          )
          <volume>41</volume>
          {
          <fpage>46</fpage>
        </mixed-citation>
      </ref>
      <ref id="ref7">
        <mixed-citation>
          7.
          <string-name>
            <surname>Godin</surname>
            ,
            <given-names>R.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Pichet</surname>
            ,
            <given-names>C.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Gecsei</surname>
          </string-name>
          , J.:
          <article-title>Design of a browsing interface for information retrieval</article-title>
          .
          <source>SIGIR Forum 23(SI) (May</source>
          <year>1989</year>
          )
          <volume>32</volume>
          {
          <fpage>39</fpage>
        </mixed-citation>
      </ref>
      <ref id="ref8">
        <mixed-citation>
          8.
          <string-name>
            <surname>Godin</surname>
            ,
            <given-names>R.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Saunders</surname>
            ,
            <given-names>E.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Gecsei</surname>
          </string-name>
          , J.:
          <article-title>Lattice model of browsable data spaces</article-title>
          .
          <source>Information Sciences</source>
          <volume>40</volume>
          (
          <issue>2</issue>
          ) (
          <year>1986</year>
          )
          <volume>89</volume>
          {
          <fpage>116</fpage>
        </mixed-citation>
      </ref>
      <ref id="ref9">
        <mixed-citation>
          9.
          <string-name>
            <surname>Lindig</surname>
            ,
            <given-names>C.</given-names>
          </string-name>
          :
          <article-title>Concept-based component retrieval</article-title>
          .
          <source>In: Working Notes of the IJCAI95 Workshop</source>
          :
          <article-title>Formal Approaches to the Reuse of Plans, Proofs, and</article-title>
          <string-name>
            <surname>Programs.</surname>
          </string-name>
          (
          <year>1995</year>
          )
          <volume>21</volume>
          {
          <fpage>25</fpage>
        </mixed-citation>
      </ref>
      <ref id="ref10">
        <mixed-citation>
          10.
          <string-name>
            <surname>Carpineto</surname>
            ,
            <given-names>C.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Romano</surname>
          </string-name>
          , G.:
          <article-title>E ective reformulation of boolean queries with concept lattices</article-title>
          .
          <source>In: Flexible Query Answering Systems</source>
          . Springer (
          <year>1998</year>
          )
          <volume>83</volume>
          {
          <fpage>94</fpage>
        </mixed-citation>
      </ref>
      <ref id="ref11">
        <mixed-citation>
          11.
          <string-name>
            <surname>Lindig</surname>
            ,
            <given-names>C.</given-names>
          </string-name>
          :
          <article-title>Algorithmen zur Begri sanalyse und ihre Anwendung bei Softwarebibliotheken</article-title>
          .
          <source>PhD thesis</source>
          , TU Braunschweig (
          <year>1999</year>
          )
        </mixed-citation>
      </ref>
      <ref id="ref12">
        <mixed-citation>
          12.
          <string-name>
            <surname>Priss</surname>
            ,
            <given-names>U.</given-names>
          </string-name>
          :
          <article-title>Lattice-based information retrieval</article-title>
          .
          <source>Knowledge Organization</source>
          <volume>27</volume>
          (
          <issue>3</issue>
          ) (
          <year>2000</year>
          )
          <volume>132</volume>
          {
          <fpage>142</fpage>
        </mixed-citation>
      </ref>
      <ref id="ref13">
        <mixed-citation>
          13.
          <string-name>
            <surname>Carpineto</surname>
            ,
            <given-names>C.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Romano</surname>
          </string-name>
          , G.:
          <article-title>Order-theoretical ranking</article-title>
          .
          <source>Journal of the American Society for Information Science</source>
          <volume>51</volume>
          (
          <issue>7</issue>
          ) (
          <year>2000</year>
          )
          <volume>587</volume>
          {
          <fpage>601</fpage>
        </mixed-citation>
      </ref>
      <ref id="ref14">
        <mixed-citation>
          14.
          <string-name>
            <surname>Codocedo</surname>
            ,
            <given-names>V.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Lykourentzou</surname>
            ,
            <given-names>I.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Napoli</surname>
            ,
            <given-names>A.</given-names>
          </string-name>
          :
          <article-title>A semantic approach to concept lattice-based information retrieval</article-title>
          .
          <source>Annals of Mathematics and Arti cial Intelligence</source>
          <volume>72</volume>
          (
          <issue>1-2</issue>
          ) (
          <year>2014</year>
          )
          <volume>169</volume>
          {
          <fpage>195</fpage>
        </mixed-citation>
      </ref>
      <ref id="ref15">
        <mixed-citation>
          15.
          <string-name>
            <surname>Fischer</surname>
            ,
            <given-names>B.</given-names>
          </string-name>
          :
          <article-title>Speci cation-based browsing of software component libraries</article-title>
          .
          <source>Autom. Softw. Eng</source>
          .
          <volume>7</volume>
          (
          <issue>2</issue>
          ) (
          <year>2000</year>
          )
          <volume>179</volume>
          {
          <fpage>200</fpage>
        </mixed-citation>
      </ref>
      <ref id="ref16">
        <mixed-citation>
          16.
          <string-name>
            <surname>Prieto-Diaz</surname>
            ,
            <given-names>R.</given-names>
          </string-name>
          :
          <article-title>Implementing faceted classi cation for software reuse</article-title>
          .
          <source>Communications of the ACM</source>
          <volume>34</volume>
          (
          <issue>5</issue>
          ) (
          <year>1991</year>
          )
          <volume>88</volume>
          {
          <fpage>97</fpage>
        </mixed-citation>
      </ref>
      <ref id="ref17">
        <mixed-citation>
          17. :
          <article-title>Wine review online</article-title>
          . http://www.winereviewonline.com/
        </mixed-citation>
      </ref>
      <ref id="ref18">
        <mixed-citation>
          18.
          <string-name>
            <surname>Ferre</surname>
            ,
            <given-names>S.</given-names>
          </string-name>
          :
          <article-title>Camelis: a logical information system to organise and browse a collection of documents</article-title>
          .
          <source>International Journal of General Systems</source>
          <volume>38</volume>
          (
          <issue>4</issue>
          ) (
          <year>2009</year>
          )
          <volume>379</volume>
          {
          <fpage>403</fpage>
        </mixed-citation>
      </ref>
      <ref id="ref19">
        <mixed-citation>
          19. :
          <article-title>Concept explorer</article-title>
          . http://conexp.sourceforge.net/
        </mixed-citation>
      </ref>
      <ref id="ref20">
        <mixed-citation>
          20.
          <string-name>
            <surname>Ganter</surname>
            ,
            <given-names>B.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Wille</surname>
          </string-name>
          , R.:
          <article-title>Conceptual Scaling</article-title>
          . In:
          <article-title>Applications of Combinatorics and Graph Theory to the Biological and</article-title>
          Social Sciences. Springer US, New York, NY (
          <year>1989</year>
          )
          <volume>139</volume>
          {
          <fpage>167</fpage>
        </mixed-citation>
      </ref>
      <ref id="ref21">
        <mixed-citation>
          21.
          <string-name>
            <given-names>Sparck</given-names>
            <surname>Jones</surname>
          </string-name>
          ,
          <string-name>
            <surname>K.</surname>
          </string-name>
          :
          <article-title>A statistical interpretation of term speci city and its application in retrieval</article-title>
          .
          <source>Journal of documentation 28(1)</source>
          (
          <year>1972</year>
          )
          <volume>11</volume>
          {
          <fpage>21</fpage>
        </mixed-citation>
      </ref>
      <ref id="ref22">
        <mixed-citation>
          22.
          <string-name>
            <surname>Codocedo</surname>
            ,
            <given-names>V.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Napoli</surname>
            ,
            <given-names>A.</given-names>
          </string-name>
          :
          <article-title>Formal concept analysis and information retrieval{a survey</article-title>
          .
          <source>In: Formal Concept Analysis</source>
          . Springer (
          <year>2015</year>
          )
          <volume>61</volume>
          {
          <fpage>77</fpage>
        </mixed-citation>
      </ref>
    </ref-list>
  </back>
</article>