<!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>Vienna, Austria
* Corresponding author.
$ lstahn@uni-wuppertal.de (L. Stahn)
 https://www.geschichte.uni-wuppertal.de/de/lehrgebiete/digital-humanities/detail/stahn/ (L. Stahn)</journal-title>
      </journal-title-group>
    </journal-meta>
    <article-meta>
      <title-group>
        <article-title>The Semantics in Works.</article-title>
      </title-group>
      <contrib-group>
        <contrib contrib-type="author">
          <string-name>Modelling the Author's Work</string-name>
        </contrib>
        <contrib contrib-type="author">
          <string-name>Its Making</string-name>
        </contrib>
        <contrib contrib-type="author">
          <string-name>Lena-Luise Stahn</string-name>
          <xref ref-type="aff" rid="aff0">0</xref>
        </contrib>
        <aff id="aff0">
          <label>0</label>
          <institution>Bergische Universität Wuppertal Gaußstraße 20</institution>
          ,
          <addr-line>42119 Wuppertal</addr-line>
          ,
          <country country="DE">Germany</country>
        </aff>
      </contrib-group>
      <pub-date>
        <year>2022</year>
      </pub-date>
      <volume>000</volume>
      <fpage>0</fpage>
      <lpage>0003</lpage>
      <abstract>
        <p>How does the author form his or her work? Can we follow the work development based on the documents found in the author's legacy? Using the scientific legacy of Niklas Luhmann as an example this article presents a way of modelling the interrelations between the legacy material, proposing first steps on the way to an legacy ontology using FRBRoo and CIDOC-CRM. The long-term project “Niklas Luhmann - Theorie als Passion. Wissenschaftliche Erschließung und Edition des Nachlasses", a collaboration between the Faculty of Sociology of the University of Bielefeld and the department for Digital Humanities of the University of Wuppertal, and funded by the North Rhine-Westphalian Academy of Sciences, Humanities and the Arts, deals with indexing, investigating, and providing access to the academic legacy of Niklas Luhmann (1927-1998), one of the best-known German sociologists of the 20th century and famous for his works in systems theory. The legacy is being archived at Bielefeld University, and comprises the notorious Zettelkasten (card index), his “Zweitgedächtnis"1 with approximately 90.000 index cards, about 150 unpublished manuscripts as well as his personal library (ca 11.100 items) and academic correspondence. The project's goal is to provide access to these materials by means of a digital scholarly edition. A main part is the development of an accurate data model for the description of the legacy as a whole (and thereby giving access to Luhmann's work and knowledge system), showing its relations and context in a semantically accurate and machine-readable way. The poster will be divided in three parts: The first part illustrates the project's platform's functionalities dealing with the legacy and the specific phenomena the material contains. The second part describes the current data model based on TEI/XML[1], its advantages in dealing with these phenomena, and points where it fails to sufice. The third</p>
      </abstract>
      <kwd-group>
        <kwd>eol&gt;Scientific legacy description and indexing</kwd>
        <kwd>Digital Archives</kwd>
        <kwd>Ontologies</kwd>
        <kwd>Knowledge Organisation</kwd>
        <kwd>Digital Humanities</kwd>
      </kwd-group>
    </article-meta>
  </front>
  <body>
    <sec id="sec-1">
      <title>1. Introduction</title>
      <p>
        part tries to answer first problems by showing how an event-based model via FRBRoo[
        <xref ref-type="bibr" rid="ref2">2</xref>
        ] (and
possibly a CIDOC-CRM extension [
        <xref ref-type="bibr" rid="ref3">3</xref>
        ]) can be used as a solution for gaps within the TEI-Model.
      </p>
    </sec>
    <sec id="sec-2">
      <title>2. The Niklas-Luhmann-Archive Digital Edition</title>
      <p>The poster starts with an introduction into the project’s scope and goals by presenting the
online platform and the way in which it provides access to the legacy’s materials within their
context in an appropriate and useful way. It focuses on how the index card links have been
digitally reproduced (figure 1) so as to show the edition’s excellent ability to connect with
Luhmann’s working practice, suggesting how the card index’s linking system and knowledge
organisation work.2</p>
    </sec>
    <sec id="sec-3">
      <title>3. The project’s TEI-Model</title>
      <p>This linking system is currently being modelled using TEI/XML (figure 2). Each index card
is being transcribed using a TEI &lt;div&gt; element. Each card’s data file comprises of a &lt;back&gt;
2A full description of the linking system can be found at https://luhmann1.soz.uni-bielefeld.de/bestand/zettelkasten/
tutorial#p_3 “Punkt (3) Zettelnavigation".
section3, where a &lt;ptr&gt;4 for each link is being created, typed according to the kind of linking.5
The “parent" &lt;linkGrp&gt; element also uses a @type attribute to indicate the link group’s nature.
This linking information provides information when rendering the frontend. In using TEI/XML
the project data is modelled in a standardised way generally accepted and used within the Digital
Humanities community.6 But beyond that it has no deeper meaning that could be interpreted
by non-human (or even non-German speaking) users. Hence there is an urgent need to look for
other ways of modelling to ensure the project data’s long-term sustainability.</p>
    </sec>
    <sec id="sec-4">
      <title>4. FRBRoo/CIDOC-CRM approach</title>
      <p>
        The project decided to base its model for bibliographic items loosely on FRBRer [
        <xref ref-type="bibr" rid="ref4">4</xref>
        ]. These
items exist only “virtually" as bibliographical references on index cards and manu-/typescript
but have proven to be very useful in terms of studying Luhmann’s “workflow". Luhmann
often cited the same literature, making these bibliographic items function as “hubs" that collect
references to all items (cards, typescripts, physical books from his personal library) that cite
this specific literature. The FRBRer oriented model suggested to also use it for modelling the
typescript and publication development (the “Genese"). However, progress in the analysis and
understanding of the work development shows that this approach may not sufice. Figure 3
gives an idea of the current state ot the “Werk-Modell"7 on a theoretical level.
      </p>
      <p>
        Whereas the typescripts individually fit into FRBRoo’s WEMI model (as manifestations) 8,
the typed TEI/XML &lt;ptr&gt; elements used for describing the versions’ development (figure
3https://tei-c.org/release/doc/tei-p5-doc/en/html/ref-back.html
4https://tei-c.org/release/doc/tei-p5-doc/en/html/ref-ptr.html
5Cf. 3.3 Ordnungsprinzip https://niklas-luhmann-archiv.de/nachlass/zettelkasten.
6A complete documentation of the currently used TEI/XML model can be found at https://niklas-luhmann-archiv.
de/projekt/dokumentation (in German).
7The model is not available yet on the project’s webportal, a preliminary version and description have been published
in P. Sahle, J. Schmidt: Der Text des Soziologen. Ist da ein Werk in diesem Nachlass? Präsentation zur GRK-Tagung
29.09.2021.
8Cf. Group 1 entities [
        <xref ref-type="bibr" rid="ref4">4</xref>
        ], p. 13.
4) cannot be mapped that easily. Attempts using R2 is derivative of for the specific relation
“entwickelt_sich_aus" and “textfortsetzung_von" proved unsuccessful. As FRBRoo does not
have any other property available, a look within CIDOC-CRM itself was necessary, starting
with P130 shows features of (as superclass of R2 is derivative of ). Figure 5 shows the proposed
mapping between the project’s TEI/XML model and FRBRoo (version A of the “Werk-Modell"
shown above) and CIDOC-CRM respectively.
      </p>
      <p>Mapping to FRBRoo and CRM seems feasible at this point. However, the progressing
“WerkModell"’ development indicates the necessity of extensions specific to manuscript and work
development and characteristics. The data model development is still in its initial phase and
ongoing, the poster will present the updated status, as well as new findings and decisions.</p>
    </sec>
    <sec id="sec-5">
      <title>5. Online Resources</title>
      <p>• Niklas Luhmann Archive Homepage,
• CIDOC-CRM Homepage,
• FRBRoo - Functional Requirements for Bibliographic Records Model.</p>
    </sec>
  </body>
  <back>
    <ref-list>
      <ref id="ref1">
        <mixed-citation>
          <article-title>[1] P5: Guidelines for electronic text encoding</article-title>
          and
          <source>interchange version 4.4.0. last updated on 19th april</source>
          <year>2022</year>
          , revision
          <year>f9cc28b0</year>
          ,
          <year>2022</year>
          . URL: https://tei-c.org/,
          <source>last accessed 26 June</source>
          <year>2022</year>
          .
        </mixed-citation>
      </ref>
      <ref id="ref2">
        <mixed-citation>
          [2]
          <string-name>
            <given-names>C.</given-names>
            <surname>Bekiari</surname>
          </string-name>
          ,
          <string-name>
            <given-names>M.</given-names>
            <surname>Doerr</surname>
          </string-name>
          ,
          <string-name>
            <given-names>P.</given-names>
            <surname>Le Boeuf</surname>
          </string-name>
          ,
          <string-name>
            <given-names>P.</given-names>
            <surname>Riva</surname>
          </string-name>
          ,
          <article-title>Frbr object-oriented definition and mapping from frbrer, frad and frsad</article-title>
          ,
          <source>version 3.0 september</source>
          <year>2017</year>
          ,
          <year>2017</year>
          . URL: https://www.cidoc-crm.org/ frbroo/sites/default/files/FRBRoo_V3.0.pdf,
          <source>last accessed 26 June</source>
          <year>2022</year>
          .
        </mixed-citation>
      </ref>
      <ref id="ref3">
        <mixed-citation>
          [3]
          <string-name>
            <given-names>C.</given-names>
            <surname>Bekiari</surname>
          </string-name>
          ,
          <string-name>
            <given-names>G.</given-names>
            <surname>Bruseker</surname>
          </string-name>
          , E. Canning,
          <string-name>
            <given-names>M.</given-names>
            <surname>Doerr</surname>
          </string-name>
          ,
          <string-name>
            <given-names>P.</given-names>
            <surname>Michon</surname>
          </string-name>
          , C.-E. Ore,
          <string-name>
            <given-names>S.</given-names>
            <surname>Stead</surname>
          </string-name>
          ,
          <string-name>
            <given-names>A.</given-names>
            <surname>Veli</surname>
          </string-name>
          ,
          <article-title>Definition of the cidoc conceptual reference mode</article-title>
          ,
          <source>version 7.2</source>
          .1,
          <string-name>
            <surname>june</surname>
            <given-names>2022l</given-names>
          </string-name>
          ,
          <year>2022</year>
          . URL: https://cidoc-crm.org/sites/default/files/cidoc_crm_
          <source>version_7.2</source>
          .1.pdf,
          <source>last accessed 26 June</source>
          <year>2022</year>
          .
        </mixed-citation>
      </ref>
      <ref id="ref4">
        <mixed-citation>
          <article-title>[4] Functional requirements for bibliographic records: Final report</article-title>
          ,
          <year>february 2009</year>
          ,
          <year>2009</year>
          . URL: https://repository.ifla.org/handle/123456789/811, last accessed
          <issue>26</issue>
          <year>June 2022</year>
          .
        </mixed-citation>
      </ref>
    </ref-list>
  </back>
</article>