Re: CfC to change Sensor approach, not progress current draft

Sakari wrote:
> I think we should have something to replace the current spec before we
drop one. Now, we have nothing.

This is a bad requirement. We're dropping Feature Permissions. We decided it was the wrong direction. We shouldn't be required to have a replacement. Once we've identified an API is the wrong direction, we should acknowledge that. 
---------------------------------------------------------------------
This transmission (including any attachments) may contain confidential information, privileged material (including material protected by the solicitor-client or other applicable privileges), or constitute non-public information. Any use of this information by anyone other than the intended recipient is prohibited. If you have received this transmission in error, please immediately reply to the sender and delete this information from your system. Use, dissemination, distribution, or reproduction of this transmission by unintended recipients is not authorized and may be unlawful.

Received on Thursday, 22 March 2012 07:06:25 UTC