-
Notifications
You must be signed in to change notification settings - Fork 12
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.
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
Update Privacy Principles #57
Conversation
Intended to resolve - #55
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks for making this update. On w3.org is definitely better. If date-specific is preferred, then I would recommend using the February 2023 version. (It would also be possible just to refer to the latest /TR/ published version, but no strong feelings either way on that.)
@@ -167,9 +167,9 @@ <h2>Scope</h2> | |||
processing of personal information. Ways in which new features might | |||
enable inappropriate processing include (but are not limited to) | |||
enabling | |||
of <a href="https://w3ctag.github.io/privacy-principles/#hl-recognition-cross-site">cross-site | |||
of <a href="https://www.w3.org/TR/2022/DNOTE-privacy-principles-20221214/#hl-recognition-cross-site">cross-site | |||
or cross context recognition</a> of users or |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Also, cross-context recognition is an explicitly-defined term now, so maybe that would be preferred, rather than
"cross-site or cross-context":
https://www.w3.org/TR/2023/DNOTE-privacy-principles-20230223/#dfn-cross-context-recognition
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Following @npdoty's suggested URL (with updated anchors). Hopefully those "permalink" links are as permanent as the name implies.
Co-authored-by: Martin Thomson <mt@lowentropy.net>
Co-authored-by: Martin Thomson <mt@lowentropy.net>
Intended to resolve - #55