<MikeSmith> shu: the data that associates anchors in the HTML spec with particular MDN articles is at https://github.com/w3c/mdn-spec-links/blob/master/html.json
17:56:06 the top-level keys are the spec anchors/IDs
17:56:31 Bikeshed and Respec spec all use data from that same repo
17:57:13 and one day we will also have MDN links in the ES spec, because we already have all the data needed
17:57:16 https://github.com/w3c/mdn-spec-links/blob/master/ecmascript.json
17:58:01 and for the ECMA-402 spec, and even for 10+ TC39 proposals
17:58:56 for the JavaScript features the spec URLs are in the data in the https://github.com/mdn/browser-compat-data/tree/master/javascript tree
18:00:56 but for all non-JavaScript features/specs (e.g., the HTML spec) the spec-URL data is regularly (re)generated by a script I run that scrapes all the MDN articles and extracts the spec URL from the Specifications sections/tables of the MDN articles
18:06:25 <shu> MikeSmith: i'm calling it for the day, but speaking as an ecma262 editor, MDN linking would definitely be great for ecma262
18:06:32 let's chat more about that later
18:06:38 <MikeSmith> yup
18:17:13 <leobalter> MikeSmith: I'm glad to know you have what you need for ECMA-402, but please let me know if there is anything else I can help
18:23:48 <MikeSmith> Hi leobalter
18:24:14 <leobalter> hi! 
18:24:23 <MikeSmith> great to see you hear and it’s also been great to see you getting involved with the web-components work
18:25:13 about what we need for MDN annos and ECMA-402, it’s the same as for the ES spec itself and I think for the proposals too
18:25:31 by which I mean, I think they are all published using the same build tool
18:26:02 so it’s a matter of adding support to that common build tool
18:26:36 and for that I think maybe some of the same code from Respec could maybe be reused
18:27:22 the current Respec main maintainer is really savvy about JavaScript coding for this kind of thing
18:27:55 I think he even actually has some of the source in TypeScript
19:02:17 <leobalter> I'll sync this with the ECMA-262 as the build process is basically the same.