Skip to content
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

Link to Lower Level #292

Open
fantasai opened this issue Jan 21, 2022 · 2 comments
Open

Link to Lower Level #292

fantasai opened this issue Jan 21, 2022 · 2 comments

Comments

@fantasai
Copy link
Contributor

@svgeesus was pointing out that it's not obvious how to get from e.g. Snapshot 2021 back to Snapshot 2020 etc. because they are separate publications, rather than a dated sequence like earlier and newer versions of a draft. But we have this same problem with levelled specs in general: e.g. Cascade 4 doesn't have an obvious header link to Cascade 3 or to the set of Cascade specs.

Is there something we can do with in the headers and/or w3.org/TR/ that can help make a sequence of specs easier to relate?

@deniak
Copy link
Member

deniak commented Jan 24, 2022

This is something we haven't emphasized so far as we were not sure how the concept of 'series' (group of specifications with different levels) would go but we have the cover pages for the series, e.g. CSS and css-cascade, which takes the shortname without the level as parameter.
You could expose these links in the headers if this is useful.

With the upcoming TR redesign and the introduction of families (GH repo), the specifications of the same series will be grouped together.

@plehegar
Copy link
Member

We left up to the editors to add those information indeed, without constraining them. Rethinking the approach with our handling of series seems the right think to do indeed.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants