<!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>Big Data Value Graph: Enhancing Security and Generating New Value from Big Data</article-title>
      </title-group>
      <contrib-group>
        <contrib contrib-type="author">
          <string-name>Massimiliano Gervasi</string-name>
          <xref ref-type="aff" rid="aff0">0</xref>
          <xref ref-type="aff" rid="aff3">3</xref>
        </contrib>
        <contrib contrib-type="author">
          <string-name>Nicolò G. Totaro</string-name>
          <xref ref-type="aff" rid="aff0">0</xref>
          <xref ref-type="aff" rid="aff3">3</xref>
        </contrib>
        <contrib contrib-type="author">
          <string-name>Anna Fornaio</string-name>
          <xref ref-type="aff" rid="aff1">1</xref>
        </contrib>
        <contrib contrib-type="author">
          <string-name>Danilo Caivano</string-name>
          <xref ref-type="aff" rid="aff2">2</xref>
        </contrib>
        <aff id="aff0">
          <label>0</label>
          <institution>Centre for Applied Mathematics and Physics for Industry (CAMPI), University of Salento</institution>
          ,
          <addr-line>Lecce</addr-line>
          ,
          <country country="IT">Italy</country>
        </aff>
        <aff id="aff1">
          <label>1</label>
          <institution>Cybersecurity Research Lab - CRLab, University of Salento</institution>
          ,
          <addr-line>Lecce</addr-line>
          ,
          <country country="IT">Italy</country>
        </aff>
        <aff id="aff2">
          <label>2</label>
          <institution>Department of Computer Science, University of Bari “Aldo Moro”</institution>
          ,
          <addr-line>Bari</addr-line>
          ,
          <country country="IT">Italy</country>
        </aff>
        <aff id="aff3">
          <label>3</label>
          <institution>Department of Innovation Engineering, University of Salento</institution>
          ,
          <addr-line>Lecce</addr-line>
          ,
          <country country="IT">Italy</country>
        </aff>
      </contrib-group>
      <abstract>
        <p>The opportunity to extract value from data has become a key capability for organisations, especially with the spread of Big Data. The Data Mesh is a model that proposes a solution for Big Data management. In this paper, we propose that the integration of this model with the Big Data Value Chain can provide benefits for organisations participating in the mesh. The two main benefits relate to security and Value Generation. The new framework resulting from this merging allows to increase the level of security and the Value Generated for participants. Throughout the paper, the concepts of Big Data and Data Mesh will be introduced. Then, our proposed integration and how it can positively afect the levels of security and the results of Value Generation will be explained.</p>
      </abstract>
      <kwd-group>
        <kwd>eol&gt;Data Mesh</kwd>
        <kwd>Big Data</kwd>
        <kwd>Accountability</kwd>
        <kwd>Integrity</kwd>
        <kwd>Value Creation</kwd>
      </kwd-group>
    </article-meta>
  </front>
  <body>
    <sec id="sec-1">
      <title>1. Introduction</title>
      <p>
        Data have economic value, and the capacity to extract it is becoming a key feature for
organisations [
        <xref ref-type="bibr" rid="ref1">1</xref>
        ]. This relevance transformed the opportunity of extracting Value from Big
Data into an imperative to establish or remain competitive [
        <xref ref-type="bibr" rid="ref2">2</xref>
        ]. Typical characteristics of Big
Data frameworks have been identified in the literature. The first aspect to be considered is
related to data availability, to which the creation of Value is linked [
        <xref ref-type="bibr" rid="ref3">3</xref>
        ]. On the other hand,
security paradigms favour data sharing only between organisations working in a common
direction [
        <xref ref-type="bibr" rid="ref2">2</xref>
        ]. A second aspect is related to the Value Generated according to the paradigm
Value( + ) &gt; Value() + Value(), as reported in [
        <xref ref-type="bibr" rid="ref4">4</xref>
        ], applied to the Big Data context. This
can also be extended to the cost and resource consumption that a Big Data initiative requires,
as sharing resources could lead to cost savings. Applying the previous paradigm and specifying
it to costs, we get Cost( + ) &lt; Cost() + Cost(), as verified in [
        <xref ref-type="bibr" rid="ref5 ref6 ref7">5, 6, 7</xref>
        ].
Focusing on security, there are two fundamental aspects that are worth of note regarding the
approach to the confederation of diferent organisations sharing resources: the first aspect is the
need to safeguard through a collective bargaining agreement the methodology of collaboration
and resource sharing between diferent organisations [
        <xref ref-type="bibr" rid="ref5 ref6">5, 6</xref>
        ]. The second concern regards the
way to ensure security in such large perimeters with several independent actors.
      </p>
      <p>In response to the proposed requirements and the considerations, a new architecture was
identified in the literature, namely, the Data Mesh, which will be explored in more detail in one
of the next section. We propose to integrate the Data Mesh model with Big Data Value Chain
model to combine the enhancement of security approaches in data and technology sharing with
the identification of processes that can generate value from Big Data. The resulting framework
brings two major benefits: first, an enhanced level of security during the generation of Data
Products through the adherence to the Data Mesh Governance; then, an increase in the Value
Generated for each of them, since both data and technologies are mapped into a network
structure where observable quantities (e.g. KPI) can be attributed to both nodes (individual
products) and processes.</p>
      <p>The scope of this work is the definition of a basis for proper modelling data and technology
sharing. In Section 2, the state of the art concerning Big Data, its security and the associated
value chain is explained. Section 3 introduces the Data Mesh model and briefly explains its
operating principles. Section 4 sets out the basis of our proposal and the research questions it
addresses. A new relational structure is illustrated in Section 5 to formalize the expected benefits
of the proposed framework in terms of security, which are described in Section 6, together with
security-related implementation aspects. Conclusions are drawn in Section 7.</p>
    </sec>
    <sec id="sec-2">
      <title>2. State of the art</title>
      <sec id="sec-2-1">
        <title>2.1. Big Data and its security issues</title>
        <p>
          In literature, Big Data are often defined according to their characteristics or features called V’s
of Big Data. The original definition included three V’s, namely Volume, Variety and Velocity
and was first introduced in [
          <xref ref-type="bibr" rid="ref8">8</xref>
          ]. Since then, many V’s have been added to the domain in order
to refine the very definition of Big Data, up to 56, see e.g. [
          <xref ref-type="bibr" rid="ref10 ref11 ref12 ref13 ref9">9, 10, 11, 12, 13</xref>
          ]. The security of
Big Data is a critical issue for organisations using this technology. The amount and variety of
data collected makes it necessary to pay more attention to its security. The main focus is on
data management and protection, regulatory compliance and risk management. The level of
security of Big Data is reflected in one of the V’s that characterize it, which is the Vulnerability
[
          <xref ref-type="bibr" rid="ref13">13</xref>
          ]. This depends on the protection barriers put in place in defence of the data. But the level of
security to be ensured depends on another V, the Value. Naturally, the greater the sum of the
value of the data held, the greater must be its protection. The value of Big Data also derives
from the correlations that can be made with it, given the large volumes available. In [
          <xref ref-type="bibr" rid="ref14">14</xref>
          ] is
