Defence semantic interoperability

SynapseCommand Operational Ontology

The SynapseCommand Operational Ontology is a draft public terminological vocabulary that gives operational concepts, relationships and identifiers stable meaning across translated sources.

Version 0.1.0Draft
Semantic role

Common syntax is not common meaning

Two sources can produce records with the same shape while using terms and relationships differently. The Operational Ontology supplies governed classes, relationships, hierarchy, labels, definitions and stable identifiers so those meanings can be inspected.

It is a terminological vocabulary, not a store of operational instances and not a reasoner. It contains no inference rules. Mapping a third-party vocabulary onto it is a governed human decision, not an automatic assertion by the validator.

Eight public Turtle modules

The repository authority is split into 8 modules. A generated JSON-LD context and packaged ontology-term registry are checked against them.

  • core
  • pnt
  • air
  • logistics
  • isr
  • c2
  • mission
  • decision
Conceptual architecture

Shape, meaning and decision logic remain distinct

This is a conceptual separation of responsibilities. A deployment does not need to exercise every adapter or semantic feature for every record.

  1. External layer

    External systems, standards and feeds

    Source formats remain authoritative for their own wire semantics.

  2. Public layer

    Public adapters

    Translate source records into the public canonical layer and, where supported, back out.

  3. Public layer

    Canonical Data Model (CDM)

    Defines the normalised record shape.

  4. Public layer

    SC-OES + Operational Ontology

    Define assertion semantics and governed operational meaning.

  5. Private layer

    SynapseCommand decision runtime

    Applies proprietary reasoning, fusion, scoring and decision support.

The public repository exposes the integration contract and semantic vocabulary. It does not publish the SynapseCommand reasoning, inference, correlation, fusion, scoring or course-of-action runtime.

Terms as published

The eight Turtle modules carry 73 terms in this release. The table below is a sourced extract, not the whole vocabulary: each identifier, definition, relationship, module and maturity value is taken from the Turtle module named in its row. No equivalence with any external vocabulary is asserted.

Extract of published Operational Ontology terms
TermIdentifierDefinitionRelationshipModuleMaturity
OperationalConcepttag:synapsecommand.com,2026-09-06:ontology:core:OperationalConceptAnything this vocabulary can name. The root of the ontology, and the only class with no parent.No parentcoreEXPERIMENTAL
OperationalEventtag:synapsecommand.com,2026-09-06:ontology:core:OperationalEventSomething asserted to have happened, at an instant or over an interval, by a producer that says so.subClassOf core:OperationalConceptcoreEXPERIMENTAL
ObservationEventtag:synapsecommand.com,2026-09-06:ontology:core:ObservationEventAn event in which a producer reports what it observed, measured or directly detected, and asserts nothing about what the observation means.subClassOf core:OperationalEventcoreEXPERIMENTAL
AssessmentEventtag:synapsecommand.com,2026-09-06:ontology:core:AssessmentEventAn event carrying an interpreted judgement, drawn from information or evidence, about something not itself directly observed.subClassOf core:OperationalEventcoreEXPERIMENTAL
DecisionEventtag:synapsecommand.com,2026-09-06:ontology:core:DecisionEventAn event recording that a decision was taken, and by whom.subClassOf core:OperationalEventcoreEXPERIMENTAL
Platformtag:synapsecommand.com,2026-09-06:ontology:core:PlatformAn asset that carries other assets, materiel or people, and whose position can change.subClassOf core:AssetcoreEXPERIMENTAL
affectstag:synapsecommand.com,2026-09-06:ontology:core:AffectsThe subject bears on the object's operational state or freedom of action. It does not say how, or that the effect is adverse.rdfs:range core:OperationalObjectcoreEXPERIMENTAL
GNSSInterferenceEventtag:synapsecommand.com,2026-09-06:ontology:pnt:GNSSInterferenceEventAn event reporting observed interference with the reception of global navigation satellite system signals.subClassOf core:ObservationEventpntEXPERIMENTAL
Aircrafttag:synapsecommand.com,2026-09-06:ontology:air:AircraftA platform that operates in the air.subClassOf core:PlatformairEXPERIMENTAL
ThreatAssessmentUpdatedEventtag:synapsecommand.com,2026-09-06:ontology:isr:ThreatAssessmentUpdatedEventAn event carrying a revised judgement about a threat.subClassOf core:AssessmentEventisrEXPERIMENTAL
C2Systemtag:synapsecommand.com,2026-09-06:ontology:c2:C2SystemA system used to exercise command and control.subClassOf core:Systemc2EXPERIMENTAL
SupplyItemtag:synapsecommand.com,2026-09-06:ontology:logistics:SupplyItemA kind of supply held, issued and consumed as countable quantity.subClassOf core:SupplylogisticsEXPERIMENTAL
OperationalImpactAssessedEventtag:synapsecommand.com,2026-09-06:ontology:mission:OperationalImpactAssessedEventAn event stating an assessed operational consequence for a mission or an activity.subClassOf core:ImpactEventmissionEXPERIMENTAL
DecisionRecordedEventtag:synapsecommand.com,2026-09-06:ontology:decision:DecisionRecordedEventAn event recording that a decision was taken, and by whom.subClassOf core:DecisionEventdecisionEXPERIMENTAL

Turtle is authoritative. The JSON-LD context and the packaged term registry are generated projections of it. Directory view: ontology/. Governance: term and event-type process.

This vocabulary is not a populated operational knowledge graph, an inference engine or an entity-fusion service. It names things and relationships so that meaning can be inspected; it holds no instances and draws no conclusions.

Governance and versioning

Version 0.1.0 is a draft maintained within the SynapseCommand project by Decent Cybersecurity. Every term in this release is marked EXPERIMENTAL; no term claims STABLE maturity.

Terms are changed through the published ontology-term process. The Turtle modules are authoritative. Derived files are generated, and repository tests reject drift between the source vocabulary, JSON-LD projection and packaged registry.

Status and limits

This is not an official NATO ontology and does not claim that external systems share one universal military ontology. It has not been submitted to, reviewed by or approved by an external standards body. Its public vocabulary does not expose proprietary SynapseCommand reasoning or decision logic.

Inspect the governed vocabulary

The public repository contains the authoritative Turtle modules, generated projections, governance process and drift checks. The documentation provides orientation without replacing those repository artefacts.