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.

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

New section on environmental impacts #27

Merged
merged 53 commits into from
Nov 4, 2021
Merged

Conversation

mprorock
Copy link
Contributor

@mprorock mprorock commented Sep 2, 2021

index.html Outdated
the human species is highly desireable. Examples of related work where
decentralized technologies have been utilized to prevent use of minerals
sourced from conflict zones may be found in the following reports from
<a href="https://sustainability.google/progress/projects/traceability/">Google</a>
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

<3

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@csuwildcat @selfissued does Microsoft have any similar initiatives for ION?

index.html Outdated
sourced from conflict zones may be found in the following reports from
<a href="https://sustainability.google/progress/projects/traceability/">Google</a>
and
<a href="https://www.apple.com/supplier-responsibility/pdf/Apple-Conflict-Minerals-Report.pdf">Apple</a>.
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

<3

index.html Outdated Show resolved Hide resolved
index.html Outdated Show resolved Hide resolved
index.html Outdated Show resolved Hide resolved
mprorock and others added 2 commits September 2, 2021 13:49
Co-authored-by: Charles E. Lehner <[email protected]>
Co-authored-by: Charles E. Lehner <[email protected]>
index.html Outdated Show resolved Hide resolved
index.html Outdated Show resolved Hide resolved
mprorock and others added 2 commits September 2, 2021 14:15
Co-authored-by: Charles E. Lehner <[email protected]>
Co-authored-by: Charles E. Lehner <[email protected]>
@OR13
Copy link
Contributor

OR13 commented Sep 2, 2021

@mprorock we might want to consider referencing https://www.w3.org/2001/tag/doc/ethical-web-principles/ directly.

cc @peacekeeper thanks for the suggestion.

@mprorock
Copy link
Contributor Author

mprorock commented Sep 3, 2021

cc @peacekeeper thanks for the suggestion.

Excellent suggestion. References added

@csuwildcat
Copy link
Contributor

csuwildcat commented Sep 3, 2021

I'm taking time off for Labor Day, and would ask that this not be merged until more of the community (including me) has an opportunity to suggest changes and submit content. It's important to give this time, because a hasty inclusion of something that lends credence to a fundamentally false narrative backed by spurious arguments and dubious claims could harm the community, implementers, and, by extension, the use of systems that are designed to deliver maximum protection of digital human rights.

@mprorock
Copy link
Contributor Author

mprorock commented Sep 3, 2021

@csuwildcat Completely agree. This is definitely something that we will want to make sure is cleanly included, and also emphasizes the strengths of DIDs in enabling further protection of human rights and other concerns that have broad ethical impacts.

edit to note: I believe that clarifying the goals, technology, and actual capabilities enabled via DIDs should hopefully make clear that the authors and actors in the DID space are acting with GOOD intention and that we wish to continue down that path. Some concerns I have seen raised around DIDs makes it clear that individuals that have not been engaged with or closely tracking the work progress might have missed some of the nuance of a reasonably complex set of capabilities, or have missed the fact that much of the motivation of the community is to promote positive and ethical use of technology.

As well stated by @csuwildcat a foremost consideration in design and use of DIDs for almost every party I have engaged with in the space is to promote "the use of systems that are designed to deliver maximum protection for digital human rights." Further many of us have leveraged the tech to bridge not just protection of digital human rights, but to aid in the prevention of real world human rights abuses such as forced labor, etc.

index.html Outdated Show resolved Hide resolved
@brentzundel
Copy link
Member

Perhaps out of scope for this PR, but if mention is being made to the Ethical web principles, it may be good to also emphasize the principles that DIDs strongly support, specifically:

  1. The web must make it possible for people to verify the information they see
  2. The web must enhance individuals' control and power
  3. Security and privacy are essential

index.html Outdated
Comment on lines 1438 to 1446
As noted in the <a href="https://www.w3.org/2001/tag/doc/ethical-web-principles/#principles">Principles</a>
section of the Ethical Web Principles, there are certain key goals that should
apply to all Web standards and technologies. DIDs explicitly support several
of these goals, especially the following:
<ul>
<li><a href="https://www.w3.org/2001/tag/doc/ethical-web-principles/#privacy">Privacy</a></li>
<li><a href="https://www.w3.org/2001/tag/doc/ethical-web-principles/#control">Individual Control</a></li>
<li><a href="https://www.w3.org/2001/tag/doc/ethical-web-principles/#multi">Device Independence</a></li>
</ul>
Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

