Only curate specs that have a good standing #1023
Merged
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This leverages the
standing
property in browser-specs to exclude specs that don't have a good standing from data curation.This makes it possible to add specs to browser-specs at an earlier level for cross-referencing purpose (Specref and terms) without having to worry too much about its impact on CSS, elements, events, and IDL definitions. It also makes it possible to keep discontinued specs in browser-specs without having to worry about extracts becoming obsolete, invalid, or conflictual.
This is intended to replace #712 with a different exclusion logic. In #712, specs that were excluded from data curation were the ones that did not target browsers, based on the
categories
property. This does not help with the main source of CSS, events and IDL hiccups, which are more common in early API proposals. Plus I still think that filtering specs based on their categories is not the right approach.This will remove the following curated extracts:
This does not add any mechanism to create exceptions to the rule. That is on purpose. Let's be optimistic ;)
Note the plan to also make Reffy skip "discontinued" specs by default, in w3c/reffy#1341. With these two updates, the workflow becomes:
The rule for inclusion in NPM packages does not change: only specs targeted at browsers are included.