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

Jump to bottom

Updating privacy considerations - accounting #148

Closed
lknik opened this issue Nov 1, 2016 · 4 comments
Closed

Updating privacy considerations - accounting #148

lknik opened this issue Nov 1, 2016 · 4 comments
Assignees
@tobie
Labels
ED-ready privacy-tracker Group bringing to attention of Privacy, or tracked by the Privacy Group but not needing response. resolved security-tracker Group bringing to attention of security, or tracked by the security Group but not needing response.
Milestone
Level 1

Comments

@lknik
Copy link
Contributor

lknik commented Nov 1, 2016

As per w3ctag/design-reviews#115 (comment)

Let's add:

"High frequency readout can potentially be used for increasing monitoring of user's environment for unexpected purposes"

"Implementations MUST enable the user to verify the current and past use of a sensor, together with requested frequencies."

It's for transparency/accounting.
@lknik lknik mentioned this issue Nov 1, 2016
Closed
@tobie
Copy link
Member

tobie commented Nov 1, 2016 •
edited
Loading

MUST => may. Security / Privacy sections are non-normative anyway.

@tobie tobie added resolved privacy-tracker Group bringing to attention of Privacy, or tracked by the Privacy Group but not needing response. ED-ready labels Nov 1, 2016
@tobie tobie self-assigned this Nov 1, 2016
@tobie tobie added this to the Level 1 milestone Nov 1, 2016
@lknik
Copy link
Contributor Author

lknik commented Nov 1, 2016

If you say so... Then why not MUST? ;)

@tobie
Copy link
Member

tobie commented Nov 1, 2016 •
edited
Loading

Heh. It makes things more confusing. :)

@tobie tobie added the security-tracker Group bringing to attention of security, or tracked by the security Group but not needing response. label Dec 2, 2016
@tobie tobie closed this as completed in 6860294 Jan 26, 2017
@tobie
Copy link
Member

tobie commented Jan 26, 2017

Also fixed by 19b25bf.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@tobie tobie

Labels
ED-ready privacy-tracker Group bringing to attention of Privacy, or tracked by the Privacy Group but not needing response. resolved security-tracker Group bringing to attention of security, or tracked by the security Group but not needing response.
Projects
None yet
Milestone
Level 1
Development

No branches or pull requests
2 participants
@tobie @lknik