Clean up cross references/versioning

[annevk]

In https://github.com/whatwg/fetch/pull/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]

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]

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]

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

[marcoscaceres]

For autopub, we have https://github.com/w3c/web-performance/issues/34

For spec cleanup in general (including bad reference) https://github.com/w3c/web-performance/issues/35

[caribouW3]

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]

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

[caribouW3]

Wide review not completed, so transition requests are still stuck