Jump to text
On this page
Copy and source
Original source · lines 1–2653
Published source confirmed at last check

Source changed 2026-11-21 03:55:42 UTC · snapshot created 2026-11-21 03:56:39 UTC · last check 2026-11-21 04:15:20 UTC

Semantic Integration Engineering Principles Framework

DocID: SIE within FPF Library.

A domain pattern language for making separately governed meanings and representations usable together for a named receiving use.

  • Author: Anatoly Levenchuk, with AI-assisted development and review
  • Version: 21 November 2026
  • Status: Eternal alpha, open to correction as methods, sources, and applications change. The thirteen Methods support construction of a receiving-use integration, model reuse or development, semantic interfaces, affected-use revalidation, and modular semantic commons.
  • License: CC BY 4.0 for original framework content; third-party material retains its own terms.
  • Publication: FPF Library repository

Use the Readme to enter from a working difficulty, or the Table of Contents to open one available pattern. The Architectural Reference explains how the contributions work together and the scope of their use. For references to this version, use the Citation.

Table of Contents

Use the Readme to follow several methods through a receiving-use problem. Use this Table of Contents when you know the result you need.

SIE.* is the PatternID namespace. Numbers are stable addresses, not a Work sequence.

Public units

UnitReader use
Semantic Integration Engineering Principles Framework ReadmeFollow connected inspection, provider and semantic-commons uses, including changed premises and partial results.
CitationCite this edition or one pattern with its PatternID and date.
Semantic Integration Engineering Principles Framework Architectural ReferenceUnderstand how the contributions connect, why their boundaries matter, and which combined results the repertoire can support.
SIE.Reference:1Meanings, identifiers, claims, carriers, and world-side referents remain distinct
SIE.Reference:2Source authority and receiving authority remain separate
SIE.Reference:3Pattern relations do not prescribe a lifecycle
SIE.Reference:4The first whole result
SIE.Reference:5Use the repertoire at the scale of the missing result
SIE.Reference:6Qualify the combined arrangement
SIE.Reference:6.1A shared request limit changes the provider result
SIE.Reference:7Architectural Rationale
SIE.Reference:7.1Source contributions behind the arrangement
SIE.Reference:8Costs, perspectives, and correction
SIE.Reference:9Before relying on the whole result
SIE.Reference:10Intended use and ordinary non-use
SIE.Reference:11PatternID and reader order
SIE.Reference:12Supplied pattern repertoire
SIE.Reference:13Package anatomy and direct result relations
SIE.Reference:14Pattern selection and first returned result
SIE.Reference:15Related modeling and engineering work
SIE.Reference:16FPF, neighboring practice, and authority boundaries
SIE.Reference:17Representative case coverage
SIE.Reference:18Publication boundary
SIE.Sources:1Source use and currentness
SIE.Sources:2Edition return
Authoritative Pattern BodiesUse the thirteen SIE bodies under their own entry conditions.
SIE.Application - Cross-Pattern ApplicationInspect AP242/QIF, semiconductor identity, quality/provenance, high-change-provider, and semantic-commons cases.
Semantic Integration Engineering Principles Framework Sources and Edition NotesCheck package anatomy, availability, sources, neighboring modeling work, owners, and edition limits.

Part I - Semantic Integration Engineering Methods

§ID & TitleStatusKeywords & Search QueriesDependencies
1SIE.1 - Bound the Receiving Use and Semantic ContractStableWhat receiving use, semantic loss boundary, authority, and validation obligation govern this integration?FPF C.37; C.39.RQ; direct receiver and source-owner results
2SIE.2 - Recover and Qualify Source Semantics and AuthorityStableWhat does each load-bearing source mean, under which edition, effectivity, authority, and access conditions?SIE.1 or equivalent contract; FPF F.0.1, F.0.2; direct source owners
3SIE.3 - Construct or Reuse a Semantic Model for a Named UseStableDoes an available model answer the receiving questions, or what semantic extension is needed?SIE.1 or equivalent use; relevant SIE.2 source meanings; domain participants
4SIE.4 - Judge Cross-Source Correspondences and Their Permitted UsesStableWhich endpoint relation, difference, or incompatibility is warranted and usable here?SIE.2; supplied SIE.3 result when required; FPF F.9
5SIE.5 - Resolve Cross-Source Identity without Erasing Identifier AuthorityStableDo these source endpoints concern the same entity at the required grain and interval, or another relation?SIE.2; conditional SIE.4; direct MDM/domain authority inputs
6SIE.6 - Fuse Source-Qualified Claims without Erasing ConflictStableHow can source claims be composed while preserving scope, authority, uncertainty, conflict, and non-comparability?SIE.2, SIE.4; SIE.5 when identity is load-bearing; FPF C.2.1, A.10
7SIE.7 - Specify Semantic Extraction and Transformation MappingsStableWhich executable rules preserve the accepted correspondences, identities, claim branches, and losses?SIE.2, SIE.4; conditional SIE.5 and SIE.6; FPF A.6.3.RT
8SIE.8 - Choose Virtual, Materialized, or Hybrid Semantic RealizationStableWhich available realization can meet the semantic, freshness, access, provenance, recovery, and combined resource conditions?SIE.1, SIE.7; direct Data Engineering, platform, provider, and protection results
9SIE.9 - Connect a Receiving Use through a Semantic InterfaceStableWhat smallest interface carries the required meanings, branches, provenance, and return paths into receiving Work?SIE.1, SIE.7, SIE.8; conditional SIE.4-SIE.6 results
10SIE.10 - Validate a Semantic Integration Result for Its Receiving UseStableWhat does the evidence settle about the named receiving use, and which claimed premises still need validation?SIE.1 or equivalent use; relevant SIE.2-SIE.9 results; direct domain and receiver acceptance criteria
11SIE.11 - Trace Semantic Change and Revalidate Affected UsesStableWhich receiving results depend on the changed semantic premise, and what can now continue?Changed relied-on premise; relevant SIE.2-SIE.10 results; FPF A.10.1 when discovery is needed
12SIE.12 - Govern Modular Semantic Commons without Universal AuthorityStableHow can users maintain and rely on shared semantic modules and their changes?Actual shared-module uses; SIE.3, SIE.4, and SIE.11 when their results are needed
13SIE.13 - Construct a Semantic Integration for a Named Receiving UseStableHow do we obtain and connect the required contributions, choose the next missing result, and supply an answer that works under their joint conditions?Receiving need and available results; SIE.1–SIE.11 where their contributions are needed; SIE.12 for actual commons work

Semantic Integration Engineering Principles Framework Readme

Practical entries

To construct a semantic integration from several contributions, use SIE.13: receiving need → required meanings and contributions → valid connections and joint conditions → next missing result → supplied receiving answer → affected return after change. Reuse adequate results. If a local result answers the question, stop there. The worked construction explains why these moves produce a usable whole.

Start from the query, decision, or operation that needs a cross-source answer. The constructed connections below show how meanings, identity, executable rules, and receiving use constrain one another. Reuse supplied results when their use and conditions still match; open the Table of Contents for another question or the pattern-selection guide for a missing result.

The Architectural Reference explains the repertoire and its architectural rationale. You can ask an assisting agent: “Explain this and give me your comments in the language of my work, without framework jargon.”

SIE-INSPECTION - Connect inspection evidence to the configured product

  • Situation: Product-definition and inspection sources are accessible, but a quality engineer cannot tell which inspection result concerns the feature in the configuration being reviewed.
  • Question: How can the receiving query return applicable evidence and expose the branches it cannot establish?
  • First useful result or blocker: The required answer for a named feature, configuration, and effectivity, with the permitted incomplete branches; or the missing configuration or acceptance decision that prevents bounding that answer.
  • Start with: SIE.1 when the receiving question is unsettled; SIE.10 when an existing result fails that question.
  • Stop or return: Stop a dependent branch on unresolved feature identity or configuration. Return a source-definition gap to its owner, a transformation defect to SIE.7, and the release or inspection-acceptance decision to the engineering or quality authority.

In APP-SIE-01, the engineer asks for the QIF plan and result concerning feature F in released revision/configuration R at effectivity E. SIE.1 makes those inputs and the acceptable answer branches explicit. SIE.2 then supplies the source editions, local definitions, the rules or assignments that identify the feature, and the authority for each. If the available model cannot distinguish a planned inspection from an observation of that configured feature, SIE.3 develops that missing distinction and tests it against those cases. An adequate existing model can be reused.

Those meanings allow SIE.4 to state a directed relation: inspection characteristic C-17 concerns product feature F-17 under the plan and configuration. SIE.5 qualifies the feature endpoint at the required grain and effectivity. The relation permits navigation between the records; it does not make a characteristic identical to a product feature. A shared label can suggest a link. If the available plan excerpt leaves the assignment open, retain it as unresolved. If the complete governing plan for that effectivity makes no assignment, report the non-match. SIE.6 uses these premises to combine definition, plan, and observation claims while retaining their sources and any conflict.

SIE.7 turns the accepted relations into selection and transformation rules. The rules select the supplied released configuration, preserve both source identifiers, and expose an unknown unit or unmatched feature. SIE.8 uses those required behaviours when comparing ways to supply the result; SIE.9 makes their meanings, timestamps, provenance, and failure branches available in the engineer’s query.

The constructed application permits a qualified row set with unresolved local-extension and unknown-unit branches shown separately. SIE.10 can support that narrower answer only with matching evidence for all premises on which it relies, including the engineer’s interpretation. A different question can finish much earlier: if a conversion returns 1 millimetre from an input of 1 metre where 1000 millimetres is required, that case establishes the mapping failure and returns it to SIE.7; unrelated layers remain unexamined. When the released configuration changes, SIE.11 follows the changed applicability through the relied-on identity, mapping, and receiving tests. The query supplies evidence; the responsible authorities still decide release and acceptance.

SIE-PROVIDERS - Compare live availability under semantic and access limits

  • Situation: Two provider APIs both expose an availability number, but their quantities and copying permissions differ from what a purchasing comparison assumes.
  • Question: Which qualified answer can the interface supply within the receiving and access conditions?
  • First useful result or blocker: Separately attributed quantities with the conditions needed for comparison, or a semantic or access limit that defeats the proposed answer.
  • Start with: SIE.2 and SIE.6 for unsettled meanings and comparison; SIE.8 when those premises are supplied and realization is the remaining question.
  • Stop or return: Exclude prohibited copying. Return an infeasible complete answer for a permitted narrower result or an access-owner decision. Reopen the affected meaning and interface when a provider changes the quantity it reports.

In the constructed provider case of APP-SIE-04 and SIE.6, Provider A reports 12 on hand and Provider B reports 9 available to promise. SIE.2 recovers the reservation and horizon rules behind the quantities. SIE.3 can reuse a model that keeps both measures, providers, units, times, and horizons distinct. SIE.4 supplies the qualified product-family relation. SIE.6 retains separate provider claims: the numbers do not support a common “21 available” total. For the question “Who can supply 8 now?”, A’s reservation check and B’s promise horizon must also support the receiving use.

Both providers prohibit replication. That prohibition is sufficient for SIE.8 to reject a copied availability store. If the question asks which remaining arrangement to use, compare query-time retrieval and any permitted hybrid with their latency, provenance, failure behaviour, and common resource demands. Develop only serious remaining alternatives. Obtain further evidence when its possible contribution to the choice justifies the burden and displaced work.

The shared-request example assumes four calls for A, four for B, and three for the required common trace, all under one ten-call allowance. The complete answer needs eleven calls before retries. With permission for an incomplete answer, A plus the trace needs seven: SIE.9 can expose “12 on hand at T” and “B not retrieved”, retaining the source and rule trace. B has not reported zero. SIE.10 checks the other conditions needed for that narrower use; if both providers are mandatory, the result is a stop until the allowance or call demand is changed on supported grounds.

Suppose B keeps the same JSON field but changes its promise horizon. SIE.11 compares the meanings and finds the uses that consume them. An “available now” view returns to claim composition, mapping, interface, and receiving-use validation; a future-planning view may accept the new horizon after checking its own conditions. Product descriptions whose meanings are independent of that quantity can keep their earlier qualification. An inaccessible consumer interpretation remains unresolved. Purchasing decides how to act on the qualified or incomplete answer.

SIE-COMMONS - Govern shared semantic modules

  • Situation: Several organizations use a shared classification, and a proposed improvement would change which objects belong to one of its classes.
  • Question: How can the shared model evolve while each consumer can still identify the meaning its work needs?
  • First useful result or blocker: The proposed distinction and the users whose questions depend on it, or an unresolved definition or decision right that prevents the change.
  • Start with: SIE.12, with SIE.3 for changed model content and SIE.11 for actual consumer reliance.
  • Stop or return: Keep incompatible criteria in scoped modules when their users need them. A pair needing only one interface can complete that agreement; shared-module governance is useful when independently maintained modules and users create that further need.

In APP-SIE-05, two manufacturers and a service partner share equipment classes. A proposal replaces “equipment with a replaceable drive” with “equipment serviced through a replaceable drive module”. Equipment X has only a separately replaceable drive; Y also supports drive-module replacement. These cases expose the changed classification: X belongs to the earlier class but not the proposed one, while Y belongs to both.

SIE.3 uses those cases to make the meanings distinguishable. Under the constructed SIE.12 agreement, the authorized maintainers keep equip:DriveReplaceable for the earlier meaning and introduce equip:DriveModuleServiceable for the new one. Both definitions and their editions remain recoverable. Source owners continue to supply the product descriptions on which membership depends.

SIE.11 follows each consumer’s question. The service partner adopts the new class for module-replacement planning, so SIE.4 revisits its correspondences and the query uses the revised relation. SIE.10 checks the integration premises, including the result that admits Y and excludes X. Manufacturer A still needs its spare-drive query under the earlier meaning and can retain matching evidence. The release supplies the access, dependencies, migration information, and notice those uses need. These two completed outcomes leave other consumers’ migration to be established where it matters.

Citation

If you use this edition, cite:

Anatoly Levenchuk, with AI-assisted development and review.
Semantic Integration Engineering Principles Framework.
21 November 2026.
GitHub repository: https://github.com/ailev/FPF

For a particular pattern, add its PatternID and title. Retain the edition designation and date, and include a permanent link or stored copy when exact wording matters.

Semantic Integration Engineering Principles Framework Architectural Reference

Semantic integration is professional Work that makes separately governed meanings and representations usable together for a particular receiver. Its governed object is the maintained semantic-integration arrangement: the use contract, qualified sources and needed model content, correspondences, identity and claim dispositions, executable mappings, realization, interface, validation, and their dependencies and maintenance. An ontology file, mapping table, graph database, registry, API, or pipeline can contribute to that arrangement; none is the whole by itself.

Begin from the query, decision, operation or engineering workflow and the people or systems receiving its result. A joint decision may depend on several recipients being able to use the answer together. Work backward to the answer claims, distinctions, sources, authorities, losses, currentness, and tests that the use needs. Preserve explicit incompatibility when it is more truthful than a common value.

An integration practitioner works with source experts and the receiving engineer, analyst, application team, or other owner of the use. A successful join may still answer the wrong question: the same code can name a product family in one source and a particular item in another, or two availability fields can carry different commitments. At the other extreme, requiring a common ontology or store for every source can delay a small useful answer and suppress a difference the receiver needs. The working problem is to connect the required meanings while keeping their authority, limits, and consequences recoverable.

The main trade-offs follow from that problem. A narrower source cut costs less but may omit a claim that changes the answer. Preserving more distinctions and provenance improves what can be inspected but increases source work, interface detail, and tests. Live access can preserve a source’s control while making availability and repeatability harder to obtain; copying can support repeatable queries while adding permission, refresh, correction, and custody obligations. The contract makes these choices answerable to the receiving use.

SIE.Reference:1 - Meanings, identifiers, claims, carriers, and world-side referents remain distinct

Working objectQuestion it answersWhat it does not establish by itself
term or designationWhich sign is used in one source?one shared concept or referent
concept, type, or relationWhich meaning or classification does the source express?that another source uses the same meaning
schema or semantic modelWhich structures and constraints can be represented?truth of the represented claims or fitness for this receiver
identifierWhat entity does this entry pick out under the applicable rule or assignment?cross-source identity, master identity, or authoritative value
claimWhat is asserted with which scope, interval, source, and uncertainty?agreement, preference, authorization, or action
data item or carrierWhere is a representation recorded or transported?preservation of meaning through extraction or transformation
world-side referentWhich entity or occurrence the claim is aboutthat two descriptions identify it at the same grain and interval

SIE.Reference:2 - Source authority and receiving authority remain separate

A source owner can define a scheme or publish a value without authorizing the receiver’s decision. A master-data steward can decide an enterprise identity without deciding product release or recall. The engineering authority can decide configuration and effectivity without owning a cross-source mapping. A data engineering team can operate a pipeline without deciding semantic equivalence. The receiving application or professional practice owns its operational or decision outcome.

Use SIE to make the semantic premises and losses available for inspection, test them for the named use and return unresolved decisions to those authorized to make them.

SIE.Reference:3 - Pattern relations do not prescribe a lifecycle

The patterns have information dependencies, not one mandatory calendar sequence. SIE.1 and SIE.2 often expose the first stop. A practitioner may enter SIE.5 when the use and source inventory already exist, SIE.8 when a realization choice is current, or SIE.10 when an existing interface needs validation. Discovery, alignment, mapping, implementation, and testing can iterate.

SIE.3 supplies a qualified reused or developed model when adequacy is unsettled. SIE.11 follows a changed semantic premise to the results that relied on it; a compatible reference repair can finish directly. SIE.12 supplies the arrangements needed by those who use the shared modules. A known adequate model, an unchanged use, or one local interface can continue without performing those further Methods.

SIE.Reference:4 - The first whole result

The first useful whole is SemanticIntegrationPackage@Use. It is a connected, inspectable set of eight results, not necessarily one file and not necessarily RDF or a graph:

  1. use contract;
  2. source manifest;
  3. correspondence set;
  4. cross-source identity disposition when it is load-bearing;
  5. source-qualified claim composition;
  6. mapping specification;
  7. realization and interface;
  8. validation account.

The package references any SIE.3 model qualification on which it relies. Preserve identity premises where the answer depends on them; explain their non-use only when it affects interpretation or later reliance. A package may return explicit conflict or non-comparability. Positive validation requires matching evidence for every load-bearing premise of the claimed whole use or contract-permitted subset.

SIE.13 supplies the Method for constructing this whole: derive the needed contributions from the answer, connect their use conditions, obtain the next missing result, and bring the permitted combination into receiving use. The following sections explain the architecture and applications of that Method.

SIE.Reference:5 - Use the repertoire at the scale of the missing result

The package anatomy states what must be inspectable when the promised result is a whole semantic interface package. Use the Methods whose results are missing or whose qualifications need reopening. With a supplied use contract and qualified source meanings, SIE.4 can return one warranted correspondence or an incompatibility and stop. With an existing interface and its premises, SIE.10 can identify a failed receiving-use obligation without rebuilding that interface. Reuse an available result when its subject, source editions, use, and conditions still match; reopen the contribution whose premise changed.

Some relations need separate answers even when one practitioner handles them. A correspondence supplies a relation between meanings; SIE.5 supplies a cross-source identity disposition when the answer depends on the same entity at a particular grain and interval. SIE.6 then qualifies the composition of source claims. Identity can hold while claims conflict, and claims can be compared without merging their subjects. SIE.7 specifies executable behavior from those premises; SIE.8 compares ways of supplying it; SIE.9 carries the qualified result into the receiver’s work. Their results constrain one another, while a defect can return to any supplying pattern.

A bounded interface package needs adequate models, its other load-bearing premises, and the required implementation and validation evidence. The five applications demonstrate interface and shared-module uses. Their differences change the work: AP242/QIF needs configuration and effectivity premises; semiconductor traceability makes identity grain and issuer rules central; an analytic can fail on a unit conversion or hidden default; live provider comparison may need qualified difference and non-comparability instead of a shared value. The shared-equipment commons adds module decisions, dependencies, and semantic change. Each application uses the same repertoire at the scope of its receiving question.

If a required distinction cannot be expressed, SIE.3 reuses, extends, or constructs the needed semantic content. An unresolved source definition still limits the dependent mapping or interface claim. SIE.11 compares changed reliance and obtains the affected domain results; its wider account is conditional on a receiving need. SIE.12 supplies shared-module maintenance and decision arrangements where users require them. The source, implementation, and receiving owners retain their respective returns.

Use SIE.13:4.1–4.4 when the missing contribution is not yet known or the available results still need to be connected into the receiving answer.

SIE.Reference:6 - Qualify the combined arrangement

Three questions remain distinct. Is each source meaning, correspondence, identity disposition, or composition rule supported? Does that result permit the particular use made of it? Can all relied-on results and their realization satisfy the receiving contract together? A true relation may be too lossy for one transformation. Two individually current sources may concern different effectivity intervals. Several feasible components may exceed a shared access limit. The relevant bodies answer their local questions; the whole-use conclusion also needs these joins and common conditions.

For the combination, bind the same receiving question and the actual subjects, grain, intervals, source and rule versions, accepted losses, authority, and failure branches. Where contributions use shared requests, credentials, storage, time, or operating support, compare their total demand with the applicable conditions, including required trace and recovery behavior. Establish who may obtain, copy and disclose the required content. One response can serve two independent uses when each recipient is permitted to receive it and can use it by their deadline. A joint decision also needs the handover and authority that let them act together. Keep a common source or derivation visible when several results rely on it; repeated citations or passing tests of the same premise are not independent support for a different claim. The realization comparison belongs in SIE.8, Solution and the bounded validation in SIE.10, Solution. SIE.13:4.2–4.6 constructs the required connections, obtains missing contributions and returns their combined result to the receiving use.

SIE.Reference:6.1 - A shared request limit changes the provider result

Consider a constructed variation of APP-SIE-04. The receiving contract allows an explicitly incomplete purchasing answer. Assume that adequate models and the required source, correspondence, identity, and composition premises have been supplied. Provider A still means “on hand”; provider B means “available to promise”; their claims must keep those meanings. Permissions allow live retrieval and the agreed immediate presentation, but prohibit replication.

For this illustration, four calls retrieve A’s required rows, four retrieve B’s, and three retrieve the common source and rule trace required even for a partial answer. All calls consume one gateway allowance of ten requests in the agreed request window; none is shared or counted twice. Retries also consume the allowance, and the contract accepts neither a copied cache nor deferral to another window for this answer. Each pair of contributions fits: 8, 7, or 7 calls. The complete answer requires at least 11 before retries, so pairwise feasibility does not establish the whole arrangement.

SIE.8 therefore cannot select that arrangement as supplying the complete result. Under the stated incomplete-answer permission, an A-only result with the required trace uses seven calls before retries and can be proposed with B explicitly marked as not retrieved under the request limit. SIE.9 must preserve A’s on-hand meaning and the incomplete branch; it must not render B as zero stock or call the response a complete provider comparison. For example, an A source value on_hand = 12 observed at T becomes a receiving row 12 on hand at T, with its source and rule trace and the branch B not retrieved. It supplies no available-to-promise value.

SIE.10 tests the remaining required conditions before any bounded positive validation. If both providers are mandatory, return a stop and the missing result: for example, an access-owner decision changing the allowance or an implementation that demonstrably reduces calls while preserving meanings and trace. Omitting provenance is not an equivalent repair.

The quantities are construction assumptions, not measurements of providers. Actual use needs evidence for the gateway condition, call demand, permissions, freshness, behavior under failure, and the receiver’s interpretation. Passing source lookups or several pairwise tests cannot supply that evidence for the whole. A changed allowance reopens the affected realization and use validation; an unchanged correspondence can remain usable.

Constituent actions in ongoing work. While processing an exchange, resolving a source identifier can constitute part of interpreting a correspondence, within an ongoing integration of the receiving information. If the receiving use changes from present eligibility to eligibility at an earlier date, a lookup that returns only the present subject state is no longer sufficient. The team may have parser and database skills but lack the intermediate meaning or temporal-identity account. Supply that contribution through the relevant SIE Method rather than treating a successful query as a successful integration. FPF B.1.5.EW helps recover the connection; SIE.8 and SIE.10 keep the whole arrangement and its warranted validation in view.

SIE.Reference:7 - Architectural Rationale

The language is organized around the results that make a receiving use possible. Source recovery, relation truth, bounded identity, claim composition, executable semantics, realization, interface, and validation can fail independently and return to different owners. Keeping their Methods directly accessible permits a useful early stop and replacement of one contribution without inventing a new lifecycle for the entire arrangement.

Serious alternativeWhen its contribution is enoughWhy SIE keeps a different boundary for the combined use
Use FPF and the owning engineering, data, MDM, or application practice directlyOne representation, domain identity, configuration, pipeline, or decision result closes the question.A recurring cross-source interface question still needs source-qualified correspondences, mappings, interpretation, and receiving-use validation joined together. SIE supplies that remainder and returns the other results to their owners.
Treat ontology engineering as the whole practiceThe missing result is a model that expresses the required distinctions and questions.An adequate existing model can support integration without a new ontology. Model construction alone does not supply identity dispositions, claim composition, executable mappings, or a usable interface. SIE.3 supplies that distinct model result.
Make a materialized knowledge graph the standard resultPermitted copying, a suitable refresh and correction arrangement, and reproducible queries meet the contract.A graph is one realization. The live-provider case forbids replication, and useful incompatibility must remain expressible. Conversely, live federation is unsuitable when its access, availability, or repeatability cannot meet the use.
Use one canonical enterprise model and master identityA responsible domain or MDM authority has supplied a bounded common model, identity, or authoritative-value result that the use can rely on.Integration alone cannot grant that authority or erase local grains, versions, claims, and incompatible meanings. SIE preserves the supplied result’s scope and the source identifiers that make correction possible.
Collapse the work into one prescribed lifecycleA local team may use a repeatable plan for a recurring, stable situation.A direct identity question, realization decision, or validation failure has different inputs and stops. The pattern language preserves those entries and conditional result relations; the local plan remains one use of it.

The complete repertoire joins model adequacy, semantic interfaces, changed reliance, and commons maintenance through the results each supplies. Completing a small model or interface question remains useful on its own. A continuing service requires its operational results, and a commons requires the rights and dependencies of those who use it.

SIE.Reference:7.1 - Source contributions behind the arrangement

The source-use account gives the qualified source cut and its dates. Standards, tools and practices each supply parts of the integration method. The receiving question determines which contributions have to work together.

Terminology and registry practice, including ISO 704:2022 and ISO/IEC 11179-3:2023, makes source objects, concepts, definitions, designations, items, and versions distinguishable. SIE.2 adapts that contribution into the smallest inventory needed by the receiver. This improves on schema inspection plus informal recollection: a mapping can point to the operative definition and edition. It still cannot infer a cross-source relation from a registry entry. FPF’s source-local meaning and direct Bridge distinctions supply the separate generic questions used by SIE.2 and SIE.4.

SKOS supplies different correspondence forms; SSSOM 1.0 makes endpoints, predicates, justification, provenance, and source versions inspectable. OAEI 2025 contributes task-dependent alignment evidence. SIE.4 uses those contributions to separate candidate generation, direct relation judgment, and a receiving-use qualification. A two-column crosswalk or score can help find a candidate, but the chosen relation, permitted loss, and counterexamples determine whether it can support this transformation. A new endpoint sense or defeating counterexample reopens that row.

ISO 8000-115:2024 contributes identifier ownership, semantics, restrictions, and resolution inputs within its declared scope. PROV-O supplies distinctions for derivation, attribution, revision, specialization, and alternate descriptions. SIE.5 and SIE.6 adapt these into two different results: an identity disposition and a source-qualified claim composition. A merged key cannot replace the first, and provenance cannot settle the second’s truth or authority. The SEMI and GS1 traceability sources in SIE.5, SoTA-Echoing make grain, issuer, and event-time failures concrete; they do not authorize a recall or establish an enterprise master identity.

R2RML and QVT 1.3 contribute bounded declarative mapping and transformation forms. The Ontop line demonstrates a virtual realization over mappings. SIE.7 and SIE.8 adapt those contributions into an independently inspectable semantic rule and a choice among whole arrangements. This costs explicit specification and comparison, but it permits an implementation to change while preserving the required behavior. Neither RDF nor MOF nor a graph store is required. Failure of a mapping premise returns to the semantic rule; an implementation discrepancy returns to its implementer.

SHACL supplies declared graph-constraint tests. DQV and the data-quality sources in SIE.10, SoTA-Echoing contribute dimensions, measurements, and process questions. SIE.10 retains their distinct evidence roles and adds the representative receiving-use replay. A passing shape can coexist with the wrong identity or a concealed stale branch. The arrangement therefore uses categorical pass, narrow, unresolved, and stop results under the contract, rather than a compensating overall score. Evidence for implementation and operation remains necessary when the conclusion relies on actual service behavior.

