6.4. Submittal Package Format Procedures
This section describes the procedures for submitting DTD candidates for evaluation and approval to the ASRL. SGML DTD candidates should be submitted to USAPA at the ASRL. USAPA will review the candidates, and if there appears to be a con ict with functional requirements, USAPA will coordinate with the functional requirement proponent.
6.4.1. SUBMISSION PACKAGE. Each submission package should be comprised of the following five parts.
6.4.2 SUBMISSION PACKAGE CONTENTS. Physical submission requirements vary depending upon the delivery option selected. The following paragraphs describe each part of the submission package.
6.4.2.1 DTD Information. Table 6-2 describes the data elements which comprise the DTD Information part of the submission package.
DTD information will be submitted in ASCII using the format template below. Each data entry must immediately follow the "=>" character in the template.
6.4.2.2 DTD Abstract. Each DTD submitted must have an abstract. An abstract is a registry term for a user-provided narrative entry describing the DTD. The abstract should provide an overview of the DTD’s purpose, its public identifier (PI), and other information identifying the DTD.
6.4.2.3 Sample DTD. The DTD for which registration is being requested must be included in the submission package. The following is a sample DTD.
<!--************** START OF FILE *******************-->
<!-- SUPPLEMENT NOTICE: This file is made available to
provide the user with a digital representation of the DTD
found in Appendix B of MIL-T-38804B. This file is incomplete
without MIL-T-38804B.-->
<!-- NOTE: The start and end of this file are marked with a
row of asterisks. If these rows are not present the file
may not be complete!-->
<!-- MIL-T-38804B Supplement DTD -->
<!-- The following set of declarations may be referred to by
using a public entity as follows:
<!ENTITY % m38804bsup PUBLIC "-//USA-DOD//DTD MIL-T-38804B
SUPP//EN" >
%m38804bsup;-->
<!-- NOTE: In order to parse the following DTD subset alone,
append the following statement to the beginning of the file:
<!DOCTYPE docsupp {and the associated"}>" to the end of the
file.-->
<!--ENTITY DECLARATION-->
%m38804b;
<!--****************** END OF FILE ************************-->
6.4.2.4 DTD Certification. The submission package must contain a statement of certification, signed by the responsible authority from the submitting activity, that the candidate DTD meets all the submission criteria and is in compliance with MIL-STD-2361(SC) and MIL-PRF-28001. The certification should identify the cognizant DoD organization certifying compliance. Figure 18 is an example of a DTD Certification.
6.4.2.5 Parse Logs. The submission package must contain parse logs (e.g., records of parsing) from at least three different ISO 8879–compliant parsers. It is recommended that one of the parsers be the SGMLS parser. SGMLS is public domain software and can be obtained through the ASRL at Uniform Resource Locator (URL): http://www.asrl.com. Figure 19 is an example of the first page of a parse report. If a parser does
6.4.3 Delivery options. Submission packages may be submitted on 3.5" DOS formatted diskettes or via an Electronic Mail message to the ASRL Administrator. Each option is described below.
6.4.3.1 Diskette delivery. Submissions on disk require that the five parts be contained in five separate MS DOS ASCII files on a 3.5" MS DOS formatted diskette. DTDs submitted by disk will share a common file name (where possible) for the first eight characters. Each part will have file name extensions as listed in Table 6-4.
Disk delivery will be made to the ASRL Administrator at the address below:
6.4.3.2 Electronic Mail. Submissions via E-mail will contain all five parts in one message. Each part will be delimited on a dedicated line as described in Table 6-5.