From 576a0e84a5b305397dcb71916918797997f9c1d1 Mon Sep 17 00:00:00 2001 From: reidmore-online Date: Fri, 15 Aug 2025 13:31:05 -0400 Subject: [PATCH 1/3] create a respec council template --- .../council-report-template-respec.html | 156 ++++++++++++++++++ .../council-report-template.html | 156 ++++++++++++++++++ 2 files changed, 312 insertions(+) create mode 100644 council-templates/council-report-template-respec.html create mode 100644 council-templates/council-report-template.html diff --git a/council-templates/council-report-template-respec.html b/council-templates/council-report-template-respec.html new file mode 100644 index 0000000..c0e63e6 --- /dev/null +++ b/council-templates/council-report-template-respec.html @@ -0,0 +1,156 @@ + + + + + W3C Council Report on the Formal Objection[s] Against [Identify the Decision] + + + + + +
+

Instructions (Do not include in final report)

+ +

This template can be used to create a W3C Council report on formal objections. Replace the placeholders with the relevant information. You can use either Markdown or HTML for the content.

+ +
+ Blocks like this are quotes from the Process, included to help understand what various sections need to cover. Delete them before publishing the report. +
+ +

Italicized sentences like this give instructions or comments to the writer of the report. Delete them before publishing the report.

+ +

Text between square brackets `[]` is meant to become part of the report, but needs adjustments or completion before publishing, or deletion in cases where it is not applicable.

+ +

You can use `class="todo"` to mark items that need to be completed before the report is published, make sure to remove all instances before publishing the report.

+ +

The source of this document is available in ReSpec format at https://github.com/w3c/AB-public/tree/main/council-templates.

+
+ +
+

Introduction

+ +

A detailed exposition of this case may be found in the [report](URL) prepared by the W3C Team.

+ +