described how it is necessary to find an optimal balance between data quality and data security.
        </p>
        <p>
          Numerous studies have delved into security analysis for Big Data. In [
          <xref ref-type="bibr" rid="ref15">15</xref>
          ] the phases and
characteristics of Big Data are studied to analyse what security requirements they need. The five
requirements identified are: confidentiality, eficiency, authenticity, availability, integrity. In [
          <xref ref-type="bibr" rid="ref16">16</xref>
          ]
there is a framework containing the most interesting threats and challenges in Big Data security.
Some possible approaches are encryption, access control mechanisms, authentication and
authorization, anomaly-based network intrusion detection and Machine Learning techniques.
In [
          <xref ref-type="bibr" rid="ref16">16</xref>
          ] are also described the main problems and attacks, as well as some solutions adopted to
protect infrastructure, privacy, and data integrity. Security systems are implemented to protect
the flow of data input and output for each element, so that each data packet in transit meets
privacy and security standards, is congruent and integral. The security system provided for
both input and output communication flows, together with mechanisms to defend the protocols
of the communication itself, is designed to counter any man-in-the-middle attacks. The layers
of protection can ensure that the data in transit are indeed the correct data in various ways. For
instance, the use of artificial intelligence could allow a check on possible pollution or repetition
of data. AI could also check the size of data in transit, to prevent DoS-type attacks. This
system of multiple layers of protection is known as defence-in-depth. As described in [
          <xref ref-type="bibr" rid="ref17">17</xref>
          ], this
methodology consists of applying distinct levels of security mechanisms, creating a redundancy
that provides protection even if one of these barriers is breached.
        </p>
        <p>From these studies it can be understood that to ensure data security, even in the Big Data
Value Chain, multiple security measures must be implemented. Furthermore, it is important
that organisations adopt a security culture that encourages the adoption of secure practices by
all employees.</p>
      </sec>
      <sec id="sec-2-2">
        <title>2.2. Big Data Value Chain</title>
        <p>
          Value, although considered as a V’s of Big Data, must be understood as an atypical feature
insofar as it relates more to the use of the data and not to its characteristics. In this regard,
in [
          <xref ref-type="bibr" rid="ref18">18</xref>
          ] is distinguished Value from other V’s, separating the concept of Big Data from its use
and attributing to this nexus the real reason for the inconsistency of Big Data definitions in
the literature. In reference to Big Data modelling the processes, we find direct reference to the
Value Chain of Porter [
          <xref ref-type="bibr" rid="ref19">19</xref>
          ], and also to [
          <xref ref-type="bibr" rid="ref20 ref21 ref22 ref23">20, 21, 22, 23</xref>
          ]. In [
          <xref ref-type="bibr" rid="ref19">19</xref>
          ] the type of resources used in its
activities are material resources that organisations can observe and are useful in production. In
[
          <xref ref-type="bibr" rid="ref24">24</xref>
          ], the set of resources includes intangible ones, as information, that managers can capture
from the virtual world and use them to generate Value. In [
          <xref ref-type="bibr" rid="ref24">24</xref>
          ], is theorized the Virtual Value
Chain, whose main activities are: gathering, organizing, selecting, synthesizing, and distributing.
As reported in [
          <xref ref-type="bibr" rid="ref23">23</xref>
          ]: “The Virtual Value Chain framework is perfectly applicable in a Big Data
context”, concept confirmed in [
          <xref ref-type="bibr" rid="ref25 ref26 ref27">25, 26, 27</xref>
          ].
        </p>
        <p>
          From the Virtual Value Chain, in line with the Process View, meaning with a focus on processes
that enable the generation of value, and moving from the framework in [
          <xref ref-type="bibr" rid="ref23">23</xref>
          ], Wu et al. [
          <xref ref-type="bibr" rid="ref28">28</xref>
          ]
extended Ackof’s Data-Information-Knowledge-Wisdom (DIKW) model [
          <xref ref-type="bibr" rid="ref29">29</xref>
          ] in the RDIKW
model, specialising the diferent phases of the Virtual Value Chain according to the capabilities
generated by the resources and required in the diferent phases of the Big Data initiatives. For
more details, see Figure 1. Here, of special interest is the division of the initiatives into two
phases: Big Data Capitalization and Big Data Exploitation, which separate into two distinct
macro-areas the steps necessary to extract value from the data. Namely, phases of generation
and transformation to a usable format, from the subsequent phases dedicated to analytics. The
two areas difer in the modelling of value-added processes, in techniques used, in skills required
and in costs to be incurred for the activities. Although the distinction is clear, the Exploitation
phase is highly dependent on the previous one, in fact the data analytics changes depending
on the granularity chosen in the Capitalization phase, as well as the type of ETL and data
cleaning adopted. The two areas can also be distinguished because data are obtained at the end
of Capitalization for consumption in Exploitation, but actors involved are not always the same,
and this leads to strategic misalignments and high consumption of resources.
        </p>
      </sec>
    </sec>
    <sec id="sec-3">
      <title>3. Data Mesh</title>
      <p>
        The Data Mesh was introduced by Dehghani [
        <xref ref-type="bibr" rid="ref3">3</xref>
        ] as a shift from centralized architectures based
on five themes. Organisation goes from a centralized data ownership to a decentralized model,
which links the ownership and responsibility of the data to the domains of source. Architecture
moves from monolithic data collection in Data Warehouse and Data Lake [
        <xref ref-type="bibr" rid="ref30 ref31">30, 31</xref>
        ] to the data
connection through distributed network. Technologies moves from technological solutions that
treat data as a sub-product of the execution of a code pipeline, to ones that treat data and the
code that handles it as a single autonomous unit. Operational model shifts data Governance
from a centralized top-down operational model with human intervention to a federated model
with computational policies embedded in the network domains. Principle shifts the system of
value association away from data seen only as a resource to be collected with its limitations
(as low quality, redundancy, dificulty of retrieval, use of diferent formats and targeting to a
specific use) to data as a product to be shared. The architecture is based on the presence of
several actors, called domains, which may represent entire organisations or individual business
units. The domains would therefore have lower total costs than the sum of the costs they would
have acting individually, as described in [
        <xref ref-type="bibr" rid="ref4 ref5 ref6">4, 5, 6</xref>
        ]. In the case of selling data to actors outside the
Data Mesh, domains could generate DPSs according to customer requirements, thus providing
a highly customized product. Here we introduce the four fundamental principles on which it is
based the Data Mesh [
        <xref ref-type="bibr" rid="ref3">3</xref>
        ].
1 - Domain-oriented decentralized data ownership and architecture: the Data Mesh
requires the decentralisation of data sharing ownership to the reference domains. Each domain
has a team of experts covering every area of data management and of ETL processes, so they
can work completely independently.
2 - Data as a product: to be considered a Data Product (DP), data must adhere to some rules
of usability, feasibility, and be valuable. Usability characteristics include: meeting predefined
quality metrics and formats, being user-friendly and understandable, being easily accessible by
any user, and being interoperable and unified with data from other domains. Each individual
DP must also fulfil the DATSIS principles [
        <xref ref-type="bibr" rid="ref32">32</xref>
        ] being: discoverable, addressable, trustworthy,
