input specification

IRI: https://spec.industrialontologies.org/ontology/construct/InputSpecification

Defined In: https://spec.industrialontologies.org/ontology/core/Core/

SubClass Of: information content entity

Class Hierarchy

owl:Thing › bfo:entity › bfo:continuant › bfo:generically dependent continuant › information content entity › input specification

Definition

information content entity that prescribes the entities to be used as inputs to a planned process or the attributes they must posses to serve as valid inputs

Examples

• A specification indicating that the cell culture media used in the expansion procedure must contain glutamine at ≥ 2 mM and be supplemented with a validated serum lot; A formulation recipe operation with an input specification stating that the stabilizing excipient must be Trehalose Dihydrate, USP grade, and present in sufficient quantity to reach 50 mM final concentration; A specification for a cell imaging protocol requiring input slides to contain at least 90% confluency before proceeding with high-content imaging; A maintenance work instruction with an input specification requiring the replacement filter cartridge used in the filter replacement operation to be the specified model and micron rating; A specification for a batch calculation step requiring the input sensor readings to be time-stamped and include units for each measured quantity; A specification stating that a freight shipment must be palletized on standard pallets and secured for transport before loading.

Counter-Examples

• Machine must be powered on before starting the procedure; The system must be depressurized and isolated before maintenance begins; The workspace must be cleaned and cleared of tools before starting the task; The room temperature must be between 18 °C and 22 °C before initiating the process

Primitive Class

This class is declared primitive and it does not have necessary and sufficient condiftions defined.

Primitive Rationale

See the general discussion and rationale provided for informational entities under ‘information content entity’.

Formal Axioms

First-Order Logic Axioms

InputSpecification(x) → InformationContentEntity(x) ∧ ∀y(prescribes(x,y) → ((Continuant(y) ∧ ∃p(isInputOf(y,p) ∧ PlannedProcess(p))) ∨ (SpecificallyDependentContinuant(y) ∧ ∃z(specificallyDependsOn(y,z) ∧ Continuant(z) ∧∃p (isInputOf(z,p) ∧ PlannedProcess(p))))))

Semi-Formal Natural Language Axioms

if x is an ‘input specification’ then x is an ‘information content entity’ and whenever x ‘prescribes’ some y that y mustbe either a ‘continuant’ that ‘is input of’ some ‘planned process’ or a ‘specifically dependent continuant’ that ‘specifically depends on’ some ‘continuant’ that ‘is input of’ some ‘planned process’

Description Logic

constr:InputSpecification ⊑ constr:InformationContentEntity

constr:InputSpecification ⊑ ∀ constr:prescribes .((bfo:continuant ⊓ ∃ constr:isInputOf .constr:PlannedProcess) ⊔ (bfo:specifically_dependent_continuant ⊓ ∃ bfo:specifically_depends_on .(bfo:continuant ⊓ ∃ constr:isInputOf .constr:PlannedProcess)))

SubClassOf: constr:InformationContentEntity

SubClassOf: constr:prescribes only ((bfo:continuant and constr:isInputOf some constr:PlannedProcess) or (bfo:specifically_dependent_continuant and bfo:specifically_depends_on some (bfo:continuant and constr:isInputOf some constr:PlannedProcess)))

Provenance

• Moved from ReferenceOntologyCandidates (https://spec.industrialontologies.org/ontology/biopharma/ReferenceOntologyCandidates/) on 2026-03-13T12:41:00