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

Clean up cross references/versioning #271

Open
annevk opened this issue Apr 21, 2021 · 7 comments
Open

Clean up cross references/versioning #271

annevk opened this issue Apr 21, 2021 · 7 comments
Assignees
Projects

Comments

@annevk
Copy link
Member

annevk commented Apr 21, 2021

In whatwg/fetch#1202 we're making Fetch's integration with Resource Timing more concrete. This creates a weird situation however where we "Mark resource timing" ends up pointing to https://www.w3.org/TR/resource-timing-2/#dfn-mark-resource-timing whereas otherwise we reference the editor's draft at https://w3c.github.io/resource-timing/. This also leads to a double entry in the References section with both RESOURCE-TIMING and RESOURCE-TIMING-2. (Disregard for now that one is marked as non-normative. That's a bug in Fetch though it's mostly because of this since if the term would point to the editor's draft as expected it would be associated with RESOURCE-TIMING and it would all be good.)

@marcoscaceres
Copy link
Member

We need to have a larger discussion in the WG towards auto-publishing everything, and maybe dropping the whole -N thing. There is really no need to have editors drafts anymore if we can have living standards that live on TR.

@yoavweiss
Copy link
Contributor

We have WG agreement on auto-publishing all the things and dropping the levels whereever we can.

@marcoscaceres - would you be able to help with that work?

@marcoscaceres
Copy link
Member

Yes, absolutely. Cc'ing @caribouW3 also. We will work on it together.

@marcoscaceres
Copy link
Member

For autopub, we have w3c/web-performance#34

For spec cleanup in general (including bad reference) w3c/web-performance#35

@caribouW3
Copy link
Member

and dropping the levels whereever we can.

I think we can consider that the CfC is over, and then publish the CRs (they need transition requests, it's an opportunity to request the reuse of the non-versioned shortnames and drop levels).

@marcoscaceres
Copy link
Member

@caribouW3, what’s the latest with the transition requests, etc.?

@caribouW3
Copy link
Member

Wide review not completed, so transition requests are still stuck

@marcoscaceres marcoscaceres changed the title Reference mess Clean up cross references/versioning Sep 7, 2021
@yoavweiss yoavweiss added this to Triage in Triage May 5, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
Triage
Triage
Development

No branches or pull requests

4 participants