<!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>
      <journal-title-group>
        <journal-title>Poitiers, France
$ philipp.skavantzos@auckland.ac.nz (P. Skavantzos); s.link@auckland.ac.nz (S. Link)
 https://profiles.auckland.ac.nz/philipp-skavantzos (P. Skavantzos); https://profiles.auckland.ac.nz/s-link (S. Link)</journal-title>
      </journal-title-group>
    </journal-meta>
    <article-meta>
      <title-group>
        <article-title>Entity/Relationship Modeling for Property Graphs</article-title>
      </title-group>
      <contrib-group>
        <contrib contrib-type="author">
          <string-name>Philipp Skavantzos</string-name>
          <xref ref-type="aff" rid="aff0">0</xref>
        </contrib>
        <contrib contrib-type="author">
          <string-name>Sebastian Link</string-name>
          <xref ref-type="aff" rid="aff0">0</xref>
        </contrib>
        <aff id="aff0">
          <label>0</label>
          <institution>School of Computer Science, University of Auckland</institution>
          ,
          <addr-line>Auckland 1010</addr-line>
          ,
          <country country="NZ">New Zealand</country>
        </aff>
      </contrib-group>
      <pub-date>
        <year>2025</year>
      </pub-date>
      <volume>000</volume>
      <fpage>0</fpage>
      <lpage>0001</lpage>
      <abstract>
        <p>This tutorial shows how traditional Entity/Relationship modeling and modern graph data modeling can be combined to bring forward well-designed graph data models that process workloads and maintain data integrity eficiently. Despite the popularity and growing maturity of graph database systems, they continue to rank well below trusted relational technology1. The reasons for this are not just historical. Indeed, an inhibitor to the further uptake of graph databases is the lack of principled methodologies for their design, rigorous schema and data integrity support. As a consequence, academics and practitioners have worked together to develop proposals for emerging standards of query languages [1, 2], schema [3], and data integrity [4]. For the emerging standards PG-Schema [3] for graph schemata and PG-Key [4] for graph integrity, it is not yet well understood which of their fragments supports which applications. PG-Schema, in particular, has been developed to support basic features of Entity/Relationship (E/R) models, but its expressiveness is well beyond those capabilities. Chen's E/R model [5] constitutes the best breed of conceptual data models. The model captures entities and their relationships in an easy-to-understand framework powerful enough to derive a formal data model. E/R models visually represent complex requirements for the target database [6]. In fact, the graphical depiction of an E/R diagram is invaluable for efective communication between experts with diferent expertise. E/R modeling is a methodology for generating well-designed E/R diagrams as they guarantee directed acyclicity, data integrity and do not exhibit redundancy of data or anomalies of updates in any instance [7, 8, 9]. Given these developments, the tutorial addresses the following ambitious research question.</p>
      </abstract>
      <kwd-group>
        <kwd>eol&gt;Conceptual modeling</kwd>
        <kwd>Entity/Relationship diagrams</kwd>
        <kwd>Entity integrity</kwd>
        <kwd>Property graphs</kwd>
        <kwd>Referential integrity</kwd>
      </kwd-group>
    </article-meta>
  </front>
  <body>
    <sec id="sec-1">
      <title>1. Topic Motivation</title>
      <p>What is a methodology for designing property graph schemata that can process workloads and
maintain data integrity eficaciously on each of their graph instances?</p>
      <p>The main goals are to show what Entity/Relationship modeling can do for graph data, and what
graph data can do for Entity/Relationship modeling. An important point is to bring together diferent
communities for their mutual benefit.</p>
      <p>In what follows, Sec. 2 will describe the target audience and knowledge outcomes. The latter are
fundamental for conceptual, graph and logical data modeling. A detailed outline and timetable of the
tutorial will be given in Sec. 3. The tutorial method is explained in Sec. 4, before a short biography for
the presenters is given in Sec. 5.</p>
    </sec>
    <sec id="sec-2">
      <title>2. Target Audience and Knowledge Outcomes</title>
      <p>The specific target audience is people with an interest in conceptual data modeling or graph data
