<!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>Multilevel modeling: What's in a level? A position paper</article-title>
      </title-group>
      <contrib-group>
        <contrib contrib-type="author">
          <string-name>Mira Balaban</string-name>
          <xref ref-type="aff" rid="aff0">0</xref>
        </contrib>
        <contrib contrib-type="author">
          <string-name>Igal Khitron</string-name>
          <xref ref-type="aff" rid="aff0">0</xref>
        </contrib>
        <contrib contrib-type="author">
          <string-name>Michael Kifer</string-name>
          <email>kifer@cs.stonybrook.edu</email>
          <xref ref-type="aff" rid="aff1">1</xref>
        </contrib>
        <contrib contrib-type="author">
          <string-name>Azzam Maraee</string-name>
          <xref ref-type="aff" rid="aff0">0</xref>
        </contrib>
        <aff id="aff0">
          <label>0</label>
          <institution>Computer Science Department, Ben-Gurion University of the Negev</institution>
          ,
          <country country="IL">ISRAEL</country>
        </aff>
        <aff id="aff1">
          <label>1</label>
          <institution>Computer Science Department, Stony Brook University NY</institution>
          ,
          <country country="US">USA</country>
        </aff>
      </contrib-group>
      <abstract>
        <p>Multi-Level Modeling (MLM) conceptualizes software models as layered architectures of sub-models whose elements are inter-related by the instance-of relation, which is radically di erent from the traditional two level representations that consist of a class model and an instance model, where the former represents the schema and the latter the population. Key to the MLM representation is the notion of a level, which is the subject of this position paper. We argue that a theory of MLM must have a distinguished notion of level, which should have both a syntactic and a semantic status. Moreover, the notion of a level must represent a class model, and the overall MLM theory must be compositional, being composed from the theory of class models.</p>
      </abstract>
    </article-meta>
  </front>
  <body>
    <sec id="sec-1">
      <title>Introduction</title>
      <p>
        Multilevel system modeling (MLM) views the enterprise as a layered collection
of models that are inter-related by the instance-of (or membership) relation
among objects and classes. The grounds for this approach are both philosophical
and pragmatic. On philosophical grounds, researchers have been arguing that
faithful modeling of real world domains cannot be restricted by the standard
two-layer architecture of the OMG meta-modeling approach. They claim that
natural domains have multiple levels of classi cation, and an arti cial restriction
to two layers yields models that are too weak [
        <xref ref-type="bibr" rid="ref14 ref3">3, 14</xref>
        ]. On pragmatic grounds,
researchers have argued that a multilevel architecture of models simpli es the
management and evolution of complex software [
        <xref ref-type="bibr" rid="ref10 ref12 ref4">4, 10, 12</xref>
        ].
      </p>
      <p>
        Classes and associations in adjacent layers in the multilevel architecture can
be related by the standard instance-of relationship, while within each layer,
classes are organized via subclass and general association relationships. A
multilevel model consists of multiple, possibly overlapping, ontological dimensions,
each being a multilevel organization of classes and associations, as discussed
above. A potency mechanism, introduced in [
        <xref ref-type="bibr" rid="ref11 ref19 ref2">2,11,19</xref>
        ], is a kind of an inheritance
mechanism between levels.
      </p>
      <p>
        E orts to formulate multilevel modeling has led to a variety of approaches,
including a category-theory-based framework [
        <xref ref-type="bibr" rid="ref19">19</xref>
        ], a UML/OCL formulation
[
        <xref ref-type="bibr" rid="ref13">13</xref>
        ], multilevel objects and relationships [
        <xref ref-type="bibr" rid="ref17 ref18">17, 18</xref>
        ], an axiomatic speci cation of
multilevel types [
        <xref ref-type="bibr" rid="ref9">9</xref>
        ], a set-theoretic formulation [
        <xref ref-type="bibr" rid="ref5">5</xref>
        ], and more. Most approaches
have some form of an instance-of relation that stands for set membership, and
of subtyping relationship that stands for set inclusion.3
      </p>
      <p>
        In [
        <xref ref-type="bibr" rid="ref1">1</xref>
        ] the authors claim that a multilevel framework can be either level
blind, i.e., enable multilevel arbitrary classi cation structures, as in Telos [
        <xref ref-type="bibr" rid="ref16">16</xref>
        ],
