<!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>Modelling Conceptual Schemata with Formal Concept Analysis</article-title>
      </title-group>
      <contrib-group>
        <contrib contrib-type="author">
          <string-name>Uta Priss</string-name>
          <xref ref-type="aff" rid="aff0">0</xref>
        </contrib>
        <aff id="aff0">
          <label>0</label>
          <institution>Ostfalia University</institution>
          ,
          <addr-line>Wolfenbu ̈ttel</addr-line>
          ,
          <country country="DE">Germany</country>
        </aff>
      </contrib-group>
      <abstract>
        <p>This paper discusses how to construct conceptual schemata (which are meant to provide conceptual information in a manner close to natural language, easy to memorise and mentally parse) from concept lattices which tend to present a more computational view of conceptual information. Different methods for constructing schemata from concept lattices (such as OR-definitions for reducing the number of attributes and implications of a concept lattice) are considered.</p>
      </abstract>
    </article-meta>
  </front>
  <body>
    <sec id="sec-1">
      <title>1 Introduction</title>
      <p>As the name states, Formal Concept Analysis (FCA) provides a means for analysing
concepts. While there are many applications for FCA, it is often easier to employ FCA
for computational problems than to actually analyse concepts in a manner similar to
how natural language is processed by humans. For the purpose of structuring and
developing teaching materials it would be desirable if FCA could serve as a means for
representing concepts in a manner that is close to how students learn domain
knowledge. A representation would be desirable that is similar to relations amongst natural
language words, for example hyponyms such as “poodle” and “dog”. Lattices that are
automatically generated from natural language databases, however, such as WordNet
or Roget’s Thesaurus tend to be more computational because their relations are not
sufficiently precisely defined (Priss &amp; Old 2010).</p>
      <p>In this paper, we are introducing an approach for shifting between word-based
natural language representations and more formal representations with FCA. For that
purpose we are distinguishing (conceptual) schemata which utilise natural language words
from (conceptual) classes which contain a set of formal contexts. Investigating the
connections between schemata and classes is a semiotic task because it considers a
relationship between words as representations of signs and concepts as meanings of signs.
It is of interest to determine how well the information of a class is retained in a schema,
how efficiently it is represented and how well a schema covers a class. The semiotic
perspective and the relationship to educational research have been discussed elsewhere
(Priss 2021a and 2021b) and are not further elaborated in this paper.</p>
      <p>The notion of “schema” is influenced by Lakoff’s (1987) “image schema”. But the
focus of schemata in this paper is on verbal description, not on images. The words
or phrases that are defined by a schema and relate one schema to other schemata are
called head representamens in this paper in analogy to the headwords of dictionary
entries which are also called catchwords, keywords, subject headings, index terms or
descriptors in other disciplines. From a semiotic view, head representamens are
representamens of signs (Priss 2017). From a computational view, head representamens are
just strings that are elements of a set. Head representamens are to be distinguished from
other representamens which have an auxiliary function.</p>
      <p>Head representamens can serve as building blocks for constructing compound
representamens using the operations AND, OR and NOT. For example, head
representamens for poodles might be “poodle” and “miniature poodle” whereas a compound
representamen might be “poodle AND cute”. Such operations are syntactically defined
in schemata and semantically defined in classes withinterpretations mapping schemata
into classes1. The operations AND and OR for head representamens are similar but
not identical to natural language “and” and ”or” because, in natural language, “and”
is sometimes used for an intersection (such as “dog and cute”), sometimes for a union
(such as “dogs and cats”) and “or” can be exclusive or inclusive. An interpretation
should map an AND-operation amongst head representamens into a meet of concepts
in a class, an OR-operation into a join of concepts or a construction involving a union
of extensions and a NOT-operation into an extensional set difference.</p>
      <p>The basics of FCA can be found in the textbook by Ganter &amp; Wille (1999) and
are not repeated in this paper. But it should be mentioned that a concept (a0, a00) is
called an attribute concept of a and a concept (o00, o0) an object concept. The ordering
amongst object concepts is called object order. Concepts that are not object concepts
are called supplemental concepts in this paper. The extension of a supplemental concept
equals the union of the extensions of its proper subconcepts. In this paper supplemental
concepts are drawn as empty nodes in the Hasse diagrams. Each supplemental concept
corresponds to a clause because for such a concept c with extension ext(c) and
intension int(c) and the condition ∀oi ∈ ext(c) : ∃ci &lt; c : oi ∈ ext(ci) it follows that
V(ai ∈ int(c)) ⇒ W(ai | ∃ci : ci &lt; c, ai ∈ int(ci), ai 6∈ int(c)) is a clause. It is
particularly interesting to consider whether some concepts always have to be supplemental
with respect to background knowledge even if more objects are added to a context. An
example for this feature is provided in the next section.</p>
      <p>Some aspects presented in Section 2 which discusses a certain type of reduction of
