- From: Marcos Caceres <w3c@marcosc.com>
- Date: Mon, 29 Aug 2011 13:49:13 +0200
- To: Robin Berjon <robin@berjon.com>
- Cc: Marcos Caceres <marcosscaceres@gmail.com>, public-native-web-apps@w3.org
-- Marcos Caceres On Monday, August 29, 2011 at 1:42 PM, Robin Berjon wrote: > On Aug 26, 2011, at 21:34 , Marcos Caceres wrote: > > As we are unbound by commercial pressure here, how about we flip this a bit… instead of starting at the mobile phone with all it's boring/done to death sensors, we start somewhere more abstract or interesting: something like an Audrino (http://www.arduino.cc/) and a bunch of flex sensors, pressure sensors, etc. I mean get right into sensor theory… thermometers, odometers… or take a car as the first use case: how do I measure the gas in my car … as web service? Or even look at what sensors are around the house: light, power consumption, etc. > > > > We could start with use cases around that and build some prototypes for supporting "sensor arrays" (groups of sensors coordinated together that create meaningful output). > > You had me until you started talking about "sensor theory". Go easy, I'm just talking about: min, max, step, error… foundational stuff. Humans have been building sensors for a couple of millennia… we might have something to learn from them. > I'm all for prototypes, looking at the coolest hackable sensors, seeing what can be done with some JS, then trying to rationalise that into something we could standardise. Agreed.
Received on Monday, 29 August 2011 13:25:56 UTC