<!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>A Framework for Semantic Publishing of Modular Content Ob jects</article-title>
      </title-group>
      <contrib-group>
        <contrib contrib-type="author">
          <string-name>Catalin David</string-name>
          <xref ref-type="aff" rid="aff0">0</xref>
        </contrib>
        <contrib contrib-type="author">
          <string-name>Deyan Ginev</string-name>
          <xref ref-type="aff" rid="aff0">0</xref>
        </contrib>
        <contrib contrib-type="author">
          <string-name>Michael Kohlhase</string-name>
          <xref ref-type="aff" rid="aff0">0</xref>
        </contrib>
        <contrib contrib-type="author">
          <string-name>Bogdan Matican</string-name>
          <xref ref-type="aff" rid="aff0">0</xref>
        </contrib>
        <contrib contrib-type="author">
          <string-name>Stefan Mirea</string-name>
          <xref ref-type="aff" rid="aff0">0</xref>
        </contrib>
        <aff id="aff0">
          <label>0</label>
          <institution>Computer Science, Jacobs University</institution>
          ,
          <country country="DE">Germany</country>
        </aff>
      </contrib-group>
      <abstract>
        <p>We present the Active Documents approach to semantic publishing (semantically annotated documents associated with a content commons that holds the background ontologies) and the Planetary system (as an active document player). In this paper we explore the interaction of content object reuse and context sensitivity in the presentation process that transforms content modules to active documents. We propose a \separate compilation and dynamic linking" regime that makes semantic publishing of highly structured content representations into active documents tractable and show how this is realized in the Planetary system.</p>
      </abstract>
    </article-meta>
  </front>
  <body>
    <sec id="sec-1">
      <title>Introduction</title>
      <sec id="sec-1-1">
        <title>Document</title>
      </sec>
      <sec id="sec-1-2">
        <title>Player</title>
        <p>AActcitvivee
DDoDAocuoccutcmiumvemenentesntsts</p>
      </sec>
      <sec id="sec-1-3">
        <title>Content</title>
      </sec>
      <sec id="sec-1-4">
        <title>Objects</title>
        <p>this by providing embedded user assistance through an extended set of user
interactions with documents based on an extensible set of client- and server side
services that draw on explicit (and thus machine-understandable)
representations in the content commons.</p>
        <p>However, the exibility and power designed into the active documents paradigm
comes at a (distribution) cost: Every page that is shown to the user has to be
assembled for the user in a non-trivial compilation process (which we call the
presentation process) that takes user preferences and context into account. On
the other hand, if the content is organized modularly, it can be reused across
contexts. This presents a completely new set of trade-o s for publishing. One of
them is that an investment in modular and semantic representational markup
enhances reusability and thus may even lower the overall cost of authoring. We
will explore another such trade-o in this paper: optimizing the distribution
costs for modular content by \separate compilation".</p>
        <p>In the next section we will look at the organization of the content presented
to the user. This will constitute the conceptual backdrop against which we can
discuss the issues involved in separate compilation and how we have solved them
in the Planetary system.
2</p>
      </sec>
    </sec>
    <sec id="sec-2">
      <title>Organization of Content/Narrative Structure</title>
      <p>The Planetary system is intended as a semantic publishing framework , i.e. as
a system providing the baseline capabilities needed for multiple specialized
instantiations. We have shown the initial feasibility of the concept in a variety
of publicly available case studies2 ranging from pre-semantic archives of
scienti c literature [Arx], over a community-driven mathematical encyclopedia [Plac]
2 Note that all of these are research systems under constant development, so your
mileage may vary.
and the course system PantaRhei [Koh+], to a community portal of formal
logics [Plaa]. As a consequence of this, we employ the general, modular knowledge
structure depicted in Figure 2.
2.1</p>
      <sec id="sec-2-1">
        <title>Levels of Content/Documents</title>
        <sec id="sec-2-1-1">
          <title>Level</title>
        </sec>
      </sec>
    </sec>
    <sec id="sec-3">
      <title>Active Documents</title>
    </sec>
    <sec id="sec-4">
      <title>Content Commons</title>
      <p>4
