<!DOCTYPE article PUBLIC "-//NLM//DTD JATS (Z39.96) Journal Archiving and Interchange DTD v1.0 20120330//EN" "JATS-archivearticle1.dtd">
<article xmlns:xlink="http://www.w3.org/1999/xlink">
  <front>
    <journal-meta />
    <article-meta>
      <title-group>
        <article-title>The Systematic Dataset Review Process: from Linked Dataset Discoverability to their FAIRness</article-title>
      </title-group>
      <contrib-group>
        <contrib contrib-type="author">
          <string-name>Sana Latif</string-name>
          <xref ref-type="aff" rid="aff0">0</xref>
        </contrib>
        <contrib contrib-type="author">
          <string-name>Maria Angela Pellegrino</string-name>
          <xref ref-type="aff" rid="aff0">0</xref>
        </contrib>
        <aff id="aff0">
          <label>0</label>
          <institution>Università degli Studi di Salerno</institution>
          ,
          <addr-line>via Giovanni Paolo II, 132, 84084 Fisciano (SA)</addr-line>
          ,
          <country country="IT">Italy</country>
        </aff>
      </contrib-group>
      <abstract>
        <p>This work presents the Systematic Dataset Review process, a systematic, cyclic, and FAIR-aligned process for dataset discovery, curation, and quality assessment, inspired by Systematic Literature Review methodologies. The process consists of three phases: (i) a (multivocal) literature review to identify and document references about datasets; (ii) a Linked Dataset Discoverability phase to curate, filter, and publish datasets as domain-specific Linked Open Data sub-clouds; and (iii) a Quality Assessment phase that enables FAIRness evaluations through automated tools. The framework is adaptable across diferent use cases: monitoring the quality of existing sub-clouds, enriching current sub-clouds with new datasets, or constructing entirely new thematic sub-clouds. By ensuring transparency, reproducibility, and ongoing quality monitoring, this approach supports the creation of accessible and sustainable dataset ecosystems.</p>
      </abstract>
      <kwd-group>
        <kwd>eol&gt;Process</kwd>
        <kwd>FAIRness</kwd>
        <kwd>Dataset discoverability</kwd>
        <kwd>Literature Review</kwd>
        <kwd>Quality assessment</kwd>
        <kwd>Reproducibility</kwd>
      </kwd-group>
    </article-meta>
  </front>
  <body>
    <sec id="sec-1">
      <title>1. Introduction</title>
      <p>A systematic literature review (SLR) is a structured and methodical approach to identifying, evaluating,
and synthesizing all relevant research on a particular topic or research question, with the aim of
minimizing bias and ensuring reproducibility. SLRs follow a well-defined protocol to ensure comprehensiveness,
traceability, and replicability of the process. This typically involves defining explicit inclusion and
exclusion criteria, conducting a systematic search across multiple databases, applying quality assessment
techniques, and organizing the findings through qualitative or quantitative synthesis.</p>
      <p>
        Over the past two decades, numerous guidelines have been proposed to support researchers in
conducting SLRs efectively, ranging from guidelines for conducting literature mappings [
        <xref ref-type="bibr" rid="ref1 ref2">1, 2</xref>
        ] to scoping
reviews [
        <xref ref-type="bibr" rid="ref3 ref4">3, 4</xref>
        ], for snowballing [
        <xref ref-type="bibr" rid="ref5">5</xref>
        ] and a wide range of diferent checklist for rigorously reviewing
literature [
        <xref ref-type="bibr" rid="ref10 ref11 ref6 ref7 ref8 ref9">6, 7, 8, 9, 10, 11</xref>
        ]. Prominent among these are the guidelines introduced by Kitchenham and
Charters [
        <xref ref-type="bibr" rid="ref12">12</xref>
        ], which formalize the planning, conducting, and reporting stages of an SLR.
      </p>
      <p>
        In response to the growing complexity and interdisciplinarity of research, the notion of multivocal
literature reviews (MLRs) has also emerged. MLRs extend traditional SLRs by incorporating not only
peerreviewed academic literature but also the so called gray literature sources such as industry reports, blog
posts, white papers, and technical documentation [
        <xref ref-type="bibr" rid="ref13">13</xref>
        ]. This is especially valuable in applied fields like
computer science and engineering, where practice-oriented insights may precede academic publication
or remain outside conventional scholarly venues. Incorporating multivocal sources helps capture a
more holistic view of the topic, reflecting both theoretical advances and practical implementations.
      </p>
      <p>
        While SLR guidelines are originally designed for synthesizing evidence from scholarly publications,
this poster proposes to adapt them to dataset discovery and assessment. It is not a straightforward
process as this adaptation poses several challenges that necessitate methodological adaptation. Unlike
academic papers, datasets are often published in non-traditional sources like data portals, GitHub,
or Zenodo, lacking standardized metadata, persistent identifiers, or peer review validation. This
requires rethinking the search strategy, often shifting from bibliographic queries to web crawling or
API-based retrieval. The unit of analysis also difers: while SLRs assess research rigour and validity,
dataset assessment must consider technical and semantic properties such as licensing, provenance,
format (e.g., RDF), and accessibility, often operationalized through frameworks like FAIR [
        <xref ref-type="bibr" rid="ref14">14</xref>
        ] or Linked
