changes in presentation

docs/presentation/dist/font/OFL.txt

@@ -0,0 +1,93 @@
+Copyright 2020 The Archivo Project Authors (https://github.com/Omnibus-Type/Archivo)
+
+This Font Software is licensed under the SIL Open Font License, Version 1.1.
+This license is copied below, and is also available with a FAQ at:
+https://openfontlicense.org
+
+
+-----------------------------------------------------------
+SIL OPEN FONT LICENSE Version 1.1 - 26 February 2007
+-----------------------------------------------------------
+
+PREAMBLE
+The goals of the Open Font License (OFL) are to stimulate worldwide
+development of collaborative font projects, to support the font creation
+efforts of academic and linguistic communities, and to provide a free and
+open framework in which fonts may be shared and improved in partnership
+with others.
+
+The OFL allows the licensed fonts to be used, studied, modified and
+redistributed freely as long as they are not sold by themselves. The
+fonts, including any derivative works, can be bundled, embedded, 
+redistributed and/or sold with any software provided that any reserved
+names are not used by derivative works. The fonts and derivatives,
+however, cannot be released under any other type of license. The
+requirement for fonts to remain under this license does not apply
+to any document created using the fonts or their derivatives.
+
+DEFINITIONS
+"Font Software" refers to the set of files released by the Copyright
+Holder(s) under this license and clearly marked as such. This may
+include source files, build scripts and documentation.
+
+"Reserved Font Name" refers to any names specified as such after the
+copyright statement(s).
+
+"Original Version" refers to the collection of Font Software components as
+distributed by the Copyright Holder(s).
+
+"Modified Version" refers to any derivative made by adding to, deleting,
+or substituting -- in part or in whole -- any of the components of the
+Original Version, by changing formats or by porting the Font Software to a
+new environment.
+
+"Author" refers to any designer, engineer, programmer, technical
+writer or other person who contributed to the Font Software.
+
+PERMISSION & CONDITIONS
+Permission is hereby granted, free of charge, to any person obtaining
+a copy of the Font Software, to use, study, copy, merge, embed, modify,
+redistribute, and sell modified and unmodified copies of the Font
+Software, subject to the following conditions:
+
+1) Neither the Font Software nor any of its individual components,
+in Original or Modified Versions, may be sold by itself.
+
+2) Original or Modified Versions of the Font Software may be bundled,
+redistributed and/or sold with any software, provided that each copy
+contains the above copyright notice and this license. These can be
+included either as stand-alone text files, human-readable headers or
+in the appropriate machine-readable metadata fields within text or
+binary files as long as those fields can be easily viewed by the user.
+
+3) No Modified Version of the Font Software may use the Reserved Font
+Name(s) unless explicit written permission is granted by the corresponding
+Copyright Holder. This restriction only applies to the primary font name as
+presented to the users.
+
+4) The name(s) of the Copyright Holder(s) or the Author(s) of the Font
+Software shall not be used to promote, endorse or advertise any
+Modified Version, except to acknowledge the contribution(s) of the
+Copyright Holder(s) and the Author(s) or with their explicit written
+permission.
+
+5) The Font Software, modified or unmodified, in part or in whole,
+must be distributed entirely under this license, and must not be
+distributed under any other license. The requirement for fonts to
+remain under this license does not apply to any document created
+using the Font Software.
+
+TERMINATION
+This license becomes null and void if any of the above conditions are
+not met.
+
+DISCLAIMER
+THE FONT SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND,
+EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO ANY WARRANTIES OF
+MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT
+OF COPYRIGHT, PATENT, TRADEMARK, OR OTHER RIGHT. IN NO EVENT SHALL THE
+COPYRIGHT HOLDER BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY,
+INCLUDING ANY GENERAL, SPECIAL, INDIRECT, INCIDENTAL, OR CONSEQUENTIAL
+DAMAGES, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING
+FROM, OUT OF THE USE OR INABILITY TO USE THE FONT SOFTWARE OR FROM
+OTHER DEALINGS IN THE FONT SOFTWARE.