self-describing, interoperable, and secure. We define DP as primitives (DPP) if derived from a
domain and secondaries (DPS) if obtained from the elaboration of one or more DPs.
      </p>
      <sec id="sec-3-1">
        <title>3 - Self-serve data infrastructure as a platform: a self-service data platform to enable</title>
        <p>
          the domains’ teams to store and manage DPs throughout their life cycle, manage the network
connection of DPs, and share knowledge that is extracted from the information on the network
[
          <xref ref-type="bibr" rid="ref3">3</xref>
          ]. As can be seen in [
          <xref ref-type="bibr" rid="ref32">32</xref>
          ], users can view DPs on a Data Mesh Catalogue, which presents the
DPs stored in the Data Mesh Catalogue Storage, where DPs of any level are stored.
4 - Federated computational Governance: autonomy over data management is granted
to each domain, but they must follow common processes and rules in order to obtain data in
the predetermined format and at a minimum quality level. Governance federation thus seeks
to balance the autonomy and agility of the domains, while guaranteeing the interoperability,
security and global conformity of the network.
        </p>
      </sec>
      <sec id="sec-3-2">
        <title>3.1. Data Mesh Application Examples</title>
        <p>
          As the Data Mesh is a recently theorized model, there is still limited literature on use cases.
In [
          <xref ref-type="bibr" rid="ref32">32</xref>
          ], the architectures of Netflix and Zalando after the implementation of the Data Mesh
are illustrated. In [
          <xref ref-type="bibr" rid="ref33">33</xref>
          ], various examples of model implementation with various technologies
are reported, including Google Cloud, AWS, Databricks, and Kafka. In particular, in the book
there is a summary table for each technology, with a brief description of it, the pros and cons,
and a suggestion as to which type of organisation would be preferable to apply each of them.
The use case of implementing the Data Mesh for Kafka is also taken up in [
          <xref ref-type="bibr" rid="ref34">34</xref>
          ], explaining how
Saxo Bank integrated Kafka mesh to achieve particular benefits. The bank had integrated Kafka
to be able to have real-time and high-quality data, but it was not enough. The integration of
the Data Mesh brought new data Governance and numerous benefits. It has increased data
quality through Governance, cataloguing and quality management processes. It reduced time
to market by facilitating the data search system. And finally, it has facilitated integration by
setting internationally followed standards.
        </p>
      </sec>
    </sec>
    <sec id="sec-4">
      <title>4. Proposal: merging Data Mesh and Big Data Value Chain to enhance secure sharing</title>
      <p>Our proposal is to integrate the Data Mesh within the Big Data Value Chain to enhance
identifying value along multiple value chains, and simultaneously the overall security of data
sharing. As the Data Mesh is a recent approach, the proposal also aims at strengthening relevant
security issues not yet addressed in the literature. The relevance of the security aspects in the
Data Mesh have been considered in [35], which mention how authorization and authentication
mechanisms are required in the Data Mesh. However, as reported in [36], there are other
security mechanisms that have to be ensured within a network: confidentiality, integrity,
nonrepudiation, access control, availability, and accountability. As the data value can increase in the
Data Mesh, as we argued above, an associate increase in the level of security for its protection
is required. Specifically, the main aspects of security we will focus on are accountability and
integrity. Accountability makes it possible to keep track of all the activities carried out in an
environment, starting from their origin, while integrity ensures that data are not modified in an
unwanted or unauthorized manner [36].</p>
      <p>Two main limitations arise when working with Big Data. The first is the management of
potential attacks or malfunctioning, which could make a DP inaccessible. The second issue is
harder to handle, as it does not relate to a failure of the information system, but to an improper
combination of DPs and technologies along a given value chain. In particular, data quality and
accountability can be granted along with technological performance, but their incompatibility
(e.g., improper application of methods for specific data types, lack of hypothesis verification)
may generate invalid inferences from their combination (insights, other products).</p>
      <p>Our proposal relies on a new representation model that allows for the allocation and
identification of Data Products creation together with their processing, through the use of Technology
Products. This representation relies on a relational network structure, i.e. a directed graph, that
helps to locate not only Data Products, but also the processes to extract information and value
from them, thus including technologies in the representation. Formally, this approach generates
two node attributions, adding Technology Products as a dual of the existing Data Products.
This approach also supports the traceability of data production, so that the diferent value
chains arising from Data Products can be securely accessed, e.g. relying on pseudonymization
protocols. In this way, we also enable the tracking of additional information of the multiple
data production processes that can be relevant when assessing the accountability of data in
relation to technologies, and vice versa.</p>
      <p>This data structure will be linked to the Data Mesh principles to foster an architectural
design for data and technology sharing and consumption in line with increasing data sources,
consumers, diversity of use cases, and access modes. As for security, this provides advantages
in terms of: (i.) increasing data veracity, by bridging the gap between the actual origin of data
and the details (where and when) of their sharing for analysis, which could be implemented
using current distributed ledger technologies; (ii.) allowing autonomy through clear contracts,
enforcing the Data Mesh Governance; (iii.) realize Governance requirements such as security,
privacy, and legal compliance; (iv.) fostering domain segregation as actions on specific DPs do
not afect other ones in diferent domains; (v.) maintain data integrity, as the network generates
new nodes when new Data Products are created instead of changing them, which reduces
the risks of corruption of existing Data Products. In addition to security benefits, operational
advantages in terms of optimal use of resources have to be underlined: (i.) optimization of
continuous change through localization of changes within domains; (ii.) cost reduction for
data ownership in a decentralized architecture; (iii.) reduced complexity of data management
and burden on domain teams in managing the life cycle of their DPs, as well as computational
capabilities necessary for Governance to find, access, build, or deploy a DP; (iv.) opportunity to
achieve higher-order value through aggregation and correlation of independent DPs.</p>
    </sec>
    <sec id="sec-5">
      <title>5. Big Data Value Graph (BDVG)</title>
      <p>Now we discuss more in-depth the proposal to merge the Data Mesh with the Big Data Value
Chain, generating a new framework that we call Big Data Value Graph. The reference
to graphs derives from the relationship between the various points in the new model. The
combination of these two elements would make it possible to increase the Value Generated
and to identify and reduce the costs associated with this generation. It could also be seen as a
generalisation of the current Big Data Value Chain. In fact, it is possible to regain the chain
when a single node participates in the mesh.</p>
      <p>
        The Big Data Value Chain is divided into two phases (Figure 1): Big Data Capitalization and Big
Data Exploitation. In the BDVG, the first phase is completely performed within the domains.
Here DPs assume the role that was of the data formats in the BDVC, they are the output
of the capitalization phase. In the Exploitation phase, the first step consists of aggregating
and correlating DPs, to extract new information and produce DPSs at the same time. Further
elements in the Exploitation phase correspond to those who collect the extracted information
to generate knowledge. This brings better decision-making, as it is based on more reliable and
more easily exploitable data, with consequences in reduction of costs and in increase of profits,
as described in [37, 38]. The edges in the BDVG are direct, and the terminal nodes in that
structure are functional to the representation of wisdom, understood as the ways in which an
organisation decides to integrate the knowledge it has obtained into its processes. This is why
the multiplicity of nodes in the Graph stops at the level of knowledge, given the individuality
of each organisation in the transformation of this into wisdom, thus abstracting it outside the
perimeter of the BDVG. The BDVG brings with it many benefits:
1) a Technology Mesh which fosters the union between the Data Mesh and the rest of the
Graph, allowing, through a series of technologies, the correct interaction between those in
charge of the Exploitation phase and those in charge of making DPs available. Just as Dehghani
proposes data as a product, in our model we also extend this concept to technologies. This is
because technological immaturity can afect the success of an initiative, such as in the creation
of assets [
        <xref ref-type="bibr" rid="ref23">23</xref>
        ]. We then define Technology Product software, algorithms, or more generally