modeling. The tutorial showcases fundamentals for these disciplines, and focuses on how they can
bring out the best in one another when combined. The topic is timely as graph databases have grown
larger in popularity among researchers and practitioners, but also because the design of graph databases
has emerged as a new and important direction. The tutorial is accessible to students with a general
computer science education at undergraduate level because fundamental concepts are introduced. This
is even of interest to experts in the area, due to the diversity of models and languages available, which
makes it necessary to fix concepts and notation.</p>
      <p>The overarching outcome targeted for this tutorial is to survey the fundamental impact E/R modeling
and graph databases have on one another.</p>
      <p>Property graphs that comply with E/R diagrams, called E/R graphs, constitute the first E/R databases
that are graphs. Hence, instead of translating E/R diagrams to other data models, we can directly manage
E/R graphs as graph databases. That is, graph databases bring E/R modeling concepts to life. The
tutorial illustrates how E/R diagrams form a core fragment of PG-Schema that captures well-designed
(graph) databases. Hence, PG-Schema can be viewed as a general data modeling tool.</p>
      <p>It is demonstrated that reasoning about PG-Key is infeasible, but keys of E/R models form a fragment
of PG-Key for eficiently managing entity integrity in well-designed property graphs.</p>
      <p>The audience learns about principled approaches to managing referential integrity eficiently in E/R
graphs. This contrasts relational and graph-based approaches, and pinpoints what opportunities for
improving integrity management in graph database systems exist.</p>
      <p>Overall, the tutorial conveys how E/R diagrams and property graphs can be combined to unify
conceptual, logical and graph data modeling, how integrity management can be taken to the next level
by eliminating property redundancy, and why relational benchmarks perform very well when translated
into property graphs. Indeed, the tutorial shows how a major inhibitor to the uptake of graph databases
can be turned into a strong driver.</p>
    </sec>
    <sec id="sec-3">
      <title>3. Detailed Outline and Timetable</title>
      <p>We will give a detailed outline of what the tutorial covers, and indicate how much time is spent on
each topic. The following subsections form the logical units of the tutorial, in the sequence they are
presented.</p>
      <p>
        After some motivation and outline of the goals (5 minutes) [
        <xref ref-type="bibr" rid="ref1 ref10 ref2">10, 1, 2</xref>
        ], we provide a background
on Entity/Relationship modeling (20 minutes) [
        <xref ref-type="bibr" rid="ref5 ref7 ref8 ref9">5, 9, 8, 7</xref>
        ]. Utilizing a small toy example suficiently
large to illustrate all concepts, and also utilizing an E/R diagram for the TPC-H benchmark to illustrate
some real-world like scenario, we fix the underlying syntax and semantics. There is a brief overview of
recent approaches applying conceptual modeling to graph databases [
        <xref ref-type="bibr" rid="ref11 ref12 ref13 ref14 ref15">11, 12, 13, 14, 15</xref>
        ], with restrictions
on the order and depth of object types utilized (5 minutes). The remaining tutorial is based on the
expressiveness of Entity/Relationship models to play out their key strength for the benefit of graph
databases [
        <xref ref-type="bibr" rid="ref16">16</xref>
        ].
      </p>
      <p>The concept of property graphs is introduced next, both in terms of formal definitions and
visualizations (10 minutes). We also illustrate the concepts on our running example.</p>
      <p>
        We then discuss the recent proposal for the definition of key constraints in property graphs, called
PG-Key [
        <xref ref-type="bibr" rid="ref3 ref4">4, 3</xref>
        ] (10 minutes). We discuss the syntax and semantics of PG-Key expressions such that
the audience is comfortable with understanding how expressive PG-Keys are and how they work. The
discussion is led by examples.
      </p>
      <p>
        Next we give a concise overview of PG-Schema [
        <xref ref-type="bibr" rid="ref3">3</xref>
        ], a recent proposal by academics and practitioners
to help standardizing schema support for graph databases (10 minutes). Similarly to PG-Key, we
highlight the syntax and semantics of major features, predominantly by way of examples.
      </p>
      <p>
        Our next aim is to show how traditional E/R modeling provides a methodology for designing property
graphs well (20 minutes). In the first of two steps, we illustrate that E/R diagrams are property graphs
themselves, but also form a fragment of PG-Schema. This situation is reminiscent of XML where
XML Schema definitions constitute XML documents themselves [
        <xref ref-type="bibr" rid="ref17">17</xref>
        ]. As a result, E/R modeling is