emphasize the principles that DIDs strongly support

@brentzundel agree - attempted to do that with this section, but i think there are improvements that could be made to wording

index.html Outdated
<h3>Energy Usage and Environmental Impacts</h3>
<p>
When implementing or utilizing a DID method, consideration should be given
to the environmental impacts of any underlying technologies. For example
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I support the guidance that one should give consideration to the environmental impacts of any system you build. However, that example is inappropriate as it does not meet any standard of objective review. Rather, it is a political an ideological attack on PoW systems, an attack which is inappropriate for the W3C and this working group to make.

In the same manner, we could demand that people consider the ethical implications of Proof of Stake algorithms which clearly reinforce existing power dynamics leading to a runaway cascade in which the larger, vested players establish an unassailable and therefore, undemocratic authority.

IMO, neither of these are appropriate positions for the W3C and the DID WG to take, precisely because it is not a technical recommendation but a political one.

If some part of the W3C were to develop standards for evaluating the environment impact of technologies, and were willing to apply that standard across the board to all existing and propose technologies, I would welcome that objective, fair framework for discussion.

This is not that.

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

In the same manner, we could demand that people consider the ethical implications of Proof of Stake algorithms which clearly reinforce existing power dynamics leading to a runaway cascade in which the larger, vested players establish an unassailable and therefore, undemocratic authority.

Good call out. Will make some adjustments

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@csuwildcat that would be great. I have adjusted the PR to avoid calling out particular approaches (as obviously these can change over time). Might be optimal if we call out that similar to making assessments on energy usage and comparing those against other benefits of an approach, we should absolutely make assessments related to potential privacy and security over time and that human rights concerns should outweigh others.

Copy link
Contributor

@jandrieu jandrieu left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Please remove the ideological attack on PoW. It's not appropriate.

…may be contested or have potential offsets on other concerns such as privacy and control of DIDs
@mprorock
Copy link
Contributor Author

mprorock commented Sep 3, 2021

@jandrieu Do the changes made in 78abe49 help with your concern?

@jandrieu
Copy link
Contributor

jandrieu commented Sep 3, 2021

@jandrieu Do the changes made in 78abe49 help with your concern?

In the right direction, although I think it still reads as an attack on PoW by any name. I think the general strategy should be to communicate that there are any number of criteria that both implementers and users should consider. See the rubric for more details.

I'm not convinced that language that is specifically designed to target a particular class of blockchains with armchair economic arguments will be able to achieve consensus, largely because for many of us in this community, PoW is the only solution that actually solves the centralization problem with a truly peer-to-peer solution. I appreciate that others have different opinions about whether or not PoW is innately evil and prefer other approaches. But I won't support the DID WG taking a position on the PoS v PoW v something else debate.

This is the whole point of the rubric.

I believe our best position wrt politically or ideologically charged differences between methods is to offer good questions--those that highlight the differences--rather than amplifying answers from any particular contingent.

@iherman
Copy link
Member

iherman commented Sep 30, 2021