LOT contributes ontology requirements, development, publication, and maintenance to SIE.3. Sufficient model reuse remains a completed result. LOT4KG distinguishes ontology work from graph construction and relates changes to dependent mappings, constraints, and validation; SIE.11 uses those relationships for graph realizations. OBO Foundry principles contribute scoped module, term-stability, maintenance, and communication practices to SIE.12, with their community-specific rules qualified in the source account.

Reconsider the affected choice when a simpler qualified contribution supplies the same result, a represented use repeatedly needs a missing Method, or a source or case defeats a relied-on boundary. When the need is a reusable Method repertoire, FPF C.39.RP returns inspectable alternatives, source contributions, relations, and gaps for that comparison; the integration-specific question stays in SIE.

SIE.Reference:8 - Costs, perspectives, and correction

The gain is an answer whose meanings, sources, qualifications, and unresolved branches can survive into receiving work. The cost is source recovery, explicit relation and loss judgments, trace, implementation evidence, and representative tests. Keep that burden proportional to what can change the answer. A single correspondence question does not require a service architecture; a claim of a usable whole interface cannot omit a load-bearing identity or provenance obligation merely to stay cheap.

The source cut reflects the receiver’s question and the sources practitioners can inspect. A well-documented schema or a familiar formal vocabulary can receive more attention than an inaccessible local rule. Source experts and receiving users may also differ over which distinctions matter. Make missing access, authority, meanings, and perspectives visible in the contract and inventory instead of treating absence as agreement. The five constructed applications illustrate how to apply the methods.

Correct the result at the point that owns the defect. A hidden default returns to SIE.7; an unsafe interpretation of a partial response to SIE.9; unsupported identity to SIE.5 and the required domain authority; a pipeline discrepancy to Data Engineering. For the AP242/QIF case, SYSE.13 supplies the decision-specific configuration basis, including actual subjects and effectivity; SIE consumes those premises and can return a mismatch, but does not decide the engineering configuration. The other owner boundaries remain in force. Preserve unaffected qualified contributions and retest what the correction can change.

SIE.Reference:9 - Before relying on the whole result

Recognition asks which available pattern can supply the next useful result. Assurance asks what supports the receiver’s use of the result. Use the checklists in the selected bodies and inherit their answers only while the subject, content, use, source versions, and relevant conditions match. For a combined package, answer these questions in the account the receiver needs:

  • Can the receiver recover the question, answer claims, accepted losses, authority boundary, and useful stop? An early correspondence or inventory result must not be presented as a validated interface.
  • Can every load-bearing correspondence, identity disposition, and claim-composition premise be traced through the mapping and interface, with its grain, interval, limits, and unresolved branches?
  • Does the whole arrangement meet shared semantic, access, resource, currentness, provenance, and failure conditions? Which implementation or owner result is still absent?
  • Does each evidence item support the claim made from it, and does the representative receiving-use test cover positive, negative, and unlike cases? Several passing layers cannot compensate for a hard stop in another.
  • Is a narrow result recognizable as narrow, with excluded or unexamined branches and their consequences visible? In the request-limit example, an A-only answer cannot stand for the complete provider comparison.
  • Do a model gap, changed semantic premise, or shared-module decision reach SIE.3, SIE.11, or SIE.12 where needed? Are source, implementation, and receiving decisions returned to their owners, with unresolved dependence made visible?

These questions address the failures in the applications: field-name equivalence, merged identifiers without authority, source claims flattened into one value, healthy transport mistaken for semantic fitness, and missing branches hidden from the receiver. Repair the specific premise or interface, obtain the missing contribution, narrow under the contract, or stop.

SIE.Reference:10 - Intended use and ordinary non-use

Use this framework when the working result must make separately governed meanings, identities, claims, or representations usable together for a named receiver. Use one pattern or a small cooperating set and stop at the first decision-changing result or blocker.

Do not use SIE for local modeling with no cross-source receiving-use question, physical data movement, pipeline operation, one application’s schema design, master-data authority, product configuration or release, generic representation choice, or the receiver’s operational decision. Obtain those results from their owning practices. A local mapping inside one source can remain local unless it changes a cross-source semantic result.

SIE.Reference:11 - PatternID and reader order

SIE.* is the Semantic Integration Engineering PatternID namespace. Numbers are stable addresses, not steps or maturity levels. The Table of Contents gives reader order. A dependency names a result needed by one use; it does not require every lower-numbered body to run.

SIE.Reference:12 - Supplied pattern repertoire

The repertoire supplies SIE.1–SIE.13. The model, change, commons and whole-construction entries return these domain results:

  • SIE.3 - Construct or Reuse a Semantic Model for a Named Use: adequate reuse or the semantic development required by a demonstrated gap.
  • SIE.11 - Trace Semantic Change and Revalidate Affected Uses: direct affected-use results, with a common account when a receiver needs it.
  • SIE.12 - Govern Modular Semantic Commons without Universal Authority: a working shared-module arrangement for actual users.
  • SIE.13 - Construct a Semantic Integration for a Named Receiving Use: the connected semantic integration, including acquisition of missing contributions, joint conditions and its bounded receiving result.

A supplied Method guides the work; an inaccessible source, unresolved meaning, missing right, or absent implementation result can still limit a particular use.

SIE.Reference:13 - Package anatomy and direct result relations

SIE.13 constructs the whole from the required contributions below. The table identifies results to connect or reuse, not a required new deliverable from every pattern.

Package partSupplying body or returnMinimum inspectable content
use contractSIE.1receiver, use, answer claims, tolerated loss/uncertainty, freshness/latency/quality, authority, representative tests, stop and reopen
source manifestSIE.2; SIE.3 qualification when neededassets, schemes, editions/effectivity, meanings and identifiers used, owners/authority, provenance/access, gaps, and references to required model qualifications
correspondence setSIE.4endpoints, relation or incompatibility, orientation, bounded use, permitted loss, justification/evidence, source versions, counterexamples and unresolved rows
cross-source identity dispositionSIE.5load-bearing endpoints, grain and interval, disposition kind, resolution rules and contexts or assignments and their issuers, evidence, authority boundary, downstream references for the relied-on identity; an explanation of unused identity only when it affects interpretation or later reliance
source-qualified claim compositionSIE.6source claims, scope, interval, authority, uncertainty, derivation, relied-on identity premises, comparable/conflicting/non-comparable/unresolved relation, qualified view or explicit conflict
mapping specificationSIE.7schemes, accepted semantic inputs, rules, conditions, cardinalities, units/codes, defaults, errors, loss, trace, examples and tests
realization and interfaceSIE.8, SIE.9virtual/materialized/hybrid decision, required implementation result, receiver contract, interpretation, currentness, errors, provenance, access assumptions and return path
validation accountSIE.10evidence sufficient for the bounded disposition; every load-bearing layer and required cases for a positive use claim; material unexamined reach, pass/narrow/unresolved/stop, and reopen condition

SIE.1 → SIE.2 supplies the use and source cut. SIE.2 → SIE.3 is conditional. SIE.2 and any supplied use-fit model feed SIE.4–SIE.6. SIE.4 can expose an identity question for SIE.5 and supplies semantic premises to SIE.7. SIE.5 supplies load-bearing identity premises to SIE.6, SIE.7, and SIE.10. SIE.6 supplies a qualified composition or explicit conflict branch to SIE.7 and SIE.9. SIE.7 → SIE.8 → SIE.9 → SIE.10 connects executable semantics to realization, receiver, and bounded validation. SIE.11 revisits only affected reliance, using these dependencies where material. SIE.12 supplies shared-module arrangements when actual users require them. These relations may iterate.

SIE.Reference:14 - Pattern selection and first returned result

Working questionStart or returnFirst result
How can the required contributions supply the receiving answer together?SIE.13SemanticIntegrationPackage@Use, a permitted partial result, or the question still unresolved or the condition that requires a stop
What use and loss boundary govern the integration?SIE.1SemanticIntegrationUseContract@Use
What does each source mean and own?SIE.2SourceSemanticInventory@Use
Are the available models adequate, or what content must change?SIE.3 when adequacy is unsettledUseFitSemanticModel@Use or the condition preventing a model result
Which endpoints correspond or remain incompatible?SIE.4QualifiedCorrespondenceSet@Use
Which identifiers concern the same entity at this grain and interval?SIE.5CrossSourceIdentityDisposition@Use
How can governed claims be composed without hiding conflict?SIE.6SourceQualifiedClaimFusion@Use
Which executable rules implement the accepted semantics?SIE.7ExecutableSemanticMappingSpecification@Use
Should the arrangement be virtual, materialized, or hybrid?SIE.8SemanticRealizationDecision@Use
What interface carries the meaning into receiving Work?SIE.9ReceivingSemanticInterface@Use
Is the result usable for the named receiver?SIE.10SemanticIntegrationValidationAccount@Use
What follows from a changed semantic premise?SIE.11qualified direct result, scoped gap, or a common affected-use account when needed
How should shared semantic modules be maintained?SIE.12 for users of the commonsModularSemanticCommonsAccount@Community or the condition preventing the shared arrangement

SIE.Reference:15 - Related modeling and engineering work

Use SIE for the contribution that makes separately governed meanings usable together. The following working questions locate that contribution and the decisions that remain with neighboring practices.

Working questionSIE contributionBoundary retained
Terminology and ontology across source modelsSIE.2 recovers source meanings, SIE.3 qualifies or develops model content for an integration use, and SIE.4 supplies correspondencesgeneric terminology, ontology, formal science, and local modeling remain with their direct owners
A model needed for a receiving integration answerSIE.2, SIE.3, SIE.4, SIE.7, and SIE.10 apply when the model supplies a named semantic-integration resultlocal model construction and research remain outside SIE
Formal apparatus needed by a semantic mapping or validationthe required formal apparatus may become a source, mapping, or validation premiseformal modeling itself is not an SIE lifecycle
Connected engineering descriptions and changed lifecycle informationSIE can return a qualified semantic interface, mapping package, identity/claim result, or affected-use resultSYSE keeps engineering descriptions, configuration, release, assurance, and digital-thread decisions; Data Engineering keeps pipeline operation

SIE.Reference:16 - FPF, neighboring practice, and authority boundaries

FPF owns generic representation, grounding, evidence, source/currentness, identity, comparison, and assurance distinctions. Method Engineering owns Method identity, qualification, trial, fit, worth, repertoire, variant, introduction, and revision. Systems Engineering owns engineered-System, engineering-description, configuration, integration, release, and assurance decisions. Data Engineering owns extraction execution, pipeline/service construction, orchestration, observability, reliability, and recovery. MDM and domain authorities own master identity, authoritative values, survivorship, and domain truth. Applications and operating or decision owners own authorization, risk acceptance, and actual outcomes.

SIE supplies Methods for use-qualified model content, cross-source meanings and correspondences, identity and claim composition, executable mappings, realization, interfaces, validation, changed semantic reliance, and modular commons. Return every non-SIE result to its owner and identify the action that depends on it.

SIE.Reference:17 - Representative case coverage

The five constructed cases demonstrate the methods. Claims about deployment, analytic validity, provider performance or practical effects need evidence for that claim in its setting. To establish a release, recall or other domain decision, identify the decision made by the responsible authority.

CaseWhat it testsBoundary for reuse
AP242/QIFconfiguration/effectivity, feature identity, source-qualified composition, mapping, interface, and receiving-use validationengineering and quality authorities retain release and acceptance; AP242 revision reopens affected premises
semiconductor traceabilityidentifiers from several issuers, the grain and interval of each assignment, conflicting evidence and disclosure limitsMDM/domain and recall authorities retain identity, value, and action
quality/provenancemapping coverage, units, defaults, derivation, currentness, and a representative analyticData Engineering and source owners repair their results; quality measures do not decide use alone
high-change providerssufficient model reuse, explicit semantic difference, virtual realization, availability/error branches, changed promise horizon, and non-comparabilityproviders retain source meanings and permissions; purchasing owns action
equipment-classification commonsmodule boundaries, local correspondences, identification, decision and release rights, semantic change, migration, and noticecontacts communicate; source owners and receiving users retain their respective decisions

SIE.Reference:18 - Publication boundary

This publication combines thirteen pattern bodies with the shared reader account. The bodies govern their Methods; the Readme, Architectural Reference, applications, Table of Contents, and boundary account help readers find and combine them.

Use an instructional Guide for sequenced learning and memory formation. Use the Engineering DPF Suite Reference for cross-framework discovery. To obtain a missing SIE result, use the method that supplies it.

For source qualifications, citation and edition information, see the Sources and Edition Notes.

SIE.Reference:End

Part I - Semantic Integration Engineering Methods

SIE.1 - Bound the Receiving Use and Semantic Contract

Type: Method pattern Status: Stable Normativity: Normative method guidance within SIE; examples are constructed and non-normative.

Primary working result: a SemanticIntegrationUseContract@Use that names the receiving use and its recipients, required answer claims, source cut, tolerated loss and uncertainty, currentness, latency, quality, authority, representative tests, stop conditions, and reopen conditions.

SIE.1:1 - Problem Frame

Use this when a request says “integrate the data”, “align the models”, “build the knowledge graph”, or “make one source of truth”, but the intended receiver and decision-changing answer are not yet explicit. The recognizable failure is an integration whose values cannot be interpreted, trusted, or used safely by the Work that requested it.

The subject is one semantic-integration use: a specified query, decision, operation or engineering workflow and the recipients who use its answer under stated conditions. The first move is to state that use and the answer claims it needs. The first result is a bounded contract that lets later workers decide which semantic loss, source age, unresolved row, and test outcome are acceptable.

The practical gain is a testable stopping rule before source, ontology, mapping, or platform choices accumulate. Do not use this pattern to authorize the receiving decision, decide product configuration, choose master identity, operate a data pipeline, or define generic evidence law. Obtain those results from their owners. Do not reopen a current contract merely because another source exists; reopen it when the receiver, use, answer, conditions, authority, or acceptance boundary changes.

SIE.1:2 - Problem

Without a receiving-use contract, “semantic integration” expands toward every source and every possible reuse. Similar labels are merged without a loss budget, freshness is treated as an implementation detail, and a passing schema or sample query is reported as success. The project cannot distinguish an informative unmatched row from a defect, or a harmless delay from a stale answer that changes action.

Technology then supplies the hidden contract. A graph platform encourages graph-shaped outputs, a warehouse encourages copying, and an API encourages whichever fields are easiest to expose. None says which answer claims the receiver may rely on, who owns them, or when the correct result is to stop.

SIE.1:3 - Forces

ForceTension
BreadthMore sources may enable future reuse, while every added source creates meanings, authority, currentness, and validation obligations.
SpeedA quick join can demonstrate access, while early conflation makes later correction expensive and hard to trace.
LossA useful common view often coarsens detail, while silent loss can reverse a decision or erase incompatibility.
Freshness and latencyQuery-time access can be current but slow or fragile; copied data can be fast but stale and harder to govern.
AuthoritySource owners, integrators, and receivers contribute different decisions; having access to or custody of a source gives no additional decision rights by itself.
AssuranceA finite representative test is needed now, while no test establishes universal semantic correctness.
ReuseA broad contract appears reusable, while a small contract is easier to validate and reopen.

SIE.1:4 - Solution

Construct the smallest semantic contract that can change the named receiving action. Begin from the receiver and work backward to required answer claims, source contexts, meanings, losses, currentness, quality, authority, representative cases, and conditions for stopping. Treat the contract as an input to later SIE patterns, not as proof that any source, correspondence, identity, mapping, interface, or implementation exists.

SIE.1:4.1 - Pattern-Use Unfolding

  1. Name the receiver and receiving Work. Identify the System or role that will use the result, the query, decision, operation, or workflow, the horizon, and the first useful answer. For separate receiving decisions, establish what each recipient may see and accept by its deadline. For one joint decision, identify who must contribute or agree and what enables the handover. One result can serve both uses if it meets both sets of conditions.
  2. State the answer claims. Write the fields or propositions the receiver needs, including scope, grain, interval or effectivity, and the action each claim can change. Keep a value, its provenance, its authority, and the receiver’s decision distinct.
  3. Select the source cut. Name only the governed contexts and candidate source assets that can change the answer. Mark sources whose inclusion is uncertain rather than adding them silently.
  4. State preserved distinctions and tolerated loss. Name identities, versions, units, codes, relations, claim scopes, and incompatibilities that must survive. For each permitted coarsening or omission, state why the receiver can tolerate it.
  5. State currentness, latency, availability, and quality conditions. Specify thresholds or unresolved returns where they change use. A deadline for one query, a time bound for every admitted request and a percentile over a specified workload call for different evidence.
  6. Recover authority, permission, and protection boundaries. Name who defines source meanings, who may grant access, who decides identities or authoritative values, who accepts semantic loss, and who owns the receiving action. Identify any missing authority or permission that blocks the use.
  7. Design representative tests before implementation. Include at least one expected positive case, one negative or unmatched case, and one unlike or changed-source case that could defeat the proposed integration. Name the expected branch rather than requiring every test to return a value.
  8. State pass, narrow, unresolved, and stop outcomes. A contract permits a bounded usable subset or explicit incompatibility when that is useful. Stop when a load-bearing meaning, source edition, identity authority, permission, or acceptance rule is unavailable.
  9. State reopen conditions and next result. Identify observations that change the contract and the smallest next result, often SourceSemanticInventory@Use from SIE.2.

SIE.1:4.2 - Record the Result

Contract positionRequired content
receiver and usenamed receiver, Work, query/decision/operation/workflow, horizon, and first useful answer
answer claimspropositions or fields, grain, scope, interval/effectivity, and action changed
source cutgoverned contexts, candidate assets, inclusion reason, and known access limits
semantic boundarydistinctions to preserve, permitted loss, uncertainty treatment, unmatched/incompatible behavior
service conditionscurrentness, latency, availability, recovery, and quality thresholds that change use
authority and protectionmeaning owner, identifier or value authority, access/permission, receiver authority, and protected conditions
validationrepresentative positive, negative, unlike/change cases and expected branches
dispositionpass, narrow, unresolved, or stop rules; next result and observable reopen conditions

SIE.1:4.3 - What Changes in Practice

The team stops treating integration scope as the set of reachable sources. Every later correspondence, identity disposition, mapping rule, realization, interface field, and validation claim must answer to a named receiving use and loss boundary. When the receiving contract allows it, an explicit unmatched or incompatible result answers the question.

SIE.1:5 - Archetypal Grounding - AP242/QIF Configuration Query

A quality engineer asks which QIF inspection plan and result concern feature F in released AP242 product-definition revision/configuration R at effectivity E. The initial request is “connect PLM and quality data in a knowledge graph.” SIE.1 replaces the carrier proposal with this contract:

PositionConstructed value
receiver/usequality engineer preparing an evidence return for one configuration-bound review; query by revision/configuration, feature, and effectivity
answer claimsAP242 feature identifier and configuration/effectivity claim; QIF plan, characteristic, and result identifiers; relation disposition; source edition; timestamp; provenance; unmatched/incompatible status
preserved distinctionsproduct feature versus inspection characteristic; definition versus performed result; revision versus configuration; applicability/effectivity; source identifier and issuer; plan versus result
tolerated lossdisplay may coarsen source-local labels after exact identifiers and relations remain available; no unmatched feature or incompatible characteristic may become a positive relation. For this constructed evidence-return review, the receiver permits the qualified row set with unresolved local-extension and unknown-unit branches shown separately
currentness and latencyfor this constructed review at time T, the receiver requires the released AP242 configuration applicable to the review, QIF observations from T minus 24 hours through T, and a response to this review query within two seconds.
authoritySystems Engineering owns release, configuration, and effectivity; the quality authority owns acceptance; source owners define their models; SIE may qualify mappings but authorizes neither decision
testsknown match; unmatched feature; changed revision; incompatible characteristic; stale QIF result; missing provenance; source timeout
stop/reopenstop on unresolved configuration/effectivity, source edition, feature identity, permission, or acceptance rule; reopen when a relied-on AP242/QIF edition, review use, or protected condition changes

This result does not claim that the two source models correspond or that an interface works. It makes those later claims testable. AP242 edition 4 is recorded by SIE.2 with its current source status; SIE.1 only requires the edition and reopen rule to be explicit.

SIE.1:6 - Bias-Annotation

LensLikely driftRepair
GovernanceThe integration team silently accepts loss or acts as source/value authority.Name each decision subject and the direct authority relation; make absence a blocker.
ArchitecturePlatform boundaries define the semantic use.Begin from the receiving result and keep realization alternatives open.
Ontology/EpistemologyA shared label or data field is treated as a shared meaning or true claim.State answer claims, source contexts, preserved distinctions, and uncertainty separately.
PragmaticsThe contract becomes a complete requirements catalogue rather than a decision tool.Keep only conditions that can change the receiving action or stop.
DidacticsReaders infer that SIE.1 must precede every other pattern.Enter directly elsewhere when an equivalent current contract exists; verify compatibility instead of repeating it.

SIE.1:7 - Conformance Checklist

  • The receiving Work and the recipient or recipients whose decisions it serves are explicit.
  • The first useful answer is expressed as claims or fields with grain, scope, and interval/effectivity.
  • The source cut is justified by the use rather than by reachability.
  • Preserved distinctions, permitted loss, uncertainty, and unmatched/incompatible behavior are explicit.
  • Currentness, latency, availability, recovery, and quality are included only where action-changing.
  • Meaning, identity/value, access, semantic-loss, and receiving-action authorities remain distinct.
  • Positive, negative, and unlike or changed-source tests have expected branches.
  • Pass, narrow, unresolved, stop, next-result, and reopen rules are stated.
  • The contract claims no correspondence, implementation, validation, authorization, or outcome that has not been obtained.

SIE.1:8 - Common Anti-Patterns and How to Avoid Them

Anti-patternRepair
“Integrate all enterprise data.”Name the receiving decision, those who use its result, and the smallest source cut that can change it.
“The knowledge graph is the deliverable.”State the receiving answer and treat graph materialization as one later realization option.
“No information loss.”Name the distinctions and tests; unlimited preservation is not an operational contract.
“Real time.”State a measurable currentness and latency condition for the use.
“Single source of truth.”Name source, identity, and value authorities and the claims each may establish.
“Every test must return a row.”Define legitimate unmatched, incompatible, unavailable, and stop branches.

SIE.1:9 - Consequences

The contract limits source fan-out, makes semantic loss and authority visible, and gives implementation and validation a shared target. It can stop an integration before expensive model or platform work. It also makes conflicts and narrow usable subsets publishable outcomes.

The cost is early negotiation about the receiver, evidence, loss, and stop conditions. Some attractive future reuse remains outside the first package and must earn its own contract or compatible extension.

SIE.1:10 - Rationale

Semantic adequacy is relative to a use. A receiver, answer claim, source context, permitted loss, authority, and representative test together constrain what counts as a successful integration. Beginning there prevents a carrier choice from becoming an implicit ontology, authority model, and acceptance rule.

SIE.1:11 - SoTA-Echoing

The best-known line for this question combines use-bounded representation selection, situational Method criteria, quality-for-use, and explicit source/provenance practice. The serious default alternative is technology- or source-led integration. The difficulty arises when the choice of graph, warehouse or federation defines the answer and loss boundary. SIE.1 applies these contributions by making the whole semantic contract, including authorities and legitimate unresolved branches, the first domain result.

Source lineAdopt, adapt, or rejectRole and limit
Current FPF C.37adoptBounds representation selection and co-use to a named use; does not supply the SIE package or application authority.
Current C.39.RQadaptSituational criteria help state receiving Work and fit conditions; SIE adds semantic endpoints, loss, source, authority, and layered tests.
DQV and ISO/IEC 25012:2008adaptSupply quality dimensions and vocabulary; the contract selects only dimensions that change this use.
Data on the Web Best PracticesadaptContributes provenance, version, access, and reuse questions; no Web publication form is mandatory.
platform-first “single source of truth”reject as defaultA carrier and custody arrangement cannot establish cross-source meaning, authority, or receiving-use adequacy.

Reopen this pattern when representative uses cannot express action-changing loss, authority, or validation obligations through the contract positions, or when a source line supplies a materially better first result.

SIE.1:12 - Relations

  • SIE.2 consumes the source cut, answer claims, distinctions, and currentness questions to produce SourceSemanticInventory@Use.
  • SIE.4–SIE.10 consume the compatible contract positions relevant to their results; none may silently widen the receiver or accepted loss.
  • C.37 governs generic use-bounded representation selection. A.10 and A.10.1 govern evidence/provenance and generic affected-use questions.
  • Applications, Systems Engineering, Operations, quality, safety, legal, and other direct owners supply their acceptance and authority results.
  • A changed contract reopens the package branches that rely on the changed premise. SIE.11 supplies affected-use discovery and integration revalidation where the affected results still need to be established.

SIE.1:End

SIE.2 - Recover and Qualify Source Semantics and Authority

Type: Method pattern Status: Stable Normativity: Normative method guidance within SIE; examples are constructed and non-normative.

Primary working result: a SourceSemanticInventory@Use that records the load-bearing source assets, local meanings, schemes, editions and effectivity, identifiers, claims, owners and authority scope, provenance, access, currentness, gaps, and any question or result to return to the responsible owner for this integration use.

SIE.2:1 - Problem Frame

Use this when a bounded integration use exists, yet endpoint meanings are being inferred from labels, column names, class names, diagrams, sample values, or undocumented organizational knowledge. The recognizable failure is a mapping that runs while joining different concepts, editions, grains, or authority scopes.

Identify the source-local semantic premises on which the receiving use depends. The first move is to select one load-bearing source asset and recover its scheme, edition or effectivity, meaning, owner, authority, provenance, and access conditions. The first result is an inventory that identifies the usable premises and what is missing.

Distinguish what a source says, what an integrator infers and what another owner must decide. Do not use SIE.2 to construct an ontology, establish a cross-source correspondence, decide identity, fuse claims, or judge receiving-use adequacy. If model adequacy for a required distinction remains unsettled, request UseFitSemanticModel@Use from SIE.3 or another qualified direct provider. Adequate reuse can finish that question; a missing distinction may require extension or construction.

SIE.2:2 - Problem

Source inventories often list files and endpoints but omit the meanings that make their values usable. A table called feature, an API field called available, and an identifier called partNumber appear self-describing. Their meanings may depend on an edition, profile, configuration, interval, issuer, lifecycle state, organizational rule, or local extension.

When those dependencies are hidden, later workers can neither justify a correspondence nor trace a failure. A changed source looks like a schema defect even when the meaning changed; an access right is mistaken for authority; and a provenance record is mistaken for truth.

SIE.2:3 - Forces

ForceTension
SelectivityReading every source is infeasible, while skipping one load-bearing definition can invalidate the package.
Formal and operative meaningStandards and schemas provide inspectable definitions, while actual profiles, extensions, and Work can narrow or alter use.
Edition and effectivityA stable name aids reuse, while its meaning or applicability can change across revisions, profiles, configurations, and intervals.
AuthorityPublishers and stewards define bounded schemes or values, while the receiver may need a decision outside their scope.
AccessA source may be meaningful but unavailable, restricted, delayed, or legally unusable for the proposed integration.
AdequacyExisting models reduce construction work, while forcing an inadequate model hides a semantic gap.

SIE.2:4 - Solution

Recover source semantics at the smallest grain that can change the receiving answer. Preserve term, concept, type, relation, schema, model, claim, data item, carrier, identifier, and world-side referent as different questions. Qualify each relied-on premise by source identity, edition/effectivity, authority scope, provenance, access, currentness, and known gaps.

SIE.2:4.1 - Pattern-Use Unfolding

  1. Take the source cut from the use contract. Add another source only when it can change an answer claim, test, loss, or stop condition.
  2. Identify the source asset and carrier. Record publisher or owning System, title or endpoint, profile/module, version or edition, publication and effectivity, retrieval location, and carrier kind. Keep the asset distinct from the concepts and claims it carries.
  3. Recover the local scheme and scope. State the domain, population, lifecycle state, configuration, jurisdiction, or Work context in which the source definitions apply.
  4. Recover exact meanings. For every load-bearing endpoint, record the designation, definition or operative rule, type/relation role, examples and counterexamples, units or codes, and unresolved ambiguity. Use source-local language before normalizing it.
  5. Resolve an identifier for this use. Identify the entry, the kind and grain of entity it can designate, and the restrictions on its use. For an issued identifier, recover the applicable assignment, its authority and its interval. For a designation resolved by a rule, establish that rule and the context in which it picks out an entity. If the sources form or resolve entries differently for this use, compare their languages of designations. When the rules agree, use that agreement and examine the particular bindings. State what remains unknown.
  6. Separate claims, data, and provenance. Record which claim a data item represents, its scope and time, how it was derived, who or what supplied it, and which uncertainty or status accompanies it. Provenance does not make the claim true.
  7. Recover authority and access. Identify who sets the source conventions, who can issue or reassign an identifier, who decides authoritative values and who may approve extensions, grant access or authorize receiving use. Mark unsupported assumptions.
  8. Assess currentness and use adequacy. Compare the source premise with the contract. State whether it is adequate, adequate only under conditions, unresolved, obsolete for this use, inaccessible, or missing.
  9. Request a model that supplies the missing distinction. If the required distinction cannot be expressed in the available source or supplied semantic model, request UseFitSemanticModel@Use; do not hide the gap in a mapping rule.
  10. Record dependencies and next results. Identify the exact definitions, editions, authority facts, and gaps consumed by SIE.4–SIE.10, plus observations that reopen this inventory.