services, including those ofered by platforms. Among the technologies present, in addition to
those needed for the Data Mesh, there will obviously be those needed for the elements dealing
with information and knowledge, such as, for example, analytical tools, data visualisation and
knowledge graphs. Just as for each DP there is a responsible, in the same way, a responsible is
identified for each Technology Product. The set of data and technologies would then constitute
the entire catalogue of products that could be shared and used within the mesh or sold to
external actors. Shared technologies may also be labelled to be contextualized to individual
use cases, each of which may be based on specific assumptions, constraints, and needs. The
concatenation process underlying the Technology Mesh and, more generally, the BDVG leads
to a compositional structure of the analysis techniques, which is not, in general, commutative;
so, the order in which they are used also afects the final result. The implementation of the
Technology Mesh also reduces the total cost to be incurred compared to the sum of the individual
costs, as these are amortized across several elements, following the principle in [
        <xref ref-type="bibr" rid="ref4">4</xref>
        ];
2) an architecture that favours the collaboration of diferent actors , even belonging to
separate organisations, in order to ensure access to and use of a wide variety of resources, as
desired in the literature [
        <xref ref-type="bibr" rid="ref2 ref7">2, 7</xref>
        ]. In addition to technology and data, the BDVG also provides for
the sharing of knowledge, skills, and competences. For example, the opportunity of having
numerous data analysis techniques that are easy to use makes it possible to reduce model risk
problems, thus minimising the influence that the use of a model has on the final result. On the
other hand, such measurable efects also make it possible to estimate latent constructs such as
skill and knowledge with appropriate analysis techniques;
3) a dynamic architecture, in order to adapt to the random nature of initiatives operating
in Big Data contexts. The requirements negotiations, typical of Big Data initiatives [39], is
facilitated through easier access to diferent and higher-level data and technologies, thanks to
the Data and Technology Mesh. They enable adaptation and scalability at diferent stages of
the initiative. The freedom granted by the dynamism of the architecture makes it possible to
envisage atomic activities of the initiative, even cyclical ones, in which testing and validation
phases are foreseen [39]. At such stages, it is necessary to leave freedom to domain experts
[40]. The cyclicity of the diferent phases is visible in various Big Data Frameworks such as in
[41, 42];
4) identify the Value Generated and the associated cost. In [
        <xref ref-type="bibr" rid="ref9">9, 43</xref>
        ], several criteria are find
to identify the Value Generated by Big Data. It derives from the benefits that an organisation
obtains from the integration of acquired knowledge within its systems, hence wisdom. In the
Graph, it is possible to derive the path that led to the generation of wisdom. It is not trivial
to calculate the Value Generated by every single element of the mesh that participated in
the initiative, as it is very complex to give a weight to the participation in the generation of
Value. Easier to identify is the cost associated with each arc of interaction, according to the
resources used. By comparing the final Value Generated with the sum of the costs along the
route, it is possible to understand whether the initiative ultimately brought added value to the
organisation, as well as analysing each point along the route to identify critical points in the
event of a failed initiative. In this way, it is also possible to correctly define for each element the
suggested retail price to actors outside the mesh. Recalling again the principle in [
        <xref ref-type="bibr" rid="ref4">4</xref>
        ], at the end
the Value Generated will be greater than the sum of the individual Values, while the total cost
will be less than the sum of the individual costs. At this point, the economic benefit of the
BDVG can be understood.
      </p>
      <p>To better understand point 4, we can observe Figure 2. It can be seen that at the  1.1 is
immediate to associate the corresponding cost. Thanks to the Graph all the products can be
associated with each interaction that took part in its creation. In this way, even for the  2.1
it is easy to calculate the associated costs, simply adding up the costs of all interactions that led
to its generation. In this way, the unit cost associated with knowledge creation can be reduced.
In fact, each element does not participate in the creation of a single block of knowledge, but
contributes to the creation of several, so that the cost can be amortized in the best possible way.</p>
      <p>In Figures 3-4, the BDVG is schematized. Governance, as visible in both images, manages
all the steps that take place in the Graph. In the first picture you can see how the Data and
Technology Mesh are integrated within the model, enabling the creation of Data Products and
Technology Products. In the second image we can see how the Graph has a multi-linear path
to the knowledge creation stage. As mentioned earlier, wisdom is outside the perimeters of
the Graph, as it is individual to each organisation. This image also shows a special case where
knowledge creation is reached via a linear path, which falls under the definition of the Big Data
Value Chain.</p>
    </sec>
    <sec id="sec-6">
      <title>6. Big Data Value Graph Security</title>
      <sec id="sec-6-1">
        <title>6.1. Data and Technology Accountability and Integrity</title>
        <p>In this work, we pay special attention to accountability and integrity in the BDVG. The path that
led to the creation of a given Data Product can be represented as in Figure 2. The path associated
with each individual DP is stored internally, and knowing this path enables the accountability
property to be fulfilled. In order to still have accountability of Data and Technology Products, and
thus study their paths backwards for verification and, potentially, make an anomaly detection
within the whole path, we can envisage a registry containing the scheme of all the paths
generated, together with the additional attributes and metadata functional to check their validity.
This scheme does not contain any DP, but merely stores the steps taken within the platform.
This register, preserving every edge of interaction of the BDVG, would ensure accountability
for the entire system.</p>
        <p>To enhance integrity, it is suficient to also keep track of the DPs hash. In this way, if the hash
remains unchanged, integrity is guaranteed along the path. Otherwise, if this is not respected,
the scheme can indicate the timestamp of the moment when the hash changed and, hence,
identify when the compromise occurred. To increase the security level of this log, distributed
ledger technology (DLT) could be used to increase the dificulty of a cyberattack. In this case,
security also depends on the type of technology chosen to implement the BDVG and its nodes.
DLT may be useful in the present scenario, depending on the transactions and consensus
protocols,as long as more than half of the nodes are not compromised.</p>
        <p>Accountability here relate to both data and technologies applied to obtain a product. In this
way, it is possible to always keep track of the data used, the technologies applied, and their
combination. The comparison of diferent results derived from the combination of the same data
with diferent technologies requires, in general, partial order structure: specifically, we cannot
assume a priori the comparability of diferent products and processes within the BDVG, which
involve multiple domains and value/security dimensions (here, integrity and accountability).
The lack of a total order underlying the comparison of data/technology production processes,
in fact, lead to a richer view where inequivalent evaluations can be highlighted by means of
order-theoretic approaches [44].</p>
      </sec>
      <sec id="sec-6-2">
        <title>6.2. Big Data Value Graph Security Challenges</title>
        <p>
          There is no unique recipe for the Data Mesh, its implementation can be declined following
