This repository has been archived by the owner on Jan 14, 2025. It is now read-only.
-
Notifications
You must be signed in to change notification settings - Fork 0
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
feat(scenarios): categorize guidance according to three scenarios
- Loading branch information
Showing
2 changed files
with
62 additions
and
1 deletion.
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
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -1 +1,23 @@ | ||
# Scenarios | ||
|
||
This document categorizes guidance based on the following scenarios: | ||
|
||
{.glossary} | ||
Baseline | ||
: Every federation operator, participant, or service should meet these | ||
standards. Anonymous, affiliation-only access is supported, but | ||
user identification may not always be possible. | ||
|
||
{.glossary} | ||
Pseudonymous | ||
: Not every service provider needs (or wants) to handle personal data, | ||
and identity providers have a duty of care for their users' privacy. | ||
Guidance in this category facilitates use cases that include | ||
privacy-preserving personalization, etc. | ||
|
||
{.glossary} | ||
Attributable | ||
: Some services must hold their users accountable for their actions | ||
within the system, which requires assurances that personal data used | ||
for identification, authorization, and accounting is correct, | ||
complete, and well-protected. |
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