concept lattices have already been covered elsewhere, for example, by Ganter &amp;
Obiedkov (2016). Ganter (2019) discusses how to render an implication basis of a formal
context more human readable by changing and grouping some of the implications and
Lopez-Rodriguez et al. (2021) provide a means for determining core implications from
a basis. In this paper, the focus is on reducing implications combined with representing
some of the information by other means (as subconcept hierarchies or prototypical
examples) if that renders the information more human readable. OR-reductions are also
relevant for reducing a concept lattice to its AOC-poset (Osswald &amp; Petersen, 2002)
which consists only of the attribute and object concepts and possibly for feature models
of Product Line Representations (Carbonnel et al. 2016).</p>
      <p>The definitions of conceptual schemata, classes and interpretations in Section 3 are
similar to a standard modelling with formal semantics, for example, Prediger’s (1998)
K-interpretations which map ordered sets of concept and relation names into power
1 Contrary to standard formal semantics where interpretations map strings into sets, in this paper
interpretations map head representamens into concepts.
context families. The aim of Prediger’s work and others who extended it was to establish
a connection between FCA and Conceptual Graphs and focused on logical properties.
The focus of this paper is on the relationship between representamens and concepts in
a more closed world setting. Most established FCA exploration and reduction methods
tend to focus on reducing the lower parts of a lattice whereas in this paper mainly
supplemental concepts in the upper part of a concept lattice are reduced. Thus, this
paper draws on existing research but from a somewhat different perspective.
2</p>
    </sec>
    <sec id="sec-2">
      <title>OR-Reduction</title>
      <p>This section uses an example of a formal context and lattice from Ganter &amp; Wille (1999)
consisting of seven prototypical types of triangles and their defining properties (Fig. 1,
left). In this example, the supplemental concepts (represented as empty nodes) must
always be supplemental because every triangle must have exactly one of the attributes
“acute”, “obtuse” or “right” and either be equilateral or not or isosceles or not. Thus
according to background knowledge about triangles, the object concepts describe actual
examples of triangles whereas the extensions of the supplemental concepts must always
be unions of the extensions of their subconcepts even if more triangles are added to the
context. The lattice displays subconcept relationships for the types of triangles. If a
student wants to learn about triangles, their types and their definitions, it would not be
efficient to memorise all of the concepts of the lattice on the left side of Fig. 1. because
it displays more a computational view than a natural language view.</p>
      <p>isosceles acute obtuse
oblique isosceles</p>
      <p>right
not equilateral
obtuse
right
isosceles acute
obtuse</p>
      <p>right
equilateral
Obj 1
Obj 2
Obj 3
Obj 4
Obj 5
Obj 6
Obj 7
obtuse, isosceles
right, isosceles
acute
equilateral
obtuse
acute, isoseceles
right
acute</p>
      <p>equilateral
equilateral
oblique := acute OR obtuse
not_equilateral := NOT equilateral
(aecquuteila⊥teorabltu−s&gt;e isosceles AND acute) Implications: aecquutielaotebrtaulse−&gt;−&gt;is⊥osceles acute
Fig. 1.aAcutleat⊥ticrieghotf triangles (cf. Ganter &amp; Wille (1999)a)caunted riitgshrte−d&gt;uc⊥ed form</p>
      <p>obtuse⊥ right obtuse right −&gt; ⊥</p>
      <p>The right side of Fig. 2 shows a reduced version of the lattice on the left. The
attributes “oblique” and “not equilateral” have been removed because oblique represents
“acute OR obtuse” and “not equilateral” is the negation of “equilateral”. Normally in
FCA reducing means to remove all attributes and objects from a context which are
at attribute or object reducible concepts. Another form of reduction is to calculate an
AOC-poset which only keeps object and attribute concepts and their ordering (Osswald
&amp; Petersen 2002). AOC-posets are compact and can be algorithmically produced (Berry
et al. 2014). A lattice can be reconstructed from its AOC-poset if a clause is added for
each concept that is neither an attribute nor an object concept. A disadvantage of
AOCposets is that conjunctions of attributes and therefore implications need not correspond
to a single node and cannot easily be read from Hasse diagrams. This disadvantage
is avoided by the reduction methods in this paper. Other means for reducing the size
of concept lattices discussed in the literature tend to rely on statistical or probabilistic
methods which cannot easily be reversed (cf. Priss &amp; Old (2011) for an overview).</p>
      <p>In this paper, only reducing attributes is of interest. Reducing attributes in the
standard manner (called AND-reduction in this paper) changes the labelling of a concept
lattice but not its structure. Removing attributes that are OR combinations (called
ORreduction in this paper) or NOT combinations (NOT-reduction) may change the concept
lattice itself and reduce its size as demonstrated in Fig. 1. All of the following
definitions focus on attributes and assume that the contexts are finite and clarified (or purified)
which means that for any two attributes a 6= b =⇒ a0 6= b0.</p>
      <p>Definition 1. An attribute a of a formal context (O, A, J ) is called OR-reducible if a
set A? := {a1, ..., an} ⊆ A exists with a0 = a01 ∪ ... ∪ a0n and ai ∈ A? ⇐⇒ a0i ⊂ a0
and ¬∃b ∈ A : a0i ⊂ b0 ⊂ a0.</p>
      <p>Definition 2. For a formal context (O, A, J ): For an OR-reducible attribute a, its
