The web should empower an equitable, informed and interconnected
society. It has been, and should continue to be, designed to enable
communication and knowledge-sharing for everyone. In order for the
web to continue to be beneficial to society, we need to consider the
ethical implications of our work when we build web technologies,
applications, and sites.
—§1 Introduction
For those of you unfamiliar with it, the Ethical Web Principles document sets out to concisely state the ethical principles which underpin all of our technical work here at the W3C .
What’s new?
So what’s new since we spoke last year? We’ve received a bunch of comments on the document from many of you and various other folk in the W3C community. People have filed a bunch of issues , and we’ve had some PR s come in too.
Acknowledgments
PR
#99
One question we got in last year’s AC meeting was if we had sought any feedback from tech ethicists and other experts outside of the W3C community. We did, but the document doesn’t have an acknowledgments section, so this isn’t obvious to people reading the document. We’ve got a PR up that adds one.
Currently a Note in /TR/ space
Intent is for it to become a W3C Statement
Will issue a call for wide review after
the #acks PR lands
Last year I told you that we intend for the document to be elevated to a W3C Statement . Once we land the acknowledgments section we’ll issue a call for wide review, which is the next step toward the document becoming a W3C Statement. After we address all of the wide review feedback that comes in, we’ll ask the Team to kick off an AC review. No one’s ever elevated a document to W3C Statement before, so we expect a few bumps on the road, but we’re happy to be the first to try, and afterwards we’ll provide feedback to the Process CG about how it went and how it could have gone more smoothly.
The TAG does a lot of design reviews
We capture learnings in Web Platform Design Principles
Many design principles rooted in the ethical web principles
So, how does this document affect our day to day work? As you probably know, the TAG does lots of design reviews of proposed Web platform features. Lots and lots of design reviews. We try to capture what we learn during these reviews in the Web Platform Design Principles document. If you look in the design principles doc, you’ll see many references back to the ethical web principles document.
But we’re not the only group that does reviews around here. The W3C prides itself on its focus on several areas of horizontal review: accessibility, internationalization, privacy, and security. We (the TAG ) are working with PING on a Privacy Principles document that Jeffrey ’s going to talk with you about in a few minutes. We’d love to see similar principles documents arise in each of the other areas of horizontal review, and we’d love to help.
How do we, the members of the W3C , evaluate how well
we are living up to these principles?
How can we measure our progress?
Okay, so, how do we make sure these principles aren’t just words on paper? Well, I’m an engineer. I like to have some kind of quantifiable measurement of the progress I’m making towards my goals. How do we, the members of the W3C , evaluate how well we are living up to these principles? How can we measure our progress? How do we hold ourselves accountable? This is my question and challenge to you all.