SIE.2:4.2 - Record the Result

Inventory positionRequired content
source identityowning/publishing System, asset or endpoint, profile/module, carrier, location
edition and applicabilityversion/edition, publication, effectivity/configuration/interval, local extension status
local semantic endpointsdesignation, definition or operative rule, type/relation role, scope, examples/counterexamples, units/codes
identifiersentry and applicable syntax, resolution rule and context or assignment and its authority, use restrictions, entity grain, relevant interval and supported or unresolved referent
claims and datasource claim, represented data item, scope/time, uncertainty/status, derivation and provenance
authority and accessmeaning, identifier, value, extension, access, and receiving-use authority scopes
qualificationadequate, conditional, unresolved, obsolete, inaccessible, missing, or model-gap return with reason
dependency and reopenconsuming package rows, known gaps, next result, and source/edition/meaning changes that reopen

SIE.2:4.3 - What Changes in Practice

Mappings are grounded in the recovered source meanings. A later correspondence or transformation can point to exact source-local endpoints and editions, and a failure can return to the owner of the missing meaning, authority, access, or model. An inventory row can be useful even when its disposition is unresolved or inaccessible.

SIE.2:5 - Archetypal Grounding - AP242 and QIF Source Cut

For the AP242/QIF query in SIE.1, the team inventories only source premises that can change the configuration-bound answer.

Source rowQualification for the constructed use
AP242:2025 edition 4Product-definition, configuration/change, and effectivity source for the case. Record the official publication identity and current stage 90.92, “to be revised”. The source owner defines its model; Systems Engineering decides which released configuration applies locally.
local AP242 exchange/profileRecord the exact application protocol/profile, implementation conventions, export version, local extensions, identifiers, and configuration/effectivity fields supplied. The standard title alone does not establish those facts.
QIF sourceRecord the applicable ISO 23952:2020 carrier/profile, plan, characteristic, and result meanings, identifiers, measurement context, status, and local quality authority. A QIF result identifier does not establish AP242 feature identity.
local source recordsRecord export or API occurrence, timestamps, derivation, access, issuer, local configuration or inspection status, and gaps. A reachable file is not automatically current or authorized for review.

The inventory marks an unresolved local AP242 extension used by one feature class. Because its meaning can change the correspondence, the package stops that row and returns to the extension owner. Other rows can continue. If neither AP242 nor QIF can express a required tolerance-state distinction, the inventory requests a qualified UseFitSemanticModel@Use; it does not invent the distinction in the transform.

SIE.2:6 - Bias-Annotation

LensLikely driftRepair
GovernanceCustody or access is mistaken for semantic or value authority.Record each authority scope and the evidence for it separately.
ArchitectureThe inventory mirrors the integration platform rather than governed sources.Identify source assets and meanings independently of the selected realization.
Ontology/EpistemologyTerm, concept, type, relation, identifier, claim, data, and referent collapse into one “field”.Use separate inventory positions and preserve unresolved senses.
PragmaticsExhaustive documentation delays the use without changing it.Inspect only premises that can change an answer, loss, test, or stop.
DidacticsA standards citation is read as proof that the local export conforms or is current.Record the local profile, occurrence, evidence, extension, and effectivity separately.

SIE.2:7 - Conformance Checklist

  • Every included source can change a named contract position.
  • Source asset, carrier, local scheme, semantic endpoint, identifier, claim, data item, and referent remain distinguishable.
  • Edition, profile/module, effectivity/configuration/interval, and local extensions are explicit where load-bearing.
  • Definitions or operative rules include scope and at least one discriminating example or counterexample where ambiguity matters.
  • The source entry, entity grain, relevant interval, restrictions and grounds for resolving it are explicit. For an issued identifier these include the applicable assignment and its authority.
  • Claims retain provenance, scope, time, status, and uncertainty without treating provenance as truth.
  • Meaning, identifier, authoritative-value, extension, access, and receiving-use authorities remain separate.
  • Every row has an adequate, conditional, unresolved, obsolete, inaccessible, missing, or model-gap disposition.
  • Consuming rows and reopen conditions are recoverable.

SIE.2:8 - Common Anti-Patterns and How to Avoid Them

Anti-patternRepair
Data dictionary by column nameAdd source-local definition, scope, edition, units/codes, examples, and authority.
Standards title as implementation evidenceInspect the local profile, export, extension, occurrence, and conformance evidence.
“Same ID format means same object.”Recover each entry’s resolution rule and context or assignment and issuer, and state the supported entity, grain and interval. Use SIE.5 for cross-source identity.
Provenance equals truthKeep derivation and source authority separate from domain truth and receiving acceptance.
Read every sourceStart from the contract and add only action-changing premises.
Patch a model gap in codeReturn the missing semantic-model result before relying on the rule.

SIE.2:9 - Consequences

Mappings become reviewable against exact endpoints, and source changes can be traced to the rows that relied on them. Authority, access, and model gaps appear before implementation. The same inventory can support several direct pattern entries while each use retains its own qualification.

The cost is source-local reading and coordination with publishers, stewards, domain specialists, and access owners. Some attractive automation must wait because the source meaning or applicability is unresolved.

SIE.2:10 - Rationale

When constructing an integration, use the meanings recovered from the source to guide mappings that must preserve them. Source-local recovery also prevents a shared vocabulary from becoming a hidden replacement for source authority. Qualification by use keeps the inventory finite and prevents documentation breadth from substituting for a workable package.

SIE.2:11 - SoTA-Echoing

The best-known line combines terminology work, metadata-registry discipline, provenance, and source-local meaning recovery. The serious default is schema inspection plus organizational folklore. Its defect is not informality alone; it leaves no stable relation among the source claim, edition, authority, and mapping premise. SIE.2 adapts the line into a use-qualified manifest with an explicit inadequate-model return.

Source lineAdopt, adapt, or rejectRole and limit
Current FPF F.0.1 and F.0.2adoptRecover source-local meaning and episteme identity; do not establish a cross-source correspondence or domain truth.
ISO 704:2022adaptDistinguish objects, concepts, definitions and designations with ISO 704. Use the receiving contract to decide which distinctions the integration must preserve.
ISO/IEC 11179-3:2023 and its item-mapping amendmentadaptContribute registry-item identity, versions, definitions, and mapping metadata; no automatic cross-source identity or fitness follows.
PROV-OadaptDistinguishes entities, activities, agents, derivation, revision, invalidation, attribution, and primary source; provenance establishes neither truth nor permission.
schema-only discoveryreject as sufficientStructure and samples can locate questions but cannot replace source-local meaning, edition, authority, and applicability.

Reopen when a source change alters a relied-on meaning, scheme, edition, effectivity, authority, access condition, or provenance chain, or when repeated cases show that an inventory position cannot support the downstream decision.

SIE.2:12 - Relations

  • SIE.1 supplies the receiving use, source cut, answer claims, preserved distinctions, and stop conditions.
  • SIE.3 qualifies an available model for the named use or develops a missing distinction. Request that result when the recovered source model leaves the integration’s model question unsettled.
  • SIE.4, SIE.5, and SIE.6 consume exact endpoint meanings, source claims, identifiers, editions, and authority limits.
  • SIE.7–SIE.10 consume the manifest, provenance, currentness, and gap dispositions relevant to implementation and validation.
  • Domain sources, MDM, access owners, Systems Engineering, Data Engineering, and applications retain their respective meanings, values, permissions, operational results, and decisions.

SIE.2:End

SIE.3 - Construct or Reuse a Semantic Model for a Named Use

Type: Method pattern Status: Stable Normativity: Normative method guidance within SIE; examples are constructed and non-normative.

Primary working result: a UseFitSemanticModel@Use: a reused, extended, or constructed semantic model qualified for the questions and distinctions that its receiving use requires.

SIE.3:1 - Problem Frame

Use this when an integration needs to express a meaning or answer a question and the adequacy of its available models is unsettled. For example, a source describes an inspection requirement, while the receiving query needs to distinguish that requirement from an observation of a particular configured feature.

Start with one question the model must help answer and examples of answers that would count as different. Ask the domain participants to explain those distinctions before choosing an encoding. The first useful result can be confirmation that an existing model is sufficient, with its applicable edition and use conditions.

The object is the semantic model for that use: its concepts, relation meanings, constraints, and relevant commitments. The practical gain is a model whose distinctions can guide correspondence and mapping work. A stronger claim, such as adequacy for additional questions or valid inference in a formal language, needs evidence for those additional conditions.

If the supplied model is qualified for the unchanged use, reuse that result. If the only open question is a correspondence between adequately understood source meanings, use SIE.4. A new integration endpoint alone does not create a model-construction requirement.

SIE.3:2 - Problem

Available models often look adequate because their terms resemble the receiving question. A field named inspection may cover a plan, a requirement, an occurrence, or a result. Mapping every such field to one class can remove the distinction the receiver needs.

The opposite failure is to construct a larger ontology whenever a model question arises. That incurs design and maintenance work even when an existing model can answer the question. Both failures begin before formalization: the required meaning and its useful boundary have not been established.

SIE.3:3 - Forces

ForceTension
ReuseExisting meanings and tools save work, while an unrecognized gap can invalidate the receiving answer.
Domain understandingParticipants know their practice, while familiar words can hide different concepts, grains, or temporal commitments.
ExpressivenessRicher formalization can support useful inference, while its cost and restrictions may exceed the use.
ModularityAn extension can preserve reusable content, while incompatible commitments may require a different model.
MaintenanceConsumers need a stable reference, while the domain and its required questions can change.

SIE.3:4 - Solution

Select or develop only the semantic content needed for the named use. Qualify it through discriminating cases and make its maintained edition accessible to the consumers who will rely on it.

SIE.3:4.1 - Pattern-Use Unfolding

  1. State the questions and answer distinctions. Use competency questions or an equivalent plain description. Name the subject, grain, configuration or interval where relevant, expected answer, and a counterexample. Work with domain participants at a level where they can explain the distinction. Separate a useful model question from a request to choose a storage or diagramming tool.
  2. Recover the available meanings. Use the relevant SIE.2 results or directly supplied source meanings. Inspect candidate models’ definitions, relations, constraints, examples, edition, access, and maintenance conditions where those can affect the use. Source labels alone cannot settle suitability.
  3. Try sufficient reuse. Replay the required questions and counterexamples against an available model. When its content and applicable conditions suffice, return that model and the qualification. This completes the Method. Leave an uncovered question explicit if a permitted narrower use can continue.
  4. Locate the gap. Identify the missing distinction, relation, constraint, or incompatible commitment. Extend a module when the addition can preserve the existing commitments that consumers still use. Construct a different model when reuse or such an extension cannot supply the required content. Keep the reason tied to the gap.
  5. Develop the meaning before encoding it. Define the needed concepts and relations, their domains of application, and the grain or temporal interpretation required by the question. Show examples and counterexamples to domain participants. Preserve a source disagreement that affects use; SIE.4 can establish a qualified correspondence between different meanings.
  6. Choose sufficient formalization. A maintained vocabulary and relation description can be enough for some uses. Select a formal language or profile when exchange, constraints, or inference require its semantics. Check the properties claimed under that choice as well as the domain cases. Repair or qualify a model that passes an encoding check but answers the domain question incorrectly.
  7. Return a maintained, use-qualified model. Identify the edition or stable content, covered questions, material limits, and the access and maintenance arrangement its consumers need. Return its meanings to correspondence or mapping work and its cases and qualifications to validation. A missing authoritative definition can leave one question unresolved while independently supported questions finish.

A small model can express these obligations in one short maintained description. When formalizing the model, obtain the assurance the selected language and use require. Formalization does not change which domain question the model must answer.

SIE.3:4.2 - Record the Result

Result positionContent needed by the receiver
Named useQuestions, expected answer distinctions, and applicable subject, grain, time, or configuration.
Selected modelReused model or developed module, its edition, definitions, relation meanings, and required commitments.
Reuse or development decisionThe adequacy evidence, or the gap that justified an extension or different model.
QualificationCovered cases, counterexamples, limits, unresolved questions, and any selected formal checks.
Continued relianceAccess, maintenance responsibility, relied-on source conditions, and change conditions that can reopen the result.

The result can refer to an existing qualified model instead of reproducing it. Record a reason only where it helps a consumer interpret or rely on the selection.

SIE.3:4.3 - What Changes in Practice

The integrator can explain why the model distinguishes two answers, or why an existing distinction is sufficient. A mapping author receives meanings and cases rather than an unexplained class list. Model construction becomes a response to a demonstrated gap.

SIE.3:5 - Archetypal Grounding

SIE.3:5.1 - Reuse for Provider Availability

The receiving interface returns separately attributed provider quantities. Its questions are “How much is on hand now?” and “How much can this provider promise under its reservation and time-horizon rules?”

An available model distinguishes both measures, their provider, unit, observation time, and relevant horizon. The integrator checks the following cases:

CaseRequired model interpretation
Provider A reports 12 on hand; provider B reports 9 available to promise.Two qualified quantities with distinct measure meanings.
Both values equal 12.Numerical equality does not remove the difference between the measures.
The provider changes the promise horizon.The horizon remains part of the promise meaning used by the receiver.

The model represents these cases and has suitable access and maintenance conditions. The completed result references that edition for the two questions. It supplies no common quantity formed by adding the values; that operation would require a separately justified receiving meaning.

SIE.3:5.2 - Extend an Inspection Model

A constructed product-definition and inspection integration asks: “What observation concerns requirement Q for feature F in configuration R?” The source model already describes the feature and its requirement, but represents no actual observation.

Model contentDevelopment and case
Existing feature and requirementReuse their qualified definitions and configuration applicability.
ObservationAdd a way to represent an observation of the configured feature separately from its plan and the requirement being checked.
Observation relationState which configured feature and applicable requirement it concerns.
Unit and timeExpress the interpretation required for this observation and question.
CounterexamplesA planned inspection is not an observation; an observation of another configuration does not answer this question.

The domain participants confirm those distinctions and identify any unresolved source-specific interpretation. The module can then supply SIE.4 and SIE.7 with the required meanings. In an AP242/QIF installation, its actual profiles, configuration relations, and inspection meanings must come from the qualified source results; the constructed model above is the working example, not a claim about a particular exchange’s conformance.

SIE.3:6 - Bias-Annotation

LensLikely driftRepair
GovernanceOne participant’s preferred vocabulary silently becomes the shared meaning.Obtain the meanings needed by the receiving use and preserve unresolved authority or source disagreement.
ArchitectureA platform choice determines the model’s concepts.State the questions and distinctions before selecting formalization or realization.
Ontology/EpistemologyRequirement, plan, observation, and result collapse because they share a label.Use a counterexample that changes the receiving answer.
PragmaticsA new ontology is built despite adequate reusable content.Try the existing model and finish when the use is supported.
DidacticsA formal diagram appears sufficient without a working example.Show how the model answers the question and excludes its counterexample.

SIE.3:7 - Conformance Checklist

  • The receiving questions and material answer distinctions are recoverable.
  • Available model content is compared with those questions before development is selected.
  • Sufficient reuse can complete the result.
  • Developed content answers an identified gap and preserves relied-on commitments or qualifies the affected use.
  • Domain examples and counterexamples support the claimed scope.
  • Formal checks match the selected encoding and claimed inference or exchange use.
  • The receiver can identify and access the maintained model and its limits.

SIE.3:8 - Common Anti-Patterns and How to Avoid Them

Anti-patternRepair
Model from familiar labelsRecover relation meanings and replay a discriminating question.
Construction as proof of progressReturn adequate existing content when it supports the use.
Hidden repair in a transformation ruleDevelop the missing semantic distinction and give the rule a qualified premise.
Language validity used as domain adequacyCheck the domain answer as well as the selected formal properties.

SIE.3:9 - Consequences

A qualified model makes correspondence and mapping decisions more explicit and reusable. Small integrations can finish with a small model. Extensions expose their commitments to later consumers.

The work costs domain conversation, example construction, and any formal checks the chosen use requires. Some questions remain unresolved until a source owner supplies a needed meaning. Larger scope creates additional content and maintenance obligations.

SIE.3:10 - Architectural Rationale

Questions and counterexamples locate the distinctions that an integration must preserve. Reuse is therefore judged by its contribution to the question; extension is justified by a specific gap. Keeping model content, its maintained edition, its formal encoding, and its instances distinct makes both adequacy and later change easier to assess.

SIE.3:11 - SoTA-Echoing

How can you determine whether an available model is adequate for the receiving questions? For the inspection question in §5.2, the selected starting line is requirements-led model qualification: recover the distinction between requirement, plan, and observation, try the available meanings, and develop only the gap that survives that trial. This adapts LOT and its maintained resources.

A serious alternative for that same unsettled question is to develop the model together with a small knowledge-graph prototype, adapting the ontology-and-graph work described by LOT4KG. The prototype can reveal a missing relation when the receiving query is executed. Compare a bounded prototype with bounded model qualification, rather than charging it for a complete production platform:

Answer to the same inspection-model questionComparable work and useful evidenceChoice and accepted trade-off
Qualify or extend the model before selecting its realizationExamine the required definitions with domain participants and replay the requirement/plan/observation, configuration, unit, and time cases. Keep the model and cases sufficient for that query.Adapt LOT in §4.1.1–5 and §5.2. This settles the semantic distinction without choosing graph encoding or query machinery. It supplies no evidence that an executable mapping or query is correct; SIE.7 and SIE.10 still need that evidence for their own claims.
Qualify the model through a small graph and executable queryExamine the same definitions and cases, then encode representative instances and the query. This adds encoding and execution work but can expose errors that a prose-only model trial misses.Adapt the LOT4KG route when execution can settle an uncertainty material to model adequacy, especially when graph realization is already selected. In §5.2, the first unresolved issue is what counts as an observation; executing a query over a class that also includes plans cannot settle that domain meaning. The model-first route is selected for that issue, accepting deferred execution evidence.

The comparison is qualitative and scoped to the same questions and counterexamples. A prototype’s additional effort earns its place when it can change the qualification. Neither route can replace domain meaning with successful execution.

The remaining contributions constrain that choice:

Source and comparison roleOperative move and limit
LOT supplies the selected requirements, development, publication, and maintenance line.Adopt domain questions and participant validation; adapt §4.1.3 and §4.1.7 so sufficient reuse can finish and the receiver can rely on a maintained model. The source does not decide local meanings or establish this model’s adequacy.
LOT4KG supplies the coupled ontology/graph alternative.Adapt its separation of ontology work and graph construction to the comparison above; reject treating graph construction as the only way to qualify a model. Its description explains how to try this alternative. A claim that it outperforms model-first qualification needs comparative evidence.
OWL 2 Overview supplies language and profile choices when formal semantics matter.Adapt §4.1.6: check the properties claimed for the chosen language as well as the domain cases. Encoding validity cannot replace the model-adequacy question.
The public ISO/IEC 21838-1 scope supplies a possible top-level basis.Adapt §4.1.2/6 only when that basis contributes needed coherence. It establishes neither a universal upper-ontology requirement nor local maintenance and versioning rules.

Reopen the comparison if one required answer depends on a selected query or inference behavior that the model-only trial cannot settle, if a bounded prototype exposes a missed distinction, or if an available model can now answer the same cases with less qualification work. Return only to the affected question and §4.1.2–6. A qualified model for an unchanged use remains the sufficient direct result in §4.1.3.

SIE.3:12 - Relations

  • SIE.1 supplies the receiving question, preserved distinctions, and permitted scope.
  • SIE.2 supplies source meanings and identifies model gaps.
  • SIE.4 uses model meanings to establish qualified correspondences; SIE.7 uses them in executable mappings.
  • SIE.10 validates the integration’s claimed receiving result using the relevant model qualification.
  • SIE.11 follows a changed model premise to affected uses. Use SIE.12 when independently governed participants depend on shared semantic modules and need arrangements for maintaining them.
  • FPF terminology, kind, relation, and evidence guidance constrains the corresponding model claims; domain participants supply the problem-specific meanings.

SIE.3:End

SIE.4 - Judge Cross-Source Correspondences and Their Permitted Uses

Type: Method pattern Status: Stable Normativity: Normative method guidance within SIE; examples are constructed and non-normative.

Primary working result: a QualifiedCorrespondenceSet@Use whose rows identify exact source-local endpoints, relation or incompatibility, orientation, bounded use, permitted loss, justification and evidence, source versions, counterexamples, confidence where meaningful, and accepted, rejected, unresolved, or incompatible disposition.

SIE.4:1 - Problem Frame

Use this when two or more governed sources contain concepts, types, relations, fields, codes, model elements, or claims that appear to match and a receiving use needs their relation made explicit. Typical triggers are a shared label, a crosswalk, an automated matcher result, a spreadsheet of “equivalences”, or a model-to-model mapping whose semantic premise has never been judged.

For one cross-source correspondence row and its named use, recover both endpoint senses and ask which direct relation, difference, or incompatibility is supported. The first result is a set that preserves accepted, rejected, unresolved, and incompatible rows rather than forcing every candidate into an equivalence.

The payoff is a defensible semantic premise for identity work, claim composition, executable mappings, and validation. Do not use SIE.4 to construct a missing semantic model, decide cross-source identity, define transformation code, or choose the authoritative value. A local relation inside one governed source remains with its source owner unless the cross-source use makes it an integration premise.

SIE.4:2 - Problem

Correspondence candidates are cheap. Labels can be normalized, lexical similarity scored, hierarchies compared, and model structures aligned. Yet “similar”, “related”, “narrower”, “same field name”, and “safe to substitute here” answer different questions. A row can state a relation correctly even when using it would lose a distinction the receiver needs.

When candidate generation and qualification collapse, downstream mapping code inherits an unstated ontology and loss policy. Counterexamples are discarded as data-quality defects, source versions disappear, and a reviewer cannot tell whether the relation itself or only its use is unsupported.

SIE.4:3 - Forces

ForceTension
AutomationMatchers can surface many candidates, while their scores do not establish relation truth or permitted use.
ReuseA general crosswalk is attractive, while relation adequacy can change with receiver, grain, interval, and accepted loss.
PrecisionNaming the relation the evidence supports avoids claiming more, even when the sources do not fully characterize it.
CoveragePressure favors filling every row, while unresolved and incompatible rows can be the most decision-useful result.
DirectionTransformation needs an orientation, while many conceptual relations are not symmetric or safely reversible.
VersioningStable mapping identifiers aid reuse, while endpoint meaning can change across source editions and profiles.

SIE.4:4 - Solution

Separate candidate discovery, direct relation judgment, and bounded-use qualification. For each row, identify exact source-local endpoints, state the relation or incompatibility and orientation, justify it with evidence and counterexamples, then decide whether that relation may support the named use under a stated loss boundary. Keep the direct relation and its use qualification independently inspectable.

SIE.4:4.1 - Pattern-Use Unfolding

  1. Take the question from the contract. State the receiving answer and why this endpoint relation can change it.
  2. Bind exact endpoints. Reference the SIE.2 source rows, schemes, definitions, editions, profiles, effectivity, units, codes, and local extensions. Do not map labels without their senses.
  3. Generate candidates without promotion. Lexical, structural, instance, expert, historical, or matcher evidence may nominate a row. Record the candidate source and score where useful, but do not treat nomination as acceptance.
  4. State the direct relation or difference. Use the narrowest warranted relation vocabulary. State direction and whether the inverse, symmetry, or transitivity is supported. A pair may be excluded from a join while the relation remains unknown. To assert that an assignment is absent, use evidence that excludes it for this configuration, such as a complete governing plan.
  5. Test examples and counterexamples. Include instances or cases that should satisfy the relation and cases that distinguish endpoints, including version, unit, code, granularity, lifecycle, and authority differences.
  6. Qualify the receiving use. State which substitution, comparison, join, navigation, or transformation the row permits, what semantic loss it introduces, and which uses remain forbidden.
  7. Preserve evidence and authority. Record justification, evidence source, reviewer or domain authority where required, uncertainty or confidence, and the owner of any unresolved domain judgment.
  8. Assign a row disposition. Use accepted-for-use, accepted-with-loss, rejected, unresolved, or incompatible. A row can state a true broader/narrower relation yet be rejected for this use.
  9. State dependencies and tests. Name whether SIE.5, SIE.6, or SIE.7 consumes the row, plus a test or observation that reopens it.

SIE.4:4.2 - Record the Result

Correspondence positionRequired content
row identity and usestable row identifier, receiver/use, consuming result
source endpointsource, scheme/model, exact sense, edition/profile/effectivity, identifier
target endpointsource, scheme/model, exact sense, edition/profile/effectivity, identifier
direct relationrelation or explicit difference/incompatibility, orientation, inverse/symmetry/transitivity qualification
use qualificationpermitted operation, accepted loss, forbidden reuse, conditions
warrantcandidate origin, justification, evidence, authority, uncertainty/confidence where meaningful
challengepositive examples, counterexamples, negative/unlike cases
disposition and continuationaccepted-for-use, accepted-with-loss, rejected, unresolved, incompatible; downstream reference and reopen condition

SIE.4:4.3 - What Changes in Practice

The team stops treating a mapping spreadsheet as a bag of equalities. A matcher result becomes a candidate; a domain judgment becomes a relation warrant; and a receiving-use decision states what the relation may safely support. Unresolved and incompatible rows remain visible to the interface and tests.

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-99Only the shared local label supports this candidate. The accessible plan excerpt supplies no assignment at R/E.Exclude the pair from the join and return the link as unresolved. If the complete governing plan for R/E contains no such assignment, return an established non-match for that configuration.
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.

SIE.4:6 - Bias-Annotation

LensLikely driftRepair
GovernanceA matcher or integrator silently becomes the domain relation authority.Record the warrant, decision scope, and required domain authority for each accepted row.
ArchitectureAvailable mapping technology limits the relation vocabulary.State the semantic relation first; choose its carrier later.
Ontology/EpistemologySimilarity, correlation, broader/narrower relation, and equivalence collapse.Use the narrowest supported relation and preserve uncertainty and counterexamples.
PragmaticsEvery possible endpoint pair is reviewed.Restrict rows to relations that can change the contract or a dependent result.
DidacticsDirection arrows are read as a mandatory processing order.Explain orientation as relation or transformation meaning, not lifecycle sequence.

SIE.4:7 - Conformance Checklist

  • Every row serves a named receiving use and consuming result.
  • Both endpoints reference exact source-local senses and applicable editions/profiles.
  • Candidate generation is distinguishable from relation judgment.
  • The direct relation, difference, or incompatibility uses the narrowest warranted kind and states orientation.
  • Inverse, symmetry, and transitivity are not inferred without support.
  • Positive examples and discriminating counterexamples are present where load-bearing.
  • Permitted operation, semantic loss, conditions, and forbidden reuse are explicit.
  • Evidence, uncertainty/confidence, and decision authority are inspectable.
  • Rejected, unresolved, and incompatible rows remain available to downstream interfaces and tests.
  • The set claims neither cross-source identity nor executable transformation by implication.

SIE.4:8 - Common Anti-Patterns and How to Avoid Them

Anti-patternRepair
Same label, therefore same meaningRecover endpoint senses and test counterexamples.
Matcher score as truthTreat the score as candidate evidence; obtain a relation warrant and use decision.
Every relation is sameAsDistinguish identity, equivalence, broader/narrower, related, concerns, transforms-to, difference, and incompatibility.
One global crosswalkQualify rows by use, source editions, loss, and forbidden reuse.
Symmetric spreadsheet mappingState orientation and test whether the inverse is supported.
Delete failed rowsRetain rejected, unresolved, and incompatible dispositions for receiver and validation behavior.

SIE.4:9 - Consequences

The correspondence set gives mapping and interface work explicit semantic premises and preserves negative results. It makes version and loss dependencies visible and allows a narrow use to proceed while other rows remain unresolved.

The cost is row-level judgment and counterexample work. Automated matchers remain useful for candidate discovery but cannot close the relation or its receiving-use qualification alone.