ORdefinition is provided by a := a1 OR ... OR an for ai ∈ A?. An attribute a with
∃{a1, ..., an} ⊆ A : a0 = a01 ∩ ... ∩ a0n is called (AND-)reducible with an
ANDdefinitionprovided by a := a1 AND ... AND an. An attribute a with ∃b ∈ A : a0 = O\b0
is called NOT-reducible with its NOT-definitionprovided by a := NOT b.
Lemma 1. If a is OR-reducible, then its set A? := {a1, ..., an} for its representation as
a1 OR ... OR an is uniquely determined. If a is NOT-reducible then its NOT-definition
is uniquely determined.</p>
      <p>Proof: For b ∈ A with b0 ⊂ a0: if b0 \ S{a0i : ai ∈ A?, ai 6= b} 6= ∅, then b ∈ A?.
Else b0 ⊆ S{a0i : ai ∈ A?, ai 6= b} = a0 and either ∃ai ∈ A? : b0 ⊂ a0i (thus b 6∈ A?)
or ¬∃ai ∈ A? : b0 ⊂ a0i (thus b ∈ A?). Thus b ∈ A? or b 6∈ A? is uniquely determined.
NOT-definitions are unique because the context is clarified.</p>
      <p>An attribute b that was removed during clarification can be considered a strong
synonym or SYN-definition in the form of a := b. As mentioned above, AND-reduction
corresponds to standard FCA ∧-reduction. AND-definitions are not unique because
often several possibilities exist to represent a ∧-reducible concept as a meet of other
concepts. OR-reduction focuses on attributes whereas standard FCA ∨-reduction focuses
on objects. Thus, these two notions are different. An OR-reducible attribute must
belong to a ∨-reducible concept, but not every ∨-reducible concept has an OR-reducible
attribute. In fact OR- and NOT-reducible attributes need not exist at all in a lattice. In a
similar manner, XOR-definitions could be declared as OR-definitions where thea0i are
pairwise disjoint.</p>
      <p>Lemma 2. i) The AND-definition of an attribute concept (a0, a00) is a.
ii) An object concept (o00, o0) cannot be OR-reducible.
iii) A ∨-reducible concept that is an attribute concept (a0, a00) and not an object concept
can always be made OR-reducible by adding further attributes to the formal context.</p>
      <p>Proof: i) Trivial. ii) Because o cannot be in the extension of proper subconcepts of
(o00, o0). iii) Attributes a1, ..., an can be added so that each lower neighbour of (a0, a00)
is an attribute concept (a0i, a0i0). Because the concept is not an object concept, Def. 1 is
then fulfilled withA? = {a1, ..., an}.</p>
      <p>Thus Lemma 1 only states that an OR-definition is unique with respect to a fixed
formal context. Turning each lower neighbour into an attribute concept is always
possible but may not be the best strategy. For example in Fig. 1, oblique is definable as “acute
OR obtuse” even though only one of its lower neighbours is an attribute concept.</p>
      <p>Standard FCA implications only use logical AND. Implications that are formed with
combinations of AND and OR are called (cumulated) clauses and are more
complicated than standard implications. For example, there is no equivalent to the
DuquenneGuigues basis for clauses (Ganter &amp; Obiedkov 2016). Because the requirements for an
OR-definition are more specific than just a logical OR, the implications discussed in
the next lemma are not standard FCA clauses. The lemma shows that if attributes are
removed from a context as OR-definitions, some of the implications of the original
context can be directly reconstructed from the OR-definitions (as background knowledge)
and the implications of the reduced context.</p>
      <p>Lemma 3. For implications involving OR-definitions with a := a1 OR ... OR an:
i) ∀ai : ai → a
ii) a → x ⇐⇒ (a1 OR ... OR an) → x ⇐⇒ (a1 → x) and ... and (an → x)
iii) x → a ⇐⇒ x → (a1 OR ... OR an) ⇐⇒ (x → a1) or ... or (x → an)
iv) a1... an → x =⇒ a → x
v) ∀ai : (x → aiy =⇒ x → ay)</p>
      <p>Proof: i) Because a0i ⊂ a0. ii) a01 ∪ ... ∪ a0n ⊆ x0 ⇐⇒ a01 ⊆ x0 and ... and a0n ⊆ x0.
iii) With A? = {a1, ..., an} it follows that x0 ⊆ a01 ∪ ... ∪ a0n ⇐⇒ ∃ai ∈ A? : x0 ⊆ a0i
because otherwise x ∈ A?. iv) follows from ii) and the Armstrong rule of composition.
v) because of transitivity of “ →”.</p>
      <p>Removing an OR-reducible attribute changes a lattice unless the attribute is also
AND-reducible. It would be desirable to develop an efficient algorithm for
reconstructing the implications of an original non-reduced context from the implications of a
reduced context together with the OR-definitions. Lemma 3 contains some rules for such
an algorithm, but the list is not complete and it is not clear whether it can be completed.
A challenge for such an algorithm is that if several OR-definitions exist, they can
mutually affect each other and thus cannot be processed in a linear sequence. It would be
even more desirable if such an algorithm were to convert basis implications into basis
implications. While all implications of an OR-reduced context are implications of its
non-reduced context, applying Lemma 3 to an implication that belongs to a basis does
not guarantee that it results in a basis implication of the non-reduced context. If
efficiency is not an issue, then the implications of the non-reduced context can always be
calculated by adding OR-definitions to a formal context as columns (for attributes) that
are unions of other columns. For the purposes of developing schemata as discussed in
the next section, it is sufficient to store those implications that cannot be easily
reconstructed with Lemma 3 in a separate list in addition to the basis implications.</p>
      <p>Presumably reconstructing the implications after NOT-reduction is even more
