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 05:29:54 UTC · snapshot created 2026-10-03 05:30:57 UTC · last check 2026-10-03 07:00:10 UTC

Source use and currentness

The source contributions guide particular actions and qualifications. Each body states what a source contributes and what remains outside its authority.

Source familyContribution used hereQualification and reopen
Current FPFsource-local meaning, episteme identity, direct Bridge truth, bounded representation use, claim/provenance reliance, representation transition, currentness and affected-use distinctionsFPF retains the generic concepts and assurance law. A changed relied-on result reopens only its SIE consumer.
Current Method Engineeringsituational criteria and the separate repertoire, variant, introduction, and revision Methods in ME.2, ME.15–ME.17SIE supplies domain content; it does not duplicate Method identity or lifecycle decisions.
Current Systems Engineeringengineering-description, configuration/effectivity, change, release, integration, and assurance resultsSIE can supply a qualified semantic premise; SYSE retains engineering decisions.
ISO 704:2022 and ISO/IEC 11179-3:2023distinguish objects, concepts, definitions, designations, registry items, versions, and mapping metadatado not establish cross-source identity, truth, or receiving-use fitness
LOT, maintained LOT resources, and LOT4KGcompetency/use questions, domain-participant validation, qualified reuse or development, and dependencies between an ontology and a selected graph realizationreuse can finish the model question; LOT4KG’s maintained activities do not establish a final peer-reviewed edition or a measured advantage
OWL 2 and the public ISO/IEC 21838-1:2021 descriptionexplicit language semantics and profile choices when formalization is useful; a deliberately selected top-level basis when coherence needs itformal validity does not supply domain adequacy; no universal ontology or full-standard conformance is required or claimed
OBO Foundry principles, including term stability, contact responsibility, and notificationactual module users, stable identification, scoped shared content, reachable responsibility, and notice of changes affecting relianceadapt to the particular commons; contact does not itself assign content or release rights, and an OBO-specific notice interval is not universal
SKOS, SSSOM 1.0, and OAEI 2025correspondence kinds, reusable mapping metadata, and task-dependent alignment evidencea label, similarity score, or matcher output remains a candidate premise
ISO 8000-115:2024, PROV-O, SEMI traceability, and GS1 EPCIS 2.0.1identifier-owner/use-restriction inputs, provenance relations, and domain identity/traceability probesthey create no cross-source equivalence, master identity, authoritative value, or receiving action
R2RML, OMG QVT 1.3, and Ontopbounded executable mapping and virtual/materialized realization formsno mandatory RDF, MOF, graph store, or source authority
SHACL, DQV, Data on the Web Best Practices, ISO/IEC 25012:2008, and ISO 8000-61:2016distinct validation, quality, provenance/version, and quality-management questionsno one layer or score proves receiving-use adequacy
ISO 10303-242:2025 and ISO 23952:2020versioned product-definition/configuration and manufacturing-quality source casesAP242 edition 4 is at stage 90.92, “to be revised”; a changed relied-on successor reopens the affected source, mapping, interface, and case only

The foundation source cut was qualified on 4 September 2026. The model, evolution, and commons contributions were qualified on 8 September using LOT, the maintained LOT4KG description, OWL 2, and the selected OBO principles. LOT4KG’s site cites an under-review manuscript and contains mixed date metadata; its inspected activities supply method guidance rather than proof of a final peer-reviewed edition or measured advantage. The earlier 2024 joint-methodology proposal is historical background; its future-work account does not describe the maintained method’s current evolution activities. The public ISO/IEC 21838-1:2021 description and stage 90.20 systematic review since 15 July 2026 delimit its use here; no full-standard conformance is claimed. Reopen only choices affected by changed relied-on content or use conditions.