- From: Marcos Caceres <marcosc@w3.org>
- Date: Fri, 16 Jul 2021 11:18:48 +1000
- To: spec-prod <spec-prod@w3.org>
Hi Editors, Just as a followup, if you are writing some WebIDL and are unsure if your IDL is valid, you can use the WebIDL Checker: https://w3c.github.io/webidl2.js/checker/ Not all spec authoring tools have a built-in WebIDL parser/validator, so the above can help catch common mistakes and provide useful error messages. It can even fix some common mistakes for you. The checker is actively maintained and generally up-to-date with the latest WebIDL spec draft. HTH! > On 15 Jul 2021, at 8:30 pm, Dominique Hazael-Massieux <dom@w3.org> wrote: > > Hi Spec Editors, > > If you edit specs that rely on WebIDL to describe your APIs, you may > encounter cases where you would like to express something in IDL that is > forbidden or seemingly impossible to do. > > Based on discussions that occurred in the context of the webref project > [1], a small group of people have volunteered to serve as a support team > when this kind of discussions emerge. At this point, Domenic Denicola, > Timothy Gu and Marcos Caceres have volunteered (with Francois Daoust and > myself more as observers) - they can magically invoked in a github > discussion happening in the w3c and WICG github organizations > respectively with the @w3c/webidl-design and @WICG/webidl-design monikers. > > We're starting with these two organizations, but can extend it to others > where WebIDL is being developed as the need arises and as we gain > experience with that set up. > > If you're available to provide expertise on WebIDL design and want to be > added to that team, please get in touch! > > Dom > > 1. https://github.com/w3c/webref/ - a project that publishes curated > view of IDL fragments across Web specifications, among other data >
Received on Friday, 16 July 2021 01:19:04 UTC