complicated. OR-reduction does not change the object order of a lattice. But adding or
deleting NOT-reducible attributes does change the object order as shown in Fig. 1. Therefore
removal of NOT-reducible attributes may not in general be advisable. For the same
reason, combining AND, OR and NOT in definitions is not even discussed in this paper. A
further reason for removing OR-reducible attributes is because their existence is
somewhat arbitrary. In the example in Fig. 1, oblique is OR-definable as “acute OR obtuse”.
There are no similar attributes for “acute OR right” and “obtuse OR right”, but there
could be. It is arbitrary which OR-definitions happen to exist as an attribute and which
do not. Successive OR-reduction might reduce a concept lattice to its object ordering.
Presumably, implications involving object concepts are particularly important whereas
all other implications somewhat depend on how upper level concepts are labelled.
3</p>
    </sec>
    <sec id="sec-3">
      <title>Conceptual Schemata and Classes</title>
      <p>Learning is a complicated task that consists of memorising information but also
acquiring skills and modes of thinking. With respect to conceptual knowledge different modes
of thinking correspond to structuring content in a variety of manners: some information
as concepts, some as implications, clauses or examples and some by techniques for
deducing further information from the memorised information. The idea for conceptual
schemata is that they present information in a format that is closer to how information
would be structured for learning purposes. The role of conceptual classes is then to
ensure that the information that is behind a schema is consistent and as complete as
possible. The definitions in this section only provide a general framework and will need
to be specified with further details for actual applications.</p>
      <p>Fig. 2 shows the conceptual schema (on the left) for the concept lattice (on the right)
of the example of Fig. 1. In this case the reduced lattice is already quite close to a
schema, except that the top and bottom node are not necessary because they can be
deduced. Further details about the schema are explained below. Evidence for the adequacy
of the diagram on the left of Fig. 2 is provided by the fact that the German Wikipedia
page about triangles contains basically the same image2 for the “hierarchy of triangles”.
Thus, the Wikipedia authors appear to consider it a suitable summary of knowledge
about basic triangles. Students can memorise that diagram together with the definition
of “oblique” and the fact that acute, right and obtuse are mutually exclusive. Students
can then deduce further implications (such as “obtuse → oblique not equilateral” and
“equilateral → isosceles acute”) from the memorised information.</p>
      <p>The following definitions specify the relationship between conceptual schemata and
classes more precisely. The definitions are similar to standard definitions of formal
semantics except that interpretations result in concepts instead of sets.</p>
      <p>Definition 3. A (conceptual) class (O, AL, J, N ) consists of a set O of formal objects,
a set AL of predicates (or “attributes”, formed according to some language L), a
relation J ⊆ O × AL with oJ a ⇐⇒ (a(o) is true) and a set N of formal contexts with
(Oi, Ai, Ji) ∈ N for Oi ⊆ O, Ai ⊆ AL, Ji ⊆ J and Ji ⊆ Oi × Ai. The set of all
concepts that can be derived from any of the contexts is denoted by C(O, AL, J, N ), the set
of all true statements that can be derived from any of the contexts by T (O, AL, J, N ).
2 https://de.wikipedia.org/wiki/Datei:Hierarchie.Dreiecke.png
isosceles
acute
right
isosceles acute
oblique := acute OR obtuse
not_equilateral := NOT equilateral
(equilateral −&gt; isosceles AND acute) Implications: equilateral −&gt; isosceles acute
aaoccbuut utteese⊥⊥⊥roribiggthuhtste aaoccbuut utteeseroirbgithguthst−e−&gt;−&gt;&gt;⊥⊥⊥
A conceptual class is a set of formal contexts which are defined with respect to a
common set of objects and attributes. While it would be possible to consider (O, AL, J )
a formal context itself, it may be too big to compute anything useful for it. Therefore
concepts and implications are only computed for the contexts in N . It is possible for
implications from one n1 ∈ N to contradict implications from another n2 ∈ N , but
that can be avoided by renaming attributes and is a matter of how the data of an
application is modelled. In this paper, the language L contains expressions formed from
unary predicates and the symbols AND, OR, NOT, → and :=, although the symbol
“AND” is usually omitted as the default operation. In general, L can be more complex.
The implications of a context are considered true for all objects of the context. In this
paper, the examples of classes only consist of a single context where the predicates are
unary attributes. But in general, Def. 3 encompasses a wide variety of possibilities. For
example, a class can be a computer program of a declarative programming language or
a relational database where the elements of O are tuples and a single predicate for each
table determines whether or not a tuple exists in the table.</p>
      <p>Definition 4. A (conceptual) schema (RH , RL, B) consists of a set R of head
representamens, a set RL of (representamen) expressions that are formed using head
representamens and elements of a language L with RH ⊆ RL and a set B of binary
(representamen) relations B ⊆ RL × RL.</p>
      <p>Further, non-mathematical conditions of conceptual schemata could be formulated,
