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

Add reference back to VC Data Model Security and Privacy Considerations sections #167

Closed
msporny opened this issue Aug 18, 2023 · 5 comments
Closed

Add reference back to VC Data Model Security and Privacy Considerations sections #167

msporny opened this issue Aug 18, 2023 · 5 comments
Assignees
@msporny
Labels
CR1 This item was processed during the first Candidate Recommendation phase. pr exists A pull request exists to address this issue. privacy-tracker Group bringing to attention of Privacy, or tracked by the Privacy Group but not needing response. security-tracker Group bringing to attention of security, or tracked by the security Group but not needing response.

Comments

@msporny
Copy link
Member

msporny commented Aug 18, 2023

From the PING's review (w3cping/privacy-request#120):

It may be worth adding a pointer back to the VC Data model's privacy considerations section here and throughout the various Cryptographic suites since the privacy considerations are often relevant to the various specs.

/cc @kdenhartog
@msporny msporny added CR1 This item was processed during the first Candidate Recommendation phase. privacy-needs-resolution Issue the Privacy Group has raised and looks for a response on. security-needs-resolution Issue the security Group has raised and looks for a response on. labels Aug 18, 2023
@msporny msporny self-assigned this Aug 19, 2023
@msporny msporny mentioned this issue Aug 19, 2023
Merged
@msporny
Copy link
Member Author

msporny commented Aug 19, 2023

PR #173 has been raised to address this issue. This issue will be closed once PR #173 has been merged.

@msporny msporny added the pr exists A pull request exists to address this issue. label Aug 19, 2023
This was referenced Aug 19, 2023
Open
Open
@bob420-svg

This comment was marked as off-topic.

Sign in to view
@msporny
Copy link
Member Author

msporny commented Sep 2, 2023 •
edited
Loading

Can I help with anything?

Are you a bot? You've added some questionable tagging in a variety of PRs -- can you identify yourself? Your behavior looks like the sort used when Github star farms try to build profiles to raise fake PRs/engagements.

@msporny
Copy link
Member Author

msporny commented Sep 2, 2023

PR #173 has been merged, closing.

@msporny msporny closed this as completed Sep 2, 2023
@bob420-svg

This comment was marked as off-topic.

Sign in to view
@plehegar plehegar added privacy-tracker Group bringing to attention of Privacy, or tracked by the Privacy Group but not needing response. security-tracker Group bringing to attention of security, or tracked by the security Group but not needing response. and removed privacy-needs-resolution Issue the Privacy Group has raised and looks for a response on. security-needs-resolution Issue the security Group has raised and looks for a response on. labels Oct 13, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@msporny msporny

Labels
CR1 This item was processed during the first Candidate Recommendation phase. pr exists A pull request exists to address this issue. privacy-tracker Group bringing to attention of Privacy, or tracked by the Privacy Group but not needing response. security-tracker Group bringing to attention of security, or tracked by the security Group but not needing response.
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
3 participants
@msporny @plehegar @bob420-svg