Skip to content

Commit 467610c

Browse files
Update Docs
Documentation updated.
1 parent 9306d0e commit 467610c

File tree

2 files changed

+53
-4
lines changed

2 files changed

+53
-4
lines changed

docs/index.md

Lines changed: 4 additions & 4 deletions
Original file line numberDiff line numberDiff line change
@@ -1,7 +1,7 @@
1-
![basic checks](https://github.com/materialdigital/core-ontology/actions/workflows/quality-checks.yaml/badge.svg)
2-
![Build Status](https://github.com/materialdigital/core-ontology/actions/workflows/qc.yml/badge.svg)
1+
![Basic Quality Checks](https://github.com/BAMresearch/wcso/actions/workflows/quality-checks.yaml/badge.svg)
2+
![Build Status](https://github.com/BAMresearch/wcso/actions/workflows/qc.yml/badge.svg)
33

4-
# Nanoparticle Ontology (wcso)
4+
# WetChemSyn Ontology (WCSO)
55

66
Welcome to the **Wet-Chemical Syntheses (WeChemSyn) Ontology (WCSO)**, a semantic framework for the structured representation of knowledge related to the production of (nano)particles by wet-chemical synthesis, focused particularly on a self-driving laboratory (SDL) setting, developed at the Bundesanstalt für Materialforschung und -prüfung (BAM) / Federal Institute for Materials Research and Testing in Berlin, Germany.
77

@@ -16,4 +16,4 @@ This documentation is designed to guide you through the ontology's structure, fe
1616

1717
- The latest version of the ontology can always be found at: [wcso.ttl](https://github.com/BAMresearch/wcso/blob/main/wcso.ttl) and [wcso.owl](https://github.com/BAMresearch/wcso/blob/main/wcso.owl)
1818
- [Widoco generated List of Classes and Properties](https://BAMresearch.github.io/wcso/)
19-
- [Documentation of wcso](https://BAMresearch.github.io/wcso/docs)
19+
- [This Documentation of WCSO](https://BAMresearch.github.io/wcso/docs)

docs/intro.md

Lines changed: 49 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,49 @@
1+
# Background to WetChemSyn Ontology (WCSO)
2+
3+
## Why WCSO exists
4+
5+
Wet-chemical synthesis procedures are traditionally documented in free-text form (e.g., “Experimental” or “Methods” sections). This human-centered style has worked so far, but it often relies on implicit knowledge and uses subjective wording instead of explicit parameters. This makes procedures harder to interpret, reproduce, and compare, which is especially true for machines.
6+
7+
At the same time, **Materials Acceleration Platforms (MAPs)** and **Self‑Driving Labs (SDLs)** are increasingly used to autonomously design and execute experiments. In these settings, machines need **precise, explicit, machine-interpretable** descriptions of steps and process parameters. When workflows are created or executed by automation, *sharing* and *reusing* them across sites becomes a central requirement, not only a side effect.
8+
9+
Even when two labs run very similar experiments, they often use different:
10+
- instrument and software stacks,
11+
- workflow/orchestrator frameworks,
12+
- naming conventions for the same operation and parameters.
13+
14+
In distributed SDL environments, this leads to heterogeneous terminology and ad‑hoc metadata practices (“vocabulary drift”), which reduces interoperability and complicates cross-experiment comparison and automated analysis. This motivates a standardized semantic layer that cleanly separates *meanings of textual descriptions* from *implementations on specific platforms*.
15+
16+
17+
## WCSO in a nutshell
18+
19+
The **WeChemSyn Ontology (WCSO)** is a **lightweight, use‑case‑driven ontology** to represent wet‑chemical synthesis workflows (especially for nano and advanced materials) as **machine-actionable “recipes”** that can be shared, queried, and interpreted across heterogeneous SDL/MAP environments.
20+
21+
22+
## Foundations: PMDco and BFO alignment
23+
24+
WCSO is grounded in the **PMD Core Ontology (PMDco)**, a mid-level ontology for materials science and engineering (MSE), which itself builds on the **Basic Formal Ontology (BFO)**. This foundation provides:
25+
- a stable semantic backbone for representing materials, processes, and their context,
26+
- and an interoperability strategy aligned with a broader ecosystem of BFO‑conformant ontologies and knowledge graphs.
27+
28+
In practice, this means WCSO does not reinvent general modeling concepts; instead, it specializes them for wet‑chemical synthesis workflows in SDL/MAP contexts while remaining compatible with other semantic assets used in materials science.
29+
30+
31+
## What you gain by using WCSO
32+
33+
> ### 1) Better reproducibility and clarity
34+
> WCSO encourages describing syntheses with explicit steps and parameters, reducing ambiguity that can arise from narrative protocols and tacit assumptions.
35+
36+
> ### 2) Workflow sharing across labs and platforms
37+
> By abstracting workflow meaning away from specific orchestrators and hardware/software backends, WCSO lowers the effort needed to transfer and reuse synthesis procedures across different SDL/MAP installations.
38+
39+
> ### 3) FAIR and machine-actionable representations
40+
> Ontology-based workflow descriptions support FAIR principles - especially interoperability and reuse as procedures become structured, machine-readable research objects rather than isolated text narratives.
41+
42+
> ### 4) Queryable knowledge graphs for planning and analysis
43+
> When synthesis workflows are exported as knowledge graphs aligned with WCSO, they can be queried to retrieve planning- and reuse-relevant information (e.g., required chemicals and amounts, key parameters, outputs). This enables systematic comparison across procedures and supports data-driven decision making.
44+
45+
46+
## Scope
47+
48+
WCSO is intentionally designed as a **practical ontology for wet‑chemical synthesis workflows** in automation-centered contexts which is focused on representing recipes in a consistent way that can be executed (or at least interpreted) by machines and shared between laboratories. It is openly maintained and meant to be extendable by the community as synthesis knowledge bases and SDL/MAP needs evolve.
49+

0 commit comments

Comments
 (0)