systems equipment, rockets and electronic systems\). Some systems may require an inspection requirements manual only, or work cards only. For other systems a combination of both inspection manual and work cards may be more suitable. This specification provides for electronic delivery of data through the use of the Document Type Definitions \(DTD\) listed in Appendixes A through F. \(Appendix E has been deleted.\)

Pages 1 - 2 - 3 - 4 - 5 - 6 - 7 - 8 - 9 - 10 - 11 - 12 - 13 - 14 - 15 - 16 - 17 - 18 - 19 - 20 - 21 - 22

MIL-DTL-5096G

APPENDIX C

ACCEPTANCE AND FUNCTIONAL CHECK FLIGHT CHECKLIST

TAGGED LANGUAGE TOOLS

C.1 SCOPE.

C.1.1 Scope. This appendix describes the standard Air Force (AF) tagged language digital tools created

for developing and delivering AF Technical Manuals (TMs). These tools are available as subsets in the

Digital Support Suites (DSS) (see C.2) provided by the AF Technical Manual Speciications and Standards

(TMSS) activity. This appendix is a mandatory part of this detail speciication. The information herein

is intended for compliance.

C.1.2 Document Type Deinition (DTD). The DTD is the primary tool that is used as the structure for

authoring AF TMs and is based on rules outlined in MIL-HDBK-28001 and ISO 8879. See C.2.1 for

information about the DTD speciied for this appendix subset.

C.2 DSS.

The DSS is comprised of the following tools for authoring and rendering the TM. See A.3 for information

about obtaining DSS component iles in digital format through the TMSS activity website. For information

about the current status of DSS tools, see A.3.3.

C.2.1 DTD. The DTD provides the structure for the content in accordance with the content speciic

requirements of this speciication. To be delivered digitally, the TM will be tagged using the applicable

DTD provided through the TMSS activity. DTDs are furnished in Standardized General Markup Language

(SGML); however, this does not preclude converting TMs authored as SGML instances to Extensible Markup

Language (XML), if directed by the acquiring activity.

C.2.2 Formatted Output Speciication Instance (FOSI). The FOSI provides formatting for each element of

an SGML tagged instance for rendering as a page-oriented document. It contains formatting information that

conforms to the content speciic requirements of this speciication. It should be noted that the FOSIs

offered by the TMSS activity are written to be used with a speciic document composition engine, i.e., DL

ComposerTM, available for use on the AF JCALS.

C.2.3 Tag Description Table (TDT). The TDT provides detailed descriptions of the elements contained in

the DTD. The TDT contains the element tagging structure, parent elements, full element name, source

paragraph for this speciication, attribute descriptions unique to the element, and entities.

C.2.4 OmniMarkTM. OmniMarkTM is a text processing language that is used by TMSS to allow authors to

auto-generate redundant material that may be dificult to tag manually. DSSs contain OmimarkTM scripts

designed for use on the AF JCALS.