Vehicle Specific Display Services Sample Clauses

Vehicle Specific Display Services. The positive control over the remote services shall be a CUCS responsibility, to include the security settings for these services. It is a CUCS responsibility to ensure adequate services are selected for the remote displays. As an example, for the web browser service this means that the selected browser must have adequate security settings to disallow un-requested windows from popping up on the system; potentially have the capability to hide the close button; and disallow the resizing of the remote display windows, etc. Vehicle specific displays can be used to request additional vehicle specific displays. When these additional vehicle specific displays are required, they shall be initially display within the resource allocated by message #1202 or within the window from which it was requested. A second method of an operator initiating remote displays from the VSM is through the use of the STANAG 4586 “Subsystem State Report Reference” field of message #1001, Subsystem Status Detail Request. These processes ensure that the operator must request all remote panels for display thus maintaining positive control over the displays. Remote Displays shall not be initiated by the VSM via message #1100 or #1101 until the CUCS Resource Report has been transmitted to the VSM. VSM shall use remote services that transmit remote displays to the CUCS in accordance with Message #1202, CUCS Resource Report. This provides a second level of security to ensure remote displays are displayed where expected on the CUCS displays, and not covering critical data.

Vehicle Specific Display Services. For generating the remote displays according to the requirements identified in this section of the document, the following services shall be supported. The display formats are determined by the VSM. The following services are the minimum requirement of the CUCS platform to support interoperability with all VSMs and the maximum allowable for the VSM platform that shall be supported for interoperability: - Web Browser Services shall be compatible with: - ▇▇▇▇://▇▇▇.▇▇.▇▇▇/TR/REC-CSS1 Cascading Style Sheets, level 1 W3C Recommendation 17 Dec 1996, revised 11 Jan 1999 - ▇▇▇▇://▇▇▇.▇▇.▇▇▇/TR/REC-DOM-Level-1 Document Object Model (DOM) Level 1 Specification Version 1.0 W3C Recommendation 1 October 1998 - ▇▇▇▇://▇▇▇.▇▇.▇▇▇/TR/html4 HTML 4.01 Specification W3C Recommendation 24 December 1999 - ▇▇▇▇://▇▇▇.▇▇▇▇-▇▇▇▇▇▇▇▇▇▇▇▇▇.▇▇▇/publications/files/ecma- st/Ecma- 262.pdf Referred as to Jscript or JavaScript ECMA Script 262 or ISO/IEC 16262 3rd Edition December 1999 - Java applet mechanism shall be compatible with: - Sun Microsystems Compliant JRE V1.1 or superior version The Java applet mechanism shall be integrated with the Web Browser Service. - The X-Server Services shall be compatible with: - X11R6 X Window System Release 6

Vehicle Specific Display Services. The positive control over the remote services shall be a CUCS responsibility, to include the security settings for these services. It is a CUCS responsibility to ensure adequate services are selected for the remote displays. As an example, for the web browser service this means that the selected browser must have adequate security settings to disallow un-requested windows from popping up on the system; potentially have the capability to hide the close button; and disallow the resizing of the remote display windows, etc. Vehicle specific displays can be used to request additional vehicle specific displays. When these additional vehicle specific displays are required, they shall be initially displayed within the resources allocated by Message #42001 or within the window from which it was requested. A second method of an operator initiating remote displays from the VSM is through the use of the STANAG 4586 “Subsystem State Report Reference” field of Message #15001, Subsystem Status Detail Request. These processes ensure that the operator must request all remote panels for display thus maintaining positive control over the displays. Remote Displays shall not be initiated by the VSM via Message #16000 or #16001 until the CUCS Resource Report has been transmitted to the VSM. VSM shall use remote services that transmit remote displays to the CUCS in accordance with Message #42001, CUCS Resource Report. This provides a second level of security to ensure remote displays are displayed where expected on the CUCS displays, and not covering critical data. Refer to Section 4.25.2 Message #42001: CUCS Resource Report for additional requirements. Figure B1-6 below provides a representation of how the remote displays are generated using the subsystem reference report. The generic displays will identify a warning condition and any requirement to place a vehicle-specific display on the CUCS display screens. The additional information will usually be information specific to the air vehicle and not provided through the generic message set. In Figure B1-6, a generic warning indication is provided to the operator in the generic displays identifying a problem with Engine #2. An enunciator flashes to indicate to the operator that an engine warning state exists, and identifies a more detailed display is available to the operator. The operator may request the additional information by clicking on the enunciator, which then generates a request to the VSM through the generic message m...