SIE.4:10 - Rationale

A direct relation and permission to use that relation answer different questions. Keeping them separate allows a true relation to be rejected for a loss-sensitive use and a qualified narrow relation to support one operation without being promoted globally.

SIE.4:11 - SoTA-Echoing

The best-known line combines explicit relation vocabularies, mapping metadata, alignment evaluation, and direct Bridge truth. The serious default is a two-column crosswalk plus confidence score. Its defect is that it hides endpoint senses, relation algebra, bounded-use loss, and counterexamples. SIE.4 adapts current mapping practice into a set that records negative dispositions and qualifies each relation for its receiving use.

Source lineAdopt, adapt, or rejectRole and limit
Current FPF F.9adoptGoverns each direct cross-context Bridge and separate bounded-use claim; a package row must not replace Bridge truth.
SKOS ReferenceadaptSupplies distinct mapping relation forms and cautions through their semantics; SKOS does not prove a candidate relation or authorize substitution.
SSSOM 1.0adaptContributes inspectable subjects, predicates, objects, provenance, justification, confidence, and source versions; metadata completeness is not relation truth.
OAEI 2025 resultsadaptDemonstrate task- and track-dependent alignment evaluation; benchmark performance does not decide a local row.
label-only or score-only crosswalkreject as sufficientIt can nominate candidates but cannot establish endpoint senses, relation, permitted loss, or authority.

Reopen when an endpoint meaning or edition changes, a counterexample defeats the relation or use qualification, the receiver’s loss boundary changes, or a better relation vocabulary materially changes action.

SIE.4:12 - Relations

  • SIE.2 supplies exact endpoint senses, editions, profiles, authority limits, and model gaps.
  • SIE.3 is a conditional return when available models cannot express a required endpoint distinction.
  • SIE.5 consumes rows that expose a load-bearing cross-source identity question.
  • SIE.6 uses correspondences to decide which source claims are comparable or composable without erasing scope or conflict.
  • SIE.7 consumes only accepted rows under their stated use and loss conditions; it adds executable transformation semantics.
  • SIE.10 tests correspondence truth and use qualification independently from mapping execution.

SIE.4:End

SIE.5 - Resolve Cross-Source Identity without Erasing Identifier Authority

Type: Method pattern Status: Stable Normativity: Normative method guidance within SIE; examples are constructed and non-normative.

Primary working result: a CrossSourceIdentityDisposition@Use that states, for each load-bearing endpoint pair or set, the required entity grain and interval, identity-related disposition, the source entries, the rules and contexts or assignments and issuers that resolve them, evidence, authority boundary, unresolved cases, and the exact mappings, claim compositions, interfaces, and tests that may consume it.

SIE.5:1 - Problem Frame

Use this when an integration needs to decide whether records or identifiers from different sources concern the same entity, a part, a version, a variant, an alternate description, a family, or different or unresolved entities. The recognizable failure is a join, merged key, or sameAs assertion that makes identifiers appear unified while erasing their issuers, grains, intervals, and authority.

For one bounded cross-source identity question, state the entity grain and time or effectivity interval at which sameness matters for the named use. The first result is a disposition that downstream work can inspect and challenge without replacing source identifiers or master-data authority.

The payoff is that the integration can join only warranted cases, identify which branches remain unresolved, and preserve source trace. Do not use SIE.5 to create identifiers, choose enterprise master identity or survivorship, decide authoritative values, or prove a source claim true. Those decisions remain with identifier owners, MDM, or the direct domain authority.

SIE.5:2 - Problem

The same real-world item can carry manufacturer, supplier, enterprise, lot, serial, package, event, and temporary process identifiers. Conversely, the same character string can be reused by different issuers or at different times. Version, configuration, part-whole, and alternate-description relations can be mistaken for identity because they support some joins.

If an integration collapses those distinctions, the merged record no longer shows which source made each claim, the identifier it used, or the time and issuer rules that qualify that use. Contradictory events appear to concern one thing without evidence, and a master key silently becomes a domain decision.

SIE.5:3 - Forces

ForceTension
JoinabilityA common key makes computation easy, while premature merging can create false identity and irreversible provenance loss.
GrainReceivers want one “item”, while wafer, die, device, package, lot, feature, version, and event answer different questions.
Time and effectivityIdentity may be stable across one interval, while reuse, replacement, split, merge, and revision change the warranted claim.
AuthorityIdentifier issuers and master-data stewards govern different schemes and decisions; crosswalk custody transfers neither authority.
Incomplete evidenceA bounded decision is needed, while some pairs must remain unresolved without blocking independent rows.
ReuseA disposition can help several mappings, while its grain, interval, and use boundary prevent blanket equivalence.

SIE.5:4 - Solution

Frame identity as a source-qualified, grain- and interval-specific disposition for one receiving use. Preserve every source identifier and the applicable context or assignment, including its issuer when it was issued. Compare the entity criteria, relation evidence, version/effectivity, and authoritative decisions that matter. Return same, different, part, version, variant, alternate-description, family, or unresolved only at the precision supported; do not force every useful relation into identity.

SIE.5:4.1 - Pattern-Use Unfolding

  1. Name the receiving identity question. State which mapping, claim composition, query, or decision needs an identity premise and what a wrong merge or split would change.
  2. Fix entity grain and interval. Name the relevant individual or occurrence kind, part-whole level, version/configuration, lifecycle state, jurisdiction or organization, and time/effectivity interval.
  3. Resolve each source entry. Use SIE.2 to establish what each entry can designate. Recover its assignment and issuing authority when it was issued, or the rule and context used to interpret it. Retain the applicable syntax, restrictions, source edition and provenance. If the evidence leaves several candidates or fails to identify one, record that outcome.
  4. Separate candidate relation kinds. Consider same individual at the stated grain, different individuals, part/whole, earlier/later version or specialization, variant, alternate description, an individual satisfying a type criterion, or membership in a declared product family. When several readings still fit, check which trace or decision differs between them. Return an answer common to every admissible reading at the requested grain. Preserve any finer relation still in doubt.
  5. Collect discriminating evidence. Use issuer records, source assertions, configuration/effectivity, provenance, physical or domain characteristics, event histories, and counterexamples. A shared string or co-occurrence is only candidate evidence.
  6. Recover authority. Identify who may bind a source identifier, govern the master identity, decide authoritative values or establish the domain relation. SIE records the disposition for its stated use under those authorities.
  7. Assign the narrowest warranted disposition. State conditions, confidence or uncertainty where meaningful, rejected alternatives, and unresolved evidence. Preserve source IDs even for accepted same-entity rows.
  8. Link consumers to the identity disposition. Reference the disposition from every mapping, claim composition, interface row, and identity test that relies on it. Never copy only the merged key.
  9. Test difficult cases and reopen. Include identifier reuse, split/merge, version/configuration change, part-whole confusion, contradictory source events, and absent-link cases. State the source or observation change that reopens the row.

SIE.5:4.2 - Record the Result

Identity positionRequired content
identity question and usereceiver, dependent action, wrong-merge/wrong-split consequence
entity boundarykind and grain, part-whole level, version/configuration, interval/effectivity, relevant context
source identifierseach source entry, the supported referent, remaining candidates or unresolved designation, the relevant rules and context or the assignment and its issuer, restrictions, edition and provenance
candidate relationssame, different, part, version/specialization, variant, alternate description, family, unresolved alternatives
warrantevidence, counterevidence, counterexamples, uncertainty/confidence, rejected alternatives
authorityscheme-local, master-data, domain, and receiving-decision scopes
dispositionnarrowest warranted relation or unresolved result, conditions, source-ID preservation rule
downstream and reopenmapping/composition/interface/test references and the change or observation that reopens the disposition

SIE.5:4.3 - What Changes in Practice

The integration stops minting a common key as proof of identity. Every load-bearing join points to a disposition with grain, interval, source identifiers, evidence, and authority. Unresolved identity becomes an explicit interface and validation branch instead of a row silently dropped or merged.

SIE.5:5 - Archetypal Grounding - Semiconductor Recall Trace

A recall-triage query crosses a wafer identifier from a fabrication source, die coordinates, device serials, package identifiers, supplier lot identifiers, GS1 event identifiers, and an enterprise material master. The receiving question is whether a shipped device can be traced to an affected fabrication lot.

Endpoint questionConstructed disposition
wafer W-204 and supplier lot L-88not identity; the supplier record asserts that the wafer is a member/output associated with the lot under a bounded process interval. Preserve both identifiers and relation provenance.
die coordinate (x17,y9) on wafer W-204 and device serial D-771Suppose the packaging record shows that this die was incorporated in the serialized device. Trace the die as a constituent of that device for the recorded interval. A serial assigned to the singulated die itself can instead identify the same die as the wafer coordinate when the designation rule or identifiable context establishes that referent. In either case retain both source identifiers, their applicable intervals and the assignment, issuer or context that establishes each designation.
device serial D-771 and package code P-55unresolved because the package identifier is reused after rework and the event history lacks effectivity. Keep the exact package history open. Test whether this uncertainty changes the lot-level answer.
enterprise material master M-12 and device serial D-771The master record describes a product class and carries the enterprise attributes it governs. To classify the particular device, establish that it meets the class criterion. Membership in a catalogue family would require the catalogue’s own grouping rule. The master and the device each retain their identity.
GS1 event E-901 and device D-771event and object are different entities; the event may concern the device. Never merge their identifiers.

Tests cover reused package identifiers, a die split/merge error, contradictory supplier events, a missing cross-enterprise link, and a later correction. If the records admit at least one package history and every such history traces the shipped device to the affected lot, the interface can return that lot finding while keeping the P-55 history unresolved. If an admissible history leads to an unaffected lot, obtain the rework or effectivity evidence that distinguishes them before attributing the device to the affected lot. MDM or the domain steward may later decide a master identity; SIE.5 has not done so.

SIE.5:6 - Bias-Annotation

LensLikely driftRepair
GovernanceThe integration registry becomes the de facto master-data authority.State the bounded disposition and retain MDM/domain decision ownership.
ArchitectureOne canonical key is required because the platform prefers it.Carry a surrogate technical key only with source IDs and the identity disposition it indexes.
Ontology/EpistemologySame individual, part, version, variant, alternate, and family relations collapse.Fix grain and interval, then choose the narrowest warranted relation.
PragmaticsEvery identifier pair receives a costly adjudication.Decide only pairs that are load-bearing for the receiving use; leave independent rows untouched.
Didactics“Same” is read as timeless universal identity.Display conditions, interval/effectivity, scheme, and forbidden reuse beside the disposition.

SIE.5:7 - Conformance Checklist

  • The receiving action and wrong-merge/wrong-split consequence are named.
  • Entity kind, grain, part-whole level, version/configuration, and interval/effectivity are explicit.
  • Each entry can be traced to its source and edition. The rule and context or the assignment and its issuer, the restrictions and the available evidence support the stated result, including an unresolved result.
  • Useful non-identity relations are not compressed into a boolean same/different field.
  • Shared strings, co-occurrence, and crosswalk membership are treated only as candidate evidence.
  • Evidence, counterevidence, counterexamples, and uncertainty are inspectable.
  • Scheme-local, master-data, domain, and receiving-decision authority scopes remain separate.
  • Accepted same-entity rows do not delete source identifiers.
  • Every dependent mapping, composition, interface, and test references the disposition.
  • Reuse, split/merge, version/configuration, part-whole, contradiction, and absent-link cases are tested where applicable.

SIE.5:8 - Common Anti-Patterns and How to Avoid Them

Anti-patternRepair
Same string, same entityResolve each entry under its own assignment or contextual rule, then compare the entities at the required grain and interval using evidence for the claimed relation.
Universal sameAsUse the narrowest relation and record unresolved or different cases.
Master key by integration fiatReturn master-identity and survivorship decisions to their authority.
Version equals objectState whether the use concerns one continuing entity, a version-specific configuration, or a relation among them.
Part joined as wholeFix the entity grain and preserve part-whole relations explicitly.
Drop unresolved rowsExpose them as interface and validation branches with dependent actions.

SIE.5:9 - Consequences

The package can join warranted identities without losing source trace and can stop only the branches that depend on unresolved identity. Corrective source or steward decisions can be replayed against explicit consumers. The method also reveals when the useful relation is part, version, membership, or event participation rather than identity.

The cost is domain evidence and authority work. Some convenient global keys remain technical indexes rather than semantic truths, and some desired traces return incomplete.

SIE.5:10 - Rationale

A formation rule determines whether an identifier is well formed. For each entry, recover what its source establishes under the applicable rule, context or assignment. Then ask what the evidence establishes about the relation at the required grain and interval. A record of reassignment can link two entries to the same entity before its serial number is known. Where the evidence permits several identities, preserve those alternatives. Retaining the source entries allows the engineer to reconsider the result as new evidence appears. Master-data and domain decisions remain with their responsible authorities.

SIE.5:11 - SoTA-Echoing

The best-known line combines explicit identifier ownership and restrictions, provenance-qualified alternate/specialization relations, and domain traceability practice. The serious default is entity resolution that optimizes a match score or golden record. The problem arises when the score or merged record obscures grain, issuer, interval or decision authority. SIE.5 uses these contributions to return a bounded disposition for the work that relies on identity.

Source lineAdopt, adapt, or rejectRole and limit
Current FPF identity and relation lawadoptKeeps identity and direct relations as explicit claims; generic law does not decide a domain pair.
ISO 8000-115:2024adaptContributes identifier owner, use restriction, semantics, and resolution inputs; excludes identifier creation, query/response syntax, and resolution method and does not decide equivalence.
PROV-OadaptSupplies specialization, alternates, derivation, attribution, revision, and invalidation relations useful to evidence; provenance relations are not blanket identity.
SEMI traceability standards and GS1 EPCIS 2.0.1adaptSupply semiconductor and event-based identity/traceability probes; scheme use does not create enterprise master identity or authorize recall.
golden-record or score-only mergingreject as sufficientIt may support candidate generation or a steward decision. Preserve source identifiers, relation kinds and authority.

Reopen the affected dispositions when an issuer reassigns one code, or when a change to a formation or resolution rule alters which entries a query can accept or resolve. New event or configuration evidence, a changed grain or interval, and repeated failures to express an action-changing relation can also reopen the result.

SIE.5:12 - Relations

  • SIE.1 supplies the receiving action, identity-sensitive answer claims, loss boundary, tests, and stop.
  • SIE.2 supplies the source entries with the contexts for their rules or the issuers of their assignments, restrictions, source claims, editions, provenance and authority gaps.
  • SIE.4 may expose an identity question but does not answer it merely by accepting a semantic correspondence.
  • SIE.6 consumes identity dispositions when composing claims about the same bounded entity; it preserves contradictory claims separately.
  • SIE.7 and SIE.9 reference dispositions rather than copying only merged keys.
  • SIE.10 tests every load-bearing identity premise. MDM and domain authorities retain master identity, authoritative values, and action.

SIE.5:End

SIE.6 - Fuse Source-Qualified Claims without Erasing Conflict

Type: Method pattern Status: Stable Normativity: Normative method guidance within SIE; examples are constructed and non-normative.

Primary working result: a SourceQualifiedClaimFusion@Use that preserves each source claim, subject and any relied-on identity premise, scope, interval, authority, uncertainty, derivation, and relation to other claims, then returns a qualified view, explicit conflict, non-comparability, or unresolved result for one receiving use.

SIE.6:1 - Problem Frame

Use this when a receiving answer must combine claims from separately governed sources and a simple union, priority rule, average, overwrite, or “golden record” would hide differences in meaning, subject, time, authority, or uncertainty. The recognizable failure is one clean value whose provenance can be displayed but whose conflict or non-comparability can no longer be recovered.

For one receiving question, state the source claims and the subject relation it requires. The first result is either a qualified view with its derivation or a conflict, non-comparability or unresolved branch.

The receiver can interpret the answer and its grounds. Do not use SIE.6 to decide domain truth, authoritative value, survivorship, risk acceptance, or action. The authorized domain or receiving participant may use the composition to choose. Preserve the basis for that choice.

SIE.6:2 - Problem

Claims that share a field name can concern different concepts, entities, grains, intervals, or authority scopes. Claims that do concern the same entity can disagree without either being malformed. A timestamp does not settle whether one claim supersedes another; a source rank does not explain why the rank applies; and an average can be meaningless across different measurement definitions.

If composition silently collapses these differences, later validation can test only the fused value. It cannot test the losing claim, the identity premise, the conflict rule, or the receiver’s permitted use. Provenance survives as a list of sources but no longer constrains meaning.

SIE.6:3 - Forces

ForceTension
SimplicityReceivers may prefer one view even when the source claims warrant several qualified rows or an explicit conflict.
AuthoritySome sources are authoritative for bounded claims, while no source may own the whole receiving question.
TimeNewer claims may supersede older ones, while differing intervals, effectivity, or observation times can make them jointly informative.
IdentityComposition needs a subject relation, while an unresolved identity premise must stop only the dependent branch.
UncertaintyQuantification can support comparison, while unlike confidence, status, or evidence forms should not be normalized without warrant.
PerformancePrecomputed canonical values are convenient, while preserving source-qualified alternatives and derivation costs storage and query work.

SIE.6:4 - Solution

Compose claims only after their meanings, subjects, scopes, intervals, authority, uncertainty, and provenance are explicit. Classify the relation among claims before applying a rule. Preserve the source claims and any relied-on identity premises in the result. Return a qualified view only under a stated rule and use boundary; otherwise return conflict, non-comparability, or unresolved.

SIE.6:4.1 - Pattern-Use Unfolding

  1. Name the receiving question and action. State what the composed answer may change and which outcomes are acceptable: one qualified row, several rows, conflict, non-comparability, unresolved, or stop.
  2. Identify the source claims. Reference SIE.2 rows and SIE.4 correspondences. Record each proposition or data-derived claim, scope, interval/effectivity, units, status, uncertainty, derivation, source, and authority.
  3. Bind the subject relation needed by the use. Reference SIE.5 when composition depends on claims concerning the same entity. For separately attributed claims about distinct subjects, preserve their subjects and attribution. Keep an explanation of unused identity only when it affects interpretation or later reliance. A correspondence alone does not establish subject identity.
  4. Test comparability. Decide whether claims use compatible concepts, subjects, grains, units, intervals, and observation/decision roles. Preserve non-comparability as a result.
  5. Classify the claim relation. Distinguish compatible conjunction, refinement, overlap, duplication, supersession under a justified rule, contradiction, non-comparability, and unresolved relation.
  6. Choose a bounded composition rule. Examples include retaining all qualified claims, selecting one claim under an explicit domain authority/effectivity rule, deriving a new claim through a stated calculation, or returning conflict. State rejected alternatives and semantic loss.
  7. Construct the qualified output. Include the source claims or stable references, applied rule, any relied-on identity premise, derived value if any, provenance/trace, authority boundary, uncertainty, conflict/non-comparability status, and permitted receiving use.
  8. Expose failure and challenge. Define missing-source, stale-source, unresolved-identity, incompatible-unit, contradictory-authority, and unsupported-default branches. Do not convert them into null or a chosen value without the contract’s permission.
  9. State downstream and reopen conditions. Identify mappings and interfaces that consume the composition and the source, identity, rule, authority, or use change that reopens it.

SIE.6:4.2 - Record the Result

Composition positionRequired content
receiving usequestion, action changed, acceptable output branches
source claimspropositions or data claims, meanings, subjects, scopes, intervals/effectivity, units, status, uncertainty, source and derivation
identity premisereferenced SIE.5 disposition when composition relies on identity; an explanation of unused identity only when it affects interpretation or later reliance
comparabilitycompatible dimensions and any difference that prevents comparison
claim relationconjunction, refinement, overlap, duplicate, qualified supersession, contradiction, non-comparability, unresolved
composition rulerule, authority/evidence basis, conditions, rejected alternatives, semantic loss
outputqualified view or explicit conflict/non-comparability/unresolved result, provenance/trace, permitted use
downstream and reopenmapping/interface references, failure branches, changes that reopen the composition

SIE.6:4.3 - What Changes in Practice

The team stops treating a canonical value as the natural output of integration. A receiver can see why claims were combined, retained separately, or stopped, and can return to the source, identity, authority, or rule that changes the answer.

SIE.6:5 - Archetypal Grounding - Provider Availability Claims

Two providers expose availability for the same buyer-recognized product family. Provider A returns onHand = 12 at 10:00; Provider B returns availableToPromise = 9 at 10:02. A purchasing integration initially proposes a single available = 21 value.

The source inventory shows that on hand is current physical stock before reservations, while available to promise is a provider-governed commitment quantity after its own reservation and horizon rules. The values are not additive and are not globally equivalent. A product-family correspondence exists, but individual inventory objects are not asserted identical.

Claim relation questionConstructed result
Can the two values be summed?non-comparable for summation because definitions, allocation rules, and authority scopes differ
Can both support a “which provider can satisfy quantity 8 now?” query?conditionally comparable only after the contract accepts Provider A’s additional reservation check and Provider B’s promise horizon; retain separate rows
What if Provider A reports 12 and a later status reports 4?classify by source occurrence, observation interval, and justified supersession rule; retain both claims and derivation rather than overwriting silently
What if product identity is unresolved?retain the SIE.5 alternatives. If there are admissible bindings and all of them give the same answer to the buyer’s question, return it with the identity limit. Withhold an individual match or recommendation that changes with the binding
What if one API times out?return available source-qualified rows plus an incomplete-result flag if the contract permits; never substitute zero

The interface can return two qualified provider rows, explicit non-comparability for arithmetic aggregation, and a missing-source branch. Purchasing owns supplier choice and risk acceptance.

SIE.6:6 - Bias-Annotation

LensLikely driftRepair
GovernanceA source priority table silently decides truth or business action.Name the authority and claim scope for every selection or supersession rule.
ArchitectureThe target schema requires one value and erases alternatives.Change the output shape or expose conflict/non-comparability as first-class branches.
Ontology/EpistemologyData values, claims, facts, and decisions collapse.Record propositions, scope, uncertainty, derivation, and receiver decision separately.
PragmaticsEvery disagreement becomes an elaborate dispute.Classify only relations that can change the receiving answer; retain independent claims without forced comparison.
Didactics“Fusion” is read as merge or averaging.Show examples where the correct fusion is a qualified set, conflict, or non-comparability.

SIE.6:7 - Conformance Checklist

  • The receiving question and every allowed output branch are explicit.
  • Source claims retain meaning, subject, scope, interval/effectivity, units, status, uncertainty, source, and derivation.
  • Every load-bearing subject identity premise is referenced and tested.
  • Comparability is judged before aggregation or selection.
  • Compatible, refining, overlapping, duplicate, superseding, contradictory, non-comparable, and unresolved relations are distinguishable.
  • A composition rule states its authority/evidence basis, conditions, rejected alternatives, and loss.
  • Source claims remain recoverable from the output.
  • Missing, stale, unresolved-identity, incompatible-unit, contradictory-authority, and default branches are explicit where applicable.
  • The result does not claim domain truth, authoritative value, preference, authorization, or action beyond its source and receiver boundaries.

SIE.6:8 - Common Anti-Patterns and How to Avoid Them

Anti-patternRepair
Last write winsState why time establishes supersession for this claim and interval; otherwise retain both.
Trusted source always winsName the scope of the source’s authority and preserve losing claims and conflict.
Average the valuesEstablish compatible meaning, subject, unit, interval, and aggregation semantics first.
Null means zero or absentPreserve missing, unavailable, unknown, not applicable, and zero as distinct branches.
Provenance after fusionKeep source claims and derivation as inputs to the composition, not decoration on the result.
One canonical factReturn a qualified view only when the use and authority rule warrant it; otherwise return plural claims or conflict.

SIE.6:9 - Consequences

Receivers obtain explainable views and conflict branches. Corrections can target the source claim, identity premise, composition rule, or receiving use without reconstructing an opaque golden record. Different receiving uses can justify different bounded views of the same preserved claims.

The cost is richer output and explicit rule ownership. Some applications must handle plural, incomplete, or conflicting results instead of one scalar value.

SIE.6:10 - Rationale

A source claim asserts something about a subject within a stated scope. Composition is a new derivation whose premises and authority must remain inspectable. Preserving the inputs is what makes conflict, correction, and changed-use replay possible.

SIE.6:11 - SoTA-Echoing

The best-known line combines claim individuation, provenance, authority-aware data integration, and explicit uncertainty. The serious default is master-record survivorship or source ranking. Those Methods can be valid under an authorized MDM use, but they are defective as a universal semantic-integration default because they hide non-comparability and transfer authority. SIE.6 adapts the line by making the qualified composition or explicit conflict the domain result.

Source lineAdopt, adapt, or rejectRole and limit
Current FPF C.2.1adoptKeeps claims as distinct representational objects; SIE supplies the cross-source use composition.
Current FPF A.10adoptGoverns claim-bound evidence and provenance reliance; evidence law does not choose the domain truth or action.
PROV-OadaptSupports derivation, attribution, revision, and invalidation traces; provenance alone establishes no truth, priority, or comparability.
MDM survivorship and golden-record practiceadapt only under direct authorityMay supply an authoritative-value result for a bounded domain; SIE preserves its source and scope rather than generalizing it.
last-write, average, or global source-rank defaultsreject as universalEach may be a justified local rule, but none is semantically safe without compatible claims and authority.

Reopen when a source claim, identity premise, authority rule, interval, uncertainty model, or receiving use changes, or when representative conflict cases cannot be expressed without hiding action-changing information.

SIE.6:12 - Relations

  • SIE.2 supplies source claims, meanings, editions, authority, provenance, currentness, and gaps.
  • SIE.4 supplies the qualified correspondences needed to compare claim predicates or values.
  • SIE.5 supplies load-bearing subject identity dispositions; claim conflict does not alter those identities by itself.
  • SIE.7 may implement the qualified composition rule but must preserve its branches and trace.
  • SIE.9 exposes qualified views, plural claims, conflict, non-comparability, and incomplete-source states to the receiver.
  • SIE.10 tests the composition rule and negative branches. MDM, domain, and application owners retain truth, value, preference, authorization, and action.

SIE.6:End

SIE.7 - Specify Semantic Extraction and Transformation Mappings

Type: Method pattern Status: Stable Normativity: Normative method guidance within SIE; examples are constructed and non-normative.

Primary working result: an ExecutableSemanticMappingSpecification@Use that states source and target schemes, accepted correspondence premises and any relied-on identity or claim-composition premises, extraction and transformation rules, selection and cardinality, units and codes, conditions, defaults, errors, information loss, trace, examples, and tests.

SIE.7:1 - Problem Frame

Use this when accepted semantic correspondences must become repeatable extraction or transformation behavior, or existing code contains joins, conversions, defaults, and exclusions that cannot be traced to their semantic premises. The recognizable failure is a pipeline that runs successfully while changing meanings, merging unresolved identities, dropping conflicts, or inventing values through defaults.

For the named use, specify the executable semantic rules independently of the pipeline that may run them. First bind each output claim to accepted input senses and any relation, identity or composition results it relies on. The specification must be precise enough to implement and test without reopening its semantic choices in code.

Data Engineering or another implementer receives the mapping specification, and validation can trace its rules to their premises. Do not use SIE.7 to choose virtual versus materialized realization, build or operate the pipeline, or authorize access. A correspondence set is an input, not executable behavior; a running transform is evidence, not the specification itself.

SIE.7:2 - Problem

Mapping logic is often dispersed across SQL, ETL configuration, model transformations, lookup tables, API adapters, and undocumented operator knowledge. The same “mapping” word then refers to a semantic relation, an extraction query, a unit conversion, a data movement, and the Work that ran it.

When these objects collapse, semantic review happens after implementation and cannot identify what was intended. Defaults conceal missing inputs, many-to-one mappings drop distinctions, identifiers are normalized without issuer context, and error rows vanish. A code diff reveals mechanics but not the receiving-use claim it is allowed to produce.

SIE.7:3 - Forces

ForceTension
ExecutabilityRules must be precise enough to run, while binding them to one technology can hide their semantic intent.
CompletenessEvery output branch needs behavior, while invented defaults make an incomplete rule appear total.
PerformanceEfficient joins and precomputation matter, while optimization must preserve semantic premises and trace.
CardinalitySource and target structures differ, while one-to-many and many-to-one choices can create loss or duplication.
Error handlingOperational systems prefer a value or null, while semantic failure needs distinct unresolved, incompatible, stale, and source-error branches.
ChangeStable rule identifiers aid maintenance, while source editions and accepted correspondences can invalidate a rule.

SIE.7:4 - Solution

Specify semantic mapping rules separately from their implementation. Bind every rule to a receiving-use contract, the source and target schemes, accepted correspondence premises, and any identity or claim-composition premise on which that rule depends. Make selection, cardinality, conversions, defaults, errors, loss, trace, and tests explicit. Require implementations to preserve these behaviors or return a named discrepancy.

SIE.7:4.1 - Pattern-Use Unfolding

  1. Name the output claim and receiver. State the target field or proposition, its meaning, grain, interval/effectivity, and the action it supports.
  2. Bind source and target schemes. Reference the SIE.2 source rows and target interface/model definitions, editions, profiles, units, codes, identifiers, and access assumptions.
  3. Bind semantic premises. Reference accepted SIE.4 correspondence rows and every load-bearing SIE.5 identity disposition. Reference a SIE.6 composition or conflict result when the rule depends on that result. Stop on an unresolved required premise; do not require identity or claim-composition work that cannot change the rule.
  4. Specify selection and extraction. State source records, predicates, joins, windows, configuration/effectivity filters, ordering, and behavior for missing or duplicate inputs.
  5. Specify transformation. State direction, construction, decomposition, aggregation, unit/code conversion, normalization, derivation, and required external lookup. Name the authority for any conversion or code table.
  6. Specify cardinality and identity preservation. State one-to-one, one-to-many, many-to-one, or conditional behavior; keep source identifiers and disposition references when rows combine or split.
  7. Specify defaults and errors. Distinguish absent, unknown, not applicable, inaccessible, stale, incompatible, unresolved, source failure, and actual zero or empty value. Permit a default only when the contract and semantic warrant state its meaning and loss.
  8. State information loss and forbidden reuse. Name omitted distinctions, coarsening, precision, interval, provenance, or conflict and the use for which the loss is accepted.
  9. Provide trace and examples. Give stable rule identifiers, input-to-output trace positions, positive examples, boundary and counterexamples, and expected negative branches.
  10. Define implementation conformance and reopen. State observable behavior an implementation must match and source, premise, contract, or target changes that invalidate the rule.

SIE.7:4.2 - Record the Result

Mapping positionRequired content
rule and usestable rule identifier, receiver, output claim, grain, interval/effectivity
schemessource/target assets, models/schemas, editions/profiles, fields/types/relations, units/codes
semantic inputsaccepted correspondence rows and any relied-on identity dispositions or composition/conflict results, with their conditions
extractionselection, joins, filters, windows, effectivity, duplicates, missing-input behavior
transformationdirection, construction/decomposition/aggregation, conversions, lookups, derivation
cardinality and identifierssource-target multiplicity, split/merge behavior, source-ID and premise preservation
defaults and errorsdistinguished states, permitted default and meaning, failure branches, quarantine or stop
loss and traceaccepted/forbidden loss, provenance, rule and premise references, input-output trace
examples and conformancepositive, boundary, negative/unlike examples, expected outputs, implementation predicate, reopen

SIE.7:4.3 - What Changes in Practice

Semantic rules and their premises become independently reviewable. Data Engineering can optimize or replace an implementation while preserving the mapping behavior, and a failed output can be traced to a source premise, rule, implementation discrepancy, or receiving-use change.

SIE.7:5 - Archetypal Grounding - AP242/QIF Mapping Rules

The AP242/QIF package needs a row set for the configuration-bound inspection query. Its specification includes these constructed rules:

RuleSemantic and executable behavior
MAP-SIE-APQ-01Select the released AP242 product-definition revision/configuration supplied by Systems Engineering and filter features by effectivity E. Do not select “latest” as a substitute.
MAP-SIE-APQ-02For each accepted SIE.4 plan-characteristic-concerns-feature row, join exact source identifiers only under the referenced SIE.5 feature disposition. Preserve AP242 and QIF IDs and issuers.
MAP-SIE-APQ-03Compose AP242 definition/effectivity and QIF plan/result claims through the referenced SIE.6 result. Emit compatible qualified claims, explicit contradiction, non-comparability, or unresolved branches; never overwrite.
MAP-SIE-APQ-04Convert units only through the contract-approved code/unit table and retain original value, unit, conversion rule, precision, and loss. An unknown unit stops that result row.
MAP-SIE-APQ-05Return unmatched AP242 feature, unmatched QIF characteristic, stale result, missing provenance, and source-error states distinctly. When both objects are identified, distinguish a plan excerpt that leaves their assignment unknown from a complete governing plan that establishes they have no such assignment at this revision and effectivity. No state defaults to an accepted match.

Positive examples cover one known configuration/feature/characteristic/result chain. Boundary cases cover one-to-many characteristics and repeated results. Negative cases cover an obsolete revision, incompatible feature, unresolved identity, unknown unit, contradictory result status, and absent QIF plan. A SQL view, R2RML mapping, QVT transformation, or application code may implement the rules; none changes the specification without reopening the affected rule.

SIE.7:6 - Bias-Annotation

LensLikely driftRepair
GovernanceMapping code silently decides source priority, identity, or authoritative value.Require references to accepted premises and the direct authority for conversions or defaults.
ArchitectureA tool’s expressiveness defines the semantic rule.State implementation-independent behavior and return an implementation gap when the tool cannot preserve it.
Ontology/EpistemologyCorrespondence truth, transformation rule, performed transformation, and output claim collapse.Keep the rule and its evidence separate from execution occurrences and resulting claims.
PragmaticsThe specification reproduces every implementation detail.Include only behavior needed to preserve semantics, errors, trace, and conformance.
DidacticsExamples are copied as the complete rule.State the general condition and use examples as tests, including counterexamples.

SIE.7:7 - Conformance Checklist

  • Every rule names a receiving output claim and use.
  • The specification identifies the source and target schemes, editions/profiles, meanings, units, codes, and identifiers used by each rule.
  • Accepted correspondence premises and any relied-on identity or composition premises are referenced rather than re-decided in code.
  • Selection, joins, filters, windows, effectivity, duplicates, and missing inputs are explicit.
  • Transformations, conversions, external lookups, and their authority are explicit.
  • Cardinality, split/merge behavior, and source-identifier preservation are specified.
  • Absent, unknown, not applicable, inaccessible, stale, incompatible, unresolved, source failure, zero, and empty values remain distinguishable where relevant.
  • Defaults have a semantic warrant, accepted loss, and test.
  • Information loss, forbidden reuse, provenance, and input-output trace are inspectable.
  • Positive, boundary, negative, and unlike cases define observable implementation conformance.
  • The specification claims no running pipeline, service level, or receiving-use validation.

SIE.7:8 - Common Anti-Patterns and How to Avoid Them

Anti-patternRepair
SQL execution treated as semantic justificationRecover the semantic rule, premises, loss, errors, and tests; check the SQL implementation against them.
Crosswalk equals transformationAdd selection, direction, cardinality, conversions, defaults, errors, trace, and examples.
Null for every failureDefine distinct semantic and operational states and their receiver behavior.
Latest record winsUse the direct configuration/effectivity or justified interval rule.
Normalize identifiersKeep the original entries and how they were resolved. Preserve the context for a rule and the issuer for an assignment. Reference the identity disposition.
Hidden unit conversionRecord source/target units, authority, precision, loss, and counterexample tests.

SIE.7:9 - Consequences

Implementers receive a bounded contract that can survive technology change, and reviewers can distinguish a semantic defect from an implementation defect. Negative branches and accepted loss become testable, and optimization can proceed under a preservation predicate.

The cost is explicit rule and example work before or alongside coding. Some tools cannot represent the required branches or trace and must be wrapped, changed, or rejected for this use.

SIE.7:10 - Rationale

A semantic correspondence states a relation; an executable mapping states how source occurrences produce target claims under conditions. Making that extra structure explicit prevents implementation convenience from becoming a semantic decision and lets Data Engineering own execution without inheriting unstated SIE authority.

SIE.7:11 - SoTA-Echoing

The best-known line combines declarative mapping languages, model transformation, traceability, and representation-preservation checks. The serious default is code-first ETL that leaves semantic premises and loss implicit. SIE.7 makes the receiving-use mapping contract independently recoverable, including its negative states. Code and its documentation can carry that contract when the semantic requirements and their grounds remain distinguishable from the implementation being tested.

Source lineAdopt, adapt, or rejectRole and limit
Current FPF A.6.3.RTadoptGoverns preservation through representation transition; it does not specify this domain mapping.
R2RMLadaptDemonstrates declarative relational-to-RDF mapping structures; RDF and relational sources are optional technology families.
OMG QVT 1.3adaptContributes model-query/view/transformation and trace forms; MOF/QVT is not mandatory.
PROV-OadaptSupports derivation and activity/agent/entity trace; provenance does not prove semantic preservation.
code-first ETL with implicit semantic premisesreject as sufficientExecution must be checked against an independently recoverable rule, loss, and branch contract.

Reopen when an input or target scheme changes, a correspondence/identity/composition premise changes, a counterexample defeats the rule, the receiver changes accepted loss, or implementations cannot satisfy the preservation predicate.

SIE.7:12 - Relations

  • SIE.1 supplies the output claims, accepted loss, service conditions, tests, and stop.
  • SIE.2 supplies source and target semantics, editions, identifiers, units/codes, provenance, and gaps.
  • SIE.4 supplies accepted correspondence premises; SIE.5 and SIE.6 supply identity and composition results when a rule relies on them.
  • SIE.8 consumes rule behavior and implementation conditions to compare realization alternatives.
  • SIE.9 exposes the rule outputs and error branches to the receiver.
  • SIE.10 tests both specification semantics and implementation conformance. Data Engineering owns pipeline construction, operation, observability, reliability, and recovery.

SIE.7:End

SIE.8 - Choose Virtual, Materialized, or Hybrid Semantic Realization

Type: Method pattern Status: Stable Normativity: Normative method guidance within SIE; examples are constructed and non-normative.

Primary working result: a SemanticRealizationDecision@Use: a supported choice, sufficient rejection, worthwhile probe, or missing-input result for a named semantic-integration use. A positive choice identifies the implementation results it still requires.

SIE.8:1 - Problem Frame

Use this when accepted semantic mappings exist and the current question is whether to evaluate them at query time, persist integrated results, or combine both. Enter also when a graph database, warehouse, federation, cache, search index, API composition, or “virtual knowledge graph” has already been proposed and its semantic consequences need comparison.

For the named integration use, derive the criteria for choosing a realization from the use contract and mapping specification. The result may be a bounded choice, probe, rejection or missing-input return. The responsible providers retain physical implementation and operation.

The payoff is a realization selected because it preserves the required meanings and service conditions, not because one carrier is fashionable or already available. Do not use SIE.8 to build, deploy, or operate a data service, select a whole enterprise platform, authorize access, or prove that the interface works. Data Engineering, platform, security, provider, finance, and other direct owners supply those results.

SIE.8:2 - Problem

Materialization can improve latency and independence from source availability but creates copied state, invalidation, custody, storage, and refresh obligations. Virtual access can preserve source currency and authority but inherits source latency, availability, access, and query-capability limits. A hybrid can isolate hot or stable subsets but adds coherence and branch complexity.

When the choice is made from technology labels, these consequences remain hidden until operation. A copied graph is described as semantic truth, a federation as automatically current, or a cache as harmless optimization. The same mapping semantics can yield different provenance, currentness, error, and recovery behavior in each realization.

SIE.8:3 - Forces

ForceTension
FreshnessVirtual reads can observe current source state, while network and source delays can still make answers stale or inconsistent.
LatencyMaterialization and caching can respond quickly, while refresh and invalidation may violate the use’s time boundary.
AvailabilityCopies can survive source outages, while they can conceal that authority or access conditions changed.
Source authorityQuerying the source keeps custody visible, while a receiver may need stable snapshots and reproducible answers.
Security and permissionFewer copies reduce exposure, while live federation can broaden runtime credentials and cross-source disclosure.
Provenance and reproducibilityMaterialized snapshots aid replay, while virtual results need captured queries, source versions, and occurrence metadata.
Operability and recoveryA simpler runtime can reduce failure modes, while hybrid arrangements add invalidation and coherence responsibilities.
CostStorage, compute, licenses, egress, support, and provider dependency trade differently across cases.

SIE.8:4 - Solution

Use a decisive restriction when it settles whether a proposed arrangement can serve the contract. For an order asking for one workable design, establish that the chosen arrangement satisfies the relevant conditions for source access, rule execution, copied state, provenance, currentness, failure, protection, operation, recovery, exit and joint resource demand. When a preference is claimed, compare the serious alternatives on conditions that distinguish them for this use. Return a supported choice, sufficient rejection, worthwhile probe, or missing-input result for the named use.

SIE.8:4.1 - Pattern-Use Unfolding

  1. Fix the receiving result. Reference the SIE.1 answer, SIE.7 rules, required source/identity/claim branches, and validation conditions that a successful candidate must preserve.
  2. Apply decisive exclusions. A known source prohibition or other sufficient condition can defeat an arrangement. Record the condition and evidence needed for that conclusion and stop developing the excluded alternative. If no serious candidate remains, return the bounded rejection or identify the missing result.
  3. Develop the relevant realization. For an order for one workable design, follow the virtual, materialized or hybrid branch below that supplies it, then check the complete design. For a comparative order, develop the alternatives needed to establish the claimed preference. For a virtual option, state source access, rule evaluation, pushdown or mediation, credentials, latency/availability behavior, provenance capture, and failure return.
  4. Describe a serious materialized alternative. When copying remains a candidate, state copied or derived state, snapshot identity, refresh/invalidation, storage and custody, source deletion/correction behavior, provenance, recovery, and exit.
  5. Describe a hybrid where warranted. Identify which permitted subset is materialized and which source-sensitive part remains virtual. State coherence, invalidation, and fallback behavior. Confirm permission for each subset selected for copying.
  6. Check the chosen arrangement and explain any preference. Use the conditions that can change the receiving result: freshness, latency, availability, access, protection, source authority, reproducibility, provenance, operability, recovery, cost, and semantic loss. Include concurrent source calls, shared credentials, trace, retries, support, and other demands within each applicable resource envelope. Every pair of contributions may fit a shared limit even when the demands of all the contributions together exceed it.
  7. Examine relevant failure and change cases. Use the source outages, corrections, access changes, mapping changes, stale or partial refresh, provenance loss, and recovery cases needed for the proposed conclusion. Earlier sufficient evidence can support a bounded rejection; a positive selection needs its load-bearing conditions.
  8. Choose or identify worthwhile further work. Select a supported arrangement, reject it, or return the missing result. Commission a discriminating probe only when its obtainable result can change the decision enough to justify its full burden and displaced work. Keep an unresolved comparison explicit when further inquiry is unavailable or not worthwhile. State the reasons for the disposition that its receiver needs.
  9. Name implementation returns for a selected choice. Identify the Data Engineering, platform, provider, security, legal, finance, or operating results required to realize that choice.
  10. Return the conditions needed by this result. For a selected realization or supplied receiving result, give SIE.9 its service, error, currentness, and fallback meanings. Retain observations that can reopen the conclusion where they change continued reliance.

SIE.8:4.2 - Record the Result

A sufficient rejection of one proposed arrangement is complete with the receiving use, named proposal, decisive grounds and evidence, scope, and material limits. It does not require a comparison with unrequested alternatives or an implementation and interface design.

Decision contentWhen it is neededContent supplied
Receiving use and dispositionEvery resultThe question and proposed arrangement or comparison scope, supported choice/rejection/probe/missing-input result, grounds, and material limits.
Decisive exclusionA proposed arrangement is rejected on sufficient groundsThe condition that defeats it, the evidence and applicability needed for that condition, and the scope of the rejection.
Candidate arrangements and comparisonThe engineer must justify a workable realization or a preferenceThe relevant conditions for the chosen realization, including required semantic branches, access, state, provenance, timing, protection, operation, failure, recovery, exit and joint demand. A claim of preference also needs a deciding difference from the alternatives.
Failure/change evidenceThe supplied conclusion depends on itEvidence for its load-bearing conditions. One qualified prohibition can suffice for rejection; positive selection needs the relevant failure and change cases for the claimed arrangement.
Further inquiryA probe is proposedObtainability, possible decision contribution, full burden, displaced work, and how its result can change the decision.
Implementation returnsA realization has been selectedRequired results from the responsible providers, what is supplied or still missing, and the acceptance evidence needed to realize that choice.
Interface semanticsA selected realization or receiving result needs themCurrentness, source/error, incomplete-result and fallback meanings supplied to SIE.9.
Continued relianceA condition can materially change the result’s useThe observation, source change, or receiving change that reopens the affected decision.

A positive choice cannot use the rejection boundary to omit a condition on which that choice relies. The selected arrangement and its implementation returns remain qualified by all the semantic, service, access and resource conditions they depend on.

SIE.8:4.3 - What Changes in Practice

The team compares ways to supply the same semantic result rather than comparing product categories. A graph store may survive as a materialized candidate, a federation as a virtual candidate, or neither. The selected decision states what still has to be implemented and operated before any service claim is made.

SIE.8:5 - Archetypal Grounding - Provider Availability without Replication

Two providers expose current availability through governed APIs. Provider A means “on hand”; Provider B means “available to promise”. SIE.4 preserves the semantic difference and SIE.6 permits a qualified side-by-side answer but forbids arithmetic fusion. Neither provider permits replication of its availability state.

If the question is only whether a proposed copied availability store may serve that contract, the completed answer is: “Reject the proposed copied availability store for this purchasing use: the qualified provider conditions prohibit copying the required availability state.” The contract, proposal, and provider conditions identify its scope and grounds. This concludes that question without a latency study, credential design, recovery plan, or alternative selection.

When the receiving question also asks which remaining arrangement to use, continue with the following comparison:

CandidateConstructed comparison
materialized common graphexcluded by the providers’ prohibition on copying availability state; that condition is sufficient without developing its implementation, recovery, and exit
query-time virtual mappingobtains metadata and values at query time and preserves source custody and timestamps. This route depends on timely access to both, the credentials and query limits, and the agreed timeout or incomplete-result branches
hybrid metadata plus virtual valuesretain an authorized current copy of stable product-family correspondences, mapping rules and source metadata. Retrieve availability values live and invalidate the copy when an applicable definition or product relation changes

Suppose the only live source for the required correspondences is unavailable throughout this buyer’s decision window. The rights holder permits a local copy and the maintainer confirms that it covers the requested products through that window. Live values and their trace can arrive in time, and maintaining the copy fits the allowance. The hybrid can serve this order. The fully live route lacks the correspondences at the deadline. If both routes meet the contract under other conditions, an engineer commissioned to provide one workable design may choose either.

For the hybrid, obtain credential handling, concurrent calls, timeout behaviour, observability and recovery from the implementation providers. Supply SIE.9 with the separately attributed quantities, timestamps, provider errors and permitted incomplete responses. An operating-service claim needs evidence from the implementation.

SIE.8:6 - Bias-Annotation

LensLikely driftRepair
GovernanceMaterialization silently transfers custody, authority, or permission.Record source rights, retention, correction, and use authority for every copied state.
ArchitectureThe incumbent platform determines the answer, or every conceivable alternative requires full design.Use a decisive exclusion when it settles the question. For a feasible design, qualify its complete arrangement. For a preference, also compare the serious alternatives on the receiving basis.
Ontology/EpistemologyA graph or warehouse is treated as the semantic arrangement itself.Keep mapping premises, claims, provenance, and validation independent of carrier.
PragmaticsEvery unresolved comparison commissions a probe.Compare obtainable decision benefit with the probe’s full burden and displaced work.
Didactics“Virtual is fresh; materialized is fast” becomes a universal rule.Show source latency, snapshot reproducibility, invalidation, and failure conditions that reverse the slogan.

SIE.8:7 - Conformance Checklist

Apply the checks below to the conclusion you are returning.

For every result

  • The receiving question, named proposal or comparison scope, disposition, grounds, and material limits are recoverable.
  • The evidence supports that disposition at its stated scope; it creates no broader feasibility, running-service, or achieved-performance claim.

For a sufficient rejection

  • The decisive condition and its qualified evidence defeat the named proposal for this use.

That rejection completes the Method when it answers the requested question. The following comparison and implementation checks do not become prerequisites for it.

For a live comparison or positive selection

  • A successful candidate preserves the receiving result, mapping rules, and required semantic branches.
  • The chosen arrangement covers its required access, state, execution, provenance, failure, operation, recovery, exit and joint resource demand. A claimed preference has grounds that distinguish the alternatives.
  • Freshness and latency are defined for the receiving use.
  • Source authority, custody, permissions, correction/deletion, and retention consequences are explicit.
  • Security/privacy and runtime credential differences are compared where they can change the result.
  • Reproducibility and provenance behavior are specified for the candidate’s virtual occurrences and copied state.
  • Relevant outage, access, mapping, correction, refresh, provenance-loss, and recovery cases support the proposed conclusion.
  • For a selected realization, the required implementation and operating results remain with their direct owners, and SIE.9 receives the required currentness, error, incomplete-result, and fallback meanings.

For a proposed inquiry

  • Its obtainable decision contribution justifies the full burden and displaced work.

SIE.8:8 - Common Anti-Patterns and How to Avoid Them

Anti-patternRepair
“Knowledge graph” as the requirementRestate the receiving result and compare graph and non-graph realizations.
Virtual means no stateRecord the state the virtual arrangement needs. Depending on the use, this can include mappings, caches, credentials, query occurrences, source snapshots and provenance.
Materialized means reliableTest refresh, invalidation, correction/deletion, recovery, and source-authority changes.
Hybrid means best of bothExpose coherence, invalidation, fallback, and doubled operating responsibilities.
Product feature checklistCompare serious arrangements on use-sensitive criteria, joint resource demand, and relevant failure cases.
Decision equals implementationName the build, provider, security, and operating results still missing.

SIE.8:9 - Consequences

The bounded realization decision exposes source, semantic, and operating trade-offs and the conditions for reconsidering it. Interface designers receive explicit currentness and error behavior, while implementers receive a clear invariant to preserve.

The cost is comparison beyond the preferred platform and coordination with operational owners. A selected candidate may still stop because access, security, service, provider, or cost evidence is missing.

SIE.8:10 - Rationale

Choosing virtual or materialized access changes when and where mappings execute, which state is copied, how provenance and currentness are established, and which failures reach the receiver. Those changes can alter semantic adequacy, so SIE owns the bounded comparison while direct practices own implementation and operation.

SIE.8:11 - SoTA-Echoing

The best-known line combines declarative mappings, virtual knowledge-graph systems, data federation, materialized integration, and operational data-product practice. The serious default alternatives are “materialize one canonical graph” and “federate everything live”. Each can be correct under conditions; each is defective as a universal answer because it hides a different set of currentness, access, provenance, and recovery obligations. SIE.8 uses these contributions to compare whole arrangements that supply the same semantic result.

Source lineAdopt, adapt, or rejectRole and limit
Ontop virtual-KG lineadaptDemonstrates query-time virtual realization over mappings; it does not make virtual RDF mandatory or supply source access and receiving acceptance.
R2RMLadaptSupplies one declarative mapping form usable in virtual or materialized arrangements; relational/RDF technology is optional.
Data on the Web Best PracticesadaptContributes access, version, provenance, reuse, and persistence questions; Web publication is not required.
universal canonical graphreject as defaultMaterialization is one candidate and cannot transfer source authority or erase incompatibility.
universal live federationreject as defaultQuery-time access does not guarantee freshness, availability, permitted disclosure, or reproducibility.

Reopen when source access or replication rights change, measured latency/availability defeats the use, refresh/invalidation fails, mapping or source semantics change, security/provenance conditions change, or a new candidate materially improves the comparison.

SIE.8:12 - Relations

  • SIE.1 supplies the invariant result and use-sensitive service and protection conditions.
  • SIE.7 supplies executable semantic behavior and loss/error branches every candidate must preserve.
  • SIE.2, SIE.5, and SIE.6 supply source authority, identity, claim, provenance, and currentness conditions.
  • SIE.9 consumes the selected realization’s currentness, latency, availability, provenance, error, access, and fallback semantics.
  • SIE.10 tests the realized candidate and receiving workflow; it can narrow or fail the decision’s assumed conditions.
  • Data Engineering, platform, provider, security, legal, finance, and Operations owners supply implementation and operating results.

SIE.8:End

SIE.9 - Connect a Receiving Use through a Semantic Interface

Type: Method pattern Status: Stable Normativity: Normative method guidance within SIE; examples are constructed and non-normative.

Primary working result: a ReceivingSemanticInterface@Use defining the smallest query, view, API, message, schema, report, or other boundary that carries the required meanings and branches to the receiver with interpretation, source and provenance, currentness, accepted loss, access assumptions, errors, unresolved returns, and a path back to the owning source or decision.

SIE.9:1 - Problem Frame

Use this when semantic mappings or integrated state exist but the receiving Work still cannot obtain, interpret, challenge, or return the bounded result. Enter when a technically reachable endpoint hides source meanings, currentness, unmatched rows, conflicts, or the difference between “no value” and “source unavailable”.

For the named receiving use, start with the action the result is meant to support. Choose the smallest interaction and result form that connects the maintained integration arrangement to that use and carries every branch the receiver needs. Supply an interface contract and a candidate interface. Establish the receiver’s authorization and the service’s operating adequacy separately when the use requires them.

The payoff is a boundary at which semantic meaning, failure, and provenance are usable by ordinary Work. Do not use SIE.9 to design the application’s whole user experience, make its decision, operate the service, or accept engineering/quality results. Those owners consume the interface under their own Methods and authority. Stop rather than return a positive interface when a required semantic branch, interpretation, provenance/currentness condition, source-return path, or receiver-side use test cannot be represented or traced.

SIE.9:2 - Problem

Integrated data can remain unusable because the receiver cannot ask the relevant question or distinguish the answer’s conditions. An API may omit source edition and effectivity; a report may list a fused value without conflict; a schema may use one null for unknown, not applicable, stale, and timeout; a user may have no path to challenge an identity or mapping premise.

When the interface is treated as transport only, semantic obligations remain in internal documentation. The receiving Work either overtrusts the result or reconstructs meanings informally, creating a second uncontrolled integration at the boundary.

SIE.9:3 - Forces

ForceTension
MinimalityA small interface is easier to use and maintain, while hiding source, loss, or failure makes it unsafe.
Receiving the resultThe receiver needs to interpret the result and be able to return a disputed premise for review. A programmatic interface needs a stable schema, stable branch codes and a return path the caller can follow. A human-readable interface needs to explain the branch and show where to raise the question.
AbstractionReceiver-friendly names reduce burden, while source identifiers and meanings must remain recoverable.
PerformanceRich provenance and alternative claims cost bandwidth and attention, while omitted trace defeats challenge and validation.
SecurityThe receiver needs enough source information to rely, while disclosure can violate provider, privacy, or protection conditions.
EvolutionStable interface promises aid use, while source or mapping changes must not be hidden behind unchanged field names.

SIE.9:4 - Solution

Design the interface from receiving actions and semantic branches, not from the internal store. Expose the smallest result that preserves interpretation, source/version, currentness, accepted loss, identity and claim status, provenance, access assumptions, errors, unresolved returns, and source-return paths. Bind every field and branch to the use contract, mapping rules, and selected realization.

SIE.9:4.1 - Pattern-Use Unfolding

  1. Name the receiver interaction. State who or what asks, the query/message/report action, timing, input parameters, and the next Work or decision that consumes the answer. For several recipients, specify what each may receive and act on, and when. Check a shared delivery against all its required users. A joint decision may also need them to exchange results or authorize a common action.
  2. Select the interface form. Choose query, view, API, message, schema, report, file, or mixed human/machine form based on the receiving Work. Do not inherit the internal realization shape automatically.
  3. Define semantic inputs. State the identifiers a request accepts, how the interface validates their form and how it resolves them. Supply any required issuer, assignment context, configuration or effectivity, time window, units, locale or code context, and permissions.
  4. Define result claims and interpretation. For each output, state meaning, grain, scope, interval/effectivity, units/codes, source identifier behavior, accepted loss, and permitted use.
  5. Expose qualified branches. Represent matched/qualified, unmatched, incompatible, unresolved identity, source-qualified conflict, non-comparability, stale, inaccessible, timeout/source error, and partial result where applicable.
  6. Expose provenance and currentness. Provide source/edition or a stable reference, observation/retrieval time, mapping/composition rule version, derivation/trace reference, and freshness status needed by the receiver.
  7. State access, protection, and authority assumptions. Explain what the interface verifies, what the caller supplies, what may be disclosed, and which actions remain unauthorized by the semantic result.
  8. Provide challenge and return paths. A receiver must be able to identify which source, correspondence, identity disposition, composition, mapping or operational result needs examination and where to return the issue.
  9. Bind service behavior without claiming it. State latency, availability, pagination/volume, ordering, idempotence or snapshot expectations only where semantic use depends on them; obtain implementation/operation evidence separately.
  10. Define conformance and reopen. Give representative requests, responses, error branches, compatibility conditions, deprecation/change behavior, and observations that reopen the interface.

