Minutes actions review from last discussion

All individuals in the FDC3 AppD WG are now listed on the Confluence page as members. Let Frank know if anyone is missing.

A new GitHub project was created for appd-glue42-launcher.exe.

Discussion around security prompted by an action item:

• Action item: Bearer Token to be added into the specification. Note that if the token is not there it can be ignored. This was done via PR #4 with a request for someone in the group to review.
• Security is being discussed across a number of groups and should be raised to the PMC.
• Agreed that this had previously been a higher priority but took a backset to other areas of focus for interoperability. Important to revisit now and closely aligned to API WG including looking at 1) security of the AppDirectory itself and 2) security between different apps and the role of AppD providing app validation/verification.
• Further discussion on potential mechanics, breadth and use cases before agreeing that this required a broader view from a design perspective before drilling down on the requirements. The PMC should start this process.

Reviewed the Standards Ratification Process, which can be accessed here.  Very briefly, key points are:

• WG creates a proposed standard and raises it to proposition status (ideally by consensus and if not consensus then by vote - guidance is included on quorum, active participation definition and voting procedure)
• Proposal is published for review and comment before being presented to PMC.
• Proposal is presented at FDC3 general meeting and is open for comments for 2 weeks
• If ratified by PMC the standards are versioned and published (in one place for all FDC3 ratified standards)

This only comes into play if there is a dispute or contention that requires a vote. It's important to note that you are not a voting member unless you have been an active participant/contributor in the working group.

The following were identified as proposals the group should ratify:

1. Discovery Proposal - Discovery of AppDirectories, ie. how do you access the appDirectory. Requires some clean-up
2. appDirectory Specification for the directory itself
3. Potentially a security specification
4. Possibly layouts - but this i son hold for now

Focus is on the first two for now. Documenting what the appDirectory is is also important and could be more structured, potentially in markdown and then stored in the repository.

There is no mandated proposal format. It was noted that ratification doesn't mean the standard is locked in stone but that basic requirements have been agreed and met. Further iterations can then take place.

Leslie noted that they have one more round of UI changes before the launched POC is ready.