On Jun 27, 2009, at 22:24 , Doug Schepers wrote:
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
Robin Berjon:
I wonder what the value is of having it on Rec track in the first place?
Could it simply be a Note?
I’d be reluctant to make it a note, given the normative requirements it
makes of implementations of a given IDL fragment.
--
Cameron McCormack ≝ http://mcc.id.au/
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
Hi, Cam-
Cameron McCormack wrote (on 6/28/09 7:10 AM):
Robin Berjon:
I wonder what the value is of having it on Rec track in the first place?
Could it simply be a Note?
I’d be reluctant to make it a note, given the normative requirements it
makes of implementations of a given IDL fragment.
Hi, again-
Oops, email sent too soon... I need to disable the keyboard shortcut for
Send on Thunderbird, it's very annoying.
Email finished inline
Doug Schepers wrote (on 6/28/09 3:37 PM):
Hi, Cam-
Cameron McCormack wrote (on 6/28/09 7:10 AM):
Robin Berjon:
I wonder what the value is
Doug Schepers:
Maybe we should have a LC to draw out these comments...
Using LC to get detailed review seems fine. I suppose it will be in the
interests of authors of specs dependent on Web IDL to ensure that the
details are correct before it gets more mature.
if not now, what timeframe are
The OMG-ish IDL fragments published for W3C specs use C preprocessor-
like directives to include other IDL fragments, so that names resolve
correctly. For example,
http://www.w3.org/TR/DOM-Level-2-Events/idl/events.idl has:
#ifndef _EVENTS_IDL_
#define _EVENTS_IDL_
#include dom.idl