for example, that a schema should be coherent, focused on a single topic and have a
certain minimal and maximal size. In this paper, the vocabulary of L is AND, OR and
NOT and B := {→, ,→, =, :=, ⊥} with “ :=” ⊆ RH × RL, r1 = r2 ⇐⇒ (r1 →
r2, r2 → r1), (r1 := r2 =⇒ r1 = r2) and (r1 ,→ r2 =⇒ r1 → r2). The relations
are definition (:=), strong synonymy (=), hyponymy (→ or edge in a Hasse diagram),
distant hyponymy (,→ or arrow in a Hasse diagram) and mutual exclusivity (⊥). Two
expressions are in a distant hyponymy relation if the exact hyponymy chain from one
to the other is not specified. Further syntactic conditions need to be provided for actual
applications. The Hasse diagram on the left of Fig. 2 is an abbreviation for some of the
expressions and the hyponymy relation. Each node corresponds to an expression, either
by itself (“acute”) or as an AND-definition (“isosceles AND acute”), but only involving
hyponyms, not distant hyponyms. The hyponymy relation is the transitive closure of the
edges in the diagram. The hyponymy instance “equilateral → isosceles AND acute” is
in brackets because it is redundant and can be read from the Hasse diagram.</p>
      <p>Expressions and relations in a schema are meaningless strings that are manipulated
according to the rules of a language. In order to evaluate whether expressions and
relations are meaningful or true, they need to be mapped into classes using interpretations.
The following definition specifies that head representamens and expressions are mapped
onto concepts and relations onto true statements.</p>
      <p>Definition 5. A schema (RH , RL, B) is interpretable over a class (O, AL, J, N ) if a
set I of partial functions (called interpretations) can be defined so that ∀r ∈ RL ∃i ∈
I : i(r) ∈ C(O, AL, J, N ) and ∀B ∈ B ∀b ∈ B ∃i ∈ I : i(b) ∈ T (O, AL, J, N ).</p>
      <p>The definition does not provide any details with respect to how the interpretations
are constructed. Further conditions must be supplied for specific applications. For
example, if r1 is a hyponym of r2, it should be required that i(r1) &lt;n i(r2) in some
context n. Ideally, there should be exactly one interpretation for each formal context so
that a head representamen can be assigned different concepts for different contexts but
only at most one concept within a single context. Because different relation instances in
a schema can utilise different interpretations, a certain amount of flexibility, ambiguity
or fuzziness is possible. For example, a tomato can be a fruit in one context and a
vegetable in another context. A schema should not just be interpretable, but also provide
sufficient information about its underlying class as specified in the next definition. All
examples of schemata in this paper fulfil Def. 6.</p>
      <p>Definition 6. A schema (RH , RL, B) covers a class (O, AL, J, N ) under a set I of
interpretations if each object concept is an interpretation of at least one representamen
expression, if the object order and the relationship between an object concept and its
attribute concepts is an interpretation of some instances of “ →” and T (O, AL, J, N )
can be logically derived from interpretations of representamen relations.
4</p>
    </sec>
    <sec id="sec-4">
      <title>Two Further Examples of Schemata and Classes</title>
      <p>This section provides two further examples for developing conceptual schemata. The
example in Fig. 3 is based on Ganter &amp; Obiedkov (2016) where it is utilised for a
discussion of clauses. According to the example, a driving license is passed exactly if both
the theoretical and the driving part are passed and failed if one of them is failed. Ganter
&amp; Obiedkov argue that the 8 implications of the lattice do not represent the information
in a natural manner. Instead they are suggesting to use 6 clauses and 2 implications.
A difference between the clauses of Ganter &amp; Obiedkov and the OR-definitions in this
paper is that OR-defined attributes can be removed from the set of attributes before
calculating the remaining implications. Thus the set of implications becomes smaller. The
example in Fig. 3 shows that after defining the attribute “license fail” as “driving fail OR
theory fail” and then removing it from the formal context, only four relation instances
corresponding to implications are left. The first two correspond to both directions of
an AND-definition ( “license pass” as “driving pass AND theory pass”). The other two
state that passing and failing each part of a driving test is mutually exclusive. Thus the
schema on the left of Fig. 3 presents all relevant information and covers the class on the
right in a succinct manner.</p>
      <p>theory_ driving_ driving_ theory_
fail fail pass pass</p>
      <p>license_fail
license_pass
license_fail := driving_fail OR theory_fail
(license_pass := theory_pass AND driving_pass)
driving_pass⊥ driving_fail
theory_pass ⊥ theory_fail
theory_
fail
driving_ driving_ theory_
fail pass pass
license_pass
.</p>
      <p>The final example of this paper is based on Ganter &amp; Wille (1999) and consists of
properties of binary relations as defined in the following table3.</p>
      <p>property definition
reflexive ∀a ∈ A : aRa
irreflexive ∀a ∈ A : ¬aRa
symmetric ∀a, b ∈ A : aRb → bRa
asymmetric ∀a, b ∈ A : aRb → ¬(bRa)
antisymmetric ∀a, b ∈ A : aRb and bRa → a = b
transitive ∀a, b, c ∈ A : aRb and bRc → aRc
semiconnex ∀a 6= b ∈ A : aRb or bRa
connex ∀a, b ∈ A : aRb or bRa</p>
      <p>The concept lattice in Fig. 4 follows Ganter &amp; Wille (1999). But it contains
