Dropping the device-info fields from BluetoothDevice

Hi all,

I'm strongly considering dropping the 4 fields from BluetoothDevice
that are populated from the Device Info service: vendorIDSource,
vendorID, productID, and productVersion (and maybe deviceClass while
I'm at it). They're holdovers from copying the interface from
chrome.bluetooth.Device and don't exist on Android
(https://developer.android.com/reference/android/bluetooth/BluetoothDevice.html)
or CoreBluetooth
(https://developer.apple.com/library/ios/documentation/CoreBluetooth/Reference/CBPeripheral_Class/index.html).
Folks will still be able to explicitly navigate the GATT tree to read
those fields.

They're also the only thing that requires connecting to the device
while the UA's creating a BluetoothDevice instance
(https://webbluetoothcg.github.io/web-bluetooth/#get-the-bluetoothdevice-representing),
and the resulting asynchrony is causing a small problem specifying the
navigator.bluetooth.referringDevice field in
https://rawgit.com/jyasskin/web-bluetooth-1/eddystone-upgrade/index.html#dom-bluetooth-referringdevice.
This could be solved by moving the referring device inside the result
of navigator.permissions.query({"bluetooth"}), but if we can get rid
of the fields, that's easier.

Any objections?

Thanks,
Jeffrey

Received on Friday, 15 April 2016 22:18:41 UTC