objective specification
IRI: https://spec.industrialontologies.org/ontology/construct/ObjectiveSpecification
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 › objective specification
Direct subclasses:
Definition
information content entity that prescribes what the outcome of some process should be
Explanatory Notes
1.Typically is part of a plan specification. 2.The NL definition states that the objective specification ‘prescribes’ the outcome of a ‘process’. This does not necessarily imply that a given process exists as an instance during the entire ‘objective specification’ lifecycle. Instead, it should be interpreted as “if an instance of the Process X (X here is intended to represent an OWL:Class that is SubClassOf: Process) exists, then its outcome should be as ‘prescribed by’ the ‘objective specification’.
Examples
- The objective specification in a manufacturer’s six-sigma process improvement program will describe in some detail, the quality improvements to be achieved (as in e.g. the level of reduction in causes of defects, or in the level variability in either or both manufacturing and business processes).
Adapted From
- http://www.obofoundry.org/ontology/iao.html
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
InformationContentEntity(x) ∧ ∃y∃p(Process(p) ∧ isAchievedByAtSomeTime(x,p) ∧ ((ProcessCharacteristic(y) ∧ processCharacteristicOf(y,p)) ∨ (ProcessProfile(y) ∧ processProfileOf(y,p)) ∨ (Capability(y) ∧ hasRealization(x,y)) ∨ (Continuant(y) ∧ isOutputOf(y,p))) ∧ prescribes(x,y)) → ObjectiveSpecification(x)
Semi-Formal Natural Language Axioms
if x is an ‘information content entity’ and x ‘is achieved by at some time’ some ‘process’ p, and x ‘prescribes’ some y that is either a ‘process characteristic’ that is ‘process characteristic of’ p, or a ‘process profile’ that is ‘process profile of’ p, or a ‘capability’ that x ‘has realization’ of, or a ‘continuant’ that ‘is output of’ p, then x is an ‘objective specification’.
Description Logic
constr:ObjectiveSpecification ⊑ constr:InformationContentEntity
constr:InformationContentEntity ⊓ ∃ constr:isAchievedByAtSomeTime .bfo:process ⊓ ∃ constr:prescribes .(bfo:process_profile ⊔ constr:Capability ⊔ constr:ProcessCharacteristic ⊔ (bfo:continuant ⊓ ∃ constr:isOutputOf .bfo:process)) ⊑ constr:ObjectiveSpecification
SubClassOf: constr:InformationContentEntity
constr:InformationContentEntity and constr:isAchievedByAtSomeTime some bfo:process and constr:prescribes some (bfo:process_profile or constr:Capability or constr:ProcessCharacteristic or (bfo:continuant and constr:isOutputOf some bfo:process)) SubClassOf: constr:ObjectiveSpecification