Engineering Services
Custom bridges, custom modules — we build them for you
The architecture is built so others can build on it. If you need to connect an existing ontology to OCO or model a new material class, we do that — by the same criteria the OCO reference implementation was made with.
Bridge construction to existing ontologies
You already work with BattINFO, EMMO-Crystallography, a custom XML/CSV spec, or a standard like ISO 15926? We build the L0 bridge that joins OCO and your world — auditable, version-stable, narrow.
Process
- Format check: OWL/RDF available, else wrapper design (DDLm-to-OWL, BMEcat-XML adapter, etc.)
- Mid-level granularity guaranteed — no upper-level duplicates
- Anchor classes identified — typically 1–20 per target, no full import
- Licence compatibility with CC-BY/CC-BY-SA validated
- SHACL validation against your ABox samples
- Architecture decision documented — reproducible on the next version bump of the target
Examples (existing or on request)
Module development for new material classes
You need an L2 for polymers, metals, HTFC, or batteries — and you don’t want to reinvent L0+L1 every time. We develop the module that fits the toolkit, anchored to your research questions.
Process
- Requirements workshop — your competency questions as the benchmark
- L1 sub-bundling: what stays material-agnostic, what gets moved out
- L2 skeleton design (material hierarchy, classification tags)
- Classes + datatype properties + anchors to your existing data
- SHACL shapes + SPARQL tests against your ABox
- Optional: L3 domain axioms for reasoning use cases
- Validation against the Norouzi criteria catalogue (REQ1–REQ9)
Domains (in development or on request)
Licensing model: Bridges to open ontologies are typically contributed back to the OCO toolkit under CC-BY (matching the L0 licence) — compatible with the bridge targets themselves. Industry-specific modules (material-class-specific L2 content, custom L3 reasoning axioms, compliance implementations) remain under project confidentiality with you, analogous to the three-tier matrix of the OCO distribution: there the full L2/L3, the material/supplier detail level, and all eleven compliance modules complete are proprietary; only the L0 bridge layer (CC-BY) and the L1 skeletons of the material-audience modules (CC-BY-SA) are public. The architecture enables this open/closed mix fine-grained per module.