- From: Suresh Chitturi <schitturi@rim.com>
- Date: Thu, 14 Jan 2010 10:23:02 -0600
- To: "Robin Berjon" <robin@robineko.com>, <public-device-apis@w3.org>
api, ext, service, device Alternate suggestion - 'system'. A system can be considered something that the underlying system/runtime provides you (whether it be a local or remote service/device). Hope this is entertaining enough!:-) Regards, Suresh -----Original Message----- From: public-device-apis-request@w3.org [mailto:public-device-apis-request@w3.org] On Behalf Of Robin Berjon Sent: Thursday, January 14, 2010 7:41 AM To: public-device-apis@w3.org Subject: ISSUE-67: Naming of "device" Hi all, I am loth to open a naming debate, so as agreed on the call yesterday let's make it swift. I initially planned on doing this on a Friday, but I won't be around tomorrow so today's the new Friday. We've resolved to use the navigator.device.<module>.<method> form yesterday (for APIs where it makes sense, naturally). It's been suggested that "device" isn't such a great name, and alternatives have been proposed. The following alternative (including keeping things as they are) have been proposed: device service api ext Since this is essentially a bike-shed decision, I've decided to use a variant of the Survivor decision process. The normal Survivor process is synchronous and therefore won't work well here. The variant is this: please vote with the list of options above ordered from the one you *hate most* (and therefore want to see voted off the island) to the one you hate least. The winner will be selected using a commonsensical ordering and tequila. Voting closes when I get to work Monday morning; since this is a vote (albeit informal) we don't need to know what the reasoning behind your preference is (though you may include it, if it's entertaining enough). My vote: api, ext, device, service. -- Robin Berjon robineko - hired gun, higher standards http://robineko.com/ --------------------------------------------------------------------- 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 Thursday, 14 January 2010 16:23:36 UTC