Wie mache ich aus Daten Wissen? Wissenschaftsinstitionen wie Hochschulen, außeruniversitäre Einrichtungen, Behörden und privatwirtschaftliche Unternehmen (z.B. Grabungsfirmen) erheben eine Vielzahl heterogener Datensätze in den unterschiedlichsten Formaten, Detailgraden und Qualitäten im Bereich de objektbezogenen materiellen Erbes der Menschheitsgeschichte. Um diese Daten gemeinsam wissenschaftlich auswerten zu können, ist die Anwendung der FAIR-Prinzipien (unter Berücksichtigung von CARE und TRUST) mit dem Gedanken von Open Science, sowie gemeinsamer Community-Standards zum Austausch von Daten unerlässlich. Zur Verknüpfung der Daten ist das Mittel der Wahl die Technologie der semantischen Modellierung und die konsequente Anwendung der Linked Open (Usable) Data Prinziples (LOD) nach Sir Tim Berners-Lee und Rob Sanderson unter Einbeziehung des W3C Standards Resource Description Framework (RDF), sowie Community-Hubs wie dem Wikiversum (z.B. Wikidata, Wikimedia Commons) oder OpenStreetMap. In NFDI4Objects, insbesondere im Bereich der Digitalen Archäologie und Digital Cultural Heritage, stehen mit CIDOC CRM, PROV-O, SKOS, GeoSPARQL, schema.org und der davon abgeleiteten Linked Archealogical Data Anwendungsontologie (LADO) Referenzmodelle und Ontologien zur Verfügung, die ein gemeinsames semantisch-vernetztes Datenmodell ermöglichen, welche in einem Knowledgegraph münden können, der FAIR durchsuchbar sein kann. Dieser Kurzvortrag zeigt beispielhaft Herausforderungen und Lösungsansätze zur semantischen Modellierung mit LOD aus dem NFDI4Objects Konsortium (u.A. Terra Sigillata, Schiffsdarstellungen auf Objekten, Ogham Steine), Fuzzyness und Wobbliness sowie die Einbindung von Citizen Science Community Hubs und wie diese Daten (inkl. Medien wie Bilder) in einem Knowledgegraph zur (semi-automatischen) Wissensgenerierung mit Hilfe von Reasoning genutzt werden können.

ongoing projects Samian Research (hosted by LEIZA) GitHub: https://github.com/RGZM/samian-lod Doku: https://rgzm.github.io/samian-lod/doc/ Daten: (Folder "data") https://zenodo.org/records/4314355 Datenmodell: https://rgzm.github.io/samian-lod/assets/images/SamianLod_map.png Linked Open Ogham (created within the Wikimedia Deutschland Fellow-Programm Freies Wissen) Data + Ontology: https://github.com/ogi-ogham/ogham-datav1/tree/main/rdf

Open Document Bedürfnisse GNM/WissKI Richtlinien zur Erstellung von Linked Open Data nach Problemen Übersicht über Schnittstellen und Endpunkte "REST/SPARQL" (von Projekten) mit Beschreibung der Daten zur Nachnutzung Technische Bedürfnisse für Modellierungen in RDF (z. B. SPARQL-star, Harvesting, Federation, Top-Level-Semantics...)

Session 514: Applying Archaeological Research Software Engineering as Little Minions: Statistical & Computational Approaches to Daily Archaeological Tasks min. 150 words and max. 300 words https://docs.google.com/document/d/1SH0OChTj2YPgeVPzIudWCu4oU0VuqLSeZQIwaG7peog/edit “Dated sites” in archaeology are usually not “dated sites”. Only parts of the “dated sites” can be set in relative relation to each other, e.g. if they belong to a group of sites within a newly occupied area or if they are part of a string of military sites related to a military campaign etc. For this purpose, we can use e.g. Allen's interval algebra. However, most of the temporality of “dated sites” is usually derived from a series of historical assumptions and interpolations. Yet, the chronology of these materials is often based on material coming from the manifold of other assumed “dated sites”, thus potentially resulting in a circulus vitiosus. A methodological way out of this dilemma is possible when we enhance the assumed external dating evidence and go back to the factual occurrences and overlaps in the data from the suspected “dated sites”, since only these data are free of any temporal interpretations. As a method, the chronological assumptions used in defining “dated sites” based on archaeological find materials in the 1st century AD must be deconstructed and restricted to the occurrences and overlaps within and between “find materials” from suspected “dated sites” only, to arrive at a relative chronology. This can be achieved by using correspondence analysis and visualising the resulting dimension values on maps recalculated in Hue values. By applying the “Alligator Method”, including the Alligator and AMT tools, we can fix missing or enhance existing start- or endpoints by adding information about the vagueness/uncertainties of the hitherto “from-to” information. The resulting relative chronology can be transferred and refined by Allen's interval algebra and visualised in graph structures such as the Resource Description Framework (RDF).