various strategies. One of the elements that the diferent implementation strategies must
certainly have in common is the focus on security. The level and quality of security must
meet the standards that this architectural model provides. The integration of the Data Mesh
within the Big Data Value Chain forces a focus on new elements and changes in priorities. Data
Products have a higher level of quality and usability than data usually stored in databases. Their
higher expendability and reliability increases their value, and consequently their attractiveness
to cybercriminals. With the same level of security and volume of data, the level of risk associated
to attacks on DPs is higher than one associated to normal data. For this reason, the importance
of security becomes even more critical. This leads to numerous challenges to be solved to ensure
protection within the Big Data Value Graph. Dehghani [
          <xref ref-type="bibr" rid="ref3">3</xref>
          ] describes how the Data Mesh must
define five basic security points: access control, encryption, confidentiality levels, data retention,
regulations, and agreements.
        </p>
        <p>However, the Data Mesh model is a recent creation, which is why the security measures to
be taken to protect it are also in their infancy. There are various challenges to overcome,
concerning all the properties that must be secured in order to define a model as secure.</p>
      </sec>
    </sec>
    <sec id="sec-7">
      <title>7. Conclusions</title>
      <p>This paper proposes a new framework for value generation to increase the Value Generated and
improve security mechanisms. This solution involves the collaboration of diferent actors who
share resources and expertise. The paper analyses the mechanisms that bring these benefits to
member organisations. The focus on future developments could be on implementing additional
security systems that ensure the protection of the entire network, also integrating the Data
Mesh Governance with a knowledge base that enhances privacy [45]. The main objective of the
proposed BDVG is to create more value at a lower cost for its member organisations. In some
contexts, one could also think of selling Data and Technology Products to actors outside the
mesh, while respecting the rules governing these markets. The sale to actors outside the mesh
may also not be envisaged, for instance, in the case of integrating this model to manage public
administration [46].</p>
      <p>Future work will address in more detail the validation of this framework in relevant scenarios.
For this purpose, the identification of the main targets and actors will be a pivotal step: in fact,
the present model aims at scalability, so it could be implemented with diferent types of actors. In
operative scenarios, the elements constituting the domains of the mesh could be compartments
of the same organisation, nodes of public bodies spread across the territory, or even diferent
organisations. In each case, the advantages would derive from diferent factors: as for the first
two targets, the advantage would be the increase in the level of eficiency and efectiveness
in the exploitation of the shared digital resources, together with increased transparency and
targeted involvement of stakeholders thanks to the structure provided by domains. In the
latter case, medium-small organisations could join to to share resources and enable synergistic
functionalities and services that they could not provide individually.
case study, in: Proceedings of the International Conference on Electronic Business (ICEB),
volume 21, 2021, pp. 599–604.
[35] I. A. Machado, C. Costa, M. Y. Santos, Data mesh: Concepts and principles of a paradigm
shift in data architectures, in: Procedia Computer Science, volume 196, 2021, pp. 263–271.
[36] J. Andress, The basics of information security: Understanding the fundamentals of
InfoSec in theory and practice, The Basics of Information Security: Understanding the
Fundamentals of InfoSec in Theory and Practice, Syngress, 2011.
[37] F. Provost, T. Fawcett, Data science and its relationship to big data and data-driven decision
making, Big Data 1 (2013) 51–59.
[38] E. Brynjolfsson, L. Hitt, H. Kim, Strength in numbers: How does data-driven
decisionmaking afect firm performance?, in: International Conference on Information Systems
2011, ICIS 2011, volume 1, 2011, pp. 541–558.
[39] H.-M. Chen, R. Kazman, J. Garbajosa, E. Gonzalez, Big data value engineering for business
model innovation, in: Proceedings of the Annual Hawaii International Conference on
System Sciences, 2017, pp. 5921–5930.
[40] M. Akerman, C. Lundgren, M. Bärring, M. Folkesson, V. Berggren, J. Stahre, U. Engström,
M. Friis, Challenges building a data value chain to enable data-driven decisions: A
predictive maintenance case in 5G-Enabled manufacturing, Procedia Manufacturing 17
(2018) 411–418.
[41] D. Kriksciuniene, V. Sakalauskas, B. Kriksciunas, Process optimization and monitoring
along big data value chain, in: W. Abramowicz (Ed.), Business Information Systems
Workshops, BIS 2015, volume 228 of Lecture Notes in Business Information Processing,
Springer, 2015, pp. 75–86.
[42] D. Dutta, I. Bose, Managing a big data project: The case of ramco cements limited,</p>
      <p>International Journal of Production Economics 165 (2015) 293–306.
[43] J. Manyika, M. Chui, B. Brown, J. Bughin, R. Dobbs, C. Roxburgh, A. Byers, Big data: The
next frontier for innovation, competition, and productivity, McKinsey Global Institute,
2011.
[44] M. Angelelli, Tropical limit and a micro-macro correspondence in statistical physics,</p>
      <p>Journal of Physics A: Mathematical and Theoretical 50 (2017) 415202.
