w3c
Ambiguity in new features for registries versus recommentations
Section 6.5.2 of the process says:
Changes that add new features (i.e., class 4 changes) are allowed in all W3C Registries, without needing them to explicitly indicate that this is allowed.
This is fine, but it might be better to add that explicit indicator to all registries so that no one has to dig into the depths of the process to find out why it’s OK for registries but not recommendations.
Does this need clarification in the Process? It seems to me something in pubrules my me sufficient and more appropriate.
If it goes into pubrules, then the last clause starting with “without needing” could be removed from the process
Registry tables are subject to the definition of the registry. And it's completely handled per-registry, the process does not constrain those changes but expect the registries to define the constraints.
So, the candidate/proposed dance is only applicable to the registry definition, which we don't expect to be updated often. Those types of changes don't cover new features.
See also #1085 - although this here issue is about the presentation and editorial side of how the process describes what changes are allowed, and maybe that could be fixed in pubrules, but there may well be another more substantive issue with how changes are allowed in Registries in CR state, so potentially these two issues could be dealt with together.
