[Open Question] Relationship to incumbents — referencing FIX / SWIFT / ISO 20022 so adoption is additive

[oa-sarvesh]

Context

OTAS positions itself as an interface layer analogous to FIX, SWIFT, and TCP/IP (Whitepaper §2.2) — governing the seams between institutions rather than replacing their infrastructure. Post-trade institutions already run on FIX/SWIFT/ISO 20022, and any standard that requires ripping those out will not be adopted.

The question

How should OTAS primitives reference, rather than replace, FIX / SWIFT / ISO 20022 so adoption is additive?

How to contribute

• Map the canonical event schema (§5.2) to the nearest ISO 20022 message components (e.g., sese settlement messages) and FIX post-trade workflows.
• Identify where an OTAS event should carry an ISO 20022/FIX correlation identifier so legacy and tokenized legs reconcile.
• Share adoption lessons from prior bridge efforts (ISO 20022 migration, FIX-to-DLT pilots, SWIFT tokenization experiments).

Reference: Whitepaper §2.2, §5.2, §6.4.