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

On Thursday, 22 March 2012 at 07:05, Josh Soref wrote:

> 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. 
> 


Yes. But this is not the same thing, Josh. Permissions are generally baked into the API (or similar approach, hence we have a substation for feature permission).  

Received on Thursday, 22 March 2012 11:41:39 UTC