5 years, 2 months ago.

What is a GATT?

Several new (for me) capitalised words are introduced. It would be very nice, especially for novices, if the meaning of those words could be found by "search". Most capitalisations are even not defined at all...

I read somewhere "General Access Profile (GAP)". That's understandable.

But then: "Services use the Generic Attribute Profile (GATT) to structure the information according to characteristics, and they're bundled together in various profiles." I expect that GATT means something like G.... A.... T.... T...., so "General Attribute Profile" is confusing, not logical.

What is an URI? You say somewhere ("usually an URL"), but I expect something like U.... R.... I..... If it is an URL, what/why is an URI something different then an URL?

What is an URL? I think I can guess what it is, but I am am not sure. And because you capitalised it, then please explain U... R.... L...

Question relating to:

Hi,

Thank you for your comment. We've added a list of abbreviations: http://docs.mbed.org/docs/ble-intros/en/latest/Additional/Abbr/

Please note that concepts that are not BLE-specific, like URI and URL, are often not explained in our BLE Intros, but we did add them to the abbreviations list to make it easier for readers to find further information.

Thanks again,

posted by Irit Arkin 07 May 2015

1 Answer

5 years, 2 months ago.

GATT Generic ATTributes. Or generic attributes protocol. As defined in Adopted Bluetooth Core Specifications V4.2

OK! I downloaded, printed and read all 2772 pages. https://www.bluetooth.org/DocMan/handlers/DownloadDoc.ashx?doc_id=286439 It is 15 kgs of paper and the pile is 30cm high. Thank you.

There is a list of Acronyms and Abbreviations beginning at p268 of the pdf. GATT is found. GAP is found URI is not found URL is not found

I would like software writers and documenters read this story: http://en.wikipedia.org/wiki/Tower_of_Babel "Come, let Us go down and there confuse their language, that they may not understand one another’s speech.”

At the end each software writer has a language that he, and only he, and no one else, understands.

posted by Geert Hospers 03 May 2015