F-Logic [
        <xref ref-type="bibr" rid="ref15">15</xref>
        ] and FOML [
        <xref ref-type="bibr" rid="ref6">6</xref>
        ], or level adjuvant, i.e., recognize the utility of levels,
as in the aforementioned frameworks. In these approaches, a level is a numeric
attribute de ned for all elements in a multilevel model, which enables layering
elements based on their level value. Yet, in most approaches the concept of a
level has no independent syntactic or semantic status.
      </p>
      <p>The main theme of this position paper is the claim that a multilevel theory
must have a distinguished notion of level with both a syntactic and a semantic
status. Moreover, levels should re ect the traditional notion of a class model, and
the overall theory should be compositional with respect to class models, i.e., be
constructed|syntactically and semantically|from the theory of class models.
2</p>
    </sec>
    <sec id="sec-2">
      <title>Multilevel Formalisms</title>
      <p>
        In this section we analyze several published approaches to MLM with respect
to the following three questions: (1) Does the formalism include a clear and
well-de ned syntax and semantics for multilevel models (the latter meaning
wellde ned notion of legal instances)? (2) Does the formalism include a distinguished
syntactic and semantic notion of a level ? (3) Is the formalism compositional with
respect to the class model language?
The category-theory-based formulation of [
        <xref ref-type="bibr" rid="ref19">19</xref>
        ]. This approach formalizes the
MLM approach of [
        <xref ref-type="bibr" rid="ref11 ref2">2, 11</xref>
        ] using category theory. It supports a syntactic de
nition of layered class models, extended with a rich potency mechanism that
enables cross-level constraints and cross-level instantiation (termed here single
potency ). The paper does not show how subtyping and standard class model
constraints, like association classes, GS-constraints, aggregation/composition and
inter-association constraints are handled.
      </p>
      <p>
        With respect to the above three questions: (1) this formalism provides a
formal de nition of multilevel models, with deep constraints and cross-level
instantiation. It is unclear, however, what is the semantics of a multilevel model,
i.e., what is the set of legal instances. For example, what is a legal population
of a model at some level, say, L3? How it is related, if at all, to the syntactic
instances in level L2? (2) This formalism includes a distinguished syntactic
notion of level : The syntactic elements of a level form a valid instance of the next
higher level, that functions as its class model. Yet, the semantic status of a level
is left unclear. (3) The formalism is syntactically compositional.
The UML/OCL constraint-based approach of [
        <xref ref-type="bibr" rid="ref13">13</xref>
        ]. This paper suggests
formulation of MLM using UML/OCL. The idea is to join metamodels of several levels
3 Some languages that support these relationships are Telos [
        <xref ref-type="bibr" rid="ref16">16</xref>
        ] and the executable
logic language FOML [
        <xref ref-type="bibr" rid="ref6">6</xref>
        ], which is derived from Flogic [
        <xref ref-type="bibr" rid="ref15">15</xref>
        ].
into a single model, using a concept of superstructure, which is modeled using
generalizations, associations and UML/OCL constraints.
      </p>
      <p>With respect to the above three questions: (1) Syntax and semantics are
given by UML/OCL; (2) elements are assigned a level, but there is no syntactic
unit that combines all elements with a common level value, and assigns it a
semantic status; (3) the formalism is not compositional.</p>
      <p>
        The multilevel objects and relationships approach of [
        <xref ref-type="bibr" rid="ref17 ref18">17, 18</xref>
        ]. This approach
suggests a representation that is based on constructs that integrate views at di erent
abstraction levels. An overall model consists of interrelated clabject hierarchies,
in which clabjects are classi ed into di erent abstraction levels. The
representation is formulated and implemented in F-logic [
        <xref ref-type="bibr" rid="ref15">15</xref>
        ].
      </p>
      <p>With respect to the above three questions, the approach is similar to the
previous one: (1) syntax and semantics are given by the de nition of abstraction
hierarchies and the F-Logic translation; (2) elements are assigned to an
abstraction level, but there is no syntactic/semantic unit of level; (3) the formalism is
not compositional.</p>
      <p>
        The FOL axiomatization of multilevel domains in [
        <xref ref-type="bibr" rid="ref9">9</xref>
        ]. This paper presents an
