General mtg that meets every 4 weeks.
We like to have anyone who is new introduce themselves. This mtg can be an intro to FDC3.
No one new on the call.
Updates from all WG. Should be given from the chair.
API WG - Nick is chair
-The past 4 weeks of August has been a slower cadence than we should see i the coming weeks.
-Has been going back and forth with some fundamental questions on the scope and standards.
-PR has been approved although the spec hasn’t been fully approved.
-Highlights are to try to make clear how one can build a more tighltly coupled RPC system on top of the standards/ Intention.
-There is an idea of hte desktop agen that exposes the FDC3 API to the app nd fulfills the interop functionality on behafl of the app. It will connetct ot one or more app directories and multiple agents. Will resolved intents, launch apps, context data. Most of what needs to be standardised are the interfaces.
Intents WG Update
Espn could make it. Nick to give update.
There is a proposal for initial set of intents and schema visible in GitHub. Waiting on some feedback from Use Cases and API WGs.
It will start up again in a couple of weeks.
Reach out if you have interest.
Purpose of intents is to create definition and schema of common intents in FDC3. You can see material in GitHub.
Leslie: The AppDirectory says I can publish these intents and tends to specify context API. General idea is that an intent is invoked with a context and that they work closely together with
Use Cases WG
Kat gave here update
- We’ve been going through both what is a use case as well as the governance of approval
- 3 stage process, everything managed in confluence
- Ad hoc
- Submitted for approval
- Approval / Rejected
- Approval → discussions with relevant use cases; flesh out which WGs need to be involved
- Acceptance guidelines
- How a long discussion of this
- What personas (actors) should we include -- e.g., do we include a CTO in this?
- Decided to do a couple technologists use case to start
- Initial traunch of use cases -- then there will be a vote after the meeting on Thursday; anyone who comments can vote on accept or reject on the initial set.
- We are not going to manage it like this going foward (they will do ad hoc, not by set)
- JT: this is really exciting -- to be asking “is this valid?”, “Is this useful?” -- it is important the people evaluate against a set of criteria -- we are asking participants to review against a set of criteria … vote will happen by email following the call and then close on Mondy