MIL-STD-2361 Digital Publications DevelopmentThis standard establishes the Extensible Markup Language XML requirements for digital development, acquisition, and delivery of Army administrative and technical and equipment publications. The requirements for technical and equipment publications include the development, acquisition, and delivery requirements for Electronic and Interactive Electronic Technical Manuals ETM/IETM. Further, this standard establishes the Standard Generalized Markup Language SGML requirements for digital development, acquisition, and delivery of Army training and doctrine publications. Designated appendices of this standard contain references to, and access instructions for, the Document Type Definitions DTD and Tag Description Lists for the development of Army publications in conjunction with the respective functional requirements documents. Data prepared in conformance to these requirements will facilitate the automated storage, retrieval, interchange, and processing of publications from heterogeneous data sources.

Pages 1 - 2 - 3 - 4 - 5 - 6 - 7 - 8 - 9 - 10 - 11 - 12 - 13 - 14 - 15 - 16 - 17 - 18 - 19 - 20 - 21 - 22 - 23 - 24 - 25 - 26 - 27 - 28 - 29 - 30 - 31 - 32 - 33 - 34 - 35 - 36 - 37 - 38 - 39 - 40 - 41 - 42 - 43 - 44 - 45 - 46 - 47 - 48

MIL-STD-2361C

rigidly interpreting the structure, content, and style requirements contained in AR 25-30. Methods of accessing the administrative publications DTD is contained in Appendix E.

4.4.5.5.1 SGML/XML Requirements. The SGML/XML requirements contained in this standard are applicable to, and shall be used to develop Multi-Service Army Regulation (MAR), Army Regulation (AR), Department of the Army (DA) Circular (CIR), DA Pamphlet (PAM), Manual for Courts-Martial (MCM) and Multi-Service DA Pamphlet (MAP). The administrative publication has one DTD to describe the

top level requirements contained in AR 25-30.

4.4.6 Notation Declarations. A notation declaration shall identify a data content notation used within the document. The notation is used in the accompanying application to identify drawings or illustrations which are non-SGML data (NDATA), such as Initial Graphics Exchange Specifcation (IGES), Computer Graphics Metafle (CGM), Consultative Committee for International Telegraphy and Telephony (CCITT) Group 4, Joint Photographers Experts Group (JPEG), Portable Network Graphics (PNG) and others. Unless otherwise specifed, notation declarations used in DTDs and style sheets developed to this standard shall be those contained in the appropriate content specifcation or standard.

4.4.7 SGML Special Features. Special features shall be defned as specifed in the contract or other form of agreement. Examples of special features include requirements for start tags, processing instructions, manual or automatic numbering, in-text references to numbered items, table handling, or additional

ISO 8879 features (e.g., SHORTTAG, CONCUR).

4.4.8 Conformance. When required in the contract or other form of agreement (see paragraph 6.2), each SGML/XML document instance shall be subjected to conformance inspection (parsing) in accordance with the contract or other form of agreement.

4.4.9 XML Declaration. The frst part of a document prolog informs the user it is an XML document and declares the version of XML being used. The character encoding utf-8 is the standard Latin characters and can be left out of the XML declaration. The encoding should be declared if it is different from the standard Latin IS0-8859-1. The standalone tells the XML processor whether there are any other fles

to load. The setting of the standalone should be no if there are other external entities or a DTD to load. The setting should be yes if the fle can stand on its own.

<?XML version="l.0" encoding="IS0-8859-l" standalone="no"?>

Source: https://assist.dla.mil -- Downloaded:

Check the source to verify that this is the current version before use.