| 6 APPENDIX II |
| ANSI | American National Standards Institute |
|
API |
Application Programming Interface |
| HTML | HyperText Mark-up Language |
|
ITU |
International Telecommunications Union |
|
JAIN |
JavaTM APIs for the Integrated Network |
|
MO |
Managed Object |
|
OMAP |
Operations and Maintenance Application Part |
|
OAM |
Operations, Administration and Maintenance |
| QMS | Quality Management System |
|
OSI |
Open Systems Interconnection |
|
SCCP |
Signaling Connection Control Part |
|
SS7 |
Signaling System 7 |
|
TCAP |
Transactions Capabilities Application Part |
| Interpretation Guru | The expert that handles the maintenance of the specification. |
|
Managed Object |
An external representation of a functional and physical domain of a system. |
|
Peer |
A particular platform specific implementation of a JavaÔ interface or API. |
|
Protocol Layer MO |
A particular MO that has the capability to create and delete all MOs associated with a particular protocol layer. |
|
Shall |
Within the Requirements Section 3, if the wording of a specific requirement includes ‘shall’ then the incorporation of this requirement in the JAIN OAM specification is mandatory. |
| Should | Within the Requirements Section 3, if the wording of a specific requirement includes ‘should’ then the incorporation of this requirement in the JAIN OAM specification is strongly recommended but is not mandatory. |
|
Specification Lead |
The expert responsible for writing the specification with input from the other experts, and hence responsible for developing consensus within the group. This person shall possess strong diplomatic and writing skills as well as technical expertise. |