FDC3 Identity & Threat Modelling -11 April 2024 about fdc3

[kriswest]

The only fly in this ointment is that it reduced the expressivity of the raise, since you can't (say) raise "ViewNews" with an fdc3.instrument anymore.

Is there a way around that?

Yes, that request context can wrap another, which could be any type of context. See fdc3.transactionResult for an example of an existing context that does that: https://fdc3.finos.org/docs/context/ref/TransactionResult

[robmoffat]

Rob / FINOS ♟️

[Yannick-Malins]

Yannick / Symphony

[hughtroeger]

Hugh / FactSet

[paulgoldsmith]

Paul Goldsmith / Morgan Stanley

[kriswest]

Kris West / interop.io 🚀

[robmoffat]

Regarding the diagram above:

The way to get hold of a PrivateChannel I think is limited to just raising an intent with an IntentResult that contains the private channel.

So, what you're saying is, when you raise the intent, the Context you send has to be this special type fdc3.encryptedChannelRequest?

The only fly in this ointment is that it reduced the expressivity of the raise, since you can't (say) raise "ViewNews" with an fdc3.instrument anymore.

Is there a way around that?