tegwick
6ae63977e7
Assistant: codex Assistant-Model: gpt-6-astra Assistant-Session: 01a087be-d842-7252-81be-2105c4279c87
62 lines
6 KiB
Markdown
62 lines
6 KiB
Markdown
# Upstream ownership and mapping
|
|
|
|
InfoTechCanon supplies shared semantics through the model's
|
|
[import manifest](../models/interface/imports.json). FIAM supplies the specialized
|
|
architecture vocabulary through its [source manifest](../assimilation/fiam/sources.json).
|
|
These mappings implement the accepted dispositions in InfoTechCanon's
|
|
[boundary acceptance record](../../../info-tech-canon/infospace/interfaces/interface-canon-boundary.md)
|
|
at commit `f921e5a543db8da49781bd560d303f780623d204`.
|
|
The [acceptance manifest](../reviews/acceptance/info-tech-canon-sources.json)
|
|
pins that exact Git blob; the sibling link is navigation to the current owner copy.
|
|
InfoTechCanon definitions and FIAM semantics remain unchanged. Compatibility
|
|
means explicit, compatible scopes; distinct concepts need not share one definition.
|
|
|
|
| FIAM/domain term | Shared owner or disposition | Mapping boundary |
|
|
| --- | --- | --- |
|
|
| Port | FIAM contract participation; ITC-NET retains network Port | Distinct meanings: a FIAM Port offers/requires a contract; network profiles distinguish physical/device ports from protocol-level transport ports. Neither is a universal alias for FIAM Port. |
|
|
| InterfaceContract | Interface-domain meaning derived from FIAM; ITC-LAND retains Interface seed | Semantic agreement over operations. Landscape Interface and Network attachment-point Interface are contextual mappings, not universal exact aliases or inferred subtype relationships. |
|
|
| Endpoint | ITC-LAND/ITC-NET shared context; FIAM-qualified usage | Locates or selects a Binding. Related to Network Endpoint for network realizations, but local bindings need not have a network endpoint. A resource selector identifies information within its provider scope instead. |
|
|
| Information Resource / Information Shape | FIAM interface-domain roles; ITC-DATA retains Dataset, DataObject, Record, DataType, Constraint | Contextual alignment according to addressed state and admissible form; no universal subtyping or exact equivalence. Detailed schema content stays in describing artifacts. |
|
|
| Representation | FIAM participation encoding; ITC-DATA retains value-level Representation | Qualify the scope: JSON is an encoding for shape participation; boolean or integer describes a value-level form. Encoding does not determine semantic type or shape identity. |
|
|
| Participant / SystemNode | Align with ITC-LAND SoftwareSystem/SoftwareComponent where applicable | No blanket equivalence to Actor, host, process, or deployment; choose by modeled scope. |
|
|
| Entity identifier | ITC-IDENT Identifier / Scoped Identifier | FIAM identifier syntax alone does not establish global identity. |
|
|
| same-entity-as | Relate to ITC-IDENT Synonymity Assertion | FIAM query-time equivalence has specific evidence constraints; no destructive merge or automatic cross-canon equivalence. |
|
|
| Assertion | ITC-GOV Assertion | FIAM specializes architectural property/relation assertions with evidence and polarity. |
|
|
| FIAM evidenceRecord | Map to ITC-EVID Evidence plus Evidence Source | FIAM evidenceRecord is support metadata with source, mode and confidence. ITC Evidence is an assertion drawn for a question; source container is separately identified. This is not a one-to-one rename. |
|
|
| Evidence score | ITC-EVID Evidence strength | A FIAM Lens computes a policy-specific heuristic; confidence and support scores are not universal truth probabilities. |
|
|
| Artifact / KnowledgeArtifact | FIAM describes/implements roles; ITC-INFOSPACE retains KnowledgeArtifact | A describing document carrying reusable knowledge may qualify as KnowledgeArtifact. Merely implementing a contract does not establish that classification. |
|
|
| Evidence Source / Evidence | ITC-EVID shared meanings; FIAM assertion/support mapping | Evidence Source is an addressable container, with relevant version or capture where mutable. Evidence is a separate assertion drawn for an explicit interest. A FIAM evidenceRecord's support metadata is not automatically that ITC assertion. |
|
|
| Zone / security profile | Reference FIAM contextual classifications | No transfer of generic network, security, trust, tenant, or authorization ownership. |
|
|
| Policy / decision | ITC-GOV Policy / Decision | A Lens finding is an interpretation, not automatically a governed decision or authorization. |
|
|
|
|
Port, Contract Participation, Operation, Binding, Channel, Interaction,
|
|
Interaction Flow, Information Resource, Information Shape, Resource Selector,
|
|
Facet, Representation, and Lens receive FIAM-derived interface-domain definitions.
|
|
Names that overlap other ITC models remain qualified as `interface-model:*`;
|
|
this initial import set is not an exhaustive federation ownership audit.
|
|
|
|
The [2026-09-09 review](review-2026-09-09.md) resolves local usage boundaries
|
|
against ITC-DATA, ITC-INFOSPACE, and ITC-NET. FIAM Port differs from network Port;
|
|
Information Resource/Shape and Representation have scoped mappings to Data;
|
|
describing artifacts may qualify as KnowledgeArtifact. These are qualified
|
|
mappings, not automatic equivalence or ownership transfers.
|
|
|
|
The initial review is complete. External federation acceptance and scoped consumer adoption are recorded in
|
|
completed INTERFACE-WP-0004; publication stays draft.
|
|
|
|
## Owner-review clarifications
|
|
|
|
Network Port covers physical/device ports as well as protocol-level transport
|
|
ports; the TCP example is illustrative, not exhaustive. Resource/shape mappings
|
|
establish neither universal subtyping nor exact equivalence. Describing artifacts
|
|
may qualify as KnowledgeArtifact; implementation artifacts do not qualify merely
|
|
because they implement a contract. Evidence Source is the addressable container,
|
|
with version/capture where mutable; Evidence states the assertion and explicit
|
|
interest. These clarifications preserve the imported source meanings.
|
|
|
|
Acceptance scope and source revisions are recorded in the
|
|
[acceptance report](../reviews/acceptance/README.md). Earlier owner reviews target
|
|
0.1.1; the local clarification revision is draft 0.1.2.
|
|
|
|
The [focused follow-through](infotech-follow-through.md) traces each clarified
|
|
meaning to the checked examples and pinned FIAM evidence.
|