Re: Specs using Web IDL

Doug Schepers:
> As we talked about at the SVG F2F, we need to have a discussion about  
> what the exit criteria for Web IDL will be, since the implementations  
> are actually other specs, and there is concurrent development between  
> those specs and Web IDL.  This seems to be a special case with regards  
> to the Recommendation Track... should other specs be allowed go to  
> CR/PR/Rec before Web IDL?  Should we park them in CR while features of  
> Web IDL are solidified by other specs, like HTML5?

Yeah I’m still not sure what the best approach for CR exit criteria is.

> Will there be an updated revision or version 2 of Web IDL?

My guess is that there will be if:

  * we find mistakes or implementors aren’t happy with how some things
    are specified,
  * we want to add some extended attributes or definitions that would be
    generally useful across multiple specs, or
  * we want to update the ECMAScript language binding to ES5.

> Another possible implementation of Web IDL would be an IDL checker, like  
> a validator.

Yes, a validator or other kind of processing tool would demonstrate
whether the conformance requirements on IDL fragments are internally
consistent, at least.

I think what we want to do is to make sure that each feature that is in
the spec is useful for at least one other spec.  There are plenty of
features that currently are depended on by other specs, but I don’t know
if (m)any people have read through the detailed conformance requirements
they entail.  It’s these details that I think are in most need of
verification somehow.

-- 
Cameron McCormack ≝ http://mcc.id.au/

Received on Sunday, 28 June 2009 11:22:39 UTC