- From: Anne van Kesteren <annevk@annevk.nl>
- Date: Thu, 21 Jul 2016 12:47:35 +0200
- To: Dominique Hazael-Massieux <dom@w3.org>
- Cc: public-script-coord <public-script-coord@w3.org>, François Daoust <fd@w3.org>
On Fri, Jul 15, 2016 at 10:00 AM, Dominique Hazael-Massieux <dom@w3.org> wrote: > A question that emerged when we built the analyzer for the first point > was which WebIDL names are "exported" by a spec (i.e. reusable in other > specs). It is logically obvious that interface names are, and there are > plenty of reasons for dictionaries and enums to be; it wasn't initially > as clear to me that typedefs were, but usage clearly show they are (e.g. > EventHandler) — which leads to the result that the very generic "JSON" > name is defined (differently!) as a typedef in two different specs. What's the other specification that defines JSON? I know Fetch has it, but I'm happy to remove the indirection there since it's only used once. -- https://annevankesteren.nl/
Received on Thursday, 21 July 2016 10:48:03 UTC