Skip to content
This repository has been archived by the owner on Nov 11, 2019. It is now read-only.

describe security considerations, if any #12

Closed
17 tasks done
chaals opened this issue May 2, 2017 · 1 comment · Fixed by #19
Closed
17 tasks done

describe security considerations, if any #12

chaals opened this issue May 2, 2017 · 1 comment · Fixed by #19
Assignees
@chaals

Comments

@chaals
Copy link
Collaborator

chaals commented May 2, 2017 •
edited
Loading

From the W3C security and privacy questionnaire

  • Does this specification deal with personally-identifiable information?
  • Does this specification deal with high-value data?
  • Does this specification introduce new state for an origin that persists across browsing sessions?
  • Does this specification expose persistent, cross-origin state to the web?
  • Does this specification expose any other data to an origin that it doesn’t currently have access to?
  • Does this specification enable new script execution/loading mechanisms?
  • Does this specification allow an origin access to a user’s location?
  • Does this specification allow an origin access to sensors on a user’s device?
  • Does this specification allow an origin access to aspects of a user’s local computing environment?
  • Does this specification allow an origin access to other devices?
  • Does this specification allow an origin some measure of control over a user agent’s native UI?
  • Does this specification expose temporary identifiers to the web?
  • Does this specification distinguish between behavior in first-party and third-party contexts?
  • How should this specification work in the context of a user agent’s "incognito" mode?
  • Does this specification persist data to a user’s local device?
  • Does this specification have a "Security Considerations" and "Privacy Considerations" section?
  • Does this specification allow downgrading default security characteristics?
@chaals chaals self-assigned this May 2, 2017
chaals pushed a commit that referenced this issue May 3, 2017
add i18n, privacy and security considerations
ec31b63 
fix #12
fix #13
all of these need review from the relevant groups.
@chaals chaals mentioned this issue May 3, 2017
Merged
@chaals
Copy link
Collaborator Author

chaals commented May 3, 2017

The specification doesn't have special access to any data, and cannot expose anything not already available to the origin.

The proposed security section warns that processors should consider the accuracy of information gathered, and whether the source was secure from interference.

@danbri danbri closed this as completed in #19 May 3, 2017
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Assignees

@chaals chaals

Labels
None yet
Projects
None yet
Milestone
No milestone
Development

Successfully merging a pull request may close this issue.

add i18n, privacy and security considerations w3c/microdata
1 participant
@chaals