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

Re: ISSUE-14: Gathering requirements [System Info & Events]

From: Robin Berjon <robin@robineko.com>
Date: Tue, 13 Oct 2009 17:09:08 +0200
Cc: (wrong string) 전종홍 <hollobit@etri.re.kr>, David Rogers <david.rogers@omtp.org>, "Nilsson, Claes1" <Claes1.Nilsson@sonyericsson.com>, "Jere.Kapyaho@nokia.com" <Jere.Kapyaho@nokia.com>, "jmcf@tid.es" <jmcf@tid.es>, "public-device-apis@w3.org" <public-device-apis@w3.org>
Message-Id: <C42A9436-FD97-453B-A8D3-9CB5041BA7EA@robineko.com>
To: "Tran, Dzung D" <dzung.d.tran@intel.com>

On Oct 8, 2009, at 22:39 , Tran, Dzung D wrote:
> Look like there is consensus that sensors need to be covered in the  
> Device APIs. I will take the action to take a first stab at the  
> requirements for sensors. We can decide later if it should be part  
> of System Info & Events or a separate API section.

Thanks, can you add it to the action tracker please?

Also, can you plan it so that basic, absolutely necessary v1 things  
are outlined separately from cool to have v2 things? A good way to  
tell the two apart is everything that can be labelled as "I cannot  
live without this, this WG is useless if it doesn't include it" is in  
v1, everything else is in v2 unless it is hanging really, really low.

Robin Berjon
   robineko  setting new standards
Received on Tuesday, 13 October 2009 15:09:38 UTC

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