<?xml version="1.0" encoding="UTF-8"?>
<!DOCTYPE article PUBLIC "-//NLM//DTD Journal Publishing DTD v2.0 20040830//EN" "http://dtd.nlm.nih.gov/publishing/2.0/journalpublishing.dtd">
<article xmlns:xlink="http://www.w3.org/1999/xlink" article-type="research-article" dtd-version="2.0">
  <front>
    <journal-meta>
      <journal-id journal-id-type="publisher-id">JMI</journal-id>
      <journal-id journal-id-type="nlm-ta">JMIR Med Inform</journal-id>
      <journal-title>JMIR Medical Informatics</journal-title>
      <issn pub-type="epub">2291-9694</issn>
      <publisher>
        <publisher-name>JMIR Publications</publisher-name>
        <publisher-loc>Toronto, Canada</publisher-loc>
      </publisher>
    </journal-meta>
    <article-meta>
      <article-id pub-id-type="publisher-id">v10i6e33847</article-id>
      <article-id pub-id-type="pmid">35737439</article-id>
      <article-id pub-id-type="doi">10.2196/33847</article-id>
      <article-categories>
        <subj-group subj-group-type="heading">
          <subject>Original Paper</subject>
        </subj-group>
        <subj-group subj-group-type="article-type">
          <subject>Original Paper</subject>
        </subj-group>
      </article-categories>
      <title-group>
        <article-title>Personalized Recommendations for Physical Activity e-Coaching (OntoRecoModel): Ontological Modeling</article-title>
      </title-group>
      <contrib-group>
        <contrib contrib-type="editor">
          <name>
            <surname>Lovis</surname>
            <given-names>Christian</given-names>
          </name>
        </contrib>
      </contrib-group>
      <contrib-group>
        <contrib contrib-type="reviewer">
          <name>
            <surname>Yu</surname>
            <given-names>Jia-Ruei</given-names>
          </name>
        </contrib>
        <contrib contrib-type="reviewer">
          <name>
            <surname>Sobrinho</surname>
            <given-names>Álvaro</given-names>
          </name>
        </contrib>
      </contrib-group>
      <contrib-group>
        <contrib id="contrib1" contrib-type="author" corresp="yes">
          <name name-style="western">
            <surname>Chatterjee</surname>
            <given-names>Ayan</given-names>
          </name>
          <degrees>MEng</degrees>
          <xref rid="aff1" ref-type="aff">1</xref>
          <address>
            <institution>Department of Information and Communication Technology</institution>
            <institution>Center for eHealth</institution>
            <institution>University of Agder</institution>
            <addr-line>Jon Lilletuns Vei 9</addr-line>
            <addr-line>Grimstad, 4879</addr-line>
            <country>Norway</country>
            <phone>47 94719372</phone>
            <email>ayan.chatterjee@uia.no</email>
          </address>
          <ext-link ext-link-type="orcid">https://orcid.org/0000-0003-0407-7702</ext-link>
        </contrib>
        <contrib id="contrib2" contrib-type="author">
          <name name-style="western">
            <surname>Prinz</surname>
            <given-names>Andreas</given-names>
          </name>
          <degrees>PhD</degrees>
          <xref rid="aff1" ref-type="aff">1</xref>
          <ext-link ext-link-type="orcid">https://orcid.org/0000-0002-0646-2877</ext-link>
        </contrib>
      </contrib-group>
      <aff id="aff1">
        <label>1</label>
        <institution>Department of Information and Communication Technology</institution>
        <institution>Center for eHealth</institution>
        <institution>University of Agder</institution>
        <addr-line>Grimstad</addr-line>
        <country>Norway</country>
      </aff>
      <author-notes>
        <corresp>Corresponding Author: Ayan Chatterjee <email>ayan.chatterjee@uia.no</email></corresp>
      </author-notes>
      <pub-date pub-type="collection">
        <month>6</month>
        <year>2022</year>
      </pub-date>
      <pub-date pub-type="epub">
        <day>23</day>
        <month>6</month>
        <year>2022</year>
      </pub-date>
      <volume>10</volume>
      <issue>6</issue>
      <elocation-id>e33847</elocation-id>
      <history>
        <date date-type="received">
          <day>26</day>
          <month>9</month>
          <year>2021</year>
        </date>
        <date date-type="rev-request">
          <day>18</day>
          <month>10</month>
          <year>2021</year>
        </date>
        <date date-type="rev-recd">
          <day>5</day>
          <month>3</month>
          <year>2022</year>
        </date>
        <date date-type="accepted">
          <day>21</day>
          <month>4</month>
          <year>2022</year>
        </date>
      </history>
      <copyright-statement>©Ayan Chatterjee, Andreas Prinz. Originally published in JMIR Medical Informatics (https://medinform.jmir.org), 23.06.2022.</copyright-statement>
      <copyright-year>2022</copyright-year>
      <license license-type="open-access" xlink:href="https://creativecommons.org/licenses/by/4.0/">
        <p>This is an open-access article distributed under the terms of the Creative Commons Attribution License (https://creativecommons.org/licenses/by/4.0/), which permits unrestricted use, distribution, and reproduction in any medium, provided the original work, first published in JMIR Medical Informatics, is properly cited. The complete bibliographic information, a link to the original publication on https://medinform.jmir.org/, as well as this copyright and license information must be included.</p>
      </license>
      <self-uri xlink:href="https://medinform.jmir.org/2022/6/e33847" xlink:type="simple"/>
      <abstract>
        <sec sec-type="background">
          <title>Background</title>
          <p>Automatic e-coaching may motivate individuals to lead a healthy lifestyle with early health risk prediction, personalized recommendation generation, and goal evaluation. Multiple studies have reported on uninterrupted and automatic monitoring of behavioral aspects (such as sedentary time, amount, and type of physical activity); however, e-coaching and personalized feedback techniques are still in a nascent stage. Current intelligent coaching strategies are mostly based on the handcrafted string messages that rarely individualize to each user’s needs, context, and preferences. Therefore, more realistic, flexible, practical, sophisticated, and engaging strategies are needed to model personalized recommendations.</p>
        </sec>
        <sec sec-type="objective">
          <title>Objective</title>
          <p>This study aims to design and develop an ontology to model personalized recommendation message intent, components (such as suggestion, feedback, argument, and follow-ups), and contents (such as spatial and temporal content and objects relevant to perform the recommended activities). A reasoning technique will help to discover implied knowledge from the proposed ontology. Furthermore, recommendation messages can be classified into different categories in the proposed ontology.</p>
        </sec>
        <sec sec-type="methods">
          <title>Methods</title>
          <p>The ontology was created using Protégé (version 5.5.0) open-source software. We used the Java-based Jena Framework (version 3.16) to build a semantic web application as a proof of concept, which included Resource Description Framework application programming interface, World Wide Web Consortium Web Ontology Language application programming interface, native tuple database, and SPARQL Protocol and Resource Description Framework Query Language query engine. The HermiT (version 1.4.3.x) ontology reasoner available in Protégé 5.x implemented the logical and structural consistency of the proposed ontology. To verify the proposed ontology model, we simulated data for 8 test cases. The personalized recommendation messages were generated based on the processing of personal activity data in combination with contextual weather data and personal preference data. The developed ontology was processed using a query engine against a rule base to generate personalized recommendations.</p>
        </sec>
        <sec sec-type="results">
          <title>Results</title>
          <p>The proposed ontology was implemented in automatic activity coaching to generate and deliver meaningful, personalized lifestyle recommendations. The ontology can be visualized using OWLViz and OntoGraf. In addition, we developed an ontology verification module that behaves similar to a rule-based decision support system to analyze the generation and delivery of personalized recommendation messages following a logical structure.</p>
        </sec>
        <sec sec-type="conclusions">
          <title>Conclusions</title>
          <p>This study led to the creation of a meaningful ontology to generate and model personalized recommendation messages for physical activity coaching.</p>
        </sec>
      </abstract>
      <kwd-group>
        <kwd>descriptive logic</kwd>
        <kwd>ontology</kwd>
        <kwd>e-coach</kwd>
        <kwd>reasoning</kwd>
        <kwd>recommendation generation</kwd>
      </kwd-group>
    </article-meta>
  </front>
  <body>
    <sec sec-type="introduction">
      <title>Introduction</title>
      <sec>
        <title>Overview</title>
        <p>Currently, risk factors associated with unhealthy lifestyle have been recognized as the foremost contributors to chronic illness and mortality in developed countries [<xref ref-type="bibr" rid="ref1">1</xref>-<xref ref-type="bibr" rid="ref6">6</xref>]. An e-coach system can guide people and convey the appropriate recommendations in context with sufficient time to prevent and improve living with chronic conditions. It is a set of computerized components that constitute an artificial entity that can observe, reason about, learn from, and predict a user’s behaviors, in context and over time, and engages proactively in an ongoing collaborative conversation with the user to aid planning and promote effective goal striving using persuasive techniques [<xref ref-type="bibr" rid="ref7">7</xref>-<xref ref-type="bibr" rid="ref10">10</xref>]. Motivating people toward a healthy lifestyle has been challenging without appropriate and continuous support and correct intervention planning [<xref ref-type="bibr" rid="ref7">7</xref>-<xref ref-type="bibr" rid="ref10">10</xref>]. Personalized recommendation technology in health care may be helpful to address such challenges. It requires the proper collection of personal health and wellness data and the right recommendation generation and delivery in a meaningful way. Our previous study [<xref ref-type="bibr" rid="ref11">11</xref>] focused on creating a meaningful, context-specific holistic ontology to model raw and unstructured observations of personal health and wellness data collected from heterogeneous sources (eg, sensors, interviews, and questionnaires) with semantic metadata and create a compact and logical abstraction for health risk prediction. However, this comprehensive study concentrated on rule-based recommendation generation and semantic modeling of recommendation messages for physical activity coaching.</p>
      </sec>
      <sec>
        <title>Motivation</title>
        <p>Generation of motivational messages is essential in e-coaching. Motivational messages provide quick information on time in a more natural and meaningful manner to translate behavioral observations into inspiring, easy-to-follow, and achievable actions. Moreover, these messages must be diverse to make the e-coach system more reasonable and reliable. In activity coaching, personalized motivational messages can offer inspiration for a day, week, or month based on the activity goals. It helps to regain motivation when the individual has lost motivation to attain activity goals. The medium of recommendation delivery can be diverse and depends on personal interaction choices (eg, graphical visualization, pop-up textual notification, and audio-visual material). In existing studies, motivational messages have textual forms that follow a static predefined format; therefore, they are difficult to individualize. Existing ontologies do not include model recommendation message intent, components, and contents important to automatically select accurate messages in e-coaching. Personalized recommendation generation for a healthy lifestyle is closely related to personal preferences. Thus, personal preferences can be of 3 types: activity goal setting (eg, nature of goals—direct vs motivational goals and generic vs personalized goals), response type (eg, mode to communicate extended health state, health state prediction, and customized recommendations for activity coaching), and nature of interaction with the e-coach system (eg, mode, frequency, and medium). In this study, we have gone one step ahead to perform semantic (ontological) modeling of preference data and recommendation messages beyond static textual form to describe its characteristics, metadata, and content information.</p>
        <p>The use of ontologies has certain benefits while modeling recommendation messages. It helps to interpret which recommendation message is to be generated using a binary tree-like structure (if-then or if-then-else conditional statement). Interpretability makes identifying the cause-and-effect relationships between data input and data output easy. In ontology, the logical and structural representation of knowledge, hierarchical model structuring (eg, class and subclass model), and inferred knowledge generation with reasoners can solve interpretability problems in decision-making. Furthermore, benefits such as extensibility, flexibility, generality, and decoupling of knowledge help ontology to develop an appropriate solution to model recommendation messages in automatic coaching.</p>
      </sec>
      <sec>
        <title>Aim of the Study</title>
        <p>This study proposes a Web Ontology Language (OWL)-based ontology (OntoRecoModel) to deal with personal preferences and recommendation messages and annotate them with semantic metadata information. The <italic>OntoRecoModel</italic> will not only support a logical representation of data and messages but also encourage rule-based decision-making to generate personalized recommendation messages using SPARQL Protocol and Resource Description Framework (RDF) Query Language (SPARQL) as a verification study against different test cases with simulated data. Moreover, we assessed the performance of the ontology against mean reasoning time and query execution time. In <italic>OntoRecoModel</italic>, we annotated the participant’s data with Semantic Web Rule Language (SWRL) and stored the resultant OWL file in a triple-store format for better readability. The <italic>OntoRecoModel</italic> allows automatic knowledge inferencing and efficient knowledge representation to balance a trade-off between complexity, persuasiveness, and reasoning about formal knowledge. The entire study was divided into the following two sections: (1) <italic>OntoRecoModel</italic> design and implementation for semantic annotation and (2) its verification with simulated data. The main contributions of this study were the following:</p>
        <list list-type="order">
          <list-item>
            <p>Annotation of personal preferences data (activity goal setting, response type, and interaction type) and recommendation messages in the <italic>OntoRecoModel</italic>.</p>
          </list-item>
          <list-item>
            <p>Preparation of semantic rules to execute SPARQL queries for different test cases.</p>
          </list-item>
          <list-item>
            <p>Use of the prepared rules to generate personalized activity recommendations.</p>
          </list-item>
        </list>
        <p>For this set of semantic data, it will be regarded as an assertion of true facts. The main goal of this paper was to trigger a logical rule of shape (A IMPLIES B) in a logically equivalent manner (NOT [A] or B). If some specific variables are inferred to be true, some suggestions should be provided to the participants of the semantic data source.</p>
      </sec>
      <sec>
        <title>Related Work</title>
        <p>This section offers existing knowledge relevant to current research and a qualitative comparison between our proposed ontology and the existing ontologies based on selected categories in <xref ref-type="table" rid="table1">Table 1</xref>. An ontology is a formal description of knowledge as concepts within a domain and their relationships. It uses existing technologies to develop new ideas through conceptual modeling or proof-of-concept studies to solve general real-world or project-specific semantic modeling problems. There are other approaches to knowledge representation that use formal specifications, such as vocabularies, taxonomies, thesaurus, topic maps, and logical models. However, unlike taxonomy or relational database schemas, ontologies express relationships and allow users to bring together or link multiple concepts in novel ways. Furthermore, all the related ontologies are not available in open source. Therefore, it is not straightforward to make quantitative comparisons between different related studies.</p>
        <table-wrap position="float" id="table1">
          <label>Table 1</label>
          <caption>
            <p>A qualitative comparison between our proposed study and the existing studies.</p>
          </caption>
          <table width="1000" cellpadding="5" cellspacing="0" border="1" rules="groups" frame="hsides">
            <col width="160"/>
            <col width="160"/>
            <col width="120"/>
            <col width="140"/>
            <col width="140"/>
            <col width="140"/>
            <col width="140"/>
            <thead>
              <tr valign="top">
                <td>Study</td>
                <td>Used technologies</td>
                <td>Annotation of sensor data</td>
                <td>Annotation of personal and health data or health management data</td>
                <td>Rule-based recommendation generation</td>
                <td>Annotation of preference data</td>
                <td>Annotation of recommendation messages</td>
              </tr>
            </thead>
            <tbody>
              <tr valign="top">
                <td>Our study</td>
                <td>OWL<sup>a</sup>, HermiT, RDF<sup>b</sup>, SPARQL<sup>c</sup>, TDB<sup>d</sup>, OWLViz, OntoGraf, and Java</td>
                <td>Yes</td>
                <td>No</td>
                <td>Yes</td>
                <td>Yes</td>
                <td>Yes</td>
              </tr>
              <tr valign="top">
                <td>Chatterjee et al [<xref ref-type="bibr" rid="ref11">11</xref>]</td>
                <td>OWL, HermiT, RDF, SPARQL, TDB, OWLViz, SSN<sup>e</sup>, SNOMED-CT<sup>f</sup>, OntoGraf, and Java</td>
                <td>Yes</td>
                <td>Yes</td>
                <td>Yes</td>
                <td>No</td>
                <td>No</td>
              </tr>
              <tr valign="top">
                <td>Kim et al [<xref ref-type="bibr" rid="ref12">12</xref>]</td>
                <td>OWL</td>
                <td>No</td>
                <td>Yes</td>
                <td>No</td>
                <td>No</td>
                <td>No</td>
              </tr>
              <tr valign="top">
                <td>Sojic et al [<xref ref-type="bibr" rid="ref13">13</xref>]</td>
                <td>OWL and SWRL<sup>g</sup></td>
                <td>No</td>
                <td>Yes</td>
                <td>No</td>
                <td>No</td>
                <td>No</td>
              </tr>
              <tr valign="top">
                <td>Kim et al [<xref ref-type="bibr" rid="ref14">14</xref>]</td>
                <td>OWL and FaCT++</td>
                <td>No</td>
                <td>Yes</td>
                <td>No</td>
                <td>No</td>
                <td>No</td>
              </tr>
              <tr valign="top">
                <td>Lasierra et al [<xref ref-type="bibr" rid="ref15">15</xref>]</td>
                <td>OWL, RDF, and SPARQL</td>
                <td>No</td>
                <td>Yes</td>
                <td>Yes</td>
                <td>No</td>
                <td>No</td>
              </tr>
              <tr valign="top">
                <td>Yao and Kumar [<xref ref-type="bibr" rid="ref16">16</xref>]</td>
                <td>OWL and SWRL</td>
                <td>No</td>
                <td>Yes</td>
                <td>Yes</td>
                <td>No</td>
                <td>No</td>
              </tr>
              <tr valign="top">
                <td>Chi et al [<xref ref-type="bibr" rid="ref17">17</xref>]</td>
                <td>OWL and SWRL</td>
                <td>No</td>
                <td>Yes</td>
                <td>Yes</td>
                <td>No</td>
                <td>No</td>
              </tr>
              <tr valign="top">
                <td>Rhayem et al [<xref ref-type="bibr" rid="ref18">18</xref>]</td>
                <td>OWL and SWRL</td>
                <td>Yes</td>
                <td>No</td>
                <td>Yes</td>
                <td>No</td>
                <td>No</td>
              </tr>
              <tr valign="top">
                <td>Galopin et al [<xref ref-type="bibr" rid="ref19">19</xref>]</td>
                <td>OWL and SWRL</td>
                <td>No</td>
                <td>Yes</td>
                <td>Yes</td>
                <td>No</td>
                <td>No</td>
              </tr>
              <tr valign="top">
                <td>Sherimon and Krishnan [<xref ref-type="bibr" rid="ref20">20</xref>]</td>
                <td>OWL and SWRL</td>
                <td>No</td>
                <td>Yes</td>
                <td>Yes</td>
                <td>No</td>
                <td>No</td>
              </tr>
              <tr valign="top">
                <td>Hristoskova et al [<xref ref-type="bibr" rid="ref21">21</xref>]</td>
                <td>SOA<sup>h</sup>, Amigo, OWL, and SWRL</td>
                <td>No</td>
                <td>Yes</td>
                <td>Yes</td>
                <td>No</td>
                <td>No</td>
              </tr>
              <tr valign="top">
                <td>Riano et al [<xref ref-type="bibr" rid="ref22">22</xref>]</td>
                <td>OWL</td>
                <td>No</td>
                <td>No</td>
                <td>Yes</td>
                <td>No</td>
                <td>No</td>
              </tr>
              <tr valign="top">
                <td>Jin and Kim [<xref ref-type="bibr" rid="ref23">23</xref>]</td>
                <td>SSN and IETF YANG</td>
                <td>Yes</td>
                <td>No</td>
                <td>No</td>
                <td>No</td>
                <td>No</td>
              </tr>
              <tr valign="top">
                <td>Ganguly et al [<xref ref-type="bibr" rid="ref24">24</xref>]</td>
                <td>OWL</td>
                <td>No</td>
                <td>No</td>
                <td>Yes</td>
                <td>No</td>
                <td>No</td>
              </tr>
              <tr valign="top">
                <td>Bouza et al [<xref ref-type="bibr" rid="ref25">25</xref>]</td>
                <td>OWL, Decision Tree, and Java</td>
                <td>No</td>
                <td>No</td>
                <td>Yes</td>
                <td>No</td>
                <td>No</td>
              </tr>
              <tr valign="top">
                <td>Villalonga et al [<xref ref-type="bibr" rid="ref26">26</xref>]</td>
                <td>OWL and SPARQL</td>
                <td>No</td>
                <td>No</td>
                <td>Yes</td>
                <td>No</td>
                <td>Yes</td>
              </tr>
            </tbody>
          </table>
          <table-wrap-foot>
            <fn id="table1fn1">
              <p><sup>a</sup>OWL: Web Ontology Language.</p>
            </fn>
            <fn id="table1fn2">
              <p><sup>b</sup>RDF: Resource Description Framework.</p>
            </fn>
            <fn id="table1fn3">
              <p><sup>c</sup>SPARQL: SPARQL Protocol and RDF Query Language.</p>
            </fn>
            <fn id="table1fn4">
              <p><sup>d</sup>TDB: tuple database.</p>
            </fn>
            <fn id="table1fn5">
              <p><sup>e</sup>SSN: semantic sensor network.</p>
            </fn>
            <fn id="table1fn6">
              <p><sup>f</sup>SNOMED-CT: Systematized Nomenclature of Medicine–Clinical Terms.</p>
            </fn>
            <fn id="table1fn7">
              <p><sup>g</sup>SWRL: Semantic Web Rule Language.</p>
            </fn>
            <fn id="table1fn8">
              <p><sup>h</sup>SOA: service-oriented architecture.</p>
            </fn>
          </table-wrap-foot>
        </table-wrap>
        <p>Kim et al [<xref ref-type="bibr" rid="ref12">12</xref>] developed an ontology model for obesity management, which realizes spontaneous participation of participants and continuous weight monitoring through the nursing process in the field of mobile devices. The scope of obesity management includes behavioral intervention, dietary advice, and physical activity. Similarly, the study includes evaluation data (BMI, gender, and hip circumference), inferred data to express diagnostic results, evaluation (causes of obesity), success or failure in behavior change, and implementation (education, advice, and intervention). Sojic et al [<xref ref-type="bibr" rid="ref13">13</xref>] used OWL to model a specific ontology in the obesity field to design reasoning models to personalize health status assessments to be age-specific and gender-specific. The ontology helps to classify personal files according to changes in personal behavior or characteristics over time and automatically infer personal health status, which is of great significance for obesity assessment and prevention. They used SWRL to write the ontology rules. Kim et al [<xref ref-type="bibr" rid="ref14">14</xref>] proposed a physical activity ontology model to support the interoperability of physical activity data. The ontology was developed in Protégé (version 4.x), and the FaCT++ reasoner verified its structural consistency. On the basis of the automatic calculation paradigm, Monitoring, Analysis, Planning, and Execution, an automatic ontology-based method was developed by Lasierra et al [<xref ref-type="bibr" rid="ref15">15</xref>] to manage information in the home-based remote monitoring service scenario. Furthermore, they proposed the following three stages [<xref ref-type="bibr" rid="ref27">27</xref>] for ontology-driven home-based personalized care for the patients with chronic illnesses: stage 1—ontology design and implementation, stage 2—the application of ontology to study the personalization problem, and stage 3—software prototype implementation. The proposed ontology was designed in the Protégé-OWL (version 4.0.2) ontology editor using OWL–Description Logic (OWL-DL) language and verified using the FaCT++ reasoner. Ontology development involves data from heterogeneous sources, such as clinical knowledge, data from medical devices, and patient’s contextual data. Yao and Kumar [<xref ref-type="bibr" rid="ref16">16</xref>] proposed a new <italic>flexible workflow based on clinical context</italic> method, which used ontology modeling to incorporate flexible and adaptive clinical pathways into clinical decision support system (CDSS). They developed 18 SWRL rules to explain practical knowledge of heart failure. The model was verified using the Pellet Reasoner plug-in for Protégé 3.4. In addition, they developed a proof-of-concept prototype of the proposed method using the Drools framework. Chi et al [<xref ref-type="bibr" rid="ref17">17</xref>] used OWL and SWRL to construct a dietary consultation system. The knowledge base (KB) involves the interaction of heterogeneous data sources and factors such as patient’s disease stage, physical condition, activity level, food intake, and key nutritional restrictions. Rhayem et al [<xref ref-type="bibr" rid="ref18">18</xref>] proposed an ontology (HealthIoT)–based system for patient monitoring using sensors, radio frequency identification, and actuators. They claim that the data obtained from medically connected devices are huge, and therefore, lack restraint and comprehensibility and are manipulated by other systems and devices. Therefore, they proposed an ontology model that represents connected medical devices and their data according to semantic rules and, then, used the proposed Internet of Things medical insurance system for model evaluation, which supports decision-making after analyzing the patient’s vital signs. Galopin et al [<xref ref-type="bibr" rid="ref19">19</xref>] proposed an ontology-based prototype CDSS to manage patients with multiple chronic diseases in accordance with clinical practice guidelines. They prepared a KB based on the clinical practice guidelines and patient observation data. The KB decision rule is based on the <italic>if-then</italic> rule. Sherimon and Krishnan [<xref ref-type="bibr" rid="ref20">20</xref>] proposed an ontology system (OntoDiabetic) using OWL2 language to support CDSS for patients with cardiovascular disease, diabetic nephropathy, and hypertension to follow clinical guidelines and <italic>if-then</italic> decision rules. Hristoskova et al [<xref ref-type="bibr" rid="ref21">21</xref>] proposed another ontology-driven environmental intelligence (AmI) framework to support personalized medical detection and alert generation based on the analysis of vital signs collected from patients diagnosed with congestive heart failure. The CDSS system can classify individual congestive heart failure risk stages and notify patients through AmI’s reasoning engine. Riano et al [<xref ref-type="bibr" rid="ref22">22</xref>] proposed an ontology-based CDSS to monitor and intervene in patients with chronic diseases to prevent critical situations, such as misdiagnosis, undetected comorbidities, lack of information, unobserved related diseases, or prevention. An eHealth system was designed and implemented by Jin and Kim [<xref ref-type="bibr" rid="ref23">23</xref>] using the IETF YANG ontology based on the semantic sensor network (SSN). This method helped to automatically configure eHealth sensors (responsible for collecting body temperature, blood pressure, electromyography, and galvanic skin response) with the help of information and communication technology and supported querying the sensor network through semantic interoperability for the planned eHealth system. The proposed eHealth system consisted of 3 main components—SSN (eHealth sensor, patient, and URI), internet (eHealth server and KB), and eHealth client (patients and professionals). The proposed semantic model used <italic>YANG to JavaScript Object Notation converter</italic> to convert YANG semantic model data into JavaScript Object Notation semantic model data to achieve semantic interoperability, and then, stored it in a database or KB. Ganguly et al [<xref ref-type="bibr" rid="ref24">24</xref>] proposed an ontology-based model for managing semantic interoperability issues in diabetic diet management. The development of the framework includes dialogue game rules, DSS with KB (rule library and database), dialogue model based on decision-making mechanism, dialogue game grammar, decision-making mechanism, and translation rules. Bouza et al [<xref ref-type="bibr" rid="ref25">25</xref>] proposed a domain ontology-based decision tree algorithm and a reasoner to separate instances with more general features for recommender system (<italic>SemTree</italic>) that outperformed comparable approaches in recommendation generation. Chatterjee et al [<xref ref-type="bibr" rid="ref11">11</xref>] focused on the creation of a meaningful, context-specific ontology (<italic>University of Agder eHealth Ontology [UiAeHo])</italic> to model unintuitive, raw, and unstructured observations of health and wellness data (eg, sensors, interviews, and questionnaires) with semantic metadata and create a compact and logical abstraction for health risk prediction. Villalonga et al [<xref ref-type="bibr" rid="ref26">26</xref>] proposed a holistic ontology model to annotate and classify motivational messages for physical activity coaching.</p>
        <p>Most studies have developed ontologies that use OWL to solve data interoperability and knowledge representation problems. However, integrating personal health and wellness data, sensor observations, preference settings, semantic rules, semantic annotations, clinical guidelines, health risk prediction, and personalized recommendation generation remains as a problem in eHealth. We gathered ideas from existing studies to conceptualize our ontology design and implementation. In our previous study [<xref ref-type="bibr" rid="ref11">11</xref>], we developed <italic>UiAeHo</italic> ontology to annotate personal and person-generated health and wellness data, sensor observations, health status in OWL format, combining SSN and Systematized Nomenclature of Medicine–Clinical Terms. Here, we extended the study to annotate preference settings and activity status and tailored recommendation messages for activity e-coaching. The design and development of <italic>UiAeHo</italic> were focused more on obesity and overweight case studies However, this study focuses strictly on activity coaching and recommendation modeling. In addition, our proposed ontology was verified with semantic rules to generate different categories of recommendation messages for different cases. The high-level graphical representation of the proposed approach has been depicted in <xref rid="figure1" ref-type="fig">Figure 1</xref> to show a distinction between <italic>OntoRecoModel</italic> and <italic>UiAeHo</italic> ontologies. <italic>OntoRecoModel</italic> annotates the following 3 types of data: sensor data (activity and weather), personal preference data, and personalized recommendations. Annotation of the sensor data in <italic>OntoRecoModel</italic> was based on the existing <italic>UiAeHo</italic> ontology following a semantic structure. Sensor data (activity data and contextual weather data) were included in this ontology design to exhibit that our <italic>OntoRecoModel</italic> can generate contextual and personalized recommendations in combination with personal preference data and semantic rules.</p>
        <fig id="figure1" position="float">
          <label>Figure 1</label>
          <caption>
            <p>High-level representation of the proposed approach. SPARQL: SPARQL Protocol and Resource Description Framework Query Language; TDB: tuple database; UiAeHo: University of Agder eHealth Ontology.</p>
          </caption>
          <graphic xlink:href="medinform_v10i6e33847_fig1.png" alt-version="no" mimetype="image" position="float" xlink:type="simple"/>
        </fig>
      </sec>
    </sec>
    <sec sec-type="methods">
      <title>Methods</title>
      <sec>
        <title>Domain Ontology</title>
        <p>Ontology supports flexibility in its design to solve real-world modeling and knowledge representation problems. It is a formal model of a specific domain, with the following essential elements: individuals or objects, classes, attributes, relationships, and axioms. The class diagram of a program written using object-oriented programming [<xref ref-type="bibr" rid="ref28">28</xref>,<xref ref-type="bibr" rid="ref29">29</xref>] visually depicts an ontology. The concept of ontology was created thousands of years ago in the philosophical domain, and it has the design flexibility of using existing ontology [<xref ref-type="bibr" rid="ref29">29</xref>,<xref ref-type="bibr" rid="ref30">30</xref>].</p>
        <p>The open-world assumption knowledge representation style uses OWL, RDF, and RDF schema syntax. It can be optimized using the ontology model, and the consistency of its logic and structure can be verified using the ontology reasoning machine. An ontology О is defined as a tuple Ω=(Ć, R), where Ć is the set of concepts and R is a set of relations. An ontology has a tree-like hierarchical structure (О<sub>h</sub>) with the following properties [<xref ref-type="bibr" rid="ref31">31</xref>,<xref ref-type="bibr" rid="ref32">32</xref>]:</p>
        <list list-type="order">
          <list-item>
            <p>L=levels (О<sub>h</sub>)=total number of levels in the ontology hierarchy, 0≤n≤L, where n <inline-graphic xlink:href="medinform_v10i6e33847_fig8.png" xlink:type="simple" mimetype="image"/> Z<sup>+</sup> and n=0 represent the root node</p>
          </list-item>
          <list-item>
            <p>C<sub>n,j</sub>=a model classifying О at a level n; where, j <inline-graphic xlink:href="medinform_v10i6e33847_fig8.png" xlink:type="simple" mimetype="image"/> (0, 1,....., &#124;C<sub>n</sub>&#124;)</p>
          </list-item>
          <list-item>
            <p>&#124;C&#124;=number of instances classified as class C</p>
          </list-item>
          <list-item>
            <p>E=edge (C<sub>n,j</sub>, C<sub>n-1, k</sub>)=edge between node C<sub>n,j</sub> and its parent node C<sub>n-1, k</sub></p>
          </list-item>
        </list>
      </sec>
      <sec>
        <title>Ontology Design Approach</title>
        <p>An ontology can be designed in 5 ways: inspirational, inductive, synthetic, deductive, and collaborative [<xref ref-type="bibr" rid="ref33">33</xref>]. We used a mixed method in our ontology design after combining the inspirational and deductive approaches. The inspirational approach helped us to identify the need for the ontology design, and the deductive approach focused more on the development of the <italic>OntoRecoModel</italic> model in Protégé. Moreover, the deductive approach helped us to adapt and adjust general principles to develop an anticipatory ontology of personalized activity recommendations as a study case. It includes general concepts that are filtered and refined to personalize specific domain subsets. The overall approaches were distributed in the following phases:</p>
        <list list-type="order">
          <list-item>
            <p>Literature search: we identified the necessary ontology components in healthy lifestyle management through a literature review, as described in the <italic>Related Work</italic> section. This study aimed to integrate ideas from the related ontology development in our proposed work.</p>
          </list-item>
          <list-item>
            <p>Ideation: we discussed with 12 experts in the domain of information and communication technologies with research background in health care to design the concept of the ontology to fit in an activity e-coaching.</p>
          </list-item>
          <list-item>
            <p>Annotation: we designed and developed the <italic>OntoRecoModel</italic> ontology to annotate personal preference data and motivational recommendation messages.</p>
          </list-item>
          <list-item>
            <p>Rule base: we created a rule base for SPARQL query engine for query execution and personalized recommendation message generation (rule-based inference).</p>
          </list-item>
          <list-item>
            <p>Verification: we verified our proposed <italic>OntoRecoModel</italic> ontology using simulated data against different test cases.</p>
          </list-item>
        </list>
        <p>The feasibility study of the proposed <italic>OntoRecoModel</italic> consists of the following steps—(1) designing the ontology to fit in activity e-coaching concept; (2) modeling the ontology in the Protégé open-source platform and reasoning with HermiT reasoner; (3) integrating the concepts, such as annotation of personal preference data and motivational recommendation messages in <italic>OntoRecoModel</italic>; (4) implementing <italic>OntoRecoModel</italic> with logical axioms, declaration axioms, classes, instances, object properties, and data properties; and (5) setting up the rule base for ontology verification with SPARQL queries. We further discussed how interpretation can be associated with rule-based activity recommendation generation.</p>
        <p>The specifications related to this study, as maintained by World Wide Web Consortium, are XML, URI, RDF, Turtle, RDF schema, OWL, SPARQL, and SWRL. The following terms are related to <italic>OntoRecoModel</italic> representation and processing:</p>
        <list list-type="order">
          <list-item>
            <p>Propositional variables (the atomic name of the truth value can be changed from one model to another)</p>
          </list-item>
          <list-item>
            <p>Constants (the only propositional variables are TRUE and FALSE; thus, their truth values cannot be changed)</p>
          </list-item>
          <list-item>
            <p>Operators (a set of logical connectors in each logic)</p>
          </list-item>
        </list>
        <p>Here, we used operators, such as NOT, AND, OR, IMPLIES, EQUIV, and quantifiers (a set of logical quantifiers in a given logic). In this study, we used FORALL as the universal quantifier, EXISTS as the existential quantifier, quantification clause (a set of propositional variables connected by operators and quantifiers), clause (a quantification clause without any quantifier), formulas (a collection of clauses and quantified clauses linked together by logical operators), and process models (a collection of assignments for each propositional variable, so that when simplified, the process will lead to the constant TRUE).</p>
        <p>Different open-access ontology editors are available in the market, such as NeOn Toolkit, Protégé, FOAF editor, TopBraid Composer, WebOnto Ontolingua Server, OntoEdit, WebODE, and Ontosaurus. The editors support the development of OWL-based ontologies. In addition, these editors support reasoning. The reasoner is a crucial component for using OWL ontology [<xref ref-type="bibr" rid="ref11">11</xref>]. It derives new truths about the concepts that are modeled using OWL ontology. All queries on OWL ontology (and its imported closures) can be performed using reasoners [<xref ref-type="bibr" rid="ref11">11</xref>,<xref ref-type="bibr" rid="ref34">34</xref>,<xref ref-type="bibr" rid="ref35">35</xref>]. Therefore, the knowledge in the ontology may not be explicit, and a reasoner is needed to infer the implicit knowledge to obtain the correct query results. If reasoner implementation is needed, the reasoner must be accessed through application programming interface (API). The OWL API includes various interfaces for accessing OWL reasoners. Reasoners can be categorized into 3 groups—OWL-DL, OWL–expression language, and OWL–query language [<xref ref-type="bibr" rid="ref11">11</xref>,<xref ref-type="bibr" rid="ref34">34</xref>-<xref ref-type="bibr" rid="ref42">42</xref>]. This study considered Protégé (version 5.x) as an ontology editor for ontology design and development, OWLViz for ontology visualization, and HermiT (version 1.4.x; ∈OWL-DL) reasoner for validating the ontology structure. In addition, we used an open-source Apache Jena Fuseki server [<xref ref-type="bibr" rid="ref39">39</xref>] for SPARQL processing [<xref ref-type="bibr" rid="ref43">43</xref>,<xref ref-type="bibr" rid="ref44">44</xref>] with a tuple database (TDB). TDB supports Jena APIs [<xref ref-type="bibr" rid="ref45">45</xref>,<xref ref-type="bibr" rid="ref46">46</xref>] and can be used as a stand-alone high-performance RDF storage.</p>
      </sec>
      <sec>
        <title>Ontology Modeling</title>
        <p>Ontology modeling in Protégé can be classified into the following 2 categories: OWL-based and frame-based categories. We have used Protégé-OWL editor to model <italic>OntoRecoModel</italic> following the open KB connectivity protocol using classes, instances (objects), properties (object properties and data properties), and relationships. The steps of <italic>OntoRecoModel</italic> modeling in Protégé are described in <xref ref-type="boxed-text" rid="box1">Textbox 1</xref>.</p>
        <boxed-text id="box1" position="float">
          <title>OntoRecoModel modeling steps in Protégé.</title>
          <p>
            <bold>Step 1</bold>
          </p>
          <p>Creation of a new Web Ontology Language project in Protégé and save it as a Turtle Resource Description Framework (RDF) format (OntoRecoModel.ttl)</p>
          <p>
            <bold>Step 2</bold>
          </p>
          <p>Create named classes under the superclass <italic>owl:Thing,</italic> maintaining consistency</p>
          <list list-type="bullet">
            <list-item>
              <p>Create a group of classes (G=[C<sub>1</sub>, C<sub>2</sub>,......, C<sub>n</sub>])</p>
            </list-item>
            <list-item>
              <p>Define disjoint classes (Cx ∩ Cy=[ø], where Cx and Cy <inline-graphic xlink:href="medinform_v10i6e33847_fig8.png" xlink:type="simple" mimetype="image"/> G)</p>
            </list-item>
            <list-item>
              <p>Define subclasses</p>
            </list-item>
            <list-item>
              <p>Define disjoint subclasses</p>
            </list-item>
          </list>
          <p>
            <bold>Step 3</bold>
          </p>
          <p>Creation of Web Ontology Language properties after identifying classes and their properties</p>
          <list list-type="bullet">
            <list-item>
              <p>Object properties (association between objects)</p>
            </list-item>
            <list-item>
              <p>Data properties (relates objects to XML schema datatype or rdf:literal)</p>
            </list-item>
            <list-item>
              <p>Annotation properties to annotate classes, objects, and properties</p>
            </list-item>
          </list>
          <p>
            <bold>Step 4</bold>
          </p>
          <p>Define nature of the properties</p>
          <list list-type="bullet">
            <list-item>
              <p>Subproperties (A ⊆ B, where A and B are two nonempty sets)</p>
            </list-item>
            <list-item>
              <p>Inverse properties (x×y=I, where x, y<inline-graphic xlink:href="medinform_v10i6e33847_fig8.png" xlink:type="simple" mimetype="image"/>A; I=identity element)</p>
            </list-item>
            <list-item>
              <p>Functional properties (X=A×X, where X is the set of all sequences &#60;a1, a2,..., an&#62; for a1, a2,.., an ⋲ A)</p>
            </list-item>
            <list-item>
              <p>Inverse functional properties (for a function f: X → Y, its inverse f<sup>-1</sup>: Y → X, where X, Y <inline-graphic xlink:href="medinform_v10i6e33847_fig8.png" xlink:type="simple" mimetype="image"/> R)</p>
            </list-item>
            <list-item>
              <p>Transitive properties (<inline-graphic xlink:href="medinform_v10i6e33847_fig9.png" xlink:type="simple" mimetype="image"/>S ⊆ S or if x=y and y=z, then x=z, where x, y, z ⊆ S set)</p>
            </list-item>
            <list-item>
              <p>Symmetric properties (if x=y, then y=x, where x, y ⊆ S set)</p>
            </list-item>
            <list-item>
              <p>Reflexive properties (x=x, where x ⋲ R)</p>
            </list-item>
          </list>
          <p>
            <bold>Step 5</bold>
          </p>
          <p>Addition of existing ontology classes (eg, semantic sensor network ontology classes to annotate sensor observations)</p>
          <p>
            <bold>Step 6</bold>
          </p>
          <p>Define property domain (D) and range (R) for both object properties and data properties as axioms in reasoning</p>
          <p>
            <bold>Step 7</bold>
          </p>
          <p>Define property restrictions</p>
          <list list-type="bullet">
            <list-item>
              <p>Qualifier restrictions (existential and universal)</p>
            </list-item>
            <list-item>
              <p>Cardinality restrictions (≥1)</p>
            </list-item>
            <list-item>
              <p>hasValue restrictions (datatype)</p>
            </list-item>
          </list>
          <p>
            <bold>Step 8</bold>
          </p>
          <p>Ontology processing with reasoner to check structural and logical consistency and compute the inferred ontology class hierarchy</p>
          <list list-type="bullet">
            <list-item>
              <p>Blue color class in inferred hierarchy for reclassification</p>
            </list-item>
            <list-item>
              <p>Red color class in inferred hierarchy for inconsistent class</p>
            </list-item>
          </list>
          <p>
            <bold>Step 9</bold>
          </p>
          <p>Remove inconsistencies from the ontology tree using pruning method</p>
          <p>
            <bold>Step 10</bold>
          </p>
          <p>Query processing with SPARQL Protocol and RDF Query Language and storing the <italic>Terse RDF Triple Language</italic> file into tuple database for persistence</p>
        </boxed-text>
      </sec>
      <sec>
        <title>Ontology Implementation</title>
        <sec>
          <title>Scope</title>
          <p>We have planned to integrate the proposed <italic>OntoRecoModel</italic> model into an automatic activity coaching system for the semantic representation of activity sensor data, weather sensor data, personal preference data, and recommendation messages. The annotation of sensor data was pre-existing, and we used the concept from our previous study [<xref ref-type="bibr" rid="ref11">11</xref>]. Furthermore, we showed a direction to use the proposed ontology model for automatic rule-based tailored activity recommendation generation with SPARQL queries to motivate individuals to maintain a healthy lifestyle. <italic>OntoRecoModel</italic> has gone one step forward to represent motivational recommendation messages beyond the <italic>string</italic> representation. Furthermore, the rule base helped to interpret the logic behind recommendation generation with logical AND and OR operations. We verified the ontology against a few test cases, which consisted of simulated data.</p>
          <p>The targeted activity e-coach system has three modules, as depicted in <xref rid="figure2" ref-type="fig">Figure 2</xref>—(1) data collection and annotation module, (2) health state monitor and prediction module, and (3) recommendation generation module. In the data collection and annotation module, we showed a direction to annotate personal preference data essential for personalized recommendation generation. Health state monitor and prediction models periodically load individual activity data and analyze them using a data-driven machine learning (ML) approach or a rule-driven binary conditional approach. We considered a rule-driven approach for monitoring individual activity data using SPARQL queries. It determines whether a participant is sedentary or active over a day based on the recorded activity data. The annotated query processing results are stored in the database. Then, the personalized recommendation generation module combines the annotated SPARQL query results with the annotated preference data to generate tailored recommendation messages for motivation, which may help individuals to achieve their activity goals.</p>
          <fig id="figure2" position="float">
            <label>Figure 2</label>
            <caption>
              <p>The modules of the e-coach prototype system. OWL: Web Ontology Language; SPARQL: SPARQL Protocol and Resource Description Framework Query Language; TDB: tuple database.</p>
            </caption>
            <graphic xlink:href="medinform_v10i6e33847_fig2.png" alt-version="no" mimetype="image" position="float" xlink:type="simple"/>
          </fig>
        </sec>
        <sec>
          <title>Annotation of Sensor Data</title>
          <p>As shown in our previous study, this study achieved annotation of activity sensor data and contextual weather sensor data using pre-existing SSN ontology [<xref ref-type="bibr" rid="ref11">11</xref>]. We used a similar logic; however, we annotated them more realistically. We examined the recorded activity parameters of different wearable activity sensors, such as Fitbit Versa, MOX2-5, and Garmin, and discovered that the following parameters are essential and common across these activity sensors: sedentary time, low physical activity (LPA) time, medium physical activity (MPA) time, vigorous physical activity (VPA) time, and total number of steps. Therefore, in this ontology, we annotated these activity parameters. Similarly, we analyzed data from different weather APIs, such as AccuWeather, Yr.no, and OpenWeather API. We found that the following observable weather parameters are common across these APIs: city, country, weather code, status, description, temperature, real feel, air pressure, humidity, visibility, and wind speed. Thus, it may help <italic>OntoRecoModel</italic> to be functional, irrespective of the choice of standard activity sensor and weather APIs.</p>
        </sec>
        <sec>
          <title>Annotation of Personal Preference Data</title>
          <p>Personal preferences reflect individual expectations from an e-coach system. We planned to collect personal preference data at the beginning of the individual e-coaching session. We classified preference data into three categories: (1) activity goal settings, (2) response type for coaching, and (3) interaction type. Activity goals were categorized into 2 groups: personalized versus generic and direct versus motivational. The generic goals in activity coaching are the general activity guidelines set by the World Health Organization [<xref ref-type="bibr" rid="ref47">47</xref>]. Personalized activity goals can be of multiple types (eg, weight reduction, staying active, body fat level, and proper sleeping). Direct goals tell the participant to perform direct activities (such as walking 2 km tomorrow).</p>
          <p>In contrast, motivational goals inspire the participants to perform some tasks through persuasion (eg, If you walk 1 km further, you can watch an excellent soccer game). Response type for e-coaching can be either direct (eg, a pop-up message or notification to receive activity progression alert) or indirect (eg, graphical representation of activity progression). Individuals can be encouraged with personalized, evidence-based, and contextual response generation and its purposeful presentation (eg, graphic illustration, selection of colors, contrasts, visual aspects of movements, and menus, which are adjustable with device type). Interaction is an action that occurs owing to the mutual effect of ≥2 objects. The concept of 2-way effects is essential in interaction, not 1-way causal effects. The interaction types can be the mode (eg, style and graph), medium (eg, audio, voice, and text), and frequency (eg, hourly, daily, weekly, and monthly). Notification generation is a subcategory of interaction and may be persistent or nonpersistent.</p>
        </sec>
        <sec>
          <title>Annotation of Recommendation Messages</title>
          <p>The recommender module generates personalized and contextual recommendations based on the prediction status. The recommendations can be direct (eg, pop-up notifications as alerts) or indirect (eg, visual representation). Direct or immediate notifications can contain 2 types of messages: to-do or formal (eg, You need to complete 1500 more steps in the next 2 hours to reach your daily goal) and informal (eg, Good work, keep it up! You have achieved the targeted steps). Therefore, we broke down the recommendation message concepts into intents and components. Intent defines the message’s intention (eg, formal or informal). Message components define time, element (eg, data types in XML schema definition language), action (eg, pop-up and graphical visualization), and subject. An individual can receive &#62;1 meaningful recommendation message based on the one-to-many relationship.</p>
        </sec>
      </sec>
      <sec>
        <title>Ontology Classes and Properties</title>
        <p><xref rid="figure3" ref-type="fig">Figure 3</xref> to 6 describe <italic>OntoRecoModel</italic> with mandatory classes to annotate the sensor, preference, and recommendation data.</p>
        <fig id="figure3" position="float">
          <label>Figure 3</label>
          <caption>
            <p>High-level graphical representation of participant using OntoGraf in Protégé. OWL: Web Ontology Language.</p>
          </caption>
          <graphic xlink:href="medinform_v10i6e33847_fig3.png" alt-version="no" mimetype="image" position="float" xlink:type="simple"/>
        </fig>
        <p>Participant is the subclass of the human class (<xref rid="figure3" ref-type="fig">Figure 3</xref>). They have dedicated role and credentials (objectProperties: hasRole, hasPassword, and hasUniqueUserId) to authorize and authenticate themselves in the system. Participants are adults (both men and women), digitally literate, and clinically fit individuals. They are associated with the data properties such as hasAge, hasDesignation, hasEmail, hasFirstName, hasLastName, hasGender, and hasMobile. Each participant has their health record (hasHealthRecord), such as activity data; status (hasStatus), such as <italic>active</italic> or <italic>inactive</italic>; context information, such as weather status; preferences (hasPreferences); and recommendations (hasReceivedRecommendation).</p>
        <p>Sensor data are ObservableEntity (<xref rid="figure4" ref-type="fig">Figure 4</xref>). Observation value is the subclass of ObservableEntity. ActivityDataValue and ExternalWeatherValue are the subclass of Observation value class. ActivityData and ActivityDataValue are linked to represent individual activity data. ActivityData class is a subclass of ParticipantHealthRecord and has objectProperty—hasBeenCollectedBy to represent associated activity data values (class: ActivityDataValue) as an observable entity. We have planned to collect activity data (such as steps, LPA, MPA, VPA, sleep time, and sedentary bouts) with a wearable MOX2-5 activity sensor. In contrast, contextual data are observable weather-related data (city, country, weather code, status, description, temperature, real feel, air pressure, humidity, visibility, and wind speed), which are planned to be collected through the OpenWeather web interfaces. ContextData class is the subclass of ContextualData class and linked with ExternalWeatherValue to represent contextual weather data. TemporalEntity class represents the time stamp when the observational data have been captured and personalized recommendations have been generated (data property: hasDateTime).</p>
        <p>Recommendation is a broad area, and we considered only activity recommendations in this study. ActivityRecommendation is a subclass of Recommendation class and parent to the MessageIntent and MessageComponent with the following objectProperties: hasMessageIntent and hasMessageComponent. MessageIntent class is the parent to ToDo and Informal classes with the following objectProperties: hasRecoInformal and hasRecoToDo (<xref rid="figure5" ref-type="fig">Figure 5</xref>). MessageComponent is the parent of Time, Element, Action, and Subject classes with the following objectProperties: hasTime, hasElement, hasAction, and hasSubject. Preferences is a subclass of the Qualifier class and related to the Goal, Interaction, and ResponseType (subclasses of the Preference class) with the following objectProperties: hasInteractionType, hasResponseType, and hasGoal. Preference class is a questionnaire-based method to receive participant’s choices on goal setting, response type for e-coaching, and nature of interaction with the e-coach system.</p>
        <p>Preference class has 3 subclasses: ResponseType, Goal, and Interaction. Goal class has 2 subclasses: Daily and Weekly (<xref rid="figure6" ref-type="fig">Figure 6</xref>). Each activity recommendations are either <italic>generic</italic> or <italic>personalized</italic>. Thus, recommendation generation depends on the assessment of the health status of the participants, regarding activity measurement and contextual information. Contextual data help recommend participants to plan indoor or outdoor activities based on external weather conditions. Table S1 in <xref ref-type="supplementary-material" rid="app1">Multimedia Appendix 1</xref> [<xref ref-type="bibr" rid="ref48">48</xref>-<xref ref-type="bibr" rid="ref51">51</xref>] summarizes the set of identified recommendation messages used for the test setup (ontology verification) and prepared based on positive psychology [<xref ref-type="bibr" rid="ref52">52</xref>] and the concept of persuasion [<xref ref-type="bibr" rid="ref48">48</xref>]. Recommendations generated on day <italic>n</italic> will reflect daily activity and contemplate what to perform on the day <italic>n+1</italic> to achieve the weekly goal. Preference data are personalized and customizable. All the necessary data for this study and their nature are summarized in Table S2 in <xref ref-type="supplementary-material" rid="app2">Multimedia Appendix 2</xref>.</p>
        <p>Description logic is the formal knowledge representation of ontology language, which provides a good trade-off between the expressiveness, complexity, and efficiency of knowledge representation and structured knowledge reasoning. We have the following proposition variables and recommended messages with their links to ensure that the paper is fully understood. Now, we need a set of clauses so that specific models can assign these variables to true, which triggers the sending of recommendations. SROIQ Description Logic [<xref ref-type="bibr" rid="ref53">53</xref>] is the logic that provides the formal basis for OWL2 and has been used as the formal logic for reasoning in this study (Table S3 in <xref ref-type="supplementary-material" rid="app3">Multimedia Appendix 3</xref>).</p>
        <fig id="figure4" position="float">
          <label>Figure 4</label>
          <caption>
            <p>High-level graphical representation of observable data using OntoGraf in Protégé.</p>
          </caption>
          <graphic xlink:href="medinform_v10i6e33847_fig4.png" alt-version="no" mimetype="image" position="float" xlink:type="simple"/>
        </fig>
        <fig id="figure5" position="float">
          <label>Figure 5</label>
          <caption>
            <p>High-level graphical representation of recommendation using OntoGraf in Protégé.</p>
          </caption>
          <graphic xlink:href="medinform_v10i6e33847_fig5.png" alt-version="no" mimetype="image" position="float" xlink:type="simple"/>
        </fig>
        <fig id="figure6" position="float">
          <label>Figure 6</label>
          <caption>
            <p>High-level graphical representation of preferences using OntoGraf in Protégé.</p>
          </caption>
          <graphic xlink:href="medinform_v10i6e33847_fig6.png" alt-version="no" mimetype="image" position="float" xlink:type="simple"/>
        </fig>
      </sec>
      <sec>
        <title>Ontology Verification</title>
        <sec>
          <title>Test Cases With Simulated Data</title>
          <p>We considered 8 test cases, as described in Table S4 in <xref ref-type="supplementary-material" rid="app4">Multimedia Appendix 4</xref>, with simulated data for the proposed ontology verification. In the table, all the data are simulated. Therefore, no ethical approval was required. Cases 1 to 4 were associated with goal type—<italic>generic</italic> (World Health Organization standard guidelines to stay active for an entire week). Cases 5 to 8 were associated with goal type—<italic>personalized</italic>. More detailed description of different cases is provided in <xref ref-type="boxed-text" rid="box2">Textbox 2</xref>. The primary objective of the test cases was to check whether the daily step goal and daily sleep goal were achieved. The sedentary time and total time of VPA, MPA, and LPA were evaluated as a part of the secondary goal achievement. Daily goal achievement consisted of both primary objective and secondary objectives.</p>
          <p>For all the test cases, the contextual weather data were considered constant (Table S5 in <xref ref-type="supplementary-material" rid="app5">Multimedia Appendix 5</xref>). These test cases were added to the proposed ontology as individuals. SPARQL query processor engine processed the simulated data against certain test cases.</p>
          <boxed-text id="box2" position="float">
            <title>Different test cases and their description.</title>
            <p>
              <bold>Goal type: <italic>Generic</italic></bold>
            </p>
            <list list-type="bullet">
              <list-item>
                <p>Case 1 (11): Daily step goal and sleep goal are achieved.</p>
              </list-item>
              <list-item>
                <p>Case 2 (10): Daily step goal is achieved; however, sleep goal is not achieved.</p>
              </list-item>
              <list-item>
                <p>Case 3 (01): Daily step goal is not achieved; however, sleep goal is achieved.</p>
              </list-item>
              <list-item>
                <p>Case 4 (00): Daily step goal and sleep goal are not achieved.</p>
              </list-item>
            </list>
            <p>
              <bold>Goal type: <italic>Personalized</italic></bold>
            </p>
            <list list-type="bullet">
              <list-item>
                <p>Case 5 (11): Daily step goal and sleep goal are achieved.</p>
              </list-item>
              <list-item>
                <p>Case 6 (10): Daily step goal is achieved; however, sleep goal is not achieved.</p>
              </list-item>
              <list-item>
                <p>Case 7 (01): Daily step goal is not achieved; however, sleep goal is achieved.</p>
              </list-item>
              <list-item>
                <p>Case 8 (00): Daily step goal and sleep goal are not achieved.</p>
              </list-item>
            </list>
            <p>
              <bold>Note:</bold>
            </p>
            <list list-type="bullet">
              <list-item>
                <p>1 and 0 are two binary numbers and represent an on-off switch.</p>
              </list-item>
              <list-item>
                <p>0 indicates that certain feature is false and 1 indicates that certain feature is true.</p>
              </list-item>
              <list-item>
                <p>Their combination (00, 01, 10, and 11) represents the following 2 combined features: daily step goal and daily sleep goal.</p>
              </list-item>
              <list-item>
                <p>The combination produces a total of 2<sup>n</sup> possible test cases (00, 01, 10, and 11) for each goal type.</p>
              </list-item>
            </list>
          </boxed-text>
        </sec>
        <sec>
          <title>Rule Creation for SPARQL and Rule Execution</title>
          <p>Rules were composed of cause (A) and effect (B) to imply A → B. For each of the conditions mentioned in Table S3 in <xref ref-type="supplementary-material" rid="app3">Multimedia Appendix 3</xref>, the recommendation module performed a SPARQL query every day to determine the type of recommended message to be delivered to each participant, as shown in the Unified Modeling Language sequence diagram (<xref rid="figure7" ref-type="fig">Figure 7</xref>). The execution of each of the predefined semantic rules specified in Table S3 in <xref ref-type="supplementary-material" rid="app3">Multimedia Appendix 3</xref> depended on the performance of the SPARQL queries, and the rules were created according to clinical guidelines [<xref ref-type="bibr" rid="ref48">48</xref>-<xref ref-type="bibr" rid="ref50">50</xref>]. This study subdivided 12 semantic rules into activity-level classification (n=10, 83%), weather classification (n=1, 8%), and satisfiability (n=1, 8%). The added concepts and rules were relatively easy to follow and use.</p>
          <p>Observable and measurable parameters related to the activities and context of the individual participants on the time stamp were obtained based on SPARQL queries at preference-based intervals. The rules 1 to 8 in Table S3 in <xref ref-type="supplementary-material" rid="app3">Multimedia Appendix 3</xref> assigned truth values to variables to ensure consistency. We confirmed with HermiT that the correct recommendation message was triggered for specific situations. However, it was necessary to ensure that no variable combination makes the entire formula unsatisfiable; that is, no model can satisfy the process. We confirmed that only 1 message was triggered at a time. In this study, we had a formal guarantee that 2 <italic>once a day</italic> messages cannot be triggered simultaneously and there cannot be a model output by HermiT every time for every possible variable combination. If we put the different variables used in the first 10 rules (Table S3 in <xref ref-type="supplementary-material" rid="app3">Multimedia Appendix 3</xref>) into the propositional variables (Table S1 in <xref ref-type="supplementary-material" rid="app1">Multimedia Appendix 1</xref>), we will have an exponential number of <italic>possible participants</italic>.</p>
          <p>As 2 messages cannot be triggered simultaneously to meet the exact requirements, we added a rule (rule 11), and the variable used in the proposal starts <italic>once a day</italic>. If rule 11 is false, the entire ruleset (deemed as significant conjunction) will be set to false, and then, there will be no model as output, and we will be able to <italic>debug</italic> our rules if needed. If it is set to true, we will have a formal guarantee that regardless of the true value we put in the rule base, 2 <italic>once a day</italic> messages will not be triggered at the same time.</p>
          <fig id="figure7" position="float">
            <label>Figure 7</label>
            <caption>
              <p>Unified Modeling Language sequence diagram for personalized recommendation generation and delivery. SPARQL: SPARQL Protocol and Resource Description Framework Query Language; TDB: tuple database.</p>
            </caption>
            <graphic xlink:href="medinform_v10i6e33847_fig7.png" alt-version="no" mimetype="image" position="float" xlink:type="simple"/>
          </fig>
        </sec>
      </sec>
      <sec>
        <title>Ethics Approval</title>
        <p>We have used simulated data for this study. Therefore, participants’ data have not been recorded or disclosed.</p>
      </sec>
    </sec>
    <sec sec-type="results">
      <title>Results</title>
      <p>An e-coach system can use the messages presented in this study (Table S1 in <xref ref-type="supplementary-material" rid="app1">Multimedia Appendix 1</xref>) to improve individual activities with proper goal management. Therefore, the e-coach system must access these messages stored in a KB during tailored recommendation generation. Both the asserted and inferred knowledge obtained through the reasoning method will be helpful to determine the most appropriate message.</p>
      <p>The TDB database, as shown in <xref rid="figure7" ref-type="fig">Figure 7</xref>, was used as a KB in this study. The test used to verify the performance and reliability of the proposed <italic>OntoRecoModel</italic> ontology included SPARQL queries and a rule base. In ontology verification, we generated personalized and contextual activity recommendations according to the semantic rules to improve the individual’s physical activity to meet their activity goals. We executed all the semantic rules described in Table S3 in <xref ref-type="supplementary-material" rid="app3">Multimedia Appendix 3</xref> and used the Jena ARQ engine to run relevant SPARQL queries on the simulated data for the 8 test cases described in Table S4 in <xref ref-type="supplementary-material" rid="app4">Multimedia Appendix 4</xref>. This helped to determine the type of recommendation message that would be generated, and we have presented our findings (rule-based recommendation generation for different cases) in <xref ref-type="table" rid="table2">Table 2</xref>. Several individual SPARQL queries are provided in Textbox S1 in <xref ref-type="supplementary-material" rid="app6">Multimedia Appendix 6</xref> as examples, and their results need to be combined to generate personalized recommendations to meet the e-coaching requirements. We achieved 100% precision in executing SPARQL queries to retrieve the necessary data.</p>
      <p><xref ref-type="table" rid="table2">Table 2</xref> shows that participants can receive multiple motivational recommendation messages under ToDo and informal categories. The purpose of the e-coaching is to motivate participants (with motivational recommendation messages) for activities on day <italic>n+1</italic> based on the activity progression on day <italic>n</italic>, so that they can meet their weekly activity goals (<italic>generic</italic> or <italic>personalized</italic>) and maintain a healthy lifestyle. Proposition variable A-15 and A-16 (Table S1 in <xref ref-type="supplementary-material" rid="app1">Multimedia Appendix 1</xref>) were the determinant of the weekly goal achievement and the delivery of the corresponding recommendation messages.</p>
      <table-wrap position="float" id="table2">
        <label>Table 2</label>
        <caption>
          <p>Recommendation generation for different cases on day n for day n+1 (n&#62;0).</p>
        </caption>
        <table width="1000" cellpadding="5" cellspacing="0" border="1" rules="groups" frame="hsides">
          <col width="120"/>
          <col width="280"/>
          <col width="330"/>
          <col width="270"/>
          <thead>
            <tr valign="top">
              <td>Case</td>
              <td>Activity status on day <italic>n</italic></td>
              <td colspan="2">Recommendations for day <italic>n+1</italic></td>
            </tr>
            <tr valign="top">
              <td>
                <break/>
              </td>
              <td>
                <break/>
              </td>
              <td>ToDo</td>
              <td>Informal</td>
            </tr>
          </thead>
          <tbody>
            <tr valign="top">
              <td>1</td>
              <td>Goal achieved</td>
              <td>A<sup>a</sup>-3, A-6, A-8, A-10, and A-12</td>
              <td>A-13 and C<sup>b</sup>-1</td>
            </tr>
            <tr valign="top">
              <td>2</td>
              <td>Goal partially achieved</td>
              <td>A-2, A-5, A-8, A-10, and A-11</td>
              <td>A-14 and C-1</td>
            </tr>
            <tr valign="top">
              <td>3</td>
              <td>Goal partially achieved</td>
              <td>A-1, A-5, A-7, A-9, and A-12</td>
              <td>A-14 and C-1</td>
            </tr>
            <tr valign="top">
              <td>4</td>
              <td>Goal not achieved</td>
              <td>A-1, A-5, A-7, A-9, and A-11</td>
              <td>A-14 and C-1</td>
            </tr>
            <tr valign="top">
              <td>5</td>
              <td>Goal achieved</td>
              <td>A-4, A-6, A-8, A-10, and A-12</td>
              <td>A-13 and C-1</td>
            </tr>
            <tr valign="top">
              <td>6</td>
              <td>Goal partially achieved</td>
              <td>A-4, A-5, A-8, A-9, and A-11</td>
              <td>A-14 and C-1</td>
            </tr>
            <tr valign="top">
              <td>7</td>
              <td>Goal partially achieved</td>
              <td>A-3, A-5, A-7, A-9, and A-12</td>
              <td>A-14 and C-1</td>
            </tr>
            <tr valign="top">
              <td>8</td>
              <td>Goal not achieved</td>
              <td>A-3, A-5, A-7, A-9, and A-11</td>
              <td>A-14 and C-1</td>
            </tr>
          </tbody>
        </table>
        <table-wrap-foot>
          <fn id="table2fn1">
            <p><sup>a</sup>A: activity recommendations.</p>
          </fn>
          <fn id="table2fn2">
            <p><sup>b</sup>C: contextual recommendations.</p>
          </fn>
        </table-wrap-foot>
      </table-wrap>
    </sec>
    <sec sec-type="discussion">
      <title>Discussion</title>
      <sec>
        <title>Principal Findings</title>
        <p>The recommendation generation module used SPARQL queries and a rule base to generate personalized and contextual activity recommendations. There is no <italic>false positive</italic> situation based on the proposed ontology. According to the test cases in Table S4 in <xref ref-type="supplementary-material" rid="app4">Multimedia Appendix 4</xref>, case 1 and case 5 achieved the daily activity goal; case 2, case 3, case 6, and case 7 achieved partial daily activity goal; and case 4 and case 8 ultimately failed to attain the daily activity goal. After combining the results of SPARQL queries with semantic rules, the related recommendation messages were updated, as shown in <xref ref-type="table" rid="table2">Table 2</xref>. The average execution time for all the SPARQL queries was between 0.1 and 0.3 seconds. The semantic rules described in Table S3 in <xref ref-type="supplementary-material" rid="app3">Multimedia Appendix 3</xref> represent the logic behind personalized recommendation message generation. The rule-based binary reasoning (if → 1, else → 0) helps to interpret the reason behind the delivery of a personal recommendation message.</p>
        <p>The reasoning time of the proposed ontology was measured against the following reasoners available in Protégé: HermiT, Pellet, FaCT++, RacerPro, and KAON2; the corresponding processing times are shown in <xref ref-type="table" rid="table3">Table 3</xref>. The HermiT reasoner performed the best without reporting any inconsistencies.</p>
        <table-wrap position="float" id="table3">
          <label>Table 3</label>
          <caption>
            <p>Comparative performance analysis of different reasoners available in Protégé.</p>
          </caption>
          <table width="1000" cellpadding="5" cellspacing="0" border="1" rules="groups" frame="hsides">
            <col width="500"/>
            <col width="500"/>
            <thead>
              <tr valign="top">
                <td>Reasoner</td>
                <td>Approximate reasoning time (seconds)</td>
              </tr>
            </thead>
            <tbody>
              <tr valign="top">
                <td>HermiT</td>
                <td>2-3</td>
              </tr>
              <tr valign="top">
                <td>Pellet</td>
                <td>4-5</td>
              </tr>
              <tr valign="top">
                <td>FaCT++</td>
                <td>5-6</td>
              </tr>
              <tr valign="top">
                <td>RacerPro</td>
                <td>4-5</td>
              </tr>
              <tr valign="top">
                <td>KAON2</td>
                <td>5-6</td>
              </tr>
            </tbody>
          </table>
        </table-wrap>
        <p>The reading time after loading the ontology into the Jena workspace was approximately 1 to 2.5 seconds, with the <italic>OWL_MEM_MICRO_RULE_INF</italic> ontology specification (OWL full) in the <italic>Terse RDF Triple Language</italic> format, <italic>in-memory</italic> storage, and <italic>optimized rule-based reasoner OWL rules</italic>. Then, we used the Jena framework to query the ontology classes, predicates, subjects, and individuals in &#60;1, &#60;0.3, &#60;0.4, and &#60;2 seconds, respectively. Each ontology model (complete RDF diagram) was associated with a document manager (default global document manager: <italic>OntDocumentManager</italic>) to assist in processing ontology documents. All classes that represent the value of the ontology in the ontology API had <italic>OntResource</italic> as a general superclass with attributes (version information, comment, label, seeAlso, isDefinedBy, sameAs, and differentFrom) and methods (add, set, list, get, update, and delete). We implemented the RDF interface provided by Jena to maintain the modeled ontology and its instances in the TDB and load them back for further processing. Jena Fuseki was tightly integrated with TDB to provide a robust transactional persistent storage layer.</p>
      </sec>
      <sec>
        <title>Limitations and Future Scope</title>
        <p>As explained in this study, we conducted the overall experiment on simulated data in a modeled e-coaching environment. This concept must be tested after integrating with a real-time activity e-coaching system, in which actual participants will be involved. Here, the personalized recommendation generation is rule-driven and straightforward. In <xref rid="figure2" ref-type="fig">Figure 2</xref>, the health state monitor and prediction module can be upgraded using data-driven ML approaches, followed by annotation of prediction results into the ontology. However, it is the future scope of this study.</p>
        <p>In our conceptualized activity e-coaching, the recommendation generation module successfully searched the KB of motivational recommendation messages based on the rules in addition to the SPARQL results. The recommendation messages can be further personalized based on human behavior, liking for sports (eg, soccer), and the concept of reward bank. The components of the activity-related message can be further divided into indoor, outdoor, morning, afternoon, evening, and night activities. If a person has a dog and the e-coach system is aware of it, its recommendation generation module may suggest some activity recommendations involving the dog.</p>
        <p><xref ref-type="table" rid="table2">Table 2</xref> shows that a participant can receive &#62;1 recommendation message. It may lead to a message overloading problem. In future research, the recommendation process can be automated with ML algorithms (eg, time series and regression model) to select an optimal set of recommendations from feasible recommendations. The scope of the proposed ontology can be enhanced by conducting a study on a cluster of trials.</p>
      </sec>
      <sec>
        <title>Conclusions</title>
        <p>This study created the <italic>OntoRecoModel</italic> ontology to generate and model personalized recommendation messages for physical activity coaching. The proposed ontology not only semantically annotates recommendation messages, their intention, and components but also models personal preference data, individual activity data, and contextual weather information (required for personalized recommendation generation). Moreover, we successfully verified the use of the proposed ontology in rule-based recommendation generation using the SPARQL query engine. This study also showed a direction to categorize recommendation messages according to the defined ontology rules. Furthermore, reasoning has helped to organize the recommendation messages into multiple aspects. The recommendation message categorization, their semantic annotation, and the ontological SPARQL queries enable the recommendation generation module to generate them based on preferences, activity data, and contextual weather data.</p>
        <p>The <italic>OntoRecoModel</italic> ontology uses the OWL-based web language to represent the collected data in the RDF triple storage format. The performance of the proposed ontology was evaluated using simulated data from 8 test cases. The structure and logical consistency of the proposed ontology were evaluated using the HermiT reasoner. In future studies, we will recruit actual participants following the inclusion and exclusion criteria to replicate the entire test scenario and assess the effectiveness of the recommendation generation plan for goal evaluation.</p>
      </sec>
    </sec>
  </body>
  <back>
    <app-group>
      <supplementary-material id="app1">
        <label>Multimedia Appendix 1</label>
        <p>Propositional variables and corresponding recommendation messages.</p>
        <media xlink:href="medinform_v10i6e33847_app1.docx" xlink:title="DOCX File , 17 KB"/>
      </supplementary-material>
      <supplementary-material id="app2">
        <label>Multimedia Appendix 2</label>
        <p>Different data types used in this study and their nature.</p>
        <media xlink:href="medinform_v10i6e33847_app2.docx" xlink:title="DOCX File , 15 KB"/>
      </supplementary-material>
      <supplementary-material id="app3">
        <label>Multimedia Appendix 3</label>
        <p>In-context recommendation conditions and corresponding rules (rule base) for test setup.</p>
        <media xlink:href="medinform_v10i6e33847_app3.docx" xlink:title="DOCX File , 16 KB"/>
      </supplementary-material>
      <supplementary-material id="app4">
        <label>Multimedia Appendix 4</label>
        <p>Description of the test cases.</p>
        <media xlink:href="medinform_v10i6e33847_app4.docx" xlink:title="DOCX File , 16 KB"/>
      </supplementary-material>
      <supplementary-material id="app5">
        <label>Multimedia Appendix 5</label>
        <p>Description of the contextual weather data.</p>
        <media xlink:href="medinform_v10i6e33847_app5.docx" xlink:title="DOCX File , 15 KB"/>
      </supplementary-material>
      <supplementary-material id="app6">
        <label>Multimedia Appendix 6</label>
        <p>Selected list of SPARQL Protocol and Resource Description Framework Query Language queries used in this study.</p>
        <media xlink:href="medinform_v10i6e33847_app6.docx" xlink:title="DOCX File , 16 KB"/>
      </supplementary-material>
    </app-group>
    <glossary>
      <title>Abbreviations</title>
      <def-list>
        <def-item>
          <term id="abb1">API</term>
          <def>
            <p>application programming interface</p>
          </def>
        </def-item>
        <def-item>
          <term id="abb2">CDSS</term>
          <def>
            <p>clinical decision support system</p>
          </def>
        </def-item>
        <def-item>
          <term id="abb3">KB</term>
          <def>
            <p>knowledge base</p>
          </def>
        </def-item>
        <def-item>
          <term id="abb4">LPA</term>
          <def>
            <p>low physical activity</p>
          </def>
        </def-item>
        <def-item>
          <term id="abb5">ML</term>
          <def>
            <p>machine learning</p>
          </def>
        </def-item>
        <def-item>
          <term id="abb6">MPA</term>
          <def>
            <p>medium physical activity</p>
          </def>
        </def-item>
        <def-item>
          <term id="abb7">OWL</term>
          <def>
            <p>Web Ontology Language</p>
          </def>
        </def-item>
        <def-item>
          <term id="abb8">OWL-DL</term>
          <def>
            <p>Web Ontology Language–Description Logic</p>
          </def>
        </def-item>
        <def-item>
          <term id="abb9">RDF</term>
          <def>
            <p>Resource Description Framework</p>
          </def>
        </def-item>
        <def-item>
          <term id="abb10">SPARQL</term>
          <def>
            <p>SPARQL Protocol and Resource Description Framework Query Language</p>
          </def>
        </def-item>
        <def-item>
          <term id="abb11">SSN</term>
          <def>
            <p>semantic sensor network</p>
          </def>
        </def-item>
        <def-item>
          <term id="abb12">SWRL</term>
          <def>
            <p>Semantic Web Rule Language</p>
          </def>
        </def-item>
        <def-item>
          <term id="abb13">TDB</term>
          <def>
            <p>tuple database</p>
          </def>
        </def-item>
        <def-item>
          <term id="abb14">UiAeHo</term>
          <def>
            <p>University of Agder eHealth Ontology</p>
          </def>
        </def-item>
        <def-item>
          <term id="abb15">VPA</term>
          <def>
            <p>vigorous physical activity</p>
          </def>
        </def-item>
      </def-list>
    </glossary>
    <ack>
      <p>The authors acknowledge the funding and infrastructure obtained from the University of Agder, Center for e-Health, Norway, to conduct this study.</p>
    </ack>
    <fn-group>
      <fn fn-type="con">
        <p>AC contributed to conceptualization, formal analysis, investigation, methodology, obtaining resources, and writing the original draft. AP was involved in funding acquisition, reviewing, and supervision. All authors read and agreed to the published version of the manuscript.</p>
      </fn>
      <fn fn-type="conflict">
        <p>None declared.</p>
      </fn>
    </fn-group>
    <ref-list>
      <ref id="ref1">
        <label>1</label>
        <nlm-citation citation-type="journal">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Chatterjee</surname>
              <given-names>A</given-names>
            </name>
            <name name-style="western">
              <surname>Gerdes</surname>
              <given-names>MW</given-names>
            </name>
            <name name-style="western">
              <surname>Martinez</surname>
              <given-names>SG</given-names>
            </name>
          </person-group>
          <article-title>Identification of risk factors associated with obesity and overweight-a machine learning overview</article-title>
          <source>Sensors (Basel)</source>
          <year>2020</year>
          <month>05</month>
          <day>11</day>
          <volume>20</volume>
          <issue>9</issue>
          <fpage>2734</fpage>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://www.mdpi.com/resolver?pii=s20092734"/>
          </comment>
          <pub-id pub-id-type="doi">10.3390/s20092734</pub-id>
          <pub-id pub-id-type="medline">32403349</pub-id>
          <pub-id pub-id-type="pii">s20092734</pub-id>
          <pub-id pub-id-type="pmcid">PMC7248873</pub-id>
        </nlm-citation>
      </ref>
      <ref id="ref2">
        <label>2</label>
        <nlm-citation citation-type="confproc">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Chatterjee</surname>
              <given-names>A</given-names>
            </name>
            <name name-style="western">
              <surname>Gerdes</surname>
              <given-names>M</given-names>
            </name>
            <name name-style="western">
              <surname>Martinez</surname>
              <given-names>S</given-names>
            </name>
          </person-group>
          <article-title>eHealth initiatives for the promotion of healthy lifestyle and allied implementation difficulties</article-title>
          <source>Proceedings of the 2019 International Conference on Wireless and Mobile Computing, Networking and Communications (WiMob)</source>
          <year>2019</year>
          <conf-name>2019 International Conference on Wireless and Mobile Computing, Networking and Communications (WiMob)</conf-name>
          <conf-date>Oct 21-23, 2019</conf-date>
          <conf-loc>Barcelona, Spain</conf-loc>
          <pub-id pub-id-type="doi">10.1109/wimob.2019.8923324</pub-id>
        </nlm-citation>
      </ref>
      <ref id="ref3">
        <label>3</label>
        <nlm-citation citation-type="journal">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Wagner</surname>
              <given-names>K</given-names>
            </name>
            <name name-style="western">
              <surname>Brath</surname>
              <given-names>H</given-names>
            </name>
          </person-group>
          <article-title>A global view on the development of non communicable diseases</article-title>
          <source>Prev Med</source>
          <year>2012</year>
          <month>05</month>
          <volume>54 Suppl</volume>
          <fpage>S38</fpage>
          <lpage>41</lpage>
          <pub-id pub-id-type="doi">10.1016/j.ypmed.2011.11.012</pub-id>
          <pub-id pub-id-type="medline">22178469</pub-id>
          <pub-id pub-id-type="pii">S0091-7435(11)00475-0</pub-id>
        </nlm-citation>
      </ref>
      <ref id="ref4">
        <label>4</label>
        <nlm-citation citation-type="web">
          <article-title>Noncommunicable diseases</article-title>
          <source>World Health Organization</source>
          <access-date>2022-02-24</access-date>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://www.who.int/news-room/fact-sheets/detail/noncommunicable-diseases">https://www.who.int/news-room/fact-sheets/detail/noncommunicable-diseases</ext-link>
          </comment>
        </nlm-citation>
      </ref>
      <ref id="ref5">
        <label>5</label>
        <nlm-citation citation-type="web">
          <article-title>Obesity and overweight</article-title>
          <source>World Health Organization</source>
          <access-date>2022-02-24</access-date>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://www.who.int/news-room/fact-sheets/detail/obesity-and-overweight">https://www.who.int/news-room/fact-sheets/detail/obesity-and-overweight</ext-link>
          </comment>
        </nlm-citation>
      </ref>
      <ref id="ref6">
        <label>6</label>
        <nlm-citation citation-type="journal">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Chatterjee</surname>
              <given-names>A</given-names>
            </name>
            <name name-style="western">
              <surname>Prinz</surname>
              <given-names>A</given-names>
            </name>
            <name name-style="western">
              <surname>Gerdes</surname>
              <given-names>M</given-names>
            </name>
            <name name-style="western">
              <surname>Martinez</surname>
              <given-names>S</given-names>
            </name>
          </person-group>
          <article-title>Digital interventions on healthy lifestyle management: systematic review</article-title>
          <source>J Med Internet Res</source>
          <year>2021</year>
          <month>11</month>
          <day>17</day>
          <volume>23</volume>
          <issue>11</issue>
          <fpage>e26931</fpage>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://www.jmir.org/2021/11/e26931/"/>
          </comment>
          <pub-id pub-id-type="doi">10.2196/26931</pub-id>
          <pub-id pub-id-type="medline">34787575</pub-id>
          <pub-id pub-id-type="pii">v23i11e26931</pub-id>
          <pub-id pub-id-type="pmcid">PMC8663673</pub-id>
        </nlm-citation>
      </ref>
      <ref id="ref7">
        <label>7</label>
        <nlm-citation citation-type="confproc">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Gerdes</surname>
              <given-names>M</given-names>
            </name>
            <name name-style="western">
              <surname>Martinez</surname>
              <given-names>S</given-names>
            </name>
            <name name-style="western">
              <surname>Tjondronegoro</surname>
              <given-names>D</given-names>
            </name>
          </person-group>
          <article-title>Conceptualization of a personalized ecoach for wellness promotion</article-title>
          <source>Proceedings of the 11th EAI International Conference on Pervasive Computing Technologies for Healthcare</source>
          <year>2017</year>
          <conf-name>PervasiveHealth '17: 11th EAI International Conference on Pervasive Computing Technologies for Healthcare</conf-name>
          <conf-date>May 23 - 26, 2017</conf-date>
          <conf-loc>Barcelona Spain</conf-loc>
          <pub-id pub-id-type="doi">10.1145/3154862.3154930</pub-id>
        </nlm-citation>
      </ref>
      <ref id="ref8">
        <label>8</label>
        <nlm-citation citation-type="confproc">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Rutjes</surname>
              <given-names>H</given-names>
            </name>
            <name name-style="western">
              <surname>Willemsen</surname>
              <given-names>M</given-names>
            </name>
            <name name-style="western">
              <surname>IJsselsteijn</surname>
              <given-names>W</given-names>
            </name>
          </person-group>
          <article-title>Understanding effective coaching on healthy lifestyle by combining theory-and data-driven approaches</article-title>
          <source>Proceedings of the Personalization in Persuasive Technology Workshop, Persuasive Technology 2016</source>
          <year>2016</year>
          <conf-name>Personalization in Persuasive Technology Workshop, Persuasive Technology 2016</conf-name>
          <conf-date>Apr 5, 2016</conf-date>
          <conf-loc>Salzburg, Austria</conf-loc>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="http://ceur-ws.org/Vol-1582/13Rutjes.pdf"/>
          </comment>
        </nlm-citation>
      </ref>
      <ref id="ref9">
        <label>9</label>
        <nlm-citation citation-type="journal">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Dijkhuis</surname>
              <given-names>TB</given-names>
            </name>
            <name name-style="western">
              <surname>Blaauw</surname>
              <given-names>FJ</given-names>
            </name>
            <name name-style="western">
              <surname>van Ittersum</surname>
              <given-names>MW</given-names>
            </name>
            <name name-style="western">
              <surname>Velthuijsen</surname>
              <given-names>H</given-names>
            </name>
            <name name-style="western">
              <surname>Aiello</surname>
              <given-names>M</given-names>
            </name>
          </person-group>
          <article-title>Personalized physical activity coaching: a machine learning approach</article-title>
          <source>Sensors (Basel)</source>
          <year>2018</year>
          <month>03</month>
          <day>19</day>
          <volume>18</volume>
          <issue>2</issue>
          <fpage>623</fpage>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://www.mdpi.com/resolver?pii=s18020623"/>
          </comment>
          <pub-id pub-id-type="doi">10.3390/s18020623</pub-id>
          <pub-id pub-id-type="medline">29463052</pub-id>
          <pub-id pub-id-type="pii">s18020623</pub-id>
          <pub-id pub-id-type="pmcid">PMC5856112</pub-id>
        </nlm-citation>
      </ref>
      <ref id="ref10">
        <label>10</label>
        <nlm-citation citation-type="journal">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Chatterjee</surname>
              <given-names>A</given-names>
            </name>
            <name name-style="western">
              <surname>Gerdes</surname>
              <given-names>M</given-names>
            </name>
            <name name-style="western">
              <surname>Prinz</surname>
              <given-names>A</given-names>
            </name>
            <name name-style="western">
              <surname>Martinez</surname>
              <given-names>S</given-names>
            </name>
          </person-group>
          <article-title>Human coaching methodologies for automatic electronic coaching (eCoaching) as behavioral interventions with information and communication technology: systematic review</article-title>
          <source>J Med Internet Res</source>
          <year>2021</year>
          <month>03</month>
          <day>24</day>
          <volume>23</volume>
          <issue>3</issue>
          <fpage>e23533</fpage>
          <pub-id pub-id-type="doi">10.2196/23533</pub-id>
          <pub-id pub-id-type="medline">33759793</pub-id>
          <pub-id pub-id-type="pii">v23i3e23533</pub-id>
          <pub-id pub-id-type="pmcid">PMC8074867</pub-id>
        </nlm-citation>
      </ref>
      <ref id="ref11">
        <label>11</label>
        <nlm-citation citation-type="journal">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Chatterjee</surname>
              <given-names>A</given-names>
            </name>
            <name name-style="western">
              <surname>Prinz</surname>
              <given-names>A</given-names>
            </name>
            <name name-style="western">
              <surname>Gerdes</surname>
              <given-names>M</given-names>
            </name>
            <name name-style="western">
              <surname>Martinez</surname>
              <given-names>S</given-names>
            </name>
          </person-group>
          <article-title>An automatic ontology-based approach to support logical representation of observable and measurable data for healthy lifestyle management: proof-of-concept study</article-title>
          <source>J Med Internet Res</source>
          <year>2021</year>
          <month>04</month>
          <day>09</day>
          <volume>23</volume>
          <issue>4</issue>
          <fpage>e24656</fpage>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://www.jmir.org/2021/4/e24656/"/>
          </comment>
          <pub-id pub-id-type="doi">10.2196/24656</pub-id>
          <pub-id pub-id-type="medline">33835031</pub-id>
          <pub-id pub-id-type="pii">v23i4e24656</pub-id>
          <pub-id pub-id-type="pmcid">PMC8065560</pub-id>
        </nlm-citation>
      </ref>
      <ref id="ref12">
        <label>12</label>
        <nlm-citation citation-type="journal">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Kim</surname>
              <given-names>H</given-names>
            </name>
            <name name-style="western">
              <surname>Park</surname>
              <given-names>H</given-names>
            </name>
            <name name-style="western">
              <surname>Min</surname>
              <given-names>YH</given-names>
            </name>
            <name name-style="western">
              <surname>Jeon</surname>
              <given-names>E</given-names>
            </name>
          </person-group>
          <article-title>Development of an obesity management ontology based on the nursing process for the mobile-device domain</article-title>
          <source>J Med Internet Res</source>
          <year>2013</year>
          <month>07</month>
          <day>28</day>
          <volume>15</volume>
          <issue>6</issue>
          <fpage>e130</fpage>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://www.jmir.org/2013/6/e130/"/>
          </comment>
          <pub-id pub-id-type="doi">10.2196/jmir.2512</pub-id>
          <pub-id pub-id-type="medline">23811542</pub-id>
          <pub-id pub-id-type="pii">v15i6e130</pub-id>
          <pub-id pub-id-type="pmcid">PMC3713932</pub-id>
        </nlm-citation>
      </ref>
      <ref id="ref13">
        <label>13</label>
        <nlm-citation citation-type="journal">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Sojic</surname>
              <given-names>A</given-names>
            </name>
            <name name-style="western">
              <surname>Terkaj</surname>
              <given-names>W</given-names>
            </name>
            <name name-style="western">
              <surname>Contini</surname>
              <given-names>G</given-names>
            </name>
            <name name-style="western">
              <surname>Sacco</surname>
              <given-names>M</given-names>
            </name>
          </person-group>
          <article-title>Modularising ontology and designing inference patterns to personalise health condition assessment: the case of obesity</article-title>
          <source>J Biomed Semantics</source>
          <year>2016</year>
          <month>05</month>
          <day>04</day>
          <volume>7</volume>
          <issue>1</issue>
          <fpage>12</fpage>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://jbiomedsem.biomedcentral.com/articles/10.1186/s13326-016-0049-1"/>
          </comment>
          <pub-id pub-id-type="doi">10.1186/s13326-016-0049-1</pub-id>
          <pub-id pub-id-type="medline">29764473</pub-id>
          <pub-id pub-id-type="pii">10.1186/s13326-016-0049-1</pub-id>
          <pub-id pub-id-type="pmcid">PMC5143447</pub-id>
        </nlm-citation>
      </ref>
      <ref id="ref14">
        <label>14</label>
        <nlm-citation citation-type="journal">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Kim</surname>
              <given-names>H</given-names>
            </name>
            <name name-style="western">
              <surname>Mentzer</surname>
              <given-names>J</given-names>
            </name>
            <name name-style="western">
              <surname>Taira</surname>
              <given-names>R</given-names>
            </name>
          </person-group>
          <article-title>Developing a physical activity ontology to support the interoperability of physical activity data</article-title>
          <source>J Med Internet Res</source>
          <year>2019</year>
          <month>04</month>
          <day>23</day>
          <volume>21</volume>
          <issue>4</issue>
          <fpage>e12776</fpage>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://www.jmir.org/2019/4/e12776/"/>
          </comment>
          <pub-id pub-id-type="doi">10.2196/12776</pub-id>
          <pub-id pub-id-type="medline">31012864</pub-id>
          <pub-id pub-id-type="pii">v21i4e12776</pub-id>
          <pub-id pub-id-type="pmcid">PMC6658272</pub-id>
        </nlm-citation>
      </ref>
      <ref id="ref15">
        <label>15</label>
        <nlm-citation citation-type="journal">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Lasierra</surname>
              <given-names>N</given-names>
            </name>
            <name name-style="western">
              <surname>Alesanco</surname>
              <given-names>A</given-names>
            </name>
            <name name-style="western">
              <surname>O'Sullivan</surname>
              <given-names>D</given-names>
            </name>
            <name name-style="western">
              <surname>García</surname>
              <given-names>J</given-names>
            </name>
          </person-group>
          <article-title>An autonomic ontology-based approach to manage information in home-based scenarios: from theory to practice</article-title>
          <source>Data Knowl Eng</source>
          <year>2013</year>
          <month>09</month>
          <volume>87</volume>
          <fpage>185</fpage>
          <lpage>205</lpage>
          <pub-id pub-id-type="doi">10.1016/j.datak.2013.06.004</pub-id>
        </nlm-citation>
      </ref>
      <ref id="ref16">
        <label>16</label>
        <nlm-citation citation-type="journal">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Yao</surname>
              <given-names>W</given-names>
            </name>
            <name name-style="western">
              <surname>Kumar</surname>
              <given-names>A</given-names>
            </name>
          </person-group>
          <article-title>CONFlexFlow: integrating flexible clinical pathways into clinical decision support systems using context and rules</article-title>
          <source>Decision Support Syst</source>
          <year>2013</year>
          <month>05</month>
          <volume>55</volume>
          <issue>2</issue>
          <fpage>499</fpage>
          <lpage>515</lpage>
          <pub-id pub-id-type="doi">10.1016/j.dss.2012.10.008</pub-id>
        </nlm-citation>
      </ref>
      <ref id="ref17">
        <label>17</label>
        <nlm-citation citation-type="journal">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Chi</surname>
              <given-names>Y</given-names>
            </name>
            <name name-style="western">
              <surname>Chen</surname>
              <given-names>T</given-names>
            </name>
            <name name-style="western">
              <surname>Tsai</surname>
              <given-names>W</given-names>
            </name>
          </person-group>
          <article-title>A chronic disease dietary consultation system using OWL-based ontologies and semantic rules</article-title>
          <source>J Biomed Inform</source>
          <year>2015</year>
          <month>03</month>
          <volume>53</volume>
          <fpage>208</fpage>
          <lpage>19</lpage>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://linkinghub.elsevier.com/retrieve/pii/S1532-0464(14)00230-5"/>
          </comment>
          <pub-id pub-id-type="doi">10.1016/j.jbi.2014.11.001</pub-id>
          <pub-id pub-id-type="medline">25451101</pub-id>
          <pub-id pub-id-type="pii">S1532-0464(14)00230-5</pub-id>
        </nlm-citation>
      </ref>
      <ref id="ref18">
        <label>18</label>
        <nlm-citation citation-type="journal">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Rhayem</surname>
              <given-names>A</given-names>
            </name>
            <name name-style="western">
              <surname>Ahmed Mhiri</surname>
              <given-names>MB</given-names>
            </name>
            <name name-style="western">
              <surname>Salah</surname>
              <given-names>MB</given-names>
            </name>
            <name name-style="western">
              <surname>Gargouri</surname>
              <given-names>F</given-names>
            </name>
          </person-group>
          <article-title>Ontology-based system for patient monitoring with connected objects</article-title>
          <source>Procedia Comput Sci</source>
          <year>2017</year>
          <volume>112</volume>
          <fpage>683</fpage>
          <lpage>92</lpage>
          <pub-id pub-id-type="doi">10.1016/j.procs.2017.08.127</pub-id>
        </nlm-citation>
      </ref>
      <ref id="ref19">
        <label>19</label>
        <nlm-citation citation-type="journal">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Galopin</surname>
              <given-names>A</given-names>
            </name>
            <name name-style="western">
              <surname>Bouaud</surname>
              <given-names>J</given-names>
            </name>
            <name name-style="western">
              <surname>Pereira</surname>
              <given-names>S</given-names>
            </name>
            <name name-style="western">
              <surname>Seroussi</surname>
              <given-names>B</given-names>
            </name>
          </person-group>
          <article-title>An ontology-based clinical decision support system for the management of patients with multiple chronic disorders</article-title>
          <source>Stud Health Technol Inform</source>
          <year>2015</year>
          <volume>216</volume>
          <fpage>275</fpage>
          <lpage>9</lpage>
          <pub-id pub-id-type="medline">26262054</pub-id>
        </nlm-citation>
      </ref>
      <ref id="ref20">
        <label>20</label>
        <nlm-citation citation-type="journal">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Sherimon</surname>
              <given-names>PC</given-names>
            </name>
            <name name-style="western">
              <surname>Krishnan</surname>
              <given-names>R</given-names>
            </name>
          </person-group>
          <article-title>OntoDiabetic: an ontology-based clinical decision support system for diabetic patients</article-title>
          <source>Arab J Sci Eng</source>
          <year>2015</year>
          <month>12</month>
          <day>16</day>
          <volume>41</volume>
          <issue>3</issue>
          <fpage>1145</fpage>
          <lpage>60</lpage>
          <pub-id pub-id-type="doi">10.1007/s13369-015-1959-4</pub-id>
        </nlm-citation>
      </ref>
      <ref id="ref21">
        <label>21</label>
        <nlm-citation citation-type="journal">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Hristoskova</surname>
              <given-names>A</given-names>
            </name>
            <name name-style="western">
              <surname>Sakkalis</surname>
              <given-names>V</given-names>
            </name>
            <name name-style="western">
              <surname>Zacharioudakis</surname>
              <given-names>G</given-names>
            </name>
            <name name-style="western">
              <surname>Tsiknakis</surname>
              <given-names>M</given-names>
            </name>
            <name name-style="western">
              <surname>De Turck</surname>
              <given-names>F</given-names>
            </name>
          </person-group>
          <article-title>Ontology-driven monitoring of patient's vital signs enabling personalized medical detection and alert</article-title>
          <source>Sensors (Basel)</source>
          <year>2014</year>
          <month>01</month>
          <day>17</day>
          <volume>14</volume>
          <issue>1</issue>
          <fpage>1598</fpage>
          <lpage>628</lpage>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://www.mdpi.com/resolver?pii=s140101598"/>
          </comment>
          <pub-id pub-id-type="doi">10.3390/s140101598</pub-id>
          <pub-id pub-id-type="medline">24445411</pub-id>
          <pub-id pub-id-type="pii">s140101598</pub-id>
          <pub-id pub-id-type="pmcid">PMC3926628</pub-id>
        </nlm-citation>
      </ref>
      <ref id="ref22">
        <label>22</label>
        <nlm-citation citation-type="journal">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Riaño</surname>
              <given-names>D</given-names>
            </name>
            <name name-style="western">
              <surname>Real</surname>
              <given-names>F</given-names>
            </name>
            <name name-style="western">
              <surname>López-Vallverdú</surname>
              <given-names>JA</given-names>
            </name>
            <name name-style="western">
              <surname>Campana</surname>
              <given-names>F</given-names>
            </name>
            <name name-style="western">
              <surname>Ercolani</surname>
              <given-names>S</given-names>
            </name>
            <name name-style="western">
              <surname>Mecocci</surname>
              <given-names>P</given-names>
            </name>
            <name name-style="western">
              <surname>Annicchiarico</surname>
              <given-names>R</given-names>
            </name>
            <name name-style="western">
              <surname>Caltagirone</surname>
              <given-names>C</given-names>
            </name>
          </person-group>
          <article-title>An ontology-based personalization of health-care knowledge to support clinical decisions for chronically ill patients</article-title>
          <source>J Biomed Inform</source>
          <year>2012</year>
          <month>07</month>
          <volume>45</volume>
          <issue>3</issue>
          <fpage>429</fpage>
          <lpage>46</lpage>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://linkinghub.elsevier.com/retrieve/pii/S1532-0464(11)00222-X"/>
          </comment>
          <pub-id pub-id-type="doi">10.1016/j.jbi.2011.12.008</pub-id>
          <pub-id pub-id-type="medline">22269224</pub-id>
          <pub-id pub-id-type="pii">S1532-0464(11)00222-X</pub-id>
        </nlm-citation>
      </ref>
      <ref id="ref23">
        <label>23</label>
        <nlm-citation citation-type="journal">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Jin</surname>
              <given-names>W</given-names>
            </name>
            <name name-style="western">
              <surname>Kim</surname>
              <given-names>DH</given-names>
            </name>
          </person-group>
          <article-title>Design and implementation of e-health system based on semantic sensor network using IETF YANG</article-title>
          <source>Sensors (Basel)</source>
          <year>2018</year>
          <month>03</month>
          <day>20</day>
          <volume>18</volume>
          <issue>2</issue>
          <fpage>629</fpage>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://www.mdpi.com/resolver?pii=s18020629"/>
          </comment>
          <pub-id pub-id-type="doi">10.3390/s18020629</pub-id>
          <pub-id pub-id-type="medline">29461493</pub-id>
          <pub-id pub-id-type="pii">s18020629</pub-id>
          <pub-id pub-id-type="pmcid">PMC5854965</pub-id>
        </nlm-citation>
      </ref>
      <ref id="ref24">
        <label>24</label>
        <nlm-citation citation-type="confproc">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Ganguly</surname>
              <given-names>P</given-names>
            </name>
            <name name-style="western">
              <surname>Chattopadhyay</surname>
              <given-names>S</given-names>
            </name>
            <name name-style="western">
              <surname>Paramesh</surname>
              <given-names>N</given-names>
            </name>
            <name name-style="western">
              <surname>Ray</surname>
              <given-names>P</given-names>
            </name>
          </person-group>
          <article-title>An ontology-based framework for managing semantic interoperability issues in e-health</article-title>
          <source>Proceedings of the HealthCom 2008 - 10th International Conference on e-health Networking, Applications and Services</source>
          <year>2008</year>
          <conf-name>HealthCom 2008 - 10th International Conference on e-health Networking, Applications and Services</conf-name>
          <conf-date>Jul 7-9, 2008</conf-date>
          <conf-loc>Singapore</conf-loc>
          <pub-id pub-id-type="doi">10.1109/health.2008.4600114</pub-id>
        </nlm-citation>
      </ref>
      <ref id="ref25">
        <label>25</label>
        <nlm-citation citation-type="confproc">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Bouza</surname>
              <given-names>A</given-names>
            </name>
            <name name-style="western">
              <surname>Reif</surname>
              <given-names>G</given-names>
            </name>
            <name name-style="western">
              <surname>Bernstein</surname>
              <given-names>A</given-names>
            </name>
            <name name-style="western">
              <surname>Gall</surname>
              <given-names>H</given-names>
            </name>
          </person-group>
          <article-title>Semtree: ontology-based decision tree algorithm for recommender systems</article-title>
          <source>Proceedings of the Poster and Demonstration Session at the 7th International Semantic Web Conference (ISWC2008)</source>
          <year>2008</year>
          <conf-name>Proceedings of the Poster and Demonstration Session at the 7th International Semantic Web Conference (ISWC2008)</conf-name>
          <conf-date>Oct 28, 2008</conf-date>
          <conf-loc>Karlsruhe, Germany</conf-loc>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://www.researchgate.net/publication/221466395_SemTree_Ontology-Based_Decision_Tree_Algorithm_for_Recommender_Systems"/>
          </comment>
        </nlm-citation>
      </ref>
      <ref id="ref26">
        <label>26</label>
        <nlm-citation citation-type="confproc">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Villalonga</surname>
              <given-names>C</given-names>
            </name>
            <name name-style="western">
              <surname>op den Akker</surname>
              <given-names>H</given-names>
            </name>
            <name name-style="western">
              <surname>Hermens</surname>
              <given-names>H</given-names>
            </name>
            <name name-style="western">
              <surname>Herrera</surname>
              <given-names>L</given-names>
            </name>
            <name name-style="western">
              <surname>Pomares</surname>
              <given-names>H</given-names>
            </name>
            <name name-style="western">
              <surname>Rojas</surname>
              <given-names>I</given-names>
            </name>
            <name name-style="western">
              <surname>Valenzuela</surname>
              <given-names>O</given-names>
            </name>
            <name name-style="western">
              <surname>Banos</surname>
              <given-names>O</given-names>
            </name>
          </person-group>
          <article-title>Ontological modeling of motivational messages for physical activity coaching</article-title>
          <source>Proceedings of the 11th EAI International Conference on Pervasive Computing Technologies for Healthcare</source>
          <year>2017</year>
          <conf-name>PervasiveHealth '17: 11th EAI International Conference on Pervasive Computing Technologies for Healthcare</conf-name>
          <conf-date>May 23 - 26, 2017</conf-date>
          <conf-loc>Barcelona Spain</conf-loc>
          <pub-id pub-id-type="doi">10.1145/3154862.3154926</pub-id>
        </nlm-citation>
      </ref>
      <ref id="ref27">
        <label>27</label>
        <nlm-citation citation-type="journal">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Lasierra</surname>
              <given-names>N</given-names>
            </name>
            <name name-style="western">
              <surname>Alesanco</surname>
              <given-names>A</given-names>
            </name>
            <name name-style="western">
              <surname>Guillén</surname>
              <given-names>S</given-names>
            </name>
            <name name-style="western">
              <surname>García</surname>
              <given-names>J</given-names>
            </name>
          </person-group>
          <article-title>A three stage ontology-driven solution to provide personalized care to chronic patients at home</article-title>
          <source>J Biomed Inform</source>
          <year>2013</year>
          <month>07</month>
          <volume>46</volume>
          <issue>3</issue>
          <fpage>516</fpage>
          <lpage>29</lpage>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://linkinghub.elsevier.com/retrieve/pii/S1532-0464(13)00040-3"/>
          </comment>
          <pub-id pub-id-type="doi">10.1016/j.jbi.2013.03.006</pub-id>
          <pub-id pub-id-type="medline">23567539</pub-id>
          <pub-id pub-id-type="pii">S1532-0464(13)00040-3</pub-id>
        </nlm-citation>
      </ref>
      <ref id="ref28">
        <label>28</label>
        <nlm-citation citation-type="web">
          <article-title>MOX2 Bluetooth LE activity monitor</article-title>
          <source>Accelerometry.eu</source>
          <access-date>2022-02-24</access-date>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://www.accelerometry.eu/products/wearable-sensors/mox2/">https://www.accelerometry.eu/products/wearable-sensors/mox2/</ext-link>
          </comment>
        </nlm-citation>
      </ref>
      <ref id="ref29">
        <label>29</label>
        <nlm-citation citation-type="journal">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Eriksson</surname>
              <given-names>O</given-names>
            </name>
            <name name-style="western">
              <surname>Johannesson</surname>
              <given-names>P</given-names>
            </name>
            <name name-style="western">
              <surname>Bergholtz</surname>
              <given-names>M</given-names>
            </name>
          </person-group>
          <article-title>Institutional ontology for Conceptual Modeling</article-title>
          <source>J Inf Technol</source>
          <year>2018</year>
          <month>06</month>
          <day>01</day>
          <volume>33</volume>
          <issue>2</issue>
          <fpage>105</fpage>
          <lpage>23</lpage>
          <pub-id pub-id-type="doi">10.1057/s41265-018-0053-2</pub-id>
        </nlm-citation>
      </ref>
      <ref id="ref30">
        <label>30</label>
        <nlm-citation citation-type="web">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Bell</surname>
              <given-names>D</given-names>
            </name>
          </person-group>
          <article-title>An introduction to the Unified Modeling Language</article-title>
          <source>IBM</source>
          <access-date>2022-04-19</access-date>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://developer.ibm.com/articles/an-introduction-to-uml/">https://developer.ibm.com/articles/an-introduction-to-uml/</ext-link>
          </comment>
        </nlm-citation>
      </ref>
      <ref id="ref31">
        <label>31</label>
        <nlm-citation citation-type="book">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Johnson</surname>
              <given-names>I</given-names>
            </name>
            <name name-style="western">
              <surname>Abécassis</surname>
              <given-names>J</given-names>
            </name>
            <name name-style="western">
              <surname>Charnomordic</surname>
              <given-names>B</given-names>
            </name>
            <name name-style="western">
              <surname>Destercke</surname>
              <given-names>S</given-names>
            </name>
            <name name-style="western">
              <surname>Thomopoulos</surname>
              <given-names>R</given-names>
            </name>
          </person-group>
          <article-title>Making Ontology-Based Knowledge and Decision Trees interact: an approach to enrich knowledge and increase expert confidence in data-driven models</article-title>
          <source>Knowledge Science, Engineering and Management</source>
          <year>2010</year>
          <publisher-loc>Berlin, Heidelberg</publisher-loc>
          <publisher-name>Springer</publisher-name>
        </nlm-citation>
      </ref>
      <ref id="ref32">
        <label>32</label>
        <nlm-citation citation-type="book">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Gajderowicz</surname>
              <given-names>B</given-names>
            </name>
            <name name-style="western">
              <surname>Sadeghian</surname>
              <given-names>A</given-names>
            </name>
            <name name-style="western">
              <surname>Soutchanski</surname>
              <given-names>M</given-names>
            </name>
          </person-group>
          <article-title>Ontology enhancement through inductive decision trees</article-title>
          <source>Uncertainty Reasoning for the Semantic Web II</source>
          <year>2013</year>
          <publisher-loc>Berlin, Heidelberg</publisher-loc>
          <publisher-name>Springer</publisher-name>
        </nlm-citation>
      </ref>
      <ref id="ref33">
        <label>33</label>
        <nlm-citation citation-type="journal">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Holsapple</surname>
              <given-names>CW</given-names>
            </name>
            <name name-style="western">
              <surname>Joshi</surname>
              <given-names>KD</given-names>
            </name>
          </person-group>
          <article-title>A collaborative approach to ontology design</article-title>
          <source>Commun ACM</source>
          <year>2002</year>
          <month>02</month>
          <volume>45</volume>
          <issue>2</issue>
          <fpage>42</fpage>
          <lpage>7</lpage>
          <pub-id pub-id-type="doi">10.1145/503124.503147</pub-id>
        </nlm-citation>
      </ref>
      <ref id="ref34">
        <label>34</label>
        <nlm-citation citation-type="web">
          <article-title>Weather API</article-title>
          <source>Open Weather</source>
          <access-date>2022-02-24</access-date>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://openweathermap.org/api">https://openweathermap.org/api</ext-link>
          </comment>
        </nlm-citation>
      </ref>
      <ref id="ref35">
        <label>35</label>
        <nlm-citation citation-type="journal">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Sirin</surname>
              <given-names>E</given-names>
            </name>
            <name name-style="western">
              <surname>Parsia</surname>
              <given-names>B</given-names>
            </name>
            <name name-style="western">
              <surname>Cuenca Grau</surname>
              <given-names>B</given-names>
            </name>
            <name name-style="western">
              <surname>Kalyanpur</surname>
              <given-names>A</given-names>
            </name>
            <name name-style="western">
              <surname>Katz</surname>
              <given-names>Y</given-names>
            </name>
          </person-group>
          <article-title>Pellet: a practical OWL-DL reasoner</article-title>
          <source>SSRN J</source>
          <year>2007</year>
          <pub-id pub-id-type="doi">10.2139/ssrn.3199351</pub-id>
        </nlm-citation>
      </ref>
      <ref id="ref36">
        <label>36</label>
        <nlm-citation citation-type="journal">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Parsia</surname>
              <given-names>B</given-names>
            </name>
            <name name-style="western">
              <surname>Matentzoglu</surname>
              <given-names>N</given-names>
            </name>
            <name name-style="western">
              <surname>Gonçalves</surname>
              <given-names>Rafael S</given-names>
            </name>
            <name name-style="western">
              <surname>Glimm</surname>
              <given-names>B</given-names>
            </name>
            <name name-style="western">
              <surname>Steigmiller</surname>
              <given-names>A</given-names>
            </name>
          </person-group>
          <article-title>The OWL Reasoner Evaluation (ORE) 2015 competition report</article-title>
          <source>J Autom Reason</source>
          <year>2017</year>
          <volume>59</volume>
          <issue>4</issue>
          <fpage>455</fpage>
          <lpage>82</lpage>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="http://europepmc.org/abstract/MED/30069067"/>
          </comment>
          <pub-id pub-id-type="doi">10.1007/s10817-017-9406-8</pub-id>
          <pub-id pub-id-type="medline">30069067</pub-id>
          <pub-id pub-id-type="pii">9406</pub-id>
          <pub-id pub-id-type="pmcid">PMC6044265</pub-id>
        </nlm-citation>
      </ref>
      <ref id="ref37">
        <label>37</label>
        <nlm-citation citation-type="book">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Knublauch</surname>
              <given-names>H</given-names>
            </name>
            <name name-style="western">
              <surname>Fergerson</surname>
              <given-names>R</given-names>
            </name>
            <name name-style="western">
              <surname>Noy</surname>
              <given-names>N</given-names>
            </name>
            <name name-style="western">
              <surname>Musen</surname>
              <given-names>M</given-names>
            </name>
          </person-group>
          <article-title>The Protégé OWL plugin: an open development environment for semantic web applications</article-title>
          <source>The Semantic Web – ISWC 2004</source>
          <year>2004</year>
          <publisher-loc>Berlin, Heidelberg</publisher-loc>
          <publisher-name>Springer</publisher-name>
        </nlm-citation>
      </ref>
      <ref id="ref38">
        <label>38</label>
        <nlm-citation citation-type="web">
          <article-title>Editors</article-title>
          <source>Semantic Web</source>
          <access-date>2022-02-24</access-date>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="http://semanticweb.org/wiki/Editors">http://semanticweb.org/wiki/Editors</ext-link>
          </comment>
        </nlm-citation>
      </ref>
      <ref id="ref39">
        <label>39</label>
        <nlm-citation citation-type="web">
          <article-title>Reasoners</article-title>
          <source>Semantic Web</source>
          <access-date>2022-02-24</access-date>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="http://semanticweb.org/wiki/Reasoners">http://semanticweb.org/wiki/Reasoners</ext-link>
          </comment>
        </nlm-citation>
      </ref>
      <ref id="ref40">
        <label>40</label>
        <nlm-citation citation-type="confproc">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Shearer</surname>
              <given-names>R</given-names>
            </name>
            <name name-style="western">
              <surname>Motik</surname>
              <given-names>B</given-names>
            </name>
            <name name-style="western">
              <surname>Horrocks</surname>
              <given-names>I</given-names>
            </name>
          </person-group>
          <article-title>HermiT: A highly-efficient OWL reasoner</article-title>
          <source>Proceedings of the Fifth OWLED Workshop on OWL: Experiences and Directions, collocated with the 7th International Semantic Web Conference (ISWC-2008)</source>
          <year>2008</year>
          <conf-name>Proceedings of the Fifth OWLED Workshop on OWL: Experiences and Directions, collocated with the 7th International Semantic Web Conference (ISWC-2008)</conf-name>
          <conf-date>Oct 26-27, 2008</conf-date>
          <conf-loc>Karlsruhe, Germany</conf-loc>
        </nlm-citation>
      </ref>
      <ref id="ref41">
        <label>41</label>
        <nlm-citation citation-type="book">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Tsarkov</surname>
              <given-names>D</given-names>
            </name>
            <name name-style="western">
              <surname>Horrocks</surname>
              <given-names>I</given-names>
            </name>
          </person-group>
          <article-title>FaCT++ description logic reasoner: system description</article-title>
          <source>Automated Reasoning</source>
          <year>2006</year>
          <publisher-loc>Berlin, Heidelberg</publisher-loc>
          <publisher-name>Springer</publisher-name>
        </nlm-citation>
      </ref>
      <ref id="ref42">
        <label>42</label>
        <nlm-citation citation-type="book">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Haarslev</surname>
              <given-names>V</given-names>
            </name>
            <name name-style="western">
              <surname>Möller</surname>
              <given-names>R</given-names>
            </name>
          </person-group>
          <article-title>RACER system description</article-title>
          <source>Automated Reasoning</source>
          <year>2001</year>
          <publisher-loc>Berlin, Heidelberg</publisher-loc>
          <publisher-name>Springer</publisher-name>
        </nlm-citation>
      </ref>
      <ref id="ref43">
        <label>43</label>
        <nlm-citation citation-type="web">
          <article-title>Getting started with Apache Jena</article-title>
          <source>Apache Jena</source>
          <access-date>2022-02-24</access-date>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://jena.apache.org/getting_started/index.html">https://jena.apache.org/getting_started/index.html</ext-link>
          </comment>
        </nlm-citation>
      </ref>
      <ref id="ref44">
        <label>44</label>
        <nlm-citation citation-type="web">
          <article-title>SPARQL 1.1 Query Language</article-title>
          <source>W3C</source>
          <access-date>2022-02-24</access-date>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="http://www.w3.org/TR/2013/REC-sparql11-query-20130321/">http://www.w3.org/TR/2013/REC-sparql11-query-20130321/</ext-link>
          </comment>
        </nlm-citation>
      </ref>
      <ref id="ref45">
        <label>45</label>
        <nlm-citation citation-type="web">
          <article-title>Appreciating SPARQL CONSTRUCT more</article-title>
          <source>SPARQL</source>
          <access-date>2022-02-24</access-date>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="http://www.snee.com/bobdc.blog/2009/09/appreciating-sparql-construct.html">http://www.snee.com/bobdc.blog/2009/09/appreciating-sparql-construct.html</ext-link>
          </comment>
        </nlm-citation>
      </ref>
      <ref id="ref46">
        <label>46</label>
        <nlm-citation citation-type="web">
          <article-title>Jena Ontology API</article-title>
          <source>Apache Jena</source>
          <access-date>2022-02-24</access-date>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="http://jena.apache.org/documentation/ontology/">http://jena.apache.org/documentation/ontology/</ext-link>
          </comment>
        </nlm-citation>
      </ref>
      <ref id="ref47">
        <label>47</label>
        <nlm-citation citation-type="journal">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Cataletto</surname>
              <given-names>M</given-names>
            </name>
          </person-group>
          <article-title>World Health Organization issues new guidelines on physical activity and sedentary behavior</article-title>
          <source>Pediatric Allergy Immunol Pulmonol</source>
          <year>2020</year>
          <month>12</month>
          <day>01</day>
          <volume>33</volume>
          <issue>4</issue>
          <fpage>167</fpage>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="http://www.seu-roma.it/riviste/annali_igiene/open_access/articoli/31-06-07-Scatigna.pdf"/>
          </comment>
          <pub-id pub-id-type="doi">10.1089/ped.2020.29005.mca</pub-id>
        </nlm-citation>
      </ref>
      <ref id="ref48">
        <label>48</label>
        <nlm-citation citation-type="web">
          <article-title>Sedentary behaviour for adults</article-title>
          <source>KFL&#38;A Public Health</source>
          <access-date>2022-02-24</access-date>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://www.kflaph.ca/en/healthy-living/sedentary-behaviour-for-adults.aspx">https://www.kflaph.ca/en/healthy-living/sedentary-behaviour-for-adults.aspx</ext-link>
          </comment>
        </nlm-citation>
      </ref>
      <ref id="ref49">
        <label>49</label>
        <nlm-citation citation-type="web">
          <article-title>Physical activity</article-title>
          <source>World Health Organization</source>
          <access-date>2022-02-24</access-date>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://www.who.int/news-room/fact-sheets/detail/physical-activity">https://www.who.int/news-room/fact-sheets/detail/physical-activity</ext-link>
          </comment>
        </nlm-citation>
      </ref>
      <ref id="ref50">
        <label>50</label>
        <nlm-citation citation-type="web">
          <article-title>How many pedometer steps should you aim for each day?</article-title>
          <source>Verywellfit</source>
          <access-date>2022-02-24</access-date>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://www.verywellfit.com/how-many-pedometer-steps-per-day-are-enough-3432827">https://www.verywellfit.com/how-many-pedometer-steps-per-day-are-enough-3432827</ext-link>
          </comment>
        </nlm-citation>
      </ref>
      <ref id="ref51">
        <label>51</label>
        <nlm-citation citation-type="web">
          <article-title>Weather conditions</article-title>
          <source>Open Weather</source>
          <access-date>2022-04-19</access-date>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://openweathermap.org/weather-conditions">https://openweathermap.org/weather-conditions</ext-link>
          </comment>
        </nlm-citation>
      </ref>
      <ref id="ref52">
        <label>52</label>
        <nlm-citation citation-type="book">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Seligman</surname>
              <given-names>M</given-names>
            </name>
            <name name-style="western">
              <surname>Csikszentmihalyi</surname>
              <given-names>M</given-names>
            </name>
          </person-group>
          <article-title>Positive psychology: an introduction</article-title>
          <source>Flow and the Foundations of Positive Psychology</source>
          <year>2014</year>
          <publisher-loc>Dordrecht</publisher-loc>
          <publisher-name>Springer</publisher-name>
        </nlm-citation>
      </ref>
      <ref id="ref53">
        <label>53</label>
        <nlm-citation citation-type="web">
          <article-title>The SROIQ(D) description logic</article-title>
          <source>Leslie Sikos</source>
          <access-date>2022-02-24</access-date>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="http://www.lesliesikos.com/sroiqd-description-logic/">http://www.lesliesikos.com/sroiqd-description-logic/</ext-link>
          </comment>
        </nlm-citation>
      </ref>
    </ref-list>
  </back>
</article>
