-
Notifications
You must be signed in to change notification settings - Fork 117
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
Upgrading web access statements from SHOULD to MUST in the API specification and FDC3 compliance pages #440
Merged
Merged
Changes from all commits
Commits
File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
|
@@ -13,10 +13,10 @@ In general, the ratified FDC3 specs represent a lowest common denominator interf | |
> actually required for interoperation or to limit behavior which has | ||
> potential for causing harm (e.g., limiting retransmisssions) For | ||
> example, they must not be used to try to impose a particular method | ||
> on implementors where the method is not required for | ||
> on implementors where the method is not required for | ||
> interoperability. | ||
|
||
These rules would apply only to standards work within FDC3. Today, this covers API, App Directory, Context Data, and Intents working groups, it does not apply to the Use Cases working group. | ||
These rules would apply only to standards work within FDC3. Today, this covers the API, App Directory, Context Data, and Intents specifications. | ||
|
||
## Personas | ||
FDC3 implementors generally fall into 2 categories: platform providers, and application providers. A platform provider supplies an implementation of the FDC3 API for applications to use. Implicitly, it connects to one or more App Directories. | ||
|
@@ -26,12 +26,13 @@ An application provider is largely a downstream consumer of FDC3 standards. It M | |
Depending on persona, implementation compliance with FDC3 will mean different things. | ||
|
||
### Platform Provider | ||
To meet the requirements of FDC3, a platform provider would need to support the following: | ||
For platform providers FDC3 compliance requires: | ||
|
||
* Connection to 1 or more App Directories meeting the FDC3 App Directory standards | ||
* Provide an API to all applications running in the context of the platform that meets the FDC3 API standards, including: | ||
* Support for connections to 1 or more App Directories meeting the FDC3 App Directory standards SHOULD be provided | ||
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. This section was missing imperatives (bar one on workflows). Matched style with Application provider section as one was needed in the |
||
* An API implementation that meets the FDC3 API standards MUST be provided to all applications running in the context of the platform, including: | ||
* Support for FDC3 Context Data and Intents standards | ||
* Support for Intent and Context resolution using a resolver UI | ||
* In the case of web applications, a Desktop Agent MUST provide the FDC3 API via a global accessible as `window.fdc3`. | ||
* At least one workflow of one of the use cases marked as Accepted by the Use Cases working group SHOULD be satisfied by the implementation. | ||
|
||
### Application Provider | ||
|
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Standardized wording