An application ontology for automotive circular economy data — products, materials, dismantling, reuse, recycling, footprints, logistics, usage, simulation, and transactional records.
AutoMatCE models circular economy scenarios across the automotive domain. It ships classes, object properties, worked examples, release artifacts, SHACL shapes, and reusable modeling patterns — enabling interoperable data exchange between design, manufacturing, use, dismantling, recycling, sustainability, and logistics systems.
|
Product Identity Vehicle, component, part, batch, VIN, BPN, manufacturer records, and product metadata. |
Material Intelligence Polymers, composites, material composition, pVT data, and simulation-ready parameters. |
Circular Decisions Reuse, remanufacturing, recycling, dismantlability, quality, condition, damage, and waste codes. |
Evidence Layer Lifecycle stages, carbon footprints, usage spectra, service life, and auditable value specs. |
Each release ships in three serializations. CI keeps the root files synchronized
with the generated artifacts under src/ontology.
| Variant | OWL | Turtle | JSON-LD | Use when |
|---|---|---|---|---|
| Main | owl | ttl | json | You need the standard public release. |
| Full | owl | ttl | json | You need import-merged semantics for reasoning or inspection. |
| Base | owl | ttl | json | You need the AutoMatCE layer without full external closure. |
The ontology is organized in three layers — external semantic commitments, the AutoMatCE domain modules, and the validation plane that turns edited OWL into synchronized release artifacts.
|
1 · External Semantics
PMD Core, BFO, RO, OBI, IAO, SKOS, and LOG SLME supply reusable upper, relation, annotation, and logistics terms. |
2 · AutoMatCE Modules
Product, material, engineering, usage, dismantling, sustainability, transactional, and shared-axiom components hold the curated application ontology. |
3 · Validation & Release
ODK builds, reasoning, SHACL shapes, pattern examples, SPARQL checks, and artifact sync guard every release. |
%%{init: {"theme": "base", "themeVariables": {"fontSize": "16px", "fontFamily": "Inter, ui-sans-serif, system-ui, sans-serif", "primaryTextColor": "#334155", "lineColor": "#cbd5e1"}, "flowchart": {"curve": "basis", "htmlLabels": true, "nodeSpacing": 50, "rankSpacing": 70}} }%%
flowchart LR
EXT["<b>External Semantics</b><br/><sub>PMD Core · BFO · RO · OBI<br/>IAO · SKOS · LOG SLME</sub>"]
MOD["<b>AutoMatCE Modules</b><br/><sub>product · material · engineering<br/>usage · dismantling · sustainability<br/>transactional · shared axioms</sub>"]
QA["<b>Validation & Release</b><br/><sub>ODK build · import closure<br/>reasoning · SHACL · patterns<br/>SPARQL checks · artifact sync</sub>"]
EXT --> MOD --> QA
classDef external fill:#f5f3ff,stroke:#c4b5fd,stroke-width:1px,color:#4c1d95,rx:10,ry:10;
classDef module fill:#f0fdfa,stroke:#99f6e4,stroke-width:1px,color:#115e59,rx:10,ry:10;
classDef quality fill:#fff7ed,stroke:#fed7aa,stroke-width:1px,color:#9a3412,rx:10,ry:10;
class EXT external;
class MOD module;
class QA quality;
|
Editors' Source automatce-edit.owl is the entry point for editors. Most curated content lives in component modules. |
Component Modules src/ontology/components holds the modular OWL file for each application area. |
Release Sync validate_release_artifacts.py blocks stale root release files. |
|
Ontology Shapes automatce-ontology-shapes.ttl checks labels, definitions, examples, value specs, object-property metadata, and controlled vocabulary. |
Pattern Examples src/patterns contains repeatable modeling recipes with SHACL example data. |
Competency Queries src/patterns/queries holds SPARQL queries for composition, pVT, logistics, lifecycle, and dismantling. |
| Component | Modeling surface | File |
|---|---|---|
| Shared | bridge annotations, external stubs, hierarchy display fixes | automatce-shared.owl |
| Shared axioms | local object properties, domains, ranges, cross-module links | automatce-axioms-shared.owl |
| Product data | products, parts, batches, vehicle information | automatce-product_data.owl |
| Material data | materials, polymers, composites, composition, pVT | automatce-material_data.owl |
| Engineering data | mechanical properties, processing temperatures, simulation cards | automatce-engineering_data.owl |
| Usage data | service life, load spectra, age, status, incidents | automatce-usage_data.owl |
| Dismantling info | dismantling, quality, condition, waste codes, circular routes | automatce-dismantling_information.owl |
| Sustainability data | footprint, lifecycle stage, scenario carbon footprint | automatce-sustainability_data.owl |
| Transactional data | manufacturer, sites, BPN, VIN, vehicle model, production dates | automatce-transactional_data.owl |
Reusable modeling recipes, each shipped with SHACL shapes and validated example data.
| Pattern | Models | Validation |
|---|---|---|
| identifier | VIN, batch IDs, BPN, manufacturer numbers, local identifiers | identifier value and denoted entity |
| quantitative attribute | numeric qualities and scalar value specifications | numeric value and optional unit IRI |
| material composition | products, components, batches, and materials linked to composition records | composition link and readable record label |
| process input output | manufacturing, dismantling, recycling, and logistics processes | participant, input, output, and plan specification |
| lifecycle footprint | carbon footprint values and lifecycle context | amount, unit, and aboutness link |
| logistics transfer | recycling batches, actors, and reverse-chain transfer records | batch-to-actor relation |
| pVT data point | pressure, temperature, and specific-volume tuples | one pressure, one temperature, one specific-volume datum |
| dismantling information | instructions, dismantlability, tools, timing, and safety data | instruction plan and disposition relationships |
| condition damage assessment | body-part quality, vehicle condition, damage, corroded regions | quality inherence and PMD corrosion reuse |
Full pattern index
Additional patterns
SPARQL competency queries
Every change flows through GitHub Actions — build, validate, and release.
%%{init: {"theme": "base", "themeVariables": {"fontSize": "15px", "fontFamily": "Inter, ui-sans-serif, system-ui, sans-serif", "primaryTextColor": "#334155", "lineColor": "#cbd5e1"}, "flowchart": {"curve": "basis", "htmlLabels": true, "nodeSpacing": 44, "rankSpacing": 56}} }%%
flowchart TD
PR["Pull request"] --> QC["Build Ontology"]
PR --> SV["SHACL & Pattern Validation"]
CFG["ODK config change"] --> UPD["Update Repo Config"] --> QC
QC --> ART["Release artifacts<br/>copied to repo root"]
SV --> CHK["Global shapes ·<br/>pattern examples · sync"]
MAIN["Merge to main"] --> QC
MAIN --> DOCS["Widoco documentation"]
MAN["Manual semver release"] --> REL["Release Ontology"]
REL --> TAG["Tag & GitHub release"]
REL --> DOCS
classDef trigger fill:#f5f3ff,stroke:#c4b5fd,stroke-width:1px,color:#4c1d95,rx:8,ry:8;
classDef job fill:#f0fdfa,stroke:#99f6e4,stroke-width:1px,color:#115e59,rx:8,ry:8;
classDef out fill:#fff7ed,stroke:#fed7aa,stroke-width:1px,color:#9a3412,rx:8,ry:8;
class PR,CFG,MAIN,MAN trigger;
class QC,SV,UPD,REL job;
class ART,CHK,DOCS,TAG out;
| Workflow | File | What it does |
|---|---|---|
| Build Ontology | qc.yml | Builds ODK artifacts, runs checks, copies root release files |
| SHACL & Pattern Validation | shacl.yml | Validates global SHACL, pattern examples, SPARQL syntax, and release sync |
| Update Repo Config | update-repo.yml | Syncs generated ODK repository files after reviewed config changes |
| Release Ontology | release.yml | Validates, stamps, uploads, tags, and publishes a semver release |
| Widoco Documentation | docs.yml | Generates human-readable ontology documentation |
| 1 · Choose module | Edit the component that owns the term — product, material, engineering, usage, dismantling, sustainability, transactional, or shared axioms. |
| 2 · Curate term | Add label, superclass, equivalence where needed, Aristotelian definition, example, datatype/unit comment, and semantic axioms. |
| 3 · Add evidence | If the modeling style is reusable, update or add a pattern with pattern.md, shape.ttl, and shape-data.ttl. |
| 4 · Open PR | GitHub Actions builds the ontology, validates SHACL, checks pattern examples, and verifies release artifact sync. |
.
├── automatce.owl · automatce.ttl · automatce.json # main release
├── automatce-full.* · automatce-base.* # full & base variants
├── README.md · LICENSE · CONTRIBUTING.md
├── .github/workflows/
│ ├── qc.yml # build ontology
│ ├── shacl.yml # SHACL & pattern validation
│ ├── update-repo.yml # ODK config sync
│ ├── release.yml # semver release
│ └── docs.yml # Widoco docs
└── src/
├── ontology/
│ ├── components/ # modular OWL per application area
│ ├── imports/ # external import modules
│ ├── automatce-edit.owl
│ └── automatce-odk.yaml
├── patterns/ # modeling recipes + SPARQL queries
├── shapes/ # global SHACL shapes
├── sparql/ # validation queries
└── scripts/ # release validation tooling
Term request checklist
- Give the intended label and module.
- State whether the concept is a class, property, value specification, identifier, quality, process, role, or information content entity.
- Provide the closest known superclass or equivalent class.
- Provide one concrete automotive circular economy example.
- Include datatype and unit expectations for quantitative values.
Release checklist
- Build Ontology workflow is green.
- SHACL and Pattern Validation workflow is green.
- Root artifacts match
src/ontologyartifacts. automatce.ttl,automatce.owl, andautomatce.jsoncarry the expected version IRI.- Manual Release Ontology workflow runs with
dry_run=falseonly after review.
AutoMatCE is released under CC-BY-4.0.
Managed with the Ontology Development Kit and aligned with the PMD Core ontology.