Skip to content

New version to settle open issues #9

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.

Sign up for GitHub

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

Merged
iherman merged 3 commits into from
Dec 10, 2025
Merged

New version to settle open issues #9

Changes from all commits
Commits
Show all changes
3 commits
Select commit Hold shift + click to select a range
89d8f7c
New version to settle open issues
iherman Dec 10, 2025
a137b7f
Trivial fix to language ahead of list of maintenance specs
philarcher Dec 10, 2025
9d6ca3d
Merge pull request #10 from philarcher/patch-2
iherman Dec 10, 2025
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
37 changes: 25 additions & 12 deletions index.html
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -195,13 +195,14 @@ <h2>Motivation and Background</h2>
<h2>Scope</h2>

<p>
For new Recommendations listed <a href="#deliverables">below</a>, the Working
Group will complete them and then will continue to maintain those
specifications. For all published Recommendations, the Working Group will
maintain those specifications, ensuring that no
<a href="https://www.w3.org/policies/process/20231103/#class-4">Class 4
changes</a> are introduced except as needed to address any serious security
issues that arise or to support the new Recommendations produced by the group.
The working group will maintain all Recommendations that were already
published at the start of the charter period by publishing <a href="#maintain">new versions</a>.
However, no new normative features will be introduced for those specifications, except as needed to
address any serious privacy or security issues that arise, or to support the new Recommendations
produced by the group.
The working group will also publish a number of new Recommendations (see the list
<a href="#normative">below</a>), and will consider working on
<a href="#incubation">incubated</a> specifications.
</p>

<section id="section-out-of-scope">
Expand Down Expand Up @@ -443,14 +444,14 @@ <h3>

</section>

<section>
<section id="maintain">
<h3>
Maintenance Specifications
</h3>
<p>
The Working Group will maintain the following W3C normative specifications without making any <a
href="https://www.w3.org/policies/process/20231103/#class-4">Class 4 changes</a> except for
serious security issues that arise.
No new normative features will be introduced for the following specifications, except as needed to
address any serious privacy or security issues that arise, or to support the new Recommendations
produced by the group.
</p>

<dl>
Expand Down Expand Up @@ -792,14 +793,26 @@ <h3>Timeline</h3>
<h2>Success Criteria</h2>

<!-- Testing and interop -->
<p>
<!-- <p>
In order to advance beyond <a href="https://www.w3.org/policies/process/#RecsCR"
title="Candidate Recommendation">Candidate Recommendation</a>, each normative specification is
expected to have <a href="https://www.w3.org/policies/process/#implementation-experience">at least
two independent interoperable implementations</a> of every feature defined in the specification,
where interoperability can be verified by passing open test suites. A feature is a distinct,
normatively required, concretely implementable piece of functionality, such as a data model property
or algorithm, that provides value by allowing a system to achieve a specific use case.
</p> -->

<p>
In order to advance beyond <a href="https://www.w3.org/policies/process/#RecsCR"
title="Candidate Recommendation">Candidate Recommendation</a>, each normative specification is
expected to have <a href="https://www.w3.org/policies/process/#implementation-experience">at least
two independent interoperable implementations</a> of every feature defined in the specification,
Copy link
Member

@msporny msporny Dec 10, 2025

Choose a reason for hiding this comment

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

Suggested change
two independent interoperable implementations</a> of every feature defined in the specification,
two independent interoperable implementations</a> of every mandatory feature defined in the specification,

Copy link
Member Author

@iherman iherman Dec 10, 2025

Choose a reason for hiding this comment

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

I am uneasy about changing this: this is the text of the charter template, and both the strategy team and the AC is touchy about changing that. I would prefer to keep it as is (and sync up with the template before we go to the AC).

If we really want to change that, the right way is to raise an issue by the strategy team on changing the template itself. (That is what I tried, and it did not gain any attention 😒)

Copy link
Member

@msporny msporny Dec 10, 2025

Choose a reason for hiding this comment

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

Alright, I won't push back hard on this since I think the current WG knows what we mean based on a very long history in the WG. I do want to bring it up on the charter template, though, because I do think it leaves too much room for interpretation and could be a process attack vector. Do you have a link to the appropriate repo where I should raise the issue?

where interoperability can be verified by passing open test suites. In order to advance beyond
Candidate Recommendation, each normative specification must have an open test suite of every feature
Copy link
Member

@msporny msporny Dec 10, 2025

Choose a reason for hiding this comment

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

Suggested change
Candidate Recommendation, each normative specification must have an open test suite of every feature
Candidate Recommendation, each normative specification must have an open test suite of every mandatory feature

Copy link
Member Author

@iherman iherman Dec 10, 2025

Choose a reason for hiding this comment

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

See above.

defined in the specification. A feature is a distinct,
normatively required, concretely implementable piece of functionality, such as a data model property
or algorithm, that provides value by allowing a system to achieve a specific use case.
</p>

<p>
Expand Down