120. Definition: User-Facing Capabilities express the requirements for the interaction between end users and all CIS Capabilities, in order to process Information Products in support of Business Processes. User-Facing Capabilities incorporate the User Appliances, as well as the User Applications that run on those appliances.
121. For the purposes of this Volume, only the standards for User Applications need to be cited.
122. Definition: User Applications, also known as application software, software applications, applications or apps, are computer software components designed to help a user perform singular or multiple related tasks and provide the logical interface between human and automated activities.
123. To provide federated services the standards listed in Table D.15 should be adhered to.
| ID: Service/Purpose | Standards | Implementation Guidance |
|---|---|---|
| 1: Displaying content within web browsers. |
Browser plug-ins are not covered by a single specification. |
Applications must support the following browsers: Microsoft Internet Explorer v9.0 and newer, and Mozilla Firefox 12.0 and newer. When a supported browser is not true to the standard, choose to support the browser that is closest to the standard[a]. Some organizations or end-user devices do not allow the use of proprietary extensions such as Adobe Flash or Microsoft Silverlight. Those technologies shall be avoided. Implementers should use open standard based solutions instead (e.g. move to HTML5 / CSS3). Some AMN members do not allow the use of ActiveX controls in the browser. Browser plug-ins will need to be approved by AMN Change Advisory Board (CAB). |
| 2: Visualize common operational symbology within C4ISR systems in order to convey information about objects in the battlespace. |
|
All presentation service shall render tracks, tactical graphics, and MOOTW objects using this standard except in the case where the object being rendered is not covered in the standard. In these exceptional cases, additional symbols shall be defined as extensions of existing symbol standards and must be backwards compatible. These extensions shall be submitted as a request for change within the configuration management process to be considered for inclusion in the next version of the specification. |
| 3: Reliable messaging over XMPP | XMPP Clients must implement the following XMPP Extension Protocols (XEP):
|
All XMPP Chat Clients used on the AMN shall implement these two protocol extensions {this section will be enhanced in the next version based on a detailed recently conducted requirements analyzis}. |
| 4: Collaborative generation of spreadsheets, charts, presentations and word processing documents | Office Open XML:
Open Document Format:
|
OASIS Open Document Format ODF 1.0 (ISO/IEC 26300) and Office Open XML (ISO/IEC 29500) are both open document formats for saving and exchanging word processing documents, spreadsheets and presentations. Both formats are XML based but differ in design and scope. ISO/IEC TR 29166:2011, Information technology -- Document description and processing languages -- Guidelines for translation between ISO/IEC 26300 and ISO/IEC 29500 document formats. |
| 5: Document exchange, storage and archiving |
|
See Operational Record Retention Schedule and AMN JMEI Exit Instructions (Vol3) for further details. |
| 6: Representation of Dates and Times |
|
See also Table D.6 (ID 1 and 4) for time synchronization within and between systems When a DTG is expressed in local time, this must use the military time zone designator. For AFG this is D30. |
| 7: Internationalization designing, developing content and (web) applications, in a way that ensures it will work well for, or can be easily adapted for, users from any culture, region, or language. |
|
Best practices and tutorials on internationalization can be found at: http://www.w3.org /International/articlelist |
|
[a] E.g. using http://html5test.com to compare features for HTML5. |
||