[45] M. T. Baldassarre, V. S. Barletta, D. Caivano, A. Piccinno, M. Scalera, Privacy Knowledge
Base for Supporting Decision-making in Software Development, in: Sense, Feel, Design:
INTERACT 2021 IFIP TC 13 Workshops, Bari, Italy, August 30–September 3, 2021, Revised
Selected Papers, Springer, 2022, pp. 147–157.
[46] C. Catalano, P. Afrune, M. Angelelli, G. Maglio, F. Striani, F. Tommasi, Security testing
reuse enhancing active cyber defence in public administration., in: ITASEC, 2021, pp.
120–132.</p>
    </sec>
  </body>
  <back>
    <ref-list>
      <ref id="ref1">
        <mixed-citation>
          [1]
          <string-name>
            <given-names>V.</given-names>
            <surname>Fast</surname>
          </string-name>
          ,
          <string-name>
            <given-names>D.</given-names>
            <surname>Schnurr</surname>
          </string-name>
          ,
          <string-name>
            <given-names>M.</given-names>
            <surname>Wohlfarth</surname>
          </string-name>
          ,
          <article-title>Data-driven competitive advantages in digital markets: An overview of data value and facilitating factors</article-title>
          ,
          <source>Lecture Notes in Information Systems and Organisation 48 LNISO</source>
          (
          <year>2021</year>
          )
          <fpage>454</fpage>
          .
        </mixed-citation>
      </ref>
      <ref id="ref2">
        <mixed-citation>
          [2]
          <string-name>
            <given-names>J. M.</given-names>
            <surname>Cavanillas</surname>
          </string-name>
          ,
          <string-name>
            <given-names>E.</given-names>
            <surname>Curry</surname>
          </string-name>
          ,
          <string-name>
            <given-names>W.</given-names>
            <surname>Wahlster</surname>
          </string-name>
          ,
          <article-title>New horizons for a data-driven economy: a roadmap for usage and exploitation of big data in Europe</article-title>
          , Springer Nature,
          <year>2016</year>
          .
        </mixed-citation>
      </ref>
      <ref id="ref3">
        <mixed-citation>
          [3]
          <string-name>
            <given-names>Z.</given-names>
            <surname>Dehghani</surname>
          </string-name>
          ,
          <source>Data Mesh: Delivering Data-Driven Value at Scale</source>
          , 1.ed - preview
          <string-name>
            <surname>version</surname>
          </string-name>
          ,
          <string-name>
            <surname>O'Reilly Media</surname>
          </string-name>
          , Inc.,
          <year>2022</year>
          .
        </mixed-citation>
      </ref>
      <ref id="ref4">
        <mixed-citation>
          [4]
          <string-name>
            <given-names>J.</given-names>
            <surname>Dong</surname>
          </string-name>
          ,
          <string-name>
            <given-names>C.-H.</given-names>
            <surname>Yang</surname>
          </string-name>
          ,
          <article-title>Business value of big data analytics: A systems-theoretic approach and empirical test</article-title>
          ,
          <source>Information and Management</source>
          <volume>57</volume>
          (
          <year>2020</year>
          ).
        </mixed-citation>
      </ref>
      <ref id="ref5">
        <mixed-citation>
          [5]
          <string-name>
            <given-names>D.</given-names>
            <surname>Lavie</surname>
          </string-name>
          ,
          <article-title>The competitive advantage of interconnected firms: An extension of the resourcebased view</article-title>
          ,
          <source>Academy of Management Review</source>
          <volume>31</volume>
          (
          <year>2005</year>
          ).
        </mixed-citation>
      </ref>
      <ref id="ref6">
        <mixed-citation>
          [6]
          <string-name>
            <given-names>J.</given-names>
            <surname>Dyer</surname>
          </string-name>
          ,
          <string-name>
            <given-names>H.</given-names>
            <surname>Singh</surname>
          </string-name>
          ,
          <article-title>The relational view: Cooperative strategy and sources of interorganizational competitive advantage</article-title>
          ,
          <source>The Academy of Management Review</source>
          <volume>23</volume>
          (
          <year>1998</year>
          ).
        </mixed-citation>
      </ref>
      <ref id="ref7">
        <mixed-citation>
          [7]
          <string-name>
            <given-names>J.</given-names>
            <surname>Zeng</surname>
          </string-name>
          ,
          <string-name>
            <given-names>K. W.</given-names>
            <surname>Glaister</surname>
          </string-name>
          ,
          <article-title>Value creation from big data: Looking inside the black box</article-title>
          ,
          <source>STRATEGIC ORGANIZATION 16</source>
          (
          <year>2018</year>
          )
          <fpage>105</fpage>
          -
          <lpage>140</lpage>
          .
        </mixed-citation>
      </ref>
      <ref id="ref8">
        <mixed-citation>
          [8]
          <string-name>
            <given-names>D.</given-names>
            <surname>Laney</surname>
          </string-name>
          , 3-
          <string-name>
            <given-names>D</given-names>
            <surname>Data Management: Controlling Data</surname>
          </string-name>
          <string-name>
            <given-names>Volume</given-names>
            ,
            <surname>Velocity</surname>
          </string-name>
          , and
          <string-name>
            <surname>Variety</surname>
          </string-name>
          ,
          <source>Technical Report, META Group Res. Note</source>
          ,
          <year>2001</year>
          .
        </mixed-citation>
      </ref>
      <ref id="ref9">
        <mixed-citation>
          [9]
          <string-name>
            <given-names>J.</given-names>
            <surname>Gantz</surname>
          </string-name>
          ,
          <string-name>
            <given-names>D.</given-names>
            <surname>Reinsel</surname>
          </string-name>
          ,
          <article-title>Extracting value from chaos</article-title>
          ,
          <source>Technical Report</source>
          <year>2011</year>
          , IDC IView,
          <year>2011</year>
          .
        </mixed-citation>
      </ref>
      <ref id="ref10">
        <mixed-citation>
          [10]
          <string-name>
            <given-names>M.</given-names>
            <surname>Schroeck</surname>
          </string-name>
          ,
          <string-name>
            <given-names>R.</given-names>
            <surname>Shockley</surname>
          </string-name>
          ,
          <string-name>
            <given-names>J.</given-names>
            <surname>Smart</surname>
          </string-name>
          ,
          <string-name>
            <given-names>D.</given-names>
            <surname>Romero-Morales</surname>
          </string-name>
          ,
          <string-name>
            <given-names>P.</given-names>
            <surname>Tufano</surname>
          </string-name>
          ,
          <article-title>Analytics: The realworld use of big data</article-title>
          ,
          <source>Technical Report</source>
          <year>2012</year>
          ,
          <string-name>
            <given-names>IBM</given-names>
            <surname>Global Business</surname>
          </string-name>
          <string-name>
            <surname>Services</surname>
          </string-name>
          ,
          <year>2012</year>
          .
        </mixed-citation>
      </ref>
      <ref id="ref11">
        <mixed-citation>
          [11]
          <string-name>
            <given-names>S.</given-names>
            <surname>Arockia</surname>
          </string-name>
          ,
          <article-title>The 17 V's Of Big Data</article-title>
          ,
          <source>International Research Journal of Engineering and Technology</source>
          <volume>4</volume>
          (
          <year>2017</year>
          )
          <fpage>329</fpage>
          -
          <lpage>333</lpage>
          .
        </mixed-citation>
      </ref>
      <ref id="ref12">
        <mixed-citation>
          [12]
          <string-name>
            <given-names>S.</given-names>
            <surname>Dhamodharavadhani</surname>
          </string-name>
          , G. Rajasekaran,
          <article-title>Unlock diferent V's of big data for analytics</article-title>
          ,
          <source>International Journal of Computer Sciences and Engineering</source>
          <volume>6</volume>
          (
          <year>2018</year>
          )
          <fpage>183</fpage>
          -
          <lpage>190</lpage>
          .
        </mixed-citation>
      </ref>
      <ref id="ref13">
        <mixed-citation>
          [13]
          <string-name>
            <given-names>A.</given-names>
            <surname>Hussien</surname>
          </string-name>
          ,
          <article-title>How Many Old and New Big Data V's Characteristics, Processing Technology</article-title>
          , And
          <string-name>
            <surname>Applications</surname>
          </string-name>
          (BD1),
          <source>International Journal of Application or Innovation in Engineering &amp; Management</source>
          <volume>9</volume>
          (
          <year>2020</year>
          )
          <fpage>15</fpage>
          -
          <lpage>27</lpage>
          .
        </mixed-citation>
      </ref>
      <ref id="ref14">
        <mixed-citation>
          [14]
          <string-name>
            <given-names>M.</given-names>
            <surname>Talha</surname>
          </string-name>
          ,
          <string-name>
            <given-names>A. A.</given-names>
            <surname>El Kalam</surname>
          </string-name>
          ,
          <string-name>
            <given-names>N.</given-names>
            <surname>Elmarzouqi</surname>
          </string-name>
          ,
          <article-title>Big data: Trade-of between data quality and data security</article-title>
          ,
          <source>in: Procedia Computer Science</source>
          , volume
          <volume>151</volume>
          ,
          <year>2019</year>
          , pp.
          <fpage>916</fpage>
          -
          <lpage>922</lpage>
          .
        </mixed-citation>
      </ref>
      <ref id="ref15">
        <mixed-citation>
          [15]
          <string-name>
            <surname>H.-M. Chen</surname>
            ,
            <given-names>R.</given-names>
          </string-name>
          <string-name>
            <surname>Kazman</surname>
            ,
            <given-names>J.</given-names>
          </string-name>
          <string-name>
            <surname>Garbajosa</surname>
          </string-name>
          , E. Gonzalez,
          <article-title>Toward big data value engineering for innovation</article-title>
          ,
          <source>in: Proceedings - 2nd International Workshop on BIG Data Software Engineering, BIGDSE</source>
          <year>2016</year>
          ,
          <year>2016</year>
          , pp.
          <fpage>44</fpage>
          -
          <lpage>50</lpage>
          .
        </mixed-citation>
      </ref>
      <ref id="ref16">
        <mixed-citation>
          [16]
          <string-name>
            <given-names>R.</given-names>
            <surname>Bhatia</surname>
          </string-name>
          ,
          <string-name>
            <given-names>M.</given-names>
            <surname>Sood</surname>
          </string-name>
          ,
          <article-title>Security of big data: A review</article-title>
          ,
          <source>in: PDGC 2018 - 2018 5th International Conference on Parallel, Distributed and Grid Computing</source>
          ,
          <year>2018</year>
          , pp.
          <fpage>182</fpage>
          -
          <lpage>186</lpage>
          .
        </mixed-citation>
      </ref>
      <ref id="ref17">
        <mixed-citation>
          [17]
          <string-name>
            <given-names>M. T.</given-names>
            <surname>Rahman</surname>
          </string-name>
          ,
          <string-name>
            <given-names>M. S.</given-names>
            <surname>Rahman</surname>
          </string-name>
          ,
          <string-name>
            <given-names>H.</given-names>
            <surname>Wang</surname>
          </string-name>
          ,
          <string-name>
            <given-names>S.</given-names>
            <surname>Tajik</surname>
          </string-name>
          ,
          <string-name>
            <given-names>W.</given-names>
            <surname>Khalil</surname>
          </string-name>
          ,
          <string-name>
            <given-names>F.</given-names>
            <surname>Farahmandi</surname>
          </string-name>
          ,
          <string-name>
            <given-names>D.</given-names>
            <surname>Forte</surname>
          </string-name>
          ,
          <string-name>
            <given-names>N.</given-names>
            <surname>Asadizanjani</surname>
          </string-name>
          ,
          <string-name>
            <given-names>M.</given-names>
            <surname>Tehranipoor</surname>
          </string-name>
          ,
          <article-title>Defense-in-depth: A recipe for logic locking to prevail</article-title>
          ,
          <source>Integration</source>
          <volume>72</volume>
          (
          <year>2020</year>
          )
          <fpage>39</fpage>
          -
          <lpage>57</lpage>
          .
        </mixed-citation>
      </ref>
      <ref id="ref18">
        <mixed-citation>
          [18]
          <string-name>
            <given-names>O.</given-names>
            <surname>Ylijoki</surname>
          </string-name>
          ,
          <string-name>
            <given-names>J.</given-names>
            <surname>Porras</surname>
          </string-name>
          ,
          <article-title>Perspectives to Definition of Big Data: A Mapping Study and Discussion</article-title>
          ,
          <source>Journal of Innovation Management</source>
          <volume>4</volume>
          (
          <year>2016</year>
          )
          <fpage>69</fpage>
          -
          <lpage>91</lpage>
          .
        </mixed-citation>
      </ref>
      <ref id="ref19">
        <mixed-citation>
          [19]
          <string-name>
            <given-names>M. E.</given-names>
            <surname>Porter</surname>
          </string-name>
          ,
          <article-title>Competitive advantage: Creating and sustaining superior performance</article-title>
          , Free Press, New York and London,
          <year>1985</year>
          .
        </mixed-citation>
      </ref>
      <ref id="ref20">
        <mixed-citation>
          [20]
          <string-name>
            <surname>E. Curry,</surname>
          </string-name>
          <article-title>The big data value chain: Definitions, concepts, and theoretical approaches, in: New Horizons for a Data-Driven Economy: A Roadmap for Usage and Exploitation of Big Data in Europe</article-title>
          , Springer Nature,
          <year>2016</year>
          , pp.
          <fpage>29</fpage>
          -
          <lpage>37</lpage>
          .
        </mixed-citation>
      </ref>
      <ref id="ref21">
        <mixed-citation>
          [21]
          <string-name>
            <given-names>R.</given-names>
            <surname>Louati</surname>
          </string-name>
          ,
          <string-name>
            <given-names>S.</given-names>
            <surname>Mekadmi</surname>
          </string-name>
          ,
          <article-title>Toward a conceptualization of big data value chain: From business problems to value creation</article-title>
          ,
          <source>in: Research Anthology on Big Data Analytics</source>
          , Architectures, and Applications, IGI Global,
          <year>2022</year>
          , pp.
          <fpage>319</fpage>
          -
          <lpage>335</lpage>
          .
        </mixed-citation>
      </ref>
      <ref id="ref22">
        <mixed-citation>
          [22]
          <string-name>
            <given-names>A. Z.</given-names>
            <surname>Faroukhi</surname>
          </string-name>
          ,
          <string-name>
            <given-names>I. El</given-names>
            <surname>Alaoui</surname>
          </string-name>
          ,
          <string-name>
            <given-names>Y.</given-names>
            <surname>Gahi</surname>
          </string-name>
          ,
          <string-name>
            <given-names>A.</given-names>
            <surname>Amine</surname>
          </string-name>
          ,
          <article-title>An adaptable big data value chain framework for end-to-end big data monetization</article-title>
          ,
          <source>Big Data and cognitive computing 4</source>
          (
          <year>2020</year>
          ).
        </mixed-citation>
      </ref>
      <ref id="ref23">
        <mixed-citation>
          [23]
          <string-name>
            <given-names>O.</given-names>
            <surname>Ylijoki</surname>
          </string-name>
          ,
          <string-name>
            <given-names>J.</given-names>
            <surname>Porras</surname>
          </string-name>
          ,
          <article-title>A recipe for big data value creation</article-title>
          ,
          <source>Business Process Management Journal</source>
          <volume>25</volume>
          (
          <year>2019</year>
          )
          <fpage>1085</fpage>
          -
          <lpage>1100</lpage>
          .
        </mixed-citation>
      </ref>
      <ref id="ref24">
        <mixed-citation>
          [24]
          <string-name>
            <given-names>J.</given-names>
            <surname>Rayport</surname>
          </string-name>
          ,
          <string-name>
            <given-names>J.</given-names>
            <surname>Sviokla</surname>
          </string-name>
          ,
          <article-title>Exploiting the virtual value chain</article-title>
          ,
          <source>Harvard Business Review</source>
          <volume>73</volume>
          (
          <year>1995</year>
          )
          <fpage>75</fpage>
          -
          <lpage>85</lpage>
          .
        </mixed-citation>
      </ref>
      <ref id="ref25">
        <mixed-citation>
          [25]
          <string-name>
            <given-names>H.</given-names>
            <surname>Miller</surname>
          </string-name>
          ,
          <string-name>
            <given-names>P.</given-names>
            <surname>Mork</surname>
          </string-name>
          ,
          <article-title>From data to decisions: a value chain for big data</article-title>
          ,
          <source>IT Professional 15</source>
          (
          <year>2013</year>
          )
          <fpage>57</fpage>
          -
          <lpage>59</lpage>
          .
        </mixed-citation>
      </ref>
      <ref id="ref26">
        <mixed-citation>
          [26]
          <string-name>
            <given-names>A.</given-names>
            <surname>Braganza</surname>
          </string-name>
          ,
          <string-name>
            <given-names>L.</given-names>
            <surname>Brooks</surname>
          </string-name>
          ,
          <string-name>
            <given-names>D.</given-names>
            <surname>Nepelski</surname>
          </string-name>
          ,
          <string-name>
            <given-names>M.</given-names>
            <surname>Ali</surname>
          </string-name>
          ,
          <string-name>
            <given-names>R.</given-names>
            <surname>Moro</surname>
          </string-name>
          ,
          <article-title>Resource management in big data initiatives: processes and dynamic capabilities</article-title>
          ,
          <source>Journal of Business Research</source>
          <volume>70</volume>
          (
          <year>2017</year>
          )
          <fpage>328</fpage>
          -
          <lpage>337</lpage>
          .
        </mixed-citation>
      </ref>
      <ref id="ref27">
        <mixed-citation>
          [27]
          <string-name>
            <given-names>M.</given-names>
            <surname>Janssen</surname>
          </string-name>
          ,
          <string-name>
            <surname>V. Van der</surname>
          </string-name>
          ,
          <string-name>
            <given-names>A.</given-names>
            <surname>Wahyudi</surname>
          </string-name>
          ,
          <article-title>Factors influencing big data decision-making quality</article-title>
          ,
          <source>Journal of Business Research</source>
          <volume>70</volume>
          (
          <year>2017</year>
          )
          <fpage>338</fpage>
          -
          <lpage>345</lpage>
          .
        </mixed-citation>
      </ref>
      <ref id="ref28">
        <mixed-citation>
          [28]
          <string-name>
            <given-names>X.</given-names>
            <surname>Wu</surname>
          </string-name>
          ,
          <string-name>
            <given-names>L.</given-names>
            <surname>Liang</surname>
          </string-name>
          ,
          <string-name>
            <given-names>S.</given-names>
            <surname>Chen</surname>
          </string-name>
          ,
          <article-title>How big data alters value creation: through the lens of big data competency, Management Decision 60 (</article-title>
          <year>2022</year>
          )
          <fpage>707</fpage>
          -
          <lpage>734</lpage>
          .
        </mixed-citation>
      </ref>
      <ref id="ref29">
        <mixed-citation>
          [29]
          <string-name>
            <given-names>R.</given-names>
            <surname>Ackof</surname>
          </string-name>
          ,
          <article-title>From data to wisdom</article-title>
          ,
          <source>Journal of Applied System Analysis</source>
          <volume>16</volume>
          (
          <year>1989</year>
          )
          <fpage>3</fpage>
          -
          <lpage>9</lpage>
          .
        </mixed-citation>
      </ref>
      <ref id="ref30">
        <mixed-citation>
          [30]
          <string-name>
            <surname>M. E. M. El Aissi</surname>
            ,
            <given-names>S.</given-names>
          </string-name>
          <string-name>
            <surname>Benjelloun</surname>
            ,
            <given-names>Y.</given-names>
          </string-name>
          <string-name>
            <surname>Loukili</surname>
            ,
            <given-names>Y.</given-names>
          </string-name>
          <string-name>
            <surname>Lakhrissi</surname>
            ,
            <given-names>A. E.</given-names>
          </string-name>
          <string-name>
            <surname>Boushaki</surname>
            ,
            <given-names>H.</given-names>
          </string-name>
          <string-name>
            <surname>Chougrad</surname>
            ,
            <given-names>S.</given-names>
          </string-name>
          <string-name>
            <surname>Elhaj Ben</surname>
            <given-names>Ali</given-names>
          </string-name>
          ,
          <article-title>Data lake versus data warehouse architecture: A comparative study</article-title>
          ,
          <source>in: WITS 2020: Proceedings of the 6th International Conference on Wireless Technologies, Embedded, and Intelligent Systems</source>
          , volume
          <volume>745</volume>
          of Lecture Notes in Electrical Engineering, Springer Nature,
          <year>2022</year>
          , pp.
          <fpage>201</fpage>
          -
          <lpage>210</lpage>
          .
        </mixed-citation>
      </ref>
      <ref id="ref31">
        <mixed-citation>
          [31]
          <string-name>
            <given-names>J.</given-names>
            <surname>Kachaoui</surname>
          </string-name>
          ,
          <string-name>
            <given-names>A.</given-names>
            <surname>Belangour</surname>
          </string-name>
          ,
          <article-title>Challenges and benefits of deploying big data storage solution</article-title>
          , in: ACM International Conference Proceeding Series,
          <year>2019</year>
          .
        </mixed-citation>
      </ref>
      <ref id="ref32">
        <mixed-citation>
          [32]
          <string-name>
            <given-names>I.</given-names>
            <surname>Machado</surname>
          </string-name>
          ,
          <string-name>
            <given-names>C.</given-names>
            <surname>Costa</surname>
          </string-name>
          ,
          <string-name>
            <given-names>M. Y.</given-names>
            <surname>Santos</surname>
          </string-name>
          ,
          <article-title>Data-driven information systems: the data mesh paradigm shift</article-title>
          ,
          <source>in: 9th International Conference on Information Systems Development (ISD2021 Valencia, Spain)</source>
          ,
          <year>2021</year>
          .
        </mixed-citation>
      </ref>
      <ref id="ref33">
        <mixed-citation>
          [33]
          <string-name>
            <given-names>M.</given-names>
            <surname>Jacek</surname>
          </string-name>
          ,
          <string-name>
            <given-names>B.</given-names>
            <surname>Sven</surname>
          </string-name>
          ,
          <string-name>
            <given-names>S.</given-names>
            <surname>Marian</surname>
          </string-name>
          ,
          <string-name>
            <given-names>S.</given-names>
            <surname>Mariusz</surname>
          </string-name>
          , Data Mesh in Action, 1.ed - preview version, Manning Publications Co.,
          <year>2023</year>
          .
        </mixed-citation>
      </ref>
      <ref id="ref34">
        <mixed-citation>
          [34]
          <string-name>
            <given-names>D.</given-names>
            <surname>Joshi</surname>
          </string-name>
          ,
          <string-name>
            <given-names>S.</given-names>
            <surname>Pratik</surname>
          </string-name>
          ,
          <string-name>
            <given-names>M. P.</given-names>
            <surname>Rao</surname>
          </string-name>
          ,
          <article-title>Data governance in data mesh infrastructures: The saxo bank</article-title>
        </mixed-citation>
      </ref>
    </ref-list>
  </back>
</article>