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

Endpoints for adding an app to an appD will often be implementation dependent and should not be required for compliance #566

Closed
Tracked by #664 ...
kriswest opened this issue Jan 24, 2022 · 0 comments · Fixed by #695 or #668
Labels
app-directory deprecation Deprecating or removing features post deprecation help wanted Extra attention is needed
Milestone

Comments

@kriswest
Copy link
Contributor

kriswest commented Jan 24, 2022

Area of Issue

[x] App Directory

Issue Description:

The AppD spec currently defines a POST endpoint (/<version>/apps) for adding an application to an appD, and in the absence of any clarifying info, this is currently required for compliance with the Standard. However, most interactions with App Directories by Desktop Agents will be focused on the retrieval of application details, meaning that these are the priority for standardisation efforts. Further, particular implementors and users of the standard may have different governance or integration requirements for their appD that may be incompatible with providing that endpoint.

Consider downgrading the requirement of this POST endpoint so that is optional by applying the SHOULD or MAY keywords to it in the specification or remove it entirely.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
app-directory deprecation Deprecating or removing features post deprecation help wanted Extra attention is needed
Projects
None yet
Development

Successfully merging a pull request may close this issue.

1 participant