axiomatic FOL speci cation of a domain of types. The domain is structured in
linearly ordered levels, starting from an initial level of individuals. A level is a
set of all types whose elements belong to a lower level.
      </p>
      <p>Concerning our three questions: (1) the paper deals only with axiomatization
of sets of instances at each level and their types; (2) there is a distinguished
semantic notion of level; (3) the compositionality issue does not apply, since this
approach lacks a concrete language for MLM.</p>
      <p>
        The set-theoretic MLM theory in [
        <xref ref-type="bibr" rid="ref5">5</xref>
        ]. The formal executable theory for MLM is
based on set-theoretic semantics of class models [
        <xref ref-type="bibr" rid="ref7 ref8">7,8</xref>
        ]. Class models are combined
to form ontological dimensions, which are the backbone of a multilevel model.
The formal theory has a direct semantics for multilevel models, which accounts
for complex model interactions, including deep constraints and inference. Legal
instances are de ned using Herbrand instances in which the syntactic symbols
comprise the semantic domain. The MLM theory is seamlessly embedded in a
provably correct way into the executable logic language FOML [
        <xref ref-type="bibr" rid="ref6">6</xref>
        ].
      </p>
      <p>Regarding our three questions, the answers are all positive, owed in part to
the distinguished syntactic and semantic status of the concept of a level. A level
is represented by a schema, which is a pair of an instance model and a class
model. The instance model is syntactically included in the class model, using a
mapping, called a Herbrand mediator, of objects to classes, links to associations,
and property renaming. This enables renaming of properties and classes between
levels, which is absolute necessity for practical applications of MLM. In addition,
the instance model of a level is required to be a partial instance of the class
model in the next higher level. This partiality is important for proper semantics
of potency, but we have no room to expand on this issue here.</p>
      <p>The semantics of a multilevel ontological dimension de nes a legal instance
of a syntactically correct dimension as a sequence of legal instances of the class
models in the schemas, where (1) an instance of the class model in level i must
include the instance model in level i 1 (which is a partial instance of this
class model); and (2) satisfy all cross-level constraints in higher level schemas.
Therefore, the formalism has a well-de ned syntax and semantics, a distinguished
notion of level, and is compositional with respect to class models.
3</p>
      <p>
        On the Necessity of Level-based Compositional Theory
for Multilevel Modeling
Much of the literature on MLM is plagued by a confusion between true multilevel
modeling in which levels correspond to class models with each level being a
partial instance of the next, and modeling that is simply based on formalisms
with higher-order features where classes are uniformly treated as objects that
can be members of other (meta)classes (like in F-logic [
        <xref ref-type="bibr" rid="ref15">15</xref>
        ], RDF, Telos [
        <xref ref-type="bibr" rid="ref16">16</xref>
        ],
etc.). With respect to the approaches discussed in Section 2, an example of the
former kind of true MLM is [
        <xref ref-type="bibr" rid="ref5">5</xref>
        ], while [
        <xref ref-type="bibr" rid="ref13">13</xref>
        ] is an example of the latter kind of
approaches (which, in our view, are not truly MLM). Approaches in the middle of
the spectrum, which attempt to include the concept of a level (with partial or no
semantics), are [
        <xref ref-type="bibr" rid="ref19 ref9">9, 19</xref>
        ]. [
        <xref ref-type="bibr" rid="ref17 ref18">17, 18</xref>
        ] has a level notion that prevents compositionality
with respect to class models.
      </p>
      <p>
        We claim that MLM is much more than just a class model with higher
order features and constraints. It is a collection of levels bound together by the
instance-of relation, where each level is a class model, not just a numeric
attribute. Besides the instance-of relations, inter-level mediation includes
terminology changing mappings that permit renaming of concepts. Thus, levels should
be expressed both syntactically and semantically as an integral part of the
structure. A compositional4 MLM theory on top of class models turns MLM into a
natural extension of the class model in two ways: (1) a class model is a degenerate
case of a simple MLM; (2) a composite multilevel model consists|syntactically
and semantically|of class models and the theory of MLM should reuse the
theory of class models. Thus, in [
        <xref ref-type="bibr" rid="ref5">5</xref>
        ] we de ne consistency, nite satis ability and
