François Daoust

> From the webref side, would it be better to have values for some of these items? @tidoust , do you have opinions about this? We're trying to avoid maintaining...

@tabatkins The Remote Playback API has been re-published since this issue was created (and the Editor's Draft on w3c.github.io is now the generated version of the document). Could the spec...

Gentle ping @tabatkins @plinss. Could the specs be added to Shepherd, please?

Thanks @plinss. The definitions contract does not talk about headings and it seems that Shepherd cannot extract headings from specs generated with ReSpec, e.g.: [Presentation API](https://github.com/tabatkins/bikeshed-data/blob/main/data/headings/headings-presentation-api-1.json), [Payment Request](https://github.com/tabatkins/bikeshed-data/blob/main/data/headings/headings-payment-request-1.json). This makes...

Bikeshed retrieves the data it needs from [bikeshed-data](https://github.com/tabatkins/bikeshed-data), so as long as the headings do not appear there, they won't show up locally either. @tabatkins, sections and headings are in...

That's what I'm proposing to change in #2358, preferring `"section": true` over `"type": "heading"` to get the headings because that gives better IDs in specs generated with ReSpec. I didn't...

> This reminds me, is there a way to get spec-prod to use a pinned version of Bikeshed? It would be convenient to avoid build breakage, plus we're already pinning...

That may be a nice end goal, but that does not match practice for now. There are a number of interfaces that, for various reasons, are defined in one spec...

> Although before CR it seems we are supposed to do a "Last Call announcement" and give time for folks to comment on the spec. Maybe now is the time...

Sure! For clarity, is that for WebGPU and WGSL or just for WebGPU? Issue title includes both but your last comment only mentions WebGPU (and I'm not seeing something explicit...