Re: ISSUE-67: Naming of "device"

service is better. However, isn't geolocation a service? Isn't mouse input a
service? Everything can be seen as a service too.... which can also be a
slippery slope.

On Mon, Jan 18, 2010 at 2:44 AM, Nilsson, Claes1 <
Claes1.Nilsson@sonyericsson.com> wrote:

>  Dion, I agree on your arguments against the “device” namespace. That’s
> why my first choice is “service” (even though I am working at a “device”
> company J )
>
>
>
> Claes
>
>
>
> *From:* Dion Almaer [mailto:dion@almaer.com]
> *Sent:* fredag den 15 januari 2010 19:40
> *To:* Nilsson, Claes1
> *Cc:* Robin Berjon; public-device-apis@w3.org
> *Subject:* Re: ISSUE-67: Naming of "device"
>
>
>
> I know that there are already minutes on this, but I am with Doug. Having a
> namespace like this adds nothing and feels arbitory. My laptop is a device.
> Geolocation is one example. Access to video recording abilities? If you look
> to the future won't MOST APIs be available through "devices"? It feels like
> a decision based on the naming of this working group and should be
> reconsidered. (This is coming from someone who works for a "device" company)
>
> On Fri, Jan 15, 2010 at 1:24 AM, Nilsson, Claes1 <
> Claes1.Nilsson@sonyericsson.com> wrote:
>
> My vote is: api, ext, device, service
>
> Looking forward to the tequila.
>
> Claes
>
>
> > -----Original Message-----
> > From: public-device-apis-request@w3.org [mailto:public-device-apis-
>
> > request@w3.org] On Behalf Of Robin Berjon
> > Sent: torsdag den 14 januari 2010 14:41
> > 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/
> >
> >
> >
> >
>
>
>