MIL-HDBK-511 Base Document:2000

FOREWORD
1.0 SCOPE
    1.1 Scope
    1.2 Application
    1.3 Background
          1.3.1 Tri-service approach to solving the
                  problem
          1.3.2 Objective and primary goal for the
                  architecture
2.0 APPLICABLE DOCUMENTS
    2.1 General
    2.2 Government documents
          2.2.1 Specifications, Standards, and
                  Handbooks
    2.3 Non-Government publications
    2.4 Order of precedence
3.0 DEFINITIONS
    3.1 Acronyms used in this handbook
    3.2 Definitions of selected terms
4.0 GENERAL GUIDANCE
    4.1 Overview of the joint IETM architecture
          4.1.1 Overall joint IETM architecture concept
          4.1.2 Basic architecture independent of
                  operating systems
          4.1.3 Developing a solution for IETM
                  interoperability
    4.2 Characteristics of the architecture which should
          be preserved in future JIA implementations
          4.2.1 Characteristics of the JIA for the user
          4.2.2 Characteristics of the JIA to be
                  maintained by the IETM developer
          4.2.3 Characteristics of the JIA for the
                  DoD IETM distribution infrastructure
    4.3 Summary of recommendations for implementation of
          the joint IETM architecture
          4.3.1 Common browser
          4.3.2 Object encapsulation and component
                  interface
          4.3.3 Electronic addressing and library
                  functions
          4.3.4 Intranet server and database server
                  interface
    4.4 Communications security and information
          assurance recommendations
    4.5 Permitting IETM use in a stand-alone environment
          4.5.1 Occasionally-connected user devices
          4.5.2 Dual-mode IETMs
5.0 BROWSER COMPONENTS
    5.1 Overview
    5.2 Classification
    5.3 Salient characteristics
          5.3.1 Thin client/server model
          5.3.2 Commercially defined object model
          5.3.3 Commonly used internet transport and
                  addressing protocols
          5.3.4 Frames
          5.3.5 Extensible components
          5.3.6 User interface
          5.3.7 Offline browsing
          5.3.8 HTML support
          5.3.9 Security
          5.3.10 Java
          5.3.11 Supported data types
          5.3.12 Multimedia
    5.4 Implementing advanced features
          5.4.1 eXtensible markup language (XML)
          5.4.2 Java
    5.5 Regulatory guidance
6.0 OBJECT ENCAPSULATION GUIDANCE
    6.1 Core object encapsulation
    6.2 Object encapsulation for various JIA architecture
          types
          6.2.1 Properties of client-based architecture
                  types
          6.2.2 Properties of server-based architecture
                  types
          6.2.3 General advisory for the development of
                  the differing architecture types
7.0 IETM ADDRESSING AND REGISTRY SOFTWARE
    7.1 General
          7.1.1 Background
          7.1.2 Recommended operational capability
          7.1.3 Operational environments
          7.1.4 Security environment
          7.1.5 Life cycle support
    7.2 Salient characteristics of external entity
          addresses
          7.2.1 External entity address description
          7.2.2 External entity address features/
                  benefits
          7.2.3 External entity address specifications
          7.2.4 Minimum criteria for external addressing
                  of entities and catalog registry
          7.2.5 Virtual uniform resource locator
          7.2.6 Other vURL attributes
    7.3 Initial guidance for establishing and using
          vURLs
    7.4 IETM object metadata
    7.5 Metadata
    7.6 Search engine
    7.7 IETM component registry description
          7.7.1 Background
          7.7.2 Recommended operational capability
          7.7.3 Life cycle support
    7.8 IETM object registry features/benefits
    7.9 IETM object registry specifications
    7.10 URLs and file pathname locators for legacy
          applications
    7.11 Service points of contact for vURL registration
8.0 WEB SERVER/CLIENT/STAND-ALONE IMPLEMENTATION GUIDANCE
    8.1 Overview
          8.1.1 The joint IETM architecture
          8.1.2 Connectivity of IETMs
          8.1.3 Off-the-shelf web servers
          8.1.4 Legacy IETM systems
    8.2 Networked client/server IETM applications
          8.2.1 Web server support and implementation
                  8.2.1.1 The networked approach
                  8.2.1.2 Use of customized server
                           applications and/or extensions
                  8.2.1.3 Networked client/server
                           configuration features
          8.2.2 Database-driven IETM applications
          8.2.3 Application development considerations
                  8.2.3.1 Servers and server-side
                           applications
                  8.2.3.2 Installation or multiple web
                           servers or multiple database
                           servers
    8.3 Occasionally connected IETM applications
          8.3.1 Web server support and implementation
          8.3.2 Addressing in the occasionally connected
                  mode
          8.3.3 Occasionally connected mode features
          8.3.4 Database-driven IETM applications in
                  the occasionally connected mode
                  8.3.4.1 Linking and addressing
                  8.3.4.2 Multiple database-driven IETMs
          8.3.5 Application development considerations
                  8.3.5.1 Custom server-side applications,
                           extensions, or databases
                  8.3.5.2 Automated replication of databases
    8.4 Stand-alone IETM applications
          8.4.1 Web server support and implementation
                  8.4.1.1 Web servers and stand-alone
                           configurations
                  8.4.1.2 Stand-alone configuration features
          8.4.2 Database-driven IETM applications in the
                  stand-alone mode
          8.4.3 Application development considerations
                  8.4.3.1 Linking and addressing
                  8.4.3.2 Multiple database-driven IETMs
9.0 MAINTAINING A COMMON LOOK AND FEEL AMONG DIFFERING IETMs
    9.1 Joint DoD/industry user-interaction guidelines
    9.2 Preliminary user-interaction guidelines for DoD
          IETMs
          9.2.1 Display format (text/font, graphics,
                  table,lists, objet embedding)
          9.2.2 Brose capability
          9.2.3 Link behaviour/navigation
          9.2.4 Control bars
          9.2.5 Icon standardization
          9.2.6 Selectable elements (hot spots)
          9.2.7 Warnings, cautions, notes
          9.2.8 Search & lookup
          9.2.9 Session control (suspend, resume,
                  nested sessions)
          9.2.10 Context filtering
          9.2.11 Screen resolution and color guidelines
          9.2.12 Information access (indices, electronic
                  TOCs, etc)
          9.2.13 Dialogs
          9.2.14 Sound
          9.2.15 Voice input/output (I/O)
          9.2.16 Graphics
          9.2.17 Hardware user interface (e.g. point and
                  click, voice, selection keys, A/N keyboard
                  touch pad, etc.)
          9.2.18 Performance (response time by context)
          9.2.19 Printer output
          9.2.20 User annotations (e.g. comments, user
                  notes, redlines, bookmarks)
          9.2.21 Feedback to originator (e.g. TMDRs,
                  form 2028, AFTO 22)
          9.2.22 Administrative information (e.g.
                  effectivity, authorization, distribution,
                  validation/verification)
          9.2.23 Interface to external references and
                  systems
          9.2.24 Rapid action chagnes and critical safety
                  interim messages
          9.2.25 Major data types (e.g. troubleshooting,
                  procedural, parts, descriptive)
10.0 NOTES
    10.1 Intended use
    10.2 Suject term (keyword) listing
FIGURES 1 - 10

Outlines issues associated with achieving IETM interoperability through the use of a common user interface, i.e. a browser.