[css-backgrounds-3][css-box-3][css-color-3][css-fonts-3][css-page-4][css-speech-1][css-style-attr-1][mediaqueries-3][selectors-3][web-animations-css-integration] Convert specs to Bikeshed

[SebastianZ]

There are several specifications, which currently use an older preprocessor to generate the document. These specifications should be converted to use Bikeshed instead. This includes:

• CSS Backgrounds 3
• CSS Fonts 3
• CSS Paged Media 4
• CSS Speech 1
• Web Animations CSS Integration

---

Recs (probably useful just to get consistent dfn markup):

• CSS Color 3
• CSS Style Attributes 1
• Media Queries 3
• Selectors 3

Note that I didn't include WG Notes and the CSS snapshots. If considered valuable, those should be added to the list. I did add CSS Color 3, CSS Style Attributes 1, Media Queries 3 and Selectors 3 even when they are already recommendations, because I expect they may still get some formal changes.

Sebastian

[tabatkins]

Box is a dead spec, so I'm removing it from the list.

[plinss]

Several of the others are RECs, so it's unclear if we want to port the drafts to Bikeshed or not at this point. If there have been significant changes the we should consider issuing a PER, but then a Bikeshed conversion may introduce too many changes? (though it would be nice for all the link/dfn markup to be consistent and functional...)

[fantasai]

The current W3C Process requires a PER even for editorial (or even markup) changes:
https://www.w3.org/2015/Process-20150901/#rec-modify
This is a regression from the previous W3C Process:
https://www.w3.org/2005/10/Process-20051014/tr.html#rec-modify
Analysis of the change (checked in as “editorial”) and request to revert (not addressed):
https://lists.w3.org/Archives/Public/public-w3process/2014Oct/0143.html
Maybe Tantek can sort this out so we can update the RECs without superfluous nonsense. :)

[xfq]

The new W3C Process now allows Edited Recommendations to incorporate editorial changes without AC review: https://www.w3.org/2017/Process-20170301/#rec-modify

[svgeesus]

I don't see the value for porting Color 3. Color 4 is in bikeshed and defines everything Color 3 does plus the new stuff.

[plinss]

The main value in porting older specs is for linking. Shepherd's spec parser has some fairly effective heuristics for determining anchors types, but bikeshed generates unambiguous anchor data, so the spec will be easier (and more accurate) to link to (and easier for non-shepherd tooling to parse the spec). Second, having a bikeshed source on the draft server allows it to play in the continuous integration and keeps all links to other specs up to date. This obviously doesn't help RECs or anything on TR. Color 3 can benefit if other specs still link to it or if it links to other specs, judgement call.

[Loirooriol]

CSS Page 4 has been done in 1f0341f and 6ad91d9.