- From: Zoltan Kis via GitHub <sysbot+gh@w3.org>
- Date: Thu, 12 Nov 2015 12:10:23 +0000
- To: public-device-apis@w3.org
I think what Dave may have meant here is to provide a mechanism - by which clients could tell the transformation algorithm and its parameters to be applied *at source* to the data before being exposed, and - for attaching metadata, so that less data is actually transferred, and by knowing the algorithm and the metadata, much of the missing data could be reconstructed on the client side. Basically, codec stuff. Also relates to negotiation mechanisms, see [here](https://github.com/w3c/sensors/issues/70#issuecomment-156084642). Problems with this is unlikely support from the sensors (unless they are expensive, with a lot of computing power to serve different clients needs). Also, we need to be explicit about use cases (because the "codec"s involved). What we could do now is to find real-world use cases, and be forward-compatible with eventual changes like the above would take. -- GitHub Notif of comment by zolkis See https://github.com/w3c/sensors/issues/68#issuecomment-156087352
Received on Thursday, 12 November 2015 12:10:28 UTC