| 01:34 | <Domenic> | Does anyone have good writeups on why "you should use URL/URIs as your API's unique ID format" turned out poorly and has mostly been abandoned? Maybe hsivonen? |
| 02:13 | <sideshowbarker> | zcorpan: FYI https://www.w3.org/wiki/TPAC/2022/SessionIdeas |
| 07:00 | <hsivonen> | Does anyone have good writeups on why "you should use URL/URIs as your API's unique ID format" turned out poorly and has mostly been abandoned? Maybe hsivonen? |
| 07:00 | <Domenic> | Searching mailing list archives is a good idea... |
| 07:04 | <Domenic> | Hmm, that was a mistake, URI/URL discussions on mailing lists are terrible, I'd forgotten how bad |
| 13:51 | <Maxim Vaarwel> | Every task has script evaluation environment settings object set. What is this case when task has in set more than one environment settings object? I couldn't find anything that would be match with that case. |
| 16:31 | <Sam Sneddon [:gsnedders]> | is it expected that platform.html5.org is down? is there anything else similar (e.g., derived from w3c/browser-specs) that is up? (cc annevk given AFAIK it's his server or at least domain?) |
| 16:35 | <sideshowbarker> | Sam Sneddon [:gsnedders]: coincidentally, I’ve been working on an update to platform.html5.org, so I do have something similar and I can have it up pretty shortly …and as far as platform.html5.org itself, it’s not expected that it should be down — I think there’s some intermittent problem at Dreamhost that’s causing it to go down, but I don’t have the access to troubleshoot it. The DNS is through Dreamhost but it’s just a CNAME to an address on the whatwg.org infrastructure. |
| 16:48 | <sideshowbarker> | Sam Sneddon [:gsnedders]: https://w3c.github.io/mdn-spec-links/ |
| 16:50 | <sideshowbarker> | smaug: ↑ |
| 16:53 | <sideshowbarker> | I’ll also have that up at platform.html5.org once we get the routing problem figured out |
| 16:53 | <smaug> | sideshowbarker: curious, what does the number in Docs column mean? |
| 16:54 | <sideshowbarker> | it’s the number of MDN articles which reference the given spec |
| 16:55 | <smaug> | Can one see the references in MDN somewhere? |
| 16:56 | <sideshowbarker> | those are in data files; e.g., https://w3c.github.io/mdn-spec-links/accelerometer.json |
| 16:56 | <sideshowbarker> | I guess I can add links to those too |
| 16:57 | <sideshowbarker> | the keys in those data files are IDs/anchors in the spec |
| 16:57 | <sideshowbarker> | the slug values are the pathnames of the MDN articles |
| 16:58 | <sideshowbarker> | I guess I should also mention that the HTML output is generated from https://w3c.github.io/mdn-spec-links/specdata.json |
| 17:01 | <sideshowbarker> | …which is an array of objects where each object represents a spec and has its URL and the associated wpt.fyi URL and caniuse URL and MDN URL and then an array of which engines currently support the spec |