diff --git a/2023_007_leipold_et_al/dejonge_001.jpg b/2023_007_leipold_et_al/dejonge_001.jpg new file mode 100644 index 0000000000000000000000000000000000000000..d376e85c02a4fead2cbf98af3c499e56d6c62e18 Binary files /dev/null and b/2023_007_leipold_et_al/dejonge_001.jpg differ diff --git a/2023_007_leipold_et_al/dejonge_002.jpg b/2023_007_leipold_et_al/dejonge_002.jpg new file mode 100644 index 0000000000000000000000000000000000000000..d660bb25a4a7a55830f1c82587721fbf6236fc8f Binary files /dev/null and b/2023_007_leipold_et_al/dejonge_002.jpg differ diff --git a/2023_007_leipold_et_al/dejonge_003.jpg b/2023_007_leipold_et_al/dejonge_003.jpg new file mode 100644 index 0000000000000000000000000000000000000000..9fa4840c4bbb35ee3dc203cc26300743db92aea3 Binary files /dev/null and b/2023_007_leipold_et_al/dejonge_003.jpg differ diff --git a/2023_007_leipold_et_al/dejonge_004.jpg b/2023_007_leipold_et_al/dejonge_004.jpg new file mode 100644 index 0000000000000000000000000000000000000000..50cc562f82189c04f0dc9cf57f4d394275e7a393 Binary files /dev/null and b/2023_007_leipold_et_al/dejonge_004.jpg differ diff --git a/2023_007_leipold_et_al/dejonge_005.jpg b/2023_007_leipold_et_al/dejonge_005.jpg new file mode 100644 index 0000000000000000000000000000000000000000..62b3714f674abea3532af27f15f9c008a96390d5 Binary files /dev/null and b/2023_007_leipold_et_al/dejonge_005.jpg differ diff --git a/2023_007_leipold_et_al/dejonge_006.jpg b/2023_007_leipold_et_al/dejonge_006.jpg new file mode 100644 index 0000000000000000000000000000000000000000..aeab0d4c3d66c03f88fe16aa0b6290195ca24668 Binary files /dev/null and b/2023_007_leipold_et_al/dejonge_006.jpg differ diff --git a/2023_007_leipold_et_al/dejonge_007.jpg b/2023_007_leipold_et_al/dejonge_007.jpg new file mode 100644 index 0000000000000000000000000000000000000000..fd45cadaf5e0094afa6dabfc56f3f8bf0c147812 Binary files /dev/null and b/2023_007_leipold_et_al/dejonge_007.jpg differ diff --git a/2023_007_leipold_et_al/dejonge_008.jpg b/2023_007_leipold_et_al/dejonge_008.jpg new file mode 100644 index 0000000000000000000000000000000000000000..4dede69b1e276b9dbfbdcbd43af1863ae4d4ed7d Binary files /dev/null and b/2023_007_leipold_et_al/dejonge_008.jpg differ diff --git a/2023_007_leipold_et_al/dejonge_009.jpg b/2023_007_leipold_et_al/dejonge_009.jpg new file mode 100644 index 0000000000000000000000000000000000000000..b5f340a11e40e3e35a54ed9cbaf37635dfb1ee1e Binary files /dev/null and b/2023_007_leipold_et_al/dejonge_009.jpg differ diff --git a/2023_007_leipold_et_al/dejonge_2023_v1_0.pdf b/2023_007_leipold_et_al/dejonge_2023_v1_0.pdf new file mode 100644 index 0000000000000000000000000000000000000000..156ef71f75044f0a75a3b00adea4e45946637b93 Binary files /dev/null and b/2023_007_leipold_et_al/dejonge_2023_v1_0.pdf differ diff --git a/2023_007_leipold_et_al/dejonge_2023_v1_0.xml b/2023_007_leipold_et_al/dejonge_2023_v1_0.xml new file mode 100644 index 0000000000000000000000000000000000000000..beff5576f3607c7013d2a8c754a4920413dc5d86 --- /dev/null +++ b/2023_007_leipold_et_al/dejonge_2023_v1_0.xml @@ -0,0 +1,856 @@ +<?xml version="1.0" encoding="utf-8"?> +<?xml-model href="https://www.zfdg.de/sites/default/files/schema/tei_zfdg.rnc" type="application/relax-ng-compact-syntax" + ?> +<TEI xmlns="http://www.tei-c.org/ns/1.0" xmlns:html="http://www.w3.org/1999/html" + xmlns:tei="http://www.tei-c.org/ns/1.0" xmlns:xhtml="http://www.w3.org/1999/xhtml" + xmlns:xlink="http://www.w3.org/1999/xlink"> + <teiHeader> + <fileDesc> + <titleStmt> + <title> + <biblStruct> + <analytic> + <title level="a">Knowledge for Men and Machines. The De Jonge Wiki as an + Example of a Scientific Research Database</title> + <respStmt> + <persName role="author"> + <forename>Frieder</forename> + <surname>Leipold</surname> + <email>fhleipold@gmail.com</email> + <idno type="gnd">1216729212</idno> + <idno type="orcid">0000-0001-8848-9186</idno> + <affiliation>Katholieke Universiteit Leuven</affiliation> + </persName> + <resp ref="http://id.loc.gov/vocabulary/relators/aut">Author</resp> + <resp ref="https://credit.niso.org/contributor-roles/writing-original-draft/">Writing â€“ original draft</resp> + </respStmt> + <respStmt> + <persName role="author"> + <forename>Max</forename> + <surname>Kristen</surname> + <email>max@kristenonline.de</email> + <idno type="gnd">129986709X</idno> + <affiliation>Ludwig-Maximilians-Universität München</affiliation> + </persName> + <resp ref="http://id.loc.gov/vocabulary/relators/aut">Author</resp> + <resp ref="https://credit.niso.org/contributor-roles/writing-original-draft/">Writing â€“ original draft</resp> + </respStmt> + <respStmt> + <persName role="author"> + <forename>Krista</forename> + <surname>de Jonge</surname> + <email>krista.dejonge@kuleuven.be</email> + <idno type="gnd">137431058</idno> + <idno type="orcid">0000-0002-6321-7392</idno> + <affiliation>Katholieke Universiteit Leuven</affiliation> + </persName> + <resp ref="http://id.loc.gov/vocabulary/relators/aut">Author</resp> + <resp ref="https://credit.niso.org/contributor-roles/writing-original-draft/">Writing â€“ original draft</resp> + </respStmt> + <respStmt> + <persName> + <forename>Aaron</forename> + <surname>Pattee</surname> + <affiliation>Ludwig-Maximilians-Universität München</affiliation> + </persName> + <resp ref="https://credit.niso.org/contributor-roles/conceptualization/">Conceptualization</resp> + </respStmt> + <respStmt> + <persName> + <forename>Vincent</forename> + <surname>Vanhamme</surname> + <affiliation>Katholieke Universiteit Leuven</affiliation> + </persName> + <resp ref="https://credit.niso.org/contributor-roles/data-curation/">Data curation</resp> + </respStmt> + <respStmt> + <persName> + <forename>Aline</forename> + <surname>Van Diessche</surname> + <affiliation>Katholieke Universiteit Leuven</affiliation> + </persName> + <resp ref="https://credit.niso.org/contributor-roles/data-curation/">Data curation</resp> + </respStmt> + <idno type="doi">10.17175/2023_007</idno> + <idno type="ppn">1851331751</idno> + <idno type="url">https://www.zfdg.de/node/459</idno> + <date when="2023-09-21">21.09.2023</date> + </analytic> + <monogr> + <title level="j">Zeitschrift für digitale Geisteswissenschaften</title> + <respStmt> + <resp>Publiziert von</resp> + <orgName role="marc_pbl">Herzog August Bibliothek</orgName> + </respStmt> + <respStmt> + <resp ref="http://id.loc.gov/vocabulary/relators/dtm">Transformation der Word Vorlage nach TEI</resp> + <persName> + <surname>Baumgarten</surname> + <forename>Marcus</forename> + <idno type="gnd">1192832655</idno> + <idno type="orcid">0000-0003-0801-9462</idno> + </persName> + </respStmt> + + <availability status="free"> + <p>Available at <ref target="https://www.zfdg.de">https://www.zfdg.de</ref></p> + </availability> + <biblScope unit="year">2023</biblScope> + <biblScope unit="artikel">07</biblScope> + </monogr> + </biblStruct> + </title> + </titleStmt> + <editionStmt> + <edition>Elektronische Ausgabe nach TEI P5</edition> + </editionStmt> + <publicationStmt> + <distributor> + <name> + <orgName>Herzog August Bibliothek Wolfenbüttel</orgName> + </name> + </distributor> + <idno type="doi">10.17175/zfdg.01</idno> + <idno type="ppn">0819494402</idno> + <authority> + <name>Herzog August Bibliothek</name> + <address> + <addrLine>Lessingplatz 1</addrLine> + <addrLine>38304 Wolfenbüttel</addrLine> + </address> + </authority> + <authority> + <name>Forschungsverbund Marbach Weimar Wolfenbüttel</name> + <address> + <addrLine>Burgplatz 4</addrLine> + <addrLine>99423 Weimar</addrLine> + </address> + </authority> + <availability status="free"> + <p>Sofern nicht anders angegeben</p> + <licence target="http://creativecommons.org/licenses/by/4.0/">CC BY SA 4.0</licence> + </availability> + <availability status="free"> + <p>Available at <ref target="https://www.zfdg.de">https://www.zfdg.de; (c) Forschungsverbund MWW</ref></p> + </availability> + </publicationStmt> + <sourceDesc> + <p>Einreichung als Projektvorstellung in der ZfdG durch die Autor*innen</p> + </sourceDesc> + </fileDesc> + <encodingDesc> + <editorialDecl> + <p>Transformation der WORD-Vorlage nach XML/TEI-P5 durch TEI-Oxgarage und XSLT-Skripten</p> + </editorialDecl> + <editorialDecl> + <p xml:lang="de">Lektorat des Textes durch die Redaktion in Person von <persName>Martin de la Iglesia</persName>.</p> + </editorialDecl> + <editorialDecl> + <p>Medienrechte liegen bei den Autor*innen</p> + </editorialDecl> + <editorialDecl> + <p>All links checked<date when="2023-08-25">25.08.2023</date></p> + </editorialDecl> + </encodingDesc> + <profileDesc> + <creation>Einreichung als Artikel der Zeitschrift für digitale + Geisteswissenschaften</creation> + <langUsage> + <language ident="en">Text auf Englisch</language> + <language ident="de">Abstract auf Deutsch</language> + <language ident="en">Abstract auf Englisch</language> + </langUsage> + <textClass> + <keywords scheme="gnd"> + <term>Denkmalpflege<ref target="4011455-7"/></term> + <term>Schloss<ref target="4052753-0"/></term> + <term>Semantisches Datenmodell<ref target="4314515-2"/></term> + <term>Virtuelle Forschungsumgebung<ref target="7741762-8"/></term> + <term>Wiki<ref target="4806885-8"/></term> + </keywords> + </textClass> + </profileDesc> + <revisionDesc> + <change/> + </revisionDesc> + </teiHeader> + <text> + <body> + <div> + <div type="abstract"> + <argument xml:lang="en"> + <p>The De Jonge Wiki is a digital, scientific research database on the building + history of Arenberg Castle in Heverlee, Belgium. As a prototype it is intended + to show how information on complex structures can be presented according to + today’s state of the art. The aim is to work according to international quality + standards as well as making the information easily accessible to users. For + this purpose, both MediaWiki and Wikibase were used as software. In this way, a + user interface was created that is visually and functionally reminiscent of + Wikipedia and can therefore be intuitively understood by users without prior + knowledge while the corresponding semantic data is stored in a database in the + background.</p> + </argument> + <argument xml:lang="de"> + <p>Das De Jonge Wiki ist eine digitale, wissenschaftliche Forschungsdatenbank zur + Baugeschichte des Kasteels van Arenberg in Heverlee in Belgien. Als Prototyp + soll sie zeigen, wie Informationen über komplexe Strukturen gemäß dem aktuellen + Stand der Technik präsentiert werden können. Das Ziel besteht darin, nach + internationalen Qualitätsstandards zu arbeiten und gleichzeitig die + Informationen für Benutzer*innen leicht zugänglich zu machen. Zu diesem Zweck wurden + sowohl MediaWiki als auch Wikibase als Software verwendet. Auf diese Weise + wurde ein Interface erstellt, das optisch und funktional an Wikipedia + erinnert und damit von Nutzer*innen ohne Vorwissen intuitiv verstanden werden + kann, während die dazugehörigen semantischen Daten in einer Datenbank im + Hintergrund gespeichert werden.</p> + </argument> + </div> + <div type="chapter"> + <head>1. Introduction</head> + <p>In order to classify the considerations underlying the <ref + target="https://set.kuleuven.be/rlicc/dejongewiki/w/index.php/Main_Page">De + Jonge Wiki</ref>, a look far back into history can illustrate the mechanisms + associated with data carriers. Around the middle of the 6th century BC Croesus, the King of + Lydia, minted his heraldic animals on standardized gold and silver blanks (<ref type="graphic" target="#abb01">Figure 1</ref>). This procedure + initiated the era of coins as a currency. However, Croesus had not only created a + means of payment, but also a data carrier, which contained information on the + wealth or the geographic range of influence of a certain regime.</p> + <figure> + <graphic xml:id="abb01" url="Medien/dejonge_001.jpg"> + <desc> + <ref type="graphic" target="#abb1">Fig. 1</ref>: Stater of Croesus, around 550 BC (16 mm, 10.76 g), minted in + Sardis. [Photograph: <ref + target="https://commons.wikimedia.org/wiki/File:Kroisos._Circa_564-53-550-39_BC._AV_Stater_(16mm,_10.76_g)._Heavy_series._Sardes_mint.jpg" + >Classical Numismatic Group, Inc. http://www.cngcoins.com. CC BY-SA + 3.0</ref>]</desc> + </graphic> + </figure> + <p>Especially for archaeologists, coins are an ideal supplier of information. They + enable the dating of an excavation layer, give evidence of trading connections and + the political and economic conditions of a certain period. However, these data + carriers used for thousands of years are increasingly disappearing from everyday + use in the living presence. With digital payment methods, there is hardly any use + for coins anymore. A millennia old cultural practice seems to approach its + end.<note type="footnote"> In Belgium, cent amounts are rounded to 5-cent + multiples in retail since December 2019, so that one- and two-cent pieces are + virtually no longer in circulation.</note> + </p> + <p>However, payment transactions are only one field in which currently the exchange + of information runs almost only digitally. As comfortable as the new, electronic + forms of communication are for humankind living today, it remains unclear how + information of our era will be usable in the long term. To interpret the cuneiform + on a clay tablet, the hieroglyphs on a stone stele or the ancient Hebrew on a + scroll, one must only know the respective writing system to be able to read it. + But when it comes to reading a digital document one must not only provide the + electronic hardware but also the matching software to simply make a text visible + at all. </p> + <p>The transmission of our current knowledge to future generations is thus + inseparably linked with electronic technology â€“ and thus with the risk of being + lost. The development of digital media shows how real and inherent this danger is. + Who can run a floppy disk or a VHS video cassette today? With every transfer of + data to a new medium, parts of information get lost. Around 400 AD a similar media + change seems to have been one of the causes of the so-called ›loss of books in + late antiquity‹ when bound codices of parchment replaced scrolls of papyrus. + Thereafter 1,400 years had to pass until modern libraries had again comparable + stocks as they are recorded for ancient libraries.</p> + <figure> + <graphic xml:id="abb02" url="Medien/dejonge_002.jpg"> + <desc> + <ref type="graphic" target="#abb2">Fig. 2</ref>: Rome and the ›dark centuries‹, the history of libraries in the + period of 300 BC until 2000 AD. [Chart: <ref target="https://commons.wikimedia.org/wiki/file:bibsta4.jpg">Bibhistor, CC BY-SA 3.0</ref>]</desc> + </graphic> + </figure> + <p>In the case of digitally stored data, there is another threat of loss that results + from the programs with which the data is stored. Specialized software can often + only be used with fixed-term licenses. If users do not have the corresponding + license (anymore), the data is unreadable to them. The same applies to the further + development of software. Due to the progress and development of programs, it is + possible that data records cannot be opened only a few years or updates after they + have been saved. Datasets that are not worked with, maintained, used or changed, + are in danger of becoming lifeless mummies in digital sarcophagi, of which it is + uncertain whether they can ever be recovered again.</p> + <p>In this regard, the very technical progress and digital development to store data + generates gigantic centrifugal forces and corrosive powers that threaten the + continued existence and further usability of records. Since these relationships + are inherent to the system, it is important to look for ways to prepare + information in such a way so that it can react as flexibly to these developments + as possible and remain accessible for as many users as possible. </p> + <p>In awareness of these challenges, the De Jonge Wiki was created as a prototype to + prepare data according to certain specifications. As medium of choice, a freely + accessible online database with English as operating language was selected, to be + easily accessible for interested users. As a software, the open source and cost + free products <ref target="https://www.mediawiki.org/wiki/MediaWiki" + >MediaWiki</ref> and the potent extension <ref target="https://wikiba.se/" + >Wikibase</ref> of the <ref target="https://wikimediafoundation.org/">Wikimedia + Foundation</ref> were chosen. This selection offers the advantage that the + required functions are tested, stable, and established by the daily use of + millions of users of the Wiki community.</p> + <p>MediaWiki software has a routine update path with only a few disruptive changes. + In addition, there are a number of ways to export to a wide variety of formats, + which is beneficial to the integrity and extensive use of the data. Furthermore, + there is the potential for communication and automated alignment with similarly + designed databases. Another important aspect is that other organizations that are + interested can adopt and adapt the data management structure used here for their + own projects. </p> + <p>Since April 2021, the De Jonge Wiki has been developed as part of a cooperation of + the EU-funded PALAMUSTO project (Grant Agreement ID: 861426) with the Institute of + Computer Science, Teaching and Research Unit for Programming and Modeling + Languages of the Ludwig-Maximilians University of Munich (LMU) and the Raymond + Lemaire International Center for Conservation (RLICC) of KU Leuven with support + from the Institute of Technology Recruitment (ITZ) of the Karlsruhe Institute of + Technology (KIT) and is still progressing.</p> + </div> + <div type="chapter"> + <head>2. Discussion</head> + + <div type="subchapter"> + <head>2.1 Building History of Arenberg Castle</head> + + <p>Arenberg Castle in Heverlee (<ref type="graphic" target="#abb03" + >Figure 3</ref>) was a fitting choice for a case study because it is both + well studied and of a manageable scale. The first mention of a castle in + Heverlee dates back to 1371, although a fortified building can be assumed to + have existed for centuries before that. The donjon of which we know from + pictorial representations seems to have been built in the first half of the + 15th century under Raas van Graven or Antoine I de Croÿ.<note + type="footnote"> In May 2023, archaeological excavations uncovered the + remains of the fortifications around the donjon (cf. <ref type="bibliography" target="#smitz_studenten_2023">Smitz 2023</ref>).</note> + The decisive expansion into a representative hunting lodge happened under + William de Croÿ, probably between 1505 and 1520, when the southern wing with + the two corner towers and significant parts of the western wing were built. + The most important pictorial and written sources for the early history of + the castle were created under the reign of Charles III de Croÿ around + 1600.<note type="footnote"> Cf. <ref type="bibliography" target="#jonge_kasteel_2002">De Jonge et al. 2002</ref>; + <ref type="bibliography" target="#jonge_schloss_2004">De Jonge + 2004</ref>.</note> + </p> + <figure> + <graphic xml:id="abb03" url="Medien/dejonge_003.jpg"> + <desc> + <ref type="graphic" target="#abb3">Fig. 3</ref>: South facade of Arenberg Castle, above [image: KU Leuven / + Koufopoulos et al. 2021]; aerial view of the main building, left [image: KU + Leuven / Koufopoulos et al. 2021]; floor plan of the ground floor with color + labeling of different structural units, right. [Image: atlas plan, KU + Leuven, <ref target="https://admin.kuleuven.be/td/en/index">Technical + Services</ref>]</desc> + </graphic> + </figure> + <p>In the late 18th century, a new building replaced the burned-down parts of + the west wing, the east wing was built in two campaigns and the already + existing rooms were redivided in the style of Baroque and Classicism and + some mezzanines were installed.<note type="footnote"> Cf. <ref type="bibliography" target="#vlaardingerbroek_arenberger_2004">Vlaardingerbroek + 2004</ref>.</note> In the late 19th century, the castle underwent further + extensions and additions in the neo-Gothic style by the architects Joseph + Claes, Joris Helleputte, Alexis Raskin and Jules Picquet.<note + type="footnote"> Cf. <ref type="bibliography" target="#bries_architectuur_1991">Brìes 1991</ref>.</note> + </p> + <p>After the castle was handed over to the University of Leuven, further + transformations by Emile Goethals in 1925 continued to follow the neo-Gothic + style. Between 1958 and 1971, Raymond Lemaire’s restoration work attempted to + recreate the state of the first phase of construction. As the last major + interventions in the building structure, further additions in a post-modern + look were designed between 1973 and 1998 by Paul Van Aerschot.<note + type="footnote"> Cf. <ref type="bibliography" target="#koufopoulos_castle_2021">Koufopoulos et al. 2021</ref>.</note> + </p> + <p>For more than 25 years, professors, lecturers, and students of architecture + or the <ref target="https://set.kuleuven.be/rlicc/education/study-programme" + >Master in Conservation of Monuments and Sites</ref> program at KU Leuven + have been studying the architectural history of the palace. In projects such + as the ArchDoc program on documenting findings of building archaeology, over + 20 experts and staff members have collected rich experience over the years, + which has been documented in various forms, some only in analogue form, some + already in digital form. Pooling this knowledge and making an overview of + the collected information available online is the task that the De Jonge + Wiki aims to serve. As one of the honorary professors, Krista De Jonge led + the various research projects over the entire period mentioned. On the + initiative of the researchers of the Wiki project, she therefore agreed to + the usage of her name for the database.</p> + </div> + <div type="subchapter"> + <head>2.2 MediaWiki and Wikibase</head> + + <p>The documentation of the architectural history of Arenberg Castle builds on + the findings and insights made by Jan Lutteroth and Frieder Leipold under + the direction of Stephan Hoppe within the interdisciplinary cooperation + project <bibl> + <title type="desc">Kulturliegenschaften 4.0</title> + </bibl>.<note type="footnote"> This initiative was financed by the + Baden-Württemberg Ministry of Finance as part of the first digital agenda + for Baden-Württemberg (digital@bw 2018/19) and is intended to develop + innovative approaches to cultural heritage. The partner directly involved + in this case was the administration of the State Palaces of + Baden-Württemberg, which is also a cooperation partner within the + PALAMUSTO project.</note> In this project, a digital, semantic research + database was created for the building history of Schloss Weikersheim in + Baden-Württemberg, Germany.<note type="footnote"> Cf. <ref type="bibliography" target="#kulturliegenschaften_rekonstruktion_2023">Virtuelle + Rekonstruktion 2023</ref>. </note> This database was set up as a <ref + target="https://wiss-ki.eu/">WissKI</ref> database following the ontology + of <ref target="https://cidoc-crm.org/">CIDOC CRM</ref>. The digital + infrastructure for this project was provided under the direction of Piotr + KuroczyÅ„ski and Peggy Große at the University of Mainz.<note type="footnote" + > On semantic databases for the documentation of 3D reconstructions see: + <ref type="bibliography" target="#lutteroth_schloss_2018">Lutteroth / Hoppe 2018</ref>; + <ref type="bibliography" target="#kuroczynski_museum_2015">KuroczyÅ„ski et al. 2015</ref>.</note> + </p> + <p>While the Weikersheim database was thus created with a software that has + been developed for academic research, the database on the building history + of Arenberg Castle was created with Wiki software. By doing so, two basic + requirements were to be fulfilled above all others. The first requirement + was the modelling of the data according to international standards, so that + the records are machine-interpretable. For this, the software Wikibase was + used, which also forms the basis for the semantic database <ref + target="https://www.wikidata.org/wiki/Wikidata:Main_Page">Wikidata</ref>. + However, such collections of data sheets that are linked together according + to the principle of knowledge graphs are difficult to grasp for human users + without prior knowledge and education.<note type="footnote"> Cf. + <ref type="bibliography" target="#baru_knowledge_2021">Baru 2021</ref>. + </note> They contain the danger to appear like reference deserts without a + human touch and can have a repulsive effect â€“ especially for researchers + from the humanities.</p> + <p>Because of this, the second main concern of the project was to strive for a + user interface based on Wikipedia, so that users will be spared the anxiety + threshold of the new and unknown. Instead they should be able to move in an + environment where design and functions are known to them from their daily + use of Wikipedia. To achieve this goal, it was obvious to use MediaWiki, the + same software with which Wikipedia is operated. In addition, it also offers + all opportunities for joint editing and documentation of editorial changes + that are offered by Wikipedia as well. It can thus be used as a <term + type="dh">Virtual Research Environment</term> (<term type="dh" + >VRE</term>)<note type="footnote"> Cf. + <ref type="bibliography" target="#carusi_research_2010">Carusi / Reimer 2010</ref>.</note> for + the exchange between the different researchers involved. First projects with + students also showed that the infrastructure of the De Jonge Wiki is + particularly well suited for <term type="dh">Peer Assisted Learning</term> + (<term type="dh">PAL</term>) in academic education, where students support + each other with their respective skills in mastering a task. Another + advantage of using an established software ecosystem is the variety of + additional tools and functionalities, for example the accessibility for + users with disabilities and their tools such as screen readers.</p> + <p>An additional benefit of using Wikimedia Foundation software is the + possibility of linking to other platforms besides Wikidata and Wikipedia, + such as <ref target="https://commons.wikimedia.org/wiki/Main_Page">Wikimedia + Commons</ref>. In this media repository, free-to-use images, sound + documents and videos as well as other media such as 3D objects can be + published. In digital infrastructures, which are based on Wikibase or + MediaWiki as software, these media can be integrated as preview images by + simple linking, while hosting and all related activities are taken over and + provided by Wikimedia Commons. This not only has the advantage that the + hosting is outsourced, but also that the media in question can also be found + in an environment used by a wider public.</p> + <p>Due to the limited options for displaying 3D objects on Wikimedia Commons, + three additional methods for embedding 3D files via <term type="dh" + >iframes</term> were tested. Firstly, <ref + target="https://sketchfab.com/">Sketchfab</ref>, which proved to be + technically straightforward. However, being a software from a commercial + provider, this solution does not align with the <term type="dh" + >FAIR/O</term> principles and can only be used as a temporary solution. + Therefore, for future integrations of digital 3D models as iframes, the use + of the <ref target="https://kompakkt.de/home">Kompakkt</ref> platform is + planned. Kompakkt is an extension of the e-learning software ILIAS developed + by the Department of Digital Humanities at the Faculty of Arts and + Humanities of the University of Cologne. Another option is Semantic + Kompakkt, a technical advancement of Kompakkt developed within the + NFDI4Culture initiative.<note type="footnote"> Cf. <ref type="bibliography" target="#nfdi_semantic_2023">Semantic Kompakkt 2023</ref>. + </note> It is a free, open-source toolchain for viewing and enriching data + of 3D models, and similarly to the De Jonge Wiki it uses Wikibase for + processing statistical data. However, experiments in collaboration with + Lozana Rossenova from the Technische Informationsbibliothek (TIB) in Hanover + showed that using this infrastructure would have only made sense if Semantic + Kompakkt had been implemented in the logic of the Wikibase records from the + beginning of the De Jonge Wiki project. Nonetheless, this option presents a + promising possibility for future projects.</p> + </div> + <div type="subchapter"> + <head>2.3 Data Structure</head> + + <p>Basically, it can be said that there are several options when creating a + scientific research database. On the one hand, there is the <term type="dh" + >Relational Database Management System</term> (<term type="dh" + >RDBMS</term>), in which entities are assigned different properties, in + the style of different columns in tables. On the other hand, there are graph + databases in which information is stored as knowledge graphs, that means as + different entities that can be linked to one another by properties. One + possible concept for such graph databases are <term type="dh">Labeled + Property Graphs</term> (<term type="dh">LPG</term>), which means that the + connection between certain entities is expressed in main properties which + are attached to a node and additional simple key–value pairs: <quote>Lauren + Bacall (date of birth: 16.09.1924; place of birth: The Bronx) was married + to Humphrey Bogart</quote>. In contrast, information in <term type="dh" + >Resource Description Framework</term> (<term type="dh" + >RDF</term>) graphs is expressed in so-called semantic triples consisting of + Subject–Predicate–Object: <quote>Lauren Bacall was married to Humphrey + Bogart; Lauren Bacall was born on 16.09.1924; Lauren Bacall was born in + the Bronx.</quote> This means that all entities are interconnected by a + particular property, thus forming a semantic triple. The Wikibase division + of the De Jonge Wiki is such an RDF database.</p> + <p>The structure of a castle is particularly suitable for a clearly defined and + structured database with a hierarchy or taxonomy. In this case, the entire + complex of the castle with its topography and all associated architectural + facilities is defined as the highest level. The initials AC for Arenberg + Castle as part of their name mark all elements that are components of this + complex. The main buildings of the castle are referred to by the initials MC + for Main Castle. This Main Castle is in turn divided into the various wings + and construction volumes, each defined by initials, such as for example EW + for the East Wing. These wings again consist of different floors as well as + facades and roofs, such as the first floor expressed as 1F. At the lowest + level are the individual rooms designated by the currently used room + numbers. The entire name of letter pairs thus refers to the position of the + room in question (<ref type="graphic" target="#abb04">Figure + 4</ref>) like coordinates, as it were. In a way, this approach + corresponds to the traditional room books<note type="footnote"> Cf. e. g. + <ref type="bibliography" target="#bsv_raumbuch_2021">Bayerische Schlösserverwaltung (ed.) 2021</ref>.</note> used in older + architectural research and can provide the information given there in a more + flexible and digitally networked manner.</p> + <figure> + <graphic xml:id="abb04" url="Medien/dejonge_004.jpg"> + <desc> + <ref type="graphic" target="#abb4">Fig. 4</ref>: Structure of the room designations in the De Jonge Wiki. + [Chart: Frieder Leipold 2021]</desc> + </graphic> + </figure> + <p>For each such architectural unit an entry was created in the De Jonge Wiki + both as a MediaWiki file and as a connected Wikibase file. In the MediaWiki + entry, the information is published as text and images in the style of + Wikipedia and â€“ if possible â€“ gives an overview of the findings to the + respective building history. In the Wikibase entry, however, statistical + information is stored in the form of RDF knowledge graphs. </p> + <p>These relationships are modelled according to a defining system, a so-called + ontology, as for example CIDOC CRM (Comité International pour la + Documentation Conceptual Reference Model). In a database, an ontology forms + the intended frame of reference, which is then filled with the contents of + the respective data records. The Wikibase datasheets of the De Jonge Wiki + are based on the ontology on which also Wikidata is based. This decision was + made, on the one hand, because this type of data modelling is applied by an + influential and internationally accepted structure as Wikidata and, on the + other hand, because this ontology is not a rigid and hierarchical taxonomy, + such as CIDOC CRM, but flat and flexible and can be adapted to the + requirements of the respective records. This makes it easily possible to + integrate new insights and research approaches seamlessly into existing + data.</p> + <p>Due to the aim that users should be able to make data entries in the De + Jonge Wiki with as short a training as possible, the structure was + deliberately kept as simple as possible. There are only three page + categories in the frontend (<ref type="graphic" target="#abb05" + >Figure 5</ref>), namely:</p> + <list> + <item>architectural structures (rooms, floors, facades, roofs, wings)</item> + <item>scientific sources (articles, research reports, scans and + photogrammetric images) </item> + <item>historical sources (archival records, artefacts and historical + photos)</item> + </list> + <figure> + <graphic xml:id="abb05" url="Medien/dejonge_005.jpg"> + <desc> + <ref type="graphic" target="#abb5">Fig. 5</ref>: Structural logic of the page categories. [Chart: Frieder + Leipold 2021]</desc> + </graphic> + </figure> + <p>As already discussed, the architectural structures represent the basic + units. In their Wikibase data sheets, statistical information such as + length, width, maximum height and area are given, but also to which next + higher category the architectural structure belongs (Property:P34 ›part + of‹). In addition, it is indicated through which other rooms the room in + question can be entered in the current situation (Property:P16 ›Accessible + from‹). </p> + <figure> + <graphic xml:id="abb06" url="Medien/dejonge_006.jpg"> + <desc> + <ref type="graphic" target="#abb6">Fig. 6</ref>: Example of a data sheet in the Wikibase database. [Screenshot + De Jonge Wiki]</desc> + </graphic> + </figure> + <p>All of this information is indicated on the frontend using a template and + can be seen as an info box at the top right there. To get to the frontend, + you simply have to click on the link in the data sheet at the bottom right. + Conversely, to get from the frontend to the corresponding data sheet, there + is the ›De Jonge Wiki item‹ function in the left-hand column, which takes + users to the Wikibase data sheet.</p> + <figure> + <graphic xml:id="abb07" url="Medien/dejonge_007.jpg"> + <desc> + <ref type="graphic" target="#abb7">Fig. 7</ref>: Example of a front-end article for a room. [Screenshot De Jonge + Wiki]</desc> + </graphic> + </figure> + <p>Other important information given in the data sheet are references to + scientific and historical sources where information about the architectural + structure in question can be found. The cells with these references are + linked directly to the entries on the relevant articles in the info box. + These links are generated automatically by entering the titles of the + articles in the Wikibase data sheet. However, the article pages of this + source material are only visible in the frontend to users who are logged in. + The reason for this access restriction is the fact that content in this + category is specially affected by copyright and data protection law. Some of + the research projects listed here were part of student education and are + treated as personal data.</p> + <p>Further information and previous research results can be discussed in the + text sections in the pages on the historical sources. In the case of written + archival material, the scan of a page and both the transcription and a + translation proposal can be displayed next to one another in a list.</p> + <figure> + <graphic xml:id="abb08" url="Medien/dejonge_008.jpg"> + <desc> + <ref type="graphic" target="#abb8">Fig. 8</ref>: Example of a front-end article on a historical source. + [Screenshot De Jonge Wiki]</desc> + </graphic> + </figure> + <p>In the case of scientific sources, on the other hand, usually only editorial + information such as authors, year and place of publication or number of + pages is given (<ref type="graphic" target="#abb09">Figure + 9</ref>). Historical sources and scientific sources can also be linked + directly to one another when the historical one is one of the main subjects + of the scientific one (Property:P28 ›Main subject‹). In this way, one + obtains a clear listing of all investigations that have already been carried + out on a specific part of the architecture.</p> + <p>Thus, the De Jonge Wiki tries to prepare diverse research data according to + the FAIR/O principles: Findable, Accessible, Interoperable, and Reusable + with the help of free Open license software. By adopting the digital + infrastructure developed as a prototype, other scientific projects or + cultural organizations can prepare their data effectively and valuable and + make it publicly accessible in a user-friendly way.</p> + <figure> + <graphic xml:id="abb09" url="Medien/dejonge_009.jpg"> + <desc> + <ref type="graphic" target="#abb9">Fig. 9</ref>: Example of a front-end article on a scientific source. + [Screenshot De Jonge Wiki]</desc> + </graphic> + </figure> + </div> + <div type="subchapter"> + <head>2.4 Open Questions and Challenges</head> + + <p>Fortunately, when the basic considerations were implemented in a functioning + database, all of the intended aspects could be set up without major + problems. When the data was entered by student research assistants, it was + found that the structure can be understood intuitively after a short + briefing. This made it possible that the student research assistants could + follow the underlying logic intuitively and suggest and implement their own + additions in order to optimize the database. In practice, + however, there were also some challenges that could not be optimally met + within a very limited time and budget framework. </p> + <p>Even at the beginning of the implementation, it became clear that the web + space, which was kindly provided by KU Leuven, did not enable an easy way to + use the Docker version of Wikibase. This is mainly due to the fact that the + University is primarily interested in protecting its own research + achievements from access by third parties. A classic virtual machine (VM) + service operation as an execution environment for Docker or other container + systems was classified as too vulnerable in regard to data security. + Therefore some practical additional services such as the <ref target="https://www.mediawiki.org/wiki/Wikidata_Query_Service/User_Manual">›Query Service‹</ref> are not yet available at the De Jonge Wiki. This + would have offered a simple, user-friendly possibility to design queries in + the <ref target="https://www.w3.org/TR/sparql11-query/">SPARQL</ref> + scripting language via the dataset in Wikibase, as well as the graphic + representation of these search results. In addition, overview pages cannot + simply be generated in this way, for example a list of all items that are + identified as rooms (Property:P2 ›instance of‹; Item:Q257 ›Room‹). In order + to still be able to have a classification, the articles in the frontend must + be tagged and marked in accordance with the categories in Wikibase. This + requires a double administration, which may eventually result in + inconsistent information.</p> + <p>The fact that Docker cannot be used also means that software updates have to + be installed manually with more effort, which is why a certain amount of + expert knowledge is required in dealing with MediaWiki software. However, + administrators often have experience in using these solutions, especially at + universities which provide wikis to support teaching, and should therefore + be able to cope with this challenge. The De Jonge Wiki is in the process of + moving to an environment in summer 2023 where Docker and SPARQL queries can + be used and where the data will be backed up on a local server for improved + security.</p> + <p>Another unavoidable issue is that the datasets are not perfectly uniform + because of the human factor, as several employees work on the same datasets + in different daily conditions. These inconsistencies would also have been + easier to identify and fix if certain Wikidata approaches had been + integrated into the project; among other things, the query service, but also + restrictions on property fields or shape expressions would have been valid + approaches to reduce these problems, but have not yet been implemented.<note + type="footnote"> Cf. <ref type="bibliography" target="#mediawiki_wikibase_2023">Extension: WikibaseQualityConstraints 2023</ref>; + <ref type="bibliography" target="#mediawiki_entity_2023">Extension: EntitySchema 2023</ref>.</note> + </p> + <p>In addition, once created, data types of properties cannot be changed + afterwards. Inventory numbers that are created as a numeric data type cannot + be converted into a textual data field afterwards. Also the search function + for both namespaces of the wiki has not yet been completely standardized and + only works in a case-sensitive manner.</p> + <p>It should also be emphasized that the software of the Wikimedia Foundation + is designed for Creative Commons-licensed content, that is for content that + can, in principle, also be shared. Data to which this does not apply, for + reasons of copyright or personal rights, can only be made accessible to a + limited extent as an article in a private area. However, this is only a + protection for article pages. With the sites of individual files such as the + images uploaded in the wiki, this function does not exist.</p> + </div> + </div> + <div type="chapter"> + <head>3. Synopsis</head> + + <p>With the De Jonge Wiki, for the first time a user-friendly frontend based on + MediaWiki was linked with a semantic database based on Wikibase with the help + of a simple template, as was previously only implemented for the exchange + between Wikipedia and Wikidata. When working with students, it became clear + that these structures could be understood quickly and that it was possible to + deal with them independently after a short introduction phase. The + infrastructure tested in this project therefore has the potential to be used by + organizations such as museums as an up-to-date tool for inventorying and + documenting measures following the FAIR/O principles. </p> + <p>Using MediaWiki and Wikibase as software results in two further advantages. On + the one hand, it is popular, long-lasting software that can be used free of + charge and does not require licensing. One has to be aware however that the + term ›long-lived‹ is very relative in the world of modern data sciences, since + this kind of wiki system itself has only been in existence for a little over 20 + years.<note type="footnote">Cf. <ref type="bibliography" target="#wikipedia_history_2023">History of Wikis 2023</ref>.</note> On the other hand, the data records created in + Wikibase can be read automatically and integrated into other databases. In this + context, it must be noted that the De Jonge Wiki will only be searchable + together with other Wikibase databases in common SPARQL queries after the + forthcoming move to a new hosting. However, this is due to the hosting in the + digital infrastructure of KU Leuven and can easily be avoided in the case of + any similar projects.</p> + <p>The De Jonge Wiki is already proving to be a welcome opportunity to convey + content. In the academic year 2021/2022, the data was used by the RLICC at KU + Leuven for the training of master’s students in the modules ›Analysis, + Registration and Documentation Techniques: ArchDOC‹ (H00W6A), ›Building + Archeology: Integrated Project Work‹ (H01X8A) and ›Integrated Project Work 3‹ + (H00X2A). In addition, as part of the Master of Digital Humanities training at + KU Leuven, a collaboration with Prof. Andrew Vande Moere from the research + group ›Research[x]Design‹ (RxD) took place in the study year 2021/2022, + which deals with digital designs to convey and develop the Arenberg Castle. + Within this project, the master students used the De Jonge Wiki for their + research.<note type="footnote">Cf. <ref type="bibliography" target="#vandemoere_rxd_2023">Prof. Andrew Vande Moere 2023</ref>.</note> At the LMU in Munich, the De Jonge Wiki served as + central example in the seminar ›Renaissance-Architektur digital. Aktuelle + Forschungen und ihre Unterstützung durch semantische Datenbanken‹ (09523) + during the winter semester 2021/2022 by Prof. Stephan Hoppe. There, students + edited their own content in the database.<note type="footnote">Cf. <ref type="bibliography" target="#lmu_renaissance_2023">Renaissance-Architektur digital 2023</ref>.</note> With Frieder Leipold and Max Kristen as members, + the De Jonge Wiki is meanwhile also represented at the international <ref + target="https://wbstakeholder.group/members#individual-members">Wikibase + Stakeholder Group</ref>.</p> + <p>With the De Jonge Wiki, a database was created that can be used intuitively to + move freely in a virtual castle and get detailed information on the building + history. Another requirement was the possibility to save data records in the + background in a semantic database that meets current international standards. + These tasks have been accomplished convincingly. </p> + <p>Organizations or projects that are interested in the De Jonge Wiki as a + prototype for scientific databases can find detailed information on the + extensions and skins used in the online reference list <ref + target="https://wikiapiary.com/wiki/DeJongeWiki">WikiApiary</ref>. More + information on the structure and logic of modeling the data can be found on the + <ref + target="https://set.kuleuven.be/rlicc/dejongewiki/w/index.php/DeJongeWiki:Help" + >De Jonge Wiki help page</ref>. Further collaborations will show whether the + prototype tested here could be used for similar databases as their digital + infrastructure.</p> + </div> + <div type="bibliography"> + <head>Reference List</head> + <listBibl> + <bibl xml:id="baru_knowledge_2021">Chaitanya Baru: What is a Knowledge Graph? Presentation as part of the + course CS 520, Knowledge Graphs Data Models, Knowledge Acquisition, Inference + and Applications, at the Department of Computer Science. Stanford University, + Spring 2021. HTML. [<ref target="https://web.archive.org/web/20230530164123/https://web.stanford.edu/~vinayc/kg/notes/What_is_a_Knowledge_Graph.html">Internet Archive</ref>] </bibl> + <bibl xml:id="bsv_raumbuch_2021">Bayerische Schlösserverwaltung (ed.): Raumbuch des Münchner Residenzmuseums. + 08.2021. PDF. [<ref + target="https://www.residenz-muenchen.de/deutsch/service/Raumbuch_Residenzmuseum.pdf" + >online</ref>]</bibl> + <bibl xml:id="bries_architectuur_1991">Ann Brìes: De neogotische architectuur van het Arenbergkasteel te Heverlee + (1872–1911). Unpublished Licentiaat thesis, KU Leuven, Faculteit van de + Letteren en de Wijsbegeerte, Departement Archeologie en Kunstwetenschap. + 1991.</bibl> + <bibl xml:id="carusi_research_2010">Annamaria Carusi / Torsten Reimer: Virtual Research Environment. + Collaborative Landscape Study. 2010. [<ref + target="https://www.researchgate.net/publication/242635295_Virtual_Research_Environment_Collaborative_Landscape_Study" + >online</ref>]</bibl> + <bibl xml:id="jonge_kasteel_2002">Krista De Jonge / Luc Verpoest / Pieter Vlaardingerbroek: Het kasteel van + Heverlee. In: Mark Derez / Marc Nelissen / Jean-Pierre Tytgat / Ann + Verbrugge / Jan Roeiers (eds.): Arenberg in de Lage Landen. Een hoogadellijk huis in Vlaanderen + & Nederland. Leuven 2002, pp. 239–251. <ptr type="gbv" + cRef="370835948"/> + </bibl> + <bibl xml:id="jonge_schloss_2004">Krista De Jonge: Schloss Heverlee bei Löwen (Leuven) und die Residenzbildung + in den südlichen Niederlanden um 1500. In: Wartburg-Gesellschaft (ed.): Burgen und Schlösser in den + Niederlanden und in Nordwestdeutschland (= Forschungen zu Burgen und + Schlössern, 8). München et al. 2004, pp. 69–80. + <ptr type="gbv" cRef="475316134"/> + </bibl> + <bibl xml:id="mediawiki_entity_2023">Extension: EntitySchema. In: MediaWiki. Last edited 06.02.2023. HTML. [<ref + target="https://www.mediawiki.org/wiki/Extension:EntitySchema" + >online</ref>]</bibl> + <bibl xml:id="mediawiki_wikibase_2023">Extension: WikibaseQualityConstraints. In: MediaWiki. Last edited 14.07.2023. + HTML. [<ref + target="https://www.mediawiki.org/wiki/Extension:WikibaseQualityConstraints" + >online</ref>]</bibl> + <bibl xml:id="wikipedia_history_2023">History of Wikis. In: Wikipedia. Last edited 15.07.2023. HTML. [<ref + target="https://en.wikipedia.org/wiki/History_of_wikis">online</ref>]</bibl> + <bibl xml:id="koufopoulos_castle_2021">Ioannis Makarios Koufopoulos / Ragini Karmarkar / Aljosa Aaron Spalte / + Wietse Vervenne: Arenberg Castle, Leuven (Heverlee). Integrated Project Work, + KU Leuven, Master in Conservation of Monuments and Sites, Raymond Lemaire + International Centre for Conservation. 13.03.2021. [<ref target="https://issuu.com/raginikarmarkar/docs/arenberg_report_v2_compressed">online</ref>]</bibl> + <bibl xml:id="kuroczynski_museum_2015">Piotr KuroczyÅ„ski / Oliver Hauck / Daniel Dworak / Lan Lutteroth: Virtual + Museum of Destroyed Cultural Heritage. 3D Documentation, Reconstruction and + Visualization in the Semantic Web. In: Virtual Archaeology. Methods and + Benefits. Proceedings of the Second International Conference held at the State + Hermitage Museum, 01.–03.06.2015, Saint Petersburg 2015, pp. 54–61. PDF. [<ref + target="http://www.virtualarchaeology.ru/pdf/281_va_book2015.pdf" + >online</ref>] <ptr type="gbv" cRef="1028860536"/> + </bibl> + <bibl xml:id="lutteroth_schloss_2018">Jan Lutteroth / Stephan Hoppe: Schloss Friedrichstein 2.0 â€“ Von digitalen + 3D-Modellen und dem Spinnen eines semantischen Graphen. In: Piotr KuroczyÅ„ski / Peter Bell / Lisa Dieckmann (eds.): Computing Art + Reader: Einführung in die digitale Kunstgeschichte (= Computing in Art and + Architecture, 1). Heidelberg 2018, pp. 184–198. PDF. DOI: <ref + target="https://doi.org/10.11588/arthistoricum.413.c5822" + >10.11588/arthistoricum.413.c5822</ref> + <ptr type="gbv" cRef="1041880960"/> + </bibl> + <bibl xml:id="vandemoere_rxd_2023">Prof. Andrew Vande Moere. In: KU Leuven, Research[x]Design. Last accessed + 06.06.2023. HTML. [<ref + target="https://rxd.architectuur.kuleuven.be/andrew-vande-moere/" + >online</ref>]</bibl> + <bibl xml:id="lmu_renaissance_2023">Renaissance-Architektur digital. Aktuelle Forschungen und ihre Unterstützung + durch semantische Datenbanken. In: LMU München, Lehre Studium Forschung. Last + accessed 06.06.2023. HTML. [<ref target="https://lsf.verwaltung.uni-muenchen.de/qisserver/rds?state=verpublish&status=init&vmfile=no&moduleCall=webInfo&publishConfFile=webInfo&publishSubDir=veranstaltung&veranstaltung.veranstid=905695">online</ref>]</bibl> + <bibl xml:id="nfdi_semantic_2023">Semantic Kompakkt. In: NFDI4Culture. Last accessed 06.06.2023. HTML. [<ref + target="https://nfdi4culture.de/de/dienste/details/semantic-kompakkt.html" + >online</ref>]</bibl> + <bibl xml:id="smitz_studenten_2023">Hannelore Smitz: Archäologie-Studenten legen Teile eines Bollwerks unter dem + Schloss Arenberg in Heverlee frei. In: VRT News. Article of 11.05.2023. HTML. + [<ref + target="https://www.vrt.be/vrtnws/de/2023/05/11/archaeologie-studenten-legen-teile-eines-bollwerks-unter-dem-sch/" + >online</ref>]</bibl> + <bibl xml:id="kulturliegenschaften_rekonstruktion_2023">Virtuelle Rekonstruktion: Kulturliegenschaften gestern und heute, main page. + Last accessed 06.06.2023. HTML. [<ref target="https://www.vr-ssg.hs-mainz.de/">online</ref>]</bibl> + <bibl xml:id="vlaardingerbroek_arenberger_2004">Pieter Vlaardingerbroek: Die Arenberger, ihre Architekten und das Arenberger + Schloss zu Heverlee (1612-1792). In: Wartburg-Gesellschaft (ed.): Burgen und Schlösser in den Niederlanden + und in Nordwestdeutschland (= Forschungen zu Burgen und Schlössern, 8). München et al. 2004, pp. 209–218. <ptr type="gbv" + cRef="475316134"/> + </bibl> + </listBibl> + </div> + <div type="abbildungsnachweis"> + <head>List of Figures</head> + <desc type="graphic" xml:id="abb1"><ref type="graphic" target="#abb01">Fig. 1</ref>: Stater of Croesus, around 550 BC (16 mm, 10.76 g), minted in + Sardis. [Photograph: <ref + target="https://commons.wikimedia.org/wiki/File:Kroisos._Circa_564-53-550-39_BC._AV_Stater_(16mm,_10.76_g)._Heavy_series._Sardes_mint.jpg" + >Classical Numismatic Group, Inc. http://www.cngcoins.com. CC BY-SA + 3.0</ref>]</desc> + <desc type="graphic" xml:id="abb2"><ref type="graphic" target="#abb02">Fig. 2</ref>: Rome and the ›dark centuries‹, the history of libraries in the + period of 300 BC until 2000 AD. [Chart: <ref target="https://commons.wikimedia.org/wiki/file:bibsta4.jpg">Bibhistor, CC BY-SA 3.0</ref>]</desc> + <desc type="graphic" xml:id="abb3"><ref type="graphic" target="#abb03">Fig. 3</ref>: South facade of Arenberg Castle, above [image: KU Leuven / + Koufopoulos et al. 2021]; aerial view of the main building, left [image: KU + Leuven / Koufopoulos et al. 2021]; floor plan of the ground floor with color + labeling of different structural units, right. [Image: atlas plan, KU + Leuven, <ref target="https://admin.kuleuven.be/td/en/index">Technical + Services</ref>]</desc> + <desc type="graphic" xml:id="abb4"><ref type="graphic" target="#abb04">Fig. 4</ref>: Structure of the room designations in the De Jonge Wiki. + [Chart: Frieder Leipold 2021]</desc> + <desc type="graphic" xml:id="abb5"><ref type="graphic" target="#abb05">Fig. 5</ref>: Structural logic of the page categories. [Chart: Frieder + Leipold 2021]</desc> + <desc type="graphic" xml:id="abb6"><ref type="graphic" target="#abb06">Fig. 6</ref>: Example of a data sheet in the Wikibase database. [Screenshot + De Jonge Wiki]</desc> + <desc type="graphic" xml:id="abb7"><ref type="graphic" target="#abb07">Fig. 7</ref>: Example of a front-end article for a room. [Screenshot De Jonge + Wiki]</desc> + <desc type="graphic" xml:id="abb8"><ref type="graphic" target="#abb08">Fig. 8</ref>: Example of a front-end article on a historical source. + [Screenshot De Jonge Wiki]</desc> + <desc type="graphic" xml:id="abb9"><ref type="graphic" target="#abb09">Fig. 9</ref>: Example of a front-end article on a scientific source. + [Screenshot De Jonge Wiki]</desc> + </div> + </div> + + </body> + </text> +</TEI>