W3C home > Mailing lists > Public > public-device-apis@w3.org > March 2014

Re: [admin] Cordova DAP prioritization proposal

From: <Frederick.Hirsch@nokia.com>
Date: Thu, 27 Mar 2014 19:25:35 +0000
To: <w3c@marcosc.com>
CC: <Frederick.Hirsch@nokia.com>, <mandyam@quicinc.com>, <public-device-apis@w3.org>, <mounir@lamouri.fr>
Message-ID: <5262A784-CB8D-4006-AFDF-791F0F7F1C54@nokia.com>
to some extent chicken-egg; having a standard can also help with implementer adoption, implementations help with progressing standards.  Hence the call for 2 implementations, to avoid premature progression, user adoption is not so clearly  measured, is it?

regards, Frederick

Frederick Hirsch

On Mar 27, 2014, at 2:52 PM, ext Marcos Caceres <w3c@marcosc.com> wrote:

> On March 27, 2014 at 2:23:50 PM, Mandyam, Giridhar (mandyam@quicinc.com) wrote:
>> But it was implemented in Webkit - https://www.webkit.org/blog/1861/last-week-in-webkit-battery-status-api-and-form-updates/,  
>> which I assume allowed the Tizen implementation (see https://developer.tizen.org/dev-guide/2.2.0/).  
>> Why does this not count? Has it been confirmed that this implementation is not interoperable?  
> I'm personally worried about progressing specs prematurely based on unreleased products. We had this happen with Widgets: lots of user agents that passed the test suite but nothing that had any market impact as none of those runtimes became real products. **I'm not saying that Tizen won't have a market impact** - just that we should not take things to Recommendation until products are in the hands of a significant set of developers and users. Making things "Rec" just because we can doesn't mean we should. 
> -- 
> Marcos Caceres
Received on Thursday, 27 March 2014 19:26:32 UTC

This archive was generated by hypermail 2.3.1 : Monday, 23 October 2017 14:54:02 UTC