Summarise the situation, clearly identify the decision that is being formally objected to, list the objections raised, indicate if any were resolved by consensus (and therefore don't need to be ruled on by the council), to make clear exactly what the Council considers it is being asked to rule on. If practical, and summarize the (not yet resolved) objections to make this report easier to read standalone. However, if the objections are long, raise numerous points, or are hard to summarize, linking may be more prudent than rephrasing.

+ +

A Council was then formed to rule on [this | these] objection[s]. This Council Report documents the conclusions of this Council.

+
+ +
+

Decision

+ +

The Council resolved to [insert one of the options below or write a similar short sentence summarizing the decision]

+ + + +

Include the consequences of the decision when appropriate.

+ + + +

If any post-AC review changes got consensus and were integrated into the proposed charter/spec/etc, especially if that was necessary to resolve some of the formal objections, and if the remaining formal objections were overruled, for the avoidance of doubt, it's usually good to clarify that the document that is cleared for advancement is the one with those changes integrated. A link to the section of the Process that explains how such changes are integrated is welcome too.

+
+ +
+

Rationale

+ +
+

must provide a rationale supporting the decision, which **should** address each argument raised in the Formal Objection(s).

+ +

The W3C Council may overrule the Formal Objection even if it agrees with **some** of the supportive arguments.

+
+ +

Delete the following paragraph if not applicable:

+ +

Some additional Member-only remarks were made in connection with the objection[s]. These were taken into account in the Council's conclusion. To respect confidentiality, they cannot be discussed in this report, but are covered in a Supplemental Member-only Council Report.

+
+ +
+

Recommendations

+ +
+

must include any recommendation decided by the Council.

+ +

When upholding an objection, it should recommend a way forward.

+
+ +

If the Council has some suggestions to give, write them here. This could be, in the case of objections overruled despite some concerns, advice on what to do in order to avoid further potentially sustainable objections at a later stage; alternatively, in the case of sustained objections, suggestions of what the originating group can do to try and overcome the disagreements. None of this, however, is binding.

+
+ +
+

Mitigations

+ +
+

If an overturned decision has already had consequences (e.g., if the objection concerns material already in a published document) the Council should suggest how these consequences might be mitigated. The Team is responsible for making sure that adequate mitigations are enacted in a timely fashion; and the Formal Objection is not considered fully addressed until then.

+ +

Note: This does not create new powers for the Team, such as the ability to “unpublish” documents. The Team's role is to ensure the responsible parties enact adequate mitigations, by whatever means they already have at their disposal.

+
+ +

If the objections were overruled, delete this section.

+
+ +
+

Appendix A: Council Participation

+ +

Information on participation, as required by Process on Councils; this section needs to be filled out.

+ +

The Council was formed on [DATE] from the members of the TAG and the AB, plus [the Team delegate chosen by] the CEO. [X, Y, and Z | no-one] renounced their seat[s] on the Council; [X, Y, and Z | no-one] [was | were] dismissed. Therefore, the actual membership of this council was:

+ + + +

[NAME] was appointed as chair.

+ +

Of those qualified to serve, the following participated in the final decision:

+ + + +

Pick among the following two paragraphs, as appropriate, and delete the other one.

+ +

The decision was made by consensus.

+ +

The decision was made by vote, with [x] in favor, [y] against, and [z] abstaining[, with the chair breaking the tie].

+
+ +
+

Appendix B: Minority Report

+ +
+

In the case of non-unanimous decisions, members of a W3C Council who disagree with the decision may write a Minority Opinion explaining the reason for their disagreement.

+
+ +

If the decision was taken by consensus, or those who lost the vote do not wish to explain their views, delete this section.

+
+ + \ No newline at end of file diff --git a/council-templates/council-report-template.html b/council-templates/council-report-template.html new file mode 100644 index 0000000..c0e63e6 --- /dev/null +++ b/council-templates/council-report-template.html @@ -0,0 +1,156 @@ + + + + + W3C Council Report on the Formal Objection[s] Against [Identify the Decision] + + + + + +
+

Instructions (Do not include in final report)

+ +

This template can be used to create a W3C Council report on formal objections. Replace the placeholders with the relevant information. You can use either Markdown or HTML for the content.

+ +
+ Blocks like this are quotes from the Process, included to help understand what various sections need to cover. Delete them before publishing the report. +
+ +

Italicized sentences like this give instructions or comments to the writer of the report. Delete them before publishing the report.

+ +

Text between square brackets `[]` is meant to become part of the report, but needs adjustments or completion before publishing, or deletion in cases where it is not applicable.

+ +

You can use `class="todo"` to mark items that need to be completed before the report is published, make sure to remove all instances before publishing the report.

+ +

The source of this document is available in ReSpec format at https://github.com/w3c/AB-public/tree/main/council-templates.

+
+ +
+

Introduction

+ +

A detailed exposition of this case may be found in the [report](URL) prepared by the W3C Team.

+ +

Summarise the situation, clearly identify the decision that is being formally objected to, list the objections raised, indicate if any were resolved by consensus (and therefore don't need to be ruled on by the council), to make clear exactly what the Council considers it is being asked to rule on. If practical, and summarize the (not yet resolved) objections to make this report easier to read standalone. However, if the objections are long, raise numerous points, or are hard to summarize, linking may be more prudent than rephrasing.

+ +

A Council was then formed to rule on [this | these] objection[s]. This Council Report documents the conclusions of this Council.

+
+ +
+

Decision

+ +

The Council resolved to [insert one of the options below or write a similar short sentence summarizing the decision]

+ + + +

Include the consequences of the decision when appropriate.

+ + + +

If any post-AC review changes got consensus and were integrated into the proposed charter/spec/etc, especially if that was necessary to resolve some of the formal objections, and if the remaining formal objections were overruled, for the avoidance of doubt, it's usually good to clarify that the document that is cleared for advancement is the one with those changes integrated. A link to the section of the Process that explains how such changes are integrated is welcome too.

+
+ +
+

Rationale

+ +
+

must provide a rationale supporting the decision, which **should** address each argument raised in the Formal Objection(s).

+ +

The W3C Council may overrule the Formal Objection even if it agrees with **some** of the supportive arguments.

+
+ +

Delete the following paragraph if not applicable:

+ +

Some additional Member-only remarks were made in connection with the objection[s]. These were taken into account in the Council's conclusion. To respect confidentiality, they cannot be discussed in this report, but are covered in a Supplemental Member-only Council Report.

+
+ +
+

Recommendations

+ +
+

must include any recommendation decided by the Council.

+ +

When upholding an objection, it should recommend a way forward.

+
+ +

If the Council has some suggestions to give, write them here. This could be, in the case of objections overruled despite some concerns, advice on what to do in order to avoid further potentially sustainable objections at a later stage; alternatively, in the case of sustained objections, suggestions of what the originating group can do to try and overcome the disagreements. None of this, however, is binding.

+
+ +
+

Mitigations

+ +
+

If an overturned decision has already had consequences (e.g., if the objection concerns material already in a published document) the Council should suggest how these consequences might be mitigated. The Team is responsible for making sure that adequate mitigations are enacted in a timely fashion; and the Formal Objection is not considered fully addressed until then.

+ +

Note: This does not create new powers for the Team, such as the ability to “unpublish” documents. The Team's role is to ensure the responsible parties enact adequate mitigations, by whatever means they already have at their disposal.

+
+ +

If the objections were overruled, delete this section.

+
+ +
+

Appendix A: Council Participation

+ +

Information on participation, as required by Process on Councils; this section needs to be filled out.

+ +

The Council was formed on [DATE] from the members of the TAG and the AB, plus [the Team delegate chosen by] the CEO. [X, Y, and Z | no-one] renounced their seat[s] on the Council; [X, Y, and Z | no-one] [was | were] dismissed. Therefore, the actual membership of this council was:

+ + + +

[NAME] was appointed as chair.

+ +

Of those qualified to serve, the following participated in the final decision:

+ + + +

Pick among the following two paragraphs, as appropriate, and delete the other one.

+ +

The decision was made by consensus.

+ +

The decision was made by vote, with [x] in favor, [y] against, and [z] abstaining[, with the chair breaking the tie].

+
+ +
+

Appendix B: Minority Report

+ +
+

In the case of non-unanimous decisions, members of a W3C Council who disagree with the decision may write a Minority Opinion explaining the reason for their disagreement.

+
+ +

If the decision was taken by consensus, or those who lost the vote do not wish to explain their views, delete this section.

+
+ + \ No newline at end of file From 6170abc249bcd4ed4f6f2fa277a5c6e3ec7eba7d Mon Sep 17 00:00:00 2001 From: reidmore-online Date: Fri, 15 Aug 2025 13:31:22 -0400 Subject: [PATCH 2/3] fix file name --- .../council-report-template.html | 156 ------------------ 1 file changed, 156 deletions(-) delete mode 100644 council-templates/council-report-template.html diff --git a/council-templates/council-report-template.html b/council-templates/council-report-template.html deleted file mode 100644 index c0e63e6..0000000 --- a/council-templates/council-report-template.html +++ /dev/null @@ -1,156 +0,0 @@ - - - - - W3C Council Report on the Formal Objection[s] Against [Identify the Decision] - - - - - -
-

Instructions (Do not include in final report)

- -

This template can be used to create a W3C Council report on formal objections. Replace the placeholders with the relevant information. You can use either Markdown or HTML for the content.

- -
- Blocks like this are quotes from the Process, included to help understand what various sections need to cover. Delete them before publishing the report. -
- -

Italicized sentences like this give instructions or comments to the writer of the report. Delete them before publishing the report.

- -

Text between square brackets `[]` is meant to become part of the report, but needs adjustments or completion before publishing, or deletion in cases where it is not applicable.

- -

You can use `class="todo"` to mark items that need to be completed before the report is published, make sure to remove all instances before publishing the report.

- -

The source of this document is available in ReSpec format at https://github.com/w3c/AB-public/tree/main/council-templates.

-
- -
-

Introduction

- -

A detailed exposition of this case may be found in the [report](URL) prepared by the W3C Team.

- -

Summarise the situation, clearly identify the decision that is being formally objected to, list the objections raised, indicate if any were resolved by consensus (and therefore don't need to be ruled on by the council), to make clear exactly what the Council considers it is being asked to rule on. If practical, and summarize the (not yet resolved) objections to make this report easier to read standalone. However, if the objections are long, raise numerous points, or are hard to summarize, linking may be more prudent than rephrasing.

- -

A Council was then formed to rule on [this | these] objection[s]. This Council Report documents the conclusions of this Council.

-
- -
-

Decision

- -

The Council resolved to [insert one of the options below or write a similar short sentence summarizing the decision]

- -
    -
  • accept the Team's recommendation to overrule the objection
    • -
  • accept the Team's recommendation to sustain the objection
    • -
  • sustain the objection
    • -
  • overrule the objection
    • -
- -

Include the consequences of the decision when appropriate.

- -
    -
  • The charter may proceed.
    • -
  • The charter, as proposed, is rejected.
    • -
  • The specification may proceed to Recommendation.
    • -
  • The specification, as proposed, cannot proceed to Recommendation.
    • -
- -

If any post-AC review changes got consensus and were integrated into the proposed charter/spec/etc, especially if that was necessary to resolve some of the formal objections, and if the remaining formal objections were overruled, for the avoidance of doubt, it's usually good to clarify that the document that is cleared for advancement is the one with those changes integrated. A link to the section of the Process that explains how such changes are integrated is welcome too.

-
- -
-

Rationale

- -
-

must provide a rationale supporting the decision, which **should** address each argument raised in the Formal Objection(s).

- -

The W3C Council may overrule the Formal Objection even if it agrees with **some** of the supportive arguments.

-
- -

Delete the following paragraph if not applicable:

- -

Some additional Member-only remarks were made in connection with the objection[s]. These were taken into account in the Council's conclusion. To respect confidentiality, they cannot be discussed in this report, but are covered in a Supplemental Member-only Council Report.

-
- -
-

Recommendations

- -
-

must include any recommendation decided by the Council.

- -

When upholding an objection, it should recommend a way forward.

-
- -

If the Council has some suggestions to give, write them here. This could be, in the case of objections overruled despite some concerns, advice on what to do in order to avoid further potentially sustainable objections at a later stage; alternatively, in the case of sustained objections, suggestions of what the originating group can do to try and overcome the disagreements. None of this, however, is binding.

-
- -
-

Mitigations

- -
-

If an overturned decision has already had consequences (e.g., if the objection concerns material already in a published document) the Council should suggest how these consequences might be mitigated. The Team is responsible for making sure that adequate mitigations are enacted in a timely fashion; and the Formal Objection is not considered fully addressed until then.

- -

Note: This does not create new powers for the Team, such as the ability to “unpublish” documents. The Team's role is to ensure the responsible parties enact adequate mitigations, by whatever means they already have at their disposal.

-
- -

If the objections were overruled, delete this section.

-
- -
-

Appendix A: Council Participation

- -

Information on participation, as required by Process on Councils; this section needs to be filled out.

- -

The Council was formed on [DATE] from the members of the TAG and the AB, plus [the Team delegate chosen by] the CEO. [X, Y, and Z | no-one] renounced their seat[s] on the Council; [X, Y, and Z | no-one] [was | were] dismissed. Therefore, the actual membership of this council was:

- -
    -
  • [...]
    • -
  • [...]
    • -
  • [...]
    • -
  • [...]
    • -
- -

[NAME] was appointed as chair.

- -

Of those qualified to serve, the following participated in the final decision:

- -
    -
  • [...]
    • -
  • [...]
    • -
  • [...]
    • -
  • [...]
    • -
- -

Pick among the following two paragraphs, as appropriate, and delete the other one.

- -

The decision was made by consensus.

- -

The decision was made by vote, with [x] in favor, [y] against, and [z] abstaining[, with the chair breaking the tie].

-
- -
-

Appendix B: Minority Report

- -
-

In the case of non-unanimous decisions, members of a W3C Council who disagree with the decision may write a Minority Opinion explaining the reason for their disagreement.

-
- -

If the decision was taken by consensus, or those who lost the vote do not wish to explain their views, delete this section.

-
- - \ No newline at end of file From d7900beb6aa2b25d8f8df374b91c4c8ff4a53312 Mon Sep 17 00:00:00 2001 From: reidmore-online Date: Fri, 15 Aug 2025 13:35:22 -0400 Subject: [PATCH 3/3] fix heading for appendix b --- council-templates/council-report-template-respec.html | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/council-templates/council-report-template-respec.html b/council-templates/council-report-template-respec.html index c0e63e6..27c2c37 100644 --- a/council-templates/council-report-template-respec.html +++ b/council-templates/council-report-template-respec.html @@ -144,7 +144,7 @@

Appendix A: Council Participation

-

Appendix B: Minority Report

+

Appendix B: Minority Report

In the case of non-unanimous decisions, members of a W3C Council who disagree with the decision may write a Minority Opinion explaining the reason for their disagreement.