<?xml version="1.0" encoding="UTF-8" standalone="no"?>
<!DOCTYPE article PUBLIC "-//NLM//DTD Journal Publishing DTD v2.3 20070202//EN" "journalpublishing.dtd">
<article xml:lang="EN" xmlns:mml="http://www.w3.org/1998/Math/MathML" xmlns:xlink="http://www.w3.org/1999/xlink" article-type="review-article">
<front>
<journal-meta>
<journal-id journal-id-type="publisher-id">Front. Big Data</journal-id>
<journal-title>Frontiers in Big Data</journal-title>
<abbrev-journal-title abbrev-type="pubmed">Front. Big Data</abbrev-journal-title>
<issn pub-type="epub">2624-909X</issn>
<publisher>
<publisher-name>Frontiers Media S.A.</publisher-name>
</publisher>
</journal-meta>
<article-meta>
<article-id pub-id-type="doi">10.3389/fdata.2024.1304439</article-id>
<article-categories>
<subj-group subj-group-type="heading">
<subject>Big Data</subject>
<subj-group>
<subject>Review</subject>
</subj-group>
</subj-group>
</article-categories>
<title-group>
<article-title>Knowledge-based recommender systems: overview and research directions</article-title>
</title-group>
<contrib-group>
<contrib contrib-type="author" corresp="yes">
<name><surname>Uta</surname> <given-names>Mathias</given-names></name>
<xref ref-type="aff" rid="aff1"><sup>1</sup></xref>
<xref ref-type="corresp" rid="c001"><sup>&#x0002A;</sup></xref>
<uri xlink:href="http://loop.frontiersin.org/people/2373014/overview"/>
<role content-type="https://credit.niso.org/contributor-roles/conceptualization/"/>
<role content-type="https://credit.niso.org/contributor-roles/data-curation/"/>
<role content-type="https://credit.niso.org/contributor-roles/formal-analysis/"/>
<role content-type="https://credit.niso.org/contributor-roles/investigation/"/>
<role content-type="https://credit.niso.org/contributor-roles/project-administration/"/>
<role content-type="https://credit.niso.org/contributor-roles/software/"/>
<role content-type="https://credit.niso.org/contributor-roles/validation/"/>
<role content-type="https://credit.niso.org/contributor-roles/writing-original-draft/"/>
<role content-type="https://credit.niso.org/contributor-roles/writing-review-editing/"/>
</contrib>
<contrib contrib-type="author">
<name><surname>Felfernig</surname> <given-names>Alexander</given-names></name>
<xref ref-type="aff" rid="aff2"><sup>2</sup></xref>
<uri xlink:href="http://loop.frontiersin.org/people/2193068/overview"/>
<role content-type="https://credit.niso.org/contributor-roles/conceptualization/"/>
<role content-type="https://credit.niso.org/contributor-roles/methodology/"/>
<role content-type="https://credit.niso.org/contributor-roles/supervision/"/>
<role content-type="https://credit.niso.org/contributor-roles/validation/"/>
<role content-type="https://credit.niso.org/contributor-roles/writing-original-draft/"/>
<role content-type="https://credit.niso.org/contributor-roles/writing-review-editing/"/>
</contrib>
<contrib contrib-type="author">
<name><surname>Le</surname> <given-names>Viet-Man</given-names></name>
<xref ref-type="aff" rid="aff2"><sup>2</sup></xref>
<uri xlink:href="http://loop.frontiersin.org/people/2571670/overview"/>
<role content-type="https://credit.niso.org/contributor-roles/conceptualization/"/>
<role content-type="https://credit.niso.org/contributor-roles/validation/"/>
<role content-type="https://credit.niso.org/contributor-roles/writing-review-editing/"/>
</contrib>
<contrib contrib-type="author">
<name><surname>Tran</surname> <given-names>Thi Ngoc Trang</given-names></name>
<xref ref-type="aff" rid="aff2"><sup>2</sup></xref>
<uri xlink:href="http://loop.frontiersin.org/people/2552800/overview"/>
<role content-type="https://credit.niso.org/contributor-roles/validation/"/>
<role content-type="https://credit.niso.org/contributor-roles/writing-review-editing/"/>
</contrib>
<contrib contrib-type="author">
<name><surname>Garber</surname> <given-names>Damian</given-names></name>
<xref ref-type="aff" rid="aff2"><sup>2</sup></xref>
<role content-type="https://credit.niso.org/contributor-roles/validation/"/>
<role content-type="https://credit.niso.org/contributor-roles/writing-review-editing/"/>
</contrib>
<contrib contrib-type="author">
<name><surname>Lubos</surname> <given-names>Sebastian</given-names></name>
<xref ref-type="aff" rid="aff2"><sup>2</sup></xref>
<uri xlink:href="http://loop.frontiersin.org/people/2175272/overview"/>
<role content-type="https://credit.niso.org/contributor-roles/validation/"/>
<role content-type="https://credit.niso.org/contributor-roles/writing-review-editing/"/>
</contrib>
<contrib contrib-type="author">
<name><surname>Burgstaller</surname> <given-names>Tamim</given-names></name>
<xref ref-type="aff" rid="aff2"><sup>2</sup></xref>
<role content-type="https://credit.niso.org/contributor-roles/validation/"/>
<role content-type="https://credit.niso.org/contributor-roles/writing-review-editing/"/>
</contrib>
</contrib-group>
<aff id="aff1"><sup>1</sup><institution>Siemens Energy AG</institution>, <addr-line>Erlangen</addr-line>, <country>Germany</country></aff>
<aff id="aff2"><sup>2</sup><institution>Institute of Software Technology (IST) - Applied Software Engineering &#x00026; Ai Research Group (ASE), Graz University of Technology</institution>, <addr-line>Graz</addr-line>, <country>Austria</country></aff>
<author-notes>
<fn fn-type="edited-by"><p>Edited by: Emanuel Laci&#x00107;, Infobip d.o.o., Croatia</p></fn>
<fn fn-type="edited-by"><p>Reviewed by: Bettina Fazzinga, University of Calabria, Italy</p>
<p>Simone Kopeinik, Know Center, Austria</p></fn>
<corresp id="c001">&#x0002A;Correspondence: Mathias Uta <email>mathias.uta&#x00040;siemens-energy.com</email></corresp>
</author-notes>
<pub-date pub-type="epub">
<day>26</day>
<month>02</month>
<year>2024</year>
</pub-date>
<pub-date pub-type="collection">
<year>2024</year>
</pub-date>
<volume>7</volume>
<elocation-id>1304439</elocation-id>
<history>
<date date-type="received">
<day>29</day>
<month>09</month>
<year>2023</year>
</date>
<date date-type="accepted">
<day>06</day>
<month>02</month>
<year>2024</year>
</date>
</history>
<permissions>
<copyright-statement>Copyright &#x000A9; 2024 Uta, Felfernig, Le, Tran, Garber, Lubos and Burgstaller.</copyright-statement>
<copyright-year>2024</copyright-year>
<copyright-holder>Uta, Felfernig, Le, Tran, Garber, Lubos and Burgstaller</copyright-holder>
<license xlink:href="http://creativecommons.org/licenses/by/4.0/"><p>This is an open-access article distributed under the terms of the Creative Commons Attribution License (CC BY). The use, distribution or reproduction in other forums is permitted, provided the original author(s) and the copyright owner(s) are credited and that the original publication in this journal is cited, in accordance with accepted academic practice. No use, distribution or reproduction is permitted which does not comply with these terms.</p></license></permissions>
<abstract>
<p>Recommender systems are decision support systems that help users to identify items of relevance from a potentially large set of alternatives. In contrast to the mainstream recommendation approaches of collaborative filtering and content-based filtering, knowledge-based recommenders exploit semantic user preference knowledge, item knowledge, and recommendation knowledge, to identify user-relevant items which is of specific relevance when dealing with complex and high-involvement items. Such recommenders are primarily applied in scenarios where users specify (and revise) their preferences, and related recommendations are determined on the basis of constraints or attribute-level similarity metrics. In this article, we provide an overview of the existing state-of-the-art in knowledge-based recommender systems. Different related recommendation techniques are explained on the basis of a working example from the domain of survey software services. On the basis of our analysis, we outline different directions for future research.</p></abstract>
<kwd-group>
<kwd>recommender systems</kwd>
<kwd>semantic recommender systems</kwd>
<kwd>knowledge-based recommender systems</kwd>
<kwd>case-based recommendation</kwd>
<kwd>constraint-based recommendation</kwd>
<kwd>critiquing-based recommendation</kwd>
<kwd>constraint solving</kwd>
<kwd>model-based diagnosis</kwd>
</kwd-group>
<contract-sponsor id="cn001">TU Graz, Internationale Beziehungen und Mobilit&#x000E4;tsprogramme<named-content content-type="fundref-id">10.13039/100008332</named-content></contract-sponsor>
<counts>
<fig-count count="0"/>
<table-count count="18"/>
<equation-count count="3"/>
<ref-count count="130"/>
<page-count count="19"/>
<word-count count="15868"/>
</counts>
<custom-meta-wrap>
<custom-meta>
<meta-name>section-at-acceptance</meta-name>
<meta-value>Recommender Systems</meta-value>
</custom-meta>
</custom-meta-wrap>
</article-meta>
</front>
<body>
<sec sec-type="intro" id="s1">
<title>1 Introduction</title>
<p>Recommender systems support users in identifying relevant items from a large set of alternatives and thus help to reduce the complexity of decisions and increase user satisfaction and sales (Felfernig and Burke, <xref ref-type="bibr" rid="B38">2008</xref>; Burke et al., <xref ref-type="bibr" rid="B12">2011</xref>; Knijnenburg et al., <xref ref-type="bibr" rid="B70">2012</xref>). <italic>Single-shot recommender systems</italic> recommend items based on already stored preferences of a user (e.g., videos a user purchased/liked in the past) without the need of engaging the user in a dialog for capturing further preferences (Rafter and Smyth, <xref ref-type="bibr" rid="B100">2005</xref>; Pramod and Bafna, <xref ref-type="bibr" rid="B99">2022</xref>). In contrast, <italic>conversational recommender systems</italic> perform preference elicitation on the basis of a user/recommender dialog (Goeker and Thompson, <xref ref-type="bibr" rid="B60">2000</xref>; Bridge, <xref ref-type="bibr" rid="B9">2002</xref>; Gao et al., <xref ref-type="bibr" rid="B59">2021</xref>). Depending on the application scenario, different recommendation approaches can be applied (see <xref ref-type="table" rid="T1">Tables 1</xref>, <xref ref-type="table" rid="T2">2</xref> for an overview of used data sources and properties of those recommendation approaches).</p>
<table-wrap position="float" id="T1">
<label>Table 1</label>
<caption><p>Basic recommendation approaches of collaborative filtering (CF), content-based filtering (CBF), and knowledge-based recommendation (KBR), and used data sources including the current user preferences, a user&#x00027;s preference history, the preferences of nearest neighbors, and item knowledge.</p></caption>
<table frame="box" rules="all">
<thead>
<tr style="background-color:#919497;color:#ffffff">
<th valign="top" align="left"><bold>Approach</bold></th>
<th valign="top" align="center"><bold>Preferences</bold></th>
<th valign="top" align="center"><bold>Preference history</bold></th>
<th valign="top" align="center"><bold>Nearest neighbors</bold></th>
<th valign="top" align="center"><bold>Item knowledge</bold></th>
</tr>
</thead>
<tbody>
 <tr>
<td valign="top" align="left">Collaborative (CF)</td>
<td valign="top" align="center">&#x02013;</td>
<td valign="top" align="center">&#x000D7;</td>
<td valign="top" align="center">&#x000D7;</td>
<td valign="top" align="center">&#x02013;</td>
</tr> <tr>
<td valign="top" align="left">Content-based (CBF)</td>
<td valign="top" align="center">&#x02013;</td>
<td valign="top" align="center">&#x000D7;</td>
<td valign="top" align="center">&#x02013;</td>
<td valign="top" align="center">&#x000D7;</td>
</tr> <tr>
<td valign="top" align="left">Knowledge-based (KBR)</td>
<td valign="top" align="center">&#x000D7;</td>
<td valign="top" align="center">&#x02013;</td>
<td valign="top" align="center">&#x02013;</td>
<td valign="top" align="center">&#x000D7;</td>
</tr></tbody>
</table>
</table-wrap>
<table-wrap position="float" id="T2">
<label>Table 2</label>
<caption><p><italic>Basic properties</italic> of different recommendation approaches: <italic>easy setup</italic> = low effort needed for setting up the recommender system, <italic>dialog-based</italic> = conversational process between system and user, <italic>serendipity</italic> = effect of proposing unexpected but relevant recommendations, <italic>cold-start problem</italic> = initial data are needed to provide reasonable recommendations, <italic>high-involvement items</italic> = a user carefully evaluates the candidate items since suboptimal decisions can have significant negative consequences.</p></caption>
<table frame="box" rules="all">
<thead>
<tr style="background-color:#919497;color:#ffffff">
<th valign="top" align="left"><bold>Recommendation approach</bold></th>
<th valign="top" align="center"><bold>Collaborative (CF)</bold></th>
<th valign="top" align="center"><bold>Content-based (CBF)</bold></th>
<th valign="top" align="center"><bold>Knowledge-based (KBR)</bold></th>
</tr>
</thead>
<tbody>
 <tr>
<td valign="top" align="left">Easy setup</td>
<td valign="top" align="center">&#x000D7;</td>
<td valign="top" align="center">&#x000D7;</td>
<td valign="top" align="center">&#x02013;</td>
</tr> <tr>
<td valign="top" align="left">Dialog-based</td>
<td valign="top" align="center">&#x02013;</td>
<td valign="top" align="center">&#x02013;</td>
<td valign="top" align="center">&#x000D7;</td>
</tr> <tr>
<td valign="top" align="left">Serendipity</td>
<td valign="top" align="center">&#x000D7;</td>
<td valign="top" align="center">&#x02013;</td>
<td valign="top" align="center">&#x000D7;</td>
</tr> <tr>
<td valign="top" align="left">Cold-start problem</td>
<td valign="top" align="center">&#x000D7;</td>
<td valign="top" align="center">&#x000D7;</td>
<td valign="top" align="center">&#x02013;</td>
</tr> <tr>
<td valign="top" align="left">High-involvement items</td>
<td valign="top" align="center">&#x02013;</td>
<td valign="top" align="center">&#x02013;</td>
<td valign="top" align="center">&#x000D7;</td>
</tr></tbody>
</table>
</table-wrap>
<p><italic>First</italic>, collaborative filtering (CF) (Ekstrand et al., <xref ref-type="bibr" rid="B27">2011</xref>) is based on the idea of simulating word-of-mouth promotion by determining recommendations on the basis of the preferences of so-called nearest neighbors (NNs), which are users with preferences similar to those of the current user. For example, a movie that has been watched by the nearest neighbors of the current user (but not by the current user) and has been evaluated positively by those nearest neighbors should also be recommended to the current user. A major advantage of CF approaches is an easy setup since no detailed information about the provided items is needed. Furthermore, serendipity effects can be created, i.e., collaborative filtering is a good choice for finding recommendations which are (in a positive sense) a kind of &#x0201C;surprise&#x0201D; for the user, thus supporting diversity and the identification of completely unexpected/unsearched items (Iaquinta et al., <xref ref-type="bibr" rid="B64">2008</xref>; Ziarani and Ravanmehr, <xref ref-type="bibr" rid="B129">2021</xref>). CF typically follows the idea of single-shot recommendation where no session-specific user dialogs are needed. A disadvantage of CF recommenders is cold-start problems which are due to the sparsity of rating information (regarding users and items) available in the recommendation algorithm, making it hard to identify accurate recommendations (Lika et al., <xref ref-type="bibr" rid="B79">2014</xref>).</p>
<p><italic>Second</italic>, content-based filtering (CBF) (Pazzani and Billsus, <xref ref-type="bibr" rid="B95">2007</xref>) is based on the idea of recommending items which are in one way or another similar to items the user has consumed in the past. In contrast to CF, CBF does not exploit the preferences of nearest neighbors which limits the cold-start problem to the availability of initial user item ratings. A kind of disadvantage of CBF recommendation approaches is need of item knowledge, for example, in terms of item categories and/or item descriptions which are used to derive a user profile representing a user item preference history. CBF systems are typically of type &#x0201C;single-shot&#x0201D;, i.e., no conversational user interface needs to be provided for preference elicitation purposes. <italic>Basic CBF</italic> that purely focuses on the recommendation of similar items is less appropriate when it comes to the triggering of serendipity effects (Iaquinta et al., <xref ref-type="bibr" rid="B64">2008</xref>). For example, if a user has purchased the song <italic>Personal Jesus</italic> from <italic>Depeche Mode</italic>, an item that could be recommended in the future could be the same song performed by <italic>Johnny Cash</italic>. However, further developments in content-based recommendation have improved the capability of CBF with regard to the achievement of serendipity effects, for example, on the basis of increasing the diversity of recommended items (Maccatrozzo et al., <xref ref-type="bibr" rid="B82">2017</xref>). In the line with CF approaches, CBF has an easy setup process, since only item knowledge is needed in the setup phase. Since preferences change over time, both CF and CBF have an issue with item domains characterized by infrequently articulated and changing preferences. For example, time intervals between individual car purchases of a user could be around 10 years&#x02014;in such long time periods, user preferences could completely change, which makes the identification of recommendations challenging without using a preference elicitation dialog.</p>
<p><italic>Third</italic>, knowledge-based recommender (KBR) systems can be considered as complementary to CF- and CBF-based approaches in terms of avoiding the related cold-start difficulties (Burke, <xref ref-type="bibr" rid="B10">2000</xref>; Towle and Quinn, <xref ref-type="bibr" rid="B112">2000</xref>; Lorenzi and Ricci, <xref ref-type="bibr" rid="B80">2005</xref>). KBR systems are based on the idea of collecting the preferences of a user (preference elicitation) within the scope of a dialog and then to recommend items either (1) on the basis of a predefined set of recommendation rules (constraints) or (2) using similarity metrics that help to identify items which are similar to the preferences of the user. The first approach is denoted as <italic>constraint-based recommendation</italic> (Felfernig and Burke, <xref ref-type="bibr" rid="B38">2008</xref>), whereas the second one is referred to as <italic>case-based recommendation</italic> (Lorenzi and Ricci, <xref ref-type="bibr" rid="B80">2005</xref>)&#x02014;these two can be regarded as major types of knowledge-based recommender systems (Aggarwal, <xref ref-type="bibr" rid="B1">2016</xref>). Serendipity effects in knowledge-based recommendation are limited by the static encoding in terms of constraints (rules) and similarity metrics. KBR systems support the determination of recommendations specifically in complex and high-involvement item domains [domains where suboptimal decisions can have significant negative consequences, for example, when investing in high-risk financial services (Felfernig et al., <xref ref-type="bibr" rid="B40">2006</xref>)] where items are not bought on a regular basis (Aggarwal, <xref ref-type="bibr" rid="B1">2016</xref>). Example item domains are financial services (Felfernig et al., <xref ref-type="bibr" rid="B44">2007</xref>; Musto et al., <xref ref-type="bibr" rid="B94">2015</xref>), software services (Felfernig et al., <xref ref-type="bibr" rid="B47">2021</xref>), apartment or house purchasing (Fano and Kurth, <xref ref-type="bibr" rid="B32">2003</xref>), and digital cameras (Felfernig et al., <xref ref-type="bibr" rid="B40">2006</xref>). These systems are able to take into account constraints (e.g., high-risk financial services must not be recommended to users with a low preparedness to take risks) and provide explanations of recommendations also in situations where no solution could be identified. In contrast to CF and CBF, KBR systems support explicit preference elicitation dialogs which makes them immune with regard to user preferences changing over time. Due to an often time-intensive knowledge exchange between domain experts and knowledge engineers, the definition of recommendation knowledge can trigger high setup costs (Ulz et al., <xref ref-type="bibr" rid="B114">2017</xref>). Both types of KBR systems (case-based and constraint-based) are conversational, since a preference elicitation dialog helps to figure out user preferences (Gao et al., <xref ref-type="bibr" rid="B59">2021</xref>).</p>
<sec>
<title>1.1 Further recommendation approaches</title>
<p>In addition to the three basic approaches of collaborative filtering, content-based filtering, and knowledge-based recommendation, there exist various further approaches. First, <italic>hybrid recommender systems</italic> (Burke, <xref ref-type="bibr" rid="B11">2002</xref>) exploit synergy effects by combining different recommendation approaches. For example, by combining CBF with CF, the cold-start problem can be solved by initially applying CBF in order to collect the relevant rating data needed for establishing a CF-based approach. Furthermore, <italic>group recommender systems</italic> (Masthoff, <xref ref-type="bibr" rid="B84">2015</xref>; Dara et al., <xref ref-type="bibr" rid="B23">2020</xref>; Felfernig et al., <xref ref-type="bibr" rid="B37">2024b</xref>) support the determination of recommendations for whole groups, i.e., not individual users. These systems apply basic recommendation approaches in such a way that recommendations satisfy the preferences of all or at least a subset of the group members. For example, the <italic>average</italic> user rating per item can be regarded as an item rating provided by the whole group.</p></sec>
<sec>
<title>1.2 Article contributions</title>
<p>The major contributions of this article are as follows. First, we provide an overview of the existing state-of-the-art in knowledge-based recommender systems. Our work significantly enhances existing overviews on the same topic (see the last row of <xref ref-type="table" rid="T3">Table 3</xref>) specifically in terms of the inclusion of new technological approaches and a broader view on how knowledge-based technologies are applied to recommender systems. Second, to assure understandability, we explain different underlying recommendation techniques on the basis of a working example. Third, to foster further related work, we discuss different open research directions derived from our literature analysis.</p>
<table-wrap position="float" id="T3">
<label>Table 3</label>
<caption><p>Overview of scientific contributions in knowledge-based recommender systems organized in the line of the primary focus of the paper: ALG, algorithms; PREF, preference elicitation; KA, knowledge acquisition; APP, application; FUR, further recommendation approaches and knowledge representations; OV, overview articles/papers including aspects related to knowledge-based recommendation.</p></caption>
<table frame="box" rules="all">
<thead>
<tr style="background-color:#919497;color:#ffffff">
<th valign="top" align="left"><bold>Approach</bold></th>
<th valign="top" align="left"><bold>ALG</bold></th>
<th valign="top" align="left"><bold>PREF</bold></th>
<th valign="top" align="left"><bold>KA</bold></th>
<th valign="top" align="left"><bold>APP</bold></th>
</tr>
</thead>
<tbody>
 <tr>