Data quality dimensions [
        <xref ref-type="bibr" rid="ref15">15</xref>
        ]. Moreover, datasets are dynamic—they can be updated, versioned, or
deleted—so temporal aspects and version tracking become essential in defining inclusion criteria and in
maintaining reproducibility. Quality assessment in this context must go beyond narrative synthesis,
incorporating metrics-based evaluations (e.g., completeness, availability, interlinking) using tools
like FAIR-Checker [
        <xref ref-type="bibr" rid="ref16">16</xref>
        ] or KGHeartBeat [
        <xref ref-type="bibr" rid="ref17">17</xref>
        ]. Finally, synthesis methods may rely less on narrative
summaries and more on dashboard visualizations, semantic mappings, or clustering of metadata. These
diferences highlight the need for a tailored methodology that retains the systematic rigour of SLRs
while embracing the unique demands of dataset discovery and evaluation in the Semantic Web.
      </p>
      <p>This poster introduces the Systematic Dataset Review (SDR) process. To the best of our
knowledge, this is the first methodology that proposes guidelines to systematic identify datasets. While
the process is detailed in Section 2, Section 3 illustrates its practical relevance through concrete use
cases. The article concludes with final thoughts, limitations, and future directions.
2. Systematic</p>
      <p>Dataset</p>
    </sec>
    <sec id="sec-2">
      <title>Review Process</title>
      <p>This section outlines the SDR process, a rigorous and Systematic three-phase process for conducting
Dataset Reviews, aimed at improving dataset discoverability and quality assessment. The approach
draws on established SLR guidelines and is aligned with the FAIR principles—Findability, Accessibility,
Interoperability, and Reusability. This proposal builds upon a comprehensive analysis of established
SLR guidelines, concrete experience in curating domain-specific collections of datasets (as detailed
in Section 3), and consolidated expertise in evaluating Linked Data quality through FAIR-aligned
frameworks and tools. The overall process is illustrated in Figure 1 which graphically reports phases,
each phase output, and the alignment with FAIR principles.</p>
      <p>
        The first phase , titled (Multivocal) Literature Review, follows conventional SLR practices and
focuses on the identification and selection of relevant scholarly contributions. Literature is retrieved
via automated database searches, manual searches, and exploration of gray literature, and then filtered
based on eligibility and inclusion criteria. The resulting set of selected papers forms the knowledge base
for further investigation. To enhance transparency and reproducibility, the outcome of this phase should
be published as a replication package, which encapsulates the review protocol, selection rationale,
and data extracted from included studies. By eating-our-own-food, the replication package might be
structured via ontologies, as SLRONT [
        <xref ref-type="bibr" rid="ref18">18</xref>
        ]. While the SLR process inherently supports findability here
interpreted as discoverability of relevant resources, the replication package significantly broadens the
impact by supporting all FAIR principles: it ensures the accessibility of review materials, interoperability
with related studies via shared standards and formats, and reusability for follow-up analysis or
metareviews. Moreover, when replication packages are published in searchable repositories and assigned a
persistent identifier—such as those provided by Zenodo—findability is also ensured. Besides enabling
transparency, replication packages enable reproducibility. It is important to note that at this stage, the
process is format-agnostic and focuses primarily on scholarly literature rather than datasets.
      </p>
      <p>The second phase, called Linked Dataset Discoverability, adapts SLR principles to dataset
identification. This involves discovering datasets mentioned in academic publications or indexed in online
repositories, using both automated and manual approaches. By applying dataset-specific eligibility and
inclusion criteria, a curated list of relevant datasets is compiled. These datasets can then be published
as part of a thematic LOD (Linked Open Data) sub-cloud, modelled after well-known examples like
the LOD Cloud1. This phase further reinforces findability of linked datasets and the LOD sub-cloud as
an output facilitates the implementation of the other FAIR principles by encouraging standard access
points (e.g., the LOD Cloud as a standard mechanism to visualize inter-linked datasets), proper licensing,
and reuse-oriented metadata. Indexing linked datasets in a unified search engine enhances findability;
adopting standardized publication mechanisms, such as linked data clouds, supports accessibility;
following linked data principles facilitates interoperability through interlinking; and defining appropriate
licensing terms enables reusability. Unlike the first phase, this stage is data format dependent, requiring
adjustments based on the data structures (e.g., RDF, JSON-LD) and the specific characteristics of the
community or domain. Repository selection, filtering criteria, and publication strategies must be tailored
accordingly to ensure compatibility and engagement.</p>
      <p>
        The third phase, Quality Assessment, evaluates the sub-cloud datasets using periodic, metric-based
