430. 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.
| ID:Service/Purpose | Standard | Implementation Guidance |
|---|---|---|
| 1:Displaying content within web browsers. | Mandatory:
W3C Hypertext Markup Language HTML 4.0.1 W3C Extensible Hypertext Markup Language XHTML 1.0 W3C Cascading Style Sheets CSS 2.0 Emerging (2014): HyperText Markup Language, Version 5 (HTML 5), W3C Candidate Recommendation, Dec 2012. Cascading Style Sheets (CSS), Level 3(CSS 3), W3C Recommendation. |
Applications must support the following browsers: Microsoft Internet Explorer v9.0 and newer, and Mozilla Firefox 16.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 (HTML5 / CSS3) instead. |
| 2:Integration of remote content and application logic into aggregating applications, such as web portals | Mandatory:
|
Portlets are pluggable user interface software components that are managed and displayed in a web portal. |
| 3:Visualize common operational symbology within C4ISR systems in order to convey information about objects in the battlespace. | Mandatory:
Recommended: MIL-STD-2525C, Common Warfighting Symbology, November 2008. Emerging (2015):
|
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. |
| 4:Reliable messaging over XMPP | Mandatory:
XMPP Extension Protocols (XEP) Client Proifle:
{this section will be enhanced in the next version based on a detailed requirements analysis recently conducted} |
All XMPP Chat Clients used on an FMN instance shall implement these two protocol extensions. |
| 5:Collaborative generation of spreadsheets, charts, presentations and word processing documents | Mandatory:
ISO/IEC 29500:2012, Information technology -- Document description and processing languages -- Office Open XML File Formats
Recommended (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. |
| 6:Document exchange, storage and archiving | Mandatory:
ISO 19005-1:2005 - Document management -Electronic document file format for long-term preservation –Part 1: Use of PDF 1.4 (PDF/A-1) Emerging (2014): ISO 19005-2:2011, Document management -- Electronic document file format for long-term preservation -- Part 2: Use of ISO 32000-1 (PDF/A-2) |
|
| 7:Representation of Date and Times | Mandatory:
W3C profile of ISO 8601 defined in:
Recommended:
Conditional (for military command and control systems):
|
When a DTG is expressed in local time, this must use the military time zone designator. A mapping of UTC offsets to military
timezone designators can be found in the next table, which is based on JC3IEDM V3.1.4/ADatP-3 BL13.1 FFIRN/FUD 1003/1.
Note that up to 4 characters will be required to represent timezone designators (e.g. 042121M120JAN11 for time zone M120). |
| 8: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. | Recommended:
|
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. |
||
| UTC offset (positive) | Timezone Designator (Eastern Hemisphere) | UTC offset (negative) | Timezone Designator (Western Hemisphere) |
|---|---|---|---|
| 00:00 | Z | 00:00 | Z |
| +01:00 | A | -01:00 | N |
| +02:00 | B | -02:00 | O |
| +03:00 | C | -03:00 | P |
| +03:30 | C30 | -03:30 | P30 |
| +04:00 | D | -04:00 | Q |
| +04:30 | D30 | -04:30 | Q30 |
| +05:00 | E | -05:00 | R |
| +05:30 | E30 | -06:00 | S |
| +05:45 | E45 | -07:00 | T |
| +06:00 | F | -08:00 | U |
| +06:30 | F30 | -09:00 | V |
| +07:00 | G | -09:30 | V30 |
| +08:00 | H | -10:00 | W |
| +08:45 | H45 | -11:00 | X |
| +09:00 | I | -12:00 | Y |
| +09:30 | I30 | ||
| +10:00 | K | ||
| +10:30 | K30 | ||
| +11:00 | L | ||
| +11:30 | L30 | ||
| +12:00 | M | ||
| +13:00 | M60 | ||
| +14:00 | M120 |