MIL-DTL-87269D
2.4 Order of precedence. In the event of a conlict between the text of this speciication and the references
cited herein, the text of this document takes precedence. Nothing in this document, however, supersedes
applicable laws and regulations unless a speciic exemption has been obtained.
REQUIREMENTS
3
3.1 General requirements. An IETMDB developed in accordance with this speciication shall conform to the
Content Data Model (CDM) speciied in this document (reference Appendix A.1.1). 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. The irst is the "Generic Layer". It deines 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 data 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 identiied transforms to
IETM functional IETM data structures found in Part 2 of the interchange layer. The inal layer is called the
"Content Speciic Layer" (CSL) and it contains the deining elements for weapon system speciic TI.
3.1.1 The "Generic Layer. The "Generic Layer" shall deine 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 generic layer deines the templates, linking elements, primitive elements, and context iltering elements
which are used to create content speciic DTDs. Templates deine rules which must be followed in the
creation of content speciic DTDs and document instances. The templates provide the structure for creating
composite nodes, context dependent iltering, user interaction and branching. The templates provide basic sets
of rules to which elements must adhere. Also included in the generic layer are coniguration management
version control and incremental update entities and elements that are used 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
lagging of updated content. A basic security classiication entity is also provided to allow consistent
identiication of classiied information within the IETM database. See DODM-5200.01 and DOD 5220.22-M
for information about the Department of Defense and the National Industrial Security Program.
3.1.2 The Interchange Layer. 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.
a. Part 1 is a holding area for harmonized standalone ETM DTD fragments that constitute
contained subsets of, or have identiied transforms to the interactive IETM data structures found
in Part 2 of the interchange layer.
b. Part 2 is a holding area for both harmonized and IETM-speciic DTD fragments that employ the
Generic Layer architectural forms to implement interactive technical manual traversal.
3.1.3 The Interchange Layer Part 1. The Interchange Layer Part 1 contains the harmonized ETM DTD
fragments which deine the common 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" functionality. 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 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 ETM data model. The above warning noted, ETM DTD data model developers are free to use all
or part of 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 harmony with the IETM database model.
3
For Parts Inquires call Parts Hangar, Inc (727) 493-0744
© Copyright 2015 Integrated Publishing, Inc.
A Service Disabled Veteran Owned Small Business