evaluations. These assessments are grounded in quality dimensions commonly addressed in SLRs (e.g.,
accuracy, completeness, timeliness) and can be mapped to the FAIR principles. The outcome is a Dataset
Quality Report ofering both aggregated and fine-grained metrics. This phase supports long-term
monitoring of dataset quality, ensuring that the curated datasets remain aligned with FAIR principles
over time. Tools as FAIR-Checker [
        <xref ref-type="bibr" rid="ref16">16</xref>
        ], SPARQLES [19], and KGHeartBeat [
        <xref ref-type="bibr" rid="ref17">17</xref>
        ] can support this stage,
enabling automated FAIRness scoring and deeper quality diagnostics. This aligns with recent eforts to
transit from traditional linked data quality assessments to FAIR-oriented evaluations [20].
      </p>
      <p>Importantly, the entire framework is designed to be iterative and extensible. The cyclical nature of
the process accommodates regular updates to dataset quality scores, the inclusion of newly published
datasets, and revisions to the literature review itself. This dynamic workflow ensures that the knowledge
ecosystem remains current, reflective of emerging standards, and responsive to the evolving landscape of
data publication and reuse. To alleviate the manual efort involved in the eligibility and inclusion phases,
recent literature has highlighted the potential of automating these steps through machine learning
and language model-based approaches [21, 22, 23, 24, 25, 26, 20]. These methods aim to streamline
the review process while preserving human oversight through a human-in-the-loop approach, where
experts retain final control to ensure relevance and contextual accuracy. This hybrid model balances
automation with the nuanced judgment essential to scholarly curation.
1LOD Cloud: https://lod-cloud.net</p>
    </sec>
    <sec id="sec-3">
      <title>3. Use Cases</title>
      <p>
        This process can be instantiated across a variety of scenarios to support dataset discoverability,
enrichment, and quality monitoring within the LOD ecosystem. Three main use cases can be distinguished:
• Quality Assessment of an Existing Sub-Cloud. In cases where a sub-cloud already exists, the
process can begin from the third phase. The curated list of datasets serves as a stable foundation,
and the third phase (Quality Assessment) can be directly integrated to enable ongoing, periodic
FAIRness evaluations. This supports long-term monitoring and maintenance of the sub-cloud’s
quality, ensuring its continued alignment with community standards. As a driving example in
this direction, we report the Linguistic LOD use case [27]. Besides relying on the Linguistic
LOD Cloud [28] as a main source, the extraction of linguistic LOD use case followed a systematic
literature review approach inspired by Kitchenham’s [
        <xref ref-type="bibr" rid="ref12">12</xref>
        ] guidelines and structured in planning,
conducting, and reporting phases. In the planning stage, the objectives and research questions
were defined, focusing on publishing trends of linguistic datasets modeled with Semantic Web
technologies, the search engines most often employed, and evidence of dataset reuse, with the
scope restricted to peer-reviewed works published in English between 2014 and 2024. The
conducting phase relied on Scopus as the sole source, chosen for its broad coverage, where
a tailored search string was applied, explicitly including terms such as “knowledge graph”,
“linked data”, and “linguistic”, while excluding acronyms and “ontology” to privilege
materialized datasets over conceptual models. This search retrieved 1, 788 records, which were
screened by two independent reviewers following PRISMA guidelines: first by title and abstract,
then by full text, with disagreements resolved through weekly discussions and, when necessary,
collaborative arbitration. The multi-stage screening resulted in 181 primary studies, of which
92 made use of LLOD resources and 89 defined 69 distinct linguistic linked datasets. In the
reporting phase, these datasets were analyzed in relation to the FAIR principles—findability,
accessibility, interoperability, and reusability—with those already indexed in the LLOD Cloud
monitored automatically on a weekly basis via KGHeartBeat [
        <xref ref-type="bibr" rid="ref17">17</xref>
        ], while the others were manually
checked through their accompanying publications and dataset websites, ensuring a consistent
and comprehensive assessment of linguistic linked data practices.
• Enrichment of an Existing Sub-Cloud. The process also supports the expansion of existing
sub-clouds. For example, the Life Sciences LOD Cloud [29] can be enriched with additional
biomedical datasets identified through automated tools or manual review. After extending the
dataset list (phase two), the newly enriched sub-cloud can undergo quality assessment (phase
three). This ensures the sub-cloud evolves with the growing needs and contributions of the
community while maintaining FAIR compliance.
• Creation of a New Thematic Sub-Cloud. The full three-phase workflow is particularly useful
for constructing a novel sub-cloud—such as the Cultural Heritage LOD Cloud (CHeCLOUD2).
Based on the process described in [20], the construction of the cloud began with the LD
discoverability phase, using the December 2024 LOD Cloud snapshot as the primary source. From
an initial pool of 1, 658 datasets, two independent annotators manually examined dataset titles,
descriptions, and keywords to identify datasets both compliant with LD principles (C1) and
relevant to the Cultural Heritage domain (C2). Conflicts (105 cases, approximately 6%) were
resolved through discussion, with a third reviewer acting as arbiter. In addition, 49 further
datasets were manually collected from complementary sources, including GitHub and Zenodo
searches, expert recommendations, and relevant literature. A final inclusion screening was then
performed, involving detailed reviews of metadata, dataset landing pages, and available data. This
step generated additional discussions on 19 cases (around 10% of the eligible pool), ultimately
leading to the inclusion of 192 datasets in CHeCLOUD. Each dataset in the index is accompanied
by both coarse-grained and fine-grained quality assessment reports generated automatically
via KGHeartBeat [
        <xref ref-type="bibr" rid="ref17">17</xref>
        ], as demonstrated in Tuozzo et al. [30]. While coarse-grain visualization
