W3C home > Mailing lists > Public > public-web-bluetooth@w3.org > August 2014

Re: Notes from meeting between Chrome and Mozilla folks

From: Bran, Cary <Cary.Bran@plantronics.com>
Date: Fri, 8 Aug 2014 22:11:54 +0000
To: Vincent Scheib <scheib@google.com>, Shawn Huang <shuang@mozilla.com>
CC: public-web-bluetooth <public-web-bluetooth@w3.org>, Jeffrey Yasskin <jyasskin@google.com>, Marcos Caceres <marcos@marcosc.com>
Message-ID: <D00A98D8.74961%cary.bran@plantronics.com>
I too agree with needing a way to accept a UUID as device manufactures may come up with their own device specific services and the friendly name for standard services makes sense to me.

From: Vincent Scheib <scheib@google.com<mailto:scheib@google.com>>
Date: Friday, August 8, 2014 at 2:51 PM
To: Shawn Huang <shuang@mozilla.com<mailto:shuang@mozilla.com>>
Cc: public-web-bluetooth <public-web-bluetooth@w3.org<mailto:public-web-bluetooth@w3.org>>, Jeffrey Yasskin <jyasskin@google.com<mailto:jyasskin@google.com>>, Marcos Caceres <marcos@marcosc.com<mailto:marcos@marcosc.com>>
Subject: Re: Notes from meeting between Chrome and Mozilla folks
Resent-From: <public-web-bluetooth@w3.org<mailto:public-web-bluetooth@w3.org>>
Resent-Date: Friday, August 8, 2014 at 2:52 PM

I agree on the 2 points:
- Need a way to accept UUID per Bluetooth spec for non standard services
- Identifying standard services via their name vs full or short UUID makes sense. Let's do functionName("standard_gatt_service_name")


On Fri, Aug 8, 2014 at 12:49 PM, Shawn Huang <shuang@mozilla.com<mailto:shuang@mozilla.com>> wrote:
>> But
>> service UUIDs are designed to efficiently solve that.

> If the strings are unique, as it the case with the enum, I don't see how using a UUID is more efficient? The are both unique strings.
It makes sense to let browser automatically map human readable string to UUID internally for Bluetooth SIG assigned number(ex: Service/Characteristics),
this will make JS easier to write/read if developers want to implement standard GATT profiles.

But we still need API to accept UUID as the parameter for those vendor specific defined GATT Profiles (it contains their own Service/Characteristic UUID).





________________________________

CONFIDENTIALITY NOTICE: This e-mail transmission, and any documents, files or previous e-mail messages attached to it, may contain information that is confidential and/or legally privileged. If you are not the intended recipient, or a person responsible for delivering it to the intended recipient, please DO NOT disclose the contents to another person, store or copy the information in any medium, or use any of the information contained in or attached to this transmission for any purpose. If you have received this transmission in error, please immediately notify the sender by reply email or at privacy@plantronics.com, and destroy the original transmission and its attachments without reading or saving in any manner.

For further information about Plantronics - the Company, its products, brands, partners, please visit our website www.plantronics.com.
Received on Friday, 8 August 2014 22:12:35 UTC

This archive was generated by hypermail 2.3.1 : Tuesday, 6 January 2015 19:38:27 UTC