App Directory Working Group (merged with API Working Group)

The Working Group was ratified by the PMC on 2018-02-28. See the for details on the progress of the group

The App Directory Working Group was merged with the API Working Group in November 2019. Please refer to the API Working Group wiki for all recent (post-November 2019) activities.

The FDC3 App Directory provides trusted identity for financial desktop apps. This identity can be used to prevent spoofing and man-in-the-middle attacks when apps communicate with one another and exchange data. The App Directory also enables service discovery. Apps are registered with a declaration of the intents and context data that can be used when interoperating.

Group Information

• Meeting Minutes

• Mailing list: fdc3-app-directory@finos.org

• Google Groups 

• Specification

• Meetings 

  • Schedule: group meets on an ad-hoc basis. Work is mainly carried out via Google Groups and github.

The team

Chair(s)

Members

Working group pages

Working Group Charter

Summary

The primary purpose of this working group is to produce industry standards for App Directories that can perform the following functions:

• Provide verification of identity for an application running on a desktop - whether it is Native, Web, or Hybrid.

• Resolve human readable names for applications to the location of and instructions for launching

• Serve as a repository for application metadata supporting discoverability by intent, context, and other workflow driven facets.

Scope

Key points about the scope of the FDC3 App Directory standards:

• Scope to include standards specifications and reference implementations

• App Directory is not an App Store standard

• App Directory standards must operate across financial platforms.

• Internals of platforms, such as entitlements, are out of scope

Deliverables

The App Directory working group will be focused on delivering the following standards:

• App Directory schema & API requirements

• App name resolution

• App launch resolution

• App directory federation 

Participation

To be successful, the FDC3 is expected to have a critical mass of active participants for its duration. Effective participation in the FDC3 means participation in the form of research, authoring, editing, and development activities outside the scope of attending regular meetings

Licensing

The FDC3 will use Apache2 license or similar for all deliverables.

Group information

Tasks 

Activity Stream