2CHeCLOUD: http://isislab.it:12280/CHe-cloud
enables datasets comparison, the fine-grain one provides punctual access to individual dataset
quality scores over time. These scores are complemented by an automatically verbalized quality
summary, currently produced through Gemini 2.5 Pro, though the framework is designed to
support interchangeable LLMs. A preliminary evaluation confirms the accuracy and usefulness
of these generated summaries, while a more structured comparative study across alternative
LLMs remains a necessary next step. While the discoverability and metadata curation phases
still require human oversight, the quality assessment pipeline is fully automated and executed
on a weekly basis, ensuring the continuous monitoring of dataset FAIRness within the Cultural
Heritage domain.
      </p>
    </sec>
    <sec id="sec-4">
      <title>4. Conclusion, Limitations, and Future Direction</title>
      <p>The SDR process represents a high-level proposal for enabling reproducible, high-quality, and
formatagnostic dataset discovery and quality assessment, while remaining adaptable to the specific needs of
individual research communities. Although a universal, one-size-fits-all toolkit is dificult to achieve,
the provision of clear guidelines can ensure transparency, comparability, and reproducibility across
domains. To illustrate how the process operates in practice, this poster presents two domain-specific
pilots: CHeCLOUD, targeting Cultural Heritage, and the Linguistic LOD sub-cloud. Both pilots have
demonstrated the feasibility of enriching existing dataset indexes while providing periodic, fully
automated FAIRness assessments. Their partial outcomes, such as curated dataset lists, quality trends,
and FAIR scores, are openly shared through public repositories, thereby strengthening transparency,
accountability, and open science practices.</p>
      <p>A defining feature of the SDR process is its community-driven nature: domain experts and dataset
