Library / Semantic Integration Engineering Principles Framework
Jump to passage
In this reading

Link to current text

Published source confirmed at last check

Source changed 2026-10-03 11:52:20 UTC · snapshot created 2026-10-03 11:53:41 UTC · last check 2026-10-03 13:05:11 UTC

SIE.4:5 - Archetypal Grounding - Product Feature and Inspection Characteristic

In the AP242/QIF application, the lexical candidate feature ↔ characteristic is too broad. The source inventory distinguishes an AP242 product-definition feature, a QIF inspection characteristic, the plan relation that applies a characteristic to a feature, and a measured result concerning that characteristic.

Candidate rowDirect relation judgmentUse qualification and disposition
AP242 feature F-17 ↔ QIF characteristic C-17not identity and not class equivalence; the QIF plan asserts that C-17 concerns the identified product feature under configuration/effectivity R/Eaccepted-for-use as a directed inspection-characteristic-concerns-feature relation only after SIE.5 qualifies the feature endpoint; no reverse substitution
AP242 feature type hole ↔ QIF characteristic type diametera diameter characteristic can characterize some holes, but the types are neither equal nor simply broader/narroweraccepted-for-use for navigation from a selected plan row with a qualified feature endpoint to its linked hole feature and diameter characteristic. Return their separate source identifiers and types with the plan relation; forbidden as a global type crosswalk
AP242 feature F-22 ↔ QIF characteristic C-99the candidate arose from a shared local label; effectivity and plan evidence do not support the relationrejected; the interface returns unmatched rather than joining
legacy feature class ↔ current QIF characteristic classone local extension lacks an authoritative definitionunresolved and stopped for dependent mapping; return to the extension owner

The set records endpoint editions and counterexamples such as a non-dimensional inspection characteristic and a feature absent at effectivity E. It establishes semantic premises; it does not decide that identifiers denote the same entity or specify executable joins.