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

4.4.3 Document Type Declaration. The document type declaration shall conform to ISO 8879,

MIL-PRF-28001, this standard, and reference a contractually specifed DTD (see Appendixes A, B, C, and D or E) with a formal public identifer (see paragraph 4.4.4.5). An XML document type declaration shall include a system identifer after the formal public identifer.

4.4.4 Document Type Defnition (DTD). The SGML DTD shall conform to ISO 8879 and this standard. An XML DTD shall conform to the XML Declaration (see paragraph 4.4.9), REC-xml-20001006, ISO

8879, and this standard.

4.4.4.1 SGML/XML Object and Construct Reuse. DTDs used for development of Army publications pursuant to this standard, shall contain Army-approved standard SGML/XML objects and constructs as defned by this standard. Army-approved SGML/XML objects and constructs shall be obtained from the ASRL for use in development of all Army publications developed using SGML/XML.

4.4.4.2 SGML/XML Object and Construct Tailoring. Tailoring of SGML/XML objects and constructs is allowed when required to meet specifc publications functional requirements. However, such tailoring shall occur within the parameters of existing SGML/XML objects and constructs. The processes for changing existing SGML/XML objects and constructs, or creating new ones, are covered in paragraph 4.4.4.3.

4.4.4.3 SGML/XML Object and Construct Registration. When specifed in the contract or other form of agreement (see paragraph 6.2), SGML/XML object and construct requirements for the defnition of a document, or class of documents, structure and content that are not covered by Army-approved SGML/XML objects and constructs on the ASRL, shall be submitted to the ASRL for approval. SGML/XML objects and constructs that have not successfully completed the ASRL registration and approval process shall not be used for the development of Army departmental media.

4.4.4.4 SGML/XML Object and Construct Access. Access to Army-approved SGML/XML objects and constructs shall be obtained through the ASRL. Procedures for access to the ASRL are contained in Appendix A, Appendix B, Appendix C, and Appendix D.

4.4.4.5 Formal Public Identifer (FPI). A completed DTD shall have a formal public identifer (FPI) conforming to ISO 8879 and this standard. The FPI shall defne a specifc version of a completed DTD. A FPI shall not identify more than one DTD, or more than one version of a DTD. Formal public identifers such as "-//DOD-USA//DTD EXAMPLE MIL-HDBK-28001 V1.0 20000531//EN" shall have

the following characteristics:

a. A registered owner identifer. For the DoD, this will be the dash or minus sign (-).

b. An owner identifer, for all DoD components, this shall be "USA-DOD" entered without the quotation marks.

c. A minimal description (called the "public text description" in ISO 8879), divided into two sections: (1) Public text class - This is an SGML construct listed in ISO 8879. In the example, the

public text class is "DTD".

(2) Public text description - A short description of the object being identifed. In the example, the public text description is "EXAMPLE MIL-HDBK-28001 V1.0 20000531".

d. A two character language code. In the example, the two character code is "EN".

4.4.4.6 System Identifer. A completed XML DTD shall contain a system identifer conforming to this standard. A system identifer specifes the location of the DTD. A system identifer may be found after the root element in a document type declaration or after the formal public identifer. The key word "SYSTEM" is required if the system identifer succeeds the root element in a DTD. If a DTD contains a formal public identifer, the system identifer succeeds the FPI. The keyword "SYSTEM" in a system identifer is not required following a FPI. The following are examples of the system identifer in a DTD:

• <!DOCTYPE product SYSTEM "product.dtd">

• <!DOCTYPE product PUBLIC "-//USA-DOD//DTD MIL-STD-2361 Product//EN" "product.dtd">

4.4.5 Document Instance. The document instance shall conform to ISO 8879, this standard, and the contractually specifed DTD.

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

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