curators are actively invited to refine inclusion criteria, validate the relevance of candidate datasets, and
update metadata through collaborative platforms such as GitHub and Zenodo. Replication packages
and interactive dashboards further support external validation, creating open feedback loops that allow
the process to evolve in tandem with community needs. To enable customization of the visualizations
ofered in CHeCLOUD, we publicly released the code for generating thematic LOD sub-clouds and
rendering dataset-related quality scores (https://github.com/isislab-unisa/Systematic-Dataset-Review).</p>
      <p>Nonetheless, several challenges remain. Persistent issues include heterogeneous and incomplete
metadata, the absence of persistent identifiers, and the need to tailor discovery and inclusion strategies
across diverse data formats [31, 32]. The proposed use cases heavily rely on the LOD Cloud, while its
obsolescence and quality issues are well known in the literature [31, 32]. Moreover, the exponential
growth in both the volume and heterogeneity of available data underscores the urgency of robust
automated mechanisms for dataset discovery. While human oversight will remain indispensable for
ensuring contextual accuracy and final quality, sustainable and scalable dataset discoverability can
only be achieved by placing automation at the backbone of the process, complemented by community
expertise to ensure trust and relevance. These challenges highlight key avenues for future improvement,
including the development of more advanced automation pipelines, metadata enrichment techniques,
and reliable linking mechanisms to guarantee long-term usability and alignment with FAIR principles.</p>
    </sec>
    <sec id="sec-5">
      <title>Acknowledgment</title>
      <p>We thank Gabriele Tuozzo for publicly releasing the sub-cloud generation code and for valuable
discussions that informed this work.</p>
    </sec>
    <sec id="sec-6">
      <title>Declaration on Generative AI</title>
      <p>During the preparation of this work, the author used ChatGPT in order to: Grammar and spelling check.
[19] P.-Y. Vandenbussche, J. Umbrich, L. Matteis, A. Hogan, C. Buil-Aranda, SPARQLES: Monitoring
public SPARQL endpoints, Semantic web 8 (2017) 1049–1065. doi:10.3233/SW-170254.
[20] A. Lieto, M. A. Pellegrino, G. Tuozzo, The FAIRness of CHeCLOUD, the cultural heritege linked
open data cloud, Semantic web (2025). URL: https://www.semantic-web-journal.net/content/
fairness-checloud-cultural-heritage-linked-open-data-cloud, [Under review].
[21] K. R. Felizardo, J. C. Carver, Automating systematic literature review, Contemporary empirical
methods in software engineering (2020) 327–355. doi:10.1007/s00607-023-01181-x.
[22] K. R. Felizardo, M. S. Lima, A. Deizepe, T. U. Conte, I. Steinmacher, ChatGPT application in
systematic literature reviews in software engineering: an evaluation of its accuracy to support the
selection activity, in: Proceedings of the 18th ACM/IEEE International Symposium on Empirical
Software Engineering and Measurement, 2024, pp. 25–36. doi:10.1145/3674805.3686666.
[23] J. de la Torre-López, A. Ramírez, J. R. Romero, Artificial intelligence to automate the
systematic review of scientific literature, Computing 105 (2023) 2171–2194. doi: 10.1007/
s00607-023-01181-x.
[24] F. Osborne, H. Muccini, P. Lago, E. Motta, Reducing the efort for systematic reviews in software
engineering, Data Science 2 (2019) 311–340. doi:10.3233/DS-190019.
[25] F. Octaviano, K. R. Felizardo, S. C. Fabbri, B. M. Napoleão, F. Petrillo, S. Hallé, SCAS-AI: a strategy
to semi-automate the initial selection task in systematic literature reviews, in: 2022 48th Euromicro
Conference on Software Engineering and Advanced Applications (SEAA), IEEE, 2022, pp. 483–490.
doi:10.1109/SEAA56994.2022.00080.
[26] S. Götz, Supporting systematic literature reviews in computer science: The systematic literature
review toolkit, in: Proceedings of the 21st ACM/IEEE International Conference on Model Driven
Engineering Languages and Systems: Companion Proceedings, 2018, pp. 22–26. doi:10.1145/
3270112.3270117.
[27] P. Esposito, M. A. Pellegrino, G. Tuozzo, FAIRness of the Linguistic Linked Open Data Cloud: an
Empirical Investigation, Special Issue on Data quality dimensions in Data FAIRification design
and processes in the Journal of Data and Information Quality (JDIQ) (2025).
[28] C. Chiarcos, S. Hellmann, S. Nordhof, Linking Linguistic Resources: Examples from the Open</p>
      <p>Linguistics Working Group, 2012, pp. 201–216. doi:10.1007/978-3-642-28249-2_19.
[29] A. Hasnain, S. Sana E Zainab, M. Kamdar, Q. Mehmood, C. Warren, Jr, Q. Fatimah, H. Deus,
M. Mehdi, S. Decker, A roadmap for navigating the life sciences linked open data cloud, 2014.
doi:10.1007/978-3-319-15615-6_8.
[30] G. Tuozzo, M. A. Pellegrino, A. Lieto, CHeCLOUD—the cultural heritage linked open data cloud,
in: International Semantic Web Conference ISWC - Poster&amp;Demo, 2025.
[31] J. Debattista, C. Lange, S. Auer, D. Cortis, Evaluating the quality of the LOD cloud: An empirical
investigation, Semantic Web 9 (2018) 859–901. doi:10.3233/SW-180306.
[32] T. Gabriele, Navigating the LOD Subclouds: Assessing Linked Open Data Quality by Domain,
in: Companion Proceedings of the Web Conference, Association for Computing Machinery, New
York, NY, USA, 2025. doi:10.1145/3701716.3717569.</p>
    </sec>
  </body>
  <back>
    <ref-list>
      <ref id="ref1">
        <mixed-citation>
          [1]
          <string-name>
            <given-names>K.</given-names>
            <surname>Petersen</surname>
          </string-name>
          ,
          <string-name>
            <given-names>S.</given-names>
            <surname>Vakkalanka</surname>
          </string-name>
          ,
          <string-name>
            <given-names>L.</given-names>
            <surname>Kuzniarz</surname>
          </string-name>
          ,
          <article-title>Guidelines for conducting systematic mapping studies in software engineering: An update</article-title>
          ,
          <source>Information and software technology 64</source>
          (
          <year>2015</year>
          )
          <fpage>1</fpage>
          -
          <lpage>18</lpage>
          . doi:
          <volume>10</volume>
          . 1016/j.infsof.
          <year>2015</year>
          .
          <volume>03</volume>
          .007.
        </mixed-citation>
      </ref>
      <ref id="ref2">
        <mixed-citation>
          [2]
          <string-name>
            <given-names>B.</given-names>
            <surname>Barn</surname>
          </string-name>
          ,
          <string-name>
            <given-names>S.</given-names>
            <surname>Barat</surname>
          </string-name>
          , T. Clark,
          <article-title>Conducting systematic literature reviews and systematic mapping studies</article-title>
          ,
          <source>in: Proceedings of the 10th innovations in software engineering conference</source>
          ,
          <year>2017</year>
          , pp.
          <fpage>212</fpage>
          -
          <lpage>213</lpage>
          . doi:
          <volume>10</volume>
          .1145/3021460.3021489.
        </mixed-citation>
      </ref>
      <ref id="ref3">
        <mixed-citation>
          [3]
          <string-name>
            <given-names>A. C.</given-names>
            <surname>Tricco</surname>
          </string-name>
          ,
          <string-name>
            <given-names>E.</given-names>
            <surname>Lillie</surname>
          </string-name>
          ,
          <string-name>
            <given-names>W.</given-names>
            <surname>Zarin</surname>
          </string-name>
          ,
          <string-name>
            <surname>K. K. O'Brien</surname>
            ,
            <given-names>H.</given-names>
          </string-name>
          <string-name>
            <surname>Colquhoun</surname>
            ,
            <given-names>D.</given-names>
          </string-name>
          <string-name>
            <surname>Levac</surname>
            ,
            <given-names>D.</given-names>
          </string-name>
          <string-name>
            <surname>Moher</surname>
            ,
            <given-names>M. D.</given-names>
          </string-name>
          <string-name>
            <surname>Peters</surname>
            ,
            <given-names>T.</given-names>
          </string-name>
          <string-name>
            <surname>Horsley</surname>
            ,
            <given-names>L.</given-names>
          </string-name>
          <string-name>
            <surname>Weeks</surname>
          </string-name>
          , et al.,
          <article-title>PRISMA extension for scoping reviews (PRISMA-ScR): checklist and explanation</article-title>
          ,
          <source>Annals of internal medicine 169</source>
          (
          <year>2018</year>
          )
          <fpage>467</fpage>
          -
          <lpage>473</lpage>
          . doi:
          <volume>10</volume>
          .7326/M18-0850.
        </mixed-citation>
      </ref>
      <ref id="ref4">
        <mixed-citation>
          [4]
          <string-name>
            <given-names>H.</given-names>
            <surname>Arksey</surname>
          </string-name>
          ,
          <string-name>
            <surname>L.</surname>
          </string-name>
          <article-title>O'malley, Scoping studies: towards a methodological framework</article-title>
          ,
          <source>International journal of social research methodology 8</source>
          (
          <year>2005</year>
          )
          <fpage>19</fpage>
          -
          <lpage>32</lpage>
          . doi:
          <volume>10</volume>
          .1080/1364557032000119616.
        </mixed-citation>
      </ref>
      <ref id="ref5">
        <mixed-citation>
          [5]
          <string-name>
            <given-names>C.</given-names>
            <surname>Wohlin</surname>
          </string-name>
          ,
          <article-title>Guidelines for snowballing in systematic literature studies and a replication in software engineering</article-title>
          ,
          <source>in: Proceedings of the 18th international conference on evaluation and assessment in software engineering</source>
          ,
          <year>2014</year>
          , pp.
          <fpage>1</fpage>
          -
          <lpage>10</lpage>
          . doi:
          <volume>10</volume>
          .1145/2601248.2601268.
        </mixed-citation>
      </ref>
      <ref id="ref6">
        <mixed-citation>
          [6]
          <string-name>
            <given-names>D.</given-names>
            <surname>Budgen</surname>
          </string-name>
          ,
          <string-name>
            <given-names>P.</given-names>
            <surname>Brereton</surname>
          </string-name>
          ,
          <article-title>Performing systematic literature reviews in software engineering</article-title>
          ,
          <source>in: Proceedings of the 28th international conference on Software engineering</source>
          ,
          <year>2006</year>
          , pp.
          <fpage>1051</fpage>
          -
          <lpage>1052</lpage>
          . doi:
          <volume>10</volume>
          .1145/1134285.1134500.
        </mixed-citation>
      </ref>
      <ref id="ref7">
        <mixed-citation>
          [7]
          <string-name>
            <given-names>M. J.</given-names>
            <surname>Page</surname>
          </string-name>
          ,
          <string-name>
            <given-names>J. E.</given-names>
            <surname>McKenzie</surname>
          </string-name>
          ,
          <string-name>
            <given-names>P. M.</given-names>
            <surname>Bossuyt</surname>
          </string-name>
          , I. Boutron,
          <string-name>
            <given-names>T. C.</given-names>
            <surname>Hofmann</surname>
          </string-name>
          ,
          <string-name>
            <given-names>C. D.</given-names>
            <surname>Mulrow</surname>
          </string-name>
          ,
          <string-name>
            <given-names>L.</given-names>
            <surname>Shamseer</surname>
          </string-name>
          ,
          <string-name>
            <given-names>J. M.</given-names>
            <surname>Tetzlaf</surname>
          </string-name>
          ,
          <string-name>
            <given-names>E. A.</given-names>
            <surname>Akl</surname>
          </string-name>
          ,
          <string-name>
            <given-names>S. E.</given-names>
            <surname>Brennan</surname>
          </string-name>
          , et al.,
          <source>The PRISMA</source>
          <year>2020</year>
          statement
          <article-title>: an updated guideline for reporting systematic reviews</article-title>
          ,
          <source>British Medical Journal (BMJ) 372</source>
          (
          <year>2021</year>
          ). doi:
          <volume>10</volume>
          .1136/bmj.n71.
        </mixed-citation>
      </ref>
      <ref id="ref8">
        <mixed-citation>
          [8]
          <string-name>
            <given-names>J. F.</given-names>
            <surname>Wolfswinkel</surname>
          </string-name>
          ,
          <string-name>
            <given-names>E.</given-names>
            <surname>Furtmueller</surname>
          </string-name>
          ,
          <string-name>
            <given-names>C. P.</given-names>
            <surname>Wilderom</surname>
          </string-name>
          ,
          <article-title>Using grounded theory as a method for rigorously reviewing literature</article-title>
          ,
          <source>European journal of information systems 22</source>
          (
          <year>2013</year>
          )
          <fpage>45</fpage>
          -
          <lpage>55</lpage>
          . doi:
          <volume>10</volume>
          .1057/ ejis.
          <year>2011</year>
          .
          <volume>51</volume>
          .
        </mixed-citation>
      </ref>
      <ref id="ref9">
        <mixed-citation>
          [9]
          <string-name>
            <given-names>Y.</given-names>
            <surname>Xiao</surname>
          </string-name>
          ,
          <string-name>
            <surname>M.</surname>
          </string-name>
          <article-title>Watson, Guidance on conducting a systematic literature review</article-title>
          ,
          <source>Journal of planning education and research 39</source>
          (
          <year>2019</year>
          )
          <fpage>93</fpage>
          -
          <lpage>112</lpage>
          . doi:
          <volume>10</volume>
          .1177/0739456X17723971.
        </mixed-citation>
      </ref>
      <ref id="ref10">
        <mixed-citation>
          [10]
          <string-name>
            <given-names>A.</given-names>
            <surname>Booth</surname>
          </string-name>
          ,
          <string-name>
            <given-names>M.</given-names>
            <surname>Martyn-St James</surname>
          </string-name>
          ,
          <string-name>
            <given-names>M.</given-names>
            <surname>Clowes</surname>
          </string-name>
          ,
          <string-name>
            <given-names>A.</given-names>
            <surname>Sutton</surname>
          </string-name>
          ,
          <article-title>Systematic approaches to a successful literature review</article-title>
          ,
          <source>SAGE Publications Ltd</source>
          ,
          <year>2021</year>
          . URL: https://digital.casalini.it/9781529759648.
        </mixed-citation>
      </ref>
      <ref id="ref11">
        <mixed-citation>
          [11]
          <string-name>
            <given-names>J. v.</given-names>
            <surname>Brocke</surname>
          </string-name>
          ,
          <string-name>
            <given-names>A.</given-names>
            <surname>Simons</surname>
          </string-name>
          ,
          <string-name>
            <given-names>B.</given-names>
            <surname>Niehaves</surname>
          </string-name>
          ,
          <string-name>
            <given-names>B.</given-names>
            <surname>Niehaves</surname>
          </string-name>
          ,
          <string-name>
            <given-names>K.</given-names>
            <surname>Riemer</surname>
          </string-name>
          ,
          <string-name>
            <given-names>R.</given-names>
            <surname>Plattfaut</surname>
          </string-name>
          ,
          <string-name>
            <given-names>A.</given-names>
            <surname>Cleven</surname>
          </string-name>
          ,
          <article-title>Reconstructing the giant: On the importance of rigour in documenting the literature search process</article-title>
          ,
          <source>European Conference on Information Systems</source>
          (
          <year>2009</year>
          ). URL: https://aisel.aisnet.org/cgi/viewcontent.cgi? article=1145&amp;context=ecis2009.
        </mixed-citation>
      </ref>
      <ref id="ref12">
        <mixed-citation>
          [12]
          <string-name>
            <given-names>S.</given-names>
            <surname>Keele</surname>
          </string-name>
          , et al.,
          <article-title>Guidelines for performing systematic literature reviews in software engineering</article-title>
          ,
          <source>Technical Report, Technical report, ver. 2.3 ebse</source>
          ,
          <year>2007</year>
          . URL: https://shorturl.at/Z19ct.
        </mixed-citation>
      </ref>
      <ref id="ref13">
        <mixed-citation>
          [13]
          <string-name>
            <given-names>V.</given-names>
            <surname>Garousi</surname>
          </string-name>
          ,
          <string-name>
            <given-names>M.</given-names>
            <surname>Felderer</surname>
          </string-name>
          ,
          <string-name>
            <given-names>M. V.</given-names>
            <surname>Mäntylä</surname>
          </string-name>
          ,
          <article-title>Guidelines for including grey literature and conducting multivocal literature reviews in software engineering</article-title>
          ,
          <source>Information and software technology 106</source>
          (
          <year>2019</year>
          )
          <fpage>101</fpage>
          -
          <lpage>121</lpage>
          . doi:
          <volume>10</volume>
          .1016/j.infsof.
          <year>2018</year>
          .
          <volume>09</volume>
          .006.
        </mixed-citation>
      </ref>
      <ref id="ref14">
        <mixed-citation>
          [14]
          <string-name>
            <given-names>A.</given-names>
            <surname>Jacobsen</surname>
          </string-name>
          , R. de Miranda Azevedo,
          <string-name>
            <given-names>N.</given-names>
            <surname>Juty</surname>
          </string-name>
          ,
          <string-name>
            <given-names>D.</given-names>
            <surname>Batista</surname>
          </string-name>
          ,
          <string-name>
            <given-names>S.</given-names>
            <surname>Coles</surname>
          </string-name>
          ,
          <string-name>
            <given-names>R.</given-names>
            <surname>Cornet</surname>
          </string-name>
          ,
          <string-name>
            <given-names>M.</given-names>
            <surname>Courtot</surname>
          </string-name>
          ,
          <string-name>
            <given-names>M.</given-names>
            <surname>Crosas</surname>
          </string-name>
          ,
          <string-name>
            <given-names>M.</given-names>
            <surname>Dumontier</surname>
          </string-name>
          ,
          <string-name>
            <given-names>C. T.</given-names>
            <surname>Evelo</surname>
          </string-name>
          , et al.,
          <source>FAIR principles: interpretations and implementation considerations</source>
          ,
          <year>2020</year>
          . doi:
          <volume>10</volume>
          .1162/dint_r_
          <fpage>00024</fpage>
          .
        </mixed-citation>
      </ref>
      <ref id="ref15">
        <mixed-citation>
          [15]
          <string-name>
            <given-names>T.</given-names>
            <surname>Berners-Lee</surname>
          </string-name>
          ,
          <fpage>5</fpage>
          -star deployment scheme,
          <year>2012</year>
          . URL: https://5stardata.info/, [Online]
          <article-title>Last access 2025, July</article-title>
          .
        </mixed-citation>
      </ref>
      <ref id="ref16">
        <mixed-citation>
          [16]
          <string-name>
            <given-names>A.</given-names>
            <surname>Gaignard</surname>
          </string-name>
          ,
          <string-name>
            <given-names>T.</given-names>
            <surname>Rosnet</surname>
          </string-name>
          ,
          <string-name>
            <given-names>F.</given-names>
            <surname>De Lamotte</surname>
          </string-name>
          ,
          <string-name>
            <given-names>V.</given-names>
            <surname>Lefort</surname>
          </string-name>
          ,
          <string-name>
            <surname>M.-D. Devignes</surname>
          </string-name>
          , FAIR-Checker:
          <article-title>supporting digital resource findability and reuse with knowledge graphs and semantic web standards</article-title>
          ,
          <source>Journal of Biomedical Semantics</source>
          <volume>14</volume>
          (
          <year>2023</year>
          )
          <article-title>7</article-title>
          . doi:
          <volume>10</volume>
          .1186/s13326-023-00289-5.
        </mixed-citation>
      </ref>
      <ref id="ref17">
        <mixed-citation>
          [17]
          <string-name>
            <given-names>M. A.</given-names>
            <surname>Pellegrino</surname>
          </string-name>
          ,
          <string-name>
            <given-names>A.</given-names>
            <surname>Rula</surname>
          </string-name>
          , G. Tuozzo,
          <string-name>
            <surname>KGHeartBeat:</surname>
          </string-name>
          <article-title>An open source tool for periodically evaluating the quality of knowledge graphs</article-title>
          , in: International Semantic Web Conference, Springer,
          <year>2024</year>
          , pp.
          <fpage>40</fpage>
          -
          <lpage>58</lpage>
          . doi:
          <volume>10</volume>
          .1007/978-3-
          <fpage>031</fpage>
          -77847-
          <issue>6</issue>
          _
          <fpage>3</fpage>
          .
        </mixed-citation>
      </ref>
      <ref id="ref18">
        <mixed-citation>
          [18]
          <string-name>
            <given-names>Y.</given-names>
            <surname>Sun</surname>
          </string-name>
          ,
          <string-name>
            <given-names>Y.</given-names>
            <surname>Yang</surname>
          </string-name>
          ,
          <string-name>
            <given-names>H.</given-names>
            <surname>Zhang</surname>
          </string-name>
          , W. Zhang,
          <string-name>
            <given-names>Q.</given-names>
            <surname>Wang</surname>
          </string-name>
          ,
          <article-title>Towards evidence-based ontology for supporting systematic literature review</article-title>
          ,
          <source>in: 16th International Conference on Evaluation Assessment in Software Engineering (EASE)</source>
          ,
          <year>2012</year>
          , pp.
          <fpage>171</fpage>
          -
          <lpage>175</lpage>
          . doi:
          <volume>10</volume>
          .1049/ic.
          <year>2012</year>
          .
          <volume>0022</volume>
          .
        </mixed-citation>
      </ref>
    </ref-list>
  </back>
</article>