Page Comparison

During the discussion on the last session, it became abundantly clear that there is enough interest for the full Interop API capability in addition to the Intents. It is also became clear that it is indeed confusing (and perhaps wrong!) to have them blended into a single API.

To that end, we would like to ask for some time on the session tomorrow for Leslie & myself to introduce a new proposal. We’ll be also withdrawing our prior PR as no longer relevant.

Leslie:

• Intent is a form of interop; for us we are talking about an interop that service discovery, request/response, streaming; mistake to add them to the current intent API
• Is a cross-platform interop API useful? If it useful, does it belong in FDC3?

Leslie offered up that Svyatoslav Kryukov should talk through the API and that "most of the discussion will happen in discussion chains in confluence or on githug ...  rather than (us) try and squeeze that in here"

https://github.com/FDC3/API/pull/15

Nick walked through the PR on the WebEx

Nick: There are only so many desktop agents; may be difficult to try and get in and standardize interoperability of what are often very proprietary. Think of this a bit like websockets and how it layered on top of HTTP. The other, layered on top standard creates a richer experience.

Leslie: An application is owned by a desktop agent -- that is a big difference of approach.

Nick: another difference is starting with loose coupling to a higher coupling rather that a tight coupling that can downgrade.

Slava: We can think of an interop like a standard alone browser but there will not be the central broker and apps will be peer to peer -- extending that would be more good than bad.

Nicholas Kolba

Brian Schwinn