W3C home > Mailing lists > Public > public-device-apis@w3.org > October 2009

Re: What does it all hang off of?

From: Frederick Hirsch <frederick.hirsch@nokia.com>
Date: Wed, 7 Oct 2009 08:17:31 -0400
Cc: Frederick Hirsch <frederick.hirsch@nokia.com>, "Kapyaho Jere (Nokia-D/Tampere)" <Jere.Kapyaho@nokia.com>, "Marcin.Hanclik@access-company.com" <Marcin.Hanclik@access-company.com>, "stewart.brodie@antplc.com" <stewart.brodie@antplc.com>, "public-device-apis@w3.org" <public-device-apis@w3.org>
Message-Id: <ADD3558E-984B-4B97-B274-32B6637F0C30@nokia.com>
To: ext Anne van Kesteren <annevk@opera.com>
Isn't this an opportunity to fix this so for the future the new APIs  
aren't in an illogical place? What is the pragmatic issue with doing  
what Jere suggests?

regards, Frederick

Frederick Hirsch
Nokia



On Oct 7, 2009, at 5:30 AM, ext Anne van Kesteren wrote:

> On Wed, 07 Oct 2009 11:23:48 +0200, <Jere.Kapyaho@nokia.com> wrote:
>> I don't really see much utility in distinguishing APIs that use some
>> hardware capability (like camera) from those that use "software"
>> capabilities (like contacts), although I could live with it. But  
>> neither
>> of these broad groups should be accessible from navigator, as it is
>> conceptually wrong.
>
> We already crossed that bridge long ago, in my opinion. The Navigator
> object is used for these kind of APIs and creating inconsistency  
> with that
> seems misguided. You are not starting with a blank slate here. The Web
> Platform has a lot of history and creating yet another fork in the  
> little
> logic it has so far seems bad for authors. Everyone always thinks  
> they can
> do it right this time around, but I've yet to see that happen.
>
>
> -- 
> Anne van Kesteren
> http://annevankesteren.nl/
>
Received on Wednesday, 7 October 2009 12:18:34 UTC

This archive was generated by hypermail 2.3.1 : Monday, 23 October 2017 14:53:39 UTC