Improve guidance on UI for user consenting #353
Merged
Conversation
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
alexshalamov
approved these changes
Mar 6, 2018
index.bs
Outdated
| @@ -302,6 +302,23 @@ and defensive programming which includes: | |||
|
|
|||
| <h2 id="security-and-privacy">Security and privacy considerations</h2> | |||
|
|
|||
| <div class="note"> | |||
| The judgement on how to communicate to the user the known [[#main-privacy-security-threats|threats]] | |||
| and mandatory [[#mitigation-strategies|mitigations]] used to protect the user against these threats | |||
There was a problem hiding this comment.
I read this sentence few times and it sounds like implementer has to communicate about "threats and mitigation strategies". IMO, implementer has to communicate about threats and implement mitigation strategies to reduce risks. Information about mitigations are technical and not relevant to the end user.
index.bs
Outdated
|
|
||
| The Generic Sensor API and its [=extension specifications=] are agnostic with respect to any user | ||
| interface aspects. This specification defines an [[#request-sensor-access|integration point]] to the | ||
| Permissions API that implementers can use for [=new information about the user's intent|explicit or implicit user consenting=]. |
There was a problem hiding this comment.
Maybe link to Permission API spec?
index.bs
Outdated
| Permissions API that implementers can use for [=new information about the user's intent|explicit or implicit user consenting=]. | ||
| In addition, implementers are encouraged to use additional privacy enchancing mechanisms inline | ||
| with their product requirements to provide a consistent and cohesive experience. Such mechanisms | ||
| can include, for example, global and per-site access controls, page info dialogs, location bar |
|
@alexshalamov, thanks for your review comments. I updated the PR accordingly. |
alexshalamov
approved these changes
Mar 7, 2018
|
We can merge this now and do another review pass on the group's call tomorrow, and improve further if new information emerges. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Preview | Diff