ISSUE-153: Would interface and event name change be possible and clearer

Would interface and event name change be possible and clearer

State:
CLOSED
Product:
Proximity API
Raised by:
Frederick Hirsch
Opened on:
2013-10-02
Description:
http://lists.w3.org/Archives/Public/public-device-apis/2013Sep/0061.html

In the Proximity Events specification, are the names are clear and whether they should be changed since the interfaces and events are really about distance and proximity, not devices and users.
The concern is whether the names would be confusing for developers using the API.

Specifically, the introduction states:

[[

The DeviceProximityEvent interface provides web developers information about the distance between the hosting device and a nearby object.

The UserProximityEvent interface provides web developers a user-agent- and platform-specific approximation that the hosting device has sensed a nearby object.

]]

We agreed to bring the question to the WG:

(1) Would it be clearer to change the names to indicate that one is about distance and the other is about sensing a nearby object, e.g. ObjectDistanceEvent and NearbyObjectEvent (to make up some possible names).

(2) Are implementations and adoption (specifically Mozilla) at a point where a change is possible or would this be disruptive at this point?

(3) If a name change is possible and appropriate, which names should we use.?
Related Actions Items:
No related actions
Related emails:
  1. [admin] Draft minutes 17 October 2013 teleconference (from Frederick.Hirsch@nokia.com on 2013-10-17)
  2. Re: Agenda - Distributed Meeting 17 October 2013 (Thursday) (from jean-claude.dufourd@telecom-paristech.fr on 2013-10-17)
  3. Re: Agenda - Distributed Meeting 17 October 2013 (Thursday) (from dom@w3.org on 2013-10-17)
  4. Agenda - Distributed Meeting 17 October 2013 (Thursday) (from Frederick.Hirsch@nokia.com on 2013-10-17)
  5. Re: [Proximity] WG agreed not to change Proximity naming, closing ISSUE-153 (from plh@w3.org on 2013-10-11)
  6. [Proximity] WG agreed not to change Proximity naming, closing ISSUE-153 (from Frederick.Hirsch@nokia.com on 2013-10-11)
  7. Agenda - Distributed Meeting 10 October 2013 (Thursday) (from Frederick.Hirsch@nokia.com on 2013-10-10)
  8. Draft minutes today 3 October 2013 (from Frederick.Hirsch@nokia.com on 2013-10-03)
  9. Agenda - Distributed Meeting 3 October 2013 (Thursday) (from Frederick.Hirsch@nokia.com on 2013-10-02)
  10. DAP-ISSUE-153: Would interface and event name change be possible and clearer [Proximity API] (from sysbot+tracker@w3.org on 2013-10-02)

Related notes:

http://lists.w3.org/Archives/Public/public-device-apis/2013Sep/0062.html

"Mozilla has shipped this API and we can not change names. Nothing prevents
us from adding new APIs/events"

Frederick Hirsch, 2 Oct 2013, 17:39:54

No information on usage is available from Mozilla, data is not collected.

http://lists.w3.org/Archives/Public/public-device-apis/2013Sep/0065.html

Frederick Hirsch, 2 Oct 2013, 17:40:36

[fjh]: feedback on list from Mozilla that too late to change naming for implementation, WG agrees to close issue with no change

3 Oct 2013, 14:10:21

Display change log ATOM feed


Anssi Kostiainen <anssi.kostiainen@intel.com>, Reilly Grant <reillyg@google.com>, Chairs, Fuqiao Xue <xfq@w3.org>, Staff Contact
Tracker: documentation, (configuration for this group), originally developed by Dean Jackson, is developed and maintained by the Systems Team <w3t-sys@w3.org>.
$Id: 153.html,v 1.1 2019/11/08 08:58:12 carcone Exp $