Definition & axiom
⚠ Conflicts with the ISO 15926-4 primary definition
Label (EN)
injection point
Label (PT-BR)
Definition (EN)
Definition (PT-BR)
Semi-formal axiom (Aristotelian)
Axiom type
LLM classification basis: function-based → ≡
ISO 15926-4 classifies it as a FunctionalObject 'that has the purpose of enabling injecting of a substance', and CFIHOS gives only an intended purpose ('Intended to inject material') plus a hedged typical composition. Identity comes from the function, not from a fixed physical configuration.
Validation status
Why primitive (necessary only)
Reviewer notes
FOL theory & disjointness
First-order logic theory (generated)
Loading…
Disjoint with
▸
Expert review
Axiomatization steps
1
Identity-Giving Function
✓ done
InjectionEnablingFunction → InjectionEnablingProcess ⊑ MomentumTransfer
▼
COPI-Core operation
MomentumTransfer via process parent MomentumTransfer
LLM rationale:
ISO 15926-4 states the purpose as 'ENABLING INJECTING' of a substance; API 570 (via the IADC Lexicon) says injection points are locations 'where water, steam, chemicals or process additives are introduced into a process stream'. InjectionFunction (injection pump, injection well) was considered. It is not reused and not made the parent: a pump or well performs the injecting, whereas the point only provides the entry, and a subsumption would make the point inherit the injecting process and its anchor. The function is therefore an independent sibling with parent DesignedFunction (the 'New' case). Anchoring: the kind 'mixing' maps to MomentumTransfer; the point itself imparts no mechanical energy, so the anchor is an approximation shared with many terms and is left as is for now.
▸
Expert review
2
Genus Proximus
✓ done
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:
parent_candidates: FunctionalObject (ISO 15926-4) and 'piping and pipeline equipment' (CFIHOS). FunctionalObject is an ISO 15926-4 top-level notion, not a COPI class, and 'piping and pipeline equipment' is only a CFIHOS grouping, so neither is a usable genus. No more specific domain superclass is known from the definitions, so the nearest IOF-Core class is used, as for cap and spacer. It is not an Assembly: the only composition statement (pipe, item, valve) is hedged with 'Typically'. The identity as an artefact rather than a location is a divergence, recorded below.
▸
Expert review
3
Differentia Specifica
✓ done
∃bearerOf.InjectionEnablingFunction
▼
Conditions that distinguish
Injection Point
from sibling classes under genus
MaterialArtifact.
Only what is not already entailed by the genus.
Differentia expression
Differentia (natural language)
LLM rationale:
The function is the identity-giving trait in both standards. It is not shared with other classes (pumps and wells bear only the parent InjectionFunction), so the equivalence does not capture them.
▸
Expert review
4
Necessary Parts
✓ done
no necessary parts · 2 candidates
▼
Consider part-whole relations beyond subsumption:
hasComponentPartAtAllTimes (universal, structurally essential)
· hasComponentPartAtSomeTime (contingent, optional component)
LLM rationale:
CFIHOS says 'Typically it consists of a pipe connected to an item and a valve in the pipe'. The hedge means pipe and valve are not shown to be present in every instance, and the API 570 literature names other injector arrangements (branch connections, quills, spargers, spray nozzles). They are kept as candidate parts, not necessary parts.
Candidate parts (unconfirmed)
Triangulated findings not yet confirmed as genus-wide. Not exported until promoted.
Pipe
“Intended to inject material. Typically it consists of a pipe connected to an item and a valve in the pipe.”
Valve
“Intended to inject material. Typically it consists of a pipe connected to an item and a valve in the pipe.”
▸
Expert review
5
Process Participation Signature ⟨I, O, T⟩
✓ done
PortionOfFluid + PortionOfFluid → FluidMixture
▼
Inputs (I)
Outputs (O)
Transformation (T)
LLM rationale:
The two inputs are the stream and the injected substance; the output is the stream carrying the substance. 'mixing' is the closest canonical term (stream combination) and maps to MomentumTransfer like the parent InjectionProcess. The 'chemical' in 'chemical injection point' qualifies the injected substance, which is a participant type, not a different kind of point.
▸
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
no CFIHOS/DEXPI properties
▼
No CFIHOS/DEXPI properties found for this cluster.
Custom axioms
none
▼
Axioms not produced by the pipeline. Each is appended verbatim as an
rdfs:subClassOf restriction on Injection Point.
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.