docs/presentation/dist/theme/dracula.css

@@ -19,14 +19,14 @@ section.has-light-background, section.has-light-background h1, section.has-light
  * GLOBAL STYLES
  *********************************************/
 :root {
-  --r-background-color: #282A36;
+  --r-background-color: #13171f;
   --r-main-font: -apple-system, BlinkMacSystemFont, avenir next, avenir, segoe ui, helvetica neue, helvetica, Cantarell, Ubuntu, roboto, noto, arial, sans-serif;
   --r-main-font-size: 40px;
-  --r-main-color: #F8F8F2;
+  --r-main-color: #f0f1f3;
   --r-block-margin: 20px;
   --r-heading-margin: 0 0 20px 0;
   --r-heading-font: League Gothic, Impact, sans-serif;
-  --r-heading-color: #BD93F9;
+  --r-heading-color: #f0f1f3;
   --r-heading-line-height: 1.2;
   --r-heading-letter-spacing: normal;
   --r-heading-text-transform: none;
@@ -38,8 +38,8 @@ section.has-light-background, section.has-light-background h1, section.has-light
   --r-heading3-size: 1.55em;
   --r-heading4-size: 1em;
   --r-code-font: Fira Code, Menlo, Consolas, Monaco, Liberation Mono, Lucida Console, monospace;
-  --r-link-color: #FF79C6;
-  --r-link-color-dark: rgb(255, 64.6, 174.0089552239);
+  --r-link-color: #00a9fe;
+  --r-link-color-dark: #00a9fe;
   --r-link-color-hover: #8BE9FD;
   --r-selection-background-color: #44475A;
   --r-selection-color: #fff;

docs/presentation/index.html

@@ -9,6 +9,22 @@
 	<link rel="stylesheet" href="dist/reveal.css">
 	<link rel="stylesheet" href="dist/theme/dracula.css">
 	<style>
+		@font-face {
+			font-family: "Archivo";
+			font-style: normal;
+			font-display: swap;
+			src: local("Archivo"), url("dist/font/Archivo-VariableFont_wdth,wght.ttf") format("truetype");
+			font-weight: 400 700;
+			font-stretch: 62% 125%;
+		}
+
+		:root{
+			--r-main-font: 'Archivo', -apple-system, BlinkMacSystemFont, avenir next, avenir, segoe ui, helvetica neue, helvetica, Cantarell, Ubuntu, roboto, noto, verdana, arial, sans-serif;
+			--r-heading-font: 'Archivo', -apple-system, BlinkMacSystemFont, avenir next, avenir, segoe ui, helvetica neue, helvetica, Cantarell, Ubuntu, roboto, noto, verdana, arial, sans-serif;
+			--r-heading-font-weight: 700;
+			--r-list-bullet-color: #fff;
+		}
+
 		.reveal h2 {
 			font-size: 1.3em
 		}
@@ -70,7 +86,7 @@ <h2>Ausgangslage & Ziel</h2>
 				<div class="flex">
 				<ul style="font-size: .75em; max-width: 40%;">
 					<li>Die Burgerbibliothek Bern verwendet zur Verzeichnung ihrer Archivalien Deskriptoren.</li>
-					<li>Die Deskriptoren sollen in einen RDF-Datensatz unter Verwendung der Records in Contexts Ontology
+					<li>Die Deskriptoren sollen in einen RDF-Datensatz unter Verwendung der Records in Contexts Ontology (RiC-O)
 						gewandelt werden.</li>
 				</ul>
 				<div style="max-width: 55%;">
@@ -83,30 +99,27 @@ <h2>Ausgangslage & Ziel</h2>
 			<section>
 				<h2>Records in Contexts (RiC)</h2>
 				<ul>
-					<li>RiC ist ein vom International Council of Archives (ICA) verabschiedeter Standard, welcher der
-						Beschreibung von Archivalien dient. <a class="cite" href="#/literaturverzeichnis">(EGAD, 2024)</a></li>
-					<li>Die Records in Contexts Ontology (RiC-O) ist als generische Blaupause zur Erstellung von<br>
-						RDF-Datensätzen für den Gebrauch im archivalischen Kontext entworfen. <a class="cite" href="#/literaturverzeichnis">(ICA EGAD,
+					<li>RiC ist ein archivischer Verzeichnungsstandard welcher die amtierenden Standards ISAD(G), ISAAR(CPF), ISDF und ISDIAH ablöst. <a class="cite" href="#/literaturverzeichnis">(EGAD, 2024)</a></li>
+					<li>Bestandteil des Standards ist die Records in Contexts Ontology (RiC-O), welche als Blaupause zur Erstellung von RDF-Datensätzen im archivischen Kontext zu verstehen ist.<a class="cite" href="#/literaturverzeichnis">(ICA EGAD,
 							2024, Abs. «RiC-O design principles»)</a></li>
 				</ul>
 			</section>
 			<section>
-				<h2>Datenaggregation (1/2)</h2>
+				<h2>Datenaggregation und -modellierung (1/3)</h2>
 				<ul>
-					<li>CSV-Export via AIS (49&nbsp;242 Einträge)</li>
-					<li>Relationen zwischen Deskriptoren via Web Scraping (82&nbsp;027 Einträge)</li>
-					<li>Serialisierung in Turtle mit RDFLib (xx Tripel) <a class="cite" href="#/literaturverzeichnis">(RDFLib Team, 2024)</a>
-					</li>
+					<li>CSV-Export via Archivinformationssystem (AIS) (49&nbsp;242&nbsp;Einträge)</li>
+					<li>Relationen zwischen Deskriptoren via Web Scraping (82&nbsp;027&nbsp;Einträge)</li>
+					<li>Serialisierung in Turtle mit RDFLib (390&nbsp;000 Tripel) <a class="cite" href="#/literaturverzeichnis">(RDFLib Team, 2024)</a></li>
 					<li>Inferenzbildung mit OWL-RL (5&nbsp;338&nbsp;997 Tripel) <a class="cite" href="#/literaturverzeichnis">(Herman, 2014)</a></li>
 					<li>RDF-Triple-Store / SPARQL-Engine Qlever <a class="cite" href="#/literaturverzeichnis">(Bast et al., 2022)</a></li>
 				</ul>
 			</section>
 			<section>
-				<h2>Datenaggregation (2/2)</h2>
+				<h2>Datenaggregation und -modellierung (2/3)</h2>
 				<img src="media/c4-data.svg" alt="C4 Diagramm des Systemkontexts für die Datenaggregation">
 			</section>
 			<section>
-				<h2>Datenmodell</h2>
+				<h2>Datenaggregation und -modellierung (3/3)</h2>
 				<img src="media/data-model.svg" alt="Diagramm des RDF-Datenmodells">
 			</section>
 			<section>
@@ -128,7 +141,7 @@ <h2>Deskriptorendetailansicht</h2>
 			<section>
 				<h2>Diskussion</h2>
 				<ul>
-					<li>Datenmodellierung: Konsistenz der Lebensdaten; Geburts- und Todesdatum ebenfalls als Eventtypse
+					<li>Konsistenz in der Datenmodellierung: Geburts- und Todesdatum ebenfalls als «rico:EventType»
 						modellieren? Oder z. B. BIO Vocabulary verwenden?<a class="cite" href="#/literaturverzeichnis">(Davis et al., 2011)</a></li>
 					<li>OWL-RL: Infernzbildung führt zu Tripel mit Literalen in der Subjektposition. Patch ist eine
 						Kombination der Lösungsvorschläge von <a href="#/literaturverzeichnis">al-Dosari (2023)</a> und <a href="#/literaturverzeichnis">Car (2023)</a></li>