3
2
1
0</p>
      <sec id="sec-4-1">
        <title>PlanetMath</title>
        <p>PantaRhei Instance</p>
      </sec>
      <sec id="sec-4-2">
        <title>Encyclopedia</title>
      </sec>
      <sec id="sec-4-3">
        <title>Article</title>
      </sec>
      <sec id="sec-4-4">
        <title>Learning Object</title>
      </sec>
      <sec id="sec-4-5">
        <title>Course</title>
      </sec>
      <sec id="sec-4-6">
        <title>Lecture</title>
      </sec>
      <sec id="sec-4-7">
        <title>Slide</title>
      </sec>
      <sec id="sec-4-8">
        <title>Library</title>
      </sec>
      <sec id="sec-4-9">
        <title>Collection</title>
      </sec>
      <sec id="sec-4-10">
        <title>Monograph</title>
      </sec>
      <sec id="sec-4-11">
        <title>Module</title>
      </sec>
      <sec id="sec-4-12">
        <title>Object</title>
        <p>The lowest level consists of atomic \modules"3, i.e. content objects that
correspond to small (active) documents dedicated to a single topic. For a course
management system these might be learning objects (either as single modules or
module trees), for an encyclopedia these would be the individual articles
introducing a topic. Note that technically, we allow modules to contain (denoted by
the arrows) other modules, so that larger discourse structures could be formed.
For example, sections can be realized as modules referencing other modules of
subsections, etc. The next level up is the level of \monographs", written works
on a single subject that have a complete, self-contained narrative structure,
usually by a single author or group of authors who feel responsible for the whole
monograph. As a content object, a monograph is usually built up from modules,
e.g. as a \module tree" that corresponds to sectioning structure of traditional
books, but often also includes front and backmatter such as a preface,
acknowledgements (both special kinds of modules), table of contents, lists of tables and
gures, an index and references (generated from content annotations). Figure 3
shows course notes in the PantaRhei system, while other documents at the
mono3 The level of objects below modules consists of individual statements (e.g. de nitions,
model assumptions, theorems, and proofs), semantic phrase-level markup, and
formulae. Even though it carries much of the semantic relations, it does not play a
great role for the document-level phenomena we want to discuss here in this paper.
graph level are articles in a journal, or books in a certain topical section of a
library.</p>
        <p>Multiple monographs can be combined into collections, adding special
modules for editorial comments, etc. Concrete collections in the document realm are
encyclopedias, academic journals, conference proceedings, or courses in a course
management system. Finally, the library level collects and grants access to
collections, concrete, modern-day examples are digital libraries, installed course
management systems, etc. In practice, a library provides a base URI that
establishes the web existence of the particular installation. In the Semantic Web
world, the library is the authority that makes its resources addressable by URLs.</p>
        <p>Content Objects and their Presentations in Active Documents
To understand the di erences between content objects and the documents
generated from them in the presentation process, let us consider the example in
Figure 4. Even though internally the content objects in Planetary are represented
in OMDoc [Koh06], we will use the surface language STEX4 for the example,
since this is what the author will write and maintain. STEX is a variant of LATEX
4</p>
        <p>We speak of an OMDoc surface language for any language that is optimized for
human authoring, but that can be converted to OMDoc automatically.
that allows to add semantic annotations in the source. It can be transformed
into OMDoc via the LATEXML daemon [GSK11] for management in Planetary;
see [Koh08] for details. We are using an example from a mathematical
document5 since content/presentation matters are most conspicuous there. In our
experience, STEX achieves a good balance (at least for authors experienced with
LATEX) conciseness and readability for mathematical documents. In particular,
since STEX documents such as the one in Figure 4 can be transformed to PDF via
the classical pdflatex for prototyping and proofreading. The semantic editing
process can further be simpli ed by semantic document development
environments like STEXIDE [JK10], which provides edit-support services lilke semantic
syntax highlighting, command completion/retrieval, and module graph
management.</p>
        <p>nbeginfmoduleg[id=binary trees]
nimportmodule[nKWARCslidesfgraphs trees/en/treesg]ftreesg
nimportmodule[nKWARCslidesfgraphs trees/en/graph depthg]fgraph depthg
...
nbeginfde nitiong[id=binary tree.def,title=Binary Tree]</p>
        <p>A nde niendum[binary tree]fbinary treeg is a ntermref[cd=trees,name=tree]ftreeg
