You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
[[
I have a concern (objection) about the removal of the words "all known" in the current charter template, made in #415 .
The original phrasing, which I would prefer to continue use, was:
Each specification should contain sections detailing all known security and privacy implications for implementers, Web authors, and end users.
As I describe in the PATCG charter issue where this change was proposed, I believe that this is a step in the wrong direction, I don't believe the concern of disruption to WGs through "weaponisation" of that requirement to be well founded, and we shouldn't be loosening the requirements on WGs to document privacy considerations, even with strong horizontal review in place, as we have.
]]
From @chrisn#416 (comment)
The text was updated successfully, but these errors were encountered:
I would prefer us to do that, as I'm seeing charters coming through for AC review with that change included, and I don't want to be objecting to everything.
[[
I have a concern (objection) about the removal of the words "all known" in the current charter template, made in #415 .
The original phrasing, which I would prefer to continue use, was:
As I describe in the PATCG charter issue where this change was proposed, I believe that this is a step in the wrong direction, I don't believe the concern of disruption to WGs through "weaponisation" of that requirement to be well founded, and we shouldn't be loosening the requirements on WGs to document privacy considerations, even with strong horizontal review in place, as we have.
]]
From @chrisn #416 (comment)
The text was updated successfully, but these errors were encountered: