- From: Clarke Stevens <C.Stevens@CableLabs.com>
- Date: Wed, 12 Oct 2011 14:34:42 -0600
- To: Josh Soref <jsoref@rim.com>, "blsaws@gmail.com" <blsaws@gmail.com>
- CC: "anssi.kostiainen@nokia.com" <anssi.kostiainen@nokia.com>, "giuseppep@opera.com" <giuseppep@opera.com>, "public-device-apis@w3.org" <public-device-apis@w3.org>, "dsr@w3.org" <dsr@w3.org>
It would not meet key requirements from HNTF which is our primary motivation for solving the discovery problem. On 10/12/11 2:10 PM, "Josh Soref" <jsoref@rim.com> wrote: >Technically a stub implementation could only expose e.g. Public servers >reachable from the same origin's backend. It would still be a valid >implementation of the general api. Sure it wouldn't give access to local >(physical), local (bluetooth), or local (subnet) elements, but it would >let the user discover and select "sensors" (e.g. I might select the YYZ >weather station instead of the LAX weather station). This could easily be >quite valuable to me even though it might not quite match someone's >expectation. >--------------------------------------------------------------------- >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 Wednesday, 12 October 2011 20:36:01 UTC