where all ntermref[cd=graphs
have ntermref[cd=graphs introi,nntarmo,en=amouet=ndoedger]efen]ofdoeustg degreeg 2 or 0.
nendfde nitiong
...
nbeginfde nitiong[id=bbt.def]</p>
        <p>A ntermref[name=binary tree]fbinary treeg $G$ is called nde niendumalt[bbt]fbalancedg
i the ntermref[cd=graph depth,name=vertex depth]fdepthg of all
ntermref[cd=trees,name=leaf]fleavesg di ers by at most by 1, and
nde niendum[fullbbt]ffully balancedg, i the
ntermref[cd=graph depth,name=vertex depth]fdepthg di erence is 0.
nendfde nitiong
...
nendfmoduleg</p>
        <p>The upper half of Figure 4 shows the content representation of a module
on binary trees, and its presentation in Planetary is in the lower box. The rst
aspect that meets the eye is that the presentation process6 adds the textual
marker \De nition 3.1.7" which is not present in the content representation
nbeginfde nitiong[id=binary tree.def,title=Binary Tree]. Note that there are (at
least) four issues at hand here pertaining to the presentation of the text marker:
5 Actually from a second-semester course on Computer Science [Koh] hosted in
PantaRhei| an instance of the Planetary system that is optimized for active course notes
and discussions.
6 We disregard the presentation of formulae in content representation like OpenMath
or content MathML into presentation MathML in this paper and refer the reader
to [KMR08] for details.
1. The marker \De nition" is context-sensitive: The presentation of a Spanish
text would have generated \De nicion".
2. The number \3.1.7" is content-sensitive in a totally di erent way: it is
determined by the document structure, here it is a consequence of being the
seventh de nition in the rst section in chapter 3.
3. The \house style" of a journal might use a di erent font family for the whole
textual marker, for the text of the de nition, or add an end marker for a
distinctive layout. For instance in mathematical publications, theorems are
usually set in italics and proofs use a box on the right of the last line as an
end marker.
4. Finally, the whole text marker may be left out altogether in some situations,
where a less formal presentation is called for.</p>
        <p>Note that all these considerations have to be taken into account when