optimization of MLM as natural extensions of their class model variants, and
show that intra-layer correctness and optimization can be checked using class
model algorithms.
4 By compositionality we mean that the semantics of MLM consists of the semantics
of the class models of the layers, properly stitched together by inter-level relations.
      </p>
    </sec>
  </body>
  <back>
    <ref-list>
      <ref id="ref1">
        <mixed-citation>
          1.
          <string-name>
            <given-names>C.</given-names>
            <surname>Atkinson</surname>
          </string-name>
          ,
          <string-name>
            <given-names>R.</given-names>
            <surname>Gerbig</surname>
          </string-name>
          , and
          <string-name>
            <given-names>T.</given-names>
            <surname>Kuehne</surname>
          </string-name>
          .
          <article-title>Comparing Multi-Level Modeling Approaches</article-title>
          .
          <source>In MULTI</source>
          <year>2014</year>
          ,
          <year>2014</year>
          .
        </mixed-citation>
      </ref>
      <ref id="ref2">
        <mixed-citation>
          2.
          <string-name>
            <given-names>C.</given-names>
            <surname>Atkinson</surname>
          </string-name>
          and
          <string-name>
            <given-names>T.</given-names>
            <surname>Ku</surname>
          </string-name>
          <article-title>hne. The essence of multilevel metamodeling</article-title>
          .
          <source>In UML</source>
          , pages
          <volume>19</volume>
          {
          <fpage>33</fpage>
          . Springer,
          <year>2001</year>
          .
        </mixed-citation>
      </ref>
      <ref id="ref3">
        <mixed-citation>
          3.
          <string-name>
            <given-names>C.</given-names>
            <surname>Atkinson</surname>
          </string-name>
          and
          <string-name>
            <given-names>T.</given-names>
            <surname>Ku</surname>
          </string-name>
          <article-title>hne. Rearchitecting the uml infrastructure</article-title>
          .
          <source>ACM Trans. Model. Comput. Simul.</source>
          ,
          <volume>12</volume>
          (
          <issue>4</issue>
          ):
          <volume>290</volume>
          {
          <fpage>321</fpage>
          ,
          <string-name>
            <surname>Oct</surname>
          </string-name>
          .
          <year>2002</year>
          .
        </mixed-citation>
      </ref>
      <ref id="ref4">
        <mixed-citation>
          4.
          <string-name>
            <given-names>C.</given-names>
            <surname>Atkinson</surname>
          </string-name>
          and
          <string-name>
            <given-names>T.</given-names>
            <surname>Ku</surname>
          </string-name>
          <article-title>hne. Reducing accidental complexity in domain models</article-title>
          .
          <source>Software &amp; Systems Modeling</source>
          ,
          <volume>7</volume>
          (
          <issue>3</issue>
          ):
          <volume>345</volume>
          {
          <fpage>359</fpage>
          ,
          <year>2008</year>
          .
        </mixed-citation>
      </ref>
      <ref id="ref5">
        <mixed-citation>
          5.
          <string-name>
            <given-names>M.</given-names>
            <surname>Balaban</surname>
          </string-name>
          , I. Khitron,
          <string-name>
            <given-names>M.</given-names>
            <surname>Kifer</surname>
          </string-name>
          ,
          <article-title>and</article-title>
          <string-name>
            <given-names>A.</given-names>
            <surname>Maraee</surname>
          </string-name>
          .
          <article-title>Formal executable theory of multilevel modeling</article-title>
          .
          <source>In CAISE</source>
          ,
          <year>2018</year>
          .
        </mixed-citation>
      </ref>
      <ref id="ref6">
        <mixed-citation>
          6.
          <string-name>
            <given-names>M.</given-names>
            <surname>Balaban</surname>
          </string-name>
          and
          <string-name>
            <given-names>M.</given-names>
            <surname>Kifer</surname>
          </string-name>
          .
          <article-title>Logic-Based Model-Level Software Development with F-OML</article-title>
          .
          <source>In MoDELS</source>
          <year>2011</year>
          ,
          <year>2011</year>
          .
        </mixed-citation>
      </ref>
      <ref id="ref7">
        <mixed-citation>
          7.
          <string-name>
            <given-names>M.</given-names>
            <surname>Balaban</surname>
          </string-name>
          and
          <string-name>
            <given-names>A.</given-names>
            <surname>Maraee</surname>
          </string-name>
          .
          <article-title>Finite Satis ability of UML Class Diagrams with Constrained Class Hierarchy</article-title>
          .
          <source>ACM TOSEM</source>
          ,
          <volume>22</volume>
          (
          <issue>3</issue>
          ):
          <volume>24</volume>
          :1{
          <fpage>24</fpage>
          :
          <fpage>42</fpage>
          ,
          <year>2013</year>
          .
        </mixed-citation>
      </ref>
      <ref id="ref8">
        <mixed-citation>
          8.
          <string-name>
            <given-names>M.</given-names>
            <surname>Balaban</surname>
          </string-name>
          and
          <string-name>
            <given-names>A.</given-names>
            <surname>Maraee. UML Class</surname>
          </string-name>
          <article-title>Diagram: Abstract syntax</article-title>
          and Semantics. https://goo.gl/UJzsjb,
          <year>2017</year>
          .
        </mixed-citation>
      </ref>
      <ref id="ref9">
        <mixed-citation>
          9.
          <string-name>
            <given-names>V. A.</given-names>
            <surname>Carvalho</surname>
          </string-name>
          and
          <string-name>
            <given-names>J. P. A.</given-names>
            <surname>Almeida</surname>
          </string-name>
          .
          <article-title>Toward a well-founded theory for multi-level conceptual modeling</article-title>
          .
          <source>Software &amp; Systems Modeling</source>
          ,
          <volume>17</volume>
          (
          <issue>1</issue>
          ):
          <volume>205</volume>
          {
          <fpage>231</fpage>
          ,
          <year>2018</year>
          .
        </mixed-citation>
      </ref>
      <ref id="ref10">
        <mixed-citation>
          10.
          <string-name>
            <surname>J. de Lara</surname>
            , E. Guerra,
            <given-names>R.</given-names>
          </string-name>
          <string-name>
            <surname>Cobos</surname>
          </string-name>
          , and J.
          <string-name>
            <surname>Moreno-Llorena</surname>
          </string-name>
          .
          <article-title>Extending deep metamodelling for practical mde</article-title>
          .
          <source>The Computer Journal</source>
          ,
          <volume>57</volume>
          (
          <issue>1</issue>
          ):
          <volume>36</volume>
          {
          <fpage>58</fpage>
          ,
          <year>2014</year>
          .
        </mixed-citation>
      </ref>
      <ref id="ref11">
        <mixed-citation>
          11.
          <string-name>
            <surname>J. de Lara</surname>
            , E. Guerra, and
            <given-names>J. S.</given-names>
          </string-name>
          <string-name>
            <surname>Cuadrado</surname>
          </string-name>
          .
          <article-title>Model-driven engineering with domainspeci c meta-modelling languages</article-title>
          .
          <source>SoSyM</source>
          ,
          <volume>14</volume>
          (
          <issue>1</issue>
          ):
          <volume>429</volume>
          {
          <fpage>459</fpage>
          ,
          <year>2013</year>
          .
        </mixed-citation>
      </ref>
      <ref id="ref12">
        <mixed-citation>
          12.
          <string-name>
            <surname>J. de Lara</surname>
            , E. Guerra, and
            <given-names>J. S.</given-names>
          </string-name>
          <string-name>
            <surname>Cuadrado</surname>
          </string-name>
          .
          <article-title>When and how to use multilevel modelling</article-title>
          .
          <source>ACM Trans. Softw</source>
          . Eng. Methodol.,
          <volume>24</volume>
          (
          <issue>2</issue>
          ):
          <volume>12</volume>
          :1{
          <fpage>12</fpage>
          :
          <fpage>46</fpage>
          ,
          <string-name>
            <surname>Dec</surname>
          </string-name>
          .
          <year>2014</year>
          .
        </mixed-citation>
      </ref>
      <ref id="ref13">
        <mixed-citation>
          13.
          <string-name>
            <surname>M. Gogolla</surname>
            ,
            <given-names>M.</given-names>
          </string-name>
          <string-name>
            <surname>Sedlmeier</surname>
            , L. Hamann, and
            <given-names>F.</given-names>
          </string-name>
          <string-name>
            <surname>Hilken</surname>
          </string-name>
          .
          <article-title>On metamodel superstructures employing UML generalization features</article-title>
          .
          <source>In MULTI'</source>
          <year>2014</year>
          ,
          <year>2014</year>
          .
        </mixed-citation>
      </ref>
      <ref id="ref14">
        <mixed-citation>
          14. B.
          <string-name>
            <surname>Henderson-Sellers</surname>
          </string-name>
          .
          <article-title>On the mathematics of modelling, metamodelling, ontologies and modelling languages</article-title>
          .
          <source>Springer Science &amp; Business Media</source>
          ,
          <year>2012</year>
          .
        </mixed-citation>
      </ref>
      <ref id="ref15">
        <mixed-citation>
          15.
          <string-name>
            <surname>M. Kifer</surname>
            ,
            <given-names>L. G.</given-names>
          </string-name>
          ,
          <article-title>and</article-title>
          <string-name>
            <given-names>J.</given-names>
            <surname>Wu</surname>
          </string-name>
          .
          <article-title>Logical foundations of object-oriented and frame-based languages</article-title>
          .
          <source>Journal of the ACM</source>
          ,
          <volume>42</volume>
          (
          <issue>4</issue>
          ):
          <volume>741</volume>
          {
          <fpage>843</fpage>
          ,
          <year>1995</year>
          .
        </mixed-citation>
      </ref>
      <ref id="ref16">
        <mixed-citation>
          16.
          <string-name>
            <surname>J. Mylopoulos</surname>
            ,
            <given-names>A.</given-names>
          </string-name>
          <string-name>
            <surname>Borgida</surname>
            ,
            <given-names>M.</given-names>
          </string-name>
          <string-name>
            <surname>Jarke</surname>
            , and
            <given-names>M.</given-names>
          </string-name>
          <string-name>
            <surname>Koubarakis</surname>
          </string-name>
          . Telos:
          <article-title>Representing knowledge about information systems</article-title>
          .
          <source>ACM TOIS</source>
          ,
          <volume>8</volume>
          (
          <issue>4</issue>
          ):
          <volume>325</volume>
          {
          <fpage>362</fpage>
          ,
          <year>1990</year>
          .
        </mixed-citation>
      </ref>
      <ref id="ref17">
        <mixed-citation>
          17.
          <string-name>
            <given-names>B.</given-names>
            <surname>Neumayr</surname>
          </string-name>
          ,
          <string-name>
            <surname>K.</surname>
          </string-name>
          <article-title>Grun, and M. Schre . Multi-level domain modeling with m-objects and m-relationships</article-title>
          .
          <source>In APCCM</source>
          <year>2009</year>
          ,
          <year>2009</year>
          .
        </mixed-citation>
      </ref>
      <ref id="ref18">
        <mixed-citation>
          18.
          <string-name>
            <given-names>B.</given-names>
            <surname>Neumayr</surname>
          </string-name>
          ,
          <string-name>
            <given-names>C. G.</given-names>
            <surname>Schuetz</surname>
          </string-name>
          ,
          <string-name>
            <given-names>M. A.</given-names>
            <surname>Jeusfeld</surname>
          </string-name>
          , and
          <string-name>
            <given-names>M.</given-names>
            <surname>Schre</surname>
          </string-name>
          .
          <article-title>Dual deep modeling: MLM with dual potencies and its formalization in F-Logic</article-title>
          .
          <source>SoSyM</source>
          , pages
          <volume>233</volume>
          {
          <fpage>268</fpage>
          ,
          <year>2018</year>
          .
        </mixed-citation>
      </ref>
      <ref id="ref19">
        <mixed-citation>
          19.
          <string-name>
            <given-names>A.</given-names>
            <surname>Rossini</surname>
          </string-name>
          , J. de Lara, E. Guerra,
          <string-name>
            <given-names>A.</given-names>
            <surname>Rutle</surname>
          </string-name>
          , and
          <string-name>
            <given-names>Y.</given-names>
            <surname>Lamo</surname>
          </string-name>
          .
          <article-title>A graph transformationbased semantics for deep metamodelling</article-title>
          .
          <source>In Applications of Graph Transformations with Industrial Relevance</source>
          . Springer,
          <year>2012</year>
          .
        </mixed-citation>
      </ref>
    </ref-list>
  </back>
</article>