scieee AI-readable full text Open interactive document viewer

Transforming a Data Monolith into a Network of FAIR Digital Objects

Backe, Christian

Abstract

This talk, held at FAIR in Action 2025, presents the transformation of a monolithic data corpus into a network of FAIR Digital Objects (FDOs). The transformation addresses two main objectives. First, the corpus is divided into data elements that are addressable at a granular scale. This allows, e.g., precise linking of propositions to specific observations, accurate error reporting and versioning, and flexible recombination of dataset components. Second, controlled semantics are established across all levels of the data model. The goal is to eliminate any ambiguity for data consumers in order to increase reuse efficiency and minize the risk of misinterpretation. The data was originally acquired within the RoBivaL project which investigated different mobile robot designs in an agricultural setting. Data collection included high-resolution sensor measurements from several modalities, field logbooks containing structured experiment documentation, and specifications providing metadata and context about research methodology, data structures, and used equipment. The corpus was first made available on Zenodo in an effort to comply with the FAIR principles. While this initial version featured a clear layout and open formats in order to facilitate reuse, it was provided as a monolith which limited its interoperability. Further, though rich semantics were explicitly documented in the initial version, they were not codified in a standardized fashion. The transformed version implements the corpus as a network of FDOs, using semantic web technologies for data modeling, and Nanopublications for distribution. The data model has three layers: The Experimental Research Ontology (ERO) forms the foundational layer. It models fundamental aspects of experimental data creation in general and is aligned with several upper ontologies. The RoBivaL Specification layer uses ERO to specify RoBivaL's project methodology, define the structure and semantics of the payload data, and provide information about the used equipment. The RoBivaL Payload Data layer uses the Specification layer to capture the values of experiment parameters and sensor measurements. The transformation was conducted as a use case of the project FDO Connect which develops tools and methodologies to bridge traditional data management practices with emerging FDO ecosystem requirements in order to facilitate the broader adoption of FAIR principles in research communities. The dataset transformation showcases modular multi-layered data modeling, a practical implementation of the FDO specifications, and a best practice for FAIR-compliant usage of semantic web technologies for distributed scientific data networks.

Full text

