NFDI4Culture Ontologies and Use Cases

These are slides presented at NFDI4Culture meetings with domain experts of the consortium on the BFO-compliant NFDIcore ontology, the NFDI4Culture ontology (CTO) and current example use cases. The goal addressed in the presentation are: Enable finding and exploring the data of the culture community. Using the research data of the community directly, intuitively and without barriers (as much as possible). Decrease the distance between data providers and data users. Do this across the culture disciplines AND cross domains. The NFDIcore ontology (https://nfdi.fiz-karlsruhe.de/ontology): represents community structure, e.g. people, projects, organisations, and NFDI infrastructure, e.g. services, software, APIs, guidelines, educational resources, etc. is compliant with the Basic Formal Ontology 2020 to improve the interoperability with other NFDI consortia contains mappings to further ontologies, e.g. schema.org The NFDI4Culture Ontology (https://nfdi4culture.de/ontology/): represents resources of NFDI4Culture, e.g. content, creative works, culture objects, historical persons, locations, events, etc. is light-weight, and represents only crucial information from source data to enable interconnection and querying. links elements to related concepts in external vocabularies What do we need to make research data findable and interconnect them via the Culture Knowledge Graph? We need a label of the resource We need to know the license of the resource due to reusability We need a resolvable IRI of the resource to link back to the data on the providers side We need to make content wise and structural interconnections of the data visible How is data integrated? Integration workflows already exist for community standards (e.g. LIDO) and the Culture Graph Interchange Format (CGIF) Interested in currently supported workflows for data integration into the Culture Knowledge Graph? Join the Linked Open Data Working Group next tuesday, 04 March 2025