Date
Attendees
| Name | Organisation |
|---|---|
| Nicholas Kolba | Openfin |
| Adam Lancaster | Tick42 |
| Colin Eberhardt | Scott Logic |
| Katherine Jones | Refinitiv |
| Leslie Spiro | Tick42 |
| Riko Eksteen | JP Morgan |
| Rob Underwood | FINOS |
| Tosha Ellison | FINOS |
Goals
- reach agreement on initial standards to Ratify
Action Items
Tasks Identified and Assigned
- Type your task here, using "@" to assign to a user and "//" to select a due date
- Type your subtask here
- Type another task. Make sure to include an owner (assignee) and a due date.
Task Report from Last Meeting
(In the task report select the meetings notes from the LAST meeting in the 'Space(s) and page(s)' field to auto-populate this table– remove this note before publishing)
Task report
Looking good, no incomplete tasks.
Discussion items
group
| Time | Item | Who | Notes |
|---|---|---|---|
| 5min | intro - roll call | group | ensure someone can minute and record the meeting - Tosha Ellison |
| 20 min | proposal for alternate API spec | Leslie Spiro | Leslie Spiro from Tick42 presented an alternate proposal (DesktopAgentimpl.ts). Some context is that Tick42 have been working with the AppDirectory, API and Context Data WGs and as a team are trying to understand how they will do their implementation. This led them to produce an alternate API. Contact Leslie for more information. Typescript that Leslie walked through: A few points from the presentation/discussion:
There was continued discussion around what the first version should cover, e.g. how specific it should be in the first instance vs. what should be deferred to a subsequent version following experience and insight gained from initial use. |
| 25 min | review current draft spec | Nicholas Kolba | Aim is to determine if the WG is ready to bring to vote. The group reviewed the remaining issues with the core one revolving around intents and the expected response. There was discussion around the expectation of what will happen once an intent is raised (e.g. immediate response or the potential waiting), including challenges dealing with UX and interoperability. Some examples of points raised include:
The group did not reach consensus and questioned whether a larger sample size was necessary. The point was raised that it might be useful to see implementations and make decisions following that. This prompted consideration of moving to “validate” rather than “ratify” in the first instance and request people to implement what is in the spec in order to get real feedback. The group agreed to use the mailing list to agree next steps as they were at an impasse and there were not enough people to make a decision. |
| 10min | AOB | group |
