- From: Josh Soref <jsoref@rim.com>
- Date: Wed, 12 Oct 2011 16:49:32 -0400
- To: "C.Stevens@CableLabs.com" <C.Stevens@CableLabs.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>
You're sort of saying that "a hypothetical unimplemented api that we need can't be implemented by what we have today", that isn't surprising. I think that using CORS one could get significantly closer, although not all the way there unless someone creates a local device/bluetooth gateway. And someone could implement a java, or native, or whatever app that also talks to that remote server and thus enables integration. -- my understanding is that you've in fact done this. Otoh, For a prototype, it would work for testing. An api is about exposing conceptual features to an application. If the features I expose to you don't match your expectation, but they behave according to the api, then I, as the user, expect you, my friendly app vendor, to use them, no questions asked. I am not interested in vendor lock in. If you or someone else want a proprietary lock in api, then you don't need w3 for it. --------------------------------------------------------------------- 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:50:05 UTC