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

c. Override the author's interpretation of contract requirements for content, style, and format.

6.4.2.1 Source File Confguration Control. Ideally, the processing system should have the capability to utilize the SGML/XML -tagged source fle (plus illustration fles) as input to the subsequent composition and output processes. However, this is not a requirement, and intermediate fles may be used. Confguration control of changes to either intermediate or output fles is necessary, since the fnal deliverable product is the SGML/XML -tagged source fle. All system processing should be governed by the following rule: When corrections are made to a working, intermediate, or output fle, corrections will be incorporated in the source fle which is the primary fnal deliverable product under the contract.

6.4.2.2 Spell Checking and Hyphenation. Requirements for spell checking and hyphenation may be specifed in the contract. Since processing systems may differ in the way they treat these subjects, users should not expect consistent treatment across system boundaries unless specifc requirements are established in advance.

6.4.2.3 Processing Instructions. Processing instructions are a tool provided by SGML/XML to handle unique or unusual conditions. Their use is discouraged, but not disallowed, because it is recognized that in some situations processing instructions are a necessary part of document processing. They are usually system-unique and are ignored by an SGML/XML parser, precluding all control except cursory syntax checks unless additional processing system software is used. Their use or exclusion should

be controlled by contract restrictions.

6.5 Subject Term (Key Word) Listing. The following subject terms (key words) are applicable: Administrative Publication

Army SGML/XML Registry and Library (ASRL) Assembly

Collective task

Doctrine

Document Type Defnition (DTD) Extensible Markup Language (XML) General information

Individual task Information chapter Information module Maintenance

Manual

Operator

Output Specifcation (OS) Publishing, Electronic

SGML/XML objects and constructs

Standard Generalized Markup Language (SGML) Supporting information

Tagging, Generic Theory of operation Troubleshooting

Work package

XML Stylesheet Language (XSL)

XML Stylesheet Language for Formatting Objects (XSL-FO) XML Stylesheet Language Transformation Language (XSL-T)

6.6 Changes from previous issue. Marginal notations are not used in this revision to identify changes with respect to the previous issue due to the extent of the changes.

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

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