additional AND-defined attributes, such as “preorder := reflexive AND transitive”. It also
contains some attributes about extreme cases. The example assumes that the relations
R are defined asR ⊆ S × S for a non-empty set S. It may seem counter-intuitive that
a relation can be both an order relation and an equivalence relation or symmetric and
antisymmetric at the same time because that is only possible for extreme cases with
attributes such as R = S × S, R = {(i, j) | i = j , S
} | | = 1 or R = {}. These attributes
are included in the lattice.</p>
      <p>Supplemental concepts are identified in Fig. 4 using background knowledge about
binary relations. OR-definitions are only applicable to supplemental concepts. In the
3 It should be remarked that the notions “semiconnex” and “connex” are used ambiguously in the
literature. Sometimes “connex” is used instead of “semiconnex” and “strong connex” instead
of “connex”.
connex</p>
      <p>preorder troellaetriaonnce
preorder poset eqreuliavtaiolennce
total
total order R = S x S
csoenmnie−x symmetric transitive symmetric
anti−
previous examples, the concept lattices had supplemental concepts higher up in the
lattice which could be removed using OR-definitions. This example only has very few
supplemental concepts which are at the bottom of the lattice. These could be removed
by introducing more attributes according to Lemma 2, but that does not reduce the
complexity of the lattice significantly and increases the set of implications. Instead, the
suggestion for developing a conceptual schema in this example is to extract meaningful
parts of the lattice. Fig. 4 indicates a subdivision according to whether a relation is
reflexive, irreflexive or neither. But such a division groups equivalence relations closely
with order relations which are separated from strict orders. Thus it seems more natural
to consider symmetric and NOT-symmetric as the main dividing factor for types of
binary relations. Therefore, Fig. 5 and Fig. 6 divide the conceptual schema of binary
relations into 3 parts: those that are not symmetric and tend to be orders, those that
are symmetric and closely related to equivalence relations and the extreme cases at the
bottom of the lattice which are antisymmetric and symmetric at the same time.</p>
      <p>Fig. 5. Conceptual schema for types of binary relations: part 1</p>
      <p>symmetric
semi−
connex
connex preorder</p>
      <p>
        total preorder
{(
        <xref ref-type="bibr" rid="ref1 ref1">1,1</xref>
        ),(
        <xref ref-type="bibr" rid="ref1 ref2">1,2</xref>
        ),(
        <xref ref-type="bibr" rid="ref2 ref2">2,2</xref>
        )},{1,2}
tolerance
relation
      </p>
      <p>partial
equivalence
relation</p>
      <p>
        reflexive
equivalence
relation
R = S x S
{(
        <xref ref-type="bibr" rid="ref1 ref1">1,1</xref>
        ),(
        <xref ref-type="bibr" rid="ref2 ref2">2,2</xref>
        )},{1,2}
connex
{(
        <xref ref-type="bibr" rid="ref1 ref1">1,1</xref>
        )},{1}
{(
        <xref ref-type="bibr" rid="ref1 ref1">1,1</xref>
        ),(
        <xref ref-type="bibr" rid="ref1 ref2">1,2</xref>
        ),(
        <xref ref-type="bibr" rid="ref1 ref2">2,1</xref>
        ),(
        <xref ref-type="bibr" rid="ref2 ref2">2,2</xref>
        )},{1,2}
antisymmetric
transitivesymmetric
(i,j)∈R=&gt; i=j
{(
        <xref ref-type="bibr" rid="ref1 ref1">1,1</xref>
        )},{1,2}
|S|=1 semiconnex
      </p>
      <p>asymmetric
irreflexive</p>
      <p>The three parts of the schema in Fig. 5 and Fig. 6 are derived from the lattice of
the class by deleting and restricting some attributes. Restricting means in this case that
an attribute is replaced by its meet with another attribute. For example, in Fig. 5, the
attribute “symmetric” is deleted and the attributes “reflexive”, “semiconnex” and
“connex” are replaced by their meet with “transitive” which results in distant hyponyms
in the schemata. AND-definitions involving distant hyponyms cannot be read from the
Hasse diagrams of the schemata. The left schema in Fig. 6 is derived by deleting the
attributes “antisymmetric”, “asymmetric”, “irreflexive” and “semiconnex”. The right
schema is derived by restricting all attributes to their meet with “antisymmetric”,
“symmetric” and “transitive”. For the non-restricted attributes, the hyponymy relation of the
schema corresponds to the subconcept relation of the class and results in the same
implications. The restricted attributes are considered distant hyponyms because their
implications are not completely contained in the parts of the schema. All phrases in Fig. 5
are head representamens. In Fig. 6, the phrases and formulas that are written above
the nodes are head representamens. The strings below the nodes represent prototypical
examples and are not head representamens. The conceptual class contains four
implications which are not just AND-definitions. Each of these four implications is included in
the part of the schema where it is visible. In this case, even the schemata are still quite
complex. But that is due to the subject manner. Learning all the relevant information
about the head representamens in Fig. 5 and Fig. 6 will require a significant amount of
time.
5</p>
    </sec>
    <sec id="sec-5">
      <title>Conclusion</title>
      <p>In summary, conceptual classes and schemata mutually influence each other. In some