I have raised a separate PR (#34) to settle #27 (comment) (and another minor issue).

Cc @TallTed

@TallTed
Copy link
Member

TallTed commented Sep 30, 2021

@iherman (/cc @OR13 @mprorock @dlongley @burnburn) --

That's helpful information, though it highlights some problematic aspects of the current setup.

If I understand correctly, we no longer have a proper Editor's Draft of the ImpGuide. That means that we must get each PR perfect-for-NOTE-publication, regardless of complexity, and we cannot usefully iterate improvements through nor blend multiple PRs (where all must be merged for some/any to be accepted).

Probably the best solution (which may not be workable right now for this doc, but would be good to set up for future work!) would be an editors-draft (a la develop) branch, which we would be working against (and which would publish to github.io/did-imp-guide) until sufficient fixes were determined (at least by Editors, if not by overall group) to warrant a new published version, at which point the editors-draft branch would be merged into main and thereby auto-published to w3c.org/TR/.

@iherman
Copy link
Member

iherman commented Sep 30, 2021

If I understand correctly, we no longer have a proper Editor's Draft of the ImpGuide. That means that we must get each PR perfect-for-NOTE-publication, regardless of complexity, and we cannot usefully iterate improvements through nor blend multiple PRs (where all must be merged for some/any to be accepted).

That is correct. The WG has decided, early on, to use this workflow for all its documents, the implementation guide is no exception.

I let the chief editors comment on the general approach.

@jandrieu
Copy link
Contributor

@TallTed I think the practical effect is that we should simply expect to leave things as PRs a bit longer than we might otherwise and that the published notes need a bit more polish than editor's drafts. (Noting also that we have a lot of cleanup pending on the Rubric to align it with the recent decision to make it a registry.)

@OR13
Copy link
Contributor

OR13 commented Oct 4, 2021

@jandrieu you requested changes 6 days ago. Have the recent changes addressed your concerns?

@OR13
Copy link
Contributor

OR13 commented Oct 12, 2021

@jandrieu can you please re-review this PR?

@rxgrant
Copy link

rxgrant commented Oct 12, 2021

This pull request is currently in a medium-low quality state, in part becuse it references other work that hasn't been done. I recommend that it keep waiting.

@OR13
Copy link
Contributor

OR13 commented Oct 18, 2021

@jandrieu can you please re-review this PR? I will be dismissing your code request change if i don't hear back from you soon.

@rxgrant I don't agree with your position on this PR, please request specific changes, or approve.

@rxgrant
Copy link

rxgrant commented Oct 19, 2021

@jandrieu can you please re-review this PR? I will be dismissing your code request change if i don't hear back from you soon.

@OR13 If you try to get out of the changes that way I will resubmit them.

@rxgrant
Copy link

rxgrant commented Oct 19, 2021

@jandrieu you requested changes 6 days ago. Have the recent changes addressed your concerns?

@OR13 What about this answer #27 (comment) didn't work for you?

Copy link
Contributor

@jandrieu jandrieu left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

We are still referring to PRs in the Rubric. Either we remove those specific references (point generally to the rubric rather than nonexistent future-likely sections) or wait until we get the content in the Rubric to which we we can directly refer.

index.html Outdated
<p class="issue">
Some members of the working group feel it important that the [[DID-RUBRIC]]
include environmental considerations as discussed in <a
href="https://github.com/w3c/did-rubric/pull/51">this pull request</a> in
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This remains unresolved. IMO, a published W3C doc should not point a pull request.

@OR13
Copy link
Contributor

OR13 commented Oct 19, 2021

@jandrieu Would it be acceptable if the link to the PR was removed?

@OR13
Copy link
Contributor

OR13 commented Oct 19, 2021

@mprorock consider removing the link to the PR, not sure how to move this PR forward.

@mprorock
Copy link
Contributor Author

@OR13 @jandrieu I have removed the link to the PR - note concern that rubric still does not have environmental criteria

@OR13
Copy link
Contributor

OR13 commented Oct 19, 2021

@jandrieu please review again.

@OR13
Copy link
Contributor

OR13 commented Oct 19, 2021

@rxgrant do you have any change requests with the PR as is?

@TallTed
Copy link
Member

TallTed commented Oct 20, 2021

note concern that rubric still does not have environmental criteria

That would seem to be reason to open an issue on the Rubric...

@mprorock
Copy link
Contributor Author

That would seem to be reason to open an issue on the Rubric...

Open PR for almost 30days now....

@TallTed
Copy link
Member

TallTed commented Oct 21, 2021

Open PR for almost 30days now....

It is often helpful to provide a link with/in statements like this...

Also, Issues on the Rubric sub-project seem more appropriate right now than PRs against its text, given that the Rubric is transforming to a Registry, and most text, before or after such PRs, isn't likely to be retained as-is.

@mprorock
Copy link
Contributor Author

mprorock commented Oct 21, 2021

It is often helpful to provide a link with/in statements like this...

absolutely, apologies as I was on mobile. Link to PR is here (that adds the section to even add any environmental criteria)

Issue related on rubric noting that there is no section to add these criteria, and that the prior PR to add at least some criteria was closed

@OR13
Copy link
Contributor

OR13 commented Oct 26, 2021

@jandrieu can you review this PR again?

@OR13
Copy link
Contributor

OR13 commented Nov 4, 2021

After a very lengthy review process, we have reached consensus on this PR. I am merging since its been open for 7 days without objection.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.