available as a mature and trusted methodology for the design of property graphs. In step two, we
showcase that E/R graphs constitute the first graph semantics for E/R diagrams, as defined in [
        <xref ref-type="bibr" rid="ref16">16</xref>
        ]. As
E/R modeling is a conceptual approach and property graphs constitute a logical data model, E/R graphs
unify conceptual, logical, and graph data modeling. As consequences, modern graph database systems
provide an operational platform for conceptual data models, ofering a viable alternative to relational
technology without having to translate conceptual models at all.
      </p>
      <p>Next, we demonstrate that E/R graphs and diagrams ofer principled concepts for maintaining
entity and referential integrity eficiently within graph database systems (20 minutes). In particular,
translations of relational databases to E/R graphs ofer various benefits for data integrity management.
We illustrate the notion of an E/R key and demonstrate that every E/R key is also a PG-Key, but not vice
versa. We demonstrate that E/R keys form an eficient fragment of PG-Key, namely for well-designed
property graphs. In terms of referential integrity, we illustrate two principled approaches: one that
always duplicates key properties as foreign key properties (relational semantics), and one that always
uses references by directed edges in graphs (graph semantics). The first approach can directly benefit
from graph technology, while the second one can only make use of current technology in case all key
properties are defined locally on nodes without use of references. Hence, we propose a third approach
(mixed semantics) which maximizes the opportunity for references while complying with current
technology limits.</p>
      <p>We then showcase TPC-H as an industry-like use case that illustrates the main concepts and quantifies
how well the E/R approach works at operational level (10 minutes). We present translations of the
TPC-H schema, including keys and foreign keys, into an E/R diagram using the diferent semantics,
translate its query and update operations, and compare the eficiency of their evaluation within Neo4j
and MySQL. The results demonstrate to the audience how well our initial research question has been
addressed. It also shows the audience how important data modeling is for core database operations.</p>
      <p>Finally, we summarize main takeaways and outline future research directions (10 minutes).</p>
    </sec>
    <sec id="sec-4">
      <title>4. Tutorial Method</title>
      <p>The presentation is based on slides to convey the knowledge outcomes in a visually appealing way
that draws the audience’s attention and promotes their understanding, but also facilitates interaction.
Our timetable, proposed above, accommodates the presentation itself but also designates time for
questions and discussions. In particular, we will prompt the audience to criticize our toy example and
ofer alternative modeling approaches, but also ask them to convert between some classical relational
database instances and graph instances to facilitate understanding further. Lots of examples and
visualizations illustrate ideas, techniques and findings. A 90 minute version was presented at VLDB
2025. The ER audience is quite diferent, the topic well aligned with ER, and a presentation of 2
hours conveys more details, discussion, and interesting direction of future research for the modeling
community.</p>
      <p>We only use a standard projector and a board for exploring ideas interactively with the audience.</p>
    </sec>
    <sec id="sec-5">
      <title>5. Presenters</title>
      <p>Philipp is a research fellow and teaching assistant with considerable experience teaching database
topics to undergraduate and postgraduate students of diferent backgrounds. The topic of his PhD was
on the design of graph databases.</p>
      <p>Sebastian is a Professor of Computer Science with vast experience in presenting database topics to
