Skip to content

Clarify council text in case of multiple objections to a single decision #1045

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

Open
wants to merge 3 commits into
base: main
Choose a base branch
from

Conversation

frivoal
Copy link
Collaborator

@frivoal frivoal commented May 13, 2025

Even though the logic already was that the Council processes all objections to a single decision together, parts of the original text were written as if there was only a single objection, and were awkward or in case of several.

This rephrasing makes the text coherent.

See #1041


Preview | Diff

Even though the logic already was that the Council processes all
objections to a single decision together, parts of the original text
were written as if there was only a single objection, and were awkward
or in case of several.

This rephrasing makes the text coherent.

See w3c#1041

Co-authored-by: fantasai <fantasai.bugs@inkedblade.net>
@frivoal frivoal added the Agenda+ Marks issues that are ready for discussion on the call label May 13, 2025
Copy link
Contributor

@nigelmegitt nigelmegitt left a comment

Choose a reason for hiding this comment

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

Small suggestions.

frivoal and others added 2 commits May 14, 2025 16:48
Co-authored-by: Nigel Megitt <nigel.megitt@bbc.co.uk>
Co-authored-by: Nigel Megitt <nigel.megitt@bbc.co.uk>
@TallTed
Copy link
Member

TallTed commented May 14, 2025

These changes focus on each decision, not on each FO (nor on each facet of each FO), which is the reverse of the perspective generally desired in today's concall.

@nigelmegitt
Copy link
Contributor

These changes focus on each decision, not on each FO (nor on each facet of each FO), which is the reverse of the perspective generally desired in today's concall.

I wasn't on the call, but I disagree with that perspective - the focus should be on Decisions not FOs in my opinion.

even if it agrees with some of the supportive arguments.
<dfn>confirm</dfn> or <dfn>overturn</dfn> the decision being objected to.
The [=W3C Council=] <em class=rfc2119>may</em> [=confirm=] the decision
even if it agrees with some of the arguments of a [=Formal Objection=].
Copy link
Contributor

Choose a reason for hiding this comment

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

Suggested change
even if it agrees with some of the arguments of a [=Formal Objection=].
even if it agrees with some of the arguments made as part of a [=Formal Objection=].

phrasing. YMMV...

@chaals
Copy link
Contributor

chaals commented May 15, 2025

These changes focus on each decision, not on each FO (nor on each facet of each FO), which is the reverse of the perspective generally desired in today's concall.

I wasn't on the call, but I disagree with that perspective - the focus should be on Decisions not FOs in my opinion.

+1 to @nigelmegitt

@chrisn
Copy link
Member

chrisn commented May 16, 2025

This looks like a good rephrasing that clarifies while preserving the intent of the original text. I agree with @TallTed though (assuming I'm understanding you correctly) that Councils need to consider all the arguments made within each FO to properly come to a conclusion on whether to uphold or overturn a decision.

@frivoal frivoal added this to the Deferred milestone May 19, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Agenda+ Marks issues that are ready for discussion on the call
Projects
None yet
Development

Successfully merging this pull request may close these issues.

5 participants