+
Skip to content

Vision for W3C 2024-10-23 > 2024-11-20 #77

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

Closed
tantek opened this issue Oct 24, 2024 · 4 comments
Closed

Vision for W3C 2024-10-23 > 2024-11-20 #77

tantek opened this issue Oct 24, 2024 · 4 comments
Assignees
Labels
REVIEW REQUESTED WD Working Draft. Not yet approaching CR.

Comments

@tantek
Copy link
Member

tantek commented Oct 24, 2024

  • name of spec to be reviewed: Vision for W3C

  • URL of spec: https://www.w3.org/TR/2024/NOTE-w3c-vision-20241018/

  • Current Rec/Note phase? Note

  • What and when is your next expected transition? Statement, upon completion of wide and horizontal reviews, and AC vote.

  • What has changed since any previous review? No previous review.

  • Please point to the results of your [self-review] No technical security features.

  • Where and how to file issues arising? https://github.com/w3c/AB-public/issues/ and label "needed for Note" if an issue MUST be resolved before publishing an updated Note, or "needed for Statement" if an issue MUST be resolved before publishing a Statement draft for the AC to vote on.

  • Pointer to any explainer for the spec? https://www.w3.org/wiki/AB/2025_Priorities#Vision

Other comments:

The minimum horizontal review period of 28 days has been requested. Please feel free to request more time for horizontal review in a comment on this issue.

@tantek tantek added pending This issue needs to get a reviewer assigned to it REVIEW REQUESTED WD Working Draft. Not yet approaching CR. labels Oct 24, 2024
@msporny
Copy link
Member

msporny commented Oct 24, 2024

I'm going to be participating in SING (once it is chartered), which I expect to take over these security request reviews, and will volunteer to review the W3C Vision document once that group is operational. Since that group doesn't exist yet, and I can't do the review in that capacity, I've performed a review in my capacity as an AC Rep.

Overall, the document is excellent. Thank you for those that have put the time and care into the creation of the document. The language is aligned with what I expect most of the W3C Members (that have been around for a while) believe the W3C is and does.

The document only mentions the word security once, in the context of thorough review, which is probably fine. It also only mentions safety once, and leans more on privacy than security in that reference. If there is no security on the Web, there is no safety and no trust. I'm struggling to think of what more we could say on the matter that wouldn't dive into the details, but the language seems a bit light on the security and safety front at the moment.

I found two other issues that were more concrete that I've already raised on the specification, here:

w3c/AB-public#211
w3c/AB-public#212

@simoneonofri simoneonofri removed the pending This issue needs to get a reviewer assigned to it label Apr 15, 2025
@simoneonofri
Copy link
Contributor

@msporny thanks for the review. @tantek I liked that we have:

The Web must be safe to use

Referring to the ethical principles which includes privacy and security (and safety).

More than anything a linguistic question (considering that at least in Italian we translate “safety” and “security” in the same way), is there a specific reason why “safe” was used in this context and "security" in the ethical principles?

If there are no more points, we can close the issue

@tantek
Copy link
Member Author

tantek commented Apr 17, 2025

@github.com/simoneonofri wrote:

> is there a specific reason why “safe” was used in this context and "security" in the ethical principles?

I believe we used the term “safe” as in safety as inclusive of both privacy and security in the linked principle as you noted. Both of those (and potentially more) are aspects of user safety, which is the perspective we wanted to capture and express, the human’s perspective.

From a copywriting and readability perspective, we tried very hard to keep those specific points as short and broadly understandable (without any jargon implications) as possible.

Simone, if you find that answer satisfactory, please feel free to close this issue as completed. Thanks again for your diligent review and follow-up, appreciated.

(Originally published at: https://tantek.com/2025/106/t4/)

@simoneonofri
Copy link
Contributor

@tantek thank you for the explanation :) for example in italian we translates "safety" and "security" with the same term "sicurezza"

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
REVIEW REQUESTED WD Working Draft. Not yet approaching CR.
Projects
None yet
Development

No branches or pull requests

3 participants
点击 这是indexloc提供的php浏览器服务,不要输入任何密码和下载