W3C home > Mailing lists > Public > public-script-coord@w3.org > July to September 2011

Re: [WebIDL] remove modules

From: Paddy Byers <paddy.byers@gmail.com>
Date: Thu, 14 Jul 2011 08:39:24 +0100
Message-ID: <CABEaZauOLJmROFQLcShT0R=NGW2C=7a42W+8Qccq2Go5fk4+BA@mail.gmail.com>
To: public-script-coord@w3.org

Two things to be aware of if we drop the feature:
> One, BONDI folks were using IDL modules, IIRC.  Although I think their
> spec stabilised well before now, so presumably they’re dependent on an
> earlier WD of Web IDL, and thus it’s probably not a big deal to drop the
> feature, aside from the fact that we should focus on the Web and not
> other concerns.

The BONDI spec has been superseded by the WAC spec [1] and this still uses
modules. The WAC spec is frozen and there is already a growing list of
incompatibilities between the WAC WebIDL and the latest WebIDL spec - so in
any event there would need to be changes if WAC creates a new revision of
its spec and wishes to migrate to the latest WebIDL.

However, the motivation for using modules I think still stands, in that a
module is the unit by which support for a given feature is enabled.

That is, we associate a WebIDL module with one or more features (in the
sense of [2]). If one or more of the features associated with a module is
successfully requested, then all of the interfaces belonging to that module
are available, and all of the objects (eg interface objects) entailed by
those interfaces are instantiated.

If modules are dropped from WebIDL, then there would still be a desire I
think to have a logical grouping of interfaces, but we would have to specify
that in prose instead of in WebIDL.

Thanks - Paddy

[2]: http://www.w3.org/TR/widgets/#the-feature-element-and-its-attributes
Received on Thursday, 14 July 2011 07:39:56 UTC

This archive was generated by hypermail 2.4.0 : Friday, 17 January 2020 17:14:04 UTC