SIE.9:4.2 - Record the Result

Interface positionRequired content
receiver interactioncaller/reader, receiving Work, request, timing, next action
interface formquery/view/API/message/schema/report/file and why it fits the Work
request semanticsparameters, acceptable identifier forms and resolution context, configuration/effectivity, windows, units/codes, permissions
response semanticsclaims, grain, scope, interval, units/codes, source IDs, accepted loss, permitted use
branch modelqualified, unmatched, incompatible, unresolved identity, conflict, non-comparable, stale, inaccessible, source error, partial
provenance/currentnesssource/edition, times, rule versions, derivation/trace, freshness status
protection/authorityverified and assumed conditions, disclosure limits, action not authorized
challenge/returnstable path to source, semantic premise, mapping, implementation, or direct decision owner
service/conformanceaction-sensitive service conditions, examples, errors, compatibility/deprecation, reopen

SIE.9:4.3 - What Changes in Practice

The receiver no longer has to infer semantic meaning from field names or call the integration team to understand a missing row. Qualified, incompatible, conflicting, stale, and source-error states become part of the normal interface contract, and every challenge can be returned to a specific premise or owner.

SIE.9:5 - Archetypal Grounding - AP242/QIF Review Interface

The quality engineer uses a view or API with request parameters productDefinitionRevision, configuration, featureIdentifier, and effectivity. The candidate response preserves these positions:

Response positionConstructed behavior
featureAP242 source identifier, issuer/profile, configuration/effectivity, source edition, and receiver-friendly label
inspectionCharacteristicQIF source identifier, plan and characteristic meanings, source edition, and the accepted correspondence-row reference
inspectionResultsource-qualified QIF claim, observation time/status, unit and original value, provenance, and any conversion rule
identityDispositionreferenced SIE.5 result and its grain/interval, not a copied boolean
claimStatusqualified, conflict, non-comparable, or unresolved with the SIE.6 composition reference
freshnessreleased AP242 configuration/effectivity used, QIF observation window, retrieval time, and stale status
rowDispositionmatched, unmatched-feature, unmatched-characteristic, unresolved-assignment, no-assignment, incompatible, unresolved-identity, stale, source-error, or prohibited
returnPathsource record and mapping/correspondence/identity/composition rule references plus the direct engineering or quality owner for the decision

A known match returns a qualified row. A feature absent at effectivity E returns unmatched rather than the nearest label. An unresolved identity returns that branch without claiming no inspection exists. Two identified objects can still have an unresolved assignment when only an excerpt of the plan is available. Return no-assignment when the complete applicable plan settles the question. A source timeout returns partial/incomplete only if the contract permits it. The responsible participants decide whether to accept the result or release the configuration.

SIE.9:6 - Bias-Annotation

LensLikely driftRepair
GovernanceInterface access is mistaken for permission to act or disclose.State verified/assumed permissions, disclosure limits, and the direct action authority.
ArchitectureInternal graph or warehouse schema becomes the public contract.Design from receiving actions and preserve realization independence where useful.
Ontology/EpistemologyField name, status code, and claim meaning collapse.Define every output and branch with scope, source, time, and permitted use.
PragmaticsFull provenance overwhelms routine use.Expose the action-changing summary and a stable trace path to detailed premises.
DidacticsError branches look like exceptional implementation failures.Teach unmatched, incompatible, conflict, and unresolved as normal semantic outcomes.

SIE.9:7 - Conformance Checklist

  • The request and receiving Work identify who uses the answer, their permitted content, and the next action of each required recipient.
  • The form is chosen for receiving use rather than copied from internal realization.
  • The request identifies the accepted entries, how to resolve them, required configuration or effectivity, windows, units or codes, and permissions.
  • Response claims state meaning, grain, scope, interval, source identifiers, loss, and permitted use.
  • Qualified, unmatched, incompatible, unresolved identity, conflict, non-comparability, stale, inaccessible, source-error, and partial branches remain distinguishable where applicable.
  • Source/edition, observation/retrieval time, rule versions, derivation/trace, and freshness are recoverable.
  • Protection, disclosure, and authority assumptions are explicit; the interface grants no unstated authorization.
  • The receiver can return a defect or gap to a specific source, semantic premise, mapping, implementation, or decision owner.
  • Action-sensitive latency, availability, snapshot, and volume behavior are stated without claiming unobserved performance.
  • Representative requests, responses, errors, compatibility/deprecation behavior, and reopen conditions are present.

SIE.9:8 - Common Anti-Patterns and How to Avoid Them

Anti-patternRepair
Expose the integrated tableStart from the receiving action and design only the claims and branches it needs.
One null or HTTP error for every absenceDistinguish semantic absence/unresolved states from access, timeout, and implementation failure.
Provenance in internal logs onlyExpose the action-changing provenance/currentness summary and stable trace reference.
Hide source IDs behind one keyRetain the source entries, the contexts or assignments used to interpret them and the disposition supporting any identity on which the interface relies.
Endpoint is available, therefore usableValidate meanings, branches, currentness, service conditions, and representative Work through SIE.10.
Semantic result authorizes actionName the application, engineering, quality, safety, legal, or other decision owner.

SIE.9:9 - Consequences

The semantic arrangement becomes directly usable and challengeable. Receivers can distinguish a negative semantic result from an operational failure, and implementations can evolve behind a stable bounded contract while preserving source and rule trace.

The cost is a richer branch model and deliberate presentation of uncertainty and provenance. Some internal schemas or protocols must be wrapped rather than exposed directly.

SIE.9:10 - Rationale

An integration result has practical value only when it crosses into receiving Work without losing the conditions that make it meaningful. The interface carries interpretation, qualification and return paths. The receiving participant uses the result within its authority and refers other decisions to their designated owners.

SIE.9:11 - SoTA-Echoing

The best-known line combines explicit API/data-contract practice, data-on-the-Web provenance/version guidance, event interfaces, and standards-based engineering exchange. The serious default is transport-first interface design. Its defect is that success is reduced to reachability and schema conformance. SIE.9 uses these contributions to make semantic branches, currentness, provenance, and challenge paths part of the receiving contract.

Source lineAdopt, adapt, or rejectRole and limit
Data on the Web Best PracticesadaptContributes metadata, provenance, version, access, and reuse questions; Web publication is optional.
GS1 EPCIS 2.0.1adaptSupplies an event-oriented cross-enterprise interface case with identifiers and query semantics; it does not decide SIE identity or receiving action.
ISO 10303-242:2025 and ISO 23952:2020adaptSupply unlike versioned engineering source/interface cases; their model scopes and direct authorities remain intact.
internal-schema or transport-first APIreject as sufficientReachability and schema shape cannot establish semantic interpretation, provenance, loss, branch behavior, or receiving-use fitness.

Reopen when the receiver or action changes, a source/mapping/realization premise changes, observed service behavior violates a semantic condition, branch handling causes unsafe interpretation, or a protocol change defeats compatibility.

SIE.9:12 - Relations

  • SIE.1 supplies the receiving action, answer claims, loss, service conditions, tests, and authority boundary.
  • SIE.2 supplies source meanings, identifiers, editions, access, provenance, and currentness.
  • SIE.4–SIE.7 supply correspondence, identity, composition, and executable mapping references and branches.
  • SIE.8 supplies selected realization, service assumptions, fallback, and missing implementation results.
  • SIE.10 validates the candidate interface and representative receiving workflow.
  • The relevant application or professional participants decide on authorization and risk acceptance. Establish any claimed outcome from the receiving work. Data Engineering and Operations remain responsible for running the service.

SIE.9:End

SIE.10 - Validate a Semantic Integration Result for Its Receiving Use

Type: Method pattern Status: Stable Normativity: Normative method guidance within SIE; examples are constructed and non-normative.

Primary working result: a SemanticIntegrationValidationAccount@Use that supports a bounded pass, narrow, unresolved, or stop conclusion with appropriate evidence and reopen conditions. A positive receiving-use claim covers all of its load-bearing obligations.

SIE.10:1 - Problem Frame

Use this when you need to judge whether a candidate semantic interface or mapping package is fit for a receiving use. Enter especially when one test family already passes and is being used as evidence for the whole: valid JSON, conforming RDF shapes, successful ETL, high matcher score, complete provenance, good data-quality metrics, or one successful demonstration.

Judge one semantic-integration result against one receiving-use contract for an identifiable package revision that you can inspect. The first move is to identify the receiving claim being judged and whether known evidence already settles a bounded failure or unresolved result. For a positive claim, identify its load-bearing obligations and the evidence that can test them. The first result can be a supported local failure, scoped uncertainty, or qualified positive use.

The receiver can see which result it may rely on, under which source editions and conditions, and which gaps remain. Do not use SIE.10 to authorize product release, accept a quality result, approve a recall, certify a service, or prove business effectiveness. Those with the relevant authority can use the validation account when making those decisions.

SIE.10:2 - Problem

Semantic integrations fail across several independent layers. A carrier can be well formed while meanings are wrong; correspondences can be defensible while transformation code violates them; identity rows can pass while claim conflicts are flattened; provenance can be complete while source claims are stale or false; quality dimensions can look good while the representative workflow receives the wrong answer.

One aggregate “quality” or “confidence” score hides which premise failed and what must reopen. It also encourages compensating a hard stop, such as unresolved identity or unauthorized source use, with strong results elsewhere.

SIE.10:3 - Forces

ForceTension
LayeringSeparate tests localize defects, while the receiver needs a whole-use conclusion.
Positive evidenceExpected matches demonstrate a path, while negative and unlike cases reveal hidden compression and defaults.
CoverageA positive use claim needs its load-bearing premises supported, while a bounded failure can be settled by sufficient defect evidence.
AutomationSchemas, shapes, queries, and metrics scale checks, while semantic and authority judgments often require input from participants with relevant domain knowledge or authority.
ChangeStable evidence is reusable, while source editions, rules, interfaces, and receiving conditions can invalidate only some results.
Decision pressureStakeholders want a pass or fail. The evidence may support only a narrower use or leave the result unresolved.

SIE.10:4 - Solution

State the conclusion at the scope its evidence supports. A known decisive failure or bounded unresolved premise can finish with sufficient evidence for that result. For a positive whole-use or contract-permitted narrower result, obtain matching evidence for every load-bearing premise, including the receiver’s interpretation. Use earlier results when their conditions still match. Preserve hard stops and distinguish unexamined premises from passing ones.

SIE.10:4.1 - Pattern-Use Unfolding

Steps 3–10 locate evidence for a positive use conclusion. A sufficient bounded failure or unresolved result can finish at step 2. Reuse matching earlier results for the applicable layers; a changed receiving interpretation can reopen a claim even when its carrier is unchanged.

  1. Identify the validation subject. Name the mapping, interface, or package result and receiving use being judged. Record the revisions and conditions on which the conclusion depends.
  2. Choose the conclusion and inspect known evidence. Take the relevant answer claim and stop condition from SIE.1. If a demonstrated defect already defeats it, return that bounded failure with sufficient evidence. If a necessary technical premise is unresolved, identify the affected claim. Apply the receiving authority’s separate acceptance rule. When a required record is absent at the contractual deadline, the authority can refuse that release while the technical property remains unknown. Keep the grounds for that decision distinct from evidence of a technical failure. For a positive claim, derive all load-bearing distinctions, loss, currentness/service/quality, authority, protection, branch, and representative-use obligations.
  3. Validate carrier and schema. Test parseability, declared schemas/shapes, required fields, datatypes, cardinalities, identifiers, and branch encodings. Treat a pass as structural only.
  4. Validate semantic-model and endpoint adequacy. Test whether source and target concepts, types, relations, constraints, units/codes, and any supplied model express the required distinctions and examples/counterexamples.
  5. Validate correspondences and mappings. Challenge accepted SIE.4 rows and execute SIE.7 positive, boundary, negative, and unlike examples. Check selection, cardinality, conversion, defaults, errors, loss, and trace independently.
  6. Validate identity and authority. Test every load-bearing SIE.5 disposition at its grain and interval, including issuer, version, part-whole, reuse, split/merge, and unresolved branches. Verify required authority and permission inputs rather than inferring them from data access.
  7. Validate claim composition. Test SIE.6 comparability, conflict, non-comparability, supersession, incomplete-source, and uncertainty branches. Confirm that source claims and derivation remain recoverable.
  8. Validate realization and interface behavior. Test currentness, latency, availability, snapshot/caching, invalidation, source failure, partial results, access/protection, provenance, error semantics, and challenge paths required by SIE.8 and SIE.9. A timed response establishes this execution’s elapsed time. For a guarantee across loads, establish a bound under the admitted joint request and resource conditions. A percentile requires evidence for the specified request population and measure.
  9. Validate provenance, currentness, and quality. Check that every relied-on output can recover its source and rule premises, that source/version/time status satisfies the use, and that selected quality measurements meet their action-changing thresholds. Do not treat provenance or process conformance as truth.
  10. Replay representative receiving Work. Run the named query, decision preparation, operation, or engineering workflow with expected positive, negative, and unlike cases. Observe whether the receiver obtains and interprets the required result and stops on forbidden branches.
  11. Assign dispositions at the supported scope. Use pass, narrow, unresolved, or stop for tested claims, and preserve any material unexamined reach. A positive narrow result states the contract-permitted subset and covers all of that subset’s load-bearing premises; excluded branches remain explicit. A hard stop cannot be offset by scores elsewhere.
  12. Record repairs, returns, and reopen. Send source, semantic, mapping, implementation, authority, or receiver defects to their direct owners; state which layer and consumers require retest after change.

SIE.10:4.2 - Record the Result

Validation positionRequired content
subject and usepackage/interface revision, source/rule versions, realization/test state, receiver and use
obligationspremises relevant to the claimed conclusion; all load-bearing contract obligations for a positive use claim
layer resultlayer, tested claim, method/case, evidence, expected/observed result, pass/narrow/unresolved/stop, defect owner
dependencysource, correspondence, identity, composition, mapping, realization or interface premise consumed
coverageexamined cases and matching earlier results; material unexamined or unresolved premises, distinguished from passing ones
use dispositionsupported local failure or gap, or positive result with its conditions and full load-bearing coverage; excluded subset and hard stops
continuationrepairs or direct-owner returns, focused retest, affected consumers, reopen condition

SIE.10:4.3 - What Changes in Practice

The team stops asking whether “the integration” passed one test. Each claim has an appropriate layer, evidence, and owner. A bounded subset can be used without hiding excluded rows, and a source or rule repair triggers focused revalidation instead of an automatic full rebuild or a silent continuation.

SIE.10:5 - Archetypal Grounding

SIE.10:5.1 - Positive AP242/QIF Subset Validation

The constructed AP242/QIF package is frozen with named AP242/QIF source occurrences, correspondence set, identity dispositions, claim-composition rules, mapping specification, hybrid realization, and review interface. It uses SIE.1:5’s stipulated receiving contract: the preceding 24-hour observation window, two-second response limit, and permission to return qualified evidence while showing unresolved local-extension and unknown-unit branches separately.

LayerConstructed probe and result
carrier/schemaRequest and response validate against their declared forms; unmatched, incompatible, unresolved, stale, and source-error states are representable. Passes structurally.
semantic-model/endpointsAP242 feature/configuration/effectivity and QIF plan/characteristic/result senses are recoverable. One local extension remains undefined; rows that consume it are unresolved.
correspondenceThe assigned pair joins. A shared label with no assignment in the accessible excerpt leaves the link unresolved. A complete governing plan with no assignment establishes a non-match at that revision and effectivity. Both objects can be identified in either case. A non-dimensional characteristic defeats a global type equivalence. Return partial coverage when the receiving contract permits it. A contract for the complete set still needs the unresolved assignment settled.
identity/authorityKnown feature identifier relation passes at revision/configuration/effectivity grain; obsolete revision and unresolved local ID stop their dependent branches. Engineering and quality authority remain external.
claim compositionCompatible AP242 definition/effectivity and QIF plan/result claims retain sources; contradictory result status returns conflict; incompatible intervals remain non-comparable. Passes for qualified branches.
transformationKnown mapping, one-to-many characteristic, unit conversion, unmatched feature, unknown unit, stale result, missing provenance, and source-timeout cases return the specified branches. One unknown-unit row stops.
realization/interfaceStable semantic metadata is available; volatile source data is queried under captured occurrence times. The one-second response meets the two-second deadline for this review query. Timeout returns an incomplete answer only where the contract permits it. Challenge paths resolve to the relevant premises.
provenance/currentness/qualityEvery accepted output row recovers sources, rules, and times. The configuration matches the released review basis; QIF observations six hours before T meet the 24-hour window, while a 25-hour control returns stale. Undefined-extension rows remain visibly unresolved outside the qualified set.
receiving workflowThe quality engineer retrieves a known result, recognizes unmatched/incompatible/conflict states, and stops on unresolved configuration or identity. Passes for the bounded subset.

The quality engineer can use the qualified rows under the narrow permission in SIE.1:5. Return the unresolved local extensions and unknown units separately as agreed. If an assignment needed for the requested feature is also unresolved, the contract gives no permission to omit it. Obtain the governing plan, report that the requested relation is still open, or agree with the recipient on a further partial return. A complete governing plan can establish the absence of an assignment for that revision even while other rows remain open. If the release authority requires a signed inspection record by its deadline and that record is missing, it can refuse release on those grounds. The unrecorded technical property can remain unresolved. A definition or unit-table repair reopens only the affected rows and receiving tests.

SIE.10:5.2 - A Decisive Defect and a Changed Receiving Meaning

In a constructed mapping probe, an input of 1 metre produces an output labelled 1 millimetre; the receiving contract requires 1000 millimetres. The input, rule, expected value, and observed output are enough to establish this mapping failure. Return that defect to SIE.7. Other layers remain unexamined; their results are unnecessary for this bounded failure. If the source unit is unavailable instead, the conversion premise remains unresolved at that scope.

Now consider a previously qualified availability interface. Its JSON field and numeric type stay unchanged, but the source changes the value from present availability to a future promise horizon. The receiver still reads the displayed quantity as “available now”. A passing shape check cannot support the earlier use conclusion: the changed interpretation defeats a relied-on premise. SIE.11 identifies the affected mapping and interface uses.

After repair, a positive conclusion for that receiving use needs the corrected interpretation and every other load-bearing condition. Matching earlier evidence can supply unchanged conditions; the known failure or its repair alone cannot establish the whole result.

SIE.10:6 - Bias-Annotation

LensLikely driftRepair
GovernanceThe validation team is treated as release, quality, safety, or business authority.State the semantic conclusion and return the owning decision with its conditions.
ArchitectureAvailable automated tests define all validation layers.Add qualified semantic, identity, authority, and receiving-work evidence where automation cannot decide.
Ontology/EpistemologyWell-formed representation, true relation, supported claim, and usable decision collapse.Test each claim at its layer and keep the whole-use composition explicit.
PragmaticsA decisive failure still triggers every layer test.Finish the bounded failure with sufficient evidence; require full load-bearing coverage for a positive whole-use or permitted subset claim.
DidacticsA score invites compensation across hard stops.Use categorical layer dispositions with evidence and state that stops are non-compensatory.

SIE.10:7 - Conformance Checklist

Apply the layer requirements below to the conclusion being claimed. A bounded failure or unresolved result needs sufficient evidence for that result; a positive use claim needs all of its load-bearing obligations covered.

  • The subject, receiving use, and conditions required by the conclusion are identified.
  • Known decisive evidence can finish a bounded failure or scoped gap; material unexamined premises remain distinct from passing ones.
  • Carrier/schema pass is not reported as semantic or receiving-use pass.
  • Endpoint/model adequacy includes examples and counterexamples for required distinctions.
  • Correspondence judgment and mapping execution are tested separately.
  • Every load-bearing identity disposition, issuer/authority condition, and unresolved branch is tested.
  • Claim composition tests include conflict, non-comparability, incomplete source, and source-claim recoverability.
  • Realization/interface tests cover currentness, failure, partial results, access/protection, provenance, and challenge paths as applicable.
  • Quality dimensions and thresholds are selected by the use and do not replace representative Work.
  • Positive, boundary, negative, unlike, and changed-source cases cover the material failure modes.
  • Whole-use disposition is pass, narrow, unresolved, or stop with no score-based compensation of hard stops.
  • Repairs, direct-owner returns, focused retests, affected consumers, and reopen conditions are explicit.
  • No external release, acceptance, authorization, effect, or universal correctness claim is implied.

SIE.10:8 - Common Anti-Patterns and How to Avoid Them

Anti-patternRepair
Valid schema, therefore valid integrationTest meanings, relations, identity, composition, mappings, provenance, quality, and receiving Work separately.
One quality/confidence scoreRecord layer-specific evidence and categorical dispositions; preserve hard stops.
Happy-path demonstrationAdd negative, boundary, unlike, changed-source, stale, conflict, and failure cases.
Provenance completeness means truthTest the source claim and receiving adequacy; provenance only makes derivation inspectable.
High alignment benchmark scoreValidate local endpoint relations and use loss against representative cases.
All-or-nothing readinessA known defect can finish a bounded failure. A positive subset result requires the contract’s permission and all premises on which that subset relies.
Semantic validation authorizes releaseReturn the account to the engineering, quality, safety, legal, or application authority.

SIE.10:9 - Consequences

Defects are localized to source, semantic, identity, composition, mapping, realization, interface, quality, or receiving-use layers. A bounded useful result can proceed without hiding excluded branches, and later changes can trigger focused replay through explicit dependencies.

The cost is several kinds of evidence and collaboration with domain and receiving practitioners. Some integrations that appear technically complete remain unresolved or stop because their identity, authority, or representative-use premises are missing.

SIE.10:10 - Rationale

Semantic integration is a claim chain. Different links require different evidence, and the receiver depends on their composition. Layered validation keeps the scope of each test result explicit. A positive conclusion requires support for every load-bearing premise of the claimed whole use or contract-permitted subset.

SIE.10:11 - SoTA-Echoing

The best-known line combines constraint validation, ontology-alignment evaluation, provenance, data-quality models, quality management, and user/task validation. The serious defaults are conformance-only testing and aggregate quality scoring. Conditions at different layers need their own evidence. Even when every condition is measured, a high score at one layer cannot offset failure of a required condition at another. SIE.10 combines these contributions in a dependency-aware account with categorical bounded dispositions and representative Work replay.

Source lineAdopt, adapt, or rejectRole and limit
SHACLadaptSupplies declared RDF graph constraint validation; passing shapes do not establish all semantics, identity, truth, or use fitness.
DQV and ISO/IEC 25012:2008adaptSupply quality vocabulary and a data-quality model; select dimensions and measurements by receiving action.
ISO 8000-61:2016adaptContributes data-quality management process questions; process conformance does not prove fitness of the answer for its receiving use.
OAEI 2025 resultsadaptProvide alignment-evaluation tasks and evidence; a local correspondence set still needs evidence for its intended use.
one conformance gate or aggregate scorereject as sufficientUnlike layers and hard stops must remain separately visible before a whole-use conclusion.

Reopen when a relied-on source, model, identifier, correspondence, composition, mapping, realization, interface, quality threshold, or receiving workflow changes; when new evidence defeats a layer; or when a representative case exposes an untested load-bearing obligation.

SIE.10:12 - Relations

  • SIE.1 supplies the receiving obligations, accepted loss, authority, representative cases, and stop rules.
  • SIE.2 supplies source meanings, editions, authority, provenance, access, currentness, and gaps.
  • SIE.4–SIE.9 supply the correspondence, identity, claim-composition, mapping, realization, and interface subjects and their branch contracts.
  • Current FPF A.10 and A.10.1 govern evidence/provenance reliance and generic affected-use discovery.
  • SIE.11 traces changed source, model, mapping, or interface premises to the receiving uses that rely on them. Matching earlier validation remains usable for unaffected results; material changes reopen the relevant premises and receiving interpretation.
  • Applications, Systems Engineering, quality, safety, legal, MDM, Data Engineering, and Operations owners consume the bounded account and retain their own acceptance, authorization, operation, and outcome decisions.

SIE.10:End

SIE.11 - Trace Semantic Change and Revalidate Affected Uses

Type: Method pattern Status: Stable Normativity: Normative method guidance within SIE; examples are constructed and non-normative.

Primary working result: qualified results for the semantic-integration uses affected by a changed premise; an AffectedSemanticUseRevalidationAccount@Change assembles them when a receiving use needs a common account.

SIE.11:1 - Problem Frame

Use this when a relied-on source definition, model commitment, identifier meaning, mapping premise, or interface interpretation changes and the integration’s continued use needs a decision. A familiar warning sign is an unchanged API field that now answers a different question.

Start by comparing the earlier and later meaning at the receiving question. A compatible documentation move can finish with a reference repair. A changed meaning can require repair or renewed validation of the integration results that relied on it.

The object is the affected semantic reliance and its consequences for receiving uses. The gain is a justified continuation, repair, narrowed use, or scoped unresolved result. To assert that all uses remain unaffected, establish adequate coverage of the relevant uses and their reliance.

Use the applicable domain Method directly for a known operational change that does not alter a relied-on source or semantic premise. If one already identified use is the whole question, resolve it with the relevant domain Method and retain the source, currentness and result-specific grounds that the use needs. Use A.10 when the source-to-use account is still implicit or needs to be made replayable. A.10.1 is needed when affected uses must be discovered across a scope.

SIE.11:2 - Problem

A source update can be treated as harmless because the schema still parses, or as universally disruptive because its version changed. Both responses miss which uses depend on the changed meaning. Some consumers use a definition that changed; others use a different proposition from the same source; still others are merely mentioned in nearby records.

Indiscriminate revalidation consumes work without settling those differences. An incomplete search can create the opposite error: one repaired mapping is reported as proof that the entire integration remains valid.

SIE.11:3 - Forces

ForceTension
SelectivityOnly affected reliance needs reopening, while hidden consumers can remain dependent on changed meaning.
ContinuityMatching earlier results save work, while changed assumptions can invalidate them.
CoverageA local answer can finish promptly, while a wider no-impact claim needs wider support.
AuthorityAn integrator can repair its mappings and interfaces, while source and receiving decisions retain their owners.
Evidence effortAdditional inquiry can change a decision, while unavailable or low-value information can consume the work needed for repair.

SIE.11:4 - Solution

Follow the changed proposition through semantic dependencies to the results and receiving uses it can alter. Complete supported branches at their proper scope. Assemble a wider account only for a receiver that needs it.

SIE.11:4.1 - Pattern-Use Unfolding

  1. Compare the relied-on meaning. Identify what the receiving question depended on in the earlier source or premise and what the later content says. Include changed applicability, subject grain, interval, assumptions, or limits where relevant. A notice from the definition owner can establish the continued meaning and applicability of a specified clause when accepted for this use. If the available evidence still permits different answers, identify the unresolved premise.
  2. Finish a compatible repair when sufficient. If the meaning and applicability remain adequate, retain the supported use. For a request to repair a reference or supply the new text, also establish that the intended reader can open the requested material under the relevant permissions. A version or URL change alone does not require every downstream Method to run again.
  3. Find affected uses when their scope is unsettled. Apply A.10.1 to discover which uses rely on the changed premise within the question’s scope, using source-side and receiver-side evidence or an index that adequately covers both. Distinguish a material dependency from a mention. Retain coverage gaps that limit the intended conclusion.
  4. Select the integration result that the change can alter. Use the domain returns below. Follow a further consumer only when the changed result can alter its action or claim. The physical proximity of files is not a dependency rule.
  5. Repair or revalidate that result. Apply its defining Method to the changed premise. Reuse earlier evidence whose conditions still match. Return a supported continuation, repair, permitted narrower use, or scoped gap. Source truth, master identity, product release, and application decisions go to the owners of those decisions.
  6. Return the completed branch. Give the receiver the result it needs, with the changed premise and remaining limits where those affect reliance. A completed direct result is sufficient for its own receiving question.
  7. Combine results when a receiver needs the wider answer. State the covered uses, their relevant results, unresolved uses or discovery gaps, and the continuation that those results support. A broader no-impact conclusion requires the corresponding coverage; completed local branches cannot supply unexamined ones.

When additional evidence is being considered, apply C.11.DUA to compare its attainable contribution to the receiving decision with its cost, delay, downside, and displaced work. A gap can remain a qualified gap when further inquiry cannot support a worthwhile next action; that limitation does not warrant a stronger claim.

SIE.11:4.2 - Domain Returns

