This standardization effort resulted in JABWT. As shown later in this
book, this standardization effort complements existing technologies
rather than replacing them. JABWT is built on top of the already established
and widely used Bluetooth protocol stack.
1.5.1 Java Community ProcessSM (JCP) and JSR-82
Standard APIs in the Java programming language are defined though the
JCP. The JCP coordinates the evolution of the Java programming
language. Each new API is developed as a Java Specification Request
Why JAVA Technology for Bluetooth Devices? 19
( JSR). All Java ME configurations, profiles, and optional packages are
defined as JSRs. The process for defining a standard Java API is as follows:
1. The potential specification lead submits a new JSR.
2. The JCP executive committee reviews and votes on the JSR.
3. After JSR approval, the specification lead forms an expert group.
4. The expert group defines the specification.
5. JCP members review the specification during the community
review period.
6. The specification is open for public review.
7. The specification lead submits the specification as the proposed
final draft.
8. The executive committee votes on the specification to accept or
deny the API.
9. If the vote passes, the final release of the specification is
announced.
The process just described was followed in standardizing the JABWT
under JSR-82 [22].
Pages:
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59