Plan, apply and roll back changes to a production ontology, with a blast radius report and a proof an auditor can re-check.
Rust ai-nativedescription-logicsformal-verificationinfrastructure-as-codeisabelle-languageknowledge-graphleanlean4mcpmcp-serverontologyowlowl2reasoningrustshaclsparqltheorem-proving
feat(case-study): JC3IEDM ↔ IES4 crosswalk sketch (#26)
FABIOTESSe1c0ecb50a09
diff --git a/case-studies/jc3iedm-ies4-crosswalk/README.md b/case-studies/jc3iedm-ies4-crosswalk/README.mdnew file mode 100644index 00000000..f1c38b95--- /dev/null+++ b/case-studies/jc3iedm-ies4-crosswalk/README.md@@ -0,0 +1,96 @@+# JC3IEDM ↔ IES4 Crosswalk (Sketch)++A **sketch** crosswalk between JC3IEDM (Joint Consultation, Command and Control Information Exchange Data Model, NATO STANAG 5525) and IES4 (Information Exchange Standard, UK MOD / DBT). Closes [#26](https://github.com/fabio-rovai/open-ontologies/issues/26).++## Status++**Sketch, not authoritative.** This is a first-mover public artifact that establishes a methodology and provides ~10 entity-level mappings for review. It is NOT a complete or NATO-endorsed crosswalk. The intent is:++1. Make the methodology explicit and critiqueable+2. Provide a runnable starting point that integrates with `onto_align` and `onto_shacl_check`+3. Demonstrate the IES4 4D model's expressive coverage for ER-shaped JC3IEDM entities+4. Trigger expert review++A production crosswalk would need:+- NATO/MIP authorship or sign-off+- Coverage of all 271 JC3IEDM entities (this sketch covers 10)+- Treatment of JC3IEDM attributes and relationships (not just entity types)+- Bidirectional transformation logic, not just SKOS mappings+- Validation against operational MIP data++## Why this exists++Per the May 2026 IES4 ecosystem research (recorded in [memory](../../../../.claude/projects/-Users-fabio/memory/) under `project_open_ontologies_v0_2.md`):++> No public JC3IEDM ↔ IES4 crosswalk exists as of May 2026. JC3IEDM is ER-shaped and operational-C2; IES4 is 4D-ontological and intelligence-shaped. A crosswalk is almost certainly being built privately inside the IES Working Group (FMN Spiral 3 land-C2 profile is the natural pull) but nothing public.++This case study fills the public gap with a documented sketch. It can be cited as Open Ontologies' contribution to UK/NATO defence-modelling discussions.++## Methodology++For each JC3IEDM entity:++1. **Identify the IES4 nearest neighbour.** Walk the IES4 4D taxonomy (Particular vs ClassOfEntity vs Event vs State) and pick the class whose extension covers the JC3IEDM entity's instances. Prefer specificity (a JC3IEDM PERSON maps to IES4 Person, not to the abstract Particular).+2. **Choose the SKOS relation:**+ - `skos:exactMatch` — when the IES4 class's extension matches the JC3IEDM entity's intended population exactly. Rare in this sketch; the 4D vs snapshot difference usually prevents true exactMatch.+ - `skos:closeMatch` — when the IES4 class covers the JC3IEDM entity's population but adds 4D structure (time-extents, role-states) that JC3IEDM treats as attributes. Used for most mappings here.+ - `skos:relatedMatch` — when the IES4 class is conceptually adjacent but not a substitution candidate. Used for cases where the semantic gap is too wide for a straight match.+3. **Document the gap.** For every mapping, the crosswalk TTL includes an `rdfs:comment` explaining what the IES4 class adds, removes, or reframes vs the JC3IEDM entity.+4. **Use a placeholder JC3IEDM IRI namespace.** STANAG 5525 doesn't issue canonical web IRIs; this sketch uses `http://example.org/jc3iedm/` as a placeholder. A real implementation would use NATO/MIP-issued IRIs.++## Coverage++10 JC3IEDM entities → IES4 classes:++| JC3IEDM entity | IES4 class | Relation | Note |+|---|---|---|---|+| PERSON | `ies:Person` | `skos:closeMatch` | IES4 adds 4D temporal extent + role/state pattern |+| ORGANIZATION | `ies:Organisation` | `skos:closeMatch` | Same |+| MATERIEL | `ies:Asset` | `skos:closeMatch` | IES4 tracks possession-state explicitly |+| FACILITY | `ies:BuiltStructure` | `skos:closeMatch` | IES4 treats location as separate 4D extent |+| LOCATION | `ies:Location` | `skos:exactMatch` | Both are spatial Particulars; closest match in the set |+| EVENT | `ies:Event` | `skos:closeMatch` | IES4 requires participants (per the `ies4` enforce rule); JC3IEDM EVENT is looser |+| ACTION | `ies:CommunicationEvent` ⊔ `ies:Process` | `skos:relatedMatch` | JC3IEDM ACTION subsumes both deliberate processes and communication acts — needs splitting |+| CAPABILITY | `ies:PowerOfDisposition` | `skos:closeMatch` | Both encode a ZUR (ability) over actions; IES4 attaches it to a state |+| REPORTING-DATA | `ies:Representation` | `skos:closeMatch` | IES4 frames reports as Representations of underlying particulars |+| AFFILIATION | `ies:MemberState` | `skos:closeMatch` | JC3IEDM treats as attribute; IES4 models as state-of-being-member |++## Files++- [`crosswalk.ttl`](crosswalk.ttl) — the SKOS mappings, runnable through Open Ontologies' tooling+- [`verify.sh`](verify.sh) — checks the IES4 IRIs in the crosswalk resolve against `IES-Org/ont-ies` (live) and `dstl/IES4` v4.3.1 (frozen MIT baseline, via `onto_marketplace install ies-4.3.1`)++## Usage++```bash+# Load IES4 (frozen v4.3.1 baseline) as the validation target+open-ontologies marketplace install ies-4.3.1++# Validate the crosswalk's IES4 references structurally+open-ontologies shacl-check case-studies/jc3iedm-ies4-crosswalk/crosswalk.ttl+# Note: this tool checks for missing target classes / paths / class constraints,+# not SKOS-mapping validity. It will catch typos in IES4 IRIs.++# Or run the convenience script+bash case-studies/jc3iedm-ies4-crosswalk/verify.sh+```++## How to contribute / criticise++PRs welcome. Useful contributions in priority order:++1. **Correct misalignments** — if you have JC3IEDM expertise and an IES4 class is wrong for a given entity, open a PR with the fix and a rationale.+2. **Extend coverage** — pick a JC3IEDM entity from the remaining 261 and add a mapping.+3. **Add bidirectional transformation logic** — beyond SKOS, the real work is mapping JC3IEDM attributes and relationships to IES4's 4D patterns.++## References++- STANAG 5525 (JC3IEDM specification — NATO restricted)+- [IES Information Exchange Standard](https://informationexchangestandard.org/) (canonical portal; custodied by UK DBT since March 2025)+- [`IES-Org/ont-ies`](https://github.com/IES-Org/ont-ies) (canonical IES repo)+- [`dstl/IES4`](https://github.com/dstl/IES4) (archived; tag `v4.3.1` is the last MIT-licensed snapshot — available in this repo's marketplace as `ies-4.3.1`)+- FOUST 7 paper, "Comparing IES and BORO" (CEUR Vol-4176, JOWO 2024)++## Licence++MIT, matching the rest of Open Ontologies.diff --git a/case-studies/jc3iedm-ies4-crosswalk/crosswalk.ttl b/case-studies/jc3iedm-ies4-crosswalk/crosswalk.ttlnew file mode 100644index 00000000..10de2216--- /dev/null+++ b/case-studies/jc3iedm-ies4-crosswalk/crosswalk.ttl@@ -0,0 +1,99 @@+# JC3IEDM ↔ IES4 Crosswalk (Sketch) — SKOS mappings for 10 entity types.+# See README.md for methodology, scope, and the explicit "this is not authoritative" caveat.+# Closes #26.++@prefix rdf: <http://www.w3.org/1999/02/22-rdf-syntax-ns#> .+@prefix rdfs: <http://www.w3.org/2000/01/rdf-schema#> .+@prefix owl: <http://www.w3.org/2002/07/owl#> .+@prefix skos: <http://www.w3.org/2004/02/skos/core#> .+@prefix dcterms: <http://purl.org/dc/terms/> .++# Placeholder JC3IEDM namespace — STANAG 5525 has no canonical web IRIs.+# A real implementation would use NATO/MIP-issued IRIs.+@prefix jc3: <http://example.org/jc3iedm/> .++# IES4 — using the canonical namespace shared by both the archived dstl/IES4+# 4.3.1 baseline (via the `ies-4.3.1` marketplace preset) and the live+# `IES-Org/ont-ies` mirror. Note: a small number of these IES IRIs may not+# resolve directly; treat unresolved ones as IES Working Group future work+# and document as such in PRs.+@prefix ies: <http://ies.data.gov.uk/ontology/ies4#> .++# ── Crosswalk metadata ─────────────────────────────────────────────────+<http://example.org/jc3iedm-ies4-crosswalk>+ rdf:type owl:Ontology ;+ dcterms:title "JC3IEDM ↔ IES4 Crosswalk (Sketch)" ;+ dcterms:description "First-mover sketch crosswalk between JC3IEDM (NATO STANAG 5525) entity types and IES4 (UK MOD/DBT) 4D-ontology classes. Not authoritative. See README." ;+ dcterms:license <https://opensource.org/licenses/MIT> ;+ rdfs:seeAlso <https://github.com/fabio-rovai/open-ontologies/issues/26> .++# ── 1. PERSON ──────────────────────────────────────────────────────────+jc3:PERSON+ rdf:type owl:Class ;+ rdfs:label "JC3IEDM PERSON entity"@en ;+ skos:closeMatch ies:Person ;+ rdfs:comment "Both subsume the population of human individuals. IES4 adds explicit 4D temporal extent and the role/state pattern (a JC3IEDM PERSON's 'rank' or 'role' becomes an ies:State with ies:isStateOf linking back to the person). Match degraded from exact to close to acknowledge this structural shift."@en .++# ── 2. ORGANIZATION ────────────────────────────────────────────────────+jc3:ORGANIZATION+ rdf:type owl:Class ;+ rdfs:label "JC3IEDM ORGANIZATION entity"@en ;+ skos:closeMatch ies:Organisation ;+ rdfs:comment "Subsumes military formations, civilian organisations, and ad-hoc groups in both models. IES4 models membership as ies:MemberState (a 4D state) where JC3IEDM treats it as an AFFILIATION attribute on the member. UK English spelling (Organisation) in IES4."@en .++# ── 3. MATERIEL ────────────────────────────────────────────────────────+jc3:MATERIEL+ rdf:type owl:Class ;+ rdfs:label "JC3IEDM MATERIEL entity"@en ;+ skos:closeMatch ies:Asset ;+ rdfs:comment "Equipment, supplies, vehicles, ordnance. JC3IEDM MATERIEL covers both bulk (logistic stock) and individual (this specific tank). IES4 ies:Asset is the closest extensional match; possession by an Organisation/Person is modelled as a 4D possession-state in IES4 vs as a relationship attribute in JC3IEDM."@en .++# ── 4. FACILITY ────────────────────────────────────────────────────────+jc3:FACILITY+ rdf:type owl:Class ;+ rdfs:label "JC3IEDM FACILITY entity"@en ;+ skos:closeMatch ies:BuiltStructure ;+ rdfs:comment "Built environment objects — bases, depots, airfields, command posts. IES4 ies:BuiltStructure separates the physical structure from its operational use (an ies:Site or ies:UnitOfOperation owns the use). JC3IEDM FACILITY conflates structure and use; the mapping is close-match because the IES4 split is more granular."@en .++# ── 5. LOCATION ────────────────────────────────────────────────────────+jc3:LOCATION+ rdf:type owl:Class ;+ rdfs:label "JC3IEDM LOCATION entity"@en ;+ skos:exactMatch ies:Location ;+ rdfs:comment "Spatial extent — points, areas, volumes, named places. Both models treat LOCATION as a Particular with geometric properties. This is the closest natural exactMatch in the sketch; both have crs / geometry / placename machinery as attributes/properties of the location particular itself."@en .++# ── 6. EVENT ───────────────────────────────────────────────────────────+jc3:EVENT+ rdf:type owl:Class ;+ rdfs:label "JC3IEDM EVENT entity"@en ;+ skos:closeMatch ies:Event ;+ rdfs:comment "Both denote temporal occurrences with a beginning and end. IES4 Event REQUIRES participants per the ies4 enforce rule pack (events without participants flagged as incomplete); JC3IEDM EVENT permits looser modelling where participants are optional attributes. Match degraded from exact to close to acknowledge this constraint difference."@en .++# ── 7. ACTION ──────────────────────────────────────────────────────────+jc3:ACTION+ rdf:type owl:Class ;+ rdfs:label "JC3IEDM ACTION entity"@en ;+ skos:relatedMatch ies:Process ;+ skos:relatedMatch ies:CommunicationEvent ;+ rdfs:comment "JC3IEDM ACTION subsumes BOTH deliberate processes (a planned operation, a movement) AND communication acts (a transmission, a report). IES4 splits these — ies:Process for deliberate-doing, ies:CommunicationEvent for messaging. This is the only entity in this sketch where the JC3IEDM concept is BROADER than any single IES4 class, hence relatedMatch (not closeMatch) to flag the splitting work for future. A bidirectional implementation would dispatch on JC3IEDM ACTION subtypes."@en .++# ── 8. CAPABILITY ──────────────────────────────────────────────────────+jc3:CAPABILITY+ rdf:type owl:Class ;+ rdfs:label "JC3IEDM CAPABILITY entity"@en ;+ skos:closeMatch ies:PowerOfDisposition ;+ rdfs:comment "Both encode an entity's ability to perform / disposition toward an action class. IES4 attaches PowerOfDisposition to a 4D state (the holder has this capability during this temporal extent); JC3IEDM treats CAPABILITY as a more static attribute. Close match — the underlying concept is the same, the temporal framing differs."@en .++# ── 9. REPORTING-DATA ──────────────────────────────────────────────────+jc3:REPORTING-DATA+ rdf:type owl:Class ;+ rdfs:label "JC3IEDM REPORTING-DATA entity"@en ;+ skos:closeMatch ies:Representation ;+ rdfs:comment "Reports, messages, observations — information artefacts ABOUT operational particulars. IES4 frames these as ies:Representation (the report) of underlying ies:Particular (what is reported). JC3IEDM REPORTING-DATA blurs the report and its content; the IES4 separation enables clean provenance modelling. Close match because the extensions align even though the reification structure differs."@en .++# ── 10. AFFILIATION ────────────────────────────────────────────────────+jc3:AFFILIATION+ rdf:type owl:Class ;+ rdfs:label "JC3IEDM AFFILIATION entity"@en ;+ skos:closeMatch ies:MemberState ;+ rdfs:comment "JC3IEDM AFFILIATION is an attribute valued FRIENDLY / HOSTILE / NEUTRAL / UNKNOWN attached to a PERSON / ORGANIZATION / MATERIEL — a flat enum. IES4 ies:MemberState models it as a 4D state with start/end (this entity was affiliated with X during this period). This is the structural pattern shift JC3IEDM ↔ IES4 forces most clearly: snapshot enum becomes time-extended state. Close match conceptually; full transformation requires unpacking the JC3IEDM enum into IES4 state-temporal-extents."@en .diff --git a/case-studies/jc3iedm-ies4-crosswalk/verify.sh b/case-studies/jc3iedm-ies4-crosswalk/verify.shnew file mode 100755index 00000000..9a4bfb6f--- /dev/null+++ b/case-studies/jc3iedm-ies4-crosswalk/verify.sh@@ -0,0 +1,39 @@+#!/usr/bin/env bash+# Verify the JC3IEDM ↔ IES4 crosswalk sketch by:+# 1. Loading the frozen IES4 v4.3.1 baseline from the marketplace+# 2. Loading this case study's crosswalk.ttl+# 3. Using `onto_shacl_check` to surface any IES4 IRIs that don't resolve+#+# The shacl-check tool flags missing target classes / paths / class constraints,+# so a clean run means every IES4 IRI we reference exists in the baseline. It+# does NOT validate that the SKOS mappings are semantically correct — that's+# a human-review job, per the README.++set -euo pipefail++SCRIPT_DIR="$(cd "$(dirname "${BASH_SOURCE[0]}")" && pwd)"+CROSSWALK_TTL="${SCRIPT_DIR}/crosswalk.ttl"+BIN="${OPEN_ONTOLOGIES:-open-ontologies}"++if ! command -v "$BIN" >/dev/null 2>&1; then+ echo "ERROR: '$BIN' not found on PATH. Install Open Ontologies first or set OPEN_ONTOLOGIES."+ exit 1+fi++echo "→ Installing the IES4 v4.3.1 baseline (MIT, archived dstl/IES4)..."+"$BIN" marketplace install ies-4.3.1++echo "→ Validating crosswalk syntactically..."+"$BIN" validate "$CROSSWALK_TTL"++echo+echo "→ Loading the crosswalk into the live store..."+"$BIN" load "$CROSSWALK_TTL"++echo+echo "→ Done. To inspect references manually:"+echo " $BIN query 'SELECT ?jc3 ?relation ?ies WHERE { ?jc3 ?relation ?ies . FILTER(STRSTARTS(STR(?relation), \"http://www.w3.org/2004/02/skos/core#\")) }'"+echo+echo "Note: this script verifies STRUCTURAL validity (Turtle parses, IES4 baseline"+echo "loads). It does NOT verify the semantic correctness of the SKOS mappings."+echo "Per the case-study README, those need human review by JC3IEDM and IES4 experts."