<td valign="top" align="left">Case-based (CBR)</td>
<td valign="top" align="left">Jannach, <xref ref-type="bibr" rid="B65">2006</xref></td>
<td valign="top" align="left">Goeker and Thompson, <xref ref-type="bibr" rid="B60">2000</xref>; Bridge, <xref ref-type="bibr" rid="B9">2002</xref>; McSherry, <xref ref-type="bibr" rid="B89">2003</xref>; Mirzadeh et al., <xref ref-type="bibr" rid="B90">2005</xref>; Christakopoulou et al., <xref ref-type="bibr" rid="B17">2016</xref></td>
<td valign="top" align="left">Khan and Hoffmann, <xref ref-type="bibr" rid="B69">2003</xref>; Zou et al., <xref ref-type="bibr" rid="B130">2020</xref></td>
<td valign="top" align="left">Fesenmaier et al., <xref ref-type="bibr" rid="B57">2003</xref>; Lee and Kim, <xref ref-type="bibr" rid="B77">2015</xref>; Musto et al., <xref ref-type="bibr" rid="B94">2015</xref>; Feely et al., <xref ref-type="bibr" rid="B34">2020</xref>; Bokolo, <xref ref-type="bibr" rid="B6">2021</xref>; Hernandez-Nieves et al., <xref ref-type="bibr" rid="B63">2021</xref></td>
</tr> <tr>
<td valign="top" align="left">Critiquing-based (CRIT)</td>
<td valign="top" align="left">Reilly et al., <xref ref-type="bibr" rid="B101">2004</xref>; Smyth et al., <xref ref-type="bibr" rid="B105">2004</xref>; McCarthy et al., <xref ref-type="bibr" rid="B86">2005</xref>; Mandl and Felfernig, <xref ref-type="bibr" rid="B83">2012</xref>; Murti et al., <xref ref-type="bibr" rid="B93">2016</xref></td>
<td valign="top" align="left">Zhang et al., <xref ref-type="bibr" rid="B126">2008</xref>; Chen et al., <xref ref-type="bibr" rid="B16">2017</xref>; Xie et al., <xref ref-type="bibr" rid="B124">2018</xref>; Wu et al., <xref ref-type="bibr" rid="B123">2019</xref>; G&#x000FC;ell et al., <xref ref-type="bibr" rid="B62">2020</xref></td>
<td valign="top" align="left">McCarthy et al., <xref ref-type="bibr" rid="B87">2010</xref></td>
<td valign="top" align="left">Burke et al., <xref ref-type="bibr" rid="B13">1996</xref>; Grasch et al., <xref ref-type="bibr" rid="B61">2013</xref></td>
</tr> <tr>
<td valign="top" align="left">Constraint-based (CON)</td>
<td valign="top" align="left">C&#x000F6;ster et al., <xref ref-type="bibr" rid="B20">2002</xref>; Felfernig and Burke, <xref ref-type="bibr" rid="B38">2008</xref>; Falkner et al., <xref ref-type="bibr" rid="B31">2011</xref>; Fargier et al., <xref ref-type="bibr" rid="B33">2016</xref>; Erdeniz et al., <xref ref-type="bibr" rid="B29">2019</xref>; Teppan and Zanker, <xref ref-type="bibr" rid="B109">2020</xref>; Felfernig et al., <xref ref-type="bibr" rid="B46">2023a</xref></td>
<td valign="top" align="left">Towle and Quinn, <xref ref-type="bibr" rid="B112">2000</xref>; Fano and Kurth, <xref ref-type="bibr" rid="B32">2003</xref>; Junker, <xref ref-type="bibr" rid="B68">2004</xref>; Felfernig et al., <xref ref-type="bibr" rid="B42">2009b</xref>, <xref ref-type="bibr" rid="B52">2012</xref>, <xref ref-type="bibr" rid="B51">2013c</xref>, <xref ref-type="bibr" rid="B53">2018a</xref>,<xref ref-type="bibr" rid="B54">b</xref>; Pereira et al., <xref ref-type="bibr" rid="B96">2016</xref>; Tazl et al., <xref ref-type="bibr" rid="B107">2019</xref>; Erdeniz et al., <xref ref-type="bibr" rid="B28">2022</xref>; Uta et al., <xref ref-type="bibr" rid="B115">2022</xref></td>
<td valign="top" align="left">Jannach and Kreutler, <xref ref-type="bibr" rid="B66">2007</xref>; Felfernig et al., <xref ref-type="bibr" rid="B39">2009a</xref>, <xref ref-type="bibr" rid="B48">2013a</xref>,<xref ref-type="bibr" rid="B50">b</xref>, <xref ref-type="bibr" rid="B49">2015</xref>; Daoudi et al., <xref ref-type="bibr" rid="B22">2016</xref>; Uta et al., <xref ref-type="bibr" rid="B116">2021</xref>; Lubos et al., <xref ref-type="bibr" rid="B81">2023</xref></td>
<td valign="top" align="left">Felfernig and Kiener, <xref ref-type="bibr" rid="B45">2005</xref>; Felfernig et al., <xref ref-type="bibr" rid="B40">2006</xref>, <xref ref-type="bibr" rid="B44">2007</xref>; Zanker et al., <xref ref-type="bibr" rid="B125">2006</xref>; Murphy et al., <xref ref-type="bibr" rid="B92">2015</xref>; Wobcke et al., <xref ref-type="bibr" rid="B121">2015</xref>; Ulz et al., <xref ref-type="bibr" rid="B114">2017</xref>; Almalis et al., <xref ref-type="bibr" rid="B2">2018</xref></td>
</tr> <tr>
<td valign="top" align="left">Further (FUR)</td>
<td valign="top" align="left">McCarthy et al., <xref ref-type="bibr" rid="B85">2006</xref></td>
<td valign="top" align="left">Burke, <xref ref-type="bibr" rid="B11">2002</xref>; Zhou et al., <xref ref-type="bibr" rid="B127">2020</xref>; Zhu et al., <xref ref-type="bibr" rid="B128">2020</xref>; Le et al., <xref ref-type="bibr" rid="B76">2022</xref></td>
<td valign="top" align="left">Wang et al., <xref ref-type="bibr" rid="B118">2019a</xref>,<xref ref-type="bibr" rid="B119">b</xref>; Sun et al., <xref ref-type="bibr" rid="B106">2020</xref>; Esheiba et al., <xref ref-type="bibr" rid="B30">2021</xref>; Sha et al., <xref ref-type="bibr" rid="B104">2021</xref></td>
<td valign="top" align="left">Lee et al., <xref ref-type="bibr" rid="B78">2006</xref>; Bahramian and Ali Abbaspour, <xref ref-type="bibr" rid="B4">2015</xref>; Colombo-Mendoza et al., <xref ref-type="bibr" rid="B18">2015</xref>; Pessemier et al., <xref ref-type="bibr" rid="B97">2017</xref>; Cordero et al., <xref ref-type="bibr" rid="B19">2020</xref>; Dong et al., <xref ref-type="bibr" rid="B24">2020</xref></td>
</tr> <tr>
<td valign="top" align="left">Overviews (OV)</td>
<td valign="top" align="left">Bridge et al., <xref ref-type="bibr" rid="B8">2005</xref>; Felfernig et al., <xref ref-type="bibr" rid="B41">2011</xref>, <xref ref-type="bibr" rid="B37">2024b</xref>; Aggarwal, <xref ref-type="bibr" rid="B1">2016</xref>; Gao et al., <xref ref-type="bibr" rid="B59">2021</xref></td>
<td valign="top" align="left">Lorenzi and Ricci, <xref ref-type="bibr" rid="B80">2005</xref>; Chen and Pu, <xref ref-type="bibr" rid="B15">2012</xref>; Masthoff, <xref ref-type="bibr" rid="B84">2015</xref>; Atas et al., <xref ref-type="bibr" rid="B3">2021</xref>; Felfernig et al., <xref ref-type="bibr" rid="B47">2021</xref>; Jannach et al., <xref ref-type="bibr" rid="B67">2021</xref>; Tran et al., <xref ref-type="bibr" rid="B113">2023</xref></td>
<td valign="top" align="left">Felfernig, <xref ref-type="bibr" rid="B35">2007</xref>; Bouraga et al., <xref ref-type="bibr" rid="B7">2014</xref>; Felfernig et al., <xref ref-type="bibr" rid="B43">2014</xref>; Cena et al., <xref ref-type="bibr" rid="B14">2021</xref>; Popescu et al., <xref ref-type="bibr" rid="B98">2022</xref></td>
<td valign="top" align="left">Burke, <xref ref-type="bibr" rid="B10">2000</xref>; Felfernig et al., <xref ref-type="bibr" rid="B36">2024a</xref></td>
</tr></tbody>
</table>
</table-wrap>
<p>The remainder of this article is organized as follows. In Section 2, we explain the methodology applied for our literature analysis. An introduction to basic knowledge-based recommendation approaches is presented in Section 3, where we specifically focus on techniques and applications of case-based and constraint-based recommendation. Thereafter, in Section 4, we provide an overview of advanced techniques in knowledge-based recommendation with a specific focus on integration scenarios with machine learning. In this context, we also discuss related topics such as hybrid recommendation with knowledge-based recommenders and knowledge-based group recommender systems. In Section 5, we discuss the identified research directions. The article is concluded with Section 6.</p></sec></sec>
<sec sec-type="methods" id="s2">
<title>2 Methodology</title>
<p>Our overview of the existing state-of-the-art in knowledge-based recommendation (KBR) is based on a literature analysis conducted using the activities of <italic>search</italic> (querying of leading research portals), <italic>review</italic> (evaluating and classifying the identified scientific contributions), and <italic>discussion of reviewed contributions</italic> (deciding about inclusion of the identified studies in our overview based on the selection criteria of quality and relevance). Queries have been performed between December 2023 and January 2024 on the research platforms Google Scholar,<xref ref-type="fn" rid="fn0001"><sup>1</sup></xref> ResearchGate,<xref ref-type="fn" rid="fn0002"><sup>2</sup></xref> ScienceDirect,<xref ref-type="fn" rid="fn0003"><sup>3</sup></xref> SpringerLink,<xref ref-type="fn" rid="fn0004"><sup>4</sup></xref> and Elsevier,<xref ref-type="fn" rid="fn0005"><sup>5</sup></xref> using the keywords of &#x0201C;recommender systems&#x0201D; &#x0002B; [&#x0201C;knowledge-based&#x0201D; | &#x0201C;case-based&#x0201D; | &#x0201C;critiquing&#x0201D; | &#x0201C;ontologies&#x0201D; | &#x0201C;knowledge graphs&#x0201D; | &#x0201C;constraint satisfaction&#x0201D; | &#x0201C;conversational&#x0201D; | &#x0201C;mass customization&#x0201D; | &#x0201C;groups&#x0201D; | &#x0201C;overview&#x0201D;], representing 10 individual search queries. Using these queries, we have also analyzed topic-related scientific contribution in conferences and journals: the International Joint Conference on Artificial Intelligence (IJCAI), the AAAI Conference on Artificial Intelligence, the European Conference on Artificial Intelligence (ECAI), the Recommender Systems Conference (RecSys), the User Modeling, Adaptation, and Personalization (UMAP) conference, the Constraint Programming Conference (CP), the Software Product Line Conference (SPLC), User Modeling and User-Adapted Interaction (UMUAI), and ACM Transactions on Recommender Systems. Thereafter, using the snowballing technique (Wohlin, <xref ref-type="bibr" rid="B122">2014</xref>), we have analyzed the reference sections of the identified studies. Major criteria for estimating the relevance of a paper were (1) a <italic>topic-wise match</italic>, i.e., a relationship to knowledge-based recommenders and (2) an <italic>official publication</italic> in a workshop, conference, journal, magazine, book, or PhD thesis. With our analysis, we have identified 97 publications directly related to the topic of knowledge-based recommendation that have been used as a basis for this article (see <xref ref-type="table" rid="T3">Table 3</xref>).</p></sec>
<sec id="s3">
<title>3 Basic approaches and applications</title>
<p>In this section, we introduce a working example from the domain of <italic>survey software service recommendation</italic> that is used to explain different knowledge-based recommendation approaches. The underlying scenario is that users search for a survey software configuration that fulfills their preferences, for example, a researcher received a new project funding and is now interested in purchasing a survey software that supports different user studies envisioned for the new project. In many cases, Web applications (services) are preferred over solutions requiring an installation at the customer site. In such a scenario, knowledge-based recommenders can support users in identifying an appropriate configuration (including pricing) of a survey software service that fulfills their wishes and needs. In our example, we include the user-selectable survey software features <italic>ABtesting</italic> (should ABtesting be supported by the survey software), <italic>statistics</italic> (should a basic statistics feature be included), <italic>multiplechoice</italic> (should the specification of multiple-choice questions be possible), and <italic>license</italic> [which license model is preferred&#x02014;<italic>free of charge</italic> (0) vs. <italic>with costs</italic>, i.e., 100]. In the following, we show how knowledge-based recommenders can support the identification of relevant items, i.e., survey software configurations.</p>
<p>Knowledge-based recommender systems can operate on different knowledge representations&#x02014;these knowledge representations will be explained and exemplified in Section 3.1. Thereafter, we introduce the two basic approaches to knowledge-based recommendation, which are (1) <italic>case-based recommendation</italic> including <italic>critiquing-based recommendation</italic> as a specific form of case-based recommendation (see Section 3.2) and (2) <italic>constraint-based recommendation</italic> (see Section 3.3).</p>
<sec>
<title>3.1 Recommendation knowledge representations</title>
<p>Knowledge representations of knowledge-based recommender systems can be (1) <italic>table-based</italic> which is used in scenarios where items are represented in terms of product table entries or (2) <italic>constraint-based</italic> which is used in scenarios where items are defined on the basis of a set of <italic>restrictions</italic> (also denoted as <italic>rules</italic> or <italic>constraints</italic>). In the first case (extensional representation&#x02014;see, for example, <xref ref-type="table" rid="T4">Table 4</xref>), each item that could be recommended is explicitly defined in a corresponding item (product) table. In the second case, there is no need to enumerate all items since items are specified in a constraint-based fashion (intensional representation&#x02014;see, for example, <xref ref-type="table" rid="T5">Table 5</xref>).</p>
<table-wrap position="float" id="T4">
<label>Table 4</label>
<caption><p>Extensional itemset representation where each item is represented as a table entry assuming the item (table) attributes <italic>ABtesting</italic> (0,1), <italic>statistics</italic> (0,1), <italic>multiplechoice</italic> (0,1), and <italic>license</italic> (0,100).</p></caption>
<table frame="box" rules="all">
<thead>
<tr style="background-color:#919497;color:#ffffff">
<th valign="top" align="left"><bold>Item</bold></th>
<th valign="top" align="center"><bold>ABtesting</bold></th>
<th valign="top" align="center"><bold>Statistics</bold></th>
<th valign="top" align="center"><bold>Multiplechoice</bold></th>
<th valign="top" align="center"><bold>License</bold></th>
</tr>
</thead>
<tbody>
 <tr>
<td valign="top" align="left"><italic>i</italic><sub>1</sub></td>
<td valign="top" align="center">0</td>
<td valign="top" align="center">1</td>
<td valign="top" align="center">0</td>
<td valign="top" align="center">0</td>
</tr> <tr>
<td valign="top" align="left"><italic>i</italic><sub>2</sub></td>
<td valign="top" align="center">0</td>
<td valign="top" align="center">0</td>
<td valign="top" align="center">1</td>
<td valign="top" align="center">100</td>
</tr> <tr>
<td valign="top" align="left"><italic>i</italic><sub>3</sub></td>
<td valign="top" align="center">1</td>
<td valign="top" align="center">1</td>
<td valign="top" align="center">0</td>
<td valign="top" align="center">100</td>
</tr> <tr>
<td valign="top" align="left"><italic>i</italic><sub>4</sub></td>
<td valign="top" align="center">0</td>
<td valign="top" align="center">1</td>
<td valign="top" align="center">1</td>
<td valign="top" align="center">100</td>
</tr> <tr>
<td valign="top" align="left"><italic>i</italic><sub>5</sub></td>
<td valign="top" align="center">1</td>
<td valign="top" align="center">1</td>
<td valign="top" align="center">1</td>
<td valign="top" align="center">100</td>
</tr></tbody>
</table>
<table-wrap-foot>
<p>In our working example, the offered survey software configurations (items <italic>i</italic><sub>1</sub>..<italic>i</italic><sub>5</sub>) represent the complete set of items (i.e., the product/item catalog). For example, item <italic>i</italic><sub>1</sub> represents a survey software configuration (a &#x0201C;free of charge version&#x0201D;) which does not support <italic>ABtesting</italic> and <italic>multiplechoice</italic> questions, i.e., only single choice questions can be asked and the <italic>statistics</italic> feature supports a basic analysis of survey data.</p>
</table-wrap-foot>
</table-wrap>
<table-wrap position="float" id="T5">
<label>Table 5</label>
<caption><p>Intensional solution space representation in terms of a set of constraints {<italic>c</italic><sub>1</sub>..<italic>c</italic><sub>5</sub>} on the CSP variables <italic>ABtesting, statistics, license</italic>, and <italic>multiplechoice</italic>.</p></caption>
<table frame="box" rules="all">
<thead>
<tr style="background-color:#919497;color:#ffffff">
<th valign="top" align="left"><bold>Id</bold></th>
<th valign="top" align="left"><bold>Constraint</bold></th>
</tr>
</thead>
<tbody>
 <tr>
<td valign="top" align="left"><italic>c</italic><sub>1</sub></td>
<td valign="top" align="left">ABtesting=1 &#x02192; statistics=1</td>
</tr> <tr>
<td valign="top" align="left"><italic>c</italic><sub>2</sub></td>
<td valign="top" align="left">&#x000AC;(ABtesting=1 &#x02227; license=0)</td>
</tr> <tr>
<td valign="top" align="left"><italic>c</italic><sub>3</sub></td>
<td valign="top" align="left">&#x000AC;(multiplechoice=1 &#x02227; license=0)</td>
</tr> <tr>
<td valign="top" align="left"><italic>c</italic><sub>4</sub></td>
<td valign="top" align="left">&#x000AC; multiplechoice=1 &#x02227;&#x000AC; ABtesting=1 &#x02192; license=0</td>
</tr> <tr>
<td valign="top" align="left"><italic>c</italic><sub>5</sub></td>
<td valign="top" align="left">&#x000AC;(ABtesting=0 &#x02227; statistics=0 &#x02227; multiplechoice=0 &#x02227; license=0)</td>
</tr></tbody>
</table>
</table-wrap>
<sec>
<title>3.1.1 Table-based representations</title>
<p>In many knowledge-based recommendation scenarios, the offered itemset is represented in terms of an item (product) table (see <xref ref-type="table" rid="T4">Table 4</xref>). The itemset is defined extensionally, i.e., all selectable alternatives (items) are enumerated. In our example, five different service configurations (items <italic>i</italic><sub>1</sub>..<italic>i</italic><sub>5</sub>) can be offered to a user. Table-based representations can be applied if the set of offered items is limited, i.e., the item space is rather small which is often the case, for example, in digital camera or financial service recommendation (Felfernig et al., <xref ref-type="bibr" rid="B40">2006</xref>, <xref ref-type="bibr" rid="B44">2007</xref>). Using a table-based knowledge representation, corresponding database queries can be performed to identify a set of recommendation candidates that support the preferences defined by the user (Felfernig et al., <xref ref-type="bibr" rid="B40">2006</xref>, <xref ref-type="bibr" rid="B46">2023a</xref>). An example of a <italic>user preference</italic> regarding the itemset defined in <xref ref-type="table" rid="T4">Table 4</xref> could be <italic>ABtesting</italic> &#x0003D; 1, meaning that the user is interested in a survey software that includes (supports) <italic>ABtesting</italic>. For simplicity, we assume that attributes have a corresponding Boolean domain definition, for example, the domain of attribute <italic>ABtesting</italic> is {0, 1} where 1 &#x0003D; <italic>true</italic> (feature included) and 0 &#x0003D; <italic>false</italic>. One exception thereof is the <italic>license</italic> attribute with a domain {0, 100} representing the price of a license.</p></sec>
<sec>
<title>3.1.2 Constraint-based representations</title>
<p>Alternatively, itemsets can be represented in an intensional fashion on the basis of a set of domain-specific constraints (see <xref ref-type="table" rid="T5">Table 5</xref>), for example, as a <italic>constraint satisfaction problem</italic> (CSP) (Rossi et al., <xref ref-type="bibr" rid="B103">2006</xref>; Felfernig and Burke, <xref ref-type="bibr" rid="B38">2008</xref>). Such knowledge representations are specifically useful if the solution (item) space becomes intractable, i.e., defining and maintaining all alternatives is extremely inefficient and error-prone (or even impossible) and related search queries become inefficient and at least impractical for interactive settings (Falkner et al., <xref ref-type="bibr" rid="B31">2011</xref>).</p>
<p>The constraints in <xref ref-type="table" rid="T5">Table 5</xref> represent exactly the solution space, as shown in <xref ref-type="table" rid="T4">Table 4</xref>. If such constraints are not explicitly known, a given set of items can be defined in terms of one constraint in disjunctive normal form, for example, the entries in <xref ref-type="table" rid="T4">Table 4</xref> would be represented as (<italic>ABtesting</italic> &#x0003D; 0&#x02227;<italic>statistics</italic> &#x0003D; 1 &#x02227; <italic>license</italic> &#x0003D; 0 &#x02227; <italic>multiplechoice</italic> &#x0003D; 0) &#x02228; .. &#x02228; (<italic>ABtesting</italic> &#x0003D; 1 &#x02227; <italic>statistics</italic> &#x0003D; 1 &#x02227; <italic>license</italic> &#x0003D; 100 &#x02227; <italic>multiplechoice</italic> &#x0003D; 1)&#x02014;for details, we refer to Felfernig and Burke (<xref ref-type="bibr" rid="B38">2008</xref>).</p></sec>
<sec>
<title>3.1.3 Further knowledge representations</title>
<p>Intensional representations of solution spaces (itemsets) as presented in <xref ref-type="table" rid="T5">Table 5</xref> can be implemented with different knowledge representations ranging from <italic>constraint satisfaction problems</italic> (CSPs) (Rossi et al., <xref ref-type="bibr" rid="B103">2006</xref>; Felfernig and Burke, <xref ref-type="bibr" rid="B38">2008</xref>) and <italic>Boolean satisfiability problems</italic> (SAT problems) (Biere et al., <xref ref-type="bibr" rid="B5">2021</xref>; Felfernig et al., <xref ref-type="bibr" rid="B47">2021</xref>) to less frequently used recommendation knowledge representations such as <italic>answer set programming</italic> (ASP) (Eiter et al., <xref ref-type="bibr" rid="B26">2009</xref>; Teppan and Zanker, <xref ref-type="bibr" rid="B109">2020</xref>) and <italic>ontology-based knowledge representations</italic>, for example, <italic>description logics</italic> (DL) (Lee et al., <xref ref-type="bibr" rid="B78">2006</xref>; McGuinness, <xref ref-type="bibr" rid="B88">2007</xref>). In addition, database queries can be applied in such a way that intensionally formulated recommendation knowledge is encoded directly in database queries&#x02014;see, for example, Felfernig et al. (<xref ref-type="bibr" rid="B40">2006</xref>, <xref ref-type="bibr" rid="B46">2023a</xref>). Without loss of generality, in this article, we focus on CSP-based representations when discussing the concepts of constraint-based recommendation. As a basis for our discussion of case-based recommendation approaches, we will use the entries of <xref ref-type="table" rid="T4">Table 4</xref>.</p></sec></sec>
<sec>
<title>3.2 Case-based recommendation</title>
<sec>
<title>3.2.1 Basic approach</title>
<p>Following the basic concepts of case-based reasoning (Kolodner, <xref ref-type="bibr" rid="B71">2014</xref>), case-based recommendation uses a knowledge-rich representation of the item domain and can therefore be classified as a kind of knowledge-based recommendation (Burke, <xref ref-type="bibr" rid="B10">2000</xref>; Khan and Hoffmann, <xref ref-type="bibr" rid="B69">2003</xref>; Lorenzi and Ricci, <xref ref-type="bibr" rid="B80">2005</xref>). In a basic setting, the item assortment can be regarded as the case base, and recommendations are determined by identifying those items from the case base which &#x0201C;support&#x0201D; the user preferences (Lorenzi and Ricci, <xref ref-type="bibr" rid="B80">2005</xref>). In this context, product features (also denoted as properties or attributes) are used to specify user preferences. The more preferences are supported by an item, the higher its user relevance. Examples of case-based recommendation approaches going beyond an equality match between item properties and user preferences are the following&#x02014;see, for example, Lorenzi and Ricci (<xref ref-type="bibr" rid="B80">2005</xref>).</p></sec>
<sec>
<title>3.2.2 Interest confidence value</title>
<p>This approach is based on the idea of predicting item relevance on the basis of the similarity of a new item with items a user has already evaluated positively in the past (Lorenzi and Ricci, <xref ref-type="bibr" rid="B80">2005</xref>; Musto et al., <xref ref-type="bibr" rid="B94">2015</xref>). This approach is in the line with the ideas of content-based recommendation where the similarity between a new item and properties of already consumed items is used to estimate recommendation relevance. A simple example of the application of interest confidence values (<italic>icv</italic>) is shown in <xref ref-type="table" rid="T6">Table 6</xref>, where the <italic>average</italic> (<italic>avg</italic>) <italic>similarity</italic> between a new item (the user did not see up to now) and (consumed) items positively evaluated in the past is used to estimate item relevance.</p>
<table-wrap position="float" id="T6">
<label>Table 6</label>
<caption><p>Example of an <italic>interest confidence value</italic> (<italic>icv</italic>)-based evaluation of the user relevance of new items (<italic>in</italic><sub><italic>k</italic></sub>) on the basis of the similarity with already consumed items <italic>i</italic><sub><italic>l</italic></sub>.</p></caption>
<table frame="box" rules="all">
<thead>
<tr style="background-color:#919497;color:#ffffff">
<th valign="top" align="left"><bold>Consumed items</bold></th>
<th valign="top" align="left" colspan="5"><bold>New items</bold></th>
</tr>
</thead>
<tbody>
<tr style="background-color:#919497;color:#ffffff">
<td/>
<td valign="top" align="center"><italic>in</italic><sub>1</sub></td>
<td valign="top" align="center"><italic>in</italic><sub>2</sub></td>
<td valign="top" align="center"><italic>in</italic><sub>3</sub></td>
<td valign="top" align="center"><italic>in</italic><sub>4</sub></td>
<td valign="top" align="center"><italic>in</italic><sub>5</sub></td>
</tr> <tr>
<td valign="top" align="left"><italic>i</italic><sub>1</sub></td>
<td valign="top" align="center">0.2</td>
<td valign="top" align="center">0.4</td>
<td valign="top" align="center">0.3</td>
<td valign="top" align="center">0.9</td>
<td valign="top" align="center">0.5</td>
</tr> <tr>
<td valign="top" align="left"><italic>i</italic><sub>2</sub></td>
<td valign="top" align="center">0.4</td>
<td valign="top" align="center">0.6</td>
<td valign="top" align="center">0.2</td>
<td valign="top" align="center">0.6</td>
<td valign="top" align="center">0.7</td>
</tr> <tr>
<td valign="top" align="left"><italic>i</italic><sub>3</sub></td>
<td valign="top" align="center">0.4</td>
<td valign="top" align="center">0.1</td>
<td valign="top" align="center">0.5</td>
<td valign="top" align="center">0.5</td>
<td valign="top" align="center">0.6</td>
</tr> <tr>
<td valign="top" align="left">icv (avg)</td>
<td valign="top" align="center">0.33</td>
<td valign="top" align="center">0.36</td>
<td valign="top" align="center">0.33</td>
<td valign="top" align="center">0.66</td>
<td valign="top" align="center">0.6</td>
</tr></tbody>
</table>
<table-wrap-foot>
<p>For example, the similarity between the consumed item <italic>i</italic><sub>1</sub> and the new item <italic>in</italic><sub>2</sub> is assumed to be 0.4. In this example, item <italic>in</italic><sub>4</sub> has the highest <italic>interest confidence value</italic> (0.66) and therefore can be regarded as a user-relevant item.</p>
</table-wrap-foot>
</table-wrap>
</sec>
<sec>
<title>3.2.3 Attribute-level similarity metrics</title>
<p>This approach is based on the idea that the degree of satisfaction of individual user requirements has a direct impact on the corresponding item ranking (Lorenzi and Ricci, <xref ref-type="bibr" rid="B80">2005</xref>). In such contexts, attribute-level similarity metrics (McSherry, <xref ref-type="bibr" rid="B89">2003</xref>) can be used to determine the similarity between the user requirements and the items included in the product assortment. For example, if explicit price information of an item is available, the <italic>less is better</italic> (LIB) similarity metric can be applied (the lower the price, the higher the item ranking). The <italic>more is better</italic> (MIB) similarity metric can be applied in the context of technical attributes, such as the resolution of a digital camera or the return rate of a financial service (McSherry, <xref ref-type="bibr" rid="B89">2003</xref>; Felfernig et al., <xref ref-type="bibr" rid="B51">2013c</xref>) (the higher the attribute value the better). <italic>Equal is better</italic> (EIB) is used in contexts where users explicitly require a specific attribute value (e.g., the color of a car), and <italic>nearer is better</italic> (NIB) can be used in situations where an item should fulfill a specific requirement as good as possible, for example, the size of a TV screen in the living room. The overall similarity between user requirements and an item is then determined on the basis of a &#x0201C;global&#x0201D; similarity that combines individual attribute-level similarity functions. In our working example, the <italic>license</italic> attribute could be associated with an <italic>LIB</italic>, the remaining attributes with an <italic>EIB</italic> attribute-level similarity.</p></sec>
<sec>
<title>3.2.4 Refine, relax, and compromise</title>
<p>When querying a case base (i.e., an item catalog) with a set of user preferences, it can happen that the number of candidate items (items that satisfy the user preferences) is (1) too large and&#x02014;as a consequence&#x02014;the initial set of user requirements needs to be refined or (2) too small (in the worst case, no solution could be identified), which means that the user requirements have to be relaxed. In the first case, the set of user requirements needs to be extended, for example, if a user has specified the requirement <italic>statistics</italic> &#x0003D; 1, this results in four candidate items ({<italic>i</italic><sub>1</sub>, <italic>i</italic><sub>3</sub>, <italic>i</italic><sub>4</sub>, <italic>i</italic><sub>5</sub>}&#x02014;see <xref ref-type="table" rid="T4">Table 4</xref>). Refining the original query to <italic>statistics</italic> &#x0003D; 1 &#x02227; <italic>ABtesting</italic> &#x0003D; 1 reduces the set of candidate items to {<italic>i</italic><sub>3</sub>, <italic>i</italic><sub>5</sub>}. In contrary, if a user has specified the requirement <italic>ABtesting</italic> &#x0003D; 1 &#x02227; <italic>license</italic> &#x0003D; 0, the corresponding query would result in an empty set. The user has two options to resolve the inconsistency, i.e., to relax the query: either to exclude <italic>ABtesting</italic> or to accept a <italic>license</italic> payment, i.e., <italic>license</italic> &#x0003D; 100. Such trade-off decisions can be supported by so-called <italic>compromise-based user interfaces</italic> which group items with regard to different possible compromises (McSherry, <xref ref-type="bibr" rid="B89">2003</xref>). Such interfaces would group and explain candidate items in the line of, for example, <italic>most of your requirements are fulfilled, however, these items require a license payment</italic>.</p></sec>
<sec>
<title>3.2.5 Critiquing</title>
<p>Critiquing-based recommendation originates from different case-based recommenders (Kolodner, <xref ref-type="bibr" rid="B72">1992</xref>; Bridge et al., <xref ref-type="bibr" rid="B8">2005</xref>) which often support a search-based approach where&#x02014;depending on a set of defined user preferences&#x02014;the system recommends items which support in one way or another those preferences. While basic case-based and constraint-based recommendation focus on supporting a <italic>search-based recommendation process</italic>, critiquing-based recommender systems (as a specific type of case-based recommender system) follow a <italic>navigation-based approach</italic> (Chen and Pu, <xref ref-type="bibr" rid="B15">2012</xref>), which focuses on better supporting users in <italic>exploring</italic> the solution (item) space. Critiquing-based recommendation is based on the idea of presenting <italic>example (reference) items</italic> to a user who then can (1) accept the proposed item or (2) define critiques in terms of changes that are needed to make an item acceptable. Existing critiquing-based recommenders are based on a predefined itemset (product table)&#x02014;see <xref ref-type="table" rid="T4">Table 4</xref>. These systems are regarded as knowledge-based, since items are associated with semantic properties, and user-defined (selected) critiques can be regarded as logical criteria (constraints) to be fulfilled by recommendations.</p></sec>
<sec>
<title>3.2.6 Unit critiquing</title>
<p>Let us assume that in the context of our working example a critiquing-based recommender supports six basic critiques which are (1) <italic>furtherstat</italic>, (2) <italic>reducestat</italic>, (3) <italic>excludemc</italic>, (4) <italic>includemc</italic>, (5) <italic>excludelicense</italic>, and (6) <italic>includelicense</italic>. The critiquing-based approach used in this example is <italic>unit-critiquing</italic> (Chen and Pu, <xref ref-type="bibr" rid="B15">2012</xref>; Mandl and Felfernig, <xref ref-type="bibr" rid="B83">2012</xref>), where in each critiquing cycle, a critique on an individual item attribute is specified. <xref ref-type="table" rid="T7">Table 7</xref> shows how critiques can be translated into corresponding item selection criteria. For example, if a user selects the critique <italic>further statistics</italic> (<italic>furtherstat</italic>) and statistics is not included in the shown reference item, the corresponding selection criteria would be <italic>statistics</italic> &#x0003D; 1. Furthermore, if statistics is already included in the reference item, <italic>ABtesting</italic> &#x0003D; 1 would be defined as additional selection criteria (see the entries in <xref ref-type="table" rid="T7">Table 7</xref>).</p>
<table-wrap position="float" id="T7">
<label>Table 7</label>
<caption><p>Translating critiques into item selection criteria where <italic>mc</italic>=<italic>multiplechoice, stat</italic>=<italic>statistics</italic>, and &#x0201C;&#x021A6;&#x0201D; represents a mapping operator from critiques to item selection criteria.</p></caption>
<table frame="box" rules="all">
<thead>
<tr style="background-color:#919497;color:#ffffff">
<th valign="top" align="left"><bold>Critique</bold></th>
<th valign="top" align="left"><bold>Item selection criteria</bold></th>
</tr>
</thead>
<tbody>
 <tr>
<td valign="top" align="left">Furtherstat</td>
<td valign="top" align="left"><italic>Statistics</italic> &#x0003D; 0&#x021A6;<italic>statistics</italic> &#x0003D; 1</td>
</tr>
 <tr>
<td/>
<td valign="top" align="left"><italic>Statistics</italic> &#x0003D; 1&#x021A6;<italic>ABtesting</italic> &#x0003D; 1</td>
</tr> <tr>
<td valign="top" align="left">Reducestat</td>
<td valign="top" align="left"><italic>ABtesting</italic> &#x0003D; 1&#x021A6;<italic>ABtesting</italic> &#x0003D; 0</td>
</tr>
 <tr>
<td/>
<td valign="top" align="left"><italic>Statistics</italic> &#x0003D; 1 &#x02227; <italic>ABtesting</italic> &#x0003D; 0&#x021A6;<italic>statistics</italic> &#x0003D; 0</td>
</tr> <tr>
<td valign="top" align="left">Excludemc</td>
<td valign="top" align="left"><italic>Multiplechoice</italic> &#x0003D; 1&#x021A6;<italic>multiplechoice</italic> &#x0003D; 0</td>
</tr> <tr>
<td valign="top" align="left">Includemc</td>
<td valign="top" align="left"><italic>Multiplechoice</italic> &#x0003D; 0&#x021A6;<italic>multiplechoice</italic> &#x0003D; 1</td>
</tr> <tr>
<td valign="top" align="left">Excludelicense</td>
<td valign="top" align="left"><italic>License</italic> &#x0003D; 100&#x021A6;<italic>license</italic> &#x0003D; 0</td>
</tr> <tr>
<td valign="top" align="left">Includelicense</td>
<td valign="top" align="left"><italic>License</italic> &#x0003D; 0&#x021A6;<italic>license</italic> &#x0003D; 100</td>
</tr></tbody>
</table>
<table-wrap-foot>
<p>For example, if the critique <italic>excludelicense</italic> is specified by the user, an item supporting the selection criteria <italic>license</italic> &#x0003D; 0 will be shown.</p>
</table-wrap-foot>
</table-wrap>
<p><xref ref-type="table" rid="T8">Table 8</xref> shows an example of a <italic>unit critiquing session</italic> where the initial (reference) item presented to the user is <italic>i</italic><sub>1</sub>. The user specifies the critique <italic>furtherstat</italic> which requires the inclusion of additional statistic features into the survey software service configuration. Taking into account, this critique means to combine the properties of the reference item <italic>i</italic><sub>1</sub> (<italic>ABtesting</italic> &#x0003D; 0, <italic>statistics</italic> &#x0003D; 1, <italic>license</italic> &#x0003D; 0, <italic>multiplechoice</italic> &#x0003D; 0) with the selection criteria derived from <xref ref-type="table" rid="T7">Table 7</xref> (i.e., <italic>ABtesting</italic> &#x0003D; 1), resulting in a new set of criteria ({<italic>ABtesting</italic> &#x0003D; 1, <italic>statistics</italic> &#x0003D; 1, <italic>license</italic> &#x0003D; 0, <italic>multiplechoice</italic> &#x0003D; 0}). There does not exist an item in {<italic>i</italic><sub>1</sub>..<italic>i</italic><sub>5</sub>} which completely fulfills these criteria. A related tradeoff is to choose an item as a new reference item which is mostly similar to the current selection criteria&#x02014;in our case, this is item <italic>i</italic><sub>3</sub> which only requires the adaptation of <italic>license</italic> &#x0003D; 0 to <italic>license</italic> &#x0003D; 100. The user again specifies a critique (<italic>includemc</italic>) which results in a new set of criteria ({<italic>ABtesting</italic> &#x0003D; 1, <italic>statistics</italic> &#x0003D; 1, <italic>license</italic> &#x0003D; 100, <italic>multiplechoice</italic> &#x0003D; 1}), leading to the new reference item <italic>i</italic><sub>5</sub> which is finally accepted by the user.</p>
<table-wrap position="float" id="T8">
<label>Table 8</label>
<caption><p>A simple example of a unit-critiquing session consisting of two critiquing cycles.</p></caption>
<table frame="box" rules="all">
<thead>
<tr style="background-color:#919497;color:#ffffff">
<th valign="top" align="left"><bold>Attribute</bold></th>
<th valign="top" align="center"><bold>Ref. item (</bold><italic>i</italic><sub>1</sub><bold>)</bold></th>
<th valign="top" align="center"><bold>Ref. item after cycle 1 (</bold><italic>i</italic><sub>3</sub><bold>)</bold></th>
<th valign="top" align="center"><bold>Ref. item after cycle 2 (</bold><italic>i</italic><sub>5</sub><bold>)</bold></th>
</tr>
</thead>
<tbody>
 <tr>
<td valign="top" align="left">ABtesting</td>
<td valign="top" align="center">0</td>
<td valign="top" align="center">1</td>
<td valign="top" align="center">1</td>
</tr> <tr>
<td valign="top" align="left">Statistics</td>
<td valign="top" align="center">1</td>
<td valign="top" align="center">1</td>
<td valign="top" align="center">1</td>
</tr> <tr>
<td valign="top" align="left">License</td>
<td valign="top" align="center">0</td>
<td valign="top" align="center">100</td>
<td valign="top" align="center">100</td>
</tr> <tr>
<td valign="top" align="left">Multiplechoice</td>
<td valign="top" align="center">0</td>
<td valign="top" align="center">0</td>
<td valign="top" align="center">1</td>
</tr> <tr>
<td valign="top" align="left"><italic>Unit critique</italic></td>
<td valign="top" align="left">(1) further statistics</td>
<td valign="top" align="left">(2) includemc</td>
<td valign="top" align="left">Accept</td>
</tr></tbody>
</table>
<table-wrap-foot>
<p>In critiquing cycle (1), the critique <italic>further statistics</italic> is specified on the reference item <italic>i</italic><sub>1</sub>, in cycle (2), <italic>includemc</italic> is specified as a critique. After cycle (2), the user is satisfied with (accepts) the recommended item (<italic>i</italic><sub>5</sub>).</p>
</table-wrap-foot>
</table-wrap>
<p>The idea of critiquing-based recommendation is to identify an item which is similar to the current item but (in addition) takes into account the criteria specified by the critique. In our example, we have assumed that the search for a new item returns an exact match (<italic>EIB</italic> metric), i.e., all search criteria are fulfilled. However, the search for new reference items is often designed more flexible, for example, other attribute-level similarity metrics can be applied to determine new reference items (Lorenzi and Ricci, <xref ref-type="bibr" rid="B80">2005</xref>).</p></sec>
<sec>
<title>3.2.7 Further critiquing approaches</title>
<p>For demonstration purposes, we have discussed the concepts of unit critiquing in more detail. However, critiquing-based recommender systems support various alternative types of critiques (Chen and Pu, <xref ref-type="bibr" rid="B15">2012</xref>; G&#x000FC;ell et al., <xref ref-type="bibr" rid="B62">2020</xref>). The idea of <italic>compound critiques</italic> (Smyth et al., <xref ref-type="bibr" rid="B105">2004</xref>; Zhang et al., <xref ref-type="bibr" rid="B126">2008</xref>) is to allow the definition of critiques which refer to more than one item property. A related example would be the compound critique <italic>furtherstat and includelicense</italic>, indicating the interest of a user in further statistics features also accepting (additional) license costs. A major advantage of compound critiquing is that due to the specification of multiple criteria in one critiquing cycle, significantly larger &#x0201C;jumps&#x0201D; in the itemspace are possible (Aggarwal, <xref ref-type="bibr" rid="B1">2016</xref>) and&#x02014;as a result&#x02014;less critiquing cycles are needed to find a solution. As an extension of compound critiques, <italic>dynamic critiques</italic> (Reilly et al., <xref ref-type="bibr" rid="B101">2004</xref>; McCarthy et al., <xref ref-type="bibr" rid="B86">2005</xref>) are based on the idea of mining frequent critiquing patterns which are then presented to a user.</p></sec>
<sec>
<title>3.2.8 Handling inconsistent search criteria</title>
<p>Critiquing-based recommender systems try to take into account the critiques defined by a user. Since user preferences (search criteria) typically change within the scope of a recommendation session, inconsistencies can occur (Atas et al., <xref ref-type="bibr" rid="B3">2021</xref>). For example, a user is first interested in a survey software configuration without license fee resulting in the reference item <italic>i</italic><sub>1</sub>. Then, the user wants to additionally include the <italic>ABtesting</italic> feature which then results in an inconsistency, since no item supports both, no license fee and <italic>ABtesting</italic> at the same time. From the logical point of view, such (inconsistent) search criteria are constraint sets <italic>CRIT</italic> &#x0003D; {<italic>crit</italic><sub>1</sub>..<italic>crit</italic><sub><italic>q</italic></sub>} and in the case of inconsistencies in <italic>CRIT</italic>, one option is to determine explanations (diagnoses) which indicate different options of resolving an inconsistency.<xref ref-type="fn" rid="fn0006"><sup>6</sup></xref> Alternatively, weighting schemes are applied in such contexts meaning that &#x0201C;elder&#x0201D; critiques have a higher probability of being deleted from a critiquing history. Another alternative is the retrieval of a new reference item which is as much as possible similar to the current set of search criteria (see our example in <xref ref-type="table" rid="T8">Table 8</xref>).</p></sec>
<sec>
<title>3.2.9 Examples of case-based recommender systems</title>
<p><xref ref-type="table" rid="T9">Table 9</xref> provides an overview of example case-based recommender applications. (Burke et al., <xref ref-type="bibr" rid="B13">1996</xref>) introduce the <sc>FindMe</sc> approach to support a unit critiquing-based navigation in complex information spaces&#x02014;discussed item domains are cars, videos, and apartments. The <sc>Entree</sc> system (Burke, <xref ref-type="bibr" rid="B10">2000</xref>) supports unit critiquing-based recommendations in the restaurant domain, and this system is also based on the <sc>FindMe</sc> approach introduced by (Burke et al., <xref ref-type="bibr" rid="B13">1996</xref>). <sc>DieToRecs</sc> (Fesenmaier et al., <xref ref-type="bibr" rid="B57">2003</xref>) is a case-based recommender system that supports a similarity-based approach to case retrieval, i.e., users have to specify their requirements and select a case of relevance which is then used as a basis for further search. <sc>Recomment</sc> (Grasch et al., <xref ref-type="bibr" rid="B61">2013</xref>) is a natural language-based user interface with an underlying unit-critiquing-based recommender system. (Musto et al., <xref ref-type="bibr" rid="B94">2015</xref>) introduce an asset allocation strategy framework which supports the recommendation of asset classes (e.g., Euro Bond, High Yield Bond, Euro Stocks, and Emerging Market Stocks) that fulfill the goals of the investor and are basically generated on the basis of an analysis of the portfolios of similar clients (investors). Lee and Kim (<xref ref-type="bibr" rid="B77">2015</xref>) introduce <sc>eHeaRSS</sc> which is a case-based recommender system in the healthcare domain which helps to identify, for example, relevant doctors, depending on the current (aggregated) health record and those of similar cases. In this context, an ontology helps to assure the correctness of recommendations, for example, in terms of the proposed medical diagnosis. Feely et al. (<xref ref-type="bibr" rid="B34">2020</xref>) introduce a case-based recommendation approach for the recommendation of marathon training plans and race pacings based on case information about the workouts and race histories of similar runners. <sc>CEBRA</sc> (Hernandez-Nieves et al., <xref ref-type="bibr" rid="B63">2021</xref>) supports the recommendation of banking products using a basic case-based reasoning recommender operating on a user&#x00027;s financial service profile and corresponding demographic data. Finally, the smart city initiative (Bokolo, <xref ref-type="bibr" rid="B6">2021</xref>) focuses on the case-based recommendation of smart city dimensions, i.e., by taking a look at similar cities, corresponding smart city-related activities for the current city are determined in order to achieve predefined sustainability goals, for example, on the basis of the best use of technological and human resources.</p>
<table-wrap position="float" id="T9">
<label>Table 9</label>
<caption><p>Overview of example case-based recommender applications.</p></caption>
<table frame="box" rules="all">
<thead>
<tr style="background-color:#919497;color:#ffffff">
<td valign="top" align="left"><bold>Recommender application</bold></td>
<td valign="top" align="left"><bold>Recommendation domain</bold></td>
<td valign="top" align="left"><bold>References</bold></td>
</tr> 
</thead>
<tbody>
<tr>
<td valign="top" align="left"><sc>RentMe</sc></td>
<td valign="top" align="left">Apartments</td>
<td valign="top" align="left">Burke et al., <xref ref-type="bibr" rid="B13">1996</xref></td>
</tr> <tr>
<td valign="top" align="left"><sc>Entree</sc></td>
<td valign="top" align="left">Restaurants</td>
<td valign="top" align="left">Burke, <xref ref-type="bibr" rid="B10">2000</xref></td>
</tr> <tr>
<td valign="top" align="left"><sc>DieToRecs</sc></td>
<td valign="top" align="left">Travel plans</td>
<td valign="top" align="left">Fesenmaier et al., <xref ref-type="bibr" rid="B57">2003</xref></td>
</tr> <tr>
<td valign="top" align="left"><sc>Recomment</sc></td>
<td valign="top" align="left">Digital cameras</td>
<td valign="top" align="left">Grasch et al., <xref ref-type="bibr" rid="B61">2013</xref></td>
</tr> <tr>
<td valign="top" align="left">Asset allocation framework</td>
<td valign="top" align="left">Financial services</td>
<td valign="top" align="left">Musto et al., <xref ref-type="bibr" rid="B94">2015</xref></td>
</tr> <tr>
<td valign="top" align="left"><sc>eHeaRSS</sc></td>
<td valign="top" align="left">Healthcare</td>
<td valign="top" align="left">Lee and Kim, <xref ref-type="bibr" rid="B77">2015</xref></td>
</tr> <tr>
<td valign="top" align="left">Recommender for Recreational Runners</td>
<td valign="top" align="left">Training plans</td>
<td valign="top" align="left">Feely et al., <xref ref-type="bibr" rid="B34">2020</xref></td>
</tr> <tr>
<td valign="top" align="left"><sc>CEBRA</sc></td>
<td valign="top" align="left">Financial services</td>
<td valign="top" align="left">Hernandez-Nieves et al., <xref ref-type="bibr" rid="B63">2021</xref></td>
</tr> <tr>
<td valign="top" align="left">Smart City Initiative</td>
<td valign="top" align="left">Smart cities</td>
<td valign="top" align="left">Bokolo, <xref ref-type="bibr" rid="B6">2021</xref></td>
</tr></tbody>
</table>
</table-wrap></sec></sec>
<sec>
<title>3.3 Constraint-based recommendation</title>
<p>The concept of constraint-based recommendation (Felfernig and Burke, <xref ref-type="bibr" rid="B38">2008</xref>) is based on the idea that recommendation knowledge is represented in terms of a set of variables and a corresponding set of constraints. As already mentioned, such constraints can be defined in an extensional fashion (by just enumerating the items part of the solution space) or in an intensional fashion where the recommendation space is represented in terms of a set of logical formulae. In this context, a constraint-based recommendation task (<sc>CB-REC Task</sc>) can be defined as follows (see Definition 1).<xref ref-type="fn" rid="fn0007"><sup>7</sup></xref></p>
<p><bold>Definition</bold> 1. A constraint-based recommendation task (<sc>CB-REC Task</sc>) can be defined as a constraint satisfaction problem (CSP) (<italic>V, C, R</italic>) where <italic>V</italic> &#x0003D; {<italic>v</italic><sub>1</sub>..<italic>v</italic><sub><italic>n</italic></sub>} is a set of finite domain variables with associated variable domain definitions <italic>dom</italic>(<italic>v</italic><sub><italic>i</italic></sub>), <italic>C</italic> &#x0003D; {<italic>c</italic><sub>1</sub>..<italic>c</italic><sub><italic>m</italic></sub>} is a set of constraints, and <italic>R</italic> &#x0003D; {<italic>r</italic><sub>1</sub>..<italic>r</italic><sub><italic>k</italic></sub>} is a set of user requirements.</p>
<p>Following Definition 1, an example recommendation task (<italic>V, C, R</italic>) based on the entries in <xref ref-type="table" rid="T5">Table 5</xref> is as follows: <italic>V</italic> &#x0003D; {<italic>ABtesting, statistics, multiplechoice, license</italic>}, <italic>dom</italic>(<italic>ABtesting</italic>) &#x0003D; <italic>dom</italic>(<italic>statistics</italic>) &#x0003D; <italic>dom</italic>(<italic>multiplechoice</italic>) &#x0003D; {0, 1}, <italic>dom</italic>(<italic>license</italic>) &#x0003D; {0, 100}, <italic>C</italic> &#x0003D; {<italic>c</italic><sub>1</sub>..<italic>c</italic><sub>5</sub>}, and <italic>R</italic> &#x0003D; {<italic>r</italic><sub>1</sub>: <italic>ABtesting</italic> &#x0003D; 1}, assuming that the user is interested in the <italic>ABtesting</italic> feature.</p>
<p>A constraint-based recommendation <sc>CB-REC</sc> for a given constraint-based recommendation task (<sc>CB-REC Task</sc>) can be defined as follows (see Definition 2).</p>
<p><bold>Definition 2</bold>. A constraint-based recommendation (<sc>CB-REC</sc>) for a defined <sc>CB-REC Task</sc> is a set of tuples <italic>REC</italic> &#x0003D; &#x022C3;<sub><italic>i</italic><sub>&#x003B1;</sub> &#x02208; <italic>I</italic></sub>{(<italic>rank</italic><sub><italic>i&#x003B1;</italic></sub>, <italic>i</italic><sub>&#x003B1;</sub>)} where <italic>rank</italic><sub><italic>i&#x003B1;</italic></sub> represents the recommendation rank assigned to item <italic>i</italic><sub>&#x003B1;</sub> &#x02208; <italic>I</italic> defined by a recommendation function <italic>rf</italic> and &#x02200;(<italic>rank</italic><sub><italic>i&#x003B1;</italic></sub>, <italic>i</italic><sub>&#x003B1;</sub>) &#x02208; <italic>REC</italic>: consistent(<italic>C</italic>&#x0222A;<italic>R</italic>&#x0222A;<italic>a</italic>(<italic>i</italic><sub>&#x003B1;</sub>)) where <italic>a</italic>(<italic>i</italic><sub>&#x003B1;</sub>) denotes the variable value assignments associated with item <italic>i</italic><sub>&#x003B1;</sub>.</p>
<p>Assuming <italic>R</italic> &#x0003D; {<italic>r</italic><sub>1</sub> : <italic>ABtesting</italic> &#x0003D; 1}, a <sc>CB-REC</sc> in our working example could be <italic>REC</italic> &#x0003D; {(1, <italic>i</italic><sub>5</sub>), (2, <italic>i</italic><sub>3</sub>)} where <italic>a</italic>(<italic>i</italic><sub>3</sub>) &#x0003D; {<italic>ABtesting</italic> &#x0003D; 1, <italic>statistics</italic> &#x0003D; 1, <italic>license</italic> &#x0003D; 100, <italic>multiplechoice</italic> &#x0003D; 0} and <italic>a</italic>(<italic>i</italic><sub>5</sub>) &#x0003D; {<italic>ABtesting</italic> &#x0003D; 1, <italic>statistics</italic> &#x0003D; 1, <italic>license</italic> &#x0003D; 100, <italic>multiplechoice</italic> &#x0003D; 1}.</p>
<sec>
<title>3.3.1 Ranking items</title>
<p>Up to now, we did not specify a function <italic>rf</italic> for the ranking of the items in <italic>REC</italic>. A simple ranking function could just count the number of supported features (see <xref ref-type="disp-formula" rid="E1">Equation 1</xref>), which would result in the mentioned recommendation ranking of <italic>REC</italic> &#x0003D; {(1, <italic>i</italic><sub>5</sub>), (2, <italic>i</italic><sub>3</sub>)} since the number of supported features of <italic>i</italic><sub>5</sub> is 3 [<italic>support</italic>(<italic>i</italic><sub>5</sub>) &#x0003D; 3] whereas <italic>support</italic>(<italic>i</italic><sub>3</sub>) &#x0003D; 2. In other words, item <italic>i</italic><sub>3</sub> is outperformed by one item resulting in a ranking of 2.<xref ref-type="fn" rid="fn0008"><sup>8</sup></xref></p>
<disp-formula id="E1"><label>(1)</label><mml:math id="M1"><mml:mtable class="eqnarray" columnalign="left"><mml:mtr><mml:mtd><mml:mi>r</mml:mi><mml:mi>f</mml:mi><mml:mrow><mml:mo stretchy="false">(</mml:mo><mml:mrow><mml:msub><mml:mrow><mml:mi>i</mml:mi></mml:mrow><mml:mrow><mml:mi>&#x003B1;</mml:mi></mml:mrow></mml:msub></mml:mrow><mml:mo stretchy="false">)</mml:mo></mml:mrow><mml:mo>=</mml:mo><mml:mn>1</mml:mn><mml:mo>&#x0002B;</mml:mo><mml:mo>|</mml:mo><mml:mrow><mml:mo>{</mml:mo><mml:mrow><mml:msub><mml:mrow><mml:mi>i</mml:mi></mml:mrow><mml:mrow><mml:mi>k</mml:mi></mml:mrow></mml:msub><mml:mo>&#x02208;</mml:mo><mml:mi>R</mml:mi><mml:mi>E</mml:mi><mml:mi>C</mml:mi><mml:mrow><mml:mo stretchy="false">(</mml:mo><mml:mrow><mml:mi>k</mml:mi><mml:mo>&#x02260;</mml:mo><mml:mi>&#x003B1;</mml:mi></mml:mrow><mml:mo stretchy="false">)</mml:mo></mml:mrow><mml:mo>:</mml:mo><mml:mi>s</mml:mi><mml:mi>u</mml:mi><mml:mi>p</mml:mi><mml:mi>p</mml:mi><mml:mi>o</mml:mi><mml:mi>r</mml:mi><mml:mi>t</mml:mi><mml:mrow><mml:mo stretchy="false">(</mml:mo><mml:mrow><mml:msub><mml:mrow><mml:mi>i</mml:mi></mml:mrow><mml:mrow><mml:mi>k</mml:mi></mml:mrow></mml:msub></mml:mrow><mml:mo stretchy="false">)</mml:mo></mml:mrow><mml:mo>&#x0003E;</mml:mo><mml:mi>s</mml:mi><mml:mi>u</mml:mi><mml:mi>p</mml:mi><mml:mi>p</mml:mi><mml:mi>o</mml:mi><mml:mi>r</mml:mi><mml:mi>t</mml:mi><mml:mrow><mml:mo stretchy="false">(</mml:mo><mml:mrow><mml:msub><mml:mrow><mml:mi>i</mml:mi></mml:mrow><mml:mrow><mml:mi>&#x003B1;</mml:mi></mml:mrow></mml:msub></mml:mrow><mml:mo stretchy="false">)</mml:mo></mml:mrow></mml:mrow><mml:mo>}</mml:mo></mml:mrow><mml:mo>|</mml:mo></mml:mtd></mml:mtr></mml:mtable></mml:math></disp-formula>
<p>An alternative to our simplified ranking function (<xref ref-type="disp-formula" rid="E1">Equation 1</xref>) is to introduce a utility function which evaluates utility of individual items on the basis of a pre-defined set of interest dimensions (Felfernig et al., <xref ref-type="bibr" rid="B40">2006</xref>, <xref ref-type="bibr" rid="B53">2018a</xref>). In our software service recommendation scenario, examples of relevant interest dimensions are <italic>economy</italic> and <italic>quality</italic> (see also <xref ref-type="table" rid="T10">Table 10</xref>).</p>
<table-wrap position="float" id="T10">
<label>Table 10</label>
<caption><p>A simple utility-based evaluation scheme for recommendation candidates, for example, paying no license fee, i.e., <italic>license</italic> &#x0003D; 0, contributes to the evaluation dimension economy.</p></caption>
<table frame="box" rules="all">
<thead>
<tr style="background-color:#919497;color:#ffffff">
<th valign="top" align="left"><bold>Interest dimension</bold></th>
<th valign="top" align="center" colspan="2"><bold>ABtesting</bold></th>
<th valign="top" align="center" colspan="2"><bold>Statistics</bold></th>
<th valign="top" align="center" colspan="2"><bold>License</bold></th>
<th valign="top" align="left" colspan="2"><bold>Multiplechoice</bold></th>
</tr>
</thead>
<tbody>
<tr style="background-color:#919497;color:#ffffff">
<td/>
<td valign="top" align="left"><bold>0</bold></td>
<td valign="top" align="left"><bold>1</bold></td>
<td valign="top" align="left"><bold>0</bold></td>
<td valign="top" align="left"><bold>1</bold></td>
<td valign="top" align="left"><bold>0</bold></td>
<td valign="top" align="left"><bold>100</bold></td>
<td valign="top" align="left"><bold>0</bold></td>
<td valign="top" align="left"><bold>1</bold></td>
</tr> <tr>
<td valign="top" align="left">Economy</td>
<td valign="top" align="center">0</td>
<td valign="top" align="center">0</td>
<td valign="top" align="center">0</td>
<td valign="top" align="center">0</td>
<td valign="top" align="center">10</td>
<td valign="top" align="center">0</td>
<td valign="top" align="center">0</td>
<td valign="top" align="center">0</td>
</tr> <tr>
<td valign="top" align="left">Quality</td>
<td valign="top" align="center">0</td>
<td valign="top" align="center">10</td>
<td valign="top" align="center">0</td>
<td valign="top" align="center">10</td>
<td valign="top" align="center">0</td>
<td valign="top" align="center">0</td>
<td valign="top" align="center">0</td>
<td valign="top" align="center">10</td>
</tr></tbody>
</table>
</table-wrap>
<p>Such utility-based evaluation schemes can then be used by a utility function to determine the overall utility of individual items&#x02014;see, for example, <xref ref-type="disp-formula" rid="E2">Equation (2)</xref>&#x02014; where <italic>D</italic> represents a set of interest dimensions [in our case, <italic>D</italic> &#x0003D; {<italic>economy, quality</italic>}] and <italic>eval</italic>(<italic>i</italic><sub>&#x003B1;</sub>, <italic>d</italic>) represents the evaluation scheme as presented in <xref ref-type="table" rid="T10">Table 10</xref>. Assuming equal importance of the two example interest dimensions [e.g., <italic>importance</italic>(<italic>economy</italic>) &#x0003D; 0.5 and <italic>importance</italic>(<italic>quality</italic>) &#x0003D; 0.5], <italic>utility</italic>(<italic>i</italic><sub>3</sub>) &#x0003D; 0.0 &#x0002B; 10.0 &#x0003D; 10.0 and <italic>utility</italic>(<italic>i</italic><sub>5</sub>) &#x0003D; 0.0 &#x0002B; 15 &#x0003D; 15.0, i.e., item <italic>i</italic><sub>5</sub> has a higher utility compared with item <italic>i</italic><sub>3</sub>. Depending on the user-specific importance of individual interest dimensions, the resulting utility values can differ.</p>
<disp-formula id="E2"><label>(2)</label><mml:math id="M2"><mml:mtable class="eqnarray" columnalign="left"><mml:mtr><mml:mtd><mml:mi>u</mml:mi><mml:mi>t</mml:mi><mml:mi>i</mml:mi><mml:mi>l</mml:mi><mml:mi>i</mml:mi><mml:mi>t</mml:mi><mml:mi>y</mml:mi><mml:mrow><mml:mo stretchy="false">(</mml:mo><mml:mrow><mml:msub><mml:mrow><mml:mi>i</mml:mi></mml:mrow><mml:mrow><mml:mi>&#x003B1;</mml:mi></mml:mrow></mml:msub></mml:mrow><mml:mo stretchy="false">)</mml:mo></mml:mrow><mml:mo>=</mml:mo><mml:msub><mml:mrow><mml:mi>&#x003A3;</mml:mi></mml:mrow><mml:mrow><mml:mi>d</mml:mi><mml:mo>&#x02208;</mml:mo><mml:mi>D</mml:mi></mml:mrow></mml:msub><mml:mi>e</mml:mi><mml:mi>v</mml:mi><mml:mi>a</mml:mi><mml:mi>l</mml:mi><mml:mrow><mml:mo stretchy="false">(</mml:mo><mml:mrow><mml:msub><mml:mrow><mml:mi>i</mml:mi></mml:mrow><mml:mrow><mml:mi>&#x003B1;</mml:mi></mml:mrow></mml:msub><mml:mo>,</mml:mo><mml:mi>d</mml:mi></mml:mrow><mml:mo stretchy="false">)</mml:mo></mml:mrow><mml:mo>&#x000D7;</mml:mo><mml:mi>i</mml:mi><mml:mi>m</mml:mi><mml:mi>p</mml:mi><mml:mi>o</mml:mi><mml:mi>r</mml:mi><mml:mi>t</mml:mi><mml:mi>a</mml:mi><mml:mi>n</mml:mi><mml:mi>c</mml:mi><mml:mi>e</mml:mi><mml:mrow><mml:mo stretchy="false">(</mml:mo><mml:mrow><mml:mi>d</mml:mi></mml:mrow><mml:mo stretchy="false">)</mml:mo></mml:mrow></mml:mtd></mml:mtr></mml:mtable></mml:math></disp-formula></sec>
<sec>
<title>3.3.2 Dealing with inconsistent requirements</title>
<p>In constraint-based recommendation, it can be the case that individual user requirements do not allow the determination of a recommendation.<xref ref-type="fn" rid="fn0009"><sup>9</sup></xref> For example, if a user is interested in the <italic>ABtesting</italic> and <italic>multiplechoice</italic> features but does not want to pay a license, i.e., <italic>R</italic> &#x0003D; {<italic>ABtesting</italic> &#x0003D; 1, <italic>multiplechoice</italic> &#x0003D; 1, <italic>license</italic> &#x0003D; 0}, no solution/item can support this set of requirements. In this example, we are able to identify two different conflicts (Junker, <xref ref-type="bibr" rid="B68">2004</xref>) (see Definition 3), which are minimal sets of requirements that induce an inconsistency.</p>
<p><bold>Definition 3</bold>. A conflict (set) <italic>CS</italic>&#x02286;<italic>R</italic> is a set of constraints with inconsistent(<italic>CS</italic> &#x0222A; <italic>C</italic>), i.e., no solution can be found for <italic>CS</italic> &#x0222A; <italic>C</italic>. A conflict set <italic>CS</italic> is minimal if &#x000AC;&#x02203;<italic>CS</italic>&#x02032;:<italic>CS</italic>&#x02032; &#x02282; <italic>CS</italic> (subset minimality).</p>
<p>Conflict set minimality is important due to the fact that just one requirement needs to be deleted (i.e., relaxed) from <italic>CS</italic> in order to resolve the conflict. In our example, there exist two minimal conflict sets which are <italic>CS</italic><sub>1</sub>:{<italic>ABtesting</italic> &#x0003D; 1, <italic>license</italic> &#x0003D; 0} and <italic>CS</italic><sub>2</sub>:{<italic>multiplechoice</italic> &#x0003D; 1, <italic>license</italic> &#x0003D; 0}. To resolve the conflict <italic>CS</italic><sub>1</sub>, a user can choose between the two options of excluding <italic>ABtesting</italic> (<italic>ABtesting</italic> &#x0003D; 0) or paying a <italic>license</italic> (<italic>license</italic> &#x0003D; 100). The same approach can be followed to resolve <italic>CS</italic><sub>2</sub>, i.e., to either accept <italic>multiplechoice</italic> &#x0003D; 0 or accept <italic>license</italic> &#x0003D; 100.</p>
<p>Such conflict sets can be used in interactive recommendation settings to support users in figuring out ways from the <italic>no solution could be found</italic> dilemma. A set &#x00394; of requirements is denoted as diagnosis (Reiter, <xref ref-type="bibr" rid="B102">1987</xref>; Felfernig et al., <xref ref-type="bibr" rid="B42">2009b</xref>, <xref ref-type="bibr" rid="B52">2012</xref>) if it helps to resolve all identified conflicts (see Definition 4).</p>
<p><bold>Definition 4</bold>. A diagnosis &#x00394; &#x02286; <italic>R</italic> is a set of constraints with consistent(<italic>R</italic> &#x02212; &#x00394; &#x0222A; <italic>C</italic>), i.e., at least one solution can be found for <italic>R</italic> &#x02212; &#x00394; &#x0222A; <italic>C</italic>. A diagnosis &#x00394; is minimal if &#x000AC; &#x02203; &#x00394; &#x02032;:&#x00394;&#x02032; &#x02282; &#x00394; (subset minimality).</p>
<p>Both concepts, i.e., <italic>conflict sets</italic> and corresponding <italic>diagnoses</italic> can be used to support users in inconsistent situations. Conflict sets are helpful in the context of <italic>repeated conflict resolution</italic> (for example, when purchasing a new car for the family, the preferences of individual family members change over time), and diagnoses can be used when users are interested in <italic>quick repairs</italic> (for example, when parametrizing an operating system, some inconsistent parameter settings need to be adapted).</p></sec>
<sec>
<title>3.3.3 Examples of constraint-based recommender systems</title>
<p><xref ref-type="table" rid="T11">Table 11</xref> provides an overview of example constraint-based recommender applications. <sc>FSAdvisor</sc> (Felfernig and Kiener, <xref ref-type="bibr" rid="B45">2005</xref>) is a financial service recommender system that proposes new financial services depending on the current financial status and requirements of the customer. In the line of <sc>FSAdvisor</sc>, <sc>VITA</sc> (Felfernig et al., <xref ref-type="bibr" rid="B44">2007</xref>) is a financial service recommender system supporting sales representatives in the preparation and conduction of customer dialogs. Both systems are based on a database query-based approach implemented in <sc>AdvisorSuite</sc>, which is a development environment for constraint-based recommender applications (Felfernig et al., <xref ref-type="bibr" rid="B40">2006</xref>; Jannach and Kreutler, <xref ref-type="bibr" rid="B66">2007</xref>). In addition, <sc>Mortimer</sc> is a constraint-based recommender application developed on the basis of <sc>AdvisorSuite</sc> which focuses on the constraint-based recommendation of cigars. <sc>Authentic</sc> (Murphy et al., <xref ref-type="bibr" rid="B92">2015</xref>) is a constraint satisfaction-based recommendation environment for supporting the achievement of energy saving goals on the basis of adapted schedules for activating household appliances. Recommendations of behavior change (e.g., postponed activation of a dishwasher to exploit more self-produced energy) are determined on the basis of energy consumption-related sensor data. Wobcke et al. (<xref ref-type="bibr" rid="B121">2015</xref>) introduce a P2P recommendation environment in the context of online dating scenarios where constraints (rules) are used to define baseline recommendation strategies. <sc>RecTurk</sc> (Ulz et al., <xref ref-type="bibr" rid="B114">2017</xref>) is a framework for the development of constraint-based recommender applications. The underyling idea is to apply the concepts of <italic>human computation</italic> (Law and von Ahn, <xref ref-type="bibr" rid="B73">2011</xref>) to alleviate the definition and maintenance of recommendation rules. Almalis et al. (<xref ref-type="bibr" rid="B2">2018</xref>) introduce a constraint-based job recommender system where constraints are used to assure defined compatibilities between job seekers and job announcements. Finally, Esheiba et al. (<xref ref-type="bibr" rid="B30">2021</xref>) present a constraint-based recommender system supporting the filtering-out of irrelevant product services and the ranking of the remaining relevant ones.</p>
<table-wrap position="float" id="T11">
<label>Table 11</label>
<caption><p>Overview of example constraint-based recommender applications.</p></caption>
<table frame="box" rules="all">
<thead>
<tr style="background-color:#919497;color:#ffffff">
<th valign="top" align="left"><bold>Recommender application</bold></th>
<th valign="top" align="left"><bold>Recommendation domain</bold></th>
<th valign="top" align="left"><bold>References</bold></th>
</tr>
</thead>
<tbody>
 <tr>
<td valign="top" align="left"><sc>FSAdvisor</sc></td>
<td valign="top" align="left">Financial services</td>
<td valign="top" align="left">Felfernig and Kiener, <xref ref-type="bibr" rid="B45">2005</xref></td>
</tr> <tr>
<td valign="top" align="left"><sc>Advisor Suite</sc></td>
<td valign="top" align="left">Digital cameras</td>
<td valign="top" align="left">Felfernig et al., <xref ref-type="bibr" rid="B40">2006</xref></td>
</tr> <tr>
<td valign="top" align="left"><sc>Mortimer</sc></td>
<td valign="top" align="left">Cigars</td>
<td valign="top" align="left">Zanker et al., <xref ref-type="bibr" rid="B125">2006</xref></td>
</tr> <tr>
<td valign="top" align="left"><sc>VITA</sc></td>
<td valign="top" align="left">Financial services</td>
<td valign="top" align="left">Felfernig et al., <xref ref-type="bibr" rid="B44">2007</xref></td>
</tr> <tr>
<td valign="top" align="left"><sc>Authentic</sc></td>
<td valign="top" align="left">Energy saving</td>
<td valign="top" align="left">Murphy et al., <xref ref-type="bibr" rid="B92">2015</xref></td>
</tr> <tr>
<td valign="top" align="left"><sc>P2P</sc> framework</td>
<td valign="top" align="left">Online dating</td>
<td valign="top" align="left">Wobcke et al., <xref ref-type="bibr" rid="B121">2015</xref></td>
</tr> <tr>
<td valign="top" align="left"><sc>RecTurk</sc> framework</td>
<td valign="top" align="left">Digital cameras</td>
<td valign="top" align="left">Ulz et al., <xref ref-type="bibr" rid="B114">2017</xref></td>
</tr> <tr>
<td valign="top" align="left"><sc>FoDRA</sc> framework</td>
<td valign="top" align="left">Jobs</td>
<td valign="top" align="left">Almalis et al., <xref ref-type="bibr" rid="B2">2018</xref></td>
</tr> <tr>
<td valign="top" align="left"><sc>PSS recommender</sc></td>
<td valign="top" align="left">Product services</td>
<td valign="top" align="left">Esheiba et al., <xref ref-type="bibr" rid="B30">2021</xref></td>
</tr></tbody>
</table>
</table-wrap>
</sec></sec></sec>
<sec id="s4">
<title>4 Recent advances in knowledge-based recommendation</title>
<p>In this section, we provide an overview of the recent advances in knowledge-based recommendation (compared with the basic approaches presented in Section 3). We discuss the following aspects: (1) Users are often in the situation of not knowing every detail about a product and&#x02014;as a consequence&#x02014;are not able to make a related informed decision. For example, if someone is interested in digital cameras, he/she might be able to specify preferences regarding attributes such as <italic>resolution, maximum price, weight</italic>, and <italic>primary application</italic> (e.g., landscape photography or sports) but at the same time might not be able to specify preferences regarding attributes such as <italic>maximum frames per second</italic> or <italic>maximum exposure time</italic>. In our example, users might not be aware of the usefulness of the <italic>ABtesting</italic> feature. Related techniques to support users in such contexts are presented in Section 4.1. (2) Given a set of user preferences, situations can occur where no solution can be identified (see also Section 3)&#x02014;in Section 4.2, we introduce concepts for personalized conflict resolution. (3) In some situations, users have adaptation (reconfiguration) requirements regarding already purchased items. For example, after having purchased an online survey software license, a user detected the relevance of the <italic>ABtesting</italic> feature and is interested in a feature extension. Related technical solutions are presented in Section 4.3. (4) Knowledge-based recommendation is not only relevant in recommendation scenarios focusing on single users but also in scenarios where recommendations have to be determined for groups, for example, planning round-trips for tourist groups or deciding about the features to be included in a software or service. Aspects of knowledge-based group recommender systems are presented in Section 4.4. (5) In Section 4.5, we discuss further approaches focusing on the topics of hybrid recommendation, search optimization, explanations, recommendation knowledge acquisition, conversational recommendation, and explanations.</p>
<sec>
<title>4.1 Recommending preference settings</title>
<p>There are situations where users need help in specifying preferences regarding specific item properties. <xref ref-type="table" rid="T12">Table 12</xref> depicts a simplified example of an attribute value proposal in the context of a <italic>case-based recommendation</italic> scenario: the <italic>current</italic> user has already specified his/her preferences regarding the attributes <italic>multiplechoice</italic> and <italic>statistics</italic>. Using a nearest neighbor (NN)-based approach, i.e., determining the session with the most similar preferences, results in session <italic>s</italic><sub>3</sub>. Consequently, we can recommend the attribute values <italic>ABtesting</italic> &#x0003D; 1 and <italic>license</italic> &#x0003D; 100 to the <italic>current</italic> user. The same approach to attribute value recommendation can also be applied (1) in the context of customer segmentation (recommendation) where customers have to be identified who will be interested in a new item feature (Felfernig et al., <xref ref-type="bibr" rid="B47">2021</xref>) and (2) to figure out features (attributes), a customer is interested in specifying&#x02014;this is relevant in scenarios where users are not interested in specifying all attributes (Mirzadeh et al., <xref ref-type="bibr" rid="B90">2005</xref>; Dragone et al., <xref ref-type="bibr" rid="B25">2018</xref>).</p>
<table-wrap position="float" id="T12">
<label>Table 12</label>
<caption><p>Example user sessions <italic>s</italic><sub><italic>i</italic></sub> representing &#x0201C;successfully&#x0201D; completed recommendation sessions (e.g., a user has selected a specific item).</p></caption>
<table frame="box" rules="all">
<thead>
<tr style="background-color:#919497;color:#ffffff">
<th valign="top" align="left"><bold>Session</bold></th>
<th valign="top" align="center"><bold>ABtesting</bold></th>
<th valign="top" align="center"><bold>Statistics</bold></th>
<th valign="top" align="center"><bold>Multiplechoice</bold></th>
<th valign="top" align="center"><bold>License</bold></th>
</tr> 
</thead>
<tbody>
<tr>
<td valign="top" align="left"><italic>s</italic><sub>1</sub></td>
<td valign="top" align="center">1</td>
<td valign="top" align="center">1</td>
<td valign="top" align="center">0</td>
<td valign="top" align="center">100</td>
</tr> <tr>
<td valign="top" align="left"><italic>s</italic><sub>2</sub></td>
<td valign="top" align="center">0</td>
<td valign="top" align="center">1</td>
<td valign="top" align="center">0</td>
<td valign="top" align="center">0</td>
</tr> <tr>
<td valign="top" align="left"><italic>s</italic><sub>3</sub> (NN)</td>
<td valign="top" align="center">1</td>
<td valign="top" align="center">1</td>
<td valign="top" align="center">1</td>
<td valign="top" align="center">100</td>
</tr> <tr>
<td valign="top" align="left"><italic>Current</italic></td>
<td valign="top" align="left">?</td>
<td valign="top" align="center">1</td>
<td valign="top" align="center">1</td>
<td valign="top" align="left">?</td>
</tr></tbody>
</table>
<table-wrap-foot>
<p>In this example, user (session) <italic>s</italic><sub>3</sub> can be regarded as the nearest neighbor (NN) of the <italic>current</italic> user, i.e., both, <italic>ABtesting</italic> and <italic>license</italic> are recommended to be included.</p>
</table-wrap-foot>
</table-wrap>
<p>An alternative to NN-based recommendation is to apply model-based approaches such as matrix factorization or neural networks&#x02014;for related details see Erdeniz et al. (<xref ref-type="bibr" rid="B29">2019</xref>, <xref ref-type="bibr" rid="B28">2022</xref>) and Uta et al. (<xref ref-type="bibr" rid="B115">2022</xref>).</p>
<p>Beyond case-based recommendation, such approaches to attribute value recommendation are also applied in <italic>constraint-based recommendation</italic> (and beyond) (Felfernig and Burke, <xref ref-type="bibr" rid="B38">2008</xref>; Falkner et al., <xref ref-type="bibr" rid="B31">2011</xref>; Fargier et al., <xref ref-type="bibr" rid="B33">2016</xref>; Pereira et al., <xref ref-type="bibr" rid="B96">2016</xref>; Temple et al., <xref ref-type="bibr" rid="B108">2017</xref>). A major issue in such contexts is the fact that a recommendation of one or more attribute settings could be <italic>inconsistent</italic> with the underlying set of constraints (C). One way to assure consistency is to pre-determine a set of nearest neighbors and to show recommendations to users after having tested recommendation consistency (C&#x000F6;ster et al., <xref ref-type="bibr" rid="B20">2002</xref>; Felfernig and Burke, <xref ref-type="bibr" rid="B38">2008</xref>; Falkner et al., <xref ref-type="bibr" rid="B31">2011</xref>; Pereira et al., <xref ref-type="bibr" rid="B96">2016</xref>).</p>
<p>An alternative is to learn <italic>solver search heuristics</italic> in such a way that constraint solvers are enabled to predict user-relevant attribute value settings (Uta et al., <xref ref-type="bibr" rid="B115">2022</xref>), i.e., to directly integrate recommendation knowledge into constraint solver search, for example, by applying neural networks that receive as input a set of user preferences and propose corresponding solver search heuristics [in terms of variable (value) orderings] as output. In the example shown in <xref ref-type="table" rid="T12">Table 12</xref>, variable value orderings for the not yet instantiated variables <italic>ABtesting</italic> and <italic>license</italic> would be <italic>ABtesting</italic> [1,0] and <italic>license</italic> [100,0], indicating that the solver should first try to instantiate these variables with 1 (100) before trying other instantiations. For an overview on the integration of machine learning and constraint solving, we refer to Popescu et al. (<xref ref-type="bibr" rid="B98">2022</xref>).</p>
<p>In <italic>critiquing-based recommendation</italic>, such attribute value recommendations could be also used in the initial preference specification phase. However, critiquing-based recommendation follows the idea of critiquing a shown reference item. Specifically, in critiquing scenarios, attribute value recommendation is &#x0201C;replaced&#x0201D; by the recommendation of critiques (McCarthy et al., <xref ref-type="bibr" rid="B87">2010</xref>; Mandl and Felfernig, <xref ref-type="bibr" rid="B83">2012</xref>; Murti et al., <xref ref-type="bibr" rid="B93">2016</xref>; Xie et al., <xref ref-type="bibr" rid="B124">2018</xref>)&#x02014;see the simplified unit critique recommendation example depicted in <xref ref-type="table" rid="T13">Table 13</xref>. In this simplified example,<xref ref-type="fn" rid="fn0010"><sup>10</sup></xref> the critiquing session most similar to the critiquing session of the <italic>current</italic> user (session) is <italic>cs</italic><sub>2</sub>. This can be determined, for example, by determining the intersection of the critiquing sets of <italic>cs</italic><sub><italic>i</italic></sub> and <italic>current</italic> where |<italic>critiques</italic>(<italic>cs</italic><sub>1</sub>) &#x02229; <italic>critiques</italic>(<italic>current</italic>)| &#x0003D; 1 and |<italic>critiques</italic>(<italic>cs</italic><sub>2</sub>) &#x02229; <italic>critiques</italic>(<italic>current</italic>)| &#x0003D; 2. Using a nearest neighbor-based approach, critiques and item selection of <italic>cs</italic><sub>2</sub> can be used to recommend future critiques to the <italic>current user</italic> but also to predict items that will be chosen by the current user (Mandl and Felfernig, <xref ref-type="bibr" rid="B83">2012</xref>).</p>
<table-wrap position="float" id="T13">
<label>Table 13</label>
<caption><p>Example critiquing sessions <italic>cs</italic><sub><italic>i</italic></sub> representing &#x0201C;successfully&#x0201D; completed recommendation sessions.</p></caption>
<table frame="box" rules="all">
<thead>
<tr style="background-color:#919497;color:#ffffff">
<th valign="top" align="left"><bold>Session</bold></th>
<th valign="top" align="center"><bold>Reference item</bold></th>
<th valign="top" align="center"><italic>crit</italic><sub>1</sub></th>
<th valign="top" align="center"><italic>crit</italic><sub>2</sub></th>
<th valign="top" align="center"><italic>crit</italic><sub>3</sub></th>
<th valign="top" align="center"><bold>Selection</bold></th>
</tr>
</thead>
<tbody>
 <tr>
<td valign="top" align="left"><italic>cs</italic><sub>1</sub></td>
<td valign="top" align="center"><italic>i</italic><sub>1</sub></td>
<td valign="top" align="center"><italic>i</italic><sub>1</sub>.<italic>furtherstat</italic></td>
<td valign="top" align="center"><italic>i</italic><sub>4</sub>.<italic>reducestat</italic></td>
<td valign="top" align="center">-</td>
<td valign="top" align="center"><italic>i</italic><sub>1</sub></td>
</tr> <tr>
<td valign="top" align="left"><italic>cs</italic><sub>2</sub> (NN)</td>
<td valign="top" align="center"><italic>i</italic><sub>1</sub></td>
<td valign="top" align="center"><italic>i</italic><sub>1</sub>.<italic>includemc</italic></td>
<td valign="top" align="center"><italic>i</italic><sub>4</sub>.<italic>furtherstat</italic></td>
<td valign="top" align="center"><italic>i</italic><sub>5</sub>.<italic>excludemc</italic></td>
<td valign="top" align="center"><italic>i</italic><sub>3</sub></td>
</tr> <tr>
<td valign="top" align="left"><italic>Current</italic></td>
<td valign="top" align="center"><italic>i</italic><sub>1</sub></td>
<td valign="top" align="center"><italic>i</italic><sub>1</sub>.<italic>includemc</italic></td>
<td valign="top" align="center"><italic>i</italic><sub>7</sub>.<italic>furtherstat</italic></td>
<td valign="top" align="center">?</td>
<td valign="top" align="center">?</td>
</tr></tbody>
</table>
<table-wrap-foot>
<p>In this example, session <italic>cs</italic><sub>2</sub> can be regarded as the nearest neighbor (NN) of the current user. The reference item <italic>i</italic><sub>1</sub> is presented in <xref ref-type="table" rid="T4">Table 4</xref>.</p>
</table-wrap-foot>
</table-wrap></sec>
<sec>
<title>4.2 Dealing with &#x0201C;no solution could be found&#x0201D; situations</title>
<p>As discussed in Section 3, users of knowledge-based recommenders in some situations need support to get out of the <italic>no solution could be found dilemma</italic>. Approaches that can proactively support users in such contexts are conflict detection (Junker, <xref ref-type="bibr" rid="B68">2004</xref>) and model-based diagnosis (Reiter, <xref ref-type="bibr" rid="B102">1987</xref>; Felfernig et al., <xref ref-type="bibr" rid="B52">2012</xref>; Walter et al., <xref ref-type="bibr" rid="B117">2017</xref>). Such algorithms help users to understand trade-offs in the current situation and propose different options to resolve inconsistencies. Having user preference weights available, for example, in terms of explicitly defined preference weights, algorithms can be applied in different ways to determine preferred (personalized) diagnoses. For demonstration purposes, we assume the following preference ordering (see <xref ref-type="table" rid="T14">Table 14</xref>) for our example conflict sets <italic>CS</italic>1: {<italic>ABtesting</italic> &#x0003D; 1, <italic>license</italic> &#x0003D; 0} and <italic>CS</italic>2: {<italic>multiplechoice</italic> &#x0003D; 1, <italic>license</italic> &#x0003D; 0} derived from the user requirements <italic>R</italic> &#x0003D; {<italic>ABtesting</italic> &#x0003D; 1, <italic>multiplechoice</italic> &#x0003D; 1, <italic>license</italic> &#x0003D; 0}.</p>
<table-wrap position="float" id="T14">
<label>Table 14</label>
<caption><p>Example preference orderings for requirements (the lower the more important the preference).</p></caption>
<table frame="box" rules="all">
<thead>
<tr style="background-color:#919497;color:#ffffff">
<th valign="top" align="left"><bold>Session</bold></th>
<th valign="top" align="center"><bold>ABtesting</bold></th>
<th valign="top" align="center"><bold>Statistics</bold></th>
<th valign="top" align="center"><bold>Multiplechoice</bold></th>
<th valign="top" align="center"><bold>License</bold></th>
<th valign="top" align="center"><bold>Diagnosis</bold> &#x00394;</th>
</tr> 
</thead>
<tbody>
<tr>
<td valign="top" align="left"><italic>s</italic><sub>1</sub></td>
<td valign="top" align="center">3</td>
<td valign="top" align="center">2</td>
<td valign="top" align="center">4</td>
<td valign="top" align="center">1</td>
<td valign="top" align="center">{<italic>ABtesting</italic> &#x0003D; 1, <italic>multiplechoice</italic> &#x0003D; 1}</td>
</tr> <tr>
<td valign="top" align="left"><italic>s</italic><sub>2</sub></td>
<td valign="top" align="center">2</td>
<td valign="top" align="center">3</td>
<td valign="top" align="center">1</td>
<td valign="top" align="center">4</td>
<td valign="top" align="center">{<italic>license</italic> &#x0003D; 0}</td>
</tr></tbody>
</table>
<table-wrap-foot>
<p>For example, in session <italic>s</italic><sub>1</sub>, keeping the selected <italic>license</italic> type as-is has the highest priority.</p>
</table-wrap-foot>
</table-wrap>
<p>Following a simple additive utility-based scheme (Felfernig et al., <xref ref-type="bibr" rid="B51">2013c</xref>) using the orderings depicted in <xref ref-type="table" rid="T14">Table 14</xref> (the lower the ordering position, the higher the importance of the related user requirement), the conflicts <italic>CS</italic><sub>1</sub> and <italic>CS</italic><sub>2</sub> would be resolved (in a personalized fashion) as follows: for the user in Session <italic>s</italic><sub>1</sub> (user 1), we would keep the exclusion of <italic>license</italic> as-is and exclude both, <italic>ABtesting</italic> and <italic>multiplechoice</italic> (1 &#x0003C; 3&#x0002B;4). Vice-versa, in the case of session <italic>s</italic><sub>2</sub> (user 2), we would keep the preferences regarding <italic>ABtesting</italic> and <italic>multiplechoice</italic> as-is and accept the inclusion of a license fee (1&#x0002B;2 &#x0003C; 4). In a similar fashion, such an approach can be applied in critiquing-based recommendation sessions where&#x02014;on the basis of importance information about individual critiques [user sentiments about individual attributes could be available or &#x0201C;older&#x0201D; critiques could be interpreted as less important (Chen et al., <xref ref-type="bibr" rid="B16">2017</xref>)]&#x02014;corresponding conflict resolutions could be proposed.</p></sec>
<sec>
<title>4.3 Recommendations for reconfiguration</title>
<p>In scenarios where users have already purchased an item and want to extend the item afterward, recommendations for reconfigurations are required, i.e., which attributes of the original solution need to be adapted such that the new user requirements can be taken into account (Felfernig et al., <xref ref-type="bibr" rid="B54">2018b</xref>; Weckesser et al., <xref ref-type="bibr" rid="B120">2018</xref>). For example, if a user has already ordered a specific survey software service consisting of the feature {<italic>statistics</italic> &#x0003D; 1} (item <italic>i</italic><sub>1</sub>) but then detects that he/she wants to include also the <italic>ABtesting</italic> feature, the question arises which of the initial attribute settings (user preferences) remain the same and which ones need to be adapted. In such scenarios, critiquing-based recommendation would not be the primary choice since reconfiguration is in the need of <italic>minimal changes</italic> to an already ordered item. In contrast, case-based reasoning can be applied by using cases (items) with an exact attribute-wise match to the already purchased item with a minimal number of needed adaptations.</p>
<p>If we assume the availability of a product table as shown in <xref ref-type="table" rid="T4">Table 4</xref> and a user who has purchased item <italic>i</italic><sub>1</sub> and now wants to extend this configuration with <italic>ABtesting</italic>, this results in the search criteria {<italic>ABtesting</italic> &#x0003D; 1, <italic>statistics</italic> &#x0003D; 1, <italic>multiplechoice</italic> &#x0003D; 0, <italic>license</italic> &#x0003D; 0}. The corresponding nearest neighbor configuration is item <italic>i</italic><sub>3</sub> [based on the <italic>equal is better</italic> (EIB) similarity metric]&#x02014;see <xref ref-type="table" rid="T15">Table 15</xref>. In addition to the inclusion of <italic>ABtesting</italic>, the selection of item <italic>i</italic><sub>3</sub> requires one additional adaptation which is <italic>license</italic> &#x0003D; 100. Beyond counting the number of adaptations, reconfiguration can also take into account sentiments (Chen et al., <xref ref-type="bibr" rid="B16">2017</xref>): if additional features could be included without further costs or efforts, this should be preferred over reconfigurations where those features are not included.</p>
<table-wrap position="float" id="T15">
<label>Table 15</label>
<caption><p>Simplified reconfiguration setting: a user has already purchased item <italic>i</italic><sub>1</sub> and&#x02014;after some time&#x02014;wants to extend this configuration by including <italic>ABtesting</italic>.</p></caption>
<table frame="box" rules="all">
<thead>
<tr style="background-color:#919497;color:#ffffff">
<th valign="top" align="left"><bold>Item</bold></th>
<th valign="top" align="center"><bold>ABtesting</bold></th>
<th valign="top" align="center"><bold>Statistics</bold></th>
<th valign="top" align="center"><bold>Multiplechoice</bold></th>
<th valign="top" align="center"><bold>License</bold></th>
</tr>
</thead>
<tbody>
 <tr>
<td valign="top" align="left"><italic>i</italic><sub>1</sub> (purchase)</td>
<td valign="top" align="center">0 (1)</td>
<td valign="top" align="center">1</td>
<td valign="top" align="center">0</td>
<td valign="top" align="center">0</td>
</tr> <tr>
<td valign="top" align="left"><italic>i</italic><sub>2</sub></td>
<td valign="top" align="center">0</td>
<td valign="top" align="center">0</td>
<td valign="top" align="center">1</td>
<td valign="top" align="center">100</td>
</tr> <tr>
<td valign="top" align="left"><italic>i</italic><sub>3</sub> (NN)</td>
<td valign="top" align="center">1</td>
<td valign="top" align="center">1</td>
<td valign="top" align="center">0</td>
<td valign="top" align="center">100</td>
</tr> <tr>
<td valign="top" align="left"><italic>i</italic><sub>4</sub></td>
<td valign="top" align="center">0</td>
<td valign="top" align="center">1</td>
<td valign="top" align="center">1</td>
<td valign="top" align="center">100</td>
</tr> <tr>
<td valign="top" align="left"><italic>i</italic><sub>5</sub></td>
<td valign="top" align="center">1</td>
<td valign="top" align="center">1</td>
<td valign="top" align="center">1</td>
<td valign="top" align="center">100</td>
</tr></tbody>
</table>
</table-wrap>
<p>In constraint-based recommendation, <italic>i</italic> &#x0003D; {<italic>a</italic><sub>1</sub>..<italic>a</italic><sub><italic>k</italic></sub>} can be regarded as a set of variable assignments (constraints) describing the original item <italic>i</italic> (in our example, <italic>i</italic><sub>1</sub>); furthermore, <italic>R</italic> &#x0003D; {<italic>r</italic><sub>1</sub>..<italic>r</italic><sub><italic>l</italic></sub>} is a set of reconfiguration requirements (in our example, <italic>R</italic> &#x0003D; {<italic>ABtesting</italic> &#x0003D; 1}). A diagnosis &#x00394;&#x02286;<italic>i</italic> is a set of variable assignments in <italic>i</italic> that need to be adapted such that a solution for the reconfiguration task can be identified (Felfernig et al., <xref ref-type="bibr" rid="B54">2018b</xref>). More formally, &#x00394;&#x02286;<italic>i</italic> represents a diagnosis if consistent (<italic>i</italic>&#x02212;&#x00394;&#x0222A;<italic>C</italic>&#x0222A;<italic>R</italic>), i.e., the corresponding domain-specific constraints <italic>C</italic> (see <xref ref-type="table" rid="T5">Table 5</xref>) need to be taken into account (Felfernig et al., <xref ref-type="bibr" rid="B54">2018b</xref>). If weights for user preferences are available (see, e.g., <xref ref-type="table" rid="T14">Table 14</xref>), reconfiguration can be personalized, i.e., for individual users having purchased the same original item, different reconfigurations could be proposed. Following the standard approach of conflict detection (Junker, <xref ref-type="bibr" rid="B68">2004</xref>) and diagnosis identification (Reiter, <xref ref-type="bibr" rid="B102">1987</xref>), a reconfiguration can be determined the same way as shown in the context of identifying minimal sets of inconsistent requirements. If a user has originally selected (purchased) item <italic>i</italic><sub>1</sub>, a corresponding reconfiguration requirement <italic>R</italic> &#x0003D; {<italic>ABtesting</italic> &#x0003D; 1} would induce the (singleton) conflicts <italic>CS</italic><sub>1</sub>: {<italic>ABtesting</italic> &#x0003D; 0} and <italic>CS</italic><sub>2</sub>: {<italic>license</italic> &#x0003D; 0}, resulting in a corresponding reconfiguration {<italic>ABtesting</italic> &#x0003D; 1, <italic>statistics</italic> &#x0003D; 1, <italic>multiplechoice</italic> &#x0003D; 0, <italic>license</italic> &#x0003D; 100} (Felfernig et al., <xref ref-type="bibr" rid="B54">2018b</xref>).</p></sec>
<sec>
<title>4.4 Knowledge-based recommendation for groups</title>
<p>Group recommender systems (Pessemier et al., <xref ref-type="bibr" rid="B97">2017</xref>; Felfernig et al., <xref ref-type="bibr" rid="B37">2024b</xref>) are typically built on the top of single user recommender systems following one of the approaches of (1) <italic>aggregated predictions</italic> or (2) <italic>aggregated models</italic>. With aggregated predictions, the items recommended to individual group members can be merged. In the context of aggregated models, the preferences of individual group members are merged, resulting in a group preference model which is then used to determine recommendations.</p>
<p>In <italic>case-based recommendation</italic> for groups, the determination of group recommendations can be based on two different approaches. With <italic>aggregated predictions</italic>, in a first step, relevant recommendations would be determined for each user (see <xref ref-type="table" rid="T16">Table 16</xref>). In the following, these individual recommendations (items) have to be aggregated, according to a specific aggregation strategy. For example, if we apply <italic>majority voting</italic>, the overall recommendation for the group would be item <italic>i</italic><sub>5</sub> since it has received more recommendations compared with other recommendation candidates.</p>
<table-wrap position="float" id="T16">
<label>Table 16</label>
<caption><p>Example of user-individual item recommendations as a basis for determining a group recommendation using the <italic>aggregated prediction</italic> approach (with majority voting, <italic>i</italic><sub>5</sub> gets recommended).</p></caption>
<table frame="box" rules="all">
<thead>
<tr style="background-color:#919497;color:#ffffff">
<th valign="top" align="left"><bold>User</bold></th>
<th valign="top" align="center"><bold>Item</bold></th>
</tr> 
</thead>
<tbody>
<tr>
<td valign="top" align="left"><italic>u</italic><sub>1</sub></td>
<td valign="top" align="center"><italic>i</italic><sub>5</sub></td>
</tr> <tr>
<td valign="top" align="left"><italic>u</italic><sub>2</sub></td>
<td valign="top" align="center"><italic>i</italic><sub>4</sub></td>
</tr> <tr>
<td valign="top" align="left"><italic>u</italic><sub>3</sub></td>
<td valign="top" align="center"><italic>i</italic><sub>1</sub></td>
</tr> <tr>
<td valign="top" align="left"><italic>u</italic><sub>4</sub></td>
<td valign="top" align="center"><italic>i</italic><sub>5</sub></td>
</tr></tbody>
</table>
</table-wrap>
<p>If the recommender system is based on <italic>aggregated models</italic> (see <xref ref-type="table" rid="T17">Table 17</xref>), user-individual preferences have to be aggregated into a group model which can then be used for determining recommendations. In the example of <xref ref-type="table" rid="T17">Table 17</xref>, the overall case-based group recommendation would be item <italic>i</italic><sub>3</sub> since this one exactly represents the preferences of the determined group model.</p>
<table-wrap position="float" id="T17">
<label>Table 17</label>
<caption><p>Example of a group recommendation based on the <italic>aggregated model</italic> approach resulting in the recommendation of item <italic>i</italic><sub>3</sub>.</p></caption>
<table frame="box" rules="all">
<thead>
<tr style="background-color:#919497;color:#ffffff">
<th valign="top" align="left"><bold>Session</bold></th>
<th valign="top" align="center"><bold>ABtesting</bold></th>
<th valign="top" align="center"><bold>Statistics</bold></th>
<th valign="top" align="center"><bold>Multiplechoice</bold></th>
<th valign="top" align="center"><bold>License</bold></th>
</tr>
</thead>
<tbody>
<tr>
<td valign="top" align="left"><italic>u</italic><sub>1</sub></td>
<td valign="top" align="center">1</td>
<td valign="top" align="center">1</td>
<td valign="top" align="center">0</td>
<td valign="top" align="center">100</td>
</tr> <tr>
<td valign="top" align="left"><italic>u</italic><sub>2</sub></td>
<td valign="top" align="center">0</td>
<td valign="top" align="center">1</td>
<td valign="top" align="center">0</td>
<td valign="top" align="center">0</td>
</tr> <tr>
<td valign="top" align="left"><italic>u</italic><sub>3</sub></td>
<td valign="top" align="center">1</td>
<td valign="top" align="center">1</td>
<td valign="top" align="center">1</td>
<td valign="top" align="center">100</td>
</tr> <tr>
<td valign="top" align="left">Group model</td>
<td valign="top" align="center">1</td>
<td valign="top" align="center">1</td>
<td valign="top" align="center">0</td>
<td valign="top" align="center">100</td>
</tr></tbody>
</table>
</table-wrap>
<p>We want to emphasize that following the approach of <italic>aggregated models</italic> can result in situations where no exact match between the attribute settings in the group model and corresponding item properties is possible. However, in such cases, the applied similarity functions will recommend items most similar to the preferences stored in the group model.</p>
<p>If a <italic>critiquing-based recommendation</italic> approach (McCarthy et al., <xref ref-type="bibr" rid="B85">2006</xref>) is used, an <italic>aggregated prediction</italic> approach can be implemented in such a way that each group member completes an individual critiquing process, and the resulting items are then merged by an aggregation function. Following an <italic>aggregated models</italic> approach, individual critiques can be merged, for example, after one or more critiquing cycles, in order to show a new reference item (to individual group members) which is regarded as current recommendation for the whole group&#x02014;see also McCarthy et al. (<xref ref-type="bibr" rid="B85">2006</xref>) and Felfernig et al. (<xref ref-type="bibr" rid="B37">2024b</xref>).</p>
<p>In <italic>constraint-based recommendation</italic>, in both cases, i.e., aggregated preferences and aggregated models, a group recommender would have to aggregate the preferences (attribute settings) of the individual group members (Felfernig et al., <xref ref-type="bibr" rid="B37">2024b</xref>). Again, different aggregation approaches on the attribute level are possible&#x02014;if we follow the goal of achieving fairness (Le et al., <xref ref-type="bibr" rid="B76">2022</xref>), for example, in terms of a nearly equal number of accepted compromises per group member, a corresponding optimization (minimization) problem needs to be solved (see <xref ref-type="disp-formula" rid="E3">Equation 3</xref>). In this context, <italic>p</italic>(<italic>u</italic><sub>&#x003B1;</sub>) denotes the preferences of group member <italic>u</italic><sub>&#x003B1;</sub>, <italic>rec</italic> denotes the determined group recommendation, and <italic>diff</italic>(<italic>p</italic>(<italic>u</italic><sub>&#x003B1;</sub>, <italic>rec</italic>)) denotes the number of preference tradeoffs to be accepted by group member <italic>u</italic><sub>&#x003B1;</sub>. This is a group recommendation that takes into account the aspect of <italic>fairness</italic> minimizing tradeoff distances among individual group members.</p>
<disp-formula id="E3"><label>(3)</label><mml:math id="M3"><mml:mrow><mml:mi>M</mml:mi><mml:mi>I</mml:mi><mml:mi>N</mml:mi><mml:mo>&#x02190;</mml:mo><mml:msub><mml:mi>&#x003A3;</mml:mi><mml:mrow><mml:mo>&#x0007B;</mml:mo><mml:msub><mml:mi>u</mml:mi><mml:mi>i</mml:mi></mml:msub><mml:mo>,</mml:mo><mml:msub><mml:mi>u</mml:mi><mml:mi>j</mml:mi></mml:msub><mml:mo>&#x0007D;</mml:mo><mml:mo>&#x02286;</mml:mo><mml:mi>U</mml:mi><mml:mi>s</mml:mi><mml:mi>e</mml:mi><mml:mi>r</mml:mi><mml:mi>s</mml:mi></mml:mrow></mml:msub><mml:mo>&#x000A0;</mml:mo><mml:mo>&#x0007C;</mml:mo><mml:mi>d</mml:mi><mml:mi>i</mml:mi><mml:mi>f</mml:mi><mml:mi>f</mml:mi><mml:mo>&#x000A0;</mml:mo><mml:mo stretchy='false'>(</mml:mo><mml:mi>p</mml:mi><mml:mo stretchy='false'>(</mml:mo><mml:msub><mml:mi>u</mml:mi><mml:mi>i</mml:mi></mml:msub><mml:mo>,</mml:mo><mml:mi>r</mml:mi><mml:mi>e</mml:mi><mml:mi>c</mml:mi><mml:mo stretchy='false'>)</mml:mo><mml:mo>&#x02212;</mml:mo><mml:mi>d</mml:mi><mml:mi>i</mml:mi><mml:mi>f</mml:mi><mml:mi>f</mml:mi><mml:mo>&#x000A0;</mml:mo><mml:mo stretchy='false'>(</mml:mo><mml:mi>p</mml:mi><mml:mo stretchy='false'>(</mml:mo><mml:msub><mml:mi>u</mml:mi><mml:mi>j</mml:mi></mml:msub><mml:mo>,</mml:mo><mml:mi>r</mml:mi><mml:mi>e</mml:mi><mml:mi>c</mml:mi><mml:mo stretchy='false'>)</mml:mo><mml:mo stretchy='false'>)</mml:mo><mml:mo>&#x0007C;</mml:mo></mml:mrow></mml:math></disp-formula>
</sec>
<sec>
<title>4.5 Further aspects</title>
<sec>
<title>4.5.1 Hybrid recommendation approaches</title>
<p>The knowledge-based recommendation approaches discussed up to now have&#x02014;as a central element&#x02014;an item assortment (i.e., product catalog) or a knowledge base that describes the item assortment in an intensional fashion. Knowledge-based recommendation can also be applied in hybrid recommendation scenarios taking over the role of a supportive/complementary component (Burke, <xref ref-type="bibr" rid="B11">2002</xref>). In many cases, knowledge-based recommender systems take over the role of being responsible of checking domain-specific properties, for example, when recommending medical services, it must be assured that the medical item is compatible with the current state of health of a patient. Furthermore, knowledge bases (e.g., in terms of ontologies and knowledge graphs) can be applied, for example, as a basis for similarity metrics that are able to take into account knowledge structures (Bahramian and Ali Abbaspour, <xref ref-type="bibr" rid="B4">2015</xref>; Colombo-Mendoza et al., <xref ref-type="bibr" rid="B18">2015</xref>; Wang et al., <xref ref-type="bibr" rid="B118">2019a</xref>,<xref ref-type="bibr" rid="B119">b</xref>; Sun et al., <xref ref-type="bibr" rid="B106">2020</xref>; Zhu et al., <xref ref-type="bibr" rid="B128">2020</xref>; Sha et al., <xref ref-type="bibr" rid="B104">2021</xref>).</p></sec>
<sec>
<title>4.5.2 Search optimization</title>
<p>Performance optimization can become an issue specifically in the context of constraint-based recommendation and related conflict detection and diagnosis problem solving (Reiter, <xref ref-type="bibr" rid="B102">1987</xref>; Junker, <xref ref-type="bibr" rid="B68">2004</xref>; Felfernig et al., <xref ref-type="bibr" rid="B52">2012</xref>; Le et al., <xref ref-type="bibr" rid="B74">2023</xref>). Improving the efficiency of constraint solving primarily depends on the ability to select optimal heuristics depending on the given search problem. Optimizing search efficiency is often based on the application of machine learning. A detailed overview of integration scenarios for constraint solving and machine learning is given in the study by Popescu et al. (<xref ref-type="bibr" rid="B98">2022</xref>). Specifically in the context of constraint-based recommendation, multi-criteria optimization becomes an issue since (1) constraint-based recommenders are typically applied in interactive scenarios with the need of efficient solution search and (2) at the same time, solutions must be personalized, i.e., take into account the preferences of a user. Thus, constraint-based recommendation is an important application field with the need of an in-depth integration of knowledge-based reasoning and machine learning (Uta et al., <xref ref-type="bibr" rid="B115">2022</xref>).</p></sec>
<sec>
<title>4.5.3 Knowledge acquisition and maintenance</title>
<p>This is an important aspect specifically in the context of constraint-based recommendation where recommendation knowledge is encoded in terms of constraints, rules, or database queries (Jannach and Kreutler, <xref ref-type="bibr" rid="B66">2007</xref>; Felfernig et al., <xref ref-type="bibr" rid="B39">2009a</xref>, <xref ref-type="bibr" rid="B50">2013b</xref>). It must be ensured that the defined constraints correspond with real-world constraints, i.e., reflect the item domain and recommendation knowledge. The related phenomenon of the <italic>knowledge acquisition bottleneck</italic>, i.e., significant communication overheads between domain experts and knowledge engineers, is still omnipresent when applying such knowledge-based systems. Related research efforts focus on the topics of <italic>automated testing and debugging, human-centered knowledge acquisition</italic>, and <italic>deep models of knowledge understanding</italic>. Automated testing and debugging focuses on the application of model-based diagnosis where pre-defined test cases are used to induce conflicts in the knowledge base which are then resolved on the basis of diagnosis algorithms&#x02014;see, for example, Le et al. (<xref ref-type="bibr" rid="B75">2021</xref>). Understanding the complexity individual knowledge structures can also help to increase the maintainability of knowledge bases&#x02014;this topic includes the aspects of cognitive complexities of knowledge structures (Felfernig et al., <xref ref-type="bibr" rid="B49">2015</xref>) and related knowledge structuring, for example, in terms of the ordering of constraints in a recommendation knowledge base (Felfernig et al., <xref ref-type="bibr" rid="B48">2013a</xref>). Finally, human-computation-based knowledge acquisition (Ulz et al., <xref ref-type="bibr" rid="B114">2017</xref>) and user query recommendation (Daoudi et al., <xref ref-type="bibr" rid="B22">2016</xref>) make knowledge definition accessible to domain experts by asking simple questions, for example, <italic>given the user requirements of</italic> <italic>statistics</italic> &#x0003D; 1 <italic>and</italic> <italic>license</italic> &#x0003D; 100<italic>, which items can be recommended?</italic> From the answers to such questions, a recommendation knowledge base can be generated (Ulz et al., <xref ref-type="bibr" rid="B114">2017</xref>).</p></sec>
<sec>
<title>4.5.4 Conversational recommendation</title>
<p>Following the characterizations of Christakopoulou et al. (<xref ref-type="bibr" rid="B17">2016</xref>), Wu et al. (<xref ref-type="bibr" rid="B123">2019</xref>),; Cordero et al. (<xref ref-type="bibr" rid="B19">2020</xref>), Dong et al. (<xref ref-type="bibr" rid="B24">2020</xref>), Zhou et al. (<xref ref-type="bibr" rid="B127">2020</xref>), and Jannach et al. (<xref ref-type="bibr" rid="B67">2021</xref>) conversational recommender systems are interactive systems supporting users in the navigation of the item space in an efficient fashion and recommend items based on a systematic approach of preference elicitation. Knowledge-based recommenders can be regarded as conversational since users are guided through a preference elicitation dialog (Zou et al., <xref ref-type="bibr" rid="B130">2020</xref>). However, further types of conversational recommender systems exist which extend existing approaches specifically with more flexible types of preference elicitation using, for example, natural language dialogs (Grasch et al., <xref ref-type="bibr" rid="B61">2013</xref>), chatbot technologies (Tazl et al., <xref ref-type="bibr" rid="B107">2019</xref>), and specific interfaces based on large language models (Dai et al., <xref ref-type="bibr" rid="B21">2023</xref>).</p></sec>
<sec>
<title>4.5.5 Explanations in knowledge-based recommendation</title>
<p>In the context of recommender systems, explanations can have various goals such as persuading users to purchase an item, to increase the level of trust in a recommendation, or simply to extend a user&#x00027;s item domain knowledge (Tintarev and Masthoff, <xref ref-type="bibr" rid="B111">2012</xref>). In this context, basic explanation types are the following: (1) <italic>why</italic> explanations help a user to understand the reasons why a specific item has been recommended. In the context of single-shot recommendation approaches such as collaborative filtering and content-based filtering, explanations are directly related to the used algorithmic approach. For example, <italic>this item is recommended, since similar users also liked it</italic> or <italic>this item is recommended, since you liked similar items in the past</italic>. Answering such <italic>why</italic> questions in the context of knowledge-based recommendation means to relate recommendations to user preferences, for example, <italic>this camera is recommended since it includes a high frame rate per second which corresponds to your requirement to be able to perform sports photography on a professional level</italic>. This example also shows that recommendation dialogs do not necessarily include technical item properties but could also support scenarios where users specify <italic>high-level preferences</italic> (Felfernig et al., <xref ref-type="bibr" rid="B40">2006</xref>) which are then translated into technical properties by the recommender system. (2) <italic>Why not</italic> explanations help users to understand in more detail why no solution could be found for their requirements. In this context, conflicts (Junker, <xref ref-type="bibr" rid="B68">2004</xref>) help to understand, for example, individual incompatibilities between user requirements, whereas diagnoses (Reiter, <xref ref-type="bibr" rid="B102">1987</xref>; Felfernig et al., <xref ref-type="bibr" rid="B52">2012</xref>) are a general proposal (explanation) for resolving an inconsistency. (3) <italic>How</italic> explanations are more related to specific aspects of a recommendation process, for example, when using a utility-based approach for item ranking (Felfernig et al., <xref ref-type="bibr" rid="B40">2006</xref>), explanations can take into account corresponding weights to explain how a recommendation has been determined, for example, <italic>since you have ranked the priority of the feature fps (frame rate per second) very high, item X is the one which is ranked highest since it received the highest utility value on the basis of our evaluation function</italic>. <italic>How</italic> explanations play a major role in the context of group recommendations&#x02014;specifically to achieve goals such as fairness and consensus (Tran et al., <xref ref-type="bibr" rid="B113">2023</xref>; Felfernig et al., <xref ref-type="bibr" rid="B37">2024b</xref>). An example of taking into account such aspects is the following: <italic>since the preferences of user X have not been taken into account for already 3 months, the current restaurant recommendation specifically focuses on taking into account the preferences of X</italic>.</p></sec></sec></sec>
<sec id="s5">
<title>5 Research directions</title>
<p>Basic insights from our analysis are the following. A major strength of knowledge-based (specifically constraint-based) recommenders is their ability to enforce domain-specific constraints. These systems are useful when recommending and explaining high-involvement items such as cars and financial services. A major disadvantage is &#x0201C;setup&#x0201D; efforts that are needed to predefine the recommendation knowledge in terms of product properties, product catalogs, similarity metrics, and constraints. There are many new developments in <italic>knowledge-based (recommender) systems</italic> focusing on a &#x0201C;deep&#x0201D; integration with <italic>machine learning</italic>, thus helping to unify the two worlds (Popescu et al., <xref ref-type="bibr" rid="B98">2022</xref>). However, there are still a couple of research directions that are of interest&#x02014;see the following discussion.</p>
<sec>
<title>5.1 Integrating knowledge-based systems with machine learning</title>
<p>Specifically in constraint-based recommender systems, a major line of research focuses on the integration of concepts and techniques from machine learning into constraint-based reasoning, for example, by learning variable and variable value ordering heuristics (Popescu et al., <xref ref-type="bibr" rid="B98">2022</xref>; Uta et al., <xref ref-type="bibr" rid="B115">2022</xref>). This way, recommendation functionalities can be directly integrated with constraint solving. An issue for future research is to analyze alternative integrations, for example, in which way constraint-based reasoning can be integrated into machine learning&#x02014;such a goal can be achieved using neuro-symbolic AI concepts (Monroe, <xref ref-type="bibr" rid="B91">2022</xref>).</p></sec>
<sec>
<title>5.2 Diagnosis performance optimization</title>
<p>A major runtime performance bottleneck in knowledge-based recommenders are conflict detection and diagnosis algorithms which operate on the basis of individual consistency checks (Jannach, <xref ref-type="bibr" rid="B65">2006</xref>). A related topic for future research is to intensively integrate machine learning techniques that can help to reduce the number of irrelevant consistency checks as much as possible and thus help to improve runtime performance of conflict detection and diagnosis.</p></sec>
<sec>
<title>5.3 Cognitive aspects of preference elicitation</title>
<p>Human decision making is amenable to different types of biases with a potential negative impact on decision quality (Atas et al., <xref ref-type="bibr" rid="B3">2021</xref>). Recommender user interfaces and corresponding preference elicitation dialogs have to take this aspect into account. A major issue for future research is to understand in detail in which way recommender user interfaces can have an impact on decision processes and how to counteract decision biases in such contexts.</p></sec>
<sec>
<title>5.4 Evaluation metrics for knowledge-based recommenders</title>
<p>Current approaches to evaluate recommender systems primarily focus on the aspect of prediction quality and user acceptance (Uta et al., <xref ref-type="bibr" rid="B116">2021</xref>). However, recommender systems also have a huge impact on how customers perceive items, which items are selected, and&#x02014;as a consequence&#x02014;which items have to be produced. This way, recommender systems have to be evaluated with regard to various additional aspects such as the visibility of items in recommendation lists (e.g., how often is an item highly-ranked) and restrictiveness of specific features in recommendation dialogs (e.g., are there too few items that support specific feature combinations). Initial related work on these aspects can be found in the study by Lubos et al. (<xref ref-type="bibr" rid="B81">2023</xref>).</p></sec>
<sec>
<title>5.5 Consequence-based explanations</title>
<p>Explanations in recommender systems focus on reasons as to why specific items have been recommended, why no solution could be identified, and how items have been determined (Friedrich and Zanker, <xref ref-type="bibr" rid="B58">2011</xref>; Tintarev and Masthoff, <xref ref-type="bibr" rid="B111">2012</xref>). Future research should focus more on the generation of explanations that take into account the consequences of choosing specific items, for example, in the context of investment decisions, a consequence-based explanation could be of type <italic>since you prefer to purchase a quite expensive car, this will have an impact on both, the quality of living (in terms of having a smaller house) and in terms of being able to have money for holidays</italic>.</p></sec>
<sec>
<title>5.6 Integration of large language models</title>
<p>The application of large language models (LLMs) in knowledge-based recommender systems (and beyond) starts to play a major role in the context of various tasks such as preference elicitation (e.g., in terms of building semantically-enriched user models) and explanations, for example, by identifying the best explanation strategy in specific recommendation contexts (see <xref ref-type="table" rid="T18">Table 18</xref>&#x02014;the examples have been generated with ChatGPT 3.5).<xref ref-type="fn" rid="fn0011"><sup>11</sup></xref></p>
<table-wrap position="float" id="T18">
<label>Table 18</label>
<caption><p>Examples of LLMs in knowledge-based digital camera recommendation.</p></caption>
<table frame="box" rules="all">
<thead>
<tr style="background-color:#919497;color:#ffffff">
<th valign="top" align="left"><bold>Scenario</bold></th>
<th valign="top" align="left"><bold>Example (prompt)</bold></th>
<th valign="top" align="left"><bold>LLM response (excerpt)</bold></th>
</tr>
</thead>
<tbody>
 <tr>
<td valign="top" align="left">Flexibly explaining physical properties</td>
<td valign="top" align="left">Why does a lower-resolution camera often provide a higher image quality?</td>
<td valign="top" align="left">In some cases, lower-resolution cameras have larger individual pixels. Larger pixels can capture more light, which can contribute to better image quality, especially in low-light conditions.</td>
</tr> <tr>
<td valign="top" align="left">Flexible item comparisons</td>
<td valign="top" align="left">What is the most important difference between the Canon EOS 5d mark IV and the 5d mark II in terms of image quality?</td>
<td valign="top" align="left">The Mark IV has a wider ISO range and generally better low-light performance compared to the Mark II. The increased resolution does not sacrifice sensitivity, and the Mark IV is capable of producing cleaner images at higher ISO settings.</td>
</tr></tbody>
</table>
<table-wrap-foot>
<p>The examples already show the high flexibility in providing explanations to recommender users.</p>
</table-wrap-foot>
</table-wrap></sec>
<sec>
<title>5.7 Sustainability aspects of recommender systems</title>
<p>Recommender systems can play a major role in achieving individual sustainability goals. These systems can help, for example, to systematically optimize energy consumption strategies in households, optimize resource reuse in supply chains, and improve personal wellbeing (Murphy et al., <xref ref-type="bibr" rid="B92">2015</xref>; Felfernig et al., <xref ref-type="bibr" rid="B55">2023b</xref>,<xref ref-type="bibr" rid="B56">c</xref>). A major issue for future research is to more intensively integrate psychological approaches such as nudging (Thaler and Sunstein, <xref ref-type="bibr" rid="B110">2021</xref>) into recommendation dialogs and to develop new algorithms which help to increase the selection share of sustainable items.</p></sec>
<sec>
<title>5.8 Generalizability to other knowledge-based systems</title>
<p>The concepts discussed in this article can be applied to other systems beyond knowledge-based recommender systems. For example, the concepts of personalized constraint-based recommendation and corresponding diagnosis concepts are also applicable in the context of configuration and re-configuration for highly-variant and complex products and services and also in the context of scheduling and re-scheduling (Felfernig et al., <xref ref-type="bibr" rid="B43">2014</xref>).</p></sec></sec>
<sec sec-type="conclusions" id="s6">
<title>6 Conclusion</title>
<p>With this article, we provide an overview of major concepts of the knowledge-based recommender systems extending existing overviews with new technological developments. In this context, we provide working examples that help to understand the underlying techniques and algorithms in more detail. Finally, as a result of our literature analysis, we discuss different research directions in knowledge-based recommendation which will help to stimulate further related research.</p></sec>
<sec sec-type="author-contributions" id="s7">
<title>Author contributions</title>
<p>MU: Conceptualization, Data curation, Formal analysis, Investigation, Project administration, Software, Validation, Writing &#x02013; original draft, Writing &#x02013; review &#x00026; editing. AF: Conceptualization, Methodology, Supervision, Validation, Writing &#x02013; original draft, Writing &#x02013; review &#x00026; editing. V-ML: Conceptualization, Validation, Writing &#x02013; review &#x00026; editing. TT: Validation, Writing &#x02013; review &#x00026; editing. DG: Validation, Writing &#x02013; review &#x00026; editing. SL: Validation, Writing &#x02013; review &#x00026; editing. TB: Validation, Writing &#x02013; review &#x00026; editing.</p></sec>
</body>
<back>
<sec sec-type="funding-information" id="s8">
<title>Funding</title>
<p>The author(s) declare financial support was received for the research, authorship, and/or publication of this article. This work was supported by TU Graz Open Access Publishing Fund.</p>
</sec>
<sec sec-type="COI-statement" id="conf1">
<title>Conflict of interest</title>
<p>MU was employed by Siemens Energy AG. The remaining authors declare that the research was conducted in the absence of any commercial or financial relationships that could be construed as a potential conflict of interest.</p>
</sec>
<sec sec-type="disclaimer" id="s9">
<title>Publisher&#x00027;s note</title>
<p>All claims expressed in this article are solely those of the authors and do not necessarily represent those of their affiliated organizations, or those of the publisher, the editors and the reviewers. Any product that may be evaluated in this article, or claim that may be made by its manufacturer, is not guaranteed or endorsed by the publisher.</p>
</sec>
<fn-group>
<fn id="fn0001"><p><sup>1</sup><ext-link ext-link-type="uri" xlink:href="https://scholar.google.com/">https://scholar.google.com/</ext-link></p></fn>
<fn id="fn0002"><p><sup>2</sup><ext-link ext-link-type="uri" xlink:href="https://www.researchgate.net/">https://www.researchgate.net/</ext-link></p></fn>
<fn id="fn0003"><p><sup>3</sup><ext-link ext-link-type="uri" xlink:href="https://www.sciencedirect.com/">https://www.sciencedirect.com/</ext-link></p></fn>
<fn id="fn0004"><p><sup>4</sup><ext-link ext-link-type="uri" xlink:href="https://link.springer.com/">https://link.springer.com/</ext-link></p></fn>
<fn id="fn0005"><p><sup>5</sup><ext-link ext-link-type="uri" xlink:href="https://www.elsevier.com/">https://www.elsevier.com/</ext-link></p></fn>
<fn id="fn0006"><p><sup>6</sup>For details, see the following discussion of constraint-based recommender systems.</p></fn>
<fn id="fn0007"><p><sup>7</sup>For simplicity, we omit a differentiation between variables describing user preferences and those describing item properties and different constraints between these variables&#x02014;for related details, we refer to Felfernig et al. (<xref ref-type="bibr" rid="B40">2006</xref>) and Felfernig and Burke (<xref ref-type="bibr" rid="B38">2008</xref>).</p></fn>
<fn id="fn0008"><p><sup>8</sup>In this context, <italic>license</italic> is not regarded as a feature.</p></fn>
<fn id="fn0009"><p><sup>9</sup>In critiquing-based recommendation, such situations occur if search criteria become inconsistent.</p></fn>
<fn id="fn0010"><p><sup>10</sup>For simplicity, all critiquing sessions have the same number of critiques, however, in real-world scenarios, the number of critiques can very significantly between different critiquing sessions.</p></fn>
<fn id="fn0011"><p><sup>11</sup><ext-link ext-link-type="uri" xlink:href="https://openai.com">openai.com</ext-link></p></fn>
</fn-group>
<ref-list>
<title>References</title>
<ref id="B1">
<citation citation-type="journal"><person-group person-group-type="author"><name><surname>Aggarwal</surname> <given-names>C. C.</given-names></name></person-group> (<year>2016</year>). <source>Recommender Systems: The Textbook, 1st Edn.</source> Springer Nature Switzerland AG.</citation>
</ref>
<ref id="B2">
<citation citation-type="journal"><person-group person-group-type="author"><name><surname>Almalis</surname> <given-names>N.</given-names></name> <name><surname>Tsihrintzis</surname> <given-names>G.</given-names></name> <name><surname>Kyritsis</surname> <given-names>E.</given-names></name></person-group> (<year>2018</year>). <article-title>A constraint-based job recommender system integrating fodra</article-title>. <source>Int. J. Comp. Intell. Stud</source>. <volume>7</volume>, <fpage>103</fpage>&#x02013;<lpage>123</lpage>. <pub-id pub-id-type="doi">10.1504/IJCISTUDIES.2018.094894</pub-id></citation>
</ref>
<ref id="B3">
<citation citation-type="journal"><person-group person-group-type="author"><name><surname>Atas</surname> <given-names>M.</given-names></name> <name><surname>Felfernig</surname> <given-names>A.</given-names></name> <name><surname>Polat-Erdeniz</surname> <given-names>S.</given-names></name> <name><surname>Popescu</surname> <given-names>A.</given-names></name> <name><surname>Tran</surname> <given-names>T. N. T.</given-names></name> <name><surname>Uta</surname> <given-names>M.</given-names></name></person-group> (<year>2021</year>). <article-title>Towards psychology-aware preference construction in recommender systems: overview and research issues</article-title>. <source>J. Intell. Inf. Syst</source>. <volume>57</volume>, <fpage>467</fpage>&#x02013;<lpage>489</lpage>. <pub-id pub-id-type="doi">10.1007/s10844-021-00674-5</pub-id></citation>
</ref>
<ref id="B4">
<citation citation-type="journal"><person-group person-group-type="author"><name><surname>Bahramian</surname> <given-names>Z.</given-names></name> <name><surname>Ali Abbaspour</surname> <given-names>R.</given-names></name></person-group> (<year>2015</year>). <article-title>An ontology-based tourism recommender system based on spreading activation model</article-title>. <source>Int. Arch. Photogramm. Remote Sens. Spat. Inf. Sci</source>. <volume>40</volume>, <fpage>83</fpage>&#x02013;<lpage>90</lpage>. <pub-id pub-id-type="doi">10.5194/isprsarchives-XL-1-W5-83-2015</pub-id></citation>
</ref>
<ref id="B5">
<citation citation-type="book"><person-group person-group-type="author"><name><surname>Biere</surname> <given-names>A.</given-names></name> <name><surname>Heule</surname> <given-names>M.</given-names></name> <name><surname>Maaren</surname> <given-names>H.</given-names></name> <name><surname>Walsh</surname> <given-names>T.</given-names></name></person-group> (<year>2021</year>). <source>Handbook of Satisfiability, 2nd Edn</source>. <publisher-loc>Amsterdam</publisher-loc>: <publisher-name>IOS Press</publisher-name>.</citation>
</ref>
<ref id="B6">
<citation citation-type="journal"><person-group person-group-type="author"><name><surname>Bokolo</surname> <given-names>A.</given-names></name></person-group> (<year>2021</year>). <article-title>A case-based reasoning recommender system for sustainable smart city development</article-title>. <source>AI Soc</source>. <volume>36</volume>, <fpage>159</fpage>&#x02013;<lpage>183</lpage>. <pub-id pub-id-type="doi">10.1007/s00146-020-00984-2</pub-id></citation>
</ref>
<ref id="B7">
<citation citation-type="journal"><person-group person-group-type="author"><name><surname>Bouraga</surname> <given-names>S.</given-names></name> <name><surname>Jureta</surname> <given-names>I.</given-names></name> <name><surname>Faulkner</surname> <given-names>S.</given-names></name> <name><surname>Herssens</surname> <given-names>C.</given-names></name></person-group> (<year>2014</year>). <article-title>Knowledge-based recommendation systems: a survey</article-title>. <source>Int. J. Intell. Inf. Technol</source>. <volume>10</volume>, <fpage>1</fpage>&#x02013;<lpage>19</lpage>. <pub-id pub-id-type="doi">10.4018/ijiit.2014040101</pub-id></citation>
</ref>
<ref id="B8">
<citation citation-type="journal"><person-group person-group-type="author"><name><surname>Bridge</surname> <given-names>D.</given-names></name> <name><surname>G&#x000F6;ker</surname> <given-names>M. H.</given-names></name> <name><surname>McGinty</surname> <given-names>L.</given-names></name> <name><surname>Smyth</surname> <given-names>B.</given-names></name></person-group> (<year>2005</year>). <article-title>Case-based recommender systems</article-title>. <source>Knowl. Eng. Rev</source>. <volume>20</volume>, <fpage>315</fpage>&#x02013;<lpage>320</lpage>. <pub-id pub-id-type="doi">10.1017/S0269888906000567</pub-id></citation>
</ref>
<ref id="B9">
<citation citation-type="book"><person-group person-group-type="author"><name><surname>Bridge</surname> <given-names>D. G.</given-names></name></person-group> (<year>2002</year>). <article-title>&#x0201C;Towards conversational recommender systems: a dialogue grammar approach,&#x0201D;</article-title> in <source>ECCBR Workshops</source> (<publisher-loc>Aberdeen</publisher-loc>), <fpage>9</fpage>&#x02013;<lpage>22</lpage>.</citation>
</ref>
<ref id="B10">
<citation citation-type="web"><person-group person-group-type="author"><name><surname>Burke</surname> <given-names>R.</given-names></name></person-group> (<year>2000</year>). <article-title>Knowledge-based recommender systems</article-title>. <source>Encyclop. Libr. Inf. Syst</source>. <volume>69</volume>, <fpage>180</fpage>&#x02013;<lpage>200</lpage>. Available online at: <ext-link ext-link-type="uri" xlink:href="https://citeseerx.ist.psu.edu/document?repid=rep1&#x00026;type=pdf&#x00026;doi=dc133144d431fc3b75c8de27f6bb21da6eb5bc1b">https://citeseerx.ist.psu.edu/document?repid=rep1&#x00026;type=pdf&#x00026;doi=dc133144d431fc3b75c8de27f6bb21da6eb5bc1b</ext-link></citation>
</ref>
<ref id="B11">
<citation citation-type="journal"><person-group person-group-type="author"><name><surname>Burke</surname> <given-names>R.</given-names></name></person-group> (<year>2002</year>). <article-title>Hybrid recommender systems: survey and experiments</article-title>. <source>User Model. User Adapt. Interact</source>. <volume>12</volume>, <fpage>331</fpage>&#x02013;<lpage>370</lpage>. <pub-id pub-id-type="doi">10.1023/A:1021240730564</pub-id></citation>
</ref>
<ref id="B12">
<citation citation-type="journal"><person-group person-group-type="author"><name><surname>Burke</surname> <given-names>R.</given-names></name> <name><surname>Felfernig</surname> <given-names>A.</given-names></name> <name><surname>G&#x000F6;ker</surname> <given-names>M. H.</given-names></name></person-group> (<year>2011</year>). <article-title>Recommender systems: an overview</article-title>. <source>AI Mag</source>. <volume>32</volume>, <fpage>13</fpage>&#x02013;<lpage>18</lpage>. <pub-id pub-id-type="doi">10.1609/aimag.v32i3.2361</pub-id></citation>
</ref>
<ref id="B13">
<citation citation-type="journal"><person-group person-group-type="author"><name><surname>Burke</surname> <given-names>R.</given-names></name> <name><surname>Hammond</surname> <given-names>K.</given-names></name> <name><surname>Young</surname> <given-names>B.</given-names></name></person-group> (<year>1996</year>). <article-title>Knowledge-based navigation of complex information spaces</article-title>. <source>Natl. Conf. Artif. Intell</source>. <volume>462</volume>, <fpage>468</fpage>.</citation>
</ref>
<ref id="B14">
<citation citation-type="journal"><person-group person-group-type="author"><name><surname>Cena</surname> <given-names>F.</given-names></name> <name><surname>Console</surname> <given-names>L.</given-names></name> <name><surname>Vernero</surname> <given-names>F.</given-names></name></person-group> (<year>2021</year>). <article-title>Logical foundations of knowledge-based recommender systems: a unifying spectrum of alternatives</article-title>. <source>Inf. Sci</source>. <volume>546</volume>, <fpage>60</fpage>&#x02013;<lpage>73</lpage>. <pub-id pub-id-type="doi">10.1016/j.ins.2020.07.075</pub-id></citation>
</ref>
<ref id="B15">
<citation citation-type="journal"><person-group person-group-type="author"><name><surname>Chen</surname> <given-names>L.</given-names></name> <name><surname>Pu</surname> <given-names>P.</given-names></name></person-group> (<year>2012</year>). <article-title>Critiquing-based recommenders: survey and emerging trends</article-title>. <source>User Model User Adapt. Interact</source>. <volume>22</volume>, <fpage>125</fpage>&#x02013;<lpage>150</lpage>. <pub-id pub-id-type="doi">10.1007/s11257-011-9108-6</pub-id></citation>
</ref>
<ref id="B16">
<citation citation-type="journal"><person-group person-group-type="author"><name><surname>Chen</surname> <given-names>L.</given-names></name> <name><surname>Yan</surname> <given-names>D.</given-names></name> <name><surname>Wang</surname> <given-names>F.</given-names></name></person-group> (<year>2017</year>). <article-title>User perception of sentiment-integrated critiquing in recommender systems</article-title>. <source>Int. J. Hum. Comput. Stud</source>. <volume>121</volume>, <fpage>4</fpage>&#x02013;<lpage>20</lpage>. <pub-id pub-id-type="doi">10.1016/j.ijhcs.2017.09.005</pub-id></citation>
</ref>
<ref id="B17">
<citation citation-type="book"><person-group person-group-type="author"><name><surname>Christakopoulou</surname> <given-names>K.</given-names></name> <name><surname>Radlinski</surname> <given-names>F.</given-names></name> <name><surname>Hofmann</surname> <given-names>K.</given-names></name></person-group> (<year>2016</year>). <article-title>&#x0201C;Towards conversational recommender systems,&#x0201D;</article-title> in <source>22nd ACM SIGKDD International Conference on Knowledge Discovery and Data Mining, KDD &#x00027;16</source> (<publisher-loc>New York, NY</publisher-loc>: <publisher-name>ACM</publisher-name>), <fpage>815</fpage>&#x02013;<lpage>824</lpage>.</citation>
</ref>
<ref id="B18">
<citation citation-type="journal"><person-group person-group-type="author"><name><surname>Colombo-Mendoza</surname> <given-names>L. O.</given-names></name> <name><surname>Valencia-Garc&#x000ED;a</surname> <given-names>R.</given-names></name> <name><surname>Rodr&#x000ED;guez-Gonz&#x000E1;lez</surname> <given-names>A.</given-names></name> <name><surname>Alor-Hern&#x000E1;ndez</surname> <given-names>G.</given-names></name> <name><surname>Samper-Zapater</surname> <given-names>J. J.</given-names></name></person-group> (<year>2015</year>). <article-title>RecomMetz: a context-aware knowledge-based mobile recommender system for movie showtimes</article-title>. <source>Expert Syst. Appl</source>. <volume>42</volume>, <fpage>1202</fpage>&#x02013;<lpage>1222</lpage>. <pub-id pub-id-type="doi">10.1016/j.eswa.2014.09.016</pub-id></citation>
</ref>
<ref id="B19">
<citation citation-type="journal"><person-group person-group-type="author"><name><surname>Cordero</surname> <given-names>P.</given-names></name> <name><surname>Enciso</surname> <given-names>M.</given-names></name> <name><surname>L&#x000F3;pez</surname> <given-names>D.</given-names></name> <name><surname>Mora</surname> <given-names>A.</given-names></name></person-group> (<year>2020</year>). <article-title>A conversational recommender system for diagnosis using fuzzy rules</article-title>. <source>Expert Syst. Appl</source>. <volume>154</volume>:<fpage>113449</fpage>. <pub-id pub-id-type="doi">10.1016/j.eswa.2020.113449</pub-id></citation>
</ref>
<ref id="B20">
<citation citation-type="book"><person-group person-group-type="author"><name><surname>C&#x000F6;ster</surname> <given-names>R.</given-names></name> <name><surname>Gustavsson</surname> <given-names>A.</given-names></name> <name><surname>Olsson</surname> <given-names>T.</given-names></name> <name><surname>Rudstr&#x000F6;m</surname> <given-names>&#x000C5;.</given-names></name></person-group> (<year>2002</year>). <article-title>&#x0201C;Enhancing web-based configuration with recommendations and cluster-based help,&#x0201D;</article-title> in <source>AH&#x00027;2002 Workshop on Recommendation and Personalization in eCommerce, 28 May 2002</source> (<publisher-loc>M&#x000E1;laga</publisher-loc>), <fpage>1</fpage>&#x02013;<lpage>10</lpage>.</citation>
</ref>
<ref id="B21">
<citation citation-type="book"><person-group person-group-type="author"><name><surname>Dai</surname> <given-names>S.</given-names></name> <name><surname>Shao</surname> <given-names>N.</given-names></name> <name><surname>Zhao</surname> <given-names>H.</given-names></name> <name><surname>Yu</surname> <given-names>W.</given-names></name> <name><surname>Si</surname> <given-names>Z.</given-names></name> <name><surname>Xu</surname> <given-names>C.</given-names></name> <etal/></person-group>. (<year>2023</year>). <article-title>&#x0201C;Uncovering chatgpt?s capabilities in recommender systems,&#x0201D;</article-title> in <source>17th ACM Conference on Recommender Systems, RecSys &#x00027;23</source> (<publisher-loc>New York, NY</publisher-loc>: <publisher-name>Association for Computing Machinery</publisher-name>), <fpage>1126</fpage>&#x02013;<lpage>1132</lpage>.</citation>
</ref>
<ref id="B22">
<citation citation-type="book"><person-group person-group-type="author"><name><surname>Daoudi</surname> <given-names>A.</given-names></name> <name><surname>Mechqrane</surname> <given-names>Y.</given-names></name> <name><surname>Bessiere</surname> <given-names>C.</given-names></name> <name><surname>Lazaar</surname> <given-names>N.</given-names></name> <name><surname>Bouyakhf</surname> <given-names>E. H.</given-names></name></person-group> (<year>2016</year>). <article-title>&#x0201C;Constraint acquisition using recommendation queries,&#x0201D;</article-title> in <source>International Joint Conferences on Artificial Intelligence</source> (<publisher-loc>Palo Alto, CA</publisher-loc>), <fpage>720</fpage>&#x02013;<lpage>726</lpage>.</citation>
</ref>
<ref id="B23">
<citation citation-type="journal"><person-group person-group-type="author"><name><surname>Dara</surname> <given-names>S.</given-names></name> <name><surname>Chowdary</surname> <given-names>C. R.</given-names></name> <name><surname>Kumar</surname> <given-names>C.</given-names></name></person-group> (<year>2020</year>). <article-title>A survey on group recommender systems</article-title>. <source>J. Intell. Inf. Syst</source>. <volume>54</volume>, <fpage>271</fpage>&#x02013;<lpage>295</lpage>. <pub-id pub-id-type="doi">10.1007/s10844-018-0542-3</pub-id></citation>
</ref>
<ref id="B24">
<citation citation-type="journal"><person-group person-group-type="author"><name><surname>Dong</surname> <given-names>M.</given-names></name> <name><surname>Zeng</surname> <given-names>X.</given-names></name> <name><surname>Koehl</surname> <given-names>L.</given-names></name> <name><surname>Zhang</surname> <given-names>J.</given-names></name></person-group> (<year>2020</year>). <article-title>An interactive knowledge-based recommender system for fashion product design in the big data environment</article-title>. <source>Inf. Sci</source>. <volume>540</volume>, <fpage>469</fpage>&#x02013;<lpage>488</lpage>. <pub-id pub-id-type="doi">10.1016/j.ins.2020.05.094</pub-id></citation>
</ref>
<ref id="B25">
<citation citation-type="journal"><person-group person-group-type="author"><name><surname>Dragone</surname> <given-names>P.</given-names></name> <name><surname>Teso</surname> <given-names>S.</given-names></name> <name><surname>Passerini</surname> <given-names>A.</given-names></name></person-group> (<year>2018</year>). <article-title>Constructive preference elicitation</article-title>. <source>Front. Robot. AI</source> <volume>4</volume>:<fpage>71</fpage>. <pub-id pub-id-type="doi">10.3389/frobt.2017.00071</pub-id></citation>
</ref>
<ref id="B26">
<citation citation-type="book"><person-group person-group-type="author"><name><surname>Eiter</surname> <given-names>T.</given-names></name> <name><surname>Ianni</surname> <given-names>G.</given-names></name> <name><surname>Krennwallner</surname> <given-names>T.</given-names></name></person-group> (<year>2009</year>). <article-title>&#x0201C;Answer set programming: a primer,&#x0201D;</article-title> in <source>Reasoning Web Semantic Technologies for Information Systems: International Summer School</source>, eds <person-group person-group-type="editor"><name><surname>Tessaris</surname> <given-names>S.</given-names></name> <name><surname>Franconi</surname> <given-names>E.</given-names></name> <name><surname>Eiter</surname> <given-names>T.</given-names></name> <name><surname>Gutierrez</surname> <given-names>C.</given-names></name> <name><surname>Handschuh</surname> <given-names>S.</given-names></name> <name><surname>Rousset</surname> <given-names>M.-C.</given-names></name> <name><surname>Schmidt</surname> <given-names>R. A.</given-names></name></person-group> (<publisher-loc>Berlin Heidelberg</publisher-loc>: <publisher-name>Springer</publisher-name>), <fpage>40</fpage>&#x02013;<lpage>110</lpage>. <pub-id pub-id-type="doi">10.1007/978-3-642-03754-2_2</pub-id></citation>
</ref>
<ref id="B27">
<citation citation-type="journal"><person-group person-group-type="author"><name><surname>Ekstrand</surname> <given-names>M.</given-names></name> <name><surname>Riedl</surname> <given-names>J.</given-names></name> <name><surname>Konstan</surname> <given-names>J.</given-names></name></person-group> (<year>2011</year>). <article-title>Collaborative filtering recommender systems</article-title>. <source>Found. Trends Human Comp. Interact</source>. 4. <pub-id pub-id-type="doi">10.1561/1100000009</pub-id></citation>
</ref>
<ref id="B28">
<citation citation-type="journal"><person-group person-group-type="author"><name><surname>Erdeniz</surname> <given-names>S. P.</given-names></name> <name><surname>Felfernig</surname> <given-names>A.</given-names></name> <name><surname>Atas</surname> <given-names>M.</given-names></name></person-group> (<year>2022</year>). <article-title>Applying matrix factorization to consistency-based direct diagnosis</article-title>. <source>Appl. Intell</source>. <volume>52</volume>, <fpage>7024</fpage>&#x02013;<lpage>7036</lpage>. <pub-id pub-id-type="doi">10.1007/s10489-020-02183-4</pub-id></citation>
</ref>
<ref id="B29">
<citation citation-type="book"><person-group person-group-type="author"><name><surname>Erdeniz</surname> <given-names>S. P.</given-names></name> <name><surname>Felfernig</surname> <given-names>A.</given-names></name> <name><surname>Samer</surname> <given-names>R.</given-names></name> <name><surname>Atas</surname> <given-names>M.</given-names></name></person-group> (<year>2019</year>). <article-title>&#x0201C;Matrix factorization based heuristics for constraint-based recommenders,&#x0201D;</article-title> in <source>34th ACM/SIGAPP Symposium on Applied Computing</source> (<publisher-loc>New York, NY</publisher-loc>: <publisher-name>ACM</publisher-name>), <fpage>1655</fpage>&#x02013;<lpage>1662</lpage>.</citation>
</ref>
<ref id="B30">
<citation citation-type="journal"><person-group person-group-type="author"><name><surname>Esheiba</surname> <given-names>L.</given-names></name> <name><surname>Elgammal</surname> <given-names>A.</given-names></name> <name><surname>Helal</surname> <given-names>I. M.</given-names></name> <name><surname>El-Sharkawi</surname> <given-names>M. E.</given-names></name></person-group> (<year>2021</year>). <article-title>A hybrid knowledge-based recommender for product-service systems mass customization</article-title>. <source>Information</source> <volume>12</volume>:<fpage>296</fpage>. <pub-id pub-id-type="doi">10.3390/info12080296</pub-id></citation>
</ref>
<ref id="B31">
<citation citation-type="journal"><person-group person-group-type="author"><name><surname>Falkner</surname> <given-names>A.</given-names></name> <name><surname>Felfernig</surname> <given-names>A.</given-names></name> <name><surname>Haag</surname> <given-names>A.</given-names></name></person-group> (<year>2011</year>). <article-title>Recommendation technologies for configurable products</article-title>. <source>AI Mag</source>. <volume>32</volume>, <fpage>99</fpage>&#x02013;<lpage>108</lpage>. <pub-id pub-id-type="doi">10.1609/aimag.v32i3.2369</pub-id></citation>
</ref>
<ref id="B32">
<citation citation-type="book"><person-group person-group-type="author"><name><surname>Fano</surname> <given-names>A.</given-names></name> <name><surname>Kurth</surname> <given-names>S. W.</given-names></name></person-group> (<year>2003</year>). <article-title>&#x0201C;Personal choice point: Helping users visualize what it means to buy a bmw,&#x0201D;</article-title> in <source>8th International Conference on Intelligent User Interfaces, IUI &#x00027;03</source> (<publisher-loc>New York, NY</publisher-loc>: <publisher-name>Association for Computing Machinery</publisher-name>), <fpage>46</fpage>&#x02013;<lpage>52</lpage>.</citation>
</ref>
<ref id="B33">
<citation citation-type="book"><person-group person-group-type="author"><name><surname>Fargier</surname> <given-names>H.</given-names></name> <name><surname>Gimenez</surname> <given-names>P.-F.</given-names></name> <name><surname>Mengin</surname> <given-names>J.</given-names></name></person-group> (<year>2016</year>). <article-title>&#x0201C;Recommendation for product configuration: an experimental evaluation,&#x0201D;</article-title> in <source>18th International Configuration Workshop (CWS 2016) within CP 2016: 22nd International Conference on Principles and Practice of Constraint Programming</source> (<publisher-loc>Albi</publisher-loc>: <publisher-name>&#x000C9;cole des Mines d&#x00027;Albi-Carmaux</publisher-name>), <fpage>9</fpage>.</citation>
</ref>
<ref id="B34">
<citation citation-type="book"><person-group person-group-type="author"><name><surname>Feely</surname> <given-names>C.</given-names></name> <name><surname>Caulfield</surname> <given-names>B.</given-names></name> <name><surname>Lawlor</surname> <given-names>A.</given-names></name> <name><surname>Smyth</surname> <given-names>B.</given-names></name></person-group> (<year>2020</year>). <article-title>&#x0201C;Using case-based reasoning to predict marathon performance and recommend tailored training plans,&#x0201D;</article-title> in <source>Case-Based Reasoning Research and Development: 28th International Conference, ICCBR 2020, Salamanca, Spain, June 8-12, 2020, Proceedings 28</source> (<publisher-loc>Springer Nature Switzerland AG</publisher-loc>), <fpage>67</fpage>&#x02013;<lpage>81</lpage>.</citation>
</ref>
<ref id="B35">
<citation citation-type="journal"><person-group person-group-type="author"><name><surname>Felfernig</surname> <given-names>A.</given-names></name></person-group> (<year>2007</year>). <article-title>Standardized configuration knowledge representations as technological foundation for mass customization</article-title>. <source>IEEE Transact. Eng. Manag</source>. <volume>54</volume>, <fpage>41</fpage>&#x02013;<lpage>56</lpage>. <pub-id pub-id-type="doi">10.1109/TEM.2006.889066</pub-id></citation>
</ref>
<ref id="B36">
<citation citation-type="book"><person-group person-group-type="author"><name><surname>Felfernig</surname> <given-names>A.</given-names></name> <name><surname>Atas</surname> <given-names>M.</given-names></name> <name><surname>Stettinger</surname> <given-names>M.</given-names></name> <name><surname>Tran</surname> <given-names>T.</given-names></name> <name><surname>Reiterer</surname> <given-names>S.</given-names></name></person-group> (<year>2024a</year>). <article-title>&#x0201C;Group recommender applications,&#x0201D;</article-title> in <source>Group Recommender Systems: An Introduction</source>, eds <person-group person-group-type="editor"><name><surname>Felfernig</surname> <given-names>A.</given-names></name> <name><surname>Boratto</surname> <given-names>L.</given-names></name> <name><surname>Stettinger</surname> <given-names>M.</given-names></name> <name><surname>Tkalcic</surname> <given-names>M.</given-names></name></person-group> (<publisher-name>Springer</publisher-name>), <fpage>79</fpage>&#x02013;<lpage>94</lpage>.</citation>
</ref>
<ref id="B37">
<citation citation-type="book"><person-group person-group-type="author"><name><surname>Felfernig</surname> <given-names>A.</given-names></name> <name><surname>Boratto</surname> <given-names>L.</given-names></name> <name><surname>Stettinger</surname> <given-names>M.</given-names></name> <name><surname>Tkalcic</surname> <given-names>M.</given-names></name></person-group> (<year>2024b</year>). <source>Group Recommender Systems: An Introduction</source>. <publisher-loc>Springer Publishing Company Inc</publisher-loc>.</citation>
</ref>
<ref id="B38">
<citation citation-type="book"><person-group person-group-type="author"><name><surname>Felfernig</surname> <given-names>A.</given-names></name> <name><surname>Burke</surname> <given-names>R.</given-names></name></person-group> (<year>2008</year>). <article-title>&#x0201C;Constraint-based recommender systems: technologies and research issues,&#x0201D;</article-title> in <source>10th International Conference on Electronic Commerce, ICEC &#x00027;08</source> (<publisher-loc>New York, NY</publisher-loc>: <publisher-name>Association for Computing Machinery</publisher-name>), <fpage>1</fpage>&#x02013;<lpage>10</lpage>.</citation>
</ref>
<ref id="B39">
<citation citation-type="journal"><person-group person-group-type="author"><name><surname>Felfernig</surname> <given-names>A.</given-names></name> <name><surname>Friedrich</surname> <given-names>G.</given-names></name> <name><surname>Isak</surname> <given-names>K.</given-names></name> <name><surname>Shchekotykhin</surname> <given-names>K.</given-names></name> <name><surname>Teppan</surname> <given-names>E.</given-names></name> <name><surname>Jannach</surname> <given-names>D.</given-names></name></person-group> (<year>2009a</year>). <article-title>Automated debugging of recommender user interface descriptions</article-title>. <source>Appl. Intell</source>. <volume>31</volume>, <fpage>1</fpage>&#x02013;<lpage>14</lpage>. <pub-id pub-id-type="doi">10.1007/s10489-007-0105-8</pub-id></citation>
</ref>
<ref id="B40">
<citation citation-type="journal"><person-group person-group-type="author"><name><surname>Felfernig</surname> <given-names>A.</given-names></name> <name><surname>Friedrich</surname> <given-names>G.</given-names></name> <name><surname>Jannach</surname> <given-names>D.</given-names></name> <name><surname>Zanker</surname> <given-names>M.</given-names></name></person-group> (<year>2006</year>). <article-title>An integrated environment for the development of knowledge-based recommender applications</article-title>. <source>Int. J. Electron. Commerce</source> <volume>11</volume>, <fpage>11</fpage>&#x02013;<lpage>34</lpage>. <pub-id pub-id-type="doi">10.2753/JEC1086-4415110201</pub-id></citation>
</ref>
<ref id="B41">
<citation citation-type="book"><person-group person-group-type="author"><name><surname>Felfernig</surname> <given-names>A.</given-names></name> <name><surname>Friedrich</surname> <given-names>G.</given-names></name> <name><surname>Jannach</surname> <given-names>D.</given-names></name> <name><surname>Zanker</surname> <given-names>M.</given-names></name></person-group> (<year>2011</year>). <article-title>&#x0201C;Developing constraint-based recommenders,&#x0201D;</article-title> in <source>Recommender Systems Handbook</source>, eds <person-group person-group-type="editor"><name><surname>Ricci</surname> <given-names>F.</given-names></name> <name><surname>Rokach</surname> <given-names>L.</given-names></name> <name><surname>Shapira</surname> <given-names>B.</given-names></name> <name><surname>Kantor</surname> <given-names>P.</given-names></name></person-group> (<publisher-name>Springer</publisher-name>), <fpage>187</fpage>&#x02013;<lpage>215</lpage>.</citation>
</ref>
<ref id="B42">
<citation citation-type="book"><person-group person-group-type="author"><name><surname>Felfernig</surname> <given-names>A.</given-names></name> <name><surname>Friedrich</surname> <given-names>G.</given-names></name> <name><surname>Schubert</surname> <given-names>M.</given-names></name> <name><surname>Mandl</surname> <given-names>M.</given-names></name> <name><surname>Mairitsch</surname> <given-names>M.</given-names></name> <name><surname>Teppan</surname> <given-names>E.</given-names></name></person-group> (<year>2009b</year>). <article-title>&#x0201C;Plausible repairs for inconsistent requirements,&#x0201D;</article-title> in <source>21st International Joint Conference on Artificial Intelligence, IJCAI&#x00027;09</source> (<publisher-loc>San Francisco, CA. Morgan Kaufmann Publishers Inc.</publisher-loc>), <fpage>791</fpage>&#x02013;<lpage>796</lpage>.</citation>
</ref>
<ref id="B43">
<citation citation-type="book"><person-group person-group-type="author"><name><surname>Felfernig</surname> <given-names>A.</given-names></name> <name><surname>Hotz</surname> <given-names>L.</given-names></name> <name><surname>Bagley</surname> <given-names>C.</given-names></name> <name><surname>Tiihonen</surname> <given-names>J.</given-names></name></person-group> (<year>2014</year>). <source>Knowledge-based Configuration: From Research to Business Cases</source>. <publisher-loc>San Francisco, CA</publisher-loc>: <publisher-name>Morgan Kaufmann Publishers Inc</publisher-name>.</citation>
</ref>
<ref id="B44">
<citation citation-type="journal"><person-group person-group-type="author"><name><surname>Felfernig</surname> <given-names>A.</given-names></name> <name><surname>Isak</surname> <given-names>K.</given-names></name> <name><surname>Szabo</surname> <given-names>K.</given-names></name> <name><surname>Zachar</surname> <given-names>P.</given-names></name></person-group> (<year>2007</year>). <article-title>&#x0201C;The VITA financial services sales support environment,&#x0201D;</article-title> in <source>19th National Conference on Innovative Applications of Artificial Intelligence</source> - <italic>Volume 2, IAAI&#x00027;07</italic> (AAAI Press), <fpage>1692</fpage>&#x02013;<lpage>1699</lpage>.</citation>
</ref>
<ref id="B45">
<citation citation-type="journal"><person-group person-group-type="author"><name><surname>Felfernig</surname> <given-names>A.</given-names></name> <name><surname>Kiener</surname> <given-names>A.</given-names></name></person-group> (<year>2005</year>). <article-title>&#x0201C;Knowledge-based interactive selling of financial services with FSAdvisor,&#x0201D;</article-title> in <source>17th Conference on Innovative Applications of Artificial Intelligence</source> - <italic>Volume 3, IAAI&#x00027;05</italic> (AAAI Press), <fpage>1475</fpage>&#x02013;<lpage>1482</lpage>.</citation>
</ref>
<ref id="B46">
<citation citation-type="book"><person-group person-group-type="author"><name><surname>Felfernig</surname> <given-names>A.</given-names></name> <name><surname>Le</surname> <given-names>V.</given-names></name> <name><surname>Lubos</surname> <given-names>S.</given-names></name></person-group> (<year>2023a</year>). <article-title>&#x0201C;Conjunctive query based constraint solving for feature model configuration,&#x0201D;</article-title> in <source>12th Conference on Information Technology and Its Applications (CITA 2023), volume 734 of Lecture Notes in Networks and Systems</source> (<publisher-loc>Springer</publisher-loc>), <fpage>357</fpage>&#x02013;<lpage>367</lpage>.</citation>
</ref>
<ref id="B47">
<citation citation-type="book"><person-group person-group-type="author"><name><surname>Felfernig</surname> <given-names>A.</given-names></name> <name><surname>Le</surname> <given-names>V.-M.</given-names></name> <name><surname>Popescu</surname> <given-names>A.</given-names></name> <name><surname>Uta</surname> <given-names>M.</given-names></name> <name><surname>Tran</surname> <given-names>T. N. T.</given-names></name> <name><surname>Atas</surname> <given-names>M.</given-names></name></person-group> (<year>2021</year>). <article-title>&#x0201C;An overview of recommender systems and machine learning in feature modeling and configuration,&#x0201D;</article-title> in <source>15th International Working Conference on Variability Modelling of Software-Intensive Systems, VaMoS &#x00027;21</source> (<publisher-loc>ACM</publisher-loc>), <fpage>1</fpage>&#x02013;<lpage>8</lpage>.</citation>
</ref>
<ref id="B48">
<citation citation-type="journal"><person-group person-group-type="author"><name><surname>Felfernig</surname> <given-names>A.</given-names></name> <name><surname>Reiterer</surname> <given-names>S.</given-names></name> <name><surname>Stettinger</surname> <given-names>M.</given-names></name> <name><surname>Reinfrank</surname> <given-names>F.</given-names></name> <name><surname>Jeran</surname> <given-names>M.</given-names></name> <name><surname>Ninaus</surname> <given-names>G.</given-names></name></person-group> (<year>2013a</year>). <article-title>&#x0201C;Recommender systems for configuration knowledge engineering,&#x0201D;</article-title> in <source>15th International Configuration Workshop, ConfWS &#x00027;13</source>, <fpage>51</fpage>&#x02013;<lpage>54</lpage>.</citation>
</ref>
<ref id="B49">
<citation citation-type="book"><person-group person-group-type="author"><name><surname>Felfernig</surname> <given-names>A.</given-names></name> <name><surname>Reiterer</surname> <given-names>S.</given-names></name> <name><surname>Stettinger</surname> <given-names>M.</given-names></name> <name><surname>Tiihonen</surname> <given-names>J.</given-names></name></person-group> (<year>2015</year>). <article-title>&#x0201C;Towards understanding cognitive aspects of configuration knowledge formalization,&#x0201D;</article-title> in <source>9th International Workshop on Variability Modelling of Software-Intensive Systems, VaMoS &#x00027;15</source> (<publisher-loc>New York, NY</publisher-loc>: <publisher-name>Association for Computing Machinery</publisher-name>), <fpage>117</fpage>&#x02013;<lpage>123</lpage>.</citation>
</ref>
<ref id="B50">
<citation citation-type="journal"><person-group person-group-type="author"><name><surname>Felfernig</surname> <given-names>A.</given-names></name> <name><surname>Schippel</surname> <given-names>S.</given-names></name> <name><surname>Leitner</surname> <given-names>G.</given-names></name> <name><surname>Reinfrank</surname> <given-names>F.</given-names></name> <name><surname>Isak</surname> <given-names>K.</given-names></name> <name><surname>Mandl</surname> <given-names>M.</given-names></name> <etal/></person-group>. (<year>2013b</year>). <article-title>Automated repair of scoring rules in constraint-based recommender systems</article-title>. <source>AI Commun</source>. <volume>26</volume>, <fpage>15</fpage>&#x02013;<lpage>27</lpage>. <pub-id pub-id-type="doi">10.3233/AIC-120543</pub-id></citation>
</ref>
<ref id="B51">
<citation citation-type="book"><person-group person-group-type="author"><name><surname>Felfernig</surname> <given-names>A.</given-names></name> <name><surname>Schubert</surname> <given-names>M.</given-names></name> <name><surname>Reiterer</surname> <given-names>S.</given-names></name></person-group> (<year>2013c</year>). <article-title>&#x0201C;Personalized diagnosis for over-constrained problems,&#x0201D;</article-title> in <source>23rd International Joint Conf. on Artificial Intelligence, IJCAI &#x00027;13</source> (<publisher-loc>AAAI</publisher-loc>), <fpage>1990</fpage>&#x02013;<lpage>1996</lpage>.</citation>
</ref>
<ref id="B52">
<citation citation-type="journal"><person-group person-group-type="author"><name><surname>Felfernig</surname> <given-names>A.</given-names></name> <name><surname>Schubert</surname> <given-names>M.</given-names></name> <name><surname>Zehentner</surname> <given-names>C.</given-names></name></person-group> (<year>2012</year>). <article-title>An efficient diagnosis algorithm for inconsistent constraint sets</article-title>. <source>AI EDAM</source> <volume>26</volume>, <fpage>53</fpage>&#x02013;<lpage>62</lpage>. <pub-id pub-id-type="doi">10.1017/S0890060411000011</pub-id></citation>
</ref>
<ref id="B53">
<citation citation-type="book"><person-group person-group-type="author"><name><surname>Felfernig</surname> <given-names>A.</given-names></name> <name><surname>Stettinger</surname> <given-names>M.</given-names></name> <name><surname>Atas</surname> <given-names>M.</given-names></name> <name><surname>Samer</surname> <given-names>R.</given-names></name> <name><surname>Nerlich</surname> <given-names>J.</given-names></name> <name><surname>Scholz</surname> <given-names>S.</given-names></name> <etal/></person-group>. (<year>2018a</year>). <article-title>&#x0201C;Towards utility-based prioritization of requirements in open source environments,&#x0201D;</article-title> in <source>2018 IEEE 26th International Requirements Engineering Conference (RE)</source> (<publisher-loc>IEEE</publisher-loc>), <fpage>406</fpage>&#x02013;<lpage>411</lpage>.</citation>
</ref>
<ref id="B54">
<citation citation-type="journal"><person-group person-group-type="author"><name><surname>Felfernig</surname> <given-names>A.</given-names></name> <name><surname>Walter</surname> <given-names>R.</given-names></name> <name><surname>Galindo</surname> <given-names>J.</given-names></name> <name><surname>Benavides</surname> <given-names>D.</given-names></name> <name><surname>Atas</surname> <given-names>M.</given-names></name> <name><surname>Polat-Erdeniz</surname> <given-names>S.</given-names></name> <etal/></person-group>. (<year>2018b</year>). <article-title>Anytime diagnosis for reconfiguration</article-title>. <source>J. Intell. Inf. Syst</source>. <volume>51</volume>, <fpage>161</fpage>&#x02013;<lpage>182</lpage>. <pub-id pub-id-type="doi">10.1007/s10844-017-0492-1</pub-id></citation>
</ref>
<ref id="B55">
<citation citation-type="journal"><person-group person-group-type="author"><name><surname>Felfernig</surname> <given-names>A.</given-names></name> <name><surname>Wundara</surname> <given-names>M.</given-names></name> <name><surname>Tran</surname> <given-names>T.</given-names></name> <name><surname>Le</surname> <given-names>V.-M.</given-names></name> <name><surname>Lubos</surname> <given-names>S.</given-names></name> <name><surname>Polat-Erdeniz</surname> <given-names>S.</given-names></name></person-group> (<year>2023b</year>). <article-title>Sports recommender systems: overview and research issues</article-title>. <source>arXiv</source>. <pub-id pub-id-type="doi">10.21203/rs.3.rs-3710874/v1</pub-id></citation>
</ref>
<ref id="B56">
<citation citation-type="journal"><person-group person-group-type="author"><name><surname>Felfernig</surname> <given-names>A.</given-names></name> <name><surname>Wundara</surname> <given-names>M.</given-names></name> <name><surname>Tran</surname> <given-names>T. N. T.</given-names></name> <name><surname>Polat-Erdeniz</surname> <given-names>S.</given-names></name> <name><surname>Lubos</surname> <given-names>S.</given-names></name> <name><surname>El Mansi</surname> <given-names>M.</given-names></name> <etal/></person-group>. (<year>2023c</year>). <article-title>Recommender systems for sustainability: overview and research issues</article-title>. <source>Front. Big Data</source> <volume>6</volume>:<fpage>1284511</fpage>. <pub-id pub-id-type="doi">10.3389/fdata.2023.1284511</pub-id><pub-id pub-id-type="pmid">37965497</pub-id></citation></ref>
<ref id="B57">
<citation citation-type="book"><person-group person-group-type="author"><name><surname>Fesenmaier</surname> <given-names>D.</given-names></name> <name><surname>Ricci</surname> <given-names>F.</given-names></name> <name><surname>Schaumlechner</surname> <given-names>E.</given-names></name> <name><surname>W&#x000F6;ber</surname> <given-names>K.</given-names></name> <name><surname>Zanella</surname> <given-names>C.</given-names></name></person-group> (<year>2003</year>). <article-title>&#x0201C;Dietorecs: travel advisory for multiple decision styles,&#x0201D;</article-title> in <source>Information and Communication Technologies in Tourism 2003</source>, eds A. Frew, M. Hitz, and P. O?Connors (<publisher-loc>New York, NY</publisher-loc>: <publisher-name>Springer</publisher-name>), <fpage>232</fpage>&#x02013;<lpage>241</lpage>.</citation>
</ref>
<ref id="B58">
<citation citation-type="journal"><person-group person-group-type="author"><name><surname>Friedrich</surname> <given-names>G.</given-names></name> <name><surname>Zanker</surname> <given-names>M.</given-names></name></person-group> (<year>2011</year>). <article-title>A taxonomy for generating explanations in recommender systems</article-title>. <source>AI Mag</source>. <volume>32</volume>, <fpage>90</fpage>&#x02013;<lpage>98</lpage>. <pub-id pub-id-type="doi">10.1609/aimag.v32i3.2365</pub-id></citation>
</ref>
<ref id="B59">
<citation citation-type="journal"><person-group person-group-type="author"><name><surname>Gao</surname> <given-names>C.</given-names></name> <name><surname>Lei</surname> <given-names>W.</given-names></name> <name><surname>He</surname> <given-names>X.</given-names></name> <name><surname>de Rijke</surname> <given-names>M.</given-names></name> <name><surname>Chua</surname> <given-names>T.-S.</given-names></name></person-group> (<year>2021</year>). <article-title>Advances and challenges in conversational recommender systems: a survey</article-title>. <source>AI Open</source> <volume>2</volume>, <fpage>100</fpage>&#x02013;<lpage>126</lpage>. <pub-id pub-id-type="doi">10.1016/j.aiopen.2021.06.002</pub-id></citation>
</ref>
<ref id="B60">
<citation citation-type="book"><person-group person-group-type="author"><name><surname>Goeker</surname> <given-names>M.</given-names></name> <name><surname>Thompson</surname> <given-names>C.</given-names></name></person-group> (<year>2000</year>). <article-title>&#x0201C;Personalized conversational case-based recommendation,&#x0201D;</article-title> in <source>Advances in Case-Based Reasoning, Volume 1898 of Lecture Notes in Computer Science</source>, eds E. Blanzieri, and L. Portinale (<publisher-loc>Berlin; Heidelberg</publisher-loc>: <publisher-name>Springer</publisher-name>), <fpage>709</fpage>&#x02013;<lpage>714</lpage>.</citation>
</ref>
<ref id="B61">
<citation citation-type="book"><person-group person-group-type="author"><name><surname>Grasch</surname> <given-names>P.</given-names></name> <name><surname>Felfernig</surname> <given-names>A.</given-names></name> <name><surname>Reinfrank</surname> <given-names>F.</given-names></name></person-group> (<year>2013</year>). <article-title>&#x0201C;ReComment: towards critiquing-based recommendation with speech interaction,&#x0201D;</article-title> in <source>7th ACM Conference on Recommender Systems, RecSys &#x00027;13</source> (<publisher-loc>New York, N</publisher-loc>: <publisher-name>ACM</publisher-name>), <fpage>157</fpage>&#x02013;<lpage>164</lpage>.</citation>
</ref>
<ref id="B62">
<citation citation-type="journal"><person-group person-group-type="author"><name><surname>G&#x000FC;ell</surname> <given-names>M.</given-names></name> <name><surname>Salam&#x000F3;</surname> <given-names>M.</given-names></name> <name><surname>Contreras</surname> <given-names>D.</given-names></name> <name><surname>Boratto</surname> <given-names>L.</given-names></name></person-group> (<year>2020</year>). <article-title>Integrating a cognitive assistant within a critique-based recommender system</article-title>. <source>Cogn. Syst. Res</source>. <volume>64</volume>:<fpage>1</fpage>&#x02013;<lpage>14</lpage>. <pub-id pub-id-type="doi">10.1016/j.cogsys.2020.07.003</pub-id></citation>
</ref>
<ref id="B63">
<citation citation-type="journal"><person-group person-group-type="author"><name><surname>Hernandez-Nieves</surname> <given-names>E.</given-names></name> <name><surname>Hern&#x000E1;ndez</surname> <given-names>G.</given-names></name> <name><surname>Gil-Gonzalez</surname> <given-names>A. B.</given-names></name> <name><surname>Rodr&#x000ED;guez-Gonz&#x000E1;lez</surname> <given-names>S.</given-names></name> <name><surname>Corchado</surname> <given-names>J. M.</given-names></name></person-group> (<year>2021</year>). <article-title>Cebra: a case-based reasoning application to recommend banking products</article-title>. <source>Eng. Appl. Artif. Intell</source>. <volume>104</volume>:<fpage>104327</fpage>. <pub-id pub-id-type="doi">10.1016/j.engappai.2021.104327</pub-id></citation>
</ref>
<ref id="B64">
<citation citation-type="book"><person-group person-group-type="author"><name><surname>Iaquinta</surname> <given-names>L.</given-names></name> <name><surname>deGemmis</surname> <given-names>M.</given-names></name> <name><surname>Lops</surname> <given-names>P.</given-names></name> <name><surname>Semeraro</surname> <given-names>G.</given-names></name> <name><surname>Filannino</surname> <given-names>M.</given-names></name> <name><surname>Molino</surname> <given-names>P.</given-names></name></person-group> (<year>2008</year>). <article-title>&#x0201C;Introducing serendipity in a content-based recommender system,&#x0201D;</article-title> in <source>8th International Conference on Hybrid Intelligent Systems, HIS &#x00027;08</source> (<publisher-loc>Barcelona</publisher-loc>: <publisher-name>IEEE Computer Society</publisher-name>), <fpage>168</fpage>&#x02013;<lpage>173</lpage>.</citation>
</ref>
<ref id="B65">
<citation citation-type="book"><person-group person-group-type="author"><name><surname>Jannach</surname> <given-names>D.</given-names></name></person-group> (<year>2006</year>). <article-title>&#x0201C;Techniques for fast query relaxation in content-based recommender systems,&#x0201D;</article-title> in <source>29th Annual German Conference on Artificial Intelligence</source> (<publisher-loc>Berlin, Heidelberg</publisher-loc>: <publisher-name>Springer</publisher-name>), <fpage>49</fpage>&#x02013;<lpage>63</lpage>.</citation>
</ref>
<ref id="B66">
<citation citation-type="web"><person-group person-group-type="author"><name><surname>Jannach</surname> <given-names>D.</given-names></name> <name><surname>Kreutler</surname> <given-names>G.</given-names></name></person-group> (<year>2007</year>). <article-title>Rapid development of knowledge-based conversational recommender applications with advisor suite</article-title>. <source>J. Web Eng</source>. <volume>6</volume>, <fpage>165</fpage>&#x02013;<lpage>192</lpage>. Available online at: <ext-link ext-link-type="uri" xlink:href="https://www.researchgate.net/profile/Dietmar-Jannach/publication/220538223_Rapid_Development_of_Knowledge-Based_Conversational_Recommender_Applications_with_Advisor_Suite/links/5e30386a299bf1cdb9f69472/Rapid-Development-of-Knowledge-Based-Conversational-Recommender-Applications-with-Advisor-Suite.pdf?_sg%5B0%5D=started_experiment_milestone&#x00026;origin=journalDetail">https://www.researchgate.net/profile/Dietmar-Jannach/publication/220538223_Rapid_Development_of_Knowledge-Based_Conversational_Recommender_Applications_with_Advisor_Suite/links/5e30386a299bf1cdb9f69472/Rapid-Development-of-Knowledge-Based-Conversational-Recommender-Applications-with-Advisor-Suite.pdf?_sg%5B0%5D=started_experiment_milestone&#x00026;origin=journalDetail</ext-link></citation>
</ref>
<ref id="B67">
<citation citation-type="journal"><person-group person-group-type="author"><name><surname>Jannach</surname> <given-names>D.</given-names></name> <name><surname>Manzoor</surname> <given-names>A.</given-names></name> <name><surname>Cai</surname> <given-names>W.</given-names></name> <name><surname>Chen</surname> <given-names>L.</given-names></name></person-group> (<year>2021</year>). <article-title>A survey on conversational recommender systems</article-title>. <source>ACM Comp. Surv</source>. <volume>54</volume>, <fpage>1</fpage>&#x02013;<lpage>36</lpage>. <pub-id pub-id-type="doi">10.1145/3453154</pub-id></citation>
</ref>
<ref id="B68">
<citation citation-type="book"><person-group person-group-type="author"><name><surname>Junker</surname> <given-names>U.</given-names></name></person-group> (<year>2004</year>). <article-title>&#x0201C;QuickXPlain: Preferred explanations and relaxations for over-constrained problems,&#x0201D;</article-title> in <source>19th National Conference on Artifical Intelligence, AAAI&#x00027;04</source> (<publisher-loc>AAAI Press</publisher-loc>), <fpage>167</fpage>&#x02013;<lpage>172</lpage>.</citation>
</ref>
<ref id="B69">
<citation citation-type="journal"><person-group person-group-type="author"><name><surname>Khan</surname> <given-names>A.</given-names></name> <name><surname>Hoffmann</surname> <given-names>A.</given-names></name></person-group> (<year>2003</year>). <article-title>Building a case-based diet recommendation system without a knowledge engineer</article-title>. <source>Artif. Intell. Med</source>. <volume>27</volume>, <fpage>155</fpage>&#x02013;<lpage>179</lpage>. <pub-id pub-id-type="doi">10.1016/S0933-3657(02)00113-6</pub-id><pub-id pub-id-type="pmid">12636977</pub-id></citation></ref>
<ref id="B70">
<citation citation-type="journal"><person-group person-group-type="author"><name><surname>Knijnenburg</surname> <given-names>B. P.</given-names></name> <name><surname>Willemsen</surname> <given-names>M. C.</given-names></name> <name><surname>Gantner</surname> <given-names>Z.</given-names></name> <name><surname>Soncu</surname> <given-names>H.</given-names></name> <name><surname>Newell</surname> <given-names>C.</given-names></name></person-group> (<year>2012</year>). <article-title>Explaining the user experience of recommender systems</article-title>. <source>User Model. User Adapt. Interact</source>. <volume>22</volume>, <fpage>441</fpage>&#x02013;<lpage>504</lpage>. <pub-id pub-id-type="doi">10.1007/s11257-011-9118-4</pub-id></citation>
</ref>
<ref id="B71">
<citation citation-type="book"><person-group person-group-type="author"><name><surname>Kolodner</surname> <given-names>J.</given-names></name></person-group> (<year>2014</year>). <source>Case-Based Reasoning</source>. <publisher-loc>San Mateo, CA</publisher-loc>: <publisher-name>Morgan Kaufmann</publisher-name>.</citation>
</ref>
<ref id="B72">
<citation citation-type="journal"><person-group person-group-type="author"><name><surname>Kolodner</surname> <given-names>J. L.</given-names></name></person-group> (<year>1992</year>). <article-title>An introduction to case-based reasoning</article-title>. <source>Artif. Intell. Rev</source>. <volume>6</volume>, <fpage>3</fpage>&#x02013;<lpage>34</lpage>. <pub-id pub-id-type="doi">10.1007/BF00155578</pub-id></citation>
</ref>
<ref id="B73">
<citation citation-type="book"><person-group person-group-type="author"><name><surname>Law</surname> <given-names>E.</given-names></name> <name><surname>von Ahn</surname> <given-names>L.</given-names></name></person-group> (<year>2011</year>). <source>Human Computation, 1st Edn</source>. <publisher-loc>Kentfield, CA</publisher-loc>: <publisher-name>Morgan &#x00026; Claypool Publishers</publisher-name>.</citation>
</ref>
<ref id="B74">
<citation citation-type="journal"><person-group person-group-type="author"><name><surname>Le</surname> <given-names>V.</given-names></name> <name><surname>Felfernig</surname> <given-names>A.</given-names></name> <name><surname>Uta</surname> <given-names>M.</given-names></name> <name><surname>Benavides</surname> <given-names>D.</given-names></name> <name><surname>Galindo</surname> <given-names>J.</given-names></name> <name><surname>Tran</surname> <given-names>T.</given-names></name></person-group> (<year>2023</year>). <article-title>&#x0201C;FASTDIAGP: an algorithm for parallelized direct diagnosis,&#x0201D;</article-title> in <source>AAAI Conference on Artificial Intelligence</source>, <fpage>6442</fpage>&#x02013;<lpage>6449</lpage>.</citation>
</ref>
<ref id="B75">
<citation citation-type="book"><person-group person-group-type="author"><name><surname>Le</surname> <given-names>V.-M.</given-names></name> <name><surname>Felfernig</surname> <given-names>A.</given-names></name> <name><surname>Uta</surname> <given-names>M.</given-names></name> <name><surname>Benavides</surname> <given-names>D.</given-names></name> <name><surname>Galindo</surname> <given-names>J.</given-names></name> <name><surname>Tran</surname> <given-names>T. N. T.</given-names></name></person-group> (<year>2021</year>). <article-title>&#x0201C;DirectDebug: automated testing and debugging of feature models,&#x0201D;</article-title> in <source>43rd International Conference on Software Engineering: New Ideas and Emerging Results, ICSE-NIER &#x00027;21</source> (<publisher-loc>Madrid</publisher-loc>: <publisher-name>IEEE Press</publisher-name>), <fpage>81</fpage>&#x02013;<lpage>85</lpage>.</citation>
</ref>
<ref id="B76">
<citation citation-type="journal"><person-group person-group-type="author"><name><surname>Le</surname> <given-names>V.-M.</given-names></name> <name><surname>Tran</surname> <given-names>T. N. T.</given-names></name> <name><surname>Felfernig</surname> <given-names>A.</given-names></name></person-group> (<year>2022</year>). <article-title>&#x0201C;Consistency-based integration of multi-stakeholder recommender systems with feature model configuration,&#x0201D;</article-title> in <source>26th ACM International Systems and Software Product Line Conference-Volume B</source>, <fpage>178</fpage>&#x02013;<lpage>182</lpage>.</citation>
</ref>
<ref id="B77">
<citation citation-type="book"><person-group person-group-type="author"><name><surname>Lee</surname> <given-names>H. J.</given-names></name> <name><surname>Kim</surname> <given-names>H. S.</given-names></name></person-group> (<year>2015</year>). <article-title>&#x0201C;eHealth recommendation service system using ontology and case-based reasoning,&#x0201D;</article-title> in <source>2015 IEEE International Conference on Smart City/SocialCom/SustainCom (SmartCity)</source> (<publisher-loc>Chengdu</publisher-loc>: <publisher-name>IEEE</publisher-name>), <fpage>1108</fpage>&#x02013;<lpage>1113</lpage>.</citation>
</ref>
<ref id="B78">
<citation citation-type="journal"><person-group person-group-type="author"><name><surname>Lee</surname> <given-names>T.</given-names></name> <name><surname>Chun</surname> <given-names>J.</given-names></name> <name><surname>Shim</surname> <given-names>J.</given-names></name> <name><surname>Lee</surname> <given-names>S.</given-names></name></person-group> (<year>2006</year>). <article-title>An ontology-based product recommender system for B2B marketplaces</article-title>. <source>Int. J. Electron. Commerce</source> <volume>11</volume>, <fpage>125</fpage>&#x02013;<lpage>155</lpage>. <pub-id pub-id-type="doi">10.2753/JEC1086-4415110206</pub-id></citation>
</ref>
<ref id="B79">
<citation citation-type="journal"><person-group person-group-type="author"><name><surname>Lika</surname> <given-names>B.</given-names></name> <name><surname>Kolomvatsos</surname> <given-names>K.</given-names></name> <name><surname>Hadjiefthymiades</surname> <given-names>S.</given-names></name></person-group> (<year>2014</year>). <article-title>Facing the cold start problem in recommender systems</article-title>. <source>Expert Syst. Appl</source>. <volume>41</volume>, <fpage>2065</fpage>&#x02013;<lpage>2073</lpage>. <pub-id pub-id-type="doi">10.1016/j.eswa.2013.09.005</pub-id></citation>
</ref>
<ref id="B80">
<citation citation-type="book"><person-group person-group-type="author"><name><surname>Lorenzi</surname> <given-names>F.</given-names></name> <name><surname>Ricci</surname> <given-names>F.</given-names></name></person-group> (<year>2005</year>). <article-title>&#x0201C;Case-based recommender systems: a unifying view,&#x0201D;</article-title> in <source>Intelligent Techniques for Web Personalization, Volume 3169 of Lecture Notes in Computer Science</source>, eds <person-group person-group-type="editor"><name><surname>Mobasher</surname> <given-names>B.</given-names></name> <name><surname>Anand</surname> <given-names>S.</given-names></name></person-group> (<publisher-loc>Berlin; Heidelberg</publisher-loc>: <publisher-name>Springer</publisher-name>), <fpage>89</fpage>&#x02013;<lpage>113</lpage>.</citation>
</ref>
<ref id="B81">
<citation citation-type="book"><person-group person-group-type="author"><name><surname>Lubos</surname> <given-names>S.</given-names></name> <name><surname>Le</surname> <given-names>V.-M.</given-names></name> <name><surname>Felfernig</surname> <given-names>A.</given-names></name> <name><surname>Tran</surname> <given-names>T. N. T.</given-names></name></person-group> (<year>2023</year>). <article-title>&#x0201C;Analysis operations for constraint-based recommender systems,&#x0201D;</article-title> in <source>17th ACM Conference on Recommender Systems, RecSys &#x00027;23</source> (<publisher-loc>New York, NY</publisher-loc>: <publisher-name>ACM</publisher-name>), <fpage>709</fpage>&#x02013;<lpage>714</lpage>.</citation>
</ref>
<ref id="B82">
<citation citation-type="book"><person-group person-group-type="author"><name><surname>Maccatrozzo</surname> <given-names>V.</given-names></name> <name><surname>Terstall</surname> <given-names>M.</given-names></name> <name><surname>Aroyo</surname> <given-names>L.</given-names></name> <name><surname>Schreiber</surname> <given-names>G.</given-names></name></person-group> (<year>2017</year>). <article-title>&#x0201C;Sirup: serendipity in recommendations via user perceptions,&#x0201D;</article-title> in <source>22nd International Conference on Intelligent User Interfaces, IUI &#x00027;17</source> (<publisher-loc>New York, NY</publisher-loc>: <publisher-name>ACM</publisher-name>), <fpage>35</fpage>&#x02013;<lpage>44</lpage>.</citation>
</ref>
<ref id="B83">
<citation citation-type="book"><person-group person-group-type="author"><name><surname>Mandl</surname> <given-names>M.</given-names></name> <name><surname>Felfernig</surname> <given-names>A.</given-names></name></person-group> (<year>2012</year>). <article-title>&#x0201C;Improving the performance of unit critiquing,&#x0201D;</article-title> in <source>20th International Conference on User Modeling, Adaptation, and Personalization, UMAP&#x00027;12</source> (<publisher-loc>Berlin, Heidelberg</publisher-loc>: <publisher-name>Springer-Verlag</publisher-name>), <fpage>176</fpage>&#x02013;<lpage>187</lpage>.</citation>
</ref>
<ref id="B84">
<citation citation-type="book"><person-group person-group-type="author"><name><surname>Masthoff</surname> <given-names>J.</given-names></name></person-group> (<year>2015</year>). <article-title>&#x0201C;Group recommender systems: aggregation, satisfaction and group attributes,&#x0201D;</article-title> in <source>Recommender Systems Handbook, Chapter 22</source> (<publisher-loc>New York, NY</publisher-loc>: <publisher-name>Springer Science&#x0002B;Business Media</publisher-name>), <fpage>743</fpage>&#x02013;<lpage>776</lpage>.</citation>
</ref>
<ref id="B85">
<citation citation-type="book"><person-group person-group-type="author"><name><surname>McCarthy</surname> <given-names>K.</given-names></name> <name><surname>McGinty</surname> <given-names>L.</given-names></name> <name><surname>Smyth</surname> <given-names>B.</given-names></name> <name><surname>Salam,&#x000F3;</surname> <given-names>M.</given-names></name></person-group> (<year>2006</year>). <article-title>&#x0201C;The needs of the many: a case-based group recommender system,&#x0201D;</article-title> in <source>ECCBR 2006, Volume 4106 of Lecture Notes in Computer Science</source>, eds <person-group person-group-type="editor"><name><surname>Roth-Berghofer</surname> <given-names>T.</given-names></name> <name><surname>G&#x000F6;ker</surname> <given-names>M.</given-names></name> <name><surname>G&#x000FC;venir</surname> <given-names>H.</given-names></name></person-group> (<publisher-loc>Berlin; Heidelberg</publisher-loc>: <publisher-name>Springer</publisher-name>), <fpage>196</fpage>&#x02013;<lpage>210</lpage>.</citation>
</ref>
<ref id="B86">
<citation citation-type="book"><person-group person-group-type="author"><name><surname>McCarthy</surname> <given-names>K.</given-names></name> <name><surname>Reilly</surname> <given-names>J.</given-names></name> <name><surname>McGinty</surname> <given-names>L.</given-names></name> <name><surname>Smyth</surname> <given-names>B.</given-names></name></person-group> (<year>2005</year>). <article-title>&#x0201C;Experiments in dynamic critiquing,&#x0201D;</article-title> in <source>10th International Conference on Intelligent User Interfaces, IUI &#x00027;05</source> (<publisher-loc>New York, NY</publisher-loc>: <publisher-name>Association for Computing Machinery</publisher-name>), <fpage>175</fpage>&#x02013;<lpage>182</lpage>.</citation>
</ref>
<ref id="B87">
<citation citation-type="book"><person-group person-group-type="author"><name><surname>McCarthy</surname> <given-names>K.</given-names></name> <name><surname>Salem</surname> <given-names>Y.</given-names></name> <name><surname>Smyth</surname> <given-names>B.</given-names></name></person-group> (<year>2010</year>). <article-title>&#x0201C;Experience-based critiquing: reusing critiquing experiences to improve conversational recommendation,&#x0201D;</article-title> in <source>ICCBR&#x00027;10</source> (<publisher-loc>Springer</publisher-loc>), <fpage>480</fpage>&#x02013;<lpage>494</lpage>.</citation>
</ref>
<ref id="B88">
<citation citation-type="book"><person-group person-group-type="author"><name><surname>McGuinness</surname> <given-names>D.</given-names></name></person-group> (<year>2007</year>). <article-title>&#x0201C;Configuration,&#x0201D;</article-title> in <source>The Description Logic Handbook: Theory, Implementation and Applications, 2 Edn</source> (<publisher-loc>Cambridge</publisher-loc>: <publisher-name>Cambridge University Press</publisher-name>), <fpage>417</fpage>&#x02013;<lpage>435</lpage>.</citation>
</ref>
<ref id="B89">
<citation citation-type="journal"><person-group person-group-type="author"><name><surname>McSherry</surname> <given-names>D.</given-names></name></person-group> (<year>2003</year>). <article-title>&#x0201C;Similarity and compromise,&#x0201D;</article-title> in <source>Case-Based Reasoning Research and Development</source>, eds K. D. Ashley, and D. G. Bridge (Berlin, Heidelberg: Springer Berlin Heidelberg), <fpage>291</fpage>&#x02013;<lpage>305</lpage>.</citation>
</ref>
<ref id="B90">
<citation citation-type="book"><person-group person-group-type="author"><name><surname>Mirzadeh</surname> <given-names>N.</given-names></name> <name><surname>Ricci</surname> <given-names>F.</given-names></name> <name><surname>Bansal</surname> <given-names>M.</given-names></name></person-group> (<year>2005</year>). <article-title>&#x0201C;Feature selection methods for conversational recommender systems,&#x0201D;</article-title> in <source>2005 IEEE International Conference on E-Technology, e-Commerce and e-Service (EEE&#x00027;05) on e-Technology, e-Commerce and e-Service, EEE &#x00027;05</source> (<publisher-loc>Hong Kong</publisher-loc>: <publisher-name>IEEE Computer Society</publisher-name>), <fpage>772</fpage>&#x02013;<lpage>777</lpage>.</citation>
</ref>
<ref id="B91">
<citation citation-type="journal"><person-group person-group-type="author"><name><surname>Monroe</surname> <given-names>D.</given-names></name></person-group> (<year>2022</year>). <article-title>Neurosymbolic AI</article-title>. <source>Commun. ACM</source> <volume>65</volume>, <fpage>11</fpage>&#x02013;<lpage>13</lpage>. <pub-id pub-id-type="doi">10.1145/3554918</pub-id></citation>
</ref>
<ref id="B92">
<citation citation-type="book"><person-group person-group-type="author"><name><surname>Murphy</surname> <given-names>S. &#x000D3;.</given-names></name> <name><surname>Manzano</surname> <given-names>&#x000D3;.</given-names></name> <name><surname>Brown</surname> <given-names>K. N.</given-names></name></person-group> (<year>2015</year>). <article-title>&#x0201C;Design and evaluation of a constraint-based energy saving and scheduling recommender system,&#x0201D;</article-title> in <source>International Conference on Principles and Practice of Constraint Programming</source> (<publisher-loc>Springer International Publishing Switzerland</publisher-loc>), <fpage>687</fpage>&#x02013;<lpage>703</lpage>.</citation>
</ref>
<ref id="B93">
<citation citation-type="journal"><person-group person-group-type="author"><name><surname>Murti</surname> <given-names>Y. A</given-names></name> <name><surname>Baizal</surname> <given-names>Z.</given-names></name> <name><surname>Adiwijaya</surname> <given-names>K.</given-names></name></person-group> (<year>2016</year>). <article-title>Compound critiquing for conversational recommender system based on functional requirement</article-title>. <source>Adv. Sci. Lett</source>. <volume>22</volume>, <fpage>1892</fpage>&#x02013;<lpage>1896</lpage>. <pub-id pub-id-type="doi">10.1166/asl.2016.7770</pub-id></citation>
</ref>
<ref id="B94">
<citation citation-type="journal"><person-group person-group-type="author"><name><surname>Musto</surname> <given-names>C.</given-names></name> <name><surname>Semeraro</surname> <given-names>G.</given-names></name> <name><surname>Lops</surname> <given-names>P.</given-names></name> <name><surname>De Gemmis</surname> <given-names>M.</given-names></name> <name><surname>Lekkas</surname> <given-names>G.</given-names></name></person-group> (<year>2015</year>). <article-title>Personalized finance advisory through case-based recommender systems and diversification strategies</article-title>. <source>Decis. Support Syst</source>. <volume>77</volume>, <fpage>100</fpage>&#x02013;<lpage>111</lpage>. <pub-id pub-id-type="doi">10.1016/j.dss.2015.06.001</pub-id></citation>
</ref>
<ref id="B95">
<citation citation-type="book"><person-group person-group-type="author"><name><surname>Pazzani</surname> <given-names>M. J.</given-names></name> <name><surname>Billsus</surname> <given-names>D.</given-names></name></person-group> (<year>2007</year>). <article-title>&#x0201C;Content-based recommendation systems,&#x0201D;</article-title> in <source>The Adaptive Web: Methods and Strategies of Web Personalization</source> (<publisher-loc>Berlin; Heidelberg</publisher-loc>: <publisher-name>Springer</publisher-name>), <fpage>325</fpage>&#x02013;<lpage>341</lpage>.</citation>
</ref>
<ref id="B96">
<citation citation-type="journal"><person-group person-group-type="author"><name><surname>Pereira</surname> <given-names>J.</given-names></name> <name><surname>Matuszyk</surname> <given-names>P.</given-names></name> <name><surname>Krieter</surname> <given-names>S.</given-names></name> <name><surname>Spiliopoulou</surname> <given-names>M.</given-names></name> <name><surname>Saake</surname> <given-names>G.</given-names></name></person-group> (<year>2016</year>). <article-title>A feature-based personalized recommender system for product-line configuration</article-title>. <source>SIGPLAN Not</source>. <volume>52</volume>:<fpage>2993249</fpage>. <pub-id pub-id-type="doi">10.1145/2993236.2993249</pub-id></citation>
</ref>
<ref id="B97">
<citation citation-type="journal"><person-group person-group-type="author"><name><surname>Pessemier</surname> <given-names>T. D.</given-names></name> <name><surname>Dhondt</surname> <given-names>J.</given-names></name> <name><surname>Martens</surname> <given-names>L.</given-names></name></person-group> (<year>2017</year>). <article-title>Hybrid group recommendations for a travel service</article-title>. <source>Multimed. Tools Appl</source>. <volume>76</volume>, <fpage>2787</fpage>&#x02013;<lpage>2811</lpage>. <pub-id pub-id-type="doi">10.1007/s11042-016-3265-x</pub-id></citation>
</ref>
<ref id="B98">
<citation citation-type="journal"><person-group person-group-type="author"><name><surname>Popescu</surname> <given-names>A.</given-names></name> <name><surname>Polat-Erdeniz</surname> <given-names>S.</given-names></name> <name><surname>Felfernig</surname> <given-names>A.</given-names></name> <name><surname>Uta</surname> <given-names>M.</given-names></name> <name><surname>Atas</surname> <given-names>M.</given-names></name> <name><surname>Le</surname> <given-names>V.-M.</given-names></name> <etal/></person-group>. (<year>2022</year>). <article-title>An overview of machine learning techniques in constraint solving</article-title>. <source>J. Intell. Inf. Syst</source>. <volume>58</volume>, <fpage>91</fpage>&#x02013;<lpage>118</lpage>. <pub-id pub-id-type="doi">10.1007/s10844-021-00666-5</pub-id></citation>
</ref>
<ref id="B99">
<citation citation-type="journal"><person-group person-group-type="author"><name><surname>Pramod</surname> <given-names>D.</given-names></name> <name><surname>Bafna</surname> <given-names>P.</given-names></name></person-group> (<year>2022</year>). <article-title>Conversational recommender systems techniques, tools, acceptance, and adoption: a state of the art review</article-title>. <source>Expert Syst. Appl</source>. <volume>203</volume>:<fpage>117539</fpage>. <pub-id pub-id-type="doi">10.1016/j.eswa.2022.117539</pub-id></citation>
</ref>
<ref id="B100">
<citation citation-type="journal"><person-group person-group-type="author"><name><surname>Rafter</surname> <given-names>R.</given-names></name> <name><surname>Smyth</surname> <given-names>B.</given-names></name></person-group> (<year>2005</year>). <article-title>Conversational collaborative recommendation&#x02014;An experimental analysis</article-title>. <source>Artif. Intell. Rev</source>. <volume>24</volume>, <fpage>301</fpage>&#x02013;<lpage>318</lpage>. <pub-id pub-id-type="doi">10.1007/s10462-005-9004-8</pub-id></citation>
</ref>
<ref id="B101">
<citation citation-type="book"><person-group person-group-type="author"><name><surname>Reilly</surname> <given-names>J.</given-names></name> <name><surname>McCarthy</surname> <given-names>K.</given-names></name> <name><surname>McGinty</surname> <given-names>L.</given-names></name> <name><surname>Smyth</surname> <given-names>B.</given-names></name></person-group> (<year>2004</year>). <article-title>&#x0201C;Dynamic critiquing,&#x0201D;</article-title> in <source>Advances in Case-Based Reasoning: 7th European Conference, ECCBR 2004, Madrid, Spain, August 30-September 2, 2004. Proceedings 7</source> (<publisher-loc>Berlin; Heidelberg</publisher-loc>: <publisher-name>Springer</publisher-name>), <fpage>763</fpage>&#x02013;<lpage>777</lpage>.</citation>
</ref>
<ref id="B102">
<citation citation-type="journal"><person-group person-group-type="author"><name><surname>Reiter</surname> <given-names>R.</given-names></name></person-group> (<year>1987</year>). <article-title>A theory of diagnosis from first principles</article-title>. <source>Artif. Intell</source>. <volume>32</volume>, <fpage>57</fpage>&#x02013;<lpage>95</lpage>. <pub-id pub-id-type="doi">10.1016/0004-3702(87)90062-2</pub-id></citation>
</ref>
<ref id="B103">
<citation citation-type="book"><person-group person-group-type="author"><name><surname>Rossi</surname> <given-names>F.</given-names></name> <name><surname>van Beek</surname> <given-names>P.</given-names></name> <name><surname>Walsh</surname> <given-names>T.</given-names></name></person-group> (<year>2006</year>). <source>Handbook of Constraint Programming</source>. <publisher-loc>Amsterdam</publisher-loc>: <publisher-name>Elsevier Science</publisher-name>.</citation>
</ref>
<ref id="B104">
<citation citation-type="journal"><person-group person-group-type="author"><name><surname>Sha</surname> <given-names>X.</given-names></name> <name><surname>Sun</surname> <given-names>Z.</given-names></name> <name><surname>Zhang</surname> <given-names>J.</given-names></name></person-group> (<year>2021</year>). <article-title>Hierarchical attentive knowledge graph embedding for personalized recommendation</article-title>. <source>Electron. Commer. Res. Appl</source>. <volume>48</volume>:<fpage>101071</fpage>. <pub-id pub-id-type="doi">10.1016/j.elerap.2021.101071</pub-id></citation>
</ref>
<ref id="B105">
<citation citation-type="book"><person-group person-group-type="author"><name><surname>Smyth</surname> <given-names>B.</given-names></name> <name><surname>McGinty</surname> <given-names>L.</given-names></name> <name><surname>Reilly</surname> <given-names>J.</given-names></name> <name><surname>McCarthy</surname> <given-names>K.</given-names></name></person-group> (<year>2004</year>). <article-title>&#x0201C;Compound critiques for conversational recommender systems,&#x0201D;</article-title> in <source>IEEE/WIC/ACM International Conference on Web Intelligence (WI&#x00027;04)</source> (<publisher-loc>Beijing</publisher-loc>: <publisher-name>IEEE</publisher-name>), <fpage>145</fpage>&#x02013;<lpage>151</lpage>.</citation>
</ref>
<ref id="B106">
<citation citation-type="journal"><person-group person-group-type="author"><name><surname>Sun</surname> <given-names>R.</given-names></name> <name><surname>Cao</surname> <given-names>X.</given-names></name> <name><surname>Zhao</surname> <given-names>Y.</given-names></name> <name><surname>Wan</surname> <given-names>J.</given-names></name> <name><surname>Zhou</surname> <given-names>K.</given-names></name> <name><surname>Zhang</surname> <given-names>F.</given-names></name> <etal/></person-group>. (<year>2020</year>). <article-title>&#x0201C;Multi-modal knowledge graphs for recommender systems,&#x0201D;</article-title> in <source>29th ACM International Conference on Information</source> &#x00026; <italic>Knowledge Management</italic>, <fpage>1405</fpage>&#x02013;<lpage>1414</lpage>.</citation>
</ref>
<ref id="B107">
<citation citation-type="book"><person-group person-group-type="author"><name><surname>Tazl</surname> <given-names>O. A.</given-names></name> <name><surname>Perko</surname> <given-names>A.</given-names></name> <name><surname>Wotawa</surname> <given-names>F.</given-names></name></person-group> (<year>2019</year>). <article-title>&#x0201C;Conversational recommendations using model-based reasoning,&#x0201D;</article-title> in <source>CEUR Workshop Proceedings, Vol. 2467</source> (<publisher-loc>Otzenhausen</publisher-loc>: <publisher-name>RWTH Aachen</publisher-name>), <fpage>13</fpage>&#x02013;<lpage>19</lpage>.</citation>
</ref>
<ref id="B108">
<citation citation-type="journal"><person-group person-group-type="author"><name><surname>Temple</surname> <given-names>P.</given-names></name> <name><surname>Acher</surname> <given-names>M.</given-names></name> <name><surname>J&#x000E9;z&#x000E9;quel</surname> <given-names>J.-M.</given-names></name> <name><surname>Barais</surname> <given-names>O.</given-names></name></person-group> (<year>2017</year>). <article-title>Learning contextual-variability models</article-title>. <source>IEEE Softw</source>. <volume>34</volume>, <fpage>64</fpage>&#x02013;<lpage>70</lpage>. <pub-id pub-id-type="doi">10.1109/MS.2017.4121211</pub-id></citation>
</ref>
<ref id="B109">
<citation citation-type="book"><person-group person-group-type="author"><name><surname>Teppan</surname> <given-names>E.</given-names></name> <name><surname>Zanker</surname> <given-names>M.</given-names></name></person-group> (<year>2020</year>). <article-title>&#x0201C;Exploiting answer set programming for building explainable recommendations,&#x0201D;</article-title> in <source>ISMIS 2020, volume 12117 of Lecture Notes in Computer Science</source> (<publisher-loc>Springer</publisher-loc>), <fpage>395</fpage>&#x02013;<lpage>404</lpage>.</citation>
</ref>
<ref id="B110">
<citation citation-type="book"><person-group person-group-type="author"><name><surname>Thaler</surname> <given-names>R.</given-names></name> <name><surname>Sunstein</surname> <given-names>C.</given-names></name></person-group> (<year>2021</year>). <source>Nudge: The Final Edition</source>. <publisher-loc>New Haven, CT; London</publisher-loc>: <publisher-name>Yale University Press</publisher-name>.</citation>
</ref>
<ref id="B111">
<citation citation-type="journal"><person-group person-group-type="author"><name><surname>Tintarev</surname> <given-names>N.</given-names></name> <name><surname>Masthoff</surname> <given-names>J.</given-names></name></person-group> (<year>2012</year>). <article-title>Evaluating the effectiveness of explanations for recommender systems</article-title>. <source>User Model. User Adapt. Interact</source>. <volume>22</volume>, <fpage>399</fpage>&#x02013;<lpage>439</lpage>. <pub-id pub-id-type="doi">10.1007/s11257-011-9117-5</pub-id></citation>
</ref>
<ref id="B112">
<citation citation-type="book"><person-group person-group-type="author"><name><surname>Towle</surname> <given-names>B.</given-names></name> <name><surname>Quinn</surname> <given-names>C.</given-names></name></person-group> (<year>2000</year>). <article-title>&#x0201C;Knowledge based recommender systems using explicit user models,&#x0201D;</article-title> in <source>AAAI Technical Report WS-00-04</source> (<publisher-loc>AAAI Press</publisher-loc>), <fpage>74</fpage>&#x02013;<lpage>77</lpage>.</citation>
</ref>
<ref id="B113">
<citation citation-type="journal"><person-group person-group-type="author"><name><surname>Tran</surname> <given-names>T.</given-names></name> <name><surname>Felfernig</surname> <given-names>A.</given-names></name> <name><surname>Le</surname> <given-names>V.</given-names></name></person-group> (<year>2023</year>). <article-title>An overview of consensus models for group decision-making and group recommender systems</article-title>. <source>User Model. User Adapt. Interact</source>. <pub-id pub-id-type="doi">10.1007/s11257-023-09380-z</pub-id></citation>
</ref>
<ref id="B114">
<citation citation-type="journal"><person-group person-group-type="author"><name><surname>Ulz</surname> <given-names>T.</given-names></name> <name><surname>Schwarz</surname> <given-names>M.</given-names></name> <name><surname>Felfernig</surname> <given-names>A.</given-names></name> <name><surname>Haas</surname> <given-names>S.</given-names></name> <name><surname>Shehadeh</surname> <given-names>A.</given-names></name> <name><surname>Reiterer</surname> <given-names>S.</given-names></name> <etal/></person-group>. (<year>2017</year>). <article-title>Human computation for constraint-based recommenders</article-title>. <source>J. Intell. Inf. Syst</source>. <volume>49</volume>, <fpage>37</fpage>&#x02013;<lpage>57</lpage>. <pub-id pub-id-type="doi">10.1007/s10844-016-0433-4</pub-id></citation>
</ref>
<ref id="B115">
<citation citation-type="book"><person-group person-group-type="author"><name><surname>Uta</surname> <given-names>M.</given-names></name> <name><surname>Felfernig</surname> <given-names>A.</given-names></name> <name><surname>Helic</surname> <given-names>D.</given-names></name> <name><surname>Le</surname> <given-names>V.-M.</given-names></name></person-group> (<year>2022</year>). <article-title>&#x0201C;Accuracy- and consistency-aware recommendation of configuratiosn,&#x0201D;</article-title> in <source>26th ACM International Systems and Software Product Line Conference</source> - <italic>Volume A, SPLC &#x00027;22</italic> (<publisher-loc>New York, NY</publisher-loc>: <publisher-name>Association for Computing Machinery</publisher-name>), <fpage>79</fpage>&#x02013;<lpage>84</lpage>.</citation>
</ref>
<ref id="B116">
<citation citation-type="book"><person-group person-group-type="author"><name><surname>Uta</surname> <given-names>M.</given-names></name> <name><surname>Felfernig</surname> <given-names>A.</given-names></name> <name><surname>Le</surname> <given-names>V.</given-names></name> <name><surname>Popescu</surname> <given-names>A.</given-names></name> <name><surname>Tran</surname> <given-names>T.</given-names></name> <name><surname>Helic</surname> <given-names>D.</given-names></name></person-group> (<year>2021</year>). <article-title>&#x0201C;Evaluating recommender systems in feature model configuration,&#x0201D;</article-title> in <source>25th ACM International Systems and Software Product Line Conference</source> - <italic>Volume A, SPLC &#x00027;21</italic> (<publisher-loc>New York, NY</publisher-loc>: <publisher-name>Association for Computing Machinery</publisher-name>), <fpage>58</fpage>&#x02013;<lpage>63</lpage>.</citation>
</ref>
<ref id="B117">
<citation citation-type="journal"><person-group person-group-type="author"><name><surname>Walter</surname> <given-names>R.</given-names></name> <name><surname>Felfernig</surname> <given-names>A.</given-names></name> <name><surname>K&#x000FC;chlin</surname> <given-names>W.</given-names></name></person-group> (<year>2017</year>). <article-title>Constraint-based and SAT-based diagnosis of automotive configuration problems</article-title>. <source>J. Intell. Inf. Syst</source>. <volume>49</volume>, <fpage>87</fpage>&#x02013;<lpage>118</lpage>. <pub-id pub-id-type="doi">10.1007/s10844-016-0422-7</pub-id></citation>
</ref>
<ref id="B118">
<citation citation-type="book"><person-group person-group-type="author"><name><surname>Wang</surname> <given-names>H.</given-names></name> <name><surname>Zhang</surname> <given-names>F.</given-names></name> <name><surname>Zhang</surname> <given-names>M.</given-names></name> <name><surname>Leskovec</surname> <given-names>J.</given-names></name> <name><surname>Zhao</surname> <given-names>M.</given-names></name> <name><surname>Li</surname> <given-names>W.</given-names></name> <etal/></person-group>. (<year>2019a</year>). <article-title>&#x0201C;Knowledge-aware graph neural networks with label smoothness regularization for recommender systems,&#x0201D;</article-title> in <source>25th ACM SIGKDD International Conference on Knowledge Discovery</source> &#x00026; <italic>Data Mining</italic> (<publisher-loc>New York, NY</publisher-loc>: <publisher-name>ACM</publisher-name>), <fpage>968</fpage>&#x02013;<lpage>977</lpage>.</citation>
</ref>
<ref id="B119">
<citation citation-type="book"><person-group person-group-type="author"><name><surname>Wang</surname> <given-names>H.</given-names></name> <name><surname>Zhao</surname> <given-names>M.</given-names></name> <name><surname>Xie</surname> <given-names>X.</given-names></name> <name><surname>Li</surname> <given-names>W.</given-names></name> <name><surname>Guo</surname> <given-names>M.</given-names></name></person-group> (<year>2019b</year>). <article-title>&#x0201C;Knowledge graph convolutional networks for recommender systems,&#x0201D;</article-title> in <source>The World Wide Web Conference</source> (<publisher-loc>New York, NY</publisher-loc>: <publisher-name>ACM</publisher-name>), <fpage>3307</fpage>&#x02013;<lpage>3313</lpage>.</citation>
</ref>
<ref id="B120">
<citation citation-type="book"><person-group person-group-type="author"><name><surname>Weckesser</surname> <given-names>M.</given-names></name> <name><surname>Kluge</surname> <given-names>R.</given-names></name> <name><surname>Pfannem&#x000FC;ller</surname> <given-names>M.</given-names></name> <name><surname>Matth&#x000E9;</surname> <given-names>M.</given-names></name> <name><surname>Sch&#x000FC;rr</surname> <given-names>A.</given-names></name> <name><surname>Becker</surname> <given-names>C.</given-names></name></person-group> (<year>2018</year>). <article-title>&#x0201C;Optimal reconfiguration of dynamic software product lines based on performance-influence models,&#x0201D;</article-title> in <source>22nd International Systems and Software Product Line Conference, Vol. 1</source> (<publisher-loc>New York, NY</publisher-loc>: <publisher-name>ACM</publisher-name>), <fpage>98</fpage>&#x02013;<lpage>109</lpage>.</citation>
</ref>
<ref id="B121">
<citation citation-type="journal"><person-group person-group-type="author"><name><surname>Wobcke</surname> <given-names>W.</given-names></name> <name><surname>Krzywicki</surname> <given-names>A.</given-names></name> <name><surname>Kim</surname> <given-names>Y. S.</given-names></name> <name><surname>Cai</surname> <given-names>X.</given-names></name> <name><surname>Bain</surname> <given-names>M.</given-names></name> <name><surname>Compton</surname> <given-names>P.</given-names></name> <etal/></person-group>. (<year>2015</year>). <article-title>A deployed people-to-people recommender system in online dating</article-title>. <source>AI Mag</source>. <volume>36</volume>, <fpage>5</fpage>&#x02013;<lpage>18</lpage>. <pub-id pub-id-type="doi">10.1609/aimag.v36i3.2599</pub-id></citation>
</ref>
<ref id="B122">
<citation citation-type="book"><person-group person-group-type="author"><name><surname>Wohlin</surname> <given-names>C.</given-names></name></person-group> (<year>2014</year>). <article-title>&#x0201C;Guidelines for snowballing in systematic literature studies and a replication in software engineering,&#x0201D;</article-title> in <source>18th Intl. Conference on Evaluation and Assessment in Software Engineering</source> (<publisher-loc>New York, NY</publisher-loc>: <publisher-name>ACM</publisher-name>), <fpage>1</fpage>&#x02013;<lpage>10</lpage>.</citation>
</ref>
<ref id="B123">
<citation citation-type="book"><person-group person-group-type="author"><name><surname>Wu</surname> <given-names>G.</given-names></name> <name><surname>Luo</surname> <given-names>K.</given-names></name> <name><surname>Sanner</surname> <given-names>S.</given-names></name> <name><surname>Soh</surname> <given-names>H.</given-names></name></person-group> (<year>2019</year>). <article-title>&#x0201C;Deep language-based critiquing for recommender systems,&#x0201D;</article-title> in <source>13th ACM Conference on Recommender Systems, RecSys &#x00027;19</source> (<publisher-loc>New York, NY</publisher-loc>: <publisher-name>Association for Computing Machinery</publisher-name>), <fpage>137</fpage>&#x02013;<lpage>145</lpage>.</citation>
</ref>
<ref id="B124">
<citation citation-type="journal"><person-group person-group-type="author"><name><surname>Xie</surname> <given-names>H.</given-names></name> <name><surname>Wang</surname> <given-names>D. D.</given-names></name> <name><surname>Rao</surname> <given-names>Y.</given-names></name> <name><surname>Wong</surname> <given-names>T.-L.</given-names></name> <name><surname>Raymond</surname> <given-names>L. Y.</given-names></name> <name><surname>Chen</surname> <given-names>L.</given-names></name> <etal/></person-group>. (<year>2018</year>). <article-title>Incorporating user experience into critiquing-based recommender systems: a collaborative approach based on compound critiquing</article-title>. <source>Int. J. Mach. Learn. Cybernet</source>. <volume>9</volume>, <fpage>837</fpage>&#x02013;<lpage>852</lpage>. <pub-id pub-id-type="doi">10.1007/s13042-016-0611-2</pub-id></citation>
</ref>
<ref id="B125">
<citation citation-type="book"><person-group person-group-type="author"><name><surname>Zanker</surname> <given-names>M.</given-names></name> <name><surname>Bricman</surname> <given-names>M.</given-names></name> <name><surname>Gordea</surname> <given-names>S.</given-names></name> <name><surname>Jannach</surname> <given-names>D.</given-names></name> <name><surname>Jessenitschnig</surname> <given-names>M.</given-names></name></person-group> (<year>2006</year>). <article-title>&#x0201C;Persuasive online-selling in quality and taste domains,&#x0201D;</article-title> in <source>7th International Conference on E-Commerce and Web Technologies, EC-Web&#x00027;06</source> (<publisher-loc>Berlin, Heidelberg</publisher-loc>: <publisher-name>Springer-Verlag</publisher-name>), <fpage>51</fpage>&#x02013;<lpage>60</lpage>.</citation>
</ref>
<ref id="B126">
<citation citation-type="book"><person-group person-group-type="author"><name><surname>Zhang</surname> <given-names>J.</given-names></name> <name><surname>Jones</surname> <given-names>N.</given-names></name> <name><surname>Pu</surname> <given-names>P.</given-names></name></person-group> (<year>2008</year>). <article-title>&#x0201C;A visual interface for critiquing-based recommender systems,&#x0201D;</article-title> in <source>9th ACM Conference on Electronic Commerce</source> (<publisher-loc>New York, NY</publisher-loc>: <publisher-name>ACM</publisher-name>), <fpage>230</fpage>&#x02013;<lpage>239</lpage>.</citation>
</ref>
<ref id="B127">
<citation citation-type="journal"><person-group person-group-type="author"><name><surname>Zhou</surname> <given-names>K.</given-names></name> <name><surname>Zhao</surname> <given-names>W. X.</given-names></name> <name><surname>Bian</surname> <given-names>S.</given-names></name> <name><surname>Zhou</surname> <given-names>Y.</given-names></name> <name><surname>Wen</surname> <given-names>J.-R.</given-names></name> <name><surname>Yu</surname> <given-names>J.</given-names></name></person-group> (<year>2020</year>). <article-title>&#x0201C;Improving conversational recommender systems via knowledge graph based semantic fusion,&#x0201D;</article-title> in <source>26th ACM SIGKDD International Conference on Knowledge Discovery</source> &#x00026; <italic>Data Mining</italic> <fpage>1006</fpage>&#x02013;<lpage>1014</lpage>.</citation>
</ref>
<ref id="B128">
<citation citation-type="book"><person-group person-group-type="author"><name><surname>Zhu</surname> <given-names>Q.</given-names></name> <name><surname>Zhou</surname> <given-names>X.</given-names></name> <name><surname>Wu</surname> <given-names>J.</given-names></name> <name><surname>Tan</surname> <given-names>J.</given-names></name> <name><surname>Guo</surname> <given-names>L.</given-names></name></person-group> (<year>2020</year>). <article-title>&#x0201C;A knowledge-aware attentional reasoning network for recommendation,&#x0201D;</article-title> in <source>AAAI Conference on Artificial Intelligence</source> (<publisher-loc>Palo Alto, CA</publisher-loc>: <publisher-name>AAAI</publisher-name>), <fpage>6999</fpage>&#x02013;<lpage>7006</lpage>.</citation>
</ref>
<ref id="B129">
<citation citation-type="journal"><person-group person-group-type="author"><name><surname>Ziarani</surname> <given-names>R.</given-names></name> <name><surname>Ravanmehr</surname> <given-names>R.</given-names></name></person-group> (<year>2021</year>). <article-title>Serendipity in recommender systems: a systematic literature review</article-title>. <source>J. Comput. Sci. Technol</source>. <volume>36</volume>, <fpage>375</fpage>&#x02013;<lpage>396</lpage>. <pub-id pub-id-type="doi">10.1007/s11390-020-0135-9</pub-id></citation>
</ref>
<ref id="B130">
<citation citation-type="book"><person-group person-group-type="author"><name><surname>Zou</surname> <given-names>J.</given-names></name> <name><surname>Chen</surname> <given-names>Y.</given-names></name> <name><surname>Kanoulas</surname> <given-names>E.</given-names></name></person-group> (<year>2020</year>). <article-title>&#x0201C;Towards question-based recommender systems,&#x0201D;</article-title> in <source>43rd International ACM SIGIR Conference on Research and Development in Information Retrieval, SIGIR &#x00027;20</source> (<publisher-loc>New York, NY</publisher-loc>: <publisher-name>ACM</publisher-name>), <fpage>881</fpage>&#x02013;<lpage>890</lpage>.</citation>
</ref>
</ref-list>
</back>
</article> 