1、NOT MEASUREMENT SENSITIVE MIL-DTL-87269C 22 JANUARY 2007 SUPERSEDING MIL-PRF-87269A 1 October 1995 DETAIL SPECIFICATION DATA BASE, REVISABLE - INTERACTIVE ELECTRONIC TECHNICAL MANUALS, FOR THE SUPPORT OF This specification is approved for use by all Departments and Agencies of the Department of Defe
2、nse. Comments, suggestions, or questions on this document should be addressed to the Air Force Technical Manual Specifications and Standards (TMSS) Office, 754 ELSG/ILMT, WPAFB OH 45433 or e-mailed to SGMLSUPPORTwpafb.af.mil . Since contact information can change, you may want to verify the currency
3、 of this address information using the ASSIST Online database http:/assist.daps.dla.mil . AMSC 7704 AREA TMSS Distribution Statement A: Approved for public release; distribution is unlimited. Provided by IHSNot for ResaleNo reproduction or networking permitted without license from IHS-,-,-MIL-DTL-87
4、269C 2 1 SCOPE. 1.1 Scope. This specification prescribes the requirements for an Interactive Electronic Technical Manual Data Base (IETMDB) to be constructed by a weapon-system contractor for the purpose of creating Interactive Electronic Technical Manuals (IETM). These requirements cover the specif
5、ication for the IETMDB and are intended to apply to one or both of two modes as specified in a contract: (1) the interchange format for the data base to be delivered to the Government; and/or (2) the structure and the naming of the elements of the data base created and maintained by the contractor f
6、or purposes of creating IETMs which are in turn delivered to the Government. 1.2 Paragraphs with limited applicability. This specification contains paragraphs and specific requirements which may not be applicable to all Services. Such paragraphs or requirements are prefixed to indicate the Services
7、to which the limited applicability pertains: (A) for Army; (N) for Navy; (M) for Marines; and (F) for Air Force. 2 APPLICABLE DOCUMENTS. 2.1 General. The documents listed in this section are referenced in sections 3 and 4 of this specification. This section does not include documents cited in other
8、sections of this specification or recommended for additional information or as examples. While every effort has been made to ensure the completeness of this list, document users are cautioned that they must meet all specified requirements documents cited in sections 3 and 4, whether or not they are
9、listed in this section. 2.2 Government documents. 2.2.1 Specifications, standards, and handbooks. The following specifications, standards, and handbooks form a part of this document to the extent specified in this document. Unless otherwise specified, the issues of these documents are those listed i
10、n the issue of the Department of Defense Index of Specifications and Standards (DODISS) and supplements thereto, cited in the solicitation (see 6.2). DEPARTMENT OF DEFENSE SPECIFICATIONS MIL-PRF-87268 - Manual, Technical - General Content, Style, Format, and User Requirements for Interactive Electro
11、nic Technical Manuals DEPARTMENT OF DEFENSE STANDARDS MIL-PRF-28001 - Markup Requirements and Generic Style Specification for Exchange of Text and its Presentation MIL-STD-1840 - Automated Interchange of Technical Information (Unless otherwise indicated, copies of the above specifications, standards
12、, and handbooks are available from the Acquisition Streamlining and Standardization Information System ASSIST Web site http:/assist.daps.dla.mil/quicksearch/ ). 2.2.2 Other Government documents, drawings, and publications. The following other Government documents, drawings, and publications form a p
13、art of this specification to the extent specified in this document. Unless otherwise specified, the issues are those cited in the solicitation. DEPARTMENT OF DEFENSE PUBLICATIONS Provided by IHSNot for ResaleNo reproduction or networking permitted without license from IHS-,-,-MIL-DTL-87269C 3 DOD 52
14、00.1-R - Department of Defense Information Security Program Regulations DOD 5220.22-M - National Industrial Security Program Operating Manual (Documents may be obtained at http:/www.dtic.mil ) 2.3 Non-Government publications. The following documents form a part of this document to the extent specifi
15、ed in this document. Unless otherwise specified, the issues of the documents which are DoD adopted are those listed in the issue of the Department of Defense Index of Specifications and Standards (DoDISS) cited in the solicitation. Unless otherwise specified, the issues of documents not listed in th
16、e DoDISS are the issues of the documents cited in the solicitation (see 6.2). International Organization for Standardization ISO 10744 - Hypermedia/Time-Based Structuring Language (HyTime) (Documents may be obtained at http:/www.ansi.org/.) 2.4 Order of precedence. In the event of a conflict between
17、 the text of this document and the publications referenced above, the text of this document takes precedence. Nothing in this document, however, supersedes applicable laws and regulations unless a specific exemption has been obtained. 3 REQUIREMENTS. 3.1 General requirements. An IETMDB developed in
18、accordance with this specification shall conform to the Content Data Model (CDM) specified in this document (reference Appendix A). The IETM Content Data Model (CDM) provides a representation of technical information (TI) elements and their relationships. The CDM is composed of three separate layers
19、. The first is the “Generic Layer“. It defines general characteristics which are common across all applications. The second layer is the “Interchange Layer”. This layer has been established to provide a content data model (i.e. DTD fragment) holding area for harmonized, commonly used ETM and IETM da
20、ta structures. The Interchange layer exists in two parts. Part 1 is a holding area for harmonized standalone ETM DTD fragments that constitute contained subsets of or identified transforms to IETM functional IETM data structures found in Part 2 of the interchange layer. The final layer is called the
21、 “Content Specific Layer” (CSL) and it contains the defining elements for weapon system specific TI. 3.1.1 The “Generic Layer“ shall define the general elements which are common across all TI applications. This layer contains resource objects that can be used for any ETM or IETM application. The gen
22、eric layer defines the templates, linking elements, primitive elements, and context filtering elements which are used to create content specific DTDs. Templates define rules which must be followed in the creation of content specific DTDs and document instances. The templates provide the structure fo
23、r creating composite nodes, context dependent filtering, user interaction and branching. The templates provide basic sets of rules to which elements must adhere. Also included in the generic layer are configuration management version control and incremental update entities and elements that are used
24、 in conjunction with declared template attributes to support the selection and incremental update of revisable information units within documents, the version control and interchange packaging of documents as spine SGML instances, and the flagging of updated content. A basic security classification
25、entity is also provided to allow consistent identification of classified information within the IETM database. 3.1.2 The Interchange Layer provides a DTD fragment holding area for harmonized, commonly used IETM and ETM data structures. The Interchange layer exists in two parts. Provided by IHSNot fo
26、r ResaleNo reproduction or networking permitted without license from IHS-,-,-MIL-DTL-87269C 4 a. Part 1 is a holding area for harmonized standalone ETM DTD fragments that constitute contained subsets of, or have identified transforms to the interactive IETM data structures found in Part 2 of the int
27、erchange layer. b. Part 2 is a holding area for both harmonized and IETM-specific DTD fragments that employ the Generic Layer architectural forms to implement interactive technical manual traversal. 3.1.3 The Interchange Layer Part 1 contains the harmonized ETM DTD fragments which define the common
28、primitive elements and data structures. These elements and structures can be referenced from or appended to ETM DTDs to maximize upward compatibility of their instance data into an IETM database presentation environment while at the same time retaining their conventional ETM “electronic book“ functi
29、onality. This Part 1 interchange layer contains declarations for primitive TEXT, GRAPHIC, AUDIO, VIDEO, PROCESS, and LINK entities and data elements, and declarations for primitive LIST data structures. These harmonized primitive entities and elements, list data models and table data model are vital
30、 to the achievement of harmonious data migration from conforming ETM instances into IETM database environments. WARNING: THESE PRIMITIVE ENTITY, ELEMENT, AND DATA STRUCTURE DECLARATIONS SHALL NOT BE ALTERED. 3.1.4 The above warning noted, ETM DTD Data model developers are free to use all or part of
31、the remaining entity, element, data structure models and DTD fragments referenced in this document. Undesired model content can simply be commented out. Data model developers are advised that the less of the included common content that is used, the less the resulting ETM product instance will be in
32、 harmony with the IETM data base model. 3.1.5 The Interchange Layer Part 2 is the holding area for a harmonized set of common content entity, element and structure declarations and DTD fragments that employ the semantics and primitive elements found in the generic layer to implement interactive pres
33、entation models. The common elements and data structures contained in this area are provided as building blocks for content-specific layer data model developers and as harmonized pathways for the migration of ETM content that was developed employing the harmonized entities, elements, and structures
34、found in Part 1 of this layer. Data model developers are free to use all or part of the entity, element and data models provided in this document by commenting out undesired content. Data model developers are advised however that commenting out of any table or list models provided in this area will
35、also necessitate the removal of their entity declarations from the generic layer. IETM table and list functionality is dependent upon the presence of both this Part 2 Harmonized IETM Interchange Model Area DTD and the generic layer DTD in the Content-specific Layer DTD Content Data Model. 3.1.8 The
36、bottom layer, the content specific layer (CSL), shall employ the generic layer when defining elements for weapon system specific TI. Many content specific layers can be developed in accordance with the generic layer. An example CSL DTD is available for download. (See Appendix A). 3.2 The CDM generic
37、 layer is the DoD standard for any IETM technical information data base procured using this specification. In addition, unless otherwise specified by the procuring activity, the content specific layer Document Type Definition (DTD) (see 6.2). The IETMDB can be invoked by a procuring activity in eith
38、er one of two modes as follows, depending on whether a data base is (1) specified for interchange and delivery to the Government, or (2) being developed and maintained for the subsequent preparation of IETMs, but not actually delivered to the Government. a. Database interchange requirements. When sp
39、ecified, IETMDBs which are to be delivered to the Government under this specification shall be structured and tagged in accordance with the DTDs and the tag set descriptions referenced in Appendix A (see 6.2). b. Database structuring and data element naming requirements. Unless otherwise specified,
40、a deliverable instance created under this specification shall be structured in accordance with the hierarchical relationships defined in the CDM DTDs referenced in Appendix A, and created and named using the tag set descriptions Provided by IHSNot for ResaleNo reproduction or networking permitted wi
41、thout license from IHS-,-,-MIL-DTL-87269C 5 contained in the referenced DTD. When a tagged instance is not specified for delivery, the contractor shall maintain the ability to map the internal element names to the specified content specific DTD names. 3.3 Format free technical information. The IETMD
42、B shall consist of an assemblage of data elements, including a listing of the specific attributes possessed by the data elements; and a list of explicit relationships providing logical links among the data elements. The relationships incorporated into the data base, by the IETMDB author, shall provi
43、de the basis of the technical structure of the IETMs and other logistic support TI which will be extracted from it. The IETMDB shall not contain format directions in the sense of arrangement of text and graphics on a display screen for presentation to the end user. The IETMDB itself shall require a
44、“format“ (data base structure) but this specification does not impose structural requirements on the actual Data Base Management System (DBMS) methodology to be employed (i.e., the data base may be either relational or object oriented). The exterior view of the data base to be used for updating, add
45、ing cross references, producing tagged output files, etc. shall conform to requirements of this specification. 3.3.1 Data portability. Formatting requirements shall be eliminated from the IETMDB to reduce the overall magnitude of data base and data interchange standardization effort. This shall also
46、 permit the use of a less complex DBMS by the contractor which is, in turn, less expensive and easier to modify. The “format-free“ nature of the IETMDB shall provide the Government the capability to: a. Acquire or access the data in a variety of ways (IETMs, other types of logistics reports, trainin
47、g TI, etc.). b. Subsequently format and style the data in a variety of ways for electronic display options. 3.3.2 Integration support. IETMDBs shall provide direct, on-line data access to a variety of users and to a number of automated logistic support and management information systems throughout t
48、he services. Establishment of standard identifiers, data entity relationships, and multiple path access routes to individual data elements shall be part of the IETMDB design and construction. 3.3.3 Data maintainability. The IETMDB shall be constructed with provisions that allow incorporation of any
49、change to automatically update all aspects of the data base affected by that change. This data-maintainability requirement shall involve the following two kinds of changes to the IETMDB: a. Additions to, eliminations of, or changes to individual data elements and attributes. b. Changes to relationships including establishment of new relationships or elimination of old relationships. 3.3.4 Additional content speci