Transforming a Data Monolith into a Network of FAIR Digital Objects Christian Backe, DFKI Robotics Innovation Center FAIR in Action, Göttingen, 2025-10-01 Overview 1. FAIR Digital Objects 2. RoBivaL Monolith 3. Ad-Hoc Semantics 4. Transformation Demo 5. Takeaways References Omissions Issues and Pitfalls FAIR Digital Objects (Subject, Predicate, Object) RoBivaL Monolith 250 million datapoints, 1.4 GB memory, 3 Zip archives  Access “I only need 500 samples.” Mutation “Does your update affect my analysis?” Provenance “My discovery is based on these 200 observations.” Ad-Hoc Semantics README, Spec files  “What is the meaning of column name robot_key?” “Which measuring unit has value 38.0?” “How was parameter travel_time measured?” Transformation Demo Experiment Run into Linked Data Original Data and Metadata run__obstacle_avoidance.csv run_id experiment_key robot_key travel_time … 42 obstacle_avoidance artemis 38.0 … … … … … … // Run42.ttl Run42 type ExperimentRun ; hasExperimentType ObstacleAvoidance ; observedRobot Artemis ; travelTime 38.0 ; . http://w3id.org/ RoBivaL/FDORecord/Payload/ ExperimentRun/ Run42 http://www.w3.org/ 1999/02/22-rdf-syntax-ns# type 38.0 Run42 ExperimentRun Artemis type observedRobot 38.0 travelTime ObstacleAvoidance hasExperimentType  travelTime travelTime type ExperimentParameter DatatypeProperty Datatype float 0.0 SEC type range unit type onDatatype withRestrictions minInclusive  observedRobot observedRobot ExperimentParameter ObjectProperty AvailableRobot Artemis Bonirob NaioOz Sherpatt FeatureOfInterest Platform System NamedIndividual "ARTEMIS" MobileRobot type type range equivalentClass subClassOf subClassOf subClassOf type label type  ObstacleAvoidance ObstacleAvoidance ExperimentType type observedRobot IndependentVariable true hasParameterUsage usesParameter hasVariableRole isRequired travelTime DependentVariable true hasParameterUsage usesParameter hasVariableRole isRequired ResearchObjectiveSpec "The objective is ..." ExperimentSetupSpec "The setup is ..." ProcedureSpec "The procedure is ..." SuccessCriteriaSpec "Success is ..." hasPart hasPart hasPart hasPart type description type description type description type description hasMethodologySpec Simplicity Flexible modeling + Easy onboarding (but: Pitfalls) Uniformity Interoperability across domains & abstraction levels  Thank you! References • This ◦ Publication: https://doi.org/10.5281/zenodo.17630784 ◦ Abstract: https://events.gwdg.de/event/1175/contributions/4203/ • Data ◦ RoBivaL Monolith: https://doi.org/10.5281/zenodo.8424932 ◦ RoBivaL FDO Data Model (IRI) http://w3id.org/RoBivaL ◦ RoBivaL FDO Data Model (Source) https://github.com/cbacke/RoBivaL ◦ Experimental Research Ontology (IRI) http://w3id.org/ExperimentalResearchOntology/ ◦ Experimental Research Ontology (Source) https://github.com/cbacke/ExperimentalResearchOntology • Projects ◦ FDO Connect: https://robotik.dfki-bremen.de/en/research/projects/fdo-connect ◦ RoBivaL: https://robotik.dfki-bremen.de/en/research/projects/robival • FAIR Digital Objects ◦ FAIR Principles: https://www.go-fair.org/fair-principles/ ◦ FDO Specifications: https://fairdo.org/specifications/ ◦ 3rd FDO Conference 2026: https://fairdo.org/fdo-conference-2026-call-for-papers/ • Tools ◦ Apache Jena: https://jena.apache.org/ ◦ ChatGPT: https://chatgpt.com/ ◦ Claude: https://claude.ai/ ◦ Nanodash: https://nanodash.knowledgepixels.com/ ◦ nanopub Python Library: https://pypi.org/project/nanopub/ ◦ Protégé: https://protege.stanford.edu/ ◦ pyshacl Python Library: https://pypi.org/project/pyshacl/ ◦ rdflib Python Library: https://pypi.org/project/rdflib/ ◦ w3id.org Home: https://w3id.org/ ◦ w3id.org Source: https://github.com/perma-id/w3id.org • Semantic Web Specifications ◦ IRI: https://www.rfc-editor.org/rfc/rfc3987.html ◦ OWL: https://www.w3.org/OWL/ ◦ RDF: https://www.w3.org/RDF/ ◦ SHACL: https://www.w3.org/TR/shacl/ • Ontologies and Terminologies ◦ BIBO: http://purl.org/ontology/bibo/ ◦ BFO: https://basic-formal-ontology.org/ ◦ CORA (IEEE 1872-2015): https://ieeexplore.ieee.org/document/7084073 ◦ DCTERMS: http://purl.org/dc/terms/ ◦ FDOF: https://w3id.org/fdof/ontology# ◦ FOAF: http://xmlns.com/foaf/0.1/ ◦ IAO: https://github.com/information-artifact-ontology/IAO/ ◦ ISO 8373-2021: https://www.iso.org/standard/75539.html ◦ OBI: https://obi-ontology.org/ ◦ ORG: http://www.w3.org/ns/org# ◦ OWL: http://www.w3.org/2002/07/owl# ◦ QUDT: http://qudt.org/schema/qudt/ ◦ RDF: http://www.w3.org/1999/02/22-rdf-syntax-ns# ◦ RDFS: http://www.w3.org/2000/01/rdf-schema# ◦ SH: http://www.w3.org/ns/shacl# ◦ SOSA / SSN: https://www.w3.org/TR/vocab-ssn/ ◦ UNIT: http://qudt.org/vocab/unit/ ◦ VANN: http://purl.org/vocab/vann/ ◦ XSD: http://www.w3.org/2001/XMLSchema# Omissions • FDO-specific properties ◦ fdof:FAIRDigitalObject ◦ fdof:isMaterializedBy ◦ dcterms:conformsTo • Established ontologies and terminologies ◦ Upper ontologies ◦ Domain-specific ontologies ◦ Basic ontologies and terminologies • Namespace registration and redirection ◦ w3id.org • “Nice-to-have” properties for humans ◦ rdfs:label ◦ rdfs:comment ◦ dcterms:title ◦ dcterms:description • FDO Profiles and SHACL Issues and Pitfalls • Open World Assumption • sh.targetNode • Resources and Tools