- From: Tobie Langel via GitHub <sysbot+gh@w3.org>
- Date: Mon, 19 Sep 2016 15:30:25 +0000
- To: public-device-apis-log@w3.org
@rwaldron: The main problem here, outside of preferences expressed by different folks on this thread, is that there's no way to express this in WebIDL. The newly added _namespace_ (arguably a misnomer) doesn't let us do that either (it can't contain constructors). As a side note, there is no plan to call `Accelerometer`, `AccelerometerSensor`. It should just be `Accelerometer` (see [Extensibility section on naming](https://w3c.github.io/sensors/#naming)). While I hear your concerns about the lack of namespacing, I do also have some concerns about namespacing: 1. it's inconsistent with the rest of the platform, 2. it might delay shipping the spec and implementation for years (or at least until we get ES6 modules in the browser), 3. the benefits are essentially cosmetic. I'd be much more inclined to have a conversation around this if we had a clearer path as to what it would imply time-wise, in relationship to ES6 modules, and in WebIDL terms to namespace concrete sensors. It would be good to hear back from implementors on this topic and it would be super useful to know if there were other parts of the platform being worked on right now that would adopt a similar design. -- GitHub Notification of comment by tobie Please view or discuss this issue at https://github.com/w3c/sensors/issues/127#issuecomment-248027040 using your GitHub account
Received on Monday, 19 September 2016 15:30:39 UTC