cases, it might be more suitable to extract a class from a schema using some form of
conceptual exploration. In other cases, a schema can be constructed after reducing a
class. The following strategies can be employed:
• Possibly splitting the context into smaller coherent subcontexts
• Conceptual exploration (for completing the set of objects and attributes)
• Purifying the lattice, adding SYN-definitions
• AND-reduction
• OR-reduction
• Further OR-reduction after adding attributes according to Lemma 2
• NOT-reduction</p>
      <p>The motivation behind this strategy is that with respect to relationships between
conceptual schemata and classes, the core content of a class is retained in its object
concepts, their ordering and the AND-definitions of object concepts. The concepts that
are above the object order may be less important, in particular if they are
supplemental concepts, because they tend to represent attributes that may be expressible as
ORdefinitions.</p>
    </sec>
  </body>
  <back>
    <ref-list>
      <ref id="ref1">
        <mixed-citation>
          1.
          <string-name>
            <surname>Berry</surname>
            ,
            <given-names>A.</given-names>
          </string-name>
          ;
          <string-name>
            <surname>Gutierrez</surname>
            ,
            <given-names>A.</given-names>
          </string-name>
          ;
          <string-name>
            <surname>Huchard</surname>
            ,
            <given-names>M.</given-names>
          </string-name>
          ;
          <string-name>
            <surname>Napoli</surname>
            ,
            <given-names>A.</given-names>
          </string-name>
          ;
          <string-name>
            <surname>Sigayret</surname>
            ,
            <given-names>A.</given-names>
          </string-name>
          (
          <year>2014</year>
          ).
          <article-title>Hermes: a simple and efficient algorithm for building the AOC-poset of a binary relation</article-title>
          .
          <source>Annals of Mathematics and Artificial Intelligence</source>
          ,
          <volume>72</volume>
          ,
          <issue>1</issue>
          , p.
          <fpage>45</fpage>
          -
          <lpage>71</lpage>
          .
        </mixed-citation>
      </ref>
      <ref id="ref2">
        <mixed-citation>
          2.
          <string-name>
            <surname>Carbonnel</surname>
          </string-name>
          , J.;
          <string-name>
            <surname>Bertet</surname>
            ,
            <given-names>K.</given-names>
          </string-name>
          ;
          <string-name>
            <surname>Huchard</surname>
            ,
            <given-names>M.</given-names>
          </string-name>
          ;
          <string-name>
            <surname>Nebut</surname>
            ,
            <given-names>C.</given-names>
          </string-name>
          (
          <year>2016</year>
          ).
          <article-title>FCA for software product lines representation: Mixing configuration and feature relationships in a unique canonical representation</article-title>
          .
          <source>In: Concept Lattices and their Applications (CLA'16)</source>
          , CEUR, p.
          <fpage>109</fpage>
          -
          <lpage>122</lpage>
          .
        </mixed-citation>
      </ref>
      <ref id="ref3">
        <mixed-citation>
          3.
          <string-name>
            <surname>Ganter</surname>
            ,
            <given-names>B.</given-names>
          </string-name>
          ;
          <string-name>
            <surname>Wille</surname>
            ,
            <given-names>R.</given-names>
          </string-name>
          (
          <year>1999</year>
          ).
          <article-title>Formal Concept Analysis</article-title>
          .
          <source>Mathematical Foundations</source>
          . Springer.
        </mixed-citation>
      </ref>
      <ref id="ref4">
        <mixed-citation>
          4.
          <string-name>
            <surname>Ganter</surname>
            ,
            <given-names>B.</given-names>
          </string-name>
          ;
          <string-name>
            <surname>Obiedkov</surname>
            ,
            <given-names>S.</given-names>
          </string-name>
          (
          <year>2016</year>
          ).
          <source>Conceptual Exploration</source>
          . Springer.
        </mixed-citation>
      </ref>
      <ref id="ref5">
        <mixed-citation>
          5.
          <string-name>
            <surname>Ganter</surname>
            ,
            <given-names>B.</given-names>
          </string-name>
          (
          <year>2019</year>
          ).
          <article-title>“Properties of Finite Lattices” by S. Reeg</article-title>
          and
          <string-name>
            <given-names>W.</given-names>
            <surname>Weiß</surname>
          </string-name>
          , Revisited. In: Cristea et al. (
          <article-title>eds) Formal Concept Analysis</article-title>
          .
          <source>ICFCA 2019. LNCS 11511</source>
          , Springer, p.
          <fpage>99</fpage>
          -
          <lpage>109</lpage>
          .
        </mixed-citation>
      </ref>
      <ref id="ref6">
        <mixed-citation>
          6.
          <string-name>
            <surname>Lakoff</surname>
            ,
            <given-names>G.</given-names>
          </string-name>
          (
          <year>1987</year>
          ). Women, Fire, and
          <string-name>
            <given-names>Dangerous</given-names>
            <surname>Things</surname>
          </string-name>
          .
          <article-title>What Categories Reveal about the Mind</article-title>
          . The University of Chicago Press.
        </mixed-citation>
      </ref>
      <ref id="ref7">
        <mixed-citation>
          7.
          <string-name>
            <surname>Lopez-Rodriguez</surname>
            <given-names>D.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Cordero</surname>
            <given-names>P.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Enciso</surname>
            <given-names>M.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Mora</surname>
            <given-names>A.</given-names>
          </string-name>
          (
          <year>2021</year>
          ).
          <article-title>Clustering and Identification of Core Implications</article-title>
          . In: Braud et al. (eds.)
          <article-title>Formal Concept Analysis</article-title>
          .
          <source>ICFCA 2021. LNAI 12733</source>
          , p.
          <fpage>138</fpage>
          -
          <lpage>154</lpage>
          .
        </mixed-citation>
      </ref>
      <ref id="ref8">
        <mixed-citation>
          8.
          <string-name>
            <surname>Osswald</surname>
            , R.; Petersen,
            <given-names>W.</given-names>
          </string-name>
          (
          <year>2002</year>
          ).
          <article-title>Induction of classifications from linguistic data</article-title>
          .
          <source>In: Proc. of the ECAI-Workshop on Advances in Formal Concept Analysis for Knowledge Discovery in Databases.</source>
        </mixed-citation>
      </ref>
      <ref id="ref9">
        <mixed-citation>
          9.
          <string-name>
            <surname>Prediger</surname>
            ,
            <given-names>S.</given-names>
          </string-name>
          (
          <year>1998</year>
          ).
          <article-title>Simple concept graphs: A logic approach</article-title>
          . In: Mugnier et al. (eds.) Conceptual Structures: Theory, Tools and
          <string-name>
            <surname>Applications. ICCS</surname>
          </string-name>
          <year>1998</year>
          .
          <source>LNCS 1453</source>
          , Springer, p.
          <fpage>225</fpage>
          -
          <lpage>239</lpage>
          .
        </mixed-citation>
      </ref>
      <ref id="ref10">
        <mixed-citation>
          10.
          <string-name>
            <surname>Priss</surname>
            ,
            <given-names>U.</given-names>
          </string-name>
          ;
          <string-name>
            <surname>Old</surname>
            ,
            <given-names>L. J.</given-names>
          </string-name>
          (
          <year>2010</year>
          ).
          <article-title>Concept Neighbourhoods in Lexical Databases</article-title>
          . In: Kwuida; Sertkaya (eds.),
          <article-title>Formal Concept Analysis</article-title>
          .
          <source>ICFCA 2010. LNCS 5986</source>
          , Springer, p.
          <fpage>283</fpage>
          -
          <lpage>295</lpage>
          .
        </mixed-citation>
      </ref>
      <ref id="ref11">
        <mixed-citation>
          11.
          <string-name>
            <surname>Priss</surname>
            ,
            <given-names>U.</given-names>
          </string-name>
          ;
          <string-name>
            <surname>Old</surname>
            ,
            <given-names>L. J.</given-names>
          </string-name>
          (
          <year>2011</year>
          ).
          <article-title>Data Weeding Techniques Applied to Roget's Thesaurus</article-title>
          . In: Wolff et al. (eds.)
          <article-title>Knowledge Processing and Data Analysis</article-title>
          .
          <source>KPP 2007. LNAI 6581</source>
          , Springer, p.
          <fpage>150</fpage>
          -
          <lpage>163</lpage>
          .
        </mixed-citation>
      </ref>
      <ref id="ref12">
        <mixed-citation>
          12.
          <string-name>
            <surname>Priss</surname>
            ,
            <given-names>U.</given-names>
          </string-name>
          (
          <year>2017</year>
          ).
          <article-title>Semiotic-Conceptual Analysis: A Proposal</article-title>
          .
          <source>International Journal of General Systems</source>
          ,
          <volume>46</volume>
          ,
          <issue>5</issue>
          , p.
          <fpage>569</fpage>
          -
          <lpage>585</lpage>
          .
        </mixed-citation>
      </ref>
      <ref id="ref13">
        <mixed-citation>
          13.
          <string-name>
            <surname>Priss</surname>
            ,
            <given-names>U.</given-names>
          </string-name>
          (
          <year>2021a</year>
          ).
          <article-title>Diagrammatic Representation of Conceptual Structures</article-title>
          . In: Braud et al. (eds.)
          <article-title>Formal Concept Analysis</article-title>
          .
          <source>ICFCA 2021. LNAI 12733</source>
          , p.
          <fpage>281</fpage>
          -
          <lpage>289</lpage>
          .
        </mixed-citation>
      </ref>
      <ref id="ref14">
        <mixed-citation>
          14.
          <string-name>
            <surname>Priss</surname>
            ,
            <given-names>U.</given-names>
          </string-name>
          (
          <year>2021b</year>
          ).
          <article-title>Conceptual Schemata as a Means for Structuring Teaching Materials</article-title>
          .
          <source>In: Concepts in Action: Representation, Learning, and Application (CARLA'21)</source>
          . Available at: https://www.conceptuccino.uni-osnabrueck.de/carla workshop/carla 2021.html
        </mixed-citation>
      </ref>
    </ref-list>
  </back>
</article>