Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Improve the description of AppD, its role and value. #555

Closed
kriswest opened this issue Jan 24, 2022 · 0 comments · Fixed by #570 or #668
Closed

Improve the description of AppD, its role and value. #555

kriswest opened this issue Jan 24, 2022 · 0 comments · Fixed by #570 or #668
Labels
Milestone

Comments

@kriswest
Copy link
Contributor

Area of Issue

[x] App Directory

Issue Description:

The description of the AppD in the FDC3 website is poor and fails to properly outline its role in FDC3, intended use and ultimately its value as part of the standard, potentially leading to recent proposals to remove it from the standard (#551 #550).

The description should be improved to the point that an individual new to FDC3 can immediately understand its role and why they might want to use it (and/or encourage vendors they work with to use it).

The expected interactions between Desktop Agents and AppD should also be clarified as some readers have interpreted the presence intent configuration data in the appD as a requirement for intent resolution to involve queries to the appD during resolution or for the appD to control intent resolution, when it is actually only intended to provide data to support intent resolution, where implementing resolution is the province of the Desktop Agent implementation (#551).

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
1 participant