Changed relianceIntegration result to revisit
A concept, relation, or model constraintSIE.3 model adequacy and any affected SIE.4 correspondence.
Identifier assignment, formation or resolution rule, entity grain or intervalFollow the changed premise to its direct users. Reassignment may affect one entry. A general rule may change the entries SIE.2 can resolve or the requests SIE.9 accepts and the SIE.10 tests for those requests. Reopen a SIE.5 identity disposition and its dependent uses when the changed premise supported that disposition.
Source-claim scope or interpretationSIE.6 composition, conflict, or non-comparability result.
A transformation premiseSIE.7 mapping and its affected outputs.
Availability, permissions, freshness, or service conditionsSIE.8 realization choice or SIE.9 receiving interface, according to the changed condition.
Receiving meaning or acceptance conditionSIE.9 interface contract and the corresponding SIE.10 validation.

This table locates the defining result; the dependency determines which returns are needed and their useful order.

SIE.11:4.3 - Record the Result

For a direct repair, use the result already needed by its consumer. For a common account, retain the following content at the scope the receiver needs:

Account positionReceiving content
Change and relianceEarlier relied-on meaning, later meaning, and the affected question.
Covered usesDependencies and the basis for the stated discovery scope.
Direct resultsCompleted repairs, revalidation, permitted continuation, or narrowed uses under their defining Methods.
Unresolved reachUnexamined or inaccessible reliance, discovery gaps, and their effect on the conclusion.
Continued useWhat the receiver can now rely on and which changed conditions would reopen it.

The account summarizes its constituent results.

SIE.11:4.4 - What Changes in Practice

The maintainer can say which interface meaning changed, which mapping or identity result was revisited, and what can continue. A corrected local reference can finish immediately. A broader claim remains bounded by the uses discovered and assessed.

SIE.11:5 - Archetypal Grounding

SIE.11:5.1 - Compatible Reference Repair

A publisher moves a vocabulary definition to a new documentation address. The integrator can access both the relied-on content and its new location. The definition, applicability, and access needed by the mapping remain compatible.

The integrator updates the reference used by that mapping. Its existing qualification still answers the unchanged question. That completes the reference-maintenance request.

Suppose the engineer cannot open the new definition, but an authoritative notice identifies the old and new editions and confirms that the definition and its scope are unchanged. The mapping may keep its qualification if that evidence meets its terms. To complete a working-link repair, also establish that the intended reader can reach the new text. Return a gap in meaning or in reader access to the owner of the affected result.

SIE.11:5.2 - Changed Promise Horizon

A provider changes availableToPromise from the reservation meaning used for present availability to a promise for a future horizon. The API field and its numeric type stay the same. The semantic-integration maintainer compares the two meanings and inspects how the consumers use the quantity.

UseReliance and result
Present-availability endpointIts mapping treated the quantity as answering “available now”. That premise changed. Repair the mapping and interface meaning, or withhold that answer until a qualified present-time source is supplied. SIE.10 checks the supported receiving result.
Future planning viewIt can use the new quantity when it exposes the horizon and the receiving question agrees. Validate those conditions instead of assuming that every use must stop.
Descriptive product catalogueIts definitions and product descriptions do not consume the changed quantity. Where that independence is established, retain its matching result.
A consumer with unavailable interpretationThe maintainer cannot determine how it uses the quantity. Return that scoped uncertainty; the other completed branches retain their own results.

If the service owner needs an integration-wide continuation decision, the account combines those results and the remaining uncertainty. It does not state that all uses are unaffected. The provider controls its source definition; the integrator controls the supplied semantic interface; each application owner determines whether the qualified answer is adequate for its decision.

SIE.11:6 - Bias-Annotation

LensLikely driftRepair
GovernanceThe integration maintainer appears to authorize the application’s decision.Return the qualified integration result to the receiving decision owner.
ArchitectureEvery linked component is treated as an affected consumer.Follow the changed proposition through dependencies that can alter results.
Ontology/EpistemologyAn unchanged field name is read as unchanged meaning.Compare the definition, applicability, and receiving interpretation.
PragmaticsAll validation restarts after every source version change.Retain matching results and finish sufficient direct repairs.
DidacticsA list of completed checks looks like complete coverage.State which uses the evidence covers and preserve unresolved reach.

SIE.11:7 - Conformance Checklist

  • The compared change concerns a premise used by an identified receiving question.
  • Compatible reference repair can complete without a wider account.
  • Discovery, where needed, supports the stated scope and distinguishes dependencies from mentions.
  • Each affected integration result uses its defining Method.
  • Each earlier result reused for this conclusion is valid under the conditions of the use under review.
  • Independently supported branches finish at their own scope.
  • A common account has a receiving use and preserves unresolved coverage.
  • A wider no-impact claim has support for the uses it covers.

SIE.11:8 - Common Anti-Patterns and How to Avoid Them

Anti-patternRepair
Schema compatibility as semantic compatibilityCompare the question answered by the field, including its horizon and applicability.
Every reference occurrence requires revalidationEstablish whether the result relies on the changed proposition.
One repaired branch clears the whole integrationBound the conclusion by discovered and assessed uses.

SIE.11:9 - Consequences

Supported uses can continue while affected branches receive focused repair. Dependency evidence becomes useful because it points to a changed receiving result. Local completion no longer waits for an unnecessary integration-wide account.

Finding hidden reliance and interpreting source changes can require domain and receiver participation. A wider assurance claim may remain unavailable while an actual consumer or later definition is inaccessible. The result preserves that limitation without erasing completed branches.

SIE.11:10 - Architectural Rationale

The changed proposition, rather than the changed carrier, determines semantic impact. Use the relevant domain methods to resolve each affected result. Discovery identifies where those questions arise. Keeping those contributions distinct permits reuse, independent completion, and limits on wider conclusions.

SIE.11:11 - SoTA-Echoing

The practice question is which receiving uses must change when one semantic premise has changed and the affected scope is still unsettled. In §5.2, both the present-availability endpoint and other consumers exist; knowing the changed field alone does not settle their reliance. The selected line combines A.10/A.10.1’s premise comparison and scoped discovery with the integration-specific returns in §4.2.

The serious alternative is a bounded full regression: identify the same receiving scope, update the tests to the new source meaning, and revalidate every registered use in it. This can be preferable when the suite is small and inexpensive or a reliable dependency analysis would cost more. It is not merely rerunning old tests against an unchanged schema.

Answer to the same multi-use horizon changeWork and evidence at the same scopeSelection and accepted trade-off
Discover changed reliance and revalidate affected resultsCompare the two meanings, inspect source-side and receiver-side dependencies, qualify coverage, and retest results that rely on the changed horizon. Keep applicable evidence for the independent catalogue.Adopt A.10/A.10.1 in §4.1.1–3/5–7; adapt §4.2 and §5.2 to semantic model, mapping, interface, and validation results. This avoids repeating the catalogue’s unrelated checks and lets supported branches finish. It spends effort establishing dependencies and leaves an inaccessible consumer unresolved.
Revalidate every identified use in the same receiving scopeMake the same meaning and coverage comparison, then execute the appropriate receiving-use checks for every member, including those ultimately found independent.Retain this alternative when those checks are cheaper or more dependable than selective impact analysis. It may reduce reliance on a detailed dependency model, but can repeat unaffected checks and delay a common release. It still cannot clear an unknown consumer or infer meaning from schema compatibility.

For the worked horizon case, the established catalogue independence and separable endpoint results justify selective revalidation. The accepted trade-off is the work needed to establish that independence and the explicit limit on the unknown consumer. §4.1.7 prevents local completions from being mistaken for a wider no-impact result. For one already known use, the direct domain result remains sufficient under §1.

LOT4KG supplies a current candidate line for changes that propagate between an ontology, mappings, graph content, constraints, and validation. Adapt those relationships in §4.1.4–5 and §4.2 when a KG realization is selected. They help locate which integration result needs work; they do not choose source truth, application action, or a universal regression policy. For other realizations, the same return question is answered from their semantic dependencies. Reject a changed version alone as evidence that every use failed, and an unchanged carrier alone as evidence that every use passed.

Reopen this comparison when an affected use was missed, when a dependency or coverage claim is defeated, or when the cost of qualifying selective impact exceeds the available full receiving-use regression. Reconsider only the affected discovery and checking choice in §4.1.3–5. Changed results still require their domain evidence whichever strategy is selected.

SIE.11:12 - Relations

  • A.10.1 governs affected-use discovery when the scope of reliance needs to be found.
  • SIE.2 supplies the source meaning, edition, authority, and access premises used in the comparison.
  • SIE.3–SIE.9 supply the domain results located in §4.2; SIE.10 supplies validation for the affected receiving claim.
  • SIE.12 supplies the module dependencies and material-change arrangements when participants depend on shared semantic modules.
  • Domain source owners, MDM, SYSE, operational providers, and receiving applications retain their respective decisions.

SIE.11:End

SIE.12 - Govern Modular Semantic Commons without Universal Authority

Type: Method pattern Status: Stable Normativity: Normative method guidance within SIE; examples are constructed and non-normative.

Primary working result: a ModularSemanticCommonsAccount@Community describing how actual users maintain and rely on shared semantic modules, their dependencies, decisions, and releases.

SIE.12:1 - Problem Frame

Use this when independently governed participants depend on shared semantic modules and need an arrangement for maintaining them. A typical failure is a changed shared term whose consumers cannot determine who could approve the change, which meaning their interface uses, or how to migrate.

Start with one module and the uses that depend on it. Establish its scope, who can decide its content and release, and how its users can obtain an identifiable maintained edition. The first useful result is an agreement through which those participants can make and use a concrete module change.

The object is the shared maintenance and reliance arrangement for semantic modules. The gain is continued reuse with explicit local commitments, contribution rights, dependencies, and change consequences. A compatibility claim covering additional users needs support for those users’ relevant reliance.

A team or a pair maintaining one interface can use its ordinary model and interface agreement when that suffices. A repeated file or shared repository alone does not establish a commons that needs this Method.

SIE.12:2 - Problem

Reusable semantic assets acquire users outside their original project. A term, class, relation, or mapping then carries assumptions into interfaces maintained by other participants. Changes can break those assumptions even when the shared file remains available.

One response is to require every participant to adopt one centrally controlled model. Another is to allow local changes without a recoverable relation to the shared meaning. Both can defeat useful reuse: the first can suppress necessary domain distinctions, while the second makes compatibility impossible to assess.

SIE.12:3 - Forces

ForceTension
Shared meaningCommon modules reduce repeated work, while participants retain distinct purposes and source authority.
Local developmentExtensions can answer local questions, while consumers need to know which shared commitments still hold.
Decision rightsMaintainers need power to release a module, while contact or repository access alone cannot establish that remit.
StabilityIdentifiable meanings support reliance, while mistakes and changed requirements need correction.
ParticipationOpen contribution can improve coverage, while unresolved proposals still need a usable decision path.

SIE.12:4 - Solution

Define the smallest shared module arrangement that serves the users who depend on the modules. Make its semantic scope, decisions, dependencies, and releases usable in their integration work. Preserve local modules and disagreement where convergence is unnecessary or unsupported.

SIE.12:4.1 - Pattern-Use Unfolding

  1. Identify the shared use. Name the users and questions that depend on the module. Locate the semantic content they share and the local distinctions they still need. If one interface agreement meets the need, complete that agreement through the relevant SIE Methods.
  2. Set module boundaries. State the module’s domain, concepts and relations, intended uses, material exclusions, and relation to local extensions. Use SIE.3 for content that needs model development and SIE.4 for qualified correspondences between different module meanings.
  3. Establish identification and dependencies. Choose namespaces or identification practices that let consumers recover the intended term or module meaning. Identify editions and the dependencies each supported use needs. A permitted version range must have a semantic compatibility basis for its claimed use.
  4. Assign the decisions and communication. State who may propose changes, decide module content, release an edition, resolve a disagreement under the community’s rules, and communicate with users. Record the scope of each responsibility. A source owner retains its source meaning and issuance authority.
  5. Make contribution workable. Give a proposer enough guidance to supply the changed meaning, rationale, examples, affected modules, and known consumer consequences. Route the proposal to whoever is authorized to decide it. Keep an unresolved disagreement explicit and permit a scoped local extension or alternative module when it can serve its users.
  6. Prepare the release for its consumers. Identify material semantic changes and use SIE.11 for affected reliance. Provide the edition, access, dependency conditions, and migration or deprecation information needed by those users. Distinguish a clarification from a changed meaning; preserve a way to identify the earlier meaning when consumers still rely on it.
  7. Notify and maintain at the agreed scope. Give affected users notice that permits the action required by their dependency and the community agreement. Maintain a responsive contact and a workable path for corrections. An urgent correction may require immediate qualified publication and notification; describe the resulting limits.
  8. Return the usable arrangement. Show how the named participants can obtain a module, propose a change, decide and release it, and interpret the effect on their supported uses. An unresolved decision right or dependency limits the part of the commons that can be claimed as governed.

These responsibilities can fit a small agreement for a small commons. Broader participation adds work only where additional semantic dependence or decision needs arise.

SIE.12:4.2 - Record the Result

Arrangement positionContent used by participants
Shared module and usersSemantic scope, supported uses, and the participants who depend on it.
Local relationshipExtensions, maintained correspondences, disagreements, and the commitments claimed across module boundaries.
Identification and dependenciesNamespaces or equivalent identifiers, recoverable editions, access, and dependency or compatibility conditions.
Decisions and communicationWho may propose changes, decide content, release an edition, resolve disputes and communicate with users, and the scope of each responsibility.
Change and continued useMaterial-change assessment, notices, correction, migration, deprecation, and maintained access needed by consumers.

Refer to existing module definitions and working agreements when they supply this content. The account makes the arrangement recoverable; it need not reproduce every module or introduce a separate record for each responsibility.

SIE.12:4.3 - What Changes in Practice

A user can identify the meaning and edition its interface consumes and find the decision needed for a proposed change. Maintainers can release a scoped improvement while preserving the commitments they claim to retain. Participants can keep different local meanings through explicit module boundaries and correspondences.

SIE.12:5 - Archetypal Grounding

SIE.12:5.1 - Equipment Classes Shared by Three Organizations

Two manufacturers and a service partner exchange service observations using a shared equipment-classification module. Each manufacturer also has local classes needed for its own products.

ArrangementConcrete use
Shared coreDescribes the equipment categories needed to interpret the service observations.
Local modulesRetain product-specific distinctions and identify their relation to the shared core.
CorrespondencesState the qualified relations between local and shared classes; different meanings remain visible.
Content decisionThe agreed maintainers decide changes to the shared module within its stated scope.
Release decisionThe participant authorized to release the module publishes an identified edition and its dependency conditions.
ContactA reachable participant receives questions, communicates decisions, and helps route disputes.
Source authorityEach manufacturer retains the authority for its product descriptions and issued source claims.

A participant proposes changing a shared class from “equipment with a replaceable drive” to “equipment serviced through a replaceable drive module.” The second definition changes the classification criterion. Existing service queries can depend on the first meaning.

For this constructed agreement, the maintainers retain the earlier class and introduce a distinct class for the new criterion. The illustrative identifier equip:DriveReplaceable continues to mean “equipment with a replaceable drive”; equip:DriveModuleServiceable means “equipment serviced through a replaceable drive module.” The second module edition contains both definitions and leaves the earlier edition accessible. It asserts no equivalence between the classes.

The manufacturers’ qualified product descriptions supply these discriminating cases:

EquipmentEarlier classNew class
X: its drive can be replaced as a separate part; it has no replaceable drive service module.Included: the drive is replaceable.Excluded: module replacement is not its service arrangement.
Y: its drive can be replaced separately, and the supported service arrangement also provides a replaceable drive module.Included.Included under the module-service criterion.

SIE.11 follows the changed classification need to the queries that use the classification. Two consumer outcomes complete the illustrative transition:

  • The service partner changes its receiving question to module-replacement planning. It adopts equip:DriveModuleServiceable, updates the relevant correspondence and query, and verifies that Y is included and X excluded. The receiving owner accepts that scoped result; SIE.10 validates its integration premises.
  • Manufacturer A retains its spare-drive query against equip:DriveReplaceable. Its required meaning and the qualified X/Y results remain unchanged, so it retains matching evidence for that use. Adopting the new class is not a prerequisite for continuing this query.

The participant authorized to release the module publishes the identified edition with those definitions, dependency conditions, and migration information. Contact supplies the notice; the content decision, product-source claims, and receiving decisions keep the separate remits shown above. The two completed consumer results do not establish migration by every other user. If the two manufacturers require incompatible local criteria, the commons can retain scoped local modules and their qualified correspondences.

SIE.12:5.2 - A Sufficient Interface Agreement

Two providers agree to expose separately attributed on hand and available to promise values. They have no additional users maintaining a shared module.

Their agreement identifies the meanings, source owners, interface responsibilities, and change conditions. SIE.3 and SIE.9 can supply the model and interface results. Those results complete the current need. A commons arrangement becomes useful if independently maintained shared modules and their users create a further maintenance problem.

SIE.12:5.3 - Urgent Semantic Correction

A shared mapping incorrectly interprets a quantity’s unit, and a supported interface can return a wrong answer. The authorized maintainer corrects or withdraws the affected mapping according to the community’s rules, identifies the affected edition, and notifies its consumers. The notice explains the correction and the supported continuation.

The completed action is an urgent qualified correction with notification. Earlier users’ unresolved reliance remains visible for SIE.11; the action cannot establish that every consumer has already migrated.

SIE.12:6 - Bias-Annotation

LensLikely driftRepair
GovernanceA listed contact is treated as the owner of every semantic decision.State content, release, dispute, communication, and source responsibilities and the remit of each.
ArchitectureA single large model replaces useful local modules.Start with the shared uses and retain local distinctions through scoped dependencies and correspondences.
Ontology/EpistemologyA stable label conceals a changed classification criterion.Compare meanings and examples; keep earlier and replacement meaning identifiable.
PragmaticsA small interface acquires unnecessary community machinery.Complete the local agreement when it meets the shared need.
DidacticsA version number is read as a guarantee of compatibility.State the semantic basis and receiving scope of compatibility.

SIE.12:7 - Conformance Checklist

  • The users’ reliance on the shared modules justifies the arrangement.
  • The shared scope and local extensions preserve the commitments they claim to use.
  • Consumers can identify the model meaning, edition, access, and applicable dependencies.
  • Proposal, content, release, dispute, contact, and source responsibilities are distinguishable where they matter.
  • A material change has a usable decision and affected-consumer path.
  • Identification, notice, migration, and deprecation follow the chosen rules and the consequences for the uses that depend on the module.
  • A local interface can finish without creating an unnecessary commons.
  • Unresolved rights or reliance limit the corresponding claimed arrangement.

SIE.12:8 - Common Anti-Patterns and How to Avoid Them

Anti-patternRepair
Shared repository treated as governanceEstablish who can make the decisions and which module dependencies the users need to maintain.
Contact metadata treated as decision authorityIdentify who may decide content and releases and at what scope.
Silent meaning replacementExpose the changed criterion, identification treatment, and consumer consequences.
Mandatory convergence of incompatible meaningsRetain scoped alternatives and the correspondences that have support.
Announcement treated as completed migrationDistinguish notification from each affected consumer’s result.

SIE.12:9 - Consequences

Shared modules can evolve while their users retain identifiable meanings and workable returns. Local development remains possible, and a community can decide changes without claiming authority outside its remit.

The arrangement costs maintenance, communication, and change assessment. Those costs increase with real dependency and participation. Some proposals remain local or unresolved when shared convergence cannot be justified.

SIE.12:10 - Architectural Rationale

A commons is useful through the semantic commitments its users share and the decisions they have the authority and practical means to make. Module boundaries preserve the scope of those commitments. Identifiable meanings and dependencies let users determine how a change affects their work; assigned rights let the relevant participants act on that result.

SIE.12:11 - SoTA-Echoing

The practice question is how the three independently governed organizations in §5.1 can change their shared equipment classification while keeping supported service queries interpretable. The selected line is a scoped shared core with separately maintained local modules, explicit dependencies, identifiable meanings, and assigned content and release rights. It adapts the OBO Foundry principles to these users.

A serious alternative for these same users is a jointly qualified release bundle: publish the relevant shared core and local profiles as one identified, compatible combination. This also preserves source authority and can retain older supported editions. It offers one combination to qualify instead of asking every consumer to select compatible module editions; it need not impose a universal ontology.

Arrangement for the same equipment-class changeComparable effort and gainSelection and accepted trade-off
Shared core with independently maintained local modulesExamine the same changed criterion, equipment counterexamples, mappings, and receiving queries. Qualify the affected module interfaces and state the editions each supported use can combine. An unchanged local module can remain on its supported basis.Adapt §4.1.2–3/5–7 and §5.1. Separate module maintenance preserves the participants’ local distinctions and lets a scoped change proceed without constructing another joint bundle. It requires explicit dependency and compatibility evidence; independent version numbers alone are insufficient.
One jointly qualified bundle of the relevant core and profilesUse the same meanings and cases and reuse unchanged component evidence, then qualify and identify the supported combination. Coordinate its release and continued support with the three participants.Retain this alternative when consumers need a common deployment combination or the participants can qualify it more economically than separate compatibility claims. It simplifies edition selection but adds joint-release coordination, including when only one component changes.

For §5.1’s independently owned local classifications, the modular arrangement is selected to preserve useful local change and scoped reuse. The accepted cost is maintaining compatibility and reliance evidence at the module interfaces. A joint bundle may be better when the shared receiving use requires it; fewer files or a central release number cannot decide the comparison. A pair needing only one interface remains the distinct sufficient-agreement case in §5.2, not the rival used to justify this commons.

Source and roleOperative move and transfer limit
OBO Foundry principles supply the selected commons-practice line.Adapt actual users, collaboration, modular reuse, and maintained access in §4.1.1–2/5/8. OBO participation criteria keep their community scope; they do not prescribe the release arrangement of these three organizations.
OBO term stability constrains either arrangement.Adapt §4.1.3/6 and §5.1 so a materially changed criterion remains distinguishable from the earlier meaning under the chosen identification rules. Reject silent replacement behind a familiar label.
OBO contact responsibility supplies a communication contribution.Adapt §4.1.4/7 to a reachable contact and mediation path. Assign content and release rights separately; contact alone establishes neither.
OBO change notice constrains continued reliance.Adapt §4.1.6–7 to actual consumer action and the community agreement. A community-specific notice interval does not settle another commons’ timing, and notification does not prove migration.
The public ISO/IEC 21838-1 scope supplies a possible common top-level basis.Adapt §4.1.2 only when that basis contributes needed coherence. It decides neither module maintenance nor the release and versioning arrangement compared above.

Reopen the arrangement comparison when one supported use requires a joint edition that separate compatibility claims cannot economically supply, when a mistaken module-dependency claim breaks a receiving query, or when changed participant rights prevent the selected release path. Reconsider the affected module combination and §4.1.3–7. A new local distinction alone does not require replacing the entire commons.

SIE.12:12 - Relations

  • SIE.3 develops or qualifies module content; SIE.4 establishes correspondences between different meanings.
  • SIE.5 retains identifier authority and grain when the use depends on identity.
  • SIE.9 supplies the receiving interfaces that consume shared modules.
  • SIE.11 follows material semantic change to affected results and users; SIE.10 supplies their integration validation.
  • Domain authorities retain source meanings and claims. A.3.1.MI contributes Method introduction or revision when the community is changing how it works.

SIE.12:End

SIE.13 - Construct a Semantic Integration for a Named Receiving Use

Type: Method pattern Status: Stable Normativity: Normative method guidance within SIE; examples are constructed and non-normative.

Primary working result: a SemanticIntegrationPackage@Use whose required semantic contributions, implementation and evidence support one receiving use together, or a bounded partial result, unresolved question or stop that states what the receiver can now do.

SIE.13:1 - Problem Frame

Use this when a query, decision or operation needs separately governed information to work together, but obtaining the individual meanings, correspondences or mappings still leaves the receiving answer unavailable. A team may already have good source inventories, a model, mapping rules and working endpoints. The remaining question is how to connect those results, obtain the missing contributions and make an answer usable under their joint conditions.

The working object is one semantic integration for a named receiving use. Its whole result is the connected package described in SIE.Reference:4: a use contract, source premises, warranted semantic relations and claim composition, mapping behavior, realization and interface, with validation of the claimed use. Identity premises and model development enter where the answer depends on them. The package can reference existing results; it need not be one document, database or graph.

Start with the action the receiver must be able to perform and the information that could change that action. Compare the available contributions with what that answer requires. This comparison helps you choose the next contribution and recognize when the connected result is sufficient.

Ordinary non-use. Use the individual Method when its result finishes the question: SIE.4 can settle one correspondence, SIE.8 can reject a prohibited realization, and SIE.10 can identify a decisive defect in a supplied interface. An already adequate package can be used without reconstructing it. SIE.13 is needed when those local results still have to be made usable together. It does not select product configuration, establish master-data authority, operate a pipeline, authorize a purchase or accept a physical inspection result.

SIE.13:2 - Problem

Local correctness does not compose automatically. A relation may be true but too lossy for the intended substitution. A mapping may preserve a meaning while consuming an identity disposition for another configuration. Two sources may be individually fresh yet concern different periods. Separately feasible retrievals may compete for one request allowance. A correct response can still be read as the wrong kind of claim.

The opposite failure is to treat the complete repertoire as a mandatory lifecycle. A practitioner repeats qualified source work, builds an ontology that already exists, or develops an excluded realization before answering a small question. This spends effort without supplying the missing connection.

Neither a list of completed tasks nor a collection of approved descriptions establishes a usable integration. Someone must determine which contributions the receiving answer depends on, whether their conditions match, what remains to obtain, and how the supplied result reaches the receiver.

SIE.13:3 - Forces

ForceWorking consequence
Sufficient answer and wider reuseThe present contract bounds construction; a useful local answer need not anticipate every future consumer.
Source autonomy and combined meaningPreserve source meanings and authority while establishing the relations the receiving use needs.
Reuse and changed conditionsReuse a qualified result where its premises still match; a familiar result under a different interval or permission can need reopening.
Local feasibility and joint performanceInclude shared limits and dependencies that no component can settle alone.
Useful partial result and misleading omissionNarrow only under the receiving contract, keeping excluded or unresolved branches interpretable.
Assurance and acquisition costObtain evidence that can settle the current claim; a decisive rejection can finish without completing unrelated positive checks.

SIE.13:4 - Solution

Construct the integration by working backward from the receiving answer and forward through the contributions that can supply it. At each connection, establish what one result permits the next operation to do, under which conditions. Obtain or repair the missing contribution, bring its result back into the combination, and test the claimed receiving use. Revisit only dependencies affected by a changed premise.

The organization is conditional. Several contributions may be available already; one result can expose a different question; and construction can end with a warranted stop.

SIE.13:4.1 - Establish what would let the receiver continue

Name the receiver’s question and the next action or judgement that the answer must support. Recover the required answer claims and the circumstances in which a partial, conflicting or unavailable answer is still useful. If these are unsettled, use SIE.1:4 to obtain the receiving-use contract. Otherwise use the supplied contract and reopen only a condition that no longer fits.

Distinguish the answer from its downstream authority. “These inspection observations concern this configured feature” can be a needed integration result; “release this product” remains an engineering or quality decision. This distinction determines which premises the integration must supply and which judgement remains with the receiving decision owner.

Compare the available result with that continuation. If it already suffices, return it with its applicable limits. If only one correspondence or one failed conversion matters, obtain that result from its Method and finish the bounded question. When the receiver still lacks a usable combination, retain the whole receiving need while identifying a smaller next contribution.

SIE.13:4.2 - Derive the required contributions from the answer

Take each answer claim that can change the receiving action and ask how it would be obtained. Follow it to the source meanings, represented claims, relations and transformations it relies on. For a query row, for example, recover why the selected records belong together, what each value means, which rule produces the output, and how an unavailable or incompatible input is represented. For a semantic exchange between organizations, recover the interpretation and use of each supplied statement. Choose how far to trace a dependency by varying the constituent, its enclosing assembly or the applicable time interval. Could the receiver have to act differently while the facts already established stay true? Follow the dependency that distinguishes those cases. Once a consistent binding exists, stop at the coarsest resolution that supports the required answer across the remaining possibilities. If the available claims admit no consistent binding, return the conflict.

Use the following returns where that dependency occurs:

The receiving answer depends on…Contribution to obtain or reuseWhat returns to the construction
A source’s meaning, applicability or authoritySIE.2:4Qualified source-local premises and the gaps that limit their use.
A distinction the available model may not expressSIE.3:4Sufficient model reuse, an extension or a different model, qualified for the required questions.
A relation between source meaningsSIE.4:4A warranted relation, difference or incompatibility, with its permitted operations and loss.
Records concerning the same entitySIE.5:4An identity disposition at the required grain and interval, retaining source identifiers and authority.
Several source claims contributing to an answerSIE.6:4A qualified composition, conflict, non-comparability or unresolved branch.
Executable extraction or transformationSIE.7:4Rules tied to those premises, including selection, conversion, absence, errors, loss and trace.
Obtaining and presenting the result in practiceSIE.8:4, SIE.9:4 and the implementation supplierA feasible realization choice, the implementation obtained from its supplier, and a receiving interface with defined interpretations.

