Action items from previous meeting were complete:

Updates to specification from last meeting to be published. - Done
Archive old AppD repository - Done

Frank also noted that FDC3 has converged on the centralized FINOD document site. The project is the same with simple markdown files. You can simply edit the files and once the PR is admitted to the repo the automated build process incorporates the generation of the API spec, conformance of the markdown files and the publishing to the central site. The build process will convert a yml file and use redoc to publish all to the central site.

Frank noted that comments should be raised as PRs, which can then be discussed. He clarified that the description (as below) is also part of the formal specification, not just the API.

Comments and discussion included:

• Application Directory Discovery is a restructured version of the proposal with some additions
• Added the Application Directory Use section, pointing to FDC3 Use Cases and describing some of the common uses, e.g. embedded launcher, standalone launcher, aggregated view, enhancing controls.
• Leslie noted that Tick42 is still upgrading to the latest yml file where manifest is separate, which is why they haven't yet contributed the demo launcher. At that point the PoC would also be in here so would that also need to be ratified?
• Frank clarified that AppD Discovery and the specs are being ratified.
• The group reviewed and okay'd the structure of the documents.
• Some discussion around versioning, which was agreed as 1.0.0 (at least for now) and whether or not there needed to be consistency across FDC3, which is a discussion for the PMC. Also some discussion around suing alpha, beta and RC tags.
• AppD has converted to the new FINOS namespace to publish maven artefacts and there is also a sonatype repository.

• Group discussed bindings and the potential need for documentation around this, e.g. how to use pre-generated bindings. This could be outside of the specification.