Title Applying archaeological Research Software Engineering as Little Minions: Statistical & computational approaches to daily archaeological tasks Abstract Nowadays computer applications as well as statistical and computational approaches constitute a big part of the toolbox of every archaeologist, as they open tremendous possibilities for all research. These can be ready-to-use (proprietary) software applications but also "Little Minions" (self-scripted tools) or research software (e.g. implementation of statistic algorithms in R, Python), which are written by researchers. Both, research software and research data are part of Computational Archaeology and play an important role in up-to-date archaeological research. Optimally research data (and software) is FAIR(4RS) – Findable, Accessible, Interoperable, Re-usable (for Research Software) – and reproducible of which other users can benefit from or even develop further. The increasing number of topics and papers at the international and national chapters of the CAA show manifold applications but also implications. Working Groups like the SIG SSLA (https://sslarch.github.io) or the "Little Minions" (https://littleminions.link) also deal with Computational Archaeology and are building a community. Several initiatives, such as the German National Research Data Infrastructure (NFDI) – especially NFDI4Objects – or the European Open Science Cloud (EOSC), engage with this topic to strengthen the position of Computational Archaeologists and Research Software Engineers, highlight the scientific merit of their work, and ensure researchers receive credit for computational approaches, software development, as well as for writing papers. To support this, this session invites contributions dealing with various aspects of Computational Archaeology, but not limited to:

Based on thorough evaluation of your proposal by the Scientific Committee (ScC), we are delighted to inform you that your session "514. Archaeological Research Software Engineering: Little Minions, Scripting in Digital Archaeology and Software as Research Data Using FAIR4RS" has been provisionally accepted subject to changes recommended by the Scientific Committee as per below: The discussed topic is highly intriguing, and the involvement of scholars less familiar with computational archaeology and engaging scholars less acquainted with computational archaeology is pivotal in elevating the status of software creation within theacademic sphere, as highlighted in the abstract. To accomplish this, refining the abstract for broader comprehension among diverse audiences would be advantageous. Moreover, we strongly advocate for emphasizing statistical and computational approaches throughout. Title new_v2 (max. 20 words) Applying archaeological Research Software Engineering as Little Minions: Statistical & computational approaches to daily archaeological tasks

Wie machen es Andere? NFDI4Culture: https://nfdi4culture.de/about-us/offices.html Dort gibt es "Offices", darunter ein "CO" und ein "TO" aus dem N4C Antrag: https://riojournal.com/article/57036/ Administrative and Technical Coordination Offices (ACO / TCO): To ensure the smooth operation of the consortium with regard to all administrative issues (reporting, contract management, financial management, documentation, etc.) and to provide an overarching and long-term technical perspective that reaches beyond single measures in the work program the consortium will set up two offices: the administrative and the technical coordination office. The staff of the two offices closely works together with the task area co spokespersons and the Spokesperson Committee. Both offices operate as distributed coordination structures and each of the co-applicant institutions has dedicated staff in both offices. The ACO lead rests with AWLM and the TCO lead rests with FIZ. ACO and TCO set up a tight coordination network for the consortium using weekly stand-ups moderated by the ACO and the TCO leads and report progress to the Spokesperson Committee at least once a month. This has proven to be very successful during the application phase with the NFDI4Culture coordination office (NCCO) being a prototype of this structure. Namen Technical Office (TO) Technical Infrastructure Group (TIG)

CfC: https://eaa.klinkhamergroup.com/eaa2024/ Title (max. 20 words) Archaeological Research Software Engineering: Little Minions, Scripting in Digital Archaeology and Software as Research Data using FAIR4RS Type Regular Session Theme Archaeological Sciences, Humanities and the Digital era: Bridging the Gaps

CfC: https://events.hifis.net/event/994/abstracts/ Title Research Software Engineering in NFDI4Objects: Community building, implementation of FAIRification Tools and scripting in Digital Archaeology Type Talk (30min) Author(s) Florian Thiery (LEIZA, N4O)

Prefix n4o.cloud ? (würde ich nehmen) n4o.io ? http://nfdi4objects.net ? Zweck gemeinsame Diskussion mit den TA, TWG und der Community (CC), welche Anforderungen an die CoreOntology gestellt werden welche Mindestanforderungen bestehen seitens der Fachwissenschaften und seitens der Community (das muss mit unseren nicht zusammenpassen) Wie kann unsere CoreOntology mit der der NFDI und der NFDI4Culture (und anderen NFDI) zusammengeführt werden

CfC: https://events.hifis.net/event/994/abstracts/ Title Using RSE skills and Open Source Software to propose a heterogenious Management Hub in NFDI4Objects Type Talk (15min) Author(s) Fabian Fricke (DAI)