referencing objects like these de nitions. More so, these dimensions combine into a
unique multi-dimensional point, which identi es the exact presentation of a
document fragment. A content reference nsreffbinary tree.defg might be presented
as \Def. 3.1.7", in the same context as above (again subject to language, house
style, etc). Note that here the style (e.g. the keyword) and generated contextual
locators (e.g. the number) of the referenced object determines the actual label of
the reference7. We follow the context dimensions speci ed in [KK08, Chapter 3],
but note that many of the phenomena involve a separate, publishing context
dimension (e.g. \house style").</p>
        <p>Another phenomenon related to referencing is induced by the term reference
ntermref[cd=graphs,name=vertex]fnodeg, which identi es the phrase \node" as
a technical term and links it to its de ning occurrence by the symbol name (here
vertex) and the module name (also called content dictionary; here graphs). The
speci ed module must be accessible in the current module via the nimportmodule
relation and must contain a de nition that contains a de niendum with symbol
name vertex. The content module in Figure 4 speci es a module/content
dictionary with name balanced binary trees, whose rst de nition supplies a de
niendum with name balanced tree via the ntwindef macro, which is referenced in the
second de nition. Note that in the presentation process where term references
are displayed e.g as hyperlinks to the de nition the name-based semantic links
have to be converted into regular URI references. For this presentational
conversion to hyperlinks one utilizes not only the module tree structure (i.e. visibility
relationship) but also the library context that provides the base of the URI.</p>
        <p>Finally, note that some content objects contribute to the context of other
objects higher up in the content hierarchy in Figure 2. A good example for
this are the de nienda discussed above. In STEX, they trigger index entries that
populate the backmatter of monographs that include the respective module.
Section titles populate the frontmatter in a similar way. Concretely, we have a
top-level index stub in the backmatter, which \builds" itself from the context.
In a sense, the index is an abstract concept with volatile presentation, generated
7 a rather peculiar notion of context when viewed from a content-only perspective
from the module tree with the help of the content commons, which answers what
objects should be indexed.
3</p>
      </sec>
    </sec>
    <sec id="sec-5">
      <title>Separate Compilation</title>
      <p>We have seen above that the various contexts (conceptual/document/language)
have a signi cant e ect on the presentation. But observe that if all the
contextdependent parts of the presentation can be generated (albeit laboriously), the
content representations are context-independent and can be reused in di erent
contexts. This makes the content representations very portable. Consider for
instance the de nitions in our example above. They have been reused not only
in eight instances of the \General Computer Science II" course [Koh] in the
years 2004-2011 (each time with di erent numbers due to additions or deletions
of preceding material), but also in di erent courses, e.g. as a recap in a more
advanced CS course (without de nition marker). But these are not the only
contexts: the Planetary system can generate \guided tours" (self-contained
explanations adapted to the user's prerequisite knowledge) for any concept in a
document. Clearly, we cannot reasonably pre-compute all necessary presentation
variants.</p>
      <p>Computationally, the described situation is analogous to (and in fact
conceptually in uenced by) the situation in software design, where large programs are
broken up into reusable source modules. As source modules are re-used in many
programs, it is important that compilers support a regime of \separate
compilation and linking" to make software development tractable: if one of many
software modules used in a program changes, only that one module has to be
re-compiled and the whole program re-linked. The rst factor that enables this is
the observation that for compilation of a module only the (relatively stable)
signatures8 of modules it depends on are needed, not the (relatively change-prone)
module implementations. The second factor is that source modules can be
compiled into a form, where references to functions imported from other modules are
left symbolic and can later be replaced by concrete static references by the linker.
We will call such forms of modules contextable, since they are contextualized
by the linker in the way described.</p>
      <p>In the Planetary architecture semantic publishing consists of the
transformation of content structures encoded in STEX to active documents encoded in
XHTML+MathML+RDFa (see Section 3.2 for details). To foster reuse, and
make the process tractable, we want to assemble active documents from reusable
content modules much in the same way as assembling an executable program
from source modules. To make the separate compilation analogy fertile for
semantic publishing it is useful to look at the role of context in the separate
compilation regime: source modules are compiled into a context-independent
form, which is then contextualized by linking compiled modules together into
a consistent con guration for a concrete program. In the next two sections we
8 Signatures contain the names of functions/procedures, possibly their types, but not
their implementations.
examine how the two factors identi ed as crucial for the separate compilation
regime can be obtained in the context of semantic publishing.
3.1</p>
      <sec id="sec-5-1">
        <title>Contextable Presentations</title>
        <p>Just as in programming, separate compilation of content modules into active
documents is impossible without contextable structures in the presentation. It is
an original contribution of our work to introduce them in the document setting.
Concretely, we make use of the XML styling architecture and computes
contextindependent presentations that can be contextualized later. For instance, the
XHTML header for the rst de nition in Figure 4 has the following form.
&lt;div id="binary tree.def" class="omdoc de nition"&gt;
&lt;span class="omdoc statement header"&gt;
&lt;span class="omdoc de nition number"/&gt;7&lt;/span&gt;
&lt;span class="omdoc statement title"&gt;Binary Tree&lt;/span&gt;
&lt;/span&gt;
...</p>
        <p>We can then add (house) style information via CSS:
span.omdoc statement header ffont weight:boldg
span.omdoc statement title:before fcontent:"("g
span.omdoc statement title:after fcontent:")"g
span.omdoc de nition number:after fcontent: ": "g
span.omdoc de nition number:before fcontent:"De nition "g
Note that the keywords are not represented explicitly in the XHTML
presentation, but added by content declarations in the CSS. This allows to overwrite the
default ones via cascaded language-speci c CSS bindings, e.g. using
span.omdoc de nition number:before fcontent:"De nicion "g
Note furthermore, that the presentation process only adds preliminary statement
numbers in the XHTML presentation (here the number 7, since the de nition is
the seventh statement in the module). In the Planetary system, these numbers are
dynamically overwritten by values computed from the context; in our example
\3.1.7". The case for references is similar; for the table of contents shown in
Figure 3 the presentation generates
&lt;div class="omdoc expandableref"&gt;
&lt;span class="omdoc ref number"&gt;4&lt;/span&gt;
&lt;span class="omdoc reftitle"&gt;
&lt;a href="../computing dmath.omdoc" class="expandable"&gt;</p>
        <p>Computing with Functions over Inductively De ned Sets
&lt;/a&gt;
&lt;/span&gt;
&lt;/div&gt;
in the table of contents on the right and in the text. The CSS class omdoc expandableref
triggers the Planetary interaction that expands the references in place to get the
expanding ToC and the main document that can be folded/unfolded via the
Mathematica-style folding bars on the extreme left.
Document Commons</p>
        <p>REST</p>
        <p>XHTML+
The role of the module signatures (think C header les) is taken by STEX module
signatures, i.e. auxiliary les generated from STEX content modules that excerpt
the information about references, modules and their dependencies; see [Koh08]
for details. This information is used to establish a mapping between the content
commons and the document commons (see Figure 1) that can be queried for the
semantic interaction services embedded into the active documents.
ure 3 and Section 2.2, the numbering is linked into the contextable modules
whenever a page is viewed, based on this information. Recall we need this
dynamic (i.e. view-time) linking as modules are re-used in di erent document
contexts.
4</p>
      </sec>
    </sec>
    <sec id="sec-6">
      <title>Conclusion</title>
      <p>In this paper we have explored the conceptual and practical decoupling and
interaction of content and presentation in the active documents paradigm of semantic
publishing. Our main focus rested on the interaction of content object reuse and
context sensitivity of the presentation process. To make semantic publishing of
highly structured content representations into active documents tractable we
have developed a \separate compilation and dynamic linking" regime for
transforming highly structured content representations into active documents. The
concrete realization in the Planetary system hinges on the development of
contextable pre-presentations that are contextualized at document load time.</p>
      <p>While the basic architecture has been realized in the Planetary system, there
is still a lot to explore in the active documents paradigm and its SCDL
implementation. One crucial aspect is that while SCDL makes building active documents
tractable, it also leads to the well-known \late binding problems" (aka \DLL
Hell"), if modules change without adaptation of the dependent ones. We are
currently working on an integration of an ontology-based management of change
process [AM10] into the Planetary system (see [Aut+11]). This tries to alleviate
late binding problems by analyzing the impacts of a change via the dependency
relation induced by the semantic structure of the content commons and supports
authors in adapting their work. To complement this, we are currently developing
a notion of \versioned references" that support the practice of creating and
cultivating \islands of consistency" in the presence of change (see [KK11]). We hope
that together, these measures can lead to semantic content management
workows that alleviate the side-e ects of the semantic publishing work ow described
in this paper.
[AM10]
[Arx]</p>
      <p>Serge Autexier and Normen Muller. \Semantics-based Change
Impact Analysis for Heterogeneous Collections of Documents". In:
Proceedings of the 10th ACM symposium on Document engineering.
Ed. by Michael Gormish and Rolf Ingold. DocEng '10. Manchester,
United Kingdom: ACM, 2010, pp. 97{106. isbn:
978-1-4503-02319. doi: http://doi.acm.org/10.1145/1860559.1860580. url:
http://doi.acm.org/10.1145/1860559.1860580.
arXMLiv Build System. url: http://arxivdemo.mathweb.org
(visited on 09/27/2010).
[Aut+11] Serge Autexier et al. \Work ows for the Management of Change in
Science, Technologies, Engineering and Mathematics". submitted.
2011.
[Cic] Intelligent Computer Mathematics. submitted. 2011.
[Dav+10] Catalin David et al. \eMath 3.0: Building Blocks for a social and
semantic Web for online mathematics &amp; ELearning". In: 1st
International Workshop on Mathematics and ICT: Education,
Research and Applications. (Bucharest, Romania, Nov. 3, 2010). Ed.
by Ion Mierlus-Mazilu. 2010. url: http://kwarc.info/kohlhase/
papers/malog10.pdf.
[GSK11] Deyan Ginev, Heinrich Stamerjohanns, and Michael Kohlhase. \The
LATEXML Daemon: A LATEX Entrance to the Semantic Web".
submitted. 2011. url: https://kwarc.eecs.iu- bremen.de/repos/
arXMLiv/doc/cicm-systems11/paper.pdf.
[JK10] Constantin Jucovschi and Michael Kohlhase. \sTeXIDE: An
Integrated Development Environment for sTeX Collections". In:
Intelligent Computer Mathematics. Ed. by Serge Autexier et al.
LNAI 6167. Springer Verlag, 2010, pp. 336{344. isbn: 3642141277.
arXiv:1005.5489v1 [cs.OH].
[KK08] Andrea Kohlhase and Michael Kohlhase. \Semantic Knowledge
Management for Education". In: Proceedings of the IEEE; Special
Issue on Educational Technology 96.6 (June 2008), pp. 970{989. url:
http://kwarc.info/kohlhase/papers/semkm4ed.pdf.
[KK11] Andrea Kohlhase and Michael Kohlhase. \Maintaining Islands of
Consistency via Versioned Links". submitted. 2011. url: http://
kwarc.info/kohlhase/submit/mkm11-verlinks.pdf.
[KMR08] Michael Kohlhase, Christine Muller, and Florian Rabe.
\Notations for Living Mathematical Documents". In: Intelligent Computer
Mathematics. 9th International Conference, AISC, 15th Symposium,
Calculemus, 7th International Conference MKM (Birmingham, UK,
July 28{Aug. 1, 2008). Ed. by Serge Autexier et al. LNAI 5144.
Springer Verlag, 2008, pp. 504{519. url: http://omdoc.org/pubs/
mkm08-notations.pdf.
[Koh] General Computer Science: GenCS I/II Lecture Notes. 2011. url:
http://gencs.kwarc.info/book/1 (visited on 03/03/2001).
[Koh+] Michael Kohlhase et al. Planet GenCS. url: http://gencs.kwarc.</p>
      <p>info (visited on 09/22/2010).
[Koh06] Michael Kohlhase. OMDoc { An open markup format for
mathematical documents [Version 1.2]. LNAI 4180. Springer Verlag, Aug.
2006. url: http://omdoc.org/pubs/omdoc1.2.pdf.
[Koh08] Michael Kohlhase. \Using LATEX as a Semantic Markup Format".</p>
      <p>In: Mathematics in Computer Science 2.2 (2008), pp. 279{304. url:
https://svn.kwarc.info/repos/stex/doc/mcs08/stex.pdf.
[Koh+11] Michael Kohlhase et al. \The Planetary System: Web 3.0 &amp; Active
Documents for STEM". In: accepted for publication at ICCS 2011
[Plab]
[ZK09]</p>
    </sec>
  </body>
  <back>
    <ref-list>
      <ref id="ref1">
        <mixed-citation>
          <source>(Finalist at the Executable Papers Challenge)</source>
          .
          <year>2011</year>
          . url: https: //svn.mathweb.org/repos/planetary/doc/epc11/paper.pdf.
        </mixed-citation>
      </ref>
      <ref id="ref2">
        <mixed-citation>
          <string-name>
            <given-names>Logic</given-names>
            <surname>Atlas</surname>
          </string-name>
          and Integrator. url: http://logicatlas.omdoc.
          <source>org (visited on 09/22/</source>
          <year>2010</year>
          ).
        </mixed-citation>
      </ref>
      <ref id="ref3">
        <mixed-citation>
          <string-name>
            <given-names>Planetary</given-names>
            <surname>Developer</surname>
          </string-name>
          <article-title>Forum</article-title>
          . url: http : / / trac . mathweb . org / planetary/ (visited on 01/20/
          <year>2011</year>
          ).
        </mixed-citation>
      </ref>
      <ref id="ref4">
        <mixed-citation>
          PlanetMath.org {
          <article-title>Math for the people, by the people</article-title>
          . url: http: //planetmath.org (visited on 01/06/
          <year>2011</year>
          ).
        </mixed-citation>
      </ref>
      <ref id="ref5">
        <mixed-citation>
          <string-name>
            <given-names>Vyacheslav</given-names>
            <surname>Zholudev</surname>
          </string-name>
          and
          <string-name>
            <given-names>Michael</given-names>
            <surname>Kohlhase</surname>
          </string-name>
          . \
          <article-title>TNTBase: a Versioned Storage for XML"</article-title>
          .
          <source>In: Proceedings of Balisage: The Markup Conference</source>
          . Vol.
          <volume>3</volume>
          . Balisage Series on Markup Technologies. Mulberry Technologies, Inc.,
          <year>2009</year>
          . doi:
          <volume>10</volume>
          .4242/BalisageVol3.Zholudev01.
        </mixed-citation>
      </ref>
    </ref-list>
  </back>
</article>