- From: Rich Tibbett <rich.tibbett@gmail.com>
- Date: Thu, 3 Feb 2011 14:13:42 +0100
- To: Dominique Hazael-Massieux <dom@w3.org>
- Cc: public-device-apis@w3.org
- Message-ID: <AANLkTinRQU-+zgg7Wkdgerv252gon-fbxgH4_6J60fGB@mail.gmail.com>
On Wed, Feb 2, 2011 at 10:19 AM, Dominique Hazael-Massieux <dom@w3.org>wrote: > Hi > > As the group has been contemplating moving the Contacts API to Last > Call, I think one remaining show-stopper that we forgot to identify was > the availability of the integration into the HTML5 Event loop — which > has been in theory deferred to the Core Device document, but hasn't been > defined yet. > > In practice, I'm not sure the value of exporting that piece of the API > to an external document is that beneficial (compared to incorporating it > in documents that need it). > Not sure on this. The Device spec [1] provides a standard root node for sub-APIs to inherit and also details standard reusable interfaces such as PendingOp. This spec should also define standard Event Loop behavior for all derivative Device API specs, such as Contacts, to hook in to. The 'service' object in the Contacts spec is still not defined in the Device spec either. In short, I think there's some value in providing a separate Device spec to gather the core components for reuse. As such, I would quite like for the Device spec to be published at the same time as the Contacts API. > Independently of where it lives, the main thing we need is concrete text > before we can reasonably claim that Contacts is ready enough for LC. I > understand that Robin as an action item to work on this (ACTION-271), > but maybe we could find someone in the group willing to give him a hand? > I'm on hand to assist pending the decision above. Up to now the event loop stuff has been deferred to the Device spec, though it's been a while since that document saw any updates. - Rich
Received on Thursday, 3 February 2011 13:14:38 UTC