W3C home > Mailing lists > Public > public-device-apis@w3.org > October 2013

DAP-ISSUE-153: Would interface and event name change be possible and clearer [Proximity API]

From: Device APIs Working Group Issue Tracker <sysbot+tracker@w3.org>
Date: Wed, 02 Oct 2013 17:38:57 +0000
Message-Id: <E1VRQO1-0006d4-0t@shauna.w3.org>
To: public-device-apis@w3.org
DAP-ISSUE-153: Would interface and event name change be possible and clearer [Proximity API]

http://www.w3.org/2009/dap/track/issues/153

Raised by: Frederick Hirsch
On product: Proximity API

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.?
Received on Wednesday, 2 October 2013 17:38:58 UTC

This archive was generated by hypermail 2.4.0 : Friday, 17 January 2020 19:33:01 UTC