Description
Group overview
There are currently 13 open issues in the FDC3 repository, under consideration for the 2.0 release, that relate to the existing concept of channels (both the 'system channels' used via the desktop agent API, and 'app channels' interacted with through the Channels API) and new concepts we've discussed introducing: transactions (a standardized way to make a request and receive a response back) and feeds (a standardized way to request a stream of data, such as a pricing stream).
Relevant issue tags
Current open issues that relate to the above concepts with the label:
Meeting Date
Thursday 9th Aug 2021 - 9am EDT / 2pm BST
WebEx info
- Meeting Link
- Meeting number: 127 494 1096
- Password: 3cqFgG7fMT2
More ways to join
- Join by video system:
- Dial [email protected]
- You can also dial 173.243.2.68 and enter your meeting number.
- Join by phone
- +1-415-655-0003 US Toll
- +44-20319-88141 UK Toll
- Access code: 127 494 1096
Meeting notices
-
FINOS Project leads are responsible for observing the FINOS guidelines for running project meetings. Project maintainers can find additional resources in the FINOS Maintainers Cheatsheet.
-
All participants in FINOS project meetings are subject to the LF Antitrust Policy, the FINOS Community Code of Conduct and all other FINOS policies.
-
FINOS meetings involve participation by industry competitors, and it is the intention of FINOS and the Linux Foundation to conduct all of its activities in accordance with applicable antitrust and competition laws. It is therefore extremely important that attendees adhere to meeting agendas, and be aware of, and not participate in, any activities that are prohibited under applicable US state, federal or foreign antitrust and competition laws. Please contact [email protected] with any questions.
-
FINOS project meetings may be recorded for use solely by the FINOS team for administration purposes. In very limited instances, and with explicit approval, recordings may be made more widely available.
-
A Discussion Group has no direct decision-making power regarding the FDC3 standard - rather it is intended that anything they propose or work on will result in proposals (via Github issues and PRs) for the Standards Working Group participants to consider and vote on for inclusion in the standard. As such, participation in a Discussion group is not required for contributing to any particular issue or FDC 2.0 as a whole.
Agenda
- Convene & roll call, review meeting notices (5mins)
- Review action items from previous meeting (5mins)
- Channels, Feeds & Transactions Discussion group meeting 12 Aug 2021 #444
- Votes still open (until shortly after next SWG meeting)
- Clarify how apps should handle broadcast and receipt of multiple context types #434 (20mins)
- Further work on Make it possible to return data from a raised intent #432 (20mins)
- Volunteers needed (5mins)
- PR Contributors and Editors
- @kriswest Support raiseIntent without a context #361 (update PR Support raise Intent without a context #375)
- @kriswest fdc3.joinChannel docs should explain expected behavior on joinChannel #418 (Documentation only)
- @kriswest Documentation for raise intent only describes the case with a specified app #426 (Documentation only)
- @kriswest Make optional: fdc3.joinChannel and fdc3.leaveChannel #431 (Documentation only)
- @mattjamieson Method.ts addContextListener signature was not updated for 1.2 and it overrides types for Desktop Agent #435 (Update methods.ts)
- Remove concept of 'global' channel, context broadcast should always be opt-in #308 (remove deprecated content from documentation and spec)
- All DesktopAgent and Channel APIs should be async #362 (minor API changes + documentation)
- Rename 'System Channels' 'User Channels' #430 (rename functions + create alias' for backwards compatibility + documentation)
- Make it possible to return data from a raised intent #432 (PR(s) for final proposal(s)
- Improve spec and documentation of
fdc3.addContentListenerto mention joining channels #451 (Documentation only)
- Reviewers needed
- PR Contributors and Editors
- Next meeting agenda, AOB & Adjourn (5mins)
Minutes
- Two issues discussed and brought to a conclusion ready to prepare PRs for the Standards Working Group to review:
- Clarify how apps should handle broadcast and receipt of multiple context types #434 (Rapid-fire broadcast all context types you want other applications to respond to, Rather than expecting them to extract types they want)
- Make it possible to return data from a raised intent #432 (preferred proposal chosen)
- Some discussion of whether we should add support for flagging 'experimental' features in the FDC3 specification to make it clearer that such features may change in future based on industry feedback.
Decisions Made
- Clarify how apps should handle broadcast and receipt of multiple context types #434
- Improve recommendations for broadcast context single vs. multiple types (for composite types) in the docs and specification
- consensus that apps should broadcast all the types that they expect other apps to respond to (allows use of typed context listeners for filtering)
- Make it possible to return data from a raised intent #432
- consensus that the updated 'option 2' proposal is workable and appropriate (if not yet proven in use)
- will go to PR and not back on agenda
- update return type from
Promise<any>toPromise<Context> - a separate issue should be raised to add support to the appD (and perhaps also to
findIntent) to express what context types an app should return
- happy to extend discussion group to another 4 meetings
Action Items
- @agitana Assign @pbaize to handle All DesktopAgent and Channel APIs should be async #362
- @kriswest Remind SWG about open votes before next meeting
- PRs and Reviews
- @kriswest Support raiseIntent without a context #361 (update PR Support raise Intent without a context #375)
- @kriswest fdc3.joinChannel docs should explain expected behavior on joinChannel #418 (Documentation only)
- @kriswest Documentation for raise intent only describes the case with a specified app #426 (Documentation only)
- @kriswest Make optional: fdc3.joinChannel and fdc3.leaveChannel #431 (Documentation only)
- @kriswest Make it possible to return data from a raised intent #432 (Create PR for final proposal @thorsent posted)
- @kriswest Clarify how apps should handle broadcast and receipt of multiple context types #434 (Documentation only, Add spec recommendation to rapid fire multiple contexts, and desktop agent should not auto-rapid fire - progress to PR)
- @pbaize All DesktopAgent and Channel APIs should be async #362
- @mattjamieson Method.ts addContextListener signature was not updated for 1.2 and it overrides types for Desktop Agent #435 (Update methods.ts)
- @rikoe Raise an issue for adding TS generics to FDC3 APIs
- @rikoe Split out separate issues for raiseIntent with data return type for other api extensions, and declaring return types in AppD intents
- @kriswest @rikoe Discuss experimental features (stage 1/stage 2) in terms of spec rewrites with LF team
- @kriswest Next meeting agenda