Definition & axiom
⚠ Conflicts with the ISO 15926-4 primary definition
Label (EN)
transmitter
Label (PT-BR)
Definition (EN)
Definition (PT-BR)
Semi-formal axiom (Aristotelian)
Axiom type
LLM classification basis: function-based → ≡
Transmitters are fundamentally defined by their function of signal transmission and conversion, not by their internal mechanism. The variety of subtypes (temperature, pressure, flow, level transmitters) shows that any measurement mechanism can implement the signal transmission function. Identity is given by the function, not the physical configuration.
Validation status
Why primitive (necessary only)
Reviewer notes
FOL theory & disjointness
First-order logic theory (generated)
Loading…
Disjoint with
▸
Expert review
— accepted
Axiomatization steps
1
Identity-Giving Function
✓ done
SignalTransmissionFunction → SignalTransmissionProcess ⊑ MeasurementProcess
▼
COPI-Core operation
MeasurementProcess via process parent MeasurementProcess
LLM rationale:
All definitions consistently emphasize the core identity-giving function: receiving process variable signals and converting/transmitting them as standardized output signals. This signal transduction function is what makes a transmitter a transmitter regardless of the measured variable or sensing mechanism.
▸
Expert review
— accepted
2
Genus Proximus
✓ done
Instrument · MaterialArtifact
▼
Genus (genus proximum)
Most specific superclass — may be a domain class like "Valve" or an IOF-Core root.
BFO/IOF-Core Root
bfo:Object branch
bfo:ObjectAggregate branch
bfo:ImmaterialEntity branch
LLM rationale:
While parent candidates include 'instrument equipment' and 'Instrumentation And Control Equipment', transmitters are clearly a subtype of instruments - devices that measure, indicate, or control process variables. They are causally unified material artifacts designed for measurement and signal processing. The genus 'Instrument' is more specific than MaterialArtifact but not yet enriched in our ontology.
▸
Expert review
— accepted
3
Differentia Specifica
✓ done
∃bearerOf.SignalTransmissionFunction ⊓ ∃hasInput.ProcessVariableSignal ⊓ ∃hasOutput.InformationContentEntity
▼
Conditions that distinguish
Transmitter
from sibling classes under genus
Instrument.
Only what is not already entailed by the genus.
Differentia expression
Differentia (natural language)
LLM rationale:
The differentia focuses on the signal conversion and transmission capability that distinguishes transmitters from other measurement instruments. The requirement for standardized output signals (typically 4-20mA, digital protocols) is a key distinguishing characteristic.
▸
Expert review
— accepted
4
Necessary Parts
✓ done
no necessary parts
▼
Consider part-whole relations beyond subsumption:
hasComponentPartAtAllTimes (universal, structurally essential)
· hasComponentPartAtSomeTime (contingent, optional component)
LLM rationale:
These three components represent the essential functional architecture of any transmitter: sensing, signal conditioning, and transmission. Specific sensor types vary by subtype but the basic architecture is universal.
▸
Expert review
— accepted
5
Process Participation Signature ⟨I, O, T⟩
✓ done
MeasurementInformationContentEntity → InformationContentEntity
▼
Inputs (I)
Outputs (O)
Transformation (T)
LLM rationale:
Transmitters consistently transform physical process variables into standardized electrical, pneumatic, or digital signals suitable for transmission to control systems, displays, or data acquisition systems.
▸
Expert review
More
Alternative labels
none
▼
Synonyms / alternative labels (comma-separated) — skos:altLabel
Language auto-detected on export (PT if the label contains accents, EN otherwise).
Properties as BFO qualities
0 of 1 selected
▼
Select which CFIHOS/DEXPI properties inhere in every instance of Transmitter as
bfo:Quality subclasses.
Each selected property →
:TransmitterQuality ⊑ bfo:Quality, inheres in :Transmitter
Custom axioms
none
▼
Axioms not produced by the pipeline. Each is appended verbatim as an
rdfs:subClassOf restriction on Transmitter.
Write the restriction block in Turtle syntax (without the leading
rdfs:subClassOf).
Example: [ owl:onProperty :hasPart ; owl:someValuesFrom :Wellhead ]
Cross-standard divergences
none detected yet
▼
Click "Detect divergences" to analyse cross-standard disagreements for this cluster.