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.

Sign up for GitHub

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

added references links #50

Merged
merged 1 commit into from
Mar 12, 2019
Merged

added references links #50

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
10 changes: 9 additions & 1 deletion docs/fdc3-compliance.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -22,7 +22,7 @@ In general, the ratified FDC3 specs represent a lowest common denominator interf

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.

## Personas:
## 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.

An application provider is largely a downstream consumer of FDC3 standards. It MAY use the API, it MAY use Context Data, it MAY use Intents. Application providers are only required to comply with the standards they make use of.
Expand All @@ -48,3 +48,11 @@ For application providers FDC3 compliance requires:
* If FDC3 defined Context Data is supported, it MUST meet the interface defined for the type of Context Data.
* If proprietary Context Data properties are handled, they SHOULD follow any recommended naming conventions in the specification.
* If Context Data is supported, the application SHOULD use the addContextListener API to set up a handler.

## References
The following specifications and use cases references apply to the above:
* [API](api/api-spec)
* [App Directory](appd-spec)
* [Context Data](context-spec)
* [Intents](intents-spec)
* [Use Cases](use-cases/overview)