Use a row when the answer depends on its contribution. For example, two already distinguished subjects can retain separately attributed claims without a cross-source identity merge. A qualified existing model can supply the required distinction without new model construction. A supplied mapping may already carry the relevant source and correspondence references.

For each required contribution, determine whether it is available under the needed conditions, unavailable, or not yet qualified. An inaccessible definition, a missing distinction, a false correspondence, a missing implementation and an incompatible access condition are different obstacles. State which dependent answer each obstacle prevents; do not reduce them all to “more data needed”.

Keep the account in the working material the participants can use. A short annotated query or mapping specification can be sufficient. A larger integration may need linked descriptions. Their form matters only insofar as the dependencies and unresolved questions remain recoverable.

SIE.13:4.3 - Make the connections valid for this use

Before consuming a result, compare its subject and conditions with the operation that will use it. Match the relevant meaning, entity grain, configuration or time, source and rule versions, authority, permitted loss and failure behavior. A report of an earlier inspection can support today’s decision when it covers the required subject, conditions and property and its use is permitted. Count the original inspection as work performed for this order only when it formed part of the job. An order commissioning a new inspection still requires that performance.

Keep these three questions distinct:

  1. What relation or claim is supported? A characteristic can concern a feature without being that feature. Two descriptions can concern the same feature while their claims conflict.
  2. What does that result permit here? A broader relation may support navigation but not value substitution. An accepted loss for an overview may be unacceptable for an inspection calculation.
  3. Can the required contributions hold together? A mapping qualified for one effectivity interval cannot borrow an identity judgement from another interval merely because the labels match.

When a connection fails, identify the premise that would have to change. Obtain a narrower warranted relation, a different mapping, an applicable source edition or an authorized change to the receiving contract. Preserve useful alternatives separately while their conditions differ. Do not combine one alternative’s semantics with another’s permissions or performance evidence.

The connected explanation should make a resulting branch understandable. If a claim is non-comparable, show the distinction that prevents comparison. If an input is not retrieved, preserve that absence through the mapping and interface. A missing source becomes neither a zero value nor evidence against that source’s claim.

SIE.13:4.4 - Choose and obtain the next missing result

Choose the next contribution by what it can change in the receiving answer, using the dependencies just recovered. Start with a known decisive constraint when it can exclude an option without further construction. Otherwise prefer an obtainable result that resolves a consequential uncertainty or enables the next required operation at a justified cost.

For example, an existing prohibition on replication is enough to reject a copied store. It does not reject a permitted live query. An unknown definition that determines whether two quantities may be compared can matter before implementing either comparison. If the definition cannot be obtained, decide whether the contract permits separately attributed claims or whether the dependent answer must stop.

Perform or request the work that obtains the missing result. State its receiving purpose, required distinction or behavior, available inputs and acceptance condition. Use the relevant SIE Method for semantic work and the practice that supplies the other work. A platform owner can establish the request allowance; an implementer can supply and test a query; a domain owner can settle a source definition. The integration practitioner connects those results but does not acquire the suppliers’ authority by requesting them.

On return, inspect the supplied result and its conditions against the dependent operation. A selected realization is not its implementation, and a specification is not evidence of that implementation’s behavior. If the contribution is still absent, retain the precise blocker. If it supplies the needed result, reconnect it and determine what remains for the whole answer. When the recipient already has enough to continue, stop expanding the work.

Necessary coordination is part of obtaining the result: establish who can perform the required work, with which access and means, and how the result will reach its consumer. Existing skills in parsing and databases may still leave nobody able to resolve a temporal-identity question. Supply that contribution or leave the dependent answer unresolved.

SIE.13:4.5 - Compare the complete arrangement and its permitted branches

Use SIE.8:4 to compare the viable ways of realizing the accepted mapping behavior and supplying the result. Bring the semantic dependencies and the shared conditions into that comparison. Include required trace, failure and recovery behavior in the workload. Query permission, replication permission and disclosure permission remain separate inputs.

Test the combined demand against each applicable limit. Count the distinct requests in one allowance window, including the retry behavior on which the service promise depends. For time, follow the operations that must finish before the receiver can act; parallel operations and serial dependencies have different effects. For storage or access, apply the conditions that govern what the arrangement retains or makes accessible. A common resource limit concerns the combination even when every component fits alone.

Keep a common source or derivation visible when several contributions rely on it. Agreement among results that share a premise is not independent corroboration of that premise. Likewise, several pairwise comparisons do not establish a condition over all contributions together.

If the proposed whole fails, compare the continuations the contract permits. A narrower answer must retain the semantic premises, trace, access and interpretation required for that answer. An authorized contract change or a different realization can reopen the choice. Dropping a required provenance contribution or quietly redefining completeness cannot repair the same promise.

A decisive failure can finish the comparison for one alternative. Stop the whole requested use only when that failure defeats every continuation still allowed by the contract, or when the needed continuation remains unavailable. Distinguish a known impossibility under the stated conditions from an unresolved option that would need another contribution.

SIE.13:4.6 - Supply the interface and establish the bounded use result

Use SIE.9:4 to specify and supply the interface that carries the qualified meanings and branches into the receiver’s work. Obtain the implementation needed by that interface and the selected realization. Develop their specifications together where their dependencies require it; a changed semantic or service condition returns to the contribution that supplies it. Check that the actual input and output behavior preserves the rules and that the receiver can interpret the result as intended. Depending on the use, the interface can be a query, service, exchange file or a documented human-facing view.

Use SIE.10:4 to validate the claim now being made. For a positive whole-use or contract-permitted subset conclusion, every load-bearing premise and required joint condition needs matching evidence. Reuse evidence whose subjects, versions, use and conditions still fit. One decisive conversion error can establish a bounded failure without testing unrelated layers; correcting it alone does not establish the full positive claim.

Return the answer, its disposition and its consequences for the receiver together. A qualified partial answer states what is covered and what remains unavailable. An unresolved answer states the missing result and the use it prevents. A stop identifies the obligation that failed and the change that could warrant reconsideration. A missing required record can settle a release refusal while the property that record would have documented remains open. A semantic integration result supplies a premise to the receiving decision; its authorization and outcome remain with the receiving owner.

SIE.13:4.7 - Reopen changed reliance and reconnect the result

Retain the dependencies needed to recognize a change that can alter the answer: the source meaning or edition used, identity and composition premises, mapping rule, access or resource condition, and receiving interpretation. Preserve them where their consumers can retrieve them, rather than copying an unexplained final value.

When one changes, use SIE.11:4 to determine the affected uses and obtain the contributions that must be revised or revalidated. A changed promise horizon may affect a purchasing interpretation and its mapping while leaving product descriptions usable. A changed gateway allowance may reopen realization and validation while leaving correspondence evidence unchanged.

Bring each affected result back into the combination and repeat only the comparisons and use checks whose premises changed. Check the new whole’s joint conditions; a local repair can move demand to a shared limit. Where the set of consumers is unknown, keep that reach unresolved instead of treating the known consumers as exhaustive. Use SIE.12 only when participants that depend on shared modules need common maintenance and decision arrangements.

SIE.13:4.8 - Keep the result inspectable

The result must let the receiver recover the answer and its allowed use, the relied-on semantic contributions, their operative connections, the realization and interface supplied, and the evidence for the returned disposition. Keep material missing contributions and change conditions visible. The package anatomy locates the supplying results; it need not be duplicated in a new record.

For a small use, links from the returned query rows to a contract, mapping and qualified source material can carry this account. For a larger use, maintained specifications and implementation evidence may be necessary.

SIE.13:5 - Archetypal Grounding

SIE.13:5.1 - Connect configured product meaning to inspection evidence

A quality engineer needs the QIF inspection plan and observations concerning AP242 feature F17 in released configuration R at effectivity E. The constructed contract in SIE.1:5 permits qualified rows with separately visible unresolved local-extension and unknown-unit branches. It retains the 24-hour observation window and two-second response limit. These are stipulated receiving conditions, not properties guaranteed by either standard.

Suppose the source owners have supplied applicable product and inspection definitions, and an available model can distinguish a configured feature, an inspection characteristic, a plan and an observation. A proposed mapping equates characteristic C17 with product feature F17. Executing that mapping faster would not supply the requested meaning. The next useful contribution is the relation judgement, not another platform trial.

SIE.4 establishes that C17 concerns a feature; it is not itself that feature. The proposed connection also relies on a QIF feature description and the AP242 feature description concerning the same feature at R/E. SIE.5 supplies that separate identity premise from the applicable source evidence. If this required identity cannot be established, withhold the dependent inspection answer. A similar label or an observation for another configuration cannot fill the gap.

The claim composition can now retain the product-definition and plan-applicability claims with their owners, and attach the qualified observation to the configured feature. SIE.7 specifies the selection by R/E, the warranted characteristic relation, unit conversion, trace and error branches. The mapping may expose an observation in a requested unit; it does not thereby decide that the product conforms.

Assume SIE.8 has selected a permitted realization and the implementer supplies it. The supplied test evidence must show the requested query, the observation-age and response conditions, and the required negative branches. SIE.9’s receiving view keeps an unknown unit visibly unresolved instead of returning a converted value. SIE.10 checks those behaviors and the semantic premises against the contract. Under matching positive evidence, the result is the qualified row set and the stated unresolved branches, not an engineering release decision.

The complete construction changed two connected operations: it replaced an invalid equality with a warranted relation and required a distinct feature-identity contribution before the join. The realization and receiving tests then exercised that corrected meaning.

Now let the released configuration change to R2. SIE.11 follows the change to the feature identity, plan applicability, selection rule and dependent query evidence. An unchanged unit-conversion rule can retain its qualification. The new configured answer remains unavailable until its affected premises and receiving behavior are supplied; the earlier answer can remain a qualified answer about R.

SIE.13:5.2 - A permitted incomplete provider answer under a shared limit

A purchasing receiver needs attributed availability claims from providers A and B. A means “on hand”; B means “available to promise”. The receiving contract permits an explicitly incomplete answer and does not permit treating the quantities as one interchangeable measure. Assume their required meanings, models and composition rules are already qualified.

Replication is prohibited, so SIE.8 rejects a copied store without building one. Live retrieval and immediate presentation are permitted. For the constructed arrangement, A needs four requests, B needs four, and the source and rule trace needs three. All distinct requests consume one gateway allowance of ten in the same window. The trace is required even for a partial answer; no requests are shared or counted twice; the contract accepts neither a copied cache nor deferral to another window.

The full result needs at least 4 + 4 + 3 = 11 requests before retries. Each pair fits, but the combination does not. The semantic premises can remain correct while this realization fails to supply the complete answer. More correspondence checking cannot remove that resource conflict.

An A-only answer requires 4 + 3 = 7 requests before retries. It is a candidate permitted continuation, not yet a positive use conclusion. The implementation must preserve the required trace and the agreed response, freshness and failure behavior; retries consume the same allowance. The interface must say, for example, A: 12 on hand at T; B: not retrieved under the request limit, with the required attribution and trace. It must not say 21 available, B: 0, or “complete provider comparison”.

If matching implementation and use evidence establishes those remaining obligations, SIE.10 can qualify the A-only branch. The receiver then decides what action an incomplete answer permits. If both providers instead become mandatory, the same seven-request branch no longer answers the contract. Return the stop and the needed change: an access-owner decision altering the allowance, or a demonstrated implementation reduction that preserves the meanings and trace.

If the allowance changes from ten to twelve, the full arrangement becomes possible on the stated minimum request count, but its retry and other service conditions still need comparison. Reuse unchanged semantic premises; reopen the affected realization and receiving-use evidence. These numbers are construction assumptions, not measured provider performance.

SIE.13:5.3 - An unchanged field with a changed meaning

An existing interface has been qualified for a source definition in which provider B’s available field states a present commitment. B later changes its definition to include quantities promised within seven days while leaving the JSON field and numeric type unchanged. A parser test can still pass.

SIE.11 traces the relied-on meaning to the composition, mapping and receiving interpretation. A request about immediate availability can no longer use the old substitution. Obtain a supported present-availability contribution, return an explicitly permitted non-comparable or incomplete branch, or stop that answer. A future-planning receiver may use the changed meaning after its own conditions and interface interpretation are qualified. Source identifiers and unrelated product descriptions need not be reconstructed merely because this claim changed.

The whole Method reconnects the repaired semantic contribution to the receiving use; notification alone leaves that work unfinished. If all that was requested was whether the old present-availability substitution remains valid, the bounded incompatibility result can finish without rebuilding an interface.

SIE.13:6 - Bias-Annotation

A common schema, a merged key, a populated store or a completed query can look like completion while hiding a changed meaning or an unsupported use. Compare the resulting claim with the receiver’s question and include a case that separates the tempting interpretations.

The requested integration can reflect one consumer’s needs while other affected consumers have different conditions. Recover the source and receiving authorities, and keep other consumers’ conditions separate. A contract change can justify a narrower answer only through the applicable agreement; the integrator’s preference for an easier result does not change that agreement.

Retain a dependency or distinction because it changes construction, interpretation, reliance or return after change. Reuse adequate explanations and evidence.

SIE.13:7 - Conformance Checklist

Recognize this problem when the receiver still cannot obtain an answer from otherwise useful local contributions. Check the claimed answer under the conditions of its intended use. A claim about a deployed service or a change in user performance requires evidence of that service or change.

  • The receiving continuation and its acceptable answer branches are explicit; an adequate supplied contract is reused.
  • Each required answer claim can be followed to its semantic premises and the operations that produce it.
  • For each operation, the input results warrant their use in that operation for the subjects and conditions in question. Correspondence, identity and claim composition have distinct roles.
  • The next missing result is chosen for its effect on the receiving answer, with an obtainable supplier or an explicit blocker.
  • The complete arrangement is compared under relevant shared limits, permissions, trace and failure conditions; local or pairwise feasibility is not substituted for that comparison.
  • The supplied interface preserves the qualified meanings, material absence and conflict branches, and the receiver’s required interpretation.
  • A positive use claim has evidence for every load-bearing premise and joint condition within its scope. A negative conclusion states the obligation it defeats and the reach left unexamined.
  • A partial answer is permitted by the contract and retains its own required premises. A changed premise reopens its dependent contributions and uses while adequate unaffected results remain reusable.
  • The result returns to the receiving owner without claiming that semantic integration grants downstream decision authority.

SIE.13:8 - Common Anti-Patterns and How to Avoid Them

Anti-patternWhy it changes the resultRepair
Twelve completed boxesIndependently completed contributions may use incompatible premises, while some boxes may be unnecessary.Work from the answer’s dependencies and inspect the connections the answer uses.
One common field means one common quantityThe carrier hides different source meanings or horizons.Retain source-qualified meanings and qualify the permitted composition.
A design stands in for its supplied resultA decision or specification can exist before the required behavior has been implemented.Obtain the implementation and matching behavior evidence, or keep that gap explicit.
Every pair fits, so the whole fitsPairs can each fit while the whole exceeds a shared limit or needs conditions that cannot all hold together.Compare the required contributions together under the same use and resource conditions.
Quiet partial successOmitted sources or provenance make the response look more complete or better supported than it is.Return only a contract-permitted subset, with its excluded branches and required trace.
Start everything again after a changeUnaffected meanings and evidence are discarded while the use that depends on the changed premise may still be overlooked.Trace changed reliance through SIE.11 and reconnect the affected results.

SIE.13:9 - Consequences

The practitioner can explain why the available contributions do or do not supply the receiving answer, choose the next useful work and return a supported branch. Source owners and implementers receive a concrete missing result rather than an undifferentiated request to “finish integration”. A later change can return to the contribution that matters.

The cost is maintaining enough dependency and condition information to support those choices. The Method is excessive when a supplied local result already finishes the question. The work grows with the dependencies that can change the receiving result. It supplies a way to construct and qualify an integration; obtaining inaccessible meanings, rights, implementation capability or authoritative decisions remains contingent on their suppliers.

SIE.13:10 - Architectural Rationale

The whole is organized around the receiving claim because that claim determines which distinctions and contributions are necessary. A list of source fields cannot determine permissible loss; a storage choice cannot determine identity; and a passed local test cannot determine whether another result may consume the tested premise.

Working backward exposes required contributions. Working forward checks whether those contributions yield the promised answer. Comparing their connections and shared conditions closes the gap between individual adequacy and whole use. Selecting the next missing result keeps that construction practicable when only part of the answer is unsettled.

The distinct local Methods remain useful: SIE.1 bounds the use; SIE.2–SIE.7 supply semantic and executable premises; SIE.8 chooses realization; SIE.9 supplies the interface; SIE.10 qualifies its use; SIE.11 follows change; SIE.12 helps participants decide who may change or release the shared modules they depend on and how to maintain them. Their actions can constitute parts of this construction when needed. None must be performed anew merely because it has a PatternID.

A linear project plan may organize one implementation, but it cannot replace these dependency and qualification judgements. A small integration can make the same connections through a short contract, qualified mapping and receiving test.

SIE.13:11 - SoTA-Echoing

The selected practice combines the use-led semantic construction developed in SIE.2–SIE.7 with realization, receiver interpretation and affected-use qualification. SIE.3 supplies model reuse or development where a distinction is missing; SIE.13 adds no requirement to develop an ontology or materialize a knowledge graph. The domain sources and their transfer limits remain in those supplying Methods.

One practical alternative is to fix a shared model and source set, complete their mappings and service, then validate the receiving query. This can support reuse across several consumers and provide a workable project plan when the shared meanings, applicability and joint conditions are settled. Compare it with the present construction at the same receiving question and available resources. In §5.1 the model is already adequate, but the correspondence and identity connection is still missing. In §5.2 completing the two-source implementation cannot overcome the ten-request allowance; a permitted partial branch can supply a useful answer. If both sources are mandatory, neither arrangement delivers without another contribution or changed condition.

Adopt sufficient shared models, mappings and implementation plans. Reject making their complete construction a prerequisite for every local answer. When an already qualified service answers the present question under unchanged conditions, reuse it directly. When its meanings, permissions or receiving branches change, obtain and reconnect the affected contribution.

The W3C Data on the Web Best Practices supplies relevant established guidance: choose formalization for the application (BP16), retain provenance (BP5), and communicate interface changes (BP26). Adapt these contributions to the named receiving use. Their publication and interface guidance does not by itself establish cross-source identity, semantic comparability or joint feasibility. The construction in §§4.2–4.7 combines those separately needed judgements.

Compare a graph or copied-store realization with live or hybrid access at the same receiving claim, semantic obligations, trace and service conditions through SIE.8. A store may support repeated queries; a live arrangement may preserve access to rapidly changing source-owned claims or avoid prohibited copying. Reject choosing either by technical preference alone. In §5.2 the permission excludes copying and the joint request demand changes the permitted answer.

The trade-off is explicit connection work where local results do not yet support the receiving answer, in exchange for avoiding both silent composition assumptions and an obligatory full lifecycle. Reopen that choice when an adequate supplied arrangement makes the work redundant, a new dependency defeats the current construction, or actual use shows that its coordination burden exceeds what the receiving question warrants.

SIE.13:12 - Relations

  • SIE.Reference:4–6 explains the whole result and combined arrangement; SIE.Reference:13–14 locates its supplying results and local entries.
  • SIE.1–SIE.7 supply the contract and semantic contributions under the conditions in §4.2. They remain directly usable for their own questions.
  • SIE.8 helps select the realization. Use SIE.9 to supply the receiving interface, obtaining the required implementations from their suppliers.
  • SIE.10 supplies bounded use validation. SIE.11 supplies affected-use returns after change; use SIE.12 when participants depend on shared modules and need arrangements for maintaining them.
  • FPF C.39 supplies general construction of a way to obtain a result; B.1.5 distinguishes Method composition, and B.1.5.EW distinguishes constituent performance in ongoing work. SIE.13 supplies the semantic-integration content of those connections.
  • Systems Engineering, Data Engineering, domain and source owners, and receiving decision owners retain the non-SIE results and authorities identified in SIE.Reference:16.

SIE.13:End

Cross-Pattern Application

The applications below show different uses of the repertoire. SIE.13 supplies the whole-construction Method; its grounding follows the missing contributions and changed conditions through to a receiving result. Individual Methods remain sufficient for their local questions.

SIE.Application:1 - APP-SIE-01 - AP242 and QIF product-lifecycle query

A quality engineer asks: “For released product-definition revision and configuration R, which QIF inspection plan and result concern feature F at effectivity E?” The AP242 and QIF sources use different models and identifiers. SIE may connect their qualified claims; Systems Engineering and authorized quality Work retain configuration, release, applicability, and acceptance decisions.

The application uses the repertoire as follows:

ContributionConstructed application result
SIE.1The constructed contract in SIE.1:5 names the engineer, workflow, answer columns and effectivity. It supplies the 24-hour QIF observation window and two-second response limit and permits qualified evidence with separately visible unresolved local-extension and unknown-unit branches. Authority, negative cases and stops remain explicit.
SIE.2A source inventory records AP242:2025 edition 4 at stage 90.92, “to be revised”, the applicable QIF edition, source models, identifiers, configuration/effectivity meanings, owners, and unresolved local extensions.
SIE.3, when neededQualify an existing model, or extend it to distinguish an inspection requirement from an observation of the applicable configured feature. The plan and an observation of another configuration provide counterexamples.
SIE.4Correspondence rows distinguish product feature, inspection characteristic, plan applicability, configuration, and result relations; unsupported equivalence and incompatible-feature rows remain explicit.
SIE.5Establish that the QIF feature reference and the AP242 feature description designate the same feature at the required revision, configuration and effectivity. Retain each identifier with its issuer and assignment context. The plan separately assigns the inspection characteristic to that feature.
SIE.6AP242 definition/effectivity claims and QIF plan/result claims are composed with source, interval, authority, and conflict branches preserved.
SIE.7Executable rules select the released configuration, map accepted endpoint relations, preserve identifiers, reject unsupported joins, and trace every output row to its premises.
SIE.8A virtual or hybrid realization is selected against freshness, access, latency, provenance, and recovery.
SIE.9The receiving interface returns matched, unmatched, incompatible, stale, and source-error branches with their interpretations and provenance.
SIE.10Layered tests cover carrier/schema, source semantics, correspondence, identity/effectivity, composition, transformations, provenance/currentness, quality, and the representative query. SIE.10:5.1 applies the stated freshness, response and partial-answer criteria while keeping excluded branches visible.

The constructed package returns the qualified rows with the unresolved local-extension and unknown-unit branches the quality engineer agreed to receive separately. It also identifies unmatched or incompatible results. For two identified objects, an incomplete plan can leave their assignment open. If the order needs that assignment, obtain the complete applicable plan or report the missing answer to the recipient. Issuing an incomplete set in its place requires the recipient’s agreement. The complete plan can establish that there was no assignment at the stated revision. It stops if configuration/effectivity or feature identity is unresolved, a load-bearing source edition cannot be qualified, a conflict is hidden, or the receiving query fails. It supplies evidence to the applicable SYSE.7, SYSE.13, SYSE.14, or quality owner; it does not choose the released revision or accept the inspection result.

SIE.Application:2 - APP-SIE-02 - Semiconductor identity and traceability

A recall-triage query crosses SEMI device/substrate identifiers, GS1 events, supplier identifiers, and enterprise master data. The package preserves wafer, die, device, package, lot, and event grains. SIE.5 records same, different, part, version, variant, alternate, or unresolved dispositions with each scheme and issuer. SIE.6 retains event time, source authority, contradictory events, and absent links. SIE.10 tests positive, reused-identifier, split/merge, contradictory-event, and missing-link cases.

A packaging event can trace a constituent die to a serialized device and thence to its lot. Preserve the wafer coordinate and the device serial with the relations they record. If both entries designate the very same unit under their source rules, retain both identifiers for that common referent. Reuse of a package code leaves the exact history open. Establish that at least one history fits the accepted events. If every such history leads to the same lot, the interface can return that lot. Conflicting mandatory records that fit no history establish a conflict. Histories leading to different lots leave attribution open. Apply the recipient’s disclosure limits in each return. MDM and domain stewards retain authoritative identity and value decisions; quality, safety, and recall authorities retain action.

SIE.Application:3 - APP-SIE-03 - End-to-end quality and provenance

A data pipeline is syntactically healthy, yet an analytic may be unsafe because a source version is stale, a unit conversion is wrong, a default hides absence, a mapping omits one category, or derivation is missing. The contract selects only quality dimensions and thresholds that can change this use. The source manifest and mapping specification expose versions, units, defaults, error branches, and provenance. The claim composition keeps governed inputs and contradictions visible. Validation can return a usable subset, an explicit failure, or an unresolved measurement need.

A mapping that returns 1 millimetre for an input of 1 metre fails the required conversion to 1000 millimetres. That probe can finish a bounded failure; unrelated layers remain unexamined. Conversely, an unchanged JSON field can carry a new future-horizon meaning while the receiver still reads “available now”. Its structural pass cannot preserve the earlier use claim.

For a positive whole-use or permitted subset result, SIE.10 covers every load-bearing premise, including receiving interpretation, with new or matching earlier evidence. Pipeline defects return to Data Engineering, mapping defects to SIE.7, and source defects to their owners. A quality vocabulary or process certificate cannot supply missing evidence for the receiving claim.

SIE.Application:4 - APP-SIE-04 - High-change provider availability without a materialized graph

Two providers expose current availability through governed APIs. One field means “on hand”; the other means “available to promise”. Neither permits replication. The contract requires a purchasing comparison with timestamps and explicit incomplete results. SIE.4 keeps the meanings distinct and accepts only narrower qualified relations. SIE.6 composes rows where supported and returns non-comparability otherwise. SIE.8 excludes copying the restricted values. For this order suppose the live sources for both metadata and values can meet the buyer’s deadline, trace and failure conditions. Query-time mapping is then one workable choice. In the variation in SIE.8:5 the live metadata source is unavailable throughout the decision window, and a permitted current copy enables a hybrid. The excluded copying alternative needs no implementation, recovery, or exit design. The interface exposes timeouts, source errors, timestamps, and incompatible rows.

SIE.3 can finish by reusing a model that distinguishes the two quantities, their attribution, unit, time, and horizon. If a provider later changes its promise horizon, SIE.11 finds which mappings and receiving interpretations depend on that meaning; unaffected product descriptions can retain their qualification. The purchasing application decides what to do with incomplete or non-comparable results.

SIE.Application:5 - APP-SIE-05 - A Modular Equipment-Classification Commons

Two manufacturers and a service partner share equipment classes to interpret service observations. Local modules retain product-specific distinctions; qualified correspondences state how they relate to the shared core. SIE.12 identifies the participants using the shared classes, module scope, dependencies, content and release rights, and contact.

A proposal changes a shared class’s criterion from equipment with a replaceable drive to equipment serviced through a replaceable drive module. Examples show which equipment changes classification. The authorized maintainers decide the shared content; the community’s identification rules keep the earlier and replacement meanings recoverable. In the worked disposition, the earlier equip:DriveReplaceable class keeps its meaning and the new equip:DriveModuleServiceable class receives a distinct identifier. SIE.11 follows the change to affected service queries and local correspondences. The service partner’s module-planning query adopts the new class: equipment X with only a separately replaceable drive is excluded, while equipment Y with the supported drive-module service arrangement is included. Manufacturer A retains its spare-drive query and matching evidence under the earlier class. The identified release keeps both meanings recoverable and supplies the migration and notice those users need; these two results do not establish every user’s migration.

The contact communicates and routes questions. Source owners retain their product descriptions; consumers decide whether a module edition supports their use. Incompatible local criteria can remain in scoped modules with supported correspondences. A pair that needs only one availability interface can finish its model and interface agreement without creating this commons.

SIE.Application:End

Semantic Integration Engineering Principles Framework Sources and Edition Notes

SIE.Sources:1 - Source use and currentness

Each pattern explains which action a source informs, the qualifications on that use and the limits of the source’s 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 Core Method-development patternssituational criteria and the separate repertoire, variant, introduction, and revision Methods in C.39.RP, A.3.1.MV, A.3.1.MI and C.36.MCSIE 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.

SIE.Sources:2 - Edition return

Semantic Integration Engineering Principles Framework — 21 November 2026 identifies this edition with thirteen pattern bodies, their stated status, and the shared reader account. The publication supplies practitioner guidance and constructed examples. An implemented service, maintained commons, or receiving decision needs the corresponding work and evidence.

The Architectural Reference explains the connected language and the consequences of these sources for its use.

SIE.Sources:End