W3C home > Mailing lists > Public > public-webapps@w3.org > April to June 2009

Re: An import statement for Web IDL

From: Ian Hickson <ian@hixie.ch>
Date: Tue, 30 Jun 2009 06:26:53 +0000 (UTC)
To: Maciej Stachowiak <mjs@apple.com>
Cc: Cameron McCormack <cam@mcc.id.au>, public-webapps@w3.org
Message-ID: <Pine.LNX.4.62.0906300625090.16244@hixie.dreamhostps.com>
On Mon, 29 Jun 2009, Maciej Stachowiak wrote:
>
> It would be nice if we could find a way to make things more rigorous 
> with a mechanism that's convenient to both spec writers and browser 
> developers.
> 
> On possibility: we could consistently use modules and have a way to 
> import by module name, a la Java. Specs could import other modules 
> wholesale with prose or an IDL fragment at the top of the document. We 
> could recommend that non-W3C spec specs should use "reverse DNS" style 
> module prefixes to avoid the possibility of collision.
> 
> This makes the name binding more rigorous than filename-based includes 
> and should not overly get in the way of implementations or specs.

I would rather have just one module for all of the Web platform, since at 
the end of the day there's only one namespace in JS.

However, I do think it'd be nice to have tools to help us check the IDL. 
Could we have a tool that just scans the textContent out of <pre> elements 
with class=idl, or something? We could give it the URLs of all the specs 
being developed, and every hour or day or something it could try to fetch 
all the specs, check that the IDLs still make sense, and if anything bad 
happens, post an e-mail to some list we all subscribe to.

-- 
Ian Hickson               U+1047E                )\._.,--....,'``.    fL
http://ln.hixie.ch/       U+263A                /,   _.. \   _\  ;`._ ,.
Things that are impossible just take longer.   `._.-(,_..'--(,_..'`-.;.'
Received on Tuesday, 30 June 2009 06:27:30 GMT

This archive was generated by hypermail 2.3.1 : Tuesday, 26 March 2013 18:49:31 GMT