| Shared labels across contexts are not enough. | Terminology and ontology practice distinguishes objects, concepts, definitions, designations, and typed relations. | ISO 704:2022; ISO 1087:2019; ISO/IEC 21838-2:2021 (BFO). | F.9 resolves exact local senses and tests a direct relation instead of using string equality. | Adopt typed term, concept, and relation discipline. |
| Viewpoint boundaries remain explicit during reuse. | Architecture-description practice distinguishes entity of interest, description, viewpoint, view, model kind, concern, and correspondence. | ISO/IEC/IEEE 42010:2022. | F.9 keeps relation, use claim, card, view, and publication separate. | Adopt boundary-explicit correspondence. |
| Metadata and validation do not create use authority. | Web-data practice separates metadata, provenance, constraints, validation, and exchange from the governed data and act. | W3C Data on the Web Best Practices (2017); W3C SHACL (2017); W3C DCAT v3 (2024). | Evidence and packaging can support a bounded-use claim but do not make a Bridge obtain or grant permission. | Adapt provenance and validation discipline. |
| Interoperability is not semantic identity. | Terminology and controlled-vocabulary practice separates concepts from designations and distinguishes mapping relations instead of treating every mapping as identity. | ISO 704:2022; ISO 1087:2019; W3C SKOS Reference (stable mapping-relation baseline, not current-best SoTA). | F.9 tests exact relation semantics and then judges each proposed use separately. | Adapt only the term, concept, and typed-mapping distinctions; the use-specific judgement is FPF-native. Reject shared spelling, a generic mapping, or interchange success as proof of identity or suitability. |