audiences of various backgrounds. He has presented extensively at top database conferences, particularly
on topics of the tutorial.</p>
    </sec>
    <sec id="sec-6">
      <title>Declaration on Generative AI</title>
      <p>The author(s) have not employed any Generative AI tools.</p>
    </sec>
  </body>
  <back>
    <ref-list>
      <ref id="ref1">
        <mixed-citation>
          [1]
          <string-name>
            <given-names>R.</given-names>
            <surname>Angles</surname>
          </string-name>
          ,
          <string-name>
            <given-names>M.</given-names>
            <surname>Arenas</surname>
          </string-name>
          ,
          <string-name>
            <given-names>P.</given-names>
            <surname>Barceló</surname>
          </string-name>
          ,
          <string-name>
            <given-names>P. A.</given-names>
            <surname>Boncz</surname>
          </string-name>
          ,
          <string-name>
            <given-names>G. H. L.</given-names>
            <surname>Fletcher</surname>
          </string-name>
          ,
          <string-name>
            <given-names>C.</given-names>
            <surname>Gutierrez</surname>
          </string-name>
          ,
          <string-name>
            <given-names>T.</given-names>
            <surname>Lindaaker</surname>
          </string-name>
          ,
          <string-name>
            <given-names>M.</given-names>
            <surname>Paradies</surname>
          </string-name>
          ,
          <string-name>
            <given-names>S.</given-names>
            <surname>Plantikow</surname>
          </string-name>
          ,
          <string-name>
            <given-names>J. F.</given-names>
            <surname>Sequeda</surname>
          </string-name>
          ,
          <string-name>
            <surname>O. van Rest</surname>
          </string-name>
          ,
          <string-name>
            <given-names>H.</given-names>
            <surname>Voigt</surname>
          </string-name>
          ,
          <string-name>
            <surname>G-CORE</surname>
          </string-name>
          :
          <article-title>A core for future graph query languages</article-title>
          ,
          <source>in: Proceedings of the 2018 International Conference on Management of Data, SIGMOD Conference</source>
          <year>2018</year>
          , Houston, TX, USA, June 10-15,
          <year>2018</year>
          ,
          <year>2018</year>
          , pp.
          <fpage>1421</fpage>
          -
          <lpage>1432</lpage>
          .
        </mixed-citation>
      </ref>
      <ref id="ref2">
        <mixed-citation>
          [2]
          <string-name>
            <given-names>R.</given-names>
            <surname>Angles</surname>
          </string-name>
          ,
          <string-name>
            <given-names>M.</given-names>
            <surname>Arenas</surname>
          </string-name>
          ,
          <string-name>
            <given-names>P.</given-names>
            <surname>Barceló</surname>
          </string-name>
          ,
          <string-name>
            <given-names>A.</given-names>
            <surname>Hogan</surname>
          </string-name>
          ,
          <string-name>
            <given-names>J. L.</given-names>
            <surname>Reutter</surname>
          </string-name>
          ,
          <string-name>
            <given-names>D.</given-names>
            <surname>Vrgoc</surname>
          </string-name>
          ,
          <article-title>Foundations of modern query languages for graph databases</article-title>
          ,
          <source>ACM Comput. Surv</source>
          .
          <volume>50</volume>
          (
          <year>2017</year>
          )
          <volume>68</volume>
          :
          <fpage>1</fpage>
          -
          <lpage>68</lpage>
          :
          <fpage>40</fpage>
          .
        </mixed-citation>
      </ref>
      <ref id="ref3">
        <mixed-citation>
          [3]
          <string-name>
            <given-names>R.</given-names>
            <surname>Angles</surname>
          </string-name>
          ,
          <string-name>
            <given-names>A.</given-names>
            <surname>Bonifati</surname>
          </string-name>
          ,
          <string-name>
            <given-names>S.</given-names>
            <surname>Dumbrava</surname>
          </string-name>
          ,
          <string-name>
            <given-names>G.</given-names>
            <surname>Fletcher</surname>
          </string-name>
          ,
          <string-name>
            <given-names>A.</given-names>
            <surname>Green</surname>
          </string-name>
          ,
          <string-name>
            <given-names>J.</given-names>
            <surname>Hidders</surname>
          </string-name>
          ,
          <string-name>
            <given-names>B.</given-names>
            <surname>Li</surname>
          </string-name>
          ,
          <string-name>
            <given-names>L.</given-names>
            <surname>Libkin</surname>
          </string-name>
          ,
          <string-name>
            <given-names>V.</given-names>
            <surname>Marsault</surname>
          </string-name>
          ,
          <string-name>
            <given-names>W.</given-names>
            <surname>Martens</surname>
          </string-name>
          ,
          <string-name>
            <given-names>F.</given-names>
            <surname>Murlak</surname>
          </string-name>
          ,
          <string-name>
            <given-names>S.</given-names>
            <surname>Plantikow</surname>
          </string-name>
          ,
          <string-name>
            <given-names>O.</given-names>
            <surname>Savkovic</surname>
          </string-name>
          ,
          <string-name>
            <given-names>M.</given-names>
            <surname>Schmidt</surname>
          </string-name>
          ,
          <string-name>
            <given-names>J.</given-names>
            <surname>Sequeda</surname>
          </string-name>
          ,
          <string-name>
            <given-names>S.</given-names>
            <surname>Staworko</surname>
          </string-name>
          ,
          <string-name>
            <given-names>D.</given-names>
            <surname>Tomaszuk</surname>
          </string-name>
          ,
          <string-name>
            <given-names>H.</given-names>
            <surname>Voigt</surname>
          </string-name>
          ,
          <string-name>
            <given-names>D.</given-names>
            <surname>Vrgoc</surname>
          </string-name>
          ,
          <string-name>
            <given-names>M.</given-names>
            <surname>Wu</surname>
          </string-name>
          ,
          <string-name>
            <given-names>D.</given-names>
            <surname>Zivkovic</surname>
          </string-name>
          ,
          <article-title>Pg-schema: Schemas for property graphs</article-title>
          ,
          <source>Proc. ACM Manag. Data</source>
          <volume>1</volume>
          (
          <year>2023</year>
          )
          <volume>198</volume>
          :
          <fpage>1</fpage>
          -
          <lpage>198</lpage>
          :
          <fpage>25</fpage>
          . URL: https://doi.org/10.1145/3589778. doi:
          <volume>10</volume>
          .1145/ 3589778.
        </mixed-citation>
      </ref>
      <ref id="ref4">
        <mixed-citation>
          [4]
          <string-name>
            <given-names>R.</given-names>
            <surname>Angles</surname>
          </string-name>
          ,
          <string-name>
            <given-names>A.</given-names>
            <surname>Bonifati</surname>
          </string-name>
          ,
          <string-name>
            <given-names>S.</given-names>
            <surname>Dumbrava</surname>
          </string-name>
          , G. Fletcher,
          <string-name>
            <given-names>K. W.</given-names>
            <surname>Hare</surname>
          </string-name>
          ,
          <string-name>
            <given-names>J.</given-names>
            <surname>Hidders</surname>
          </string-name>
          ,
          <string-name>
            <given-names>V. E.</given-names>
            <surname>Lee</surname>
          </string-name>
          ,
          <string-name>
            <given-names>B.</given-names>
            <surname>Li</surname>
          </string-name>
          ,
          <string-name>
            <given-names>L.</given-names>
            <surname>Libkin</surname>
          </string-name>
          ,
          <string-name>
            <given-names>W.</given-names>
            <surname>Martens</surname>
          </string-name>
          ,
          <string-name>
            <given-names>F.</given-names>
            <surname>Murlak</surname>
          </string-name>
          ,
          <string-name>
            <given-names>J.</given-names>
            <surname>Perryman</surname>
          </string-name>
          ,
          <string-name>
            <given-names>O.</given-names>
            <surname>Savkovic</surname>
          </string-name>
          ,
          <string-name>
            <given-names>M.</given-names>
            <surname>Schmidt</surname>
          </string-name>
          ,
          <string-name>
            <given-names>J. F.</given-names>
            <surname>Sequeda</surname>
          </string-name>
          ,
          <string-name>
            <given-names>S.</given-names>
            <surname>Staworko</surname>
          </string-name>
          ,
          <string-name>
            <given-names>D.</given-names>
            <surname>Tomaszuk</surname>
          </string-name>
          ,
          <article-title>Pg-keys: Keys for property graphs</article-title>
          ,
          <source>in: SIGMOD '21: International Conference on Management of Data</source>
          , Virtual Event, China, June 20-25,
          <year>2021</year>
          ,
          <year>2021</year>
          , pp.
          <fpage>2423</fpage>
          -
          <lpage>2436</lpage>
          . URL: https://doi.org/10.1145/3448016.3457561. doi:
          <volume>10</volume>
          .1145/3448016.3457561.
        </mixed-citation>
      </ref>
      <ref id="ref5">
        <mixed-citation>
          [5]
          <string-name>
            <given-names>P. P.</given-names>
            <surname>Chen</surname>
          </string-name>
          ,
          <article-title>The entity-relationship model - toward a unified view of data</article-title>
          ,
          <source>ACM Trans. Database Syst</source>
          .
          <volume>1</volume>
          (
          <issue>1976</issue>
          )
          <fpage>9</fpage>
          -
          <lpage>36</lpage>
          .
        </mixed-citation>
      </ref>
      <ref id="ref6">
        <mixed-citation>
          [6]
          <string-name>
            <given-names>P. P.</given-names>
            <surname>Chen</surname>
          </string-name>
          , English, chinese and ER diagrams,
          <source>Data Knowl. Eng</source>
          .
          <volume>23</volume>
          (
          <year>1997</year>
          )
          <fpage>5</fpage>
          -
          <lpage>16</lpage>
          .
        </mixed-citation>
      </ref>
      <ref id="ref7">
        <mixed-citation>
          [7]
          <string-name>
            <given-names>M.</given-names>
            <surname>Levene</surname>
          </string-name>
          ,
          <string-name>
            <given-names>M. W.</given-names>
            <surname>Vincent</surname>
          </string-name>
          ,
          <article-title>Justification for inclusion dependency normal form</article-title>
          ,
          <source>IEEE Trans. Knowl. Data Eng</source>
          .
          <volume>12</volume>
          (
          <year>2000</year>
          )
          <fpage>281</fpage>
          -
          <lpage>291</lpage>
          .
        </mixed-citation>
      </ref>
      <ref id="ref8">
        <mixed-citation>
          [8]
          <string-name>
            <given-names>H.</given-names>
            <surname>Mannila</surname>
          </string-name>
          ,
          <string-name>
            <given-names>K.</given-names>
            <surname>Räihä</surname>
          </string-name>
          , Design of Relational Databases, Addison-Wesley,
          <year>1992</year>
          .
        </mixed-citation>
      </ref>
      <ref id="ref9">
        <mixed-citation>
          [9]
          <string-name>
            <given-names>B.</given-names>
            <surname>Thalheim</surname>
          </string-name>
          ,
          <article-title>Entity-relationship modeling - foundations of database technology</article-title>
          , Springer,
          <year>2000</year>
          .
        </mixed-citation>
      </ref>
      <ref id="ref10">
        <mixed-citation>
          [10]
          <string-name>
            <given-names>A.</given-names>
            <surname>Bonifati</surname>
          </string-name>
          ,
          <string-name>
            <given-names>G. H. L.</given-names>
            <surname>Fletcher</surname>
          </string-name>
          ,
          <string-name>
            <given-names>H.</given-names>
            <surname>Voigt</surname>
          </string-name>
          ,
          <string-name>
            <given-names>N.</given-names>
            <surname>Yakovets</surname>
          </string-name>
          , Querying Graphs,
          <source>Synthesis Lectures on Data Management</source>
          , Morgan &amp; Claypool Publishers,
          <year>2018</year>
          .
        </mixed-citation>
      </ref>
      <ref id="ref11">
        <mixed-citation>
          [11]
          <string-name>
            <given-names>E.</given-names>
            <surname>Gelling</surname>
          </string-name>
          , G. Fletcher,
          <string-name>
            <given-names>M.</given-names>
            <surname>Schmidt</surname>
          </string-name>
          ,
          <article-title>Bridging graph data models: Rdf, rdf-star, and property graphs as directed acyclic graphs</article-title>
          ,
          <source>CoRR abs/2304</source>
          .13097 (
          <year>2023</year>
          ).
        </mixed-citation>
      </ref>
      <ref id="ref12">
        <mixed-citation>
          [12]
          <string-name>
            <given-names>G.</given-names>
            <surname>Daniel</surname>
          </string-name>
          , G. Sunyé,
          <string-name>
            <given-names>J.</given-names>
            <surname>Cabot</surname>
          </string-name>
          , Umltographdb:
          <article-title>Mapping conceptual schemas to graph databases</article-title>
          , in: Conceptual Modeling - 35th International Conference, ER 2016, Gifu, Japan,
          <source>November 14-17</source>
          ,
          <year>2016</year>
          , Proceedings,
          <year>2016</year>
          , pp.
          <fpage>430</fpage>
          -
          <lpage>444</lpage>
          .
        </mixed-citation>
      </ref>
      <ref id="ref13">
        <mixed-citation>
          [13]
          <string-name>
            <given-names>J.</given-names>
            <surname>Pokorný</surname>
          </string-name>
          ,
          <article-title>Conceptual and database modelling of graph databases</article-title>
          ,
          <source>in: Proceedings of the 20th International Database Engineering &amp; Applications Symposium</source>
          ,
          <string-name>
            <surname>IDEAS</surname>
          </string-name>
          <year>2016</year>
          , Montreal, QC, Canada,
          <source>July 11-13</source>
          ,
          <year>2016</year>
          ,
          <year>2016</year>
          , pp.
          <fpage>370</fpage>
          -
          <lpage>377</lpage>
          .
        </mixed-citation>
      </ref>
      <ref id="ref14">
        <mixed-citation>
          [14]
          <string-name>
            <surname>V. M. de Sousa</surname>
          </string-name>
          , L. M.
          <string-name>
            <surname>del Val</surname>
            <given-names>Cura</given-names>
          </string-name>
          ,
          <article-title>Logical design of graph databases from an entity-relationship conceptual model</article-title>
          ,
          <source>in: Proceedings of the 20th International Conference on Information Integration and Web-based Applications &amp; Services</source>
          , iiWAS
          <year>2018</year>
          , Yogyakarta, Indonesia,
          <source>November 19-21</source>
          ,
          <year>2018</year>
          ,
          <year>2018</year>
          , pp.
          <fpage>183</fpage>
          -
          <lpage>189</lpage>
          .
        </mixed-citation>
      </ref>
      <ref id="ref15">
        <mixed-citation>
          [15]
          <string-name>
            <given-names>R. D.</given-names>
            <surname>Virgilio</surname>
          </string-name>
          ,
          <string-name>
            <given-names>A.</given-names>
            <surname>Maccioni</surname>
          </string-name>
          ,
          <string-name>
            <given-names>R.</given-names>
            <surname>Torlone</surname>
          </string-name>
          ,
          <article-title>Model-driven design of graph databases</article-title>
          , in: Conceptual Modeling - 33rd International Conference, ER 2014,
          <article-title>Atlanta</article-title>
          ,
          <string-name>
            <surname>GA</surname>
          </string-name>
          , USA, October
          <volume>27</volume>
          -
          <issue>29</issue>
          ,
          <year>2014</year>
          . Proceedings,
          <year>2014</year>
          , pp.
          <fpage>172</fpage>
          -
          <lpage>185</lpage>
          .
        </mixed-citation>
      </ref>
      <ref id="ref16">
        <mixed-citation>
          [16]
          <string-name>
            <given-names>P.</given-names>
            <surname>Skavantzos</surname>
          </string-name>
          ,
          <string-name>
            <given-names>S.</given-names>
            <surname>Link</surname>
          </string-name>
          , Entity/relationship graphs:
          <article-title>Principled design, modeling and data integrity management of graph databases</article-title>
          ,
          <source>Proc. ACM Manag. Data</source>
          <volume>3</volume>
          (
          <year>2025</year>
          )
          <fpage>1</fpage>
          -
          <lpage>25</lpage>
          .
        </mixed-citation>
      </ref>
      <ref id="ref17">
        <mixed-citation>
          [17]
          <string-name>
            <given-names>G. J.</given-names>
            <surname>Bex</surname>
          </string-name>
          ,
          <string-name>
            <given-names>F.</given-names>
            <surname>Neven</surname>
          </string-name>
          ,
          <string-name>
            <surname>J. V.</surname>
          </string-name>
          den Bussche,
          <article-title>Dtds versus XML schema: A practical study</article-title>
          ,
          <source>in: Proceedings of the Seventh International Workshop on the Web and Databases</source>
          ,
          <source>WebDB</source>
          <year>2004</year>
          , June 17-18,
          <year>2004</year>
          , Maison de la Chimie, Paris, France,
          <source>Colocated with ACM SIGMOD/PODS</source>
          <year>2004</year>
          ,
          <year>2004</year>
          , pp.
          <fpage>79</fpage>
          -
          <lpage>84</lpage>
          .
        </mixed-citation>
      </ref>
    </ref-list>
  </back>
</article>