Ni Stir 5108

(Supersedes NISTIR 4567)
Raster Graphics:
A Tutorial and
Implementation Guide
Frankie E. Spielman
Louis H. Sharpe, II
U.S. DEPARTMENT OF COMMERCE

Technology Administration
National Institute of Standards
and Technology
Computer Systems Laboratory
Gaithersburg, MD 20899
QC
100
• U56 NIST
#5108
1993
(Supersedes NISTIR 4567)
Raster Graphics:
A Tutorial and
Implementation Guide
Frankie E. Spielman
Louis H. Sharpe, II

Technology Administration
National Institute of Standards
and Technology
Computer Systems Laboratory
Gaithersburg, MD 20899
January 1993

Barbara Hackman Franklin, Secretary
TECHNOLOGY ADMINISTRATION
Robert M. White, Under Secretary for Technology
NATIONAL INSTITUTE OF STANDARDS

AND TECHNOLOGY
John W. Lyons, Director
.
- '
..
,;
^^''^;S' :% 'j!
v'- v'
/7'' •''../ A^vi' .ig;'-^^,-
'
" '“"*'
-,
‘''='
;•.. \-'''--
'
• :
-1
J \7A^rif^y“''f7£y
'
I .. 1 -
'.VI i .
Preface
This report examines the technical issues facing an implementor of

the raster data interchange format defined in the Open Document
Architecture (ODA) Raster Document Application Profile (DAP) . The
ODA Raster DAP is also included as an appendix to military
specification MIL-R-28002B . Information previously scattered
throughout several standards is incorporated into this report for
ease of reference. The ODA Raster DAP is analyzed with regard to
both notation and intent.
The motivation behind the development of the raster graphics file

formats for large documents which are detailed in the ODA Raster
DAP originated in a meeting between the Department of Defense (DoD)
and industry experts in 1987. The Computer-aided Acquisition and
Logistic Support (CALS) Office of DoD asked the large document
raster industry to provide suggestions for a standard interchange
file format and raster encoding scheme. The result was the
formation of an ad-hoc industry group known as the Tiling Task
Group (TTG) which quickly completed work on a draft standard based
on Consultative Committee on International Telegraphy and Telephony
(CCITT) recommendations.
CCITT had been collaborating with the International Organization

for Standardization (ISO) and was developing a technology based
upon the concept of a compound document which was to replace the
current facsimile environment. International Standard (IS) 8613,
which defines the Open Document Architecture (ODA) was the result.
,
It fills two important needs: (1) storing complex documents

containing graphics and textual information in complex word
processors, and (2) allowing facsimile technology to produce true
compound documents which are more than just hard copy.
Using the TTG draft standard, the TTG defined its requirements in
a DAP and wrote a proposed addendum to IS 8613, Part 7, in order to
insert the minimal mechanisms needed to support tiling. The DAP
was further developed through the efforts of the Open Systems
Environment Implementors' Workshop (OIW) which named it the "ODA
Raster DAP." Requirements were recently added to the ODA Raster
DAP to support requirements defined by the Association for
Information and Image Management (AIIM) and to make the ODA Raster
DAP more compatible with other ODA DAPs that are being developed.
This document supersedes NISTIR 4567, Tiled Raster Graphics and

MIL-R-28002A: A Tutorial and Implementation Guide.
Ill
Acknowledgments
Many people contributed to the creation of this report. All the

members of the Tiling Task Group originated and reviewed many of
the ideas in this document and anticipated the problems
implementors might have. Marcel Rivard, Christian Kunz Bancroft
,
Scott, Peter Sih, Rick Pond, and members of the ODA Special
Interest Group brought to light and analyzed some difficult areas
of ODA or ASN.l interpretation. Nick Mitschkowetz created the
tiled test image which is used in the examples. Joe Farrington
helped analyze the original examples with the use of the NIST Free
Value tool and developed procedures for using the tool. Annette
Shuford and Les Potter made particularly close readings of the
drafts of this report. Joe Garner, Jack Jeffers, Phil Battey, Bob
Moyer, and Jim Dalgety contributed to the original version of this
document, NISTIR 4567.
The efforts of many other people too numerous to mention are

gratefully acknowledged.
IV
Table of Contents
Preface iii
Acknowledgments iv
Table of Contents v
1 Introduction 1
2 Pertinent Standards 2
2.1 MIL-STD-1840 2
2.2 MIL-R-28002B 2
Contracting Options 2
Type I and Type II Data 3
2 3
. ODA Raster DAP 3
2.4 ANSI/AIIM MS-53 4
3 Benefits of ODA 5
3 1
. Compound Documents 5
3.2 Relationship to Facsimile 5
3.3 Using ODA 6
4 Overview of ODA 7
4.1 ODA's Relation to OSI 7
4.2 ODA's Base Standard: IS 8613 7
4 3
. ODA Encoding 8
4.4 Document Application Profiles (DAPs) 9
5 Involved Organizations 10
5.1 Government Initiatives 10
5.2 U.S. Initiatives 10
5.3 International Initiatives 10
6 File Structure 12
6.1 DoD Raster Header Information 12
6.2 ODA Structure 12
Document Profile 12
Presentation Styles 12
Document Layout Root 12
Composite Page 12
Frame 12
Block 13
Content Portion 13
7 Views of Raster Data 15
8 ODA Constituents and Attributes 20

8.1 Content Portion Description 20
V
8.1.1 Content Portion Attributes 20
8.1.2 Content Information 22
8.1.3 Alternative Representation 23
8.2 Presentation of the Image 23
8.2.1 Presentation Attributes 24
8.2.2 Presentation Style ..... 25
8.3 Document Layout Structure 26
8.3.1 Document Layout Root 27
8.3.2 Composite Page 27
8.3.3 Image Frame 28
8.3.4 Specific Block 28
8.3.5 Relationship Attributes and Layout
Objects 28
8.3.6 Specific Layout Attributes 31
8.4 Document Profile 32
8.4.1 General Attributes 33
8.4.2 Document Characteristics 33
8.4.2. 1 Raster Graphics Content Defaults . . 35
8. 4. 2. 2 Non-basic Document Characteristics . 35
8.4.3 Document Reference Attribute 36
8.4.4 Summary 36
8.5 Relationship of Objects 37
9 Technical Specification in the DAP 40

9.1 Genealogy 40
9.2 Simplifications 40
9.3 DAP Narrowed by MIL-R-28002B 40
9.4 Proforma and Notation 41
9.5 Elements of the DAP 42
9.6 Format of DAP Technical Specification Section ... 42
9.7 DAP Technical Specification 42
9.7.1 Content Portion Constraints 43
9.7.2 Presentation Style Constraints 44
9.7.3 Layout Constituent Constraints 45
9.7.4 Document Profile Constraints 47
10 ASN.l Coding Concepts 49

10.1 ASN.l Notation 49
10.2 Sample of ASN.l Definitions 49
10.3 The Basic Encoding Rules 53
10.4 Transfer Values 56
11 Technical Concepts 64
11.1 Raster Graphics Basics 64
11.2 Encoders and Decoders 67
11.3 Converters Versus Native Systems 68
11.4 Bit Order 68
11.5 Padding/Byte Boundaries 68
11.6 Partial tiles 69
11.7 Tile Ordering 70
11.8 Orientation 71
11.9 Rotation to Proper Viewing Orientation 74
VI
1
11.10 Uncompressed Bit Sense 74

11.11 Database Issues 74
11.12 Definite Versus Indefinite Length 75
11.13 Basic Versus Non-basic Versus Default Values . 75
11.14 Null Tiles 76
11.15 Presentation Styles 76
12 Tools 78
12.1 ODA Toolkit 78
12.2 The ISO Development Environment (ISODE) 78
12.3 Free Value tool, ASN.l Compilers 79
13 Glossary 80
14 References 83
Appendix A ASN.l Definitions 85
Appendix B Test Chart 93
Appendix C AIIM Document: With Clipping and Number of

Lines 95
Appendix D AIIM Document: Without Clipping and Number of

Lines 102
Appendix E CALS: Tiled Example Minimum Parameters .... 108
Appendix F CALS: Tiled Example All Parameters 115
VI
' . , '
*
;\.-«k;suo'^ vx,.i.jl!* .
5 :*
>':V' ’i- x:^. 'iy; 'iV',
3^ „ cr i t . >:*
.
.
't., •'-;'• '
'
» A r;x . . . iH
--
-
'
•
'
\ v’V>-: T ':^ .
*,'>. 'i<1'^v«T.o-:s'^ ,. .t.-tl ,
’'4
'
^ .
. .
- "
... I iWO i . !>X V .
;V, .
.
-r .. .-, .î;iv,.f*. a;..- ^{ 1^1
'
... t- n.. •'7 <‘i''
„
• .', ^ . O.;
• '
'
.« ' ’
^
.
.
'
. :.!.fC.'^-il'.»iwl!3<h , JSJJb':
' '.J ^
.i
- ‘i - ... ' H .xl.tiwT«aq£|A
- ’ * -
lu*
'
' '
^ ^
'---'"
* - --v. .,n'> - . jji- ... y<>-.btaiini‘^4.%
'.
'
^ .,..., .:^b
.. w. * ’
.' -
^(xXJi, ’
* • ®i' 5 T U3i - •% t.'
'
'
'
-r * '4 ‘r^
. _ ,
/^r. ., Â:iiv.V t ,.i:?.i'5a ! . rI)i7aq4Al

k-.
., *
- ‘i-;'’^' t Ta; 1 fXbiwquyt ''
-
’.^'j
'
i^
‘
^
-
< . * ;
•‘
'"
.’i
' ,
; i .' ’i ' .
- T
".
*
yJX
- ? V
•i* !6
X.,'
•"^0. Ir
-
'iM.
(S'
^*-
?*. . 6 'V-v. •
1 Introduction
The purpose of this tutorial is to give informal guidance and
suggestions to those undertaking implementations of the Open
Document Architecture (ODA) Raster Document Application Profile
(DAP) The intended audience is therefore system architects and
.
programmers
First, this tutorial provides an overview of the pertinent

standards (section 2 a discussion on the benefits of ODA (section
) ,
3) and an overview of ODA (section 4)

,
Following the introductory
.
sections is a discussion of the organizations involved with ODA and

raster graphics (section 5)
The tutorial examines the actual sequence of data elements found in

a raster graphics file (section 6) and discusses various views of
raster data (section 7) This then leads into a detailed
.
description of the ODA structure and its elements (section 8) and

the technical specifications within the ODA Raster DAP (section 9).
It then explains the coding concepts used for the ODA interchange
format. These are based upon the abstract syntax notation and
basic encoding rules (section 10)
In the latter portion of this document, the details of several

technical concepts are explained (section 11) A brief tutorial on
.
the basics of raster graphics is presented at the beginning of

section 11. Following section 11, this tutorial briefly discusses
some tools that may be used by implementors (section 12) and
provides a glossary (section 13) and a list of references (section
14) .
Appendix A provides a complete list of the abstract syntax notation

definitions representing an implementation of the ODA Raster DAP.
Appendix B contains a test chart image used in building examples
illustrated in the remaining appendices (C-F) . Information
contained in all of these appendices as well as actual interchange
files may be obtained from NIST (see Appendix A)
This document is intended to be an aid to an implementor of the ODA

Raster DAP and the requisite standards referenced in it. The
guidance provided in this tutorial is for information only. In
cases of technical errors or conflicts with the referenced
standards, the standards will prevail.
1
2 Pertinent Standards
There are several documents which serve as a basis for this
tutorial. First of all, there are two military documents. Military
Standard MIL-STD-1840 and Military Specification MIL-R-28002B.
Secondly, there is the ODA Raster DAP developed by the Open Systems
Environment Implementors' Workshop and a proposed ANSI/AIIM MS-53
document being developed by the Association for Information and
Image Management (AIIM) . In turn, these documents reference other
pertinent International Organization for Standardization (ISO) and
Federal Information Processing Standards (FIPS) standards.
2.1 MIL-STD-1840
MIL-STD-1840, Military Standard. Automated Interchange of Technical
Information [20], standardizes the format and structure of digital
technical data files for the purpose of interchange between
organizations or systems. For raster files, it describes a file
header to be placed ahead of any raster data specified by
MIL-R-28002B .One of the motivations behind the creation of MIL-
STD-1840 was the need to capture the Hollerith information from
aperture cards and deliver it along with the scanned raster data on
magnetic tape or other media.
2.2 MIL-R-28002B
MIL-R-28002B, Military Specification, Requirements for Raster
Graphics Representation in Binary Format [19], defines the
structure and encoding of raster data files to be delivered to the
government. It was created with the storage and interchange of
scanned engineering drawings in mind, but applies to other
documents as well, such as technical manuals and illustrations in
raster form. MIL-R-28002B can also serve as a means for standard
interchange between private contractors.
MIL-R-28002B restricts certain features of the ODA Raster DAP

either because generality was desired in the DAP or because the
mechanisms for these specific kinds of limitations are not
available within ODA (see ODA Raster DAP, paragraph 2.3).
Contracting Options
There are a variety of parameters that are free to vary while
still remaining within the bounds of MIL-R-28002B . These
items are separated into two classes:
1. Those that must be specified by the contracting officer

in order to avoid ambiguity or incorrect implementations, and
2
Pertinent Standards
2. Those that a contracting officer may wish to specify,

but which, in the absence of compelling reasons to do so, are
better left to the implementor's judgement.
Some issues within MIL-R-28002B requiring additional
clarification are discussed in the Technical Concepts section
of this tutorial.
Type I and Type II Data
MIL-R-28002B discusses two different possible representations

of raster data: Type I and Type II.
Type I data is simply CCITT T.6 encoded data for an entire

image representation enclosed within MIL-STD-1840 header
information. The CCITT T.6 encoding of raster data is defined
in FIPS PUB 150, Telecommunications: Facsimile Coding Schemes
and Coding Control Functions for Group 4 Facsimile Apparatus
[6] (CCITT Recommendation T.6 [4]). Type I data has no
support for tiling, but has the virtue of simplicity.
Type II data is a MIL-STD-1840 header wrapped around an

ODA-style document as specified in the ODA Raster DAP,
Appendix A to MIL-R-28002B . The ODA document may include
tiled raster data or may include a single compressed block of
raster data as in Type I, but with all ODA parameters and data
structuring included. An article published in Inform [24]
describes the use of a tiling scheme for large images.
2 . 3 ODA Raster DAP
ODA DAPs describe a restricted subset of the wide range of objects

available under the ODA base standard, IS 8613, Information
Processing - Text and office systems - Office Document Architecture
(ODA) and Interchange Format As such, DAPs relieve implementors
.
of having to support features not of use to their application. The

ODA Raster DAP identifies the requirements suited for raster
graphics applications.
The ODA Raster DAP represents the state of work within the Open
Systems Environment Implementors' Workshop (see Involved
Organizations, section 5) as of the December 1992 workshop. It is
being published as Part 23 of the NIST Special Publication 500-206,
Stable Implementation Agreements for Open Systems Interconnection
Protocols [22]. It is anticipated that the ODA Raster DAP will be
proposed as a Federal Information Processing Standard (FIPS) In .
addition, a group of international delegates have agreed to a plan

for rapid harmonization of the ODA Raster DAP with the goal of
3
Pertinent Standards
obtaining an approved International Standard Profile (ISP) by

January 1994.
2.4 ANSI/AIIM MS-53

AIIM is also developing a related document, ANSI/AIIM MS-53
(Proposed), Bi-Level Image File Format [1]. It specifies a file
format for the exchange of bi-level electronic images and is based
upon the ODA Raster DAP. Using a series of tables from the AIIM
document, the intent is that the user constructs an ODA data stream
without understanding the details of ODA and its associated
interchange format. It implements only a subset of the ODA Raster
DAP. AIIM plans to publish this document in April 1993.
4
3 Benefits of ODA
3 . 1 Compound Documents
Compound documents are those electronic documents consisting of

multiple content types, e.g., text, raster graphics, vector
graphics, voice annotation, etc. With the emergence of compound
documents, raster will become more useful and widespread.
Word processor vendors are developing ODA export and import

converters to allow documents received over data networks to be
refined, modified, and re-used. Within the OIW, there is an ODA
Interoperability subgroup scheduling and registering ODA
interoperability tests.
Since the ODA Raster DAP is similar to other DAPs, the possibility
exists that common platforms and raster editors will be used in the
future for handling both large and small documents.
3.2 Relationship to Facsimile

CCITT has advanced a recommendation for a very simple ODA document
application profile to support the needs of low-cost Group 4
facsimile hardware. This is known as CCITT Recommendation T.503,
A document application profile for the interchange of group 4
facsimile documents [ 3 ]
Since the Group 4 facsimile world is adopting ODA, using ODA for
the tiled representation of large document images offers certain
advantages. It could be expected that the ODA orientation of the
new Group 4 facsimile market will make the choice of an ODA
approach in MIL-R-28002B beneficial to the smaller market for
large-document systems .
Provisions exist in the international Profile Alignment Group for

ODA (PAGODA) DAPs (see Involved Organizations, section 5) for the
packaging of ODA documents as X.400 electronic mail messages, and
also for the exchange of ODA documents using the File Transfer,
Access, and Management (FTAM) file transfer scheme for high speed
networks. ODA is designed with interchange in mind.
ODA through ISO 8613-7 allows both T.4 encoding (commonly

^
known as "CCITT Group 3") and T.6 encoding (often called "CCITT
Group 4") In this discussion of machines for Group 4 facsimile,
it should be made clear that current Group 3 machines do not use
ODA, although the exchange of "CCITT Group 3" data via ODA is
possible in principle.
5
Benefits of ODA
3.3 Using ODA
The resistance some people have expressed after their first

encounter with ODA and ASN.l [8] may come from the overwhelming
avalanche of terms the standards appear to have generated.
However, the terms more directly result from the complexity of
automating the document and image environment than it is with the
standards. For example, just take a look at the complexity of some
of the word processors that are commonly used today. Luckily, it
is only necessary to learn ODA at its most general level to
complete an implementation of the ODA Raster DAP.
There have been some recent developments that will expand the
knowledge and use of ODA and ASN.l. First of all, this tutorial is
intended to help educate users and reduce the fear of ODA and
ASN.l. Second, the availability of an ODA Toolkit will help
implementors who are implementing ODA. Third, the development of
an AIIM document is intended to help ease implementors into ODA
compliant image interchange without requiring a knowledge of ODA.
Fourth, ASN.l is becoming more widely used in other standards and
more ASN.l tools are becoming available.
6
.
4 Overview of ODA
4.1 ODA's Relation to OSI
A new era of connectivity is beginning as the Open Systems

Interconnection (OSI) standards are becoming popular. ODA is
clearly in the mainstream of OSI development and uses the
mechanisms, formalisms, and abstract syntaxes that other OSI
protocols use.
Version 2 of GOSIP [21] contains information required to transport

any ODA document as a body part of a message or content of a file.
Future versions of GOSIP will reference applicable DAPs which NIST
plans to issue for Federal agency use.
4.2 ODA's Base Standard: IS 8613
Each realm of OSI standards development has at its nucleus the base
standards that define the building blocks available for creating
more complex protocols or services. IS 8613, Information
Processing - Text and office systems - Open Document Architecture
(PDA) and Interchange Format [9-15]^ is the fundamental standard
for ODA. A general overview of ODA may be found in ODA and
Document Interchange [5] and a more comprehensive description of
ODA is contained in Document Architecture in Open Systems The ODA
,
Standard [2]. Other standards also affect ODA work in some degree,
but we will not discuss them in this document.
IS 8613 has several parts, each of which addresses some portion of

ODA. The pertinent parts are discussed below.
Part 1; Introduction and General Principles [9] gives a great

many definitions of basic ideas. It describes the motivations
and unifying design principles of ODA.
Part 2 Document Structures [10] defines the basic elements of

;
a document architecture and the conceptual models necessary to

understand the layout and imaging processes. It also defines
the different classes of allowed document architectures.
Part 4; Document Profile [11] describes the purpose and

attributes of a document profile.
Part 5; Office Document Interchange Format (PDIF) [12] shows

how to apply the encoding rules to ODA documents to prepare
them for interchange as ODIF data streams (files)
^ The ISO 8613 ODA Standard is scheduled to be republished in

March 1993 incorporating several addenda, including some not
mentioned. It will be published as a joint CCITT and ISO document.
7
Overview of ODA
Part 7 Raster graphics content architectures [13] is the

;
portion IS 8613 that defines raster graphics content

of
(data). All of the relevant attributes of raster data that
need to be properly spelled out for successful interchange are
identified. Allowed (permissible) values for those attributes
and their defaults are all defined.
Part 7 Tiling Addendum [14] contains the extensions to Part 7

necessary to implement tiling. Such attributes as tile size
and tile type (how a tile is encoded) are specified.
Part 7 Additional Bit Order Mapping Addendum [15]^ contains

the extensions to Part 7 necessary to encode CCITT T.4/T.6
data in the down bit order sequence.
4.3 ODA Encoding
The interchange format for an ODA document is a data structure

described or expressed in a notation which is independent of any
particular machine in which the structure might be represented.
For example, problems with the particular manner in which an
integer might be represented on two different machines can be
avoided. This notation is called an abstract syntax. In
recognition of the fact that many such syntaxes are possible, the
notation used in ODA and elsewhere in the Open Systems
Interconnection (OSI) family of protocols is called Abstract Syntax
Notation One (ASN.l).
ASN.l is defined in two standards: IS 8824, Information processing

systems - Open Systems Interconnection - Specification of Abstract
Syntax Notation One ASN.l)
f [16], and IS 8825, Information
processing systems - Open Systems Interconnection - Specification
of Basic Encoding Rules for Abstract Syntax Notation One (ASN.l)
[17]. ASN.l is further described in The Open Book, A Practical
Perspective on OSI [23].
The first document describes ASN.l syntax without defining the

encoding rules that actually permit a protocol or interchange
format to be put "on a wire" or in a file. The encoding of the
syntax is a separate issue entirely.
The addendum was approved by CCITT but was not approved by

^
ISO. The text supporting this addendum will appear in the joint
publication with a note added stating that it was not approved by
ISO. PAGODA has submitted a defect report which requests that ISO
reconsider its position and approve the addendum. Otherwise
implementors will refer to the CCITT version of the publication.
8
Overview of ODA
The encoding represents the elements of the syntax as actual

machine-readable symbols. These so-called Basic Encoding Rules are
defined in IS 8825. They are called basic because other encoding
rules are possible.
One other encoding called Office Document Language (ODL) is also

defined in IS 8613-5. It is based on the Standard Generalized
Markup Language (SGML) . ODL is not illustrated in this tutorial.
4.4 Document Application Profiles (DAPs)
DAPs are well-defined profiles, or subsets, of the ODA standard.

Each DAP is created by a user group to meets its own needs. DAPs
greatly limit the knowledge of ODA required for specific
applications. The ODA Raster DAP was initially created by the
Tiling Task Group and then further developed through the efforts of
the Open Systems Environment Implementors' Workshop. It has been
simplified to meet the needs of the large-document and technical
publications raster communities, particularly as they interact with
the CALS program. It also includes specifications necessary to
support AIIM's bi-level image file format.
9
5 Involved Organizations
All of the organizations listed below have had some hand in either
the format, the development, or the content of the hierarchy of
standards embodied in the ODA Raster DAP.
5.1 Government Initiatives

The Department of Defense Office for Computer-aided Acquisition and
Logistic Support (CALS) ,
the National Institute of Standards and
Technology (NIST) , and the industry-based Tiling Task Group (TTG)
are the primary developers of the technical content of the ODA
Raster DAP.
5.2 U.S. Initiatives
The Open Systems Environment Implementors' Workshop (OIW) is hosted

by NIST and the Institute of Electrical and Electronic Engineers
(IEEE) and meets quarterly. The ODA Special Interest Group (ODA
SIG) meets under its auspices and undertakes North American
development of ODA-related items, primarily DAPs. The ODA Raster
DAP was developed, voted on, and approved by this group. The
American National Standards Institute (ANSI) X3V1 committee is the
North American contributor to the development of IS 8613 within the
International Organization for Standardization (ISO)
5.3 International Initiatives
The international Profile Alignment Group for ODA (PAGODA) has

developed a common set of ODA International Standard Profiles
(ISPs) or internationally approved DAPs for world-wide use. These
groups include the European Workshop for Open Systems (EWOS) ,
the
Asia-Oceania Workshop (AOW) the
, Open Systems Environment
Implementors' Workshop (OIW) and CCITT.
,
PAGODA coordinated development of three related document processing

applications DAPs. These are known as FODll, FOD26, and FOD36.
Additionally, PAGODA has initiated action to develop image
application DAPs including the ODA Raster DAP. At the PAGODA
meeting of October 19-23, 1992, the delegations agreed to a plan
for rapid harmonization of the ODA Raster DAP specification with
the goal of obtaining an approved ISP by January 1994.
The Association for Information and Image Management (AIIM) is

coordinating the development of the ANSI/AIIM MS-53 document. It
was initiated within the U.S. and is now progressing as a work item
to its corresponding international body.
The ODA Consortium was established in April 1991 to promote the

electronic interchange of documents among different computer
10
.
Involved Organizations
systems throughout the world. It has developed an ODA Toolkit (see

Tools in section 12)
11
6 File Structure
This section discusses the actual sequence of items inside an

interchanged raster file.
The ordering of data elements within an ODA document is specified

in IS 8613 Part 5, section 5.2, where use of the class A data
stream is mandated for the ODA Raster DAP.
The entire sequence of data items transferred is illustrated below

in figure 1. Each of the ODA items is discussed in greater detail
in the section 8, ODA Constituents and Attributes.
6.1 DoD Raster Header Information
The DoD raster header information is required for interchange of

raster data within DoD. The fields of this header are clearly
spelled out in MIL-STD-1840 This header information is not
.
required to interchange an ODA document.

6 . 2 ODA Structure
Document Profile
The document profile is the first item in the representation of an
ODA document.
Presentation Styles
The presentation styles are optional, but if they do appear, they
must occur immediately following the document profile.
Document Layout Root

The dociiment layout root must occur next and serves as the root for
all pages of the document that follow the root.
Composite Page
There can be one or more composite pages. The term composite is
applied to these pages because they are layout objects containing
subordinate layout objects, a single frame in the case of the ODA
Raster DAP.
Frame
The frame is a rectangular area within the page and contains a
single block. For the ODA Raster DAP, the frame is coincident with
the page.
12
File Structure
Block
The block is a rectangular area within the frame. The raster image
is always associated with a block. Each block (in the tiled case)
may have the following optional entry among its sub-elements:
Tile Index
The optional tile index may be present only in tiled files.

The order of its elements matches the order of the tiles.
Content Portion
The content portion is the actual raster data and its associated
attributes for a single raster image. The raster data may be in
either the tiled or untiled format. If tiled, the data for tiles
occur within that content portion in an order that is primarily
along the pel (picture element) path direction and secondarily
along the line progression direction.
The pages, frames, and blocks may occur as many times as necessary
to represent all the raster images in the document. One image per
block, one block per frame, and one frame per page. All of the
associated content portion objects containing the actual image
information occur as a group following the last block. Figure 1
shows the file structure of a file. Only DoD files require the
MIL-STD-1840 header.
13
File Structure
MIL-STD-1840 Header DoD

Only
Document Profile ODA

Structure
Presentation Styles (optional)
Document Layout Root
Page Layout Object 1
Frame Layout Object 1
Block Layout Object 1
Repeat as necessary
Content Portion n
Figure 1 - File Structure
14
.
7 Views of Raster Data

There are different views of raster graphics data discussed in the
ensuing sections. These views are related to one another and not
everyone needs to understand the details of each view. This
section will provide a brief overview of each view and how they
relate to one another. See figure 2.
Figure 2 - Views of Raster Data
The views may be associated with how an implementor develops and

implements a system supporting the ODA Raster DAP. If an
implementor purchases an ODA system off the shelf which supports
all of ODA, it is conceivable that he would not have to look past
the section 8, ODA Constituents and Attributes.
Taking this one step further, an implementation of ODA may be set

up to process a specific DAP, i.e., the ODA Raster DAP. In this
case, a thorough analysis of the technical specifications in the
DAP, section 9, Technical Specifications of the DAP, may have to be
reviewed
If an implementor is implementing an ODA Raster DAP interchange

capability without the aid of an ODA system, the implementor will
likely have to take the development one step deeper and implement
15
.
views of Raster Data
it using ASN.l. See the ASN.l Coding Concepts, section 10, which
discusses the interchange format.
AIIM has taken this process one step further by describing a data
stream through the use of tables. This resulting data stream is
intended to be an ODA Raster DAP compliant data stream. Using the
AIIM tables will result in a limited subset of the ODA interchange
f ormat
The following paragraphs provide a general overview of each of

these views prior to diving into the details in later sections of
this document. To do this, these views and relationships are based
upon an elementary view of raster data. For example, when
interchanging raster data, it is generally understood that the
n\iniber of pels per line (line length) must be known and that the
number of lines is helpful although not required.
First of all, the number of pels per line must be known before a
system can decode the compressed raster data. Although not
required, sometimes it is helpful to know the number of lines to
determine memory space allocation, etc. These attributes are
grouped together within ODA into a set called raster graphics
coding attributes. Another piece of information that needs to be
known is how the data is encoded, e.g., CCITT T.6, CCITT T.4,
bitmap, tiled, etc. This characteristic is determined by the type
of coding attribute. Of course, the interchange would not be
complete without including the actual raster data, the content
information. All of this information is grouped together in ODA as
an object called content portion. One important attribute required
in ODA is the content identifier layout attribute. This attribute
is used to identify each of the content portion objects separately
from all of the other ODA objects that are present in the
interchange.
If we use these attributes, we could build an example of a raster

graphics structure like the following:
Content portion (raster graphics)

Content identifier layout
Type of coding
Coding attributes (raster graphics coding attributes)
number of lines
number of pels per line
Content information (the raster data)
With this basic knowledge in mind, the first view is to look at

requirements from a textual description viewpoint. This was begun
in the paragraphs above but the complete raster graphics
requirements are defined in section 6 of the ODA Raster DAP. These
16
requirements are also discussed as a tutorial later in this

document, see section 8, ODA Constituents and Attributes. Only a
few of the attributes are introduced at this time in order to
explain the general content and structure of this document.
The second view looks at the raster data from a syntactical or

notational standpoint. Here, the text from the first view is
defined in a notation that computers can understand. See figure 3.
The complete raster graphics technical specifications are defined
in section 7 of the ODA Raster DAP. If you have a "DAP Reader"
(DAP parser) that could read the DAP notation, then implementors
and conformance testers would require no further views to
understand the ODA Raster DAP. The DAP notation describes the data
to an ODA system which can then generate data in the proper
interchange format.
Raster-graphics-content-portion {
REQ Content-identifier-layout {ANY_VALUE},
PERM Type-of-coding { ASN.l {2 8 3 7 5} - tiled encoding -
1
ASN.l {2 8 3 7 6} - T.6 encoding - MSB -
}
PERM Coding-attributes {
REQ #raster-graphics-coding-attributes {
PERM #number-of-lines {>0}-
REQ #number-of-pels-per-line {>0}}}/
PERM Content-information {RASTER}
}
Figure 3 - Technical Specification
The third view looks at the raster data from an ODA interchange
standpoint using ASN.l Definitions as depicted in figure 4. The
complete set of ASN.l Definitions used in the ODA Raster DAP are
found in IS 8613-5, IS 8613-7, and the IS 8613-7 Tiling Addendum.
The ASN.l Definitions in figure 4 is a restricted subset of
definitions extracted from these standards documents. Tracing
through the ASN.l Definitions in figure 4 results in a hierarchical
data structure. If you follow the arrows which point to the
definition of the referenced name, you will end up with the same
structure as shown in figure 3.
The fourth view illustrates actual data instances of an image as

shown in figure 5. The type of coding indicates that the data is
'T.6 encoded - MSB', the number of pels per line is 2,550, and the
number of lines is 3,300 and these attributes are followed by
12,792 octets of T.6 encoded (MSB) data, content information. You
should note that column one illustrates the same basic structure as
17
illustrated in our original example of a raster graphics structure.

Column two illustrates the actual encoded file in a hexadecimal
representation using ASN.l Basic Encoding Rules. This second
column illustrates the use of tags, lengths, and values that are
needed to describe the interchange format for a specific raster
data image.
Text-Unit ::= SEQUENCE {

content-portion-attributes Content-Portion-Attributes OPTIONAL,
content-information Content-Information OPTIONAL
}
Content-Information ::= CHOICE {

one-octet-string OCTET STRING,
seq-octet-string SEQUENCE OF OCTET STRING }
Content-Portion-Attributes 7:= SEtT

content-identifier-layout Content-Portion-Identifier OPTIONAL,
type-of-coding Type-Of-Coding OPTIONAL,
coding-attributes CHOICE {
raster-gr-coding-attributes [2] IMPLICIT Raster-Gr-Coding-Attributes,
alternative-representation [3] IMPLICIT Alternative-Representation
} OPTIONAL }
Type-Of-Coding CHOICE {
other-coding [6] IMPLICIT OBJECT IDENTIFIER
“ or {2 8 3 7 5} 'tiled encoding'
“ or {2 8 3 7 6} 'T6 encoding - MSB'
}
Raster-Gr-Coding-Attributes* Ti^ SET {
number-of-pels-per-line [0] IMPLICIT INTEGER OPTIONAL,

number-of-lines [1] IMPLICIT INTEGER OPTIONAL,
}
Figure 4 - ASN.l Definitions
The remaining sections of this document describe each of these

views in more depth. Section 8 describes the ODA Constituents and
Attributes needed to support the characteristics in section 6 of
the ODA Raster DAP. Section 9 describes the Technical
Specifications in the DAP in a syntactical notation. Section 10,
ASN.l Coding Concepts, describes the data interchange requirements
using ASN.l and how to encode an interchange file based on example
data.
18
Specific Data Values Interchange Transfer Values
content-portion { a3 82 32 09 [3] constr <12825>

content-portion-attributes . 31 1b [UNIV 17] constr <27 >
{
content-identifier-layout "1 0 0 0 0", . 40 09 [APPL 0] <9>
.
31 20 30 20 30 20 30 20 30
type-of-coding other-coding { 2, 8, 3, 7, 6 },
. 86 04 [6] <4>
.
58 03 07 06
coding-attributes raster-gr-coding-attributes . a2 Ob [2] constr <8>
.
{
number-of-pels-per-line 2550, ... 80 02 [0] <2>
09 f6
number-of-lines 3300 } },
... 81 02 [1] <2>
Oc e4
content-information one-octet-string . 04 82 31 f8 [UNIV 4] < 1 2792 >
'...'H - '< <T.6 encoded - MSB data> >'H - 12792 octets of compressed
data (T.6 encoded - MSB)
}
Figure 5 - Interchange Data Values
19
8 ODA Constituents and Attributes
For the purpose of interchange, an ODA document is presented as a
collection of constituents or objects. Each constituent is a
segment or portion of the interchange which contains a set of
interrelated attributes. Each attribute describes a certain
characteristic of that specific constituent or segment of the
document. Constituents are often defined in an incremental way,
with references being made back to earlier definitions. No
constituent is used before it is defined.
The types of constituents used in the ODA Raster DAP are: document
profile, presentation style, docximent layout description, and
content portion description. This order is as specified in IS
8613-5, clause 5.2. The document layout description constituents
consists of four types of ODA Raster DAP objects: document layout
root, composite page, image frame, and specific block. For a
multiple page document, the layout and content portion constituents
repeat as shown in figure 1.
In the discussion below, the constituent, attribute, and attribute

set names are shown in bold face when each term is being introduced
or defined. The hyphens normally found in the names of items in
the DAP have been removed for readability. The order of the
discussion below has been chosen to help those with raster graphics
related background by starting with an area that they are probably
already familiar with. The sequence of the discussion is in the
order of: content portion description (the raster data),
presentation style (presentation characteristics) document layout
,
description (layout on the media) and document profile (global

,
file information) Note that this is not in the same order as the
.
sequence of objects to be found in the interchange file.
8.1 Content Portion Description
The content portion description is a constituent of the document

which describes how the raster graphics data is represented in the
file. The content portion description includes two parts: (1) the
coding attributes, content portion attributes, needed to specify
the properties of the content information; and (2) the actual
content information (raster image) For the ODA Raster DAP, each
.
content portion will be laid out on a single page and will consist
of only raster graphics content.
8.1.1 Content Portion Attributes
The content portion attributes is a set of attributes consisting of

content identifier layout, type of coding, and raster graphics
coding attributes.
20
.
ODA Constituents and Attributes
The content identifier layout is a relationship attribute. As

can be seen from figure 1 there may be multiple content portion
,
description objects within the data stream. It is the content

identifier layout attribute that uniquely identifies a specific
content portion description and associates that content portion
description with a unique document layout description (specific
block). It is a sequence of non-negative integers which will be
discussed later.
Type of coding is an attribute which specifies the coding used
to represent the content information. For the ODA Raster DAP,
the allowable values are as follows:
'T.6 encoding' indicates that the entire raster data (image)

is not tiled and is encoded in accordance with the CCITT T.6
algorithm using the up bit order sequence. See discussion on
bit order in section 11, Technical Concepts.
'T.4 one dimensional encoding' indicates that the raster data

is encoded according to the one-dimensional encoding scheme
defined in CCITT Recommendation T.4 using the up bit order
sequence.
'T.4 two dimensional encoding' indicates that the raster data

is encoded according to the two-dimensional encoding scheme
defined in CCITT Recommendation T.4 using the up bit order
sequence.
'Bitmap encoding' indicates that the entire raster data

(image) is not tiled and is in the uncompressed or bitmap
form.
'Tiled encoding' indicates that the raster data is tiled and

that each tile may then be represented in one of five
possible ways: 'T.6 encoding', 'T.6 encoding - MSB', 'bitmap
encoding', 'null background', or 'null foreground' (see Tile
types below)
'T.6 encoding - MSB' indicates that the entire raster data

(image) is not tiled and is in encoded in accordance with the
CCITT T.6 algorithm using the down bit order sequence.
'T.4 one dimensional encoding - MSB' indicates that the

raster data is encoded according to the one-dimensional
encoding scheme defined in CCITT Recommendation T.4 using the
down bit order sequence.
'T.4 two dimensional encoding - MSB' indicates that the

raster data is encoded according to the two-dimensional
21
,
encoding scheme defined in CCITT Recommendation T.4 using the

down bit order sequence.
NOTE; The only valid values for MIL-R-28002B are 'T.6

encoding - MSB', 'tiled encoding', and 'bitmap encoding'; the
others are only valid outside of MIL-R-28002B.
Raster graphics (gr) coding attributes is a set of attributes

which provide information required for encoding and decoding the
content information as well as other information that is
intrinsic to the content portion and required to layout and
image the content. All of the attributes in this set deal with
how to interpret the content data stream (content information)
not how the image is to be presented on the display media. The
attributes are defined as follows:
Number of pels per line specifies the number of pels in each
line within the content information. This attribute must
always be specified.
Number of lines specifies the number of lines of pels within

the content information.
Tiling offset applies only to tiled content information. It

specifies the location of the pel array within the tile space
by defining the offset of the first pel of the pel array from
the first pel position of the first tile. This is specified
by a coordinate pair, consisting of two non-negative
integers. Note that these integer values cannot be larger
than the dimensions of a tile.
Tile types applies only to tiled content information. It is

a sequence of integer values where each integer indicates the
type of coding for the respective tiles in the content
information. For the ODA Raster DAP ,the types of tiles
allowed are: null background, null foreground, T6 encoded, T6
encoded-MSB, and bitmap. If the tile types attribute is
used (it is optional) , there must be an integer value for
each tile. If it is not used, all tiles must be T.6 encoded.
For the ODA Raster DAP, the tiles are always square and are
512 by 512 pels in size.
8.1.2 Content Information
The content information is that part of the content portion

description which is composed of the raster data, that is, the
raster graphics content that is to be displayed.
22
The raster data is a pel array which is a two-dimensional array

used to represent a pictorial image. It consists of pels or
picture elements which make up the smallest graphic element that
can be individually addressed within a picture. The pels have a
defined order. The array consists of an ordered seguence of rows
of picture elements. Each row in the array contains the same
number of picture elements and consists of an ordered sequence of
pels that represents a line of the image.
In a tiled encoding of the content information, the pel array is

segmented into a two dimensional array of non-overlapping
rectangular regions called tiles. The content information of each
tile is coded independently of the content information of the other
tiles of the same pel array. See figure 14.
The content information or pel array is represented by one of the

following encoded schemes as discussed above: (1) T.6 encoding, (2)
T.4 one dimensional encoding, (3) T.4 two dimensional encoding, (4)
bitmap encoding, (5) tiled encoding, (6) T.6 encoding-MSB, (7) T.4
one dimensional encoding-MSB, or (8) T.4 two dimensional encoding-
MSB. It is important that the type of coding attribute discussed
earlier accurate identify which encoding scheme has been used for
the content information otherwise decoders will not be able to
properly decode the content information.
8.1.3 Alternative Representation
The alternative representation attribute may contain an ASCII

character string that may be displayed in lieu of the content
information when a receiver is not capable of decoding and/or
imaging the raster data.
8.2 Presentation of the Image
There is a set of optional ODA presentation attributes which guide

the format and appearance of the raster image on a display media.
See figure 14 and section 11 for a detailed discussion on the
relationship of these attributes.
There are four alternatives for specifying the presentation
attribute values. One alternative is to not specify any
presentation attributes at all and let them default to those values
specified in the base standard. That is, the document layout
description does not reference any presentation attributes, either
directly or indirectly through a presentation style.
A second alternative is to specify the appropriate attributes

directly in the applicable block layout object.
23
. .
A third alternative is to specify the set of attributes in a

separate presentation style object and then refer to that
presentation style from the applicable block layout object.
The fourth alternative is to use a combination of the two. That
is, a document layout description references one of the
presentation styles and then specifies its own specific attributes
that may override some of those attributes in the referenced
presentation style.
An additional discussion on the relationship of presentation
attributes, presentation styles, and other objects is in section
11, Technical Concepts. All of the presentation attributes and
general information about presentation styles are discussed in the
following paragraphs.
8.2.1 Presentation Attributes
Content architecture class is an attribute which specifies the

class of content contained in the content portion. It implicitly
identifies a set of presentation attributes, control functions, and
coding attributes which are applicable to that specific type of
content. For example, raster graphics content requires a different
set of attributes than does character content. For the ODA Raster
DAP, this attribute will always contain an object identifier of {2
8272} designating the contents as raster 'formatted processable
content architecture'
Pel path specifies the direction of progression of successive pels

along a line and is expressed as a direction relative to the
horizontal axis of the page coordinate system. Pel path is one of
two attributes used to reflect the proper viewing orientation of
the image
Line progression specifies the direction of progression of

successive lines and is expressed as a direction relative to the
pel path. Lines of pels are positioned such that the first pel to
be positioned on each line falls on an imaginary line which passes
through the initial point in the direction of line progression.
Line progression along with pel path are the two attributes used to
reflect the proper viewing orientation of the image. There are a
possibility of eight different orientations. See section 11,
Technical Concepts.
Clipping is used to determine the subregion of the entire pel

array, as described by the content portion, which is to be
considered by the content layout and imaging processes. It
consists of two coordinate pairs. The first pair specifies the
24
.
first pel that is part of the selected array. The second pair
specifies the last pel that is part of the selected array.
Pel spacing specifies the distance between two adjacent pels along
a line, in the direction of the pel path. Pel spacing is the
distance measured using the Basic Measurement Unit (BMU) There
.
are 1200 BMUs per inch. Pel spacing is expressed as a ratio. Thus
a pel spacing of 6/1 is a ratio of a distance of 6 BMUs to one pel
interval. Since 6 BMUs/pel * (1 inch / 1200 BMUs) = (1 inch / 200
pels) this corresponds to 200 pels per inch along the pel path
,
direction.
Spacing ratio is the ratio of line spacing to pel spacing. The

normal situation is for the spaces between the pels along a line
and between successive lines to be the same, i.e., a ratio of 1/1.
The default value is 1/1. In those situations where the spacing
between the pels in one direction is different from the spacing in
the other direction, the spacing ratio may be used. The spacing
ratio is synonymous with aspect ratio.
8.2.2 Presentation Style

The presentation style is an optional constituent of the document
which guides the format and appearance of the document content
(raster image) . If present, it must be referred to from a block
layout object. A style serves to group together sets of attributes
which could alternately be applied directly and individually during
the layout and imaging process.
A presentation style contains an attribute, style identifier, which

identifies the presentation style uniquely within the context of
the document. It is a sequence of two non-negative integers, the
first of which is always '5' to signify a presentation style
constituent. Since a document may contain more than one
presentation style, a second integer is used to uniquely identify
each presentation style within the interchange document. The value
selected for this second integer may be any non-negative value as
long as the integer sequence (integer pair) is unique for each
presentation style. All other constituents using a specific
presentation style must reference it using the integer sequence
corresponding to the style identifier for that presentation style.
In this way, a specific block layout object may refer to the
presentation style needed to lay out the corresponding raster
image
For example, a document may consist of six pages (containing six

frames and specific blocks) requiring two different presentation
styles. The first style would have an identifier of '5 0' and the
second a '5 1'. Specific blocks 1 and 5 could reference style '5
25
0' Whereas all of the other blocks 2 3, 4 and 6 might reference

, ,
style '51'. A block need not necessarily reference a presentation

style.
8.3 Dociiment Layout structure
To provide for a compound document, it must be capable of

containing raster graphics, geometric (vector) graphics, and
character content. ODA provides this capability through its
document layout structure as illustrated in figure 6.
Pages
Frames
Document
Blocks
Page Sets
Figure 6 - ODA Layout Structure
The document layout structure consists of a series of layout

objects. Each layout object has an associated set of attributes
which specifies how the document content is to be laid out and
presented to the viewer.
You will note from figure 6 that an ODA document structure may
consist of page sets with each consisting of multiple pages. Pages
are made up of any number of frames and frames are made up of any
number of blocks. The ODA Raster DAP, however, has a simpler
structure. See figure 7.
For the ODA Raster DAP, the specific layout structure is a simple
four-level hierarchy consisting of a document layout root.
26
composite basic page(s) image frame, and specific block objects.

,
See figures 7 and 8. The term "specific" is used to contrast with

generic layout structure, an ODA feature omitted for simplicity
from the ODA Raster DAP. Each of the layout object types has some
attributes in common with other layout object types and some
distinct attributes. The content information consisting of a
raster graphics image, representing an engineering drawing,
illustration, or other raster scanned image, can only be associated
with a specific block. This content may contain either untiled or
tiled raster graphics data.
Figure 7 - ODA Layout Structure (ODA Raster DAP)
8.3.1 Dociunent Layout Root
The document layout root is at the highest level of the hierarchy

in a document layout structure. Its basic purpose is to identify
the subordinate objects that exist at the second level of the
hierarchy. For the ODA Raster DAP these subordinates can only be
,
a sequence of one or more composite pages.
8.3.2 Composite Page
The composite page is a layout object that corresponds to the

rectangular area representing the page and is used for presenting
the raster image.
27
8.3.3
Image Frame
The image frame is a layout object that corresponds to the

rectangular area within a page, For the ODA Raster DAP, there can
be only one frame per page and the frame is coincident with the
page.
Figure 8 - Specific Layout Structure
8.3.4 Specific Block
The specific block is a layout object that corresponds to the

rectangular area within a frame. For the ODA Raster DAP, there can
be only one block per frame. The block area will typically be
synonymous with the area of the frame, however, the block area may
be smaller than the frame area. This later case can be the
situation when the clipping attribute is used. The dimensions and
position attributes discussed later in this section are also used
in this situation. The content portion may only be associated with
a specific block.
8.3.5 Relationship Attributes and Layout Objects
Figure 9 illustrates the layout structure and associated contents

for an example document consisting of three composite pages. This
illustration is used to describe several of the relationship
28
attributes that are discussed in the remainder of this section.

Relationship attributes are used to describe the relationship
between all of the objects contained in an interchange file.
Figure 9 - Illustration of Layout Structure
Every layout object must include an object type attribute which is

an integer specifying the type of object as being either the root,
page, frame, or block. The object type is then used to identify
the set of attributes that may be specified for that respective
object.
Because of the hierarchical nature of the layout structure, every

layout object must be identified with an attribute, object
identifier, which identifies the object uniguely within the context
of the document and within the layout hierarchy. An object
29
.
identifier consists of a sequence of integers. Each integer in the

sequence corresponds to a hierarchical level and identifies one
particular object instance at that level.
For the three page example in figure 9, the document layout root,
the first level of the hierarchy, is always identified with a '1'.
The object identifier for the second level of the hierarchy must
include two integers separated by a space. For this example, the
identifier on the first page contains a '1 O', the second page a '1
1', and the third page a '1 2'. The first integer in the sequence,
'1', always indicates the object belongs to the specific document
layout hierarchy. The second integer within the sequence uniquely
identifies the page within that second level of the layout
hierarchy, in other words, a 'O', '1', or '2' for pages 1, 2, or 3
respectively
This same logic then applies in assigning object identifiers to
frames and blocks. That is, the third integer is used to identify
the frame within a page and the fourth integer to identify the
block within a frame. Since there can be only a single frame and
block to a page, the third and fourth integers are always zero.
Using this scheme for the object identifier, every layout object in
the document structure can be uniquely identified. No two objects
will have the same identifier.
The four levels of hierarchy create additional encoding that does

not provide any material benefit for the ODA Raster DAP. However,
the four levels are necessary in order to be upwards compatible
with other DAPs.
The document layout root additionally contains a relationship

attribute, subordinates, which identifies the set of composite
pages that are immediately subordinate to the document layout root.
The value of this attribute is a sequence of one or more integers.
Each integer corresponds to an immediately subordinate page. In
our example, the value for subordinates would be '0 1 2' which
corresponds to the second digit in the three composite page object
identifiers. In other words, it identifies the pages 0, 1, and 2
as being subordinate to the root.
The composite page and image block must also include the
subordinates attribute. However, it will always be a single
integer of zero(O). This is because there is only one frame per
page and one block per frame; consequently, we will assign a value
of zero to each of them.
The specific block has a different relationship attribute, content

portions, which functions similar to the subordinates attribute.
30
It is used to specify which content portions are associated with

the specific block. Since there is only one content portion
associated with each block, this value will always be a zero (0)
Although not a part of the layout description, the content portion

must be associated with a specific block. This will be discussed
at the end of this section.
8.3.6 Specific Layout Attributes
Specific layout attributes are used to describe each specific

layout object.
An optional attribute on the composite page is medium type. It is

used to specify the nominal (physical) page size of the output
media. It specifies the rectangular size of the output media in
both the horizontal and vertical directions without any allowances
for border margins.
Another optional attribute is dimensions which may be used on

either the composite page or specific block objects. It specifies
the rectangular size of the page or block, respectively, in both
the horizontal and vertical directions and is specified in BMUs.
The dimensions for a page should be, wherever possible, smaller
than the nominal page size to allow for unused border space.
In the ODA Raster DAP, the dimensions of the frame cannot be

specified and the values default to the page dimensions.
Similarly, if the block dimensions are not specified, the block
dimensions default to the frame/page dimensions. When both page
and block dimensions are present, the block dimensions may be
smaller but not larger than the page dimensions.
Another optional attribute is page position which specifies the

location on the nominal page to position the page. It also is
specified in BMUs. The page position can only be used on the page
layout object. If the page size dimensions are the same as the
nominal page size, then the page position should be zero (0) so
that the edge of the page and the edge of the nominal page
coincide. If the page size is smaller than the nominal page size,
then a page position value should be selected that provides
approximately equal margins (border space) in the vertical
direction and equal margins in the horizontal direction. IS 8613-
2, clause 7.3, describes the general rules for positioning pages on
the media.
Another optional attribute for the specific block is position which

specifies the location of the block within the frame. This is the
location to start laying out the raster graphics content. It also
31
is specified in BMUs. It is particularly useful in conjunction

with the clipping attribute.
The optional application comments may be used when the content

contains tiled raster graphics data. It contains a sequence of
positive integers, one for each tile in the content portion. The
sequence of integers is a set of indices representing the octet
offsets to the beginning of the respective tiles, starting from the
beginning of the content information. The offsets will be
sequenced in the same order as the tiles.
Other optional attributes associated with the layout objects are:

presentation style (specific block only) ,user visible name, and
user readable comments. The presentation style was discussed
earlier. It contains the identifier, i.e., '5 O', linking it to a
specific presentation style constituent previously defined in the
document. The user visible name and user readable comments are
textual information attributes and are permitted on all layout
objects.
8.4 Document Profile
The document profile consist of a set of attributes which specifies

the characteristics of the document as a whole. Some of these
characteristics include: the DAP identifier, class of the specific
document, basic structure of the document, and default values for
attributes if they differ from the IS 8613 default values. Many of
the attributes in the document profile are also used in other
constituents but their use in the document profile is in a
different context. The relationships between the use of these
attributes in different constituents will be explained.
Some of the attributes are mandatory and others are optional

("non-mandatory") . The attributes applicable to the document
profile are defined for easy reference in Table 1 at the end of
this section. This table is a copy of Table D.3 from the ODA
Raster DAP.
In the discussion that follows, each of the attributes from Table

1 is defined and described in the order in which it appears in the
table. If it is desired to use a default value for any given
attribute other than the normal ODA default value, the default
value must be specified in the document profile. Otherwise, the
only default available for that attribute would be that default
value specified in IS 8613.
32
8.4.1 General Attributes
Specific layout structure: An attribute used if and only if the

document contains any specific layout descriptions. It specifies
that specific layout objects are 'present' in the document. For
the ODA Raster DAP, there will always be layout object descriptions
so this attribute must always be present.
Presentation styles: An attribute used if and only if the document

contains any presentation style constituents, that is, the
presentation style (s) is (are) 'present' in the document.
8.4.2 Document Characteristics
The document characteristics are a set of attributes which

describes the characteristics of the document. Most of the
attributes in the document profile are included within this set.
Document architecture class: An attribute which specifies the
architecture class of the document. For the ODA Raster DAP, this
can only be the 'formatted' form which facilitates the reproduction
of a document exactly as intended by the originator.
Document application profile: An attribute which specifies the

Document Application Profile (DAP) that pertains to the document.
Each DAP is assigned a unique identifier. This identifier is a
number registered with the appropriate authorities to distinguish
this DAP from any other. The object identifier assigned to the ODA
Raster DAP is {1 3 14 11 1 1}. AIIM is using an object identifier
of {1 2 840 10012}.
Content architecture classes: An attribute which specifies the

different classes of content allowed in the document. For the ODA
Raster DAP, only 'formatted processable raster content' is
permitted. This is content (raster data) which carries some of the
formatting intentions of the originator, but which still contains
enough of the original information to be further manipulated by the
receiving party.
Interchange format class: An attribute which specifies one of two
types of Office Document Interchange Formats (ODIF) to be used,
either 'A' or 'B'. Only class 'A' is permitted in the ODA Raster
DAP. This means that the order of the constituents is as follows:
document profile, presentation styles (optional) ,layout objects,
and content portions, see figure 1. The rules for using each class
and specifying the order of the data stream are defined in IS
8613-5, clause 5.
33
ODA version: An attribute identifying the standard and version to

which the document conforms. For the ODA Raster DAP, the values
are 'ISO 8613' and '1991-12-31', respectively.
Document architecture defaults: A set of attributes that specifies

the default attribute values for the document if the values are to
be different from the default values specified in IS 8613. The
attributes in this set are listed below:
Content architecture class: An attribute which specifies the

default value for the contents of the document. IS 8613
specifies the default value as 'formatted character content
architecture' which is not allowed in the ODA Raster DAP. This
value has no meaning in the context of raster data. Therefore,
the ODA Raster DAP has specified that this attribute is
mandatory and the value must be an object identifier of {2 8 2
7 2} for raster 'formatted processable content architecture'.
Type of coding: This attribute is mandatory. The default

encoding specified in IS 8613-7 for raster graphics data is 'T.6
encoding' which is the up bit order. MIL-R-28002B only allows
down bit order for encoding of T.6 data and therefore does not
allow the DAP permitted 'T.6 encoding' value. If the default
encoding for the document is to be tiled raster data, then this
attribute will contain a value of 'tiled encoding'. If the
default encoding for the document is to be T.6 encoding in the
down bit order, then the value will be 'T.6 encoding - MSB'.
The DAP does not allow the less useful default of 'bitmap
encoding' to be applied to the entire document.
Page dimensions: An attribute which specifies the default value

of the "dimensions" attribute for the page layout object. This
attribute must be specified only if the default is to be a value
other than NA-A size page.
Mediiim types: An attribute which specifies the default value of

the "medium type" (nominal page size) attribute used in the
document. This attribute must be specified only if the default
is to be a value other than NA-A size page.
Page position: An attribute which specifies the default value

of the "page position" attribute used in the document. Clause
7.3 of IS 8613-2 describes the rules for positioning pages on
presentation surfaces.
34
8. 4. 2.1 Raster Graphics Content Defaults

Raster graphics content defaults is a set of attributes which
specifies the default attribute values for the specific raster
graphics content within the document if the values are to be
different from the values specified in IS 8613-7. None of the
attributes in this set are mandatory. The ODA Raster DAP allows
the use of five attributes:
Pel path: The normal default is 0 degrees, it must be specified

if the default is to be 90, 180, or 270 degrees.
Line progression: The normal default is 270 degrees, it must be

specified if the default is to be 90 degrees.
Pel spacing: The normal default is 4 BMUs (300 pels/in.), it

must be specified if the default is to be 16, 12, 8, 6, 5, 3, 2,
or 1 BMU.
Spacing ratio: The normal default value is 1/1, it must be

specified if the default is to be other than 1/1.
Compression: The normal default value is 'compressed'. This

should be the normal situation. It must be specified as
'uncompressed' if the default is to allow the T.6 algorithm to
escape to the uncompressed mode. MIL-R-28002B has specified
that the 'uncompressed' mode will never be used, therefore this
attribute is not used within DoD.
8. 4. 2. 2 Non-basic Document Characteristics
The non-basic document characteristics is a set of attributes used

to specify the attribute values for the specific document if the
values are non-basic. A non-basic value is a value for an
attribute that is only allowed by the governing DAP (in this case
the ODA Raster DAP) to appear in the document interchange if its
use is declared in the document profile. All vendors supporting
the DAP would commonly be expected to support all the basic values,
but vendors may not commonly be expected to support the non-basic
values. Before processing a document, a receiving implementation
should look at the non-basic document characteristics to ensure
that it can continue processing the document. For example, a fall-
back procedure might be invoked rather than simply quitting, e.g.,
displaying an image at half-size.
The specification of the values of the attributes in this set is
mandatory only if non-basic values are to be used. For the ODA
Raster DAP, the allowable attributes are: page dimensions, medium
types, pel path, line progression, pel spacing, and compression.
35
Note that the pel path, line progression, pel spacing, and
compression attributes are grouped within a set called Raster
Graphics Presentation Defaults.
The medium types attribute must always be specified. There are no

basic values. Table 1 and the technical specifications of the DAP
show this attribute as being non-mandatory (permitted) However,
.
the text (section 6) and a comment in the technical specifications

(section 7) indicate that all nominal page sizes must be identified
as non-basic values. This approach was taken in the ODA Raster DAP
to be consistent with other international standard profiles.
If the image size is larger than the North American A size (spelled
out as basic in the DAP), then the page dimensions attribute has to
be declared in this section of the document profile. Any user's
choice of an image size up to NA-A size is declared as basic in the
DAP.
If a pel path of 180 or 270 degrees is to be used, then pel path

will have to be included in this section of the document profile.
If a line progression of 90 degrees is to be used, then line

progression will have to be included.
If a pel spacing of other than 16, 12, 8, 6, 5, 4, 3, 2, or 1 BMU

is to be used, then pel spacing will also have to be included in
this section of the document profile.
If the uncompressed mode of the T.6 algorithm is to be used within

the encoded data, the compression attribute must be included in the
document profile with a value of 'uncompressed'. This is not
applicable to MIL-R-28002B.
8.4.3 Document Reference Attribute
The dociuaent reference attribute contains a character string and is

used to identify the document. It is the only attribute out of a
set of document management attributes that is permitted for use in
the ODA Raster DAP.
8.4.4 Summary
In summary, the document profile has several attributes that may be

used. Many of them are optional and defaultable so they do not
always need to be specified. Table 1 contains the complete list of
36
these attributes. The following notation is used in the class

column of this table:
m mandatory attribute
nm non-mandatory attribute
d defaultable attribute
Capital letters (M, NM, and D) are used for groups of attributes.
8.5 Relationship of Objects

As stated earlier, the document profile must occur first in the
interchange and it will occur only once. It will be followed by
the presentation styles (if present) document layout descriptions,
,
and then the content portion descriptions. See figure 1.
Because the presentation styles, document layout descriptions, and

content portion descriptions may have multiple occurrences in the
interchange file, the relationship identifiers play an extremely
important role in uniquely identifying each of the objects. The
object identifier in the document layout descriptions, the style
identifier in the presentation styles, and the content identifier
layout in the content portions are used for this purpose. They all
consist of a sequence of non-negative integers as previously
discussed.
The style identifier consists of two integers with the first being
a five and the second uniquely identifying the presentation style.
The object identifier and content identifier layout all start with
a one as depicted in figure 9. There is only one document layout
root but all other objects have a second integer which uniquely
identifies the page in the document. The number of integers making
up the remainder of the identifier depends upon the level of the
object in the hierarchy but will always be zeros for the ODA Raster
DAP. Note that although the content portion is not considered a
part of the document layout description, the structure of content
identifier layout is the same as the structure of the object
identifier, it has one more integer than the specific block. This
is done so that each content portion can be uniquely assigned to a
specific block in the document layout description.
37
Table 1 - Document profile attributes
Attribute Class Permissible values
Specific-layout-structure m present
Presentation-styles nm present
Document-characteristics M
Document-architecture-class m formatted
Document-application-profile m {131411 1 1}
Content-architecture-classes m {2 8 2 7 2}
Interchange-format-class m A
ODA-version m ISO 8613, 1991-12-31
Document-architecture-defaults M
Content-architecture-class m formatted processable raster graphics
Type-of-coding m T.6 encoding, tiled encoding, T.6 encoding -
MSB
Page-dimensions nm See list in table 1 of ODA Raster DAP,
(Default value is NA-A, 9240 x 13200 BMU)
Medium-types nm See list in table 1 if ODA Raster DAP,
(Default value is NA-A, 9240 x 13200 BMU)
Page-position nm any coordinate pair within page (normal

default is 0,0)
Raster-gr-content-defaults NM
Pel-path nm 0, 90, 180, 270 degrees (0 is normal
default)
Line-progression nm 90, 270 degrees (270 is normal default)
Pel-spacing nm 16, 12, 8, 6 5, 4, 3, 2, 1 BMU, (Normal

default is 4 BMU)
Spacing Ratio nm Any value (normal default is 1/1)
Non-basic-doc-characteristics NM
Page-dimensions nm See table 1 in ODA Raster DAP
Medium-types nm See table 1 in ODA Raster DAP
38
Table 1 - Document profile attributes (concluded)
Attribute Class Permissible values
Raster-gr-presentation-features NM
Pel-path nm 1 80, 270 degrees
Line-progression nm 90 degrees
Pel-spacing nm Any value except 16, 12, 8, 6, 5, 4, 3,

2, or 1 BMU
Document-management-attributes M
Document Reference m Any string of characters
39
9 Technical Specification in the DAP
9.1 Genealogy
The ODA Raster DAP was created by direct reference to CCITT T.503
[3], an extremely simple DAP which allows only a single piece of
T.6 encoded raster content. Its simple structure formed an
appropriate basis for the ODA Raster DAP.
9.2 Simplifications
Many unnecessary items found in more fully-featured DAPs were
intentionally left out. Primary among these items are elements of
logical structure such as descriptions which allow for chapters,
sections, and paragraphs. The layout structure of page sets was
also omitted.
9.3 DAP Narrowed by MIL-R-28002B
Although some parameters in the DAP allow for great flexibility,

several of these are further limited by MIL-R-28002B.
For example, the DAP follows the ODA convention that specifies a
default pel spacing of 4 Basic Measurement Units (BMUs) . This
equates to 300 pels per inch. MIL-R-28002B requires 300 pels per
inch for technical manuals and illustrations, but 2 00 pels per inch
for large-format engineering drawings. This means that the
defaulting mechanism inherent in the DAP cannot be used with
engineering drawing scans.
MIL-R-28002B requires systems to export images with sizes which are
multiples of eight; the DAP has no similar restriction.
Using a checklist in MIL-R-28002B, other parameters are left to the

determination of the contracting officer and may be narrowed by
restrictive language in the contract document. These could include
disallowing bitmapped tiles except in the case of reverse
compression, requiring rotation of the image to proper viewing
orientation (rather than merely describing the proper viewing
orientation) , and requiring the zeroing of the unused portions of
tiles. These issues are further considered in the Technical
Concepts section. (See also MIL-R-28002B section 6.2.)
The DAP uses the notion of pel spacing rather than pels per
unit length (the reciprocal) . The pel spacing is thus a distance
measured using the unit BMU (basic measurement unit) . There are
1200 BMUs per inch. Pel spacing is expressed as a ratio, rather
than simply as a number. A pel spacing of 6/1 is a ratio of a
distance of 6 BMUs to one pel interval. Since 6 * (1/1200) =
(1/200) ,
this corresponds to 200 pels per inch.
40
. .
Technical Specification In the DAP
9 . 4 Proforma and Notation
The proforma and notation for ODA DAPs is defined in Annex F of IS

8613-1. It describes in detail the format for a DAP. It also
specifies a meta-language to be used in writing a DAP, specifically
the technical specifications in section 7 of the ODA Raster DAP.
The meta-language may be thought of as a higher level language

similar to the high level programming languages such as COBOL,
Pascal, etc. The ASN.l Definitions may be thought of more like a
lower level assembly programming language. However, in either
case, the meta-language and ASN.l Definitions define the structure
of the Raster Interchange Format (RIF)
The intended purpose of using the proforma and notation is to aid

clarity and remove ambiguity, ensure that all necessary information
is included, aid comparison between DAPs, and aid verification and
conformance testing. As verification and conformance testing of
the DAP proceeds, section 7 of the DAP may have to be revised. The
following discussion of the section 7 is intended to provide
general guidance on proforma and notation, not a detailed tutorial.
As experience grows in using proforma notation, verification, and
conformance testing, this section may be expanded.
The following terms are used in document application profiles.

They are the reserved keywords of the DAP proforma and notation.
Their definitions, as found in Annex F, are:
REQ Required.
PERM Permitted.
DIS Disallowed.
DEFINE Defines a macro.
MUL A group of parameters that may be
repetitive.
PMUL A group of parameters that may be optional.
SPECIFIC: Announces attributes specified for
objects
FACTOR: Announces a common set of constraints.
$ Begins a macro invocation.
{ } Used as a pair of symbols to delimit a
syntactical unit or grouping.
{ANY_VALUE} Any attribute or parameter value
permitted by IS 8613.
# Indicates parameter or
control function name.
[•] Indicates an optional syntactic item.
41
,
Technical Specification in the DAP
9.5 Elements of the DAP
The remainder of this section of the tutorial discusses a technical

view of the different elements of the DAP and how they arise from
the standards. A DAP Technical Specification section is an
unambiguous definition that can be read by automated systems such
as compilers and test suites. These suites could check for
consistency and implementability of the DAP. This is the objective
of the ODA Conformance Test (ODA-CT )a testing tool developed
jointly by the Canadian Department of Communications, the United
Kingdom National Computing Center, and Japan's Interoperability
Technology Association for Information Processing (INTAP) ODA-CT
.
will also check ODA Office Document Interchange Format (ODIF) data
streams for conformance to IS 8613.
9.6 Format of DAP Technical Specification Section

In section 7 of the DAP, there is a description for each type of
constituent that is allowed in a document conforming to the DAP.
Each description may include three primary elements of information:
macro definitions, factor constraints, and constituent constraints.
Macro definitions provide a shorthand mechanism for use later in
the notation.
Factor constraints describe the attributes and their associated

values which apply to all constituents within that specific
category, i.e., factor constraints for the layout structure
apply to all the layout objects.
Constituent constraints describe the attributes and their

associated values which apply specifically to each constituent
in that category, i.e., for the layout structure, there is a
constituent constraint for each of the document layout objects.
9.7 DAP Technical Specification
All of the DAP notations and name references below in the smaller
font illustrate examples extracted directly from the ODA Raster
DAP. Much of the detailed discussion concerning the constituents
and associated attributes was done in the earlier section, ODA
Constituents and Attributes, and will not be repeated in this
section. Again, the order of the discussion that follows has been
chosen to help those with raster graphics related background by
starting with an area that they are probably already familiar with.
42
9.7.1 Content Portion Constraints
The content portion constraints section shown below (extracted from

section 7.6 of the ODA Raster DAP) describes the content portion.
The Raster-graphics-content-portion describes the content portion description.
The Content-identifier-layout is a required attribute consisting of five
integers as discussed in section 8 of this document. The {ANY VALUE}
means any value permitted by ISO 8613. Type-of-coding is optional but
when used must be one of the listed ASN.l object identifiers. The
default value is 'T.6 encoding' (down bit order) unless specified
differently in the document profile.
Raster-graphics-content-portion {
REQ Content-identifier-layout {ANY_VALUE},
PERM Type-of-coding { ASN.1{2 8 3 7 0} “ T.6 encoding -
I
ASN.1{2 8 3 7 1} - T.4 one dimensional -
I
ASN.1{2 8 3 7 2} - T.4 two dimensional --
I
ASN.1{2 8 3 7 3} - bitmap encoding --
1
ASN.1{2 8 3 7 5} - tiled encoding —
I
ASN.1{2 8 3 7 6} - T.6 encoding - MSB —
1
ASN.1{2 8 3 7 7} - T.4 one dimensional - MSB -
1
ASN.1{2 8 3 7 8} - T.4 two dimensional - MSB -
h
PERM Coding-attributes {
REQ #raster-graphics-coding-attributes {
PERM #compression {ANY VALUE},
PERM #number-of-lines {>0}/
REQ #number-of-pels-per-line {>0}»
CASE Raster-graphics-content-portion (Type-of-coding) QF {
{$TILED}: (PERM #number-of-pels-per-tile-line {512},

PERM #number-of-lines-per-tile {512},
PERM #tiling-offset {ANYVALUE},
PERM #tile-types {'null background' |
'null foreground' |
'T.6 encoded' |
'bitmap encoded' |
'T.6 encoded - MSB'}}}},

PERM Alternative-representation {ANY_STRING},
PERM Content-information {RASTER}
}
The Coding-attributes for raster graphics always requires the

number-of-pels-per-line attribute and it must always be greater than zero.
The compression and number-of-lines attributes are permitted at any time.
43
. ,
The compression attribute is not permitted in MIL-R-28002B. The

pound (#) character in front of the attributes is used by the DAP
notation to indicate that it is a parameter. For purposes of this
tutorial, only the attribute term is used.
The CASE structureindicates that the number-of-pels-per-tile-line

number-of-lines-per-tile , and tile-types attributes are permitted when
tiling-offset,
Type-of-coding is 'ASN.1{2 8 3 7 5}'. Note that the CASE structure
references the macro TILED which was defined in the paragraph 7 6 of .
the DAP as: DEFINEITILED," ASN.l {2 8 3 7 5}") The number-of-pels-per-tile-line, and

.
number-of-lines-per-tile, if specified, can only contain the value of 512

which is the default value specified in ISO 8613-7. Consequently,
these attributes never need to be specified. For the tile-types
attribute, any one of the five listed values is allowed.
The raster data is contained in the Content-information. Although it is

shown as permitted, it is not logical to omit the raster image from
the interchange. The Alternative-representation attribute is permitted and
may contain an ASCII character string for display by a receiver if
the raster image cannot be displayed.
9.7.2 Presentation Style Constraints
The Factor Constraints description, FACTOR shown below, specifies

the attributes and their associated values that apply to any of the
presentation style constituents, ANY-PRESENTATION-STYLE, regardless of
the number of occurrences that may exist in the interchange file.
The Presentation-style-identifier attribute is always required and consists of
a sequence of integers as discussed in the earlier section, ODA
Constituents and Attributes.
FACTOR ANY-PRESENTATION-STYLE {
REQ Presentation-style-identifier {ANYVALUE},

PERM User-readable-comments {ANY STRING},
PERM User-visible-name {ANY_STR1NG}
}
The PStyle description (shown below) specifies the attributes and

their associated values that apply to only raster presentation
style constituents. It contains any of the factor constraints
listed above in the ANY-PRESENTATION-STYLE plus any of the raster
graphics Presentation-attributes; pel-path, line-progression, pel-spacing, spacing-ratio,
clipping
44
PStyle: ANY-PRESENTATION-STYLE {
PERM Presentation-attributes {
PERM #raster-graphics-attributes {
PERM #pel-path {ANY_VALUE},
PERM ^line-progression {ANY_VALUE},
PERM #pel-spacing {REQ ^length {ANY_VALUE},
REQ #pel-spaces {ANY VALUE}},
PERM #spacing-ratio {REQ {ANY VALUE},
#line-spacing-value
REQ #pel-spacing-value {ANY_VALUE}},
PERM ^clipping {ANY_VALUE}}}
}
9 . 7.3 Layout Constituent Constraints
A single macro definition is defined and referenced within the

specific block.
DEFINEIRAST," CQNTENT_ID_QF(Raster-graphics-content-portion)")
The FACTQR in the case below describes the attributes that may be
specified in ANY-LAYQUT. The Qbject-identifier is required, the values
consist of a sequence of integers and were described in the ODA
Constituents and Attributes section. The Qbject-type attribute shows
a value of VIRTUAL which means its value is specified in a later
constraint, e.g., DocumentLayoutRoot, CompositePage, ImageFrame and ,
SpecificBlock.
FACTQR ANY-LAYQUT {
SPECIFIC:
PERM Qbject-type {VIRTUAL},
REQ Qbject-identifier {ANYVALUE},
PERM Subordinates {VIRTUAL},
PERM User-visible-name {ANYVALUE},
PERM User-readable-comments {ANYVALUE}
}
In the DocumentLayoutRoot, the attribute identifies the object

Qbject-type
as a document-layout-root. Subordinates identifier is used to uniquely
The
identify each page under the DocumentLayoutRoot. The plus sign
indicates an incrementing subordinate identifier is associated with
each succeeding page.
45
}
DocumentLayoutRoot: ANY-LAYOUT {
SPECIFIC:
REQ Object-type { 'document-layout-root'},
REQ Subordinates {SUBJD_OF(CompositePage) -i-
In the CompositePage the Object-type attribute identifies the object as

,
a page. The Subordinates attribute operates basically the same as above

except it identifies the frame associated with the page. Note that
there is not a plus sign, so there can be only one frame per page.
The CompositePage includes additional attributes for describing the
page, e.g.. Dimensions, Page-position, and Medium-type. The Dimensions
attribute uses a macro PermissiblePageDimensions which is defined in the
document profile.
CompositePage: ANY-LAYOUT {
SPECIFIC:
REO Object-type {'page'},
REQ Subordinates {SUBJDOFdmageFrame)},
PERM Dimensions {$ PermissiblePageDimensions},
PERM Page-position {ANY_VALUE},
PERM Medium-type {PERM #nominal-page-size {$NominalPageSizes},
PERM #side-of-sheet {ANY_VALUE}},
PERM Application-comments {ANY_VALUE}
}
ImageFrame: ANY-LAYOUT {
SPECIFIC:
REQ Object-type {'frame'},
REQ Subordinates {SUB_ID_OF(SpecificBlock)},
PERM Application-comments {ANY_VALUE}
}
The SpecificBlock refers to two macros, RAST and Content-architecture-class which

are defined in the content portion and document profile,
respectively. The Position and Dimensions attributes describe the
positioning and size characteristics of the block within the frame.
Note that presentation attributes may be specified by either of two
alternatives. The attributes could be listed directly in the block
or there could be a reference to a presentation style. It is even
possible to have both. An implementor could refer to a
presentation style which specifies certain characteristics for
presenting the image. In turn, there could be a specific
presentation attribute in the block which overrides the same
46
.
attribute in the presentation style. This does make the encoding

more complex but does allow for greater flexibility.
SpecificBlock {
SPECIFIC:
REQ Object-type {'block'},
REQ Object-identifier {ANY_VALUE},
REQ Content-portions {$RAST},
PERM Position {REQ #fixed-position {
REQ ^horizontal-position {ANY VALUE},
REQ #vertical-position {ANY_VALUE}}},
PERM Dimensions {REQ ^horizontal-dimension
{REQ #fixed-dimension {ANY VALUE}},
REQ #vertical-dimension
{REQ #fixed-dimension
{ANY_VALUE}}},
PERM Content-architecture-class {$FPR},
PERM User-readable-comments {ANY_STRING},
PERM User-visible-name {ANY_STRING},
PERM Application-comments {ANYVALUE},
PERM Presentation-style {STYLEJD_OF(PStyle)},
PERM Presentation-attributes {
PERM #raster-graphics-attributes {
PERM #pel-path {ANY_VALUE},
PERM #line-progression {ANY_VALUE},
PERM #pel-spacing {REQ ^length {ANY VALUE},
REQ #pel-spaces {ANY_VALUE}},
PERM #spacing-ratio {REQ #line-spacing-value {ANY_VALUE},
REQ #pel-spacing-value {ANY VALUE}},
PERM ^clipping {ANYVALUE}}}
9.7.4 Doctment Profile Constraints
At this point, practically every DAP proforma and notation

construct used in the ODA Raster DAP has been discussed above.
Therefore, the document profile constraints are not shown in this
tutorial
It might be worth discussing macros:

four BasicPageDimension,
NonBasicPageDimensions PermissiblePageDimensions, and
, NominalPageSizes. The
BasicPageDimension macro identifies the range of allowable basic values
(up to ISO AO and NA A) for the page dimensions. The
NonBasicPageDimensions (only a partial list included in this document)
identifies the range of allowable non-basic values (larger than ISO
AO and NA A size) for the page dimensions. The PermissiblePageDimensions
macro identifies the total range of permissible page sizes. The
47
NominalPageSizes macro identifies actual nominal page sizes permitted

by the ODA Raster DAP.
DEFINEIBasicPageDimension,"
REQ #horizontal-dimension {REQ #fixed-dimension { 1..9240 }},
REQ #vertical-dimension {REQ #fixed-dimension { 1.. 12400 }}
I
REQ ^horizontal-dimension {REQ ^fixed-dimension { 1.. 12400 }},
REQ #vertical-dimension {REQ #fixed-dimension { 1..9240 }}
DEFINEINonBasicPageDimensions,"
{REQ ^horizontal-dimension {REQ #fixed-dimension {1.. 39680}},
REQ #vertical-dimension {REQ #fixed-dimension {1 2401 ..561 20}}}
I
{REQ ^horizontal-dimension {REQ #fixed-dimension {9241 ..39680}},
REQ #vertical-dimension {REQ #fixed-dimension {1.. 561 20}}}
- up to ISQ AO portrait --
... etc
DEFINE(PermissiblePageDimensions,"
{REQ #horizontal-dimension {REQ #fixed-dimension {1.. 39680}},
REQ #vertical-dimension {REQ #fixed-dimension {1.. 561 20}}}
- up to ISQ AO portrait --
• • • etc
DEFINEINominalPageSizes,"
REQ ^horizontal-dimension {7015}, REQ #vertical-dimension {9920}

- ISQ A5 Portrait -
... etc
48
. . .
10 ASN.l Coding Concepts

10.1 ASN.l Notation
ASN.l provides a very formal and rigidly defined notation for

describing protocols and standards. A good working knowledge of
ASN.l and the Basic Encoding Rules is essential to a successful
implementation of the ODA Raster DAP encoding or decoding program
at least until more ODA tools become available.
ASN.l is a formal description language based on the concept of

tags, data types, and values for those types. All objects to be
interchanged are either primitive or constructed data types.
Primitive types are simple elementary types such as an integer or
octet string. Constructed types are those that have been built up
from various simple types or other constructed types. A large set
of predefined data types exists and application specific ones may
be created.
ASN.l provides powerful mechanisms for expressing the restriction

of types to other types or to ranges of values. Recursive
definitions are permitted.
It would seem possible to implement the ODA Raster DAP in several

ways: (1) compile section 7 of the DAP with a "DAP Compiler", which
directly generates C code from the DAP (nothing like this is known
to exist), (2) compile the ASN.l Definitions describing the DAP
into C code using an ASN.l compiler (these do exist), or (3)
directly write C code or use any other programming language to
implement the structures in the ASN.l Definitions describing the
DAP. It should be noted that there are certain semantical
descriptions in the DAP that are not present in the ASN.l
Definitions; therefore, these semantical meanings are lost when
using an ASN.l compiler versus a DAP compiler. Similarly, when
generating C code versus using an ASN.l compiler, some of the
rigidity and restrictions may be lost if the implementor is not
careful
10.2 Sample of ASN.l Definitions
The following discussion is based upon the ASN.l Definitions which

represent the source statements for the implementation of the ODA
Raster DAP. The entire listing of the ASN.l Definitions appears in
ASN.l Definitions, Appendix A. Excerpts are included below to aid
in the discussion.
Comments may be used in ASN.l and are identified with a double

hyphen (
—
This tutorial also uses additional comments which are
)
interspersed within the ASN.l Definitions and appear in a different

font
49
ASN.l Coding Concepts
Any set of ASN.l Definitions must be enclosed within an ASN.l shell

structure as follows.
Rif-Module
DEFINITIONS :: =
BEGIN
-- ASN.l Definitions for a module called Rif-module.
END
The Rif-module, Raster Interchange Format module, is the name given to

this particular set of ASN.l definitions. All of the definitions
must be within the BEGIN and END block. The first group of
definitions list the allowable objects, called Interchange Data
Elements, that may be selected.
Rif-Module
DEFINITIONS :: =
BEGIN
Interchange-Data-Element ::= CHOICE {

document-profile [0] IMPLICIT Document-Profile-Descriptor,
layout-object [2] IMPLICIT Layout-Object-Descriptor,
content-portion [3] IMPLICIT Text-Unit,
presentation-style [7] IMPLICIT Presentation-Style-Descriptor
}
An interchanged document can consist of several Interchange-Data-Element

objects. Which and how many of them are used will depend upon the
contents of the specific document. For the ODA Raster DAP, a
single page document requires the selection of a document-profile,
optionally a presentation-style, the layout-object four times (once each for
document layout root, composite page, image frame, and specific
block) and a content-portion.
,
All of these objects to be interchanged are further defined as

constructed (built up of other types) The Rif-Module itself is the
.
first such object definition which is a constructed type. It

begins with a DEFINITIONS ::= and is contained within a BEGIN END ...
block. The Rif-Module has the rules to create each interchange data
element that the DAP might specify. For this reason, it is a
CHOICE. A different recipe applies depending on which type of item
is to be interchanged next. Each choice must be uniquely tagged,
and is identified with a number in brackets. For example, the
document-profile has a tag of zero [0] whereas the content-portion has a tag
of three (3).
The content-portion is further defined by a reference to Text-Unit.
50
ASN . 1 Coding Concepts
Text-Unit :;= SEQUENCE {

}
The Text Unit is a SEQUENCE consisting of the items within the braces.
The order must be preserved, that is, content-portion-attributes comes first
followed by content-information. In a sequence, there does not need to
be any tags. Among those items, the ones listed as OPTIONAL are not
mandatory.
The content-information is further defined by Content-Information (below) which

is a CHOICE between one-octet-string or seq-octet-string The one-octet-string is a .
primitive of OCTET STRING. This octet string is designed to contain

an untiled raster image. The seq-octet-string is a SEQUENCE OF OCTET STRINGS
where each octet string will contain a single tile of the raster
image.

In returning to the Text-Unit to examine the Content-Portion-Attributes, we can

see that it is a SET (below) That means that the items within
.
braces may occur in any order.

Content-Portion-Attributes ::= SET{

} OPTIONAL }
The content-identifier-layout is further defined by and the

Content-Portion-Identifier
type-of-coding by Type-Of-Coding . The coding-attributes must be a CHOICE between
raster-gr-coding-attributes or alternative-representation which have tags of [2] and
[3], respectively.
is a keyword which saves space when the data is reduced to

IMPLICIT
bytes in the encoding process. It indicates that in building the
tag for a given object, the type for the object is not needed.
Content-Portion-Identifier ;:= [APPLICATION 0] IMPLICIT PrintableString
The is a primitive (simple, elementary) type that

Content-Portion-Identifier
is not further defined. It is specifically defined for the ODA
application as a printable string.
51
Type-Of-Coding ::= CHOICE {

{2 8 3 7 0} 'T6 encoding'
” or {2 8 3 7 1} 'T4 one dimensional encoding'
” or (2 8 3 7 2} 'T4 two dimensional encoding'
“ or {2 8 3 7 3} 'bitmap encoding'
- or {2 8 3 7 5} 'tiled encoding'
" or {2 8 3 7 6} 'T6 encoding - MSB'
- or {2 8 3 7 7} 'T4 one dimensional encoding - MSB'
” or {2 8 3 7 8} 'T4 two dimensional encoding - MSB'
}
The Type-Of-Coding is also another primitive type. In this case, it

is a CHOICE between one of the object identifiers which determines
the type of encoding of the content information (raster image)
Raster-Gr-Coding-Attributes SET {

compression [2] IMPLICIT Compression OPTIONAL,
- number-of-pels-per-tile-line [6] IMPLICIT INTEGER OPTIONAL,

number-of-pels-per-tile-line is always a constant 512
- number-of-lines-per-tile [7] IMPLICIT INTEGER OPTIONAL,
number-of-lines-per-tile is always a constant 512
tiling-offset [8] IMPLICIT Coordinate-Pair OPTIONAL,

tile-types [9] IMPLICIT SEQUENCE OF Tile-Type OPTIONAL
}
The Raster-Gr-Coding-Attributes structure type defines all of the raster

graphics coding attributes. Note that the number-of-pels-per-line and
number-of-lines are primitive types of INTEGER.
The tile-types is a sequence of Tile-Type. Each Tile-Type is an integer value

(below) The allowable values are 0, 1 ,
2 , 5 , or 6
Tile-Type INTEGER
null-background (0),
null-foreground (1),
encoded-t6 (2),
bitmap (5),
encoded-t6-msb (6)
}
- T.4 not supported in tiled encoding
There is one other definition that has not been discussed and that
is the enumerated data name. This is illustrated by the document-
architecture-class (below) within the Document-Characteristics of the Document-
52
.
The code that follows describes the usage formatted (0) for
Profile-Descriptor,
This indicates that the interchanged value is
document-architecture-class.
a zero, but that zero is simply the defined representation for the
formatted type of document architecture class. The word
'formatted' is used in ODA ASN.l Definitions as an enumerated data
name. The data stream will contain an integer with the value of
zero (0) which signifies that it is a formatted document.
document-architecture-class [1] IMPLICIT INTEGER {
formatted (0)}
OPTIONAL
All of the other ASN.l Definitions use the same basic data types as
those discussed above. For a complete list of the ASN.l
Definitions for the ODA Raster DAP, refer to Appendix A.
10.3 The Basic Encoding Rules
The Basic Encoding Rules define one way to actually encode ASN.l
objects into binary values for interchange (transfer values) using
a syntax called Office Document Interchange Format (ODIF) ODA .
permits other encoding rules to be used. The Basic Encoding Rules

are the only rules discussed in this document.
A detailed understanding of the Basic Encoding Rules is not

required to understand the ODA Raster DAP. In fact, users of a
library of ASN.l routines would probably never need to understand
encodings at the bit or byte level. Only a programmer of elemental
ASN.l input and output routines would need such a detailed
understanding. These individuals should refer directly to ASN.l
(IS 8824) and Basic Encoding Rules (IS 8825) standards to assure a
proper implementation.
This section provides a brief introduction to the Basic Encoding

Rules. The key idea is that these codes are best left to programs
to read and write. One would not wish to read a business letter by
viewing hexadecimal ASCII codes; one would use a word processing
program
The Basic Encoding Rules are similar to many file formats in that
for each object they encode, they specify a type, a length, and
then a value. Each type is specified by a tag identifier. These
tag identifiers are specified in the ASN.l Definitions inside the
brackets, i.e., [3].
Each tag identifier belongs to one of four classes of tags, defined

by a two bit pattern. A tag identifier also has a five bit tag
number which was chosen in each case to be unambiguous in the
context of other tags. A one bit flag, which indicates whether the
53
value to which the tag identifier refers, is constructed or

primitive is also present in the tag identifier. Constructed
values or objects are built up from other objects.
Figure 10 indicates how the tag identifiers are built up from the
class, tag number, and constructed flag of a given ASN.l object.
Tag identifiers also have a long form for handling tag numbers
greater than 30. We show only the short form.
7 6 5 4 3 2 1 0 Bit Number In Byte
1 0 Tag Class - cont-spec
1 Constnjcted Rag
0 0 0 1 0 Tag Number - 2
1 0 1 0 0 0 1 0 Assembled
1
Tag Identifier
I
Hexadecimal Version
Figure 10 - Constructing Tag Identifiers.
There are four classes of tags. Shown below are their names, their
two-bit codes used in constructing tag identifiers, and their use:
Universal 00 Types that are defined in IS 8824,

e.g., INTEGER, OCTET STRING. [13]
Application 01 Types that are defined for the

specific application, e.g. ODA has ,
defined APPLICATION 0 to be a string

containing only digits and spaces.
Context-specific 10 Types which are defined only for a

specific context such as SET or
SEQUENCE which were illustrated
earlier.
Private 11 Not used in the ODA Raster DAP.
54
The length associated with an object includes the length of all

objects contained within it. Figure 11 shows the two length
encoding schemes: definite and indefinite length. The definite
length method can have either a short or a long form. The short
definite form is only valid for contents with a length of 0 to 127
whereas the long definite form is valid for any definite length,
including small values that could use the short definite form. For
primitive objects and simpler constructed objects, it is relatively
easy to anticipate their length. In this situation, the definite
length encoding is used.
Short definito form:
1 i n I 1 1 i 1
(toriflin )
Long definite form:
1 ...
Ill'll I 1 I 1 I 1 1 I 1
(« of suosaquont (langih (
)
( octets )
indefinite form:
1 0 0 0 0 0 0 0 constructed contents octets •••
(indefinite length)
i
00000000
J-L
00000000
III
I,.I. 1, 1 I
I ' I '
(endofconteno )
Figure 11 - Definite and Indefinite Length Encoding.

This figure is extracted from Gaudette [7].
For complicated tagged objects, it might not be possible to

determine their lengths until the lengths of their sub-elements are
known. In this case, indefinite length encoding becomes useful.
This method begins the object without specifying its length. A
sequence of sub-elements then appears. The end of the object is
marked by appending an end-of -contents flag, two bytes of zeros.
Indefinite length encoding may be easier for a writing program when

it encounters complicated objects, but it makes a reading program's
job more difficult. If the length is not known, it is not possible
to simply skip over the large object even if it is not of interest.
The object must be parsed in detail in order to find the
end-of -contents flag. This parsing examines only the type and
length of each sub-element. Each sub-element which is not an
55
end-of -contents flag can then be skipped over by use of its length
information.
10.4 Transfer Values

Transfer values are hexadecimal listings that specify the actual
binary octets (bytes) placed in an interchanged file. They are the
result of applying the Basic Encoding Rules to the ASN.l
Definitions. A standard indenting scheme makes it easier to
understand the nesting of objects.
Although the DAP notation and ASN.l Definitions describe the entire
range of all possible interchanged files, the transfer values
—
listing is very specific it describes a single instance of an
interchanged file. Using the ASN.l Definitions from Appendix A and
a full page test chart from Appendix B, interchange examples of
transfer values were developed in Appendices C-F.
The ASN.l Definitions were read into the Free Value (Freeval) tool
(see Tools, section 11) to evaluate and verify the correct ASN.l
syntax. The tool was then used to insert values for attributes
specific to the test chart document and to encode the transfer
values for the different interchange examples illustrated in
Appendices C-F. The first column of Appendices C-F shows the
source data for each of the attributes to be included in the
interchange file. The second column contains the resulting output
from the Free Value tool after encoding the source data.
Appendix C is used for the remainder of this section to describe

the transfer values. However, only an excerpt, specifically the
content-portion will be used to describe the transfer values in detail.
The relevant ASN.l Definitions from Appendix A is extracted and
shown below.
Interchange-Data-Element :: = CHOICE {
document-profile [0] IMPLICIT Document-Profile-Descriptor,

}
Text-Unit SEOUENCE {
}
56

}
OPTIONAL }
Content-Portion-Identifier :: = [APPLICATION 0] IMPLICIT PrintableString
Type-Of-Coding ::= CHOICE {

- {2 8 3 7 6} 'T6 encoding - MSB'
}

seq-octet-string SEOUENCE OF OCTET STRING }
Alternative-Representation ;:= OCTET STRING
Raster-Gr-Coding-Attributes SET{
- number-of-pels-per-tile-line [6] IMPLICIT INTEGER OPTIONAL,

number-of-pels-per-tile-line is always a constant 512

}
Tile-Type ::= INTEGER!

encoded-t6 (2),
bitmap (5),
encoded-t6-msb (6)
}
Ra-Gr-Coding-Attribute CHOICE!
compression [0] IMPLICIT Compression
}
57
Compression ::= INTEGER {uncompressed (0), compressed (1 )}

-- The 'Compression' attributesupported by AliM but not by CALS.
is
-- CALS data streams always uses the default value of 'compressed'.
Inserting the source data transfer values for the content-portion

resulted in the structure illustrated below. The type-of-coding object
identifier value of {2 8 3 7 6} indicates that the image will be
encoded as 'T.6 encoded - MSB' data. The number-of-pels-per-line will be
'2550', the number-of-lines will be '3300', and the compression is '1'
indicating that the T.6 escape mechanism is not used.
content-portion {
content-portion-attributes {
content-identifier-layout "1 0 0 0 0",
type-of-coding other-coding { 2, 8, 3, 7, 6 },
coding-attributes raster-gr-coding-attributes {
compression 1,
number-of-pels-per-line 2550,
number-of-lines 3300 } },
content-information one-octet-string
'...'H - '< <T.6 encoded - MSB data> >'H
}
This results in the interchanged transfer data values as follows:
<12832>
a3 82 32 1c [3] constr <12828>
. 31 1e [UNIV 17] constr <30>
. . 40 09 [APPLO] <9>
31 20 30 20 30 20 30 20 30
. . 86 04 [6] <4>
58 03 07 06
. . a2 Ob [2] constr < 1 1 >
. . . 82 01 [2] <1 >
01
. . 80 02 [0] <2>
.
09 f6
. . 81 02 [1] <2>
.
Oc e4
. 04 82 31 f8 [UNIV 4] <12792>
- 12792 octets of compressed data (T.6 encoded - MSB)
The only items which actually appear in the interchanged data are
the octets shown as hexadecimal values. Words, decimal points, or
items in angle or square brackets are placed in the listing by the
Free Value tool to aid readability and do not occur in the
interchanged data.
58
;
Items in angle brackets are decimal lengths of the values that

follow. Items in square brackets are decimal tags corresponding to
the ASN.l Definitions. Items occurring in pairs are hexadecimal
digits. Each pair of hexadecimal digits represents one octet. The
octet values are a part of the interchange file whereas the other
inf oirmation, such as decimal points and numbers contained in angle
brackets and square brackets, are not a part of the interchange
file but are used to aid the discussion and understanding of the
file contents. The decimal points are included to show the
structure of the data and make it easier to follow the example.
Referring to the interchange object represented in the sixteen

lines above and beginning with 'a3 82 32 Ic [3] constr < 2828> ' we see 1 ,
that it is a constructed object made up of smaller objects. The

word "constr" inserted by the Free Value tool is actually
redundant. We could have come to the same conclusion by several
other means: (1) the indenting structure using the decimal points
below that line shows other objects; or (2) the bit structure of an
'a3', binary of '10100110', by the Basic Encoding Rules indicates
a constructed type (third bit is a 1) .
In the discussion below, binary values are shown in parentheses.

While going through this encoding, it is helpful to refer to the
ASN.l Definitions describing the Interchange-Data-Element in the Rif-module
(see relevant ASN.l Definitions above).
<12832>
a3 82 32 1c [3] constr <12828>
Each Interchange-Data-Element, interchange object, in the transfer values

listing begins with a decimal number in angle brackets showing the
length in octets of the entire Interchange-Data-Element. In this example,
the entire length of the content-portion object is 12,832 octets.
Encoding the third CHOICE, content-portion, of the Interchange-Data-Element
results in the a transfer entry 'a3 82 32 Ic' The tag identifier
.
'a3', refer to figure 10, stipulates a context-specific (10),

constructed (1) transfer value with a tag number of three (00011)
(10 )
( 1 )
( 00011 )
(10100011) = a3 hexadecimal.
From the ASN.l Definitions, we see that the item having the tag [3]
in the present context is the content-portion. From this, we see that
the content-portion is of type Text-Unit.
59
, , ,
.
The '82' uses the long definite form of length and specifies the
number of octets in the length value of the structure that will
follow. That is, the first bit of the octet (1) designates a long
definite form and therefore the following bits (0000010) is a
length (length of a length) indicating that two octets follows
which in turn contains the length of '32 1c' for the
content-portion. The actual length of the value for the
content-portion is '321c' or 12,828 octets.
. 31 1e [UNIV 17] constr <30>
Encoding the first element in the SEQUENCE of the Text-Unit, content-

results in the second entry '31 1e'.
portion-attributes, The '31'
stipulates a universal type (00), constructed (1), transfer value
having tag number (10001) representing decimal 17. The resulting
encoding is a constructed type, universal type 17 which indicates
a set. The length of the transfer value (structure that follows)
'1e', is 30 octets shown in the short definite form.
. . 40 09 (APPL 0] <9>
31 20 30 20 30 20 30 20 30
Encoding the first element in the SET of the content-portion-attributes,

results in the third and fourth entry '40 09' and
content-identifier-layout,
'31 20 30 20 30 20 30 20 30', respectively. The '40' stipulates an
application type (01) primitive (0)
,
tag number of zero (00000)
In this instance, the tag number identifies the application class
tag. The application class tags are defined within the ODA realm
of "application." They are shown in IS 8613-5, Annex B, to be:
Application 0 Content-Portion-Identifier
Application 1 Object-or-Class-Identif ier
Application 2 Content-Type
Application 3 Character-Data
Application 4 Date-and-Time
Application 5 Style-Identif ier
Again, the length of the transfer value, '09', is nine octets in

the short definite form and the value is '31 20 30 20 30 20 30 20 30'
which is the encoding for the Printable String '1 0 0 00'.
. . 86 04 [6] <4>
58 03 07 06
Encoding the second element in the SET of the content-portion-attributes, type-

results in the fifth and sixth entry '86 04' and '58030706',
of-coding,
respectively. The '86' stipulates a context-specific (10) ,
primitive (0) tag number of six for object identifier (00110)
60
. ,
The '04' again is a short definite form with the length being four.
The type-of-coding value of {2, 8, 3, 7, 6} is encoded as '58 03 07 06'.
Clause 20 of IS 8825 describes the encoding process for object
identifiers
. . a2 Ob [2] constr <11>
Encoding the third element in the SET of the content-portion-attributes,

results in the seventh entry 'a20b'. The coding-attributes
coding-attributes,
consists of a CHOICE, in our case it is the raster-gr-coding-attributes The .
'a2' stipulates a context-specific (10), constructed (1), transfer

value with a tag number of two (00010) for tag [2]. The length of
the transfer value, 'Ob' is 11 octets shown in the short definite
form.
. . 82 01 [2] <1 >

01
Encoding the first element in the SET of the raster-gr-coding-attributes,

compression, results in the eighth and ninth entry '8201 01 '. The '82'
stipulates a context-specific (10) primitive (0) transfer value
,
for compression (00010), tag [2]. The length of '01' indicates that
the following transfer value is contained within the one octet.
The transfer value, '01', is an integer value of one to indicate
compression. This means that the encoded data is compressed and that
the T.6 escape mechanism is not permitted, which is the default
value. As stated earlier in this document, this attribute may be
used by AIIM but is not used by DoD.
. . 80 02 [0] <2>
09 f6
Encoding the second element in the SET of the raster-gr-coding-attributes,

results in the tenth and eleventh entry '80 02' and
number-of-pels-per-line ,
'09f6', respectively. The '80' stipulates a context-specific (10),

primitive (0) transfer value for number-of-pels-per-line (00000) tag [01.
, ,
The length of '02' indicates that the following transfer value is

contained within two octets. The transfer value, '09 f6', is an
integer value of 2,550 for the number-of-pels-per-line.
. . 81 02 [1] <2>
Oc e4
Encoding the third element in the SET of the raster-gr-coding-attributes,

results in the twelfth and thirteenth entry '81 02' and
number-of-lines,
'0ce4', respectively. The '81' stipulates a context-specific (10),
primitive (0) transfer value for number-of-lines (00001) tag [1]. The
, ,
61
.
length of '02' indicates that the following transfer value is

contained within two octets. The transfer value, '0ce4', is an
integer value of 3,300 for the number-of-lines
. 04 82 31 f8 [UNIV 4] <12792>
Encoding the second element in the SEQUENCE of the Text-Unit, content-

results in the fourteenth and last entry, '04 82 31 f8', the
information,
raster data. The '04' stipulates a universal type (00) primitive
,
(0) transfer value having tag number (00100)

, . The resulting
encoding is a primitive type, universal 4 which indicates an octet
string, one-octet-string. The length of the transfer value, '82 31 f8',
is 12,792 octets shown in the long definite form. Following the
'8231 f8' is 12,792 octets of CCITT T.6 encoded-MSB data which was
previously stipulated by the type-of-coding attribute.
If you compare the encoding example discussed above with a complete

example in the appendices, you will find that tag identifiers, such
as 'a2' and 'a3', may occur several times in the data stream. They
have a common characteristic in that they are context-specific tag
identifiers. This is valid because the tag identifiers are located
in a different area of the data stream. This illustrates why the
term "context-specific" is used to describe a type of tag. This
context sensitivity means that another object of a completely
different type may also have the same tag, but one can tell them
apart because both will never appear in the same context.
The above example could have been encoded using the indefinite
length encoding of the ASN.l Basic Encoding Rules. The following
encoding illustrates that the content-portion may be encoded as 'a3 80' .
The '80' with the first bit a one and the remaining seven bits a
zero indicate indefinite length. The content-information encoded as '04
80' also illustrates indefinite length encoding. For every
occurrence of an indefinite length encoding, there must be a
corresponding pair of octets containing zeros to terminate the
encoding. Therefore at the end of the encoding, there are four
octets of zeros, the first pair indicate the end of the content-
information and the second pair indicate the end of the content-portion.
62
<12832>
a3 80 [3] constr < Indefinite length >
. 31 1e [UNIV 17] constr <30>
. . 40 09 [APPL 0] <9>
31 20 30 20 30 20 30 20 30
. . 86 04 [6] <4>
58 03 07 06
. . a2 Ob [2] constr <11>
. . . 82 01 [2] <1 >
01
. . . 80 02 [01 <2>
09 f6
. . . 81 02 [1] <2>
Oc e4
. 04 80 [UNIV 4] < Indefinite length >
12792
-- octets of compressed data (T.6 encoded - MSB)
. 00 00
00 00
63
11 Technical Concepts
This section discusses questions likely to arise in the minds of
implementors in the course of reading the ODA Raster DAP. Much of
the explanation given in this section would have been inappropriate
to include in the DAP, which is intended to be brief.
11.1 Raster Graphics Basics

Raster graphics provides the capability to process, store, and
exchange images in a digital format. This technology plays a
significant role in systems development as we move toward the
elusive goal of the paperless office and work environment.
Raster graphics has been used for several years to exchange

documents by facsimile. Currently, elements of the Department of
Defense (DoD) are using this technology to store and exchange
engineering documents. Similarly, the Patent Trademark Office
digitizes and stores patents using raster graphics, thus making
them available for on-line review. Organizations are also using
this technology to store and retrieve scanned office documents.
Raster graphics technology is absolutely necessary for applications
that interchange and store pictorial data such as photographs and
logos
Raster graphics is a method of representing a two-dimensional image

by dividing it into a rectangular two-dimensional array of picture
elements (pels) . Each element of the pel array comprises data
indicating the color and the brightness of the corresponding
picture element of the image. To produce a raster image from an
existing document, the hard copy paper or microfilm media must be
processed through a raster scanning device.
The data which determines the image of a pel specifies one of two
states, named "set" and "unset." The set state is used to identify
the foreground color and the unset to identify the background
color. In black and white images, the foreground is represented by
a "1" and background by a "0." For reproduction on paper, the
background color will normally be white and the foreground color
black. The array is often referred to as the bitmap image.
In the electronic data capture and conversion of existing images to

digital form by an optical scan process, the scanner superimposes
an imaginary grid or raster over the image to be scanned. Each of
the grid squares represents an individual pel in the pel-array.
Scanning is performed from left to right along each line beginning
at the top of the page. The scanner evaluates each pel and assigns
a corresponding binary value of "0" for mostly white or "1" for
mostly black.
64
Technical Concepts
Figure 12 - The Raster Scan Process
NOTE: The boundary of each pel is directly adjacent to its

neighboring pel without any space between them.
The dimensions of the array or bitmap are determined by the size of

the document or image being represented. The image detail that can
be illustrated is dependent upon the resolution density of the
raster grid. The resolution density is the specific number of pels
per inch which is normally the same for both directions of the
image dimensions. Image detail can be improved by increasing the
grid density but this also increases the storage and data
processing requirements. Consequently, there is a trade-off
between the image detail required for the application and the costs
associated with the higher density requirements.
One of the costlier aspects of raster graphics processing is the

large amount of data generated by the process. For example, the
actual letters "Me," as illustrated in figure 12, require only 16
bits, or two bytes, to represent using ASCII character coding.
65
Technical Concepts
000000000000000000000000000000000000000000
000000000000000000000000000000000000000000
000000000000000000000000000000000000000000
000000000000000000000000000000000000000000
000011100000000001110000000000000000000000
000011100000000011110000000000000000000000
000011110000000011110000000000000000000000
000011110000000111110000000000000000000000
000011110000000111100000000000000000000000
000011111000000111100000000000000000000000
000011111000001111100000000011111110000000
000011001100001101100000000111111111000000
000011001100001101100000001111000111100000
000011001110011001100000011110000011110000
000011001111111001100000011100000001110000
000011000111110001100000011100000001110000
000011000111110001100000111100000001110000
000011000011100001100000111111111111110000
000011000001100001100000111111111111110000
000011000000000001100000111000000000000000
000011000000000001100000111000000000000000
000011000000000001100000011000000000000000
000011000000000001100000011100000000110000
000011100000000011100000001111000001110000
000011100000000011110000000111111111100000
000011100000000011100000000011111110000000
000000000000000000000000000001110000000000
000000000000000000000000000000000000000000
000000000000000000000000000000000000000000
000000000000000000000000000000000000000000
Figure 13 - Raster Data
The bitmap image, as shown in figure 13, requires a total of 1260

bits, or 158 bytes, to represent these same two letters in a raster
image format. To help reduce the storage requirements, there have
been several encoding schemes developed to compress raster data.
In the world of facsimile transmission, the CCITT Recommendation
T.4 (Group 3) is currently used for compressing the documents
during transmission. It is anticipated that future systems will
66
Technical Concepts
use the CCITT Recommendation T.6 (Group 4) compression algorithm.

DoD Military Standard 184 0 stipulates the use of CCITT
Recommendation T.6 (Group 4) as the DoD standard to be used for the
interchange of raster data between DoD installations and their
vendors. Compression ratios can typically range from 10:1 to 50:1
depending upon the complexity of the image.
Raster graphics images can be integrated into office documents
through the use of IS 8613, Office Document Architecture (ODA) and
Interchange Format. ODA provides for open interchange of
structured compound documents containing text, vector graphics and
raster graphics. It provides the rules for partitioning and
organizing (structuring) the document and the encodings for this
structure using ASN.l.
ODA also provides a scheme for subdividing a large raster graphics

image into non-overlapping regions called tiles. This scheme
provides a format that supports operations on portions of a large
image without requiring other portions of the image to be accessed.
It also allows parallel compression and decompression of the
individual tiles.
11.2 Encoders and Decoders
It is worth noting that encoders (writers) and decoders (readers)

of ODA Raster DAP files have differing needs for generality.
Programs which create ODA Raster DAP files may be relatively simple
because they may be hard-coded to produce a specific file that
meets the specifications of the contract and that still remains
compliant with the document application profile (DAP). This allows
a simpler conversion of data out of a given system format for
export to other organizations.
For example, encoding programs may use definite or indefinite

length encoding, may or may not include the optional tile index,
may or may not zero out unused portions of partial tiles, may or
may not create documents with sizes divisible by eight, etc.
Writers may freely rely on default values for as many parameters as
they are allowed according to the DAP.
Programs decoding ODA Raster DAP files must be more general in that
they must be prepared to receive data from a wide range of writers,
each of which is producing files in the manner simplest for them.
11.3 Converters Versus Native Systems
Systems that store data internally in a format close to that of an

ODA document are called native systems. There is some advantage to
67
.
Technical Concepts
having a native system, although differing implementation

requirements may make it impractical in many cases.
Non-native systems must implement file converters for translation
of interchanged documents. This can add some overhead at import
and export time.
11.4 Bit Order
The proper ordering of bits within bytes (octets) is a subject of

industry-wide dispute. The traditional method in facsimile
equipment for compressed data is to pack code bits into bytes in up
fashion, that is, least significant bit (LSB) to most significant
bit (MSB) . The most widespread method used in sending bitmapped
(uncompressed) data to computer display adapters is with a down
ordering (MSB to LSB) . This MSB to LSB bit ordering has also
become a common representation for compressed data in many PC and
workstation implementations.
A Proposed Technical Corrigendum (PTC) Number 47 to ISO/IEC
JTC1/SC18/WG3 proposed that additional type of coding attribute
values be added to CCITT Recommendation T.417 and ISO 8613-7. This
change would allow support in either bit order sequence. The PTC
was approved by CCITT but not by ISO. However, the revised text
will appear in the joint publication of CCITT Rec. 417 ISO 8613-7
|
with a note that it is approved only for CCITT. The consequence of

this is that the DAPs may refer to the CCITT Recommendation T.417
instead of ISO 8613-7. Thus, the indication of this as being for
CCITT only has no effect on current implementations. PAGODA has
asked that ISO review its position and approve the PTC 47 before
publication of the joint document.
In the design process, it might be prudent to plan for reading both

compressed bit orderings, especially if such support comes more
cheaply during the early development phases.
11.5 Padding/Byte Boundaries
Some systems may derive efficiencies from handling documents which

have sizes which are multiples of eight. MIL-R-28002B requires an
encoding program to export documents having such sizes.
Decoding programs may be required by contract to import documents

from other systems which allow for arbitrary dimensions. They may
do this either natively, or by padding out lines with zeros to
dimensions which are multiples of eight, or by truncation (since it
is unlikely that this will lose significant data)
68
Technical Concepts
A related issue is whether compressed data has byte boundary

constraints. The T.6 standard assumes that a T.6 compressed data
block will have zeros (called pad bits) placed after the valid bits
in the last, partial byte. The next data item begins on a byte
boundary. Byte boundaries are a major issue only for T.4
compression, which is not permitted under MIL-R-28002B.
11.6 Partial tiles
In ODA Raster DAP tiled files, a document's size along either

dimension will generally not be a multiple of 512 pels. This means
that some unused data can exist in tiles around any or all of the
document's four edges. In IS 8613 Part 7, this unused data is not
considered to be information. Please refer to figure 14.
Decoding programs should therefore behave as if garbage data will
exist in those pels and guard against its presentation.
Unless specified in the DoD contract that the un-imaged pels be set
to background, encoding programs have the option of leaving garbage
in those pels or zeroing them out prior to compression. It is
understood that compression will improve if zeros are in the unused
portion of the tile.
It is further understood that some systems may get a needed price

or performance benefit from not zeroing that data. For example, at
a quality assurance (QA) workstation, an operator may perform
dynamic clipping of scans of poorly registered aperture cards.
Leaving garbage in the partial tiles and simply changing the
clipping parameters in the file would avoid having to recompress
the peripheral tiles.
Referring again to figure 14, we notice it shows only one band of

partial tiles around the periphery of the tile grid. This is
because the tiling offset measure pair coordinates must be less
than or equal to 512.
What is particularly useful is the clipping function illustrated in

figure 14. This feature allows an intelligent scanning subsystem
to identify the borders of the "good" region of the scan and merely
paste the appropriate clipping coordinate pairs into the file. It
does not need to recompress the tiles to remove the trimmed areas.
11.7 Tile Ordering
During interchange, the tiles must appear in the file in an order

which is primarily along the pel path direction and secondarily
along the line progression direction.
69
Technical Concepts
Many systems have to internally store tiles in random order because

the tiles leave parallelized hardware in unpredictable order or
because a series of tile-local editing sessions have occurred. At
interchange time, however, these tiles must be properly ordered.
11.8 Orientation
For ODA Raster DAP documents, the manner in which the ODA raster
architecture deals with orientation requires the use of two
attributes, pel path and line progression. The pel path and line
70
Technical Concepts
progression directions specified for the document at interchange

time guide the reader during the imaging process. To get proper
viewing, a reader will take pels from a compressed or uncompressed
data stream (file) and place them on the screen or paper in the
directions indicated. The decoding program will lay down the first
line of pels along the pel path direction and the second line along
a path parallel to the first, but displaced from it along the line
progression direction.
The decoding system knows its own requirements. If the target
device is a display, the pels may be placed in memory in one
organization. If the target device is a narrow printer, the pels
may be placed in memory by the decoding program in a different way.
The point is that the orientation parameters found in the file are
purely descriptive, not prescriptive.
The pel path direction may have any of four values and the line
progression direction can be at either of the two possible right
angles to it. Therefore, this model can describe images which are
not only rotated, but also mirrored either vertically and/or
horizontally. This allows the orientation parameters to describe
how to image a file which might have resulted from scanning the
back side of an aperture card or paper sepia. This procedure might
have been done in order to improve image quality.
Refer to figures 15 and 16 for an illustration of the possible

orientations.
If a mix of scans is done as a batch and the file writer assumes

all of the scans have a certain orientation when in fact they do
not, then a QA post-process will be necessary. The QA operator
would view each scan, check its quality, perhaps perform a clipping
operation, and then identify which direction would be "up" for
proper viewing orientation. The orientation parameters would end
up in the file, which until that point would have had incorrect
orientation parameters. No other changes or actual rotation would
be required.
It is worth noting that the DAP requires all tiles to have the same
orientation.
71
Technical Concepts
Figure 15 - Position of Pels, Portrait Document
4
ALL FED TTH POLICE SCANNER
IN THIS DIRECTION
Pel Path = 270

270 o
N.
= CM
Progression
Vi
Vi
2
?
0.
Line o
c
270
Progression
Line
Note 1: The pel path direction is measured in degrees

counterclockwise from the positive horizontal axis (east).
Note 2: The line progression direction is measured in degrees

counterclockwise from the pel path direction.
72
Technical Concepts
Figure 16 - Position of Pels, Landscape Document
ALL FED IHROUQH SCANNER

IN THIS DIRECTION
Pel Path = 90
Pel Path = 0
270
Progression
Line
270
Progression
Line U.
Note 1: The pel path direction is measured in degrees

counterclockwise from the positive horizontal axis (east).
Note 2: The line progression direction is measured in degrees

counterclockwise from the pel path direction.
73
Technical Concepts
11.9 Rotation to Proper Viewing Orientation

MIL-R-28002B allows the contract to optionally specify that all
documents be rotated where necessary to achieve proper viewing
orientation with pel path direction set to 0 and line progression
direction set to 270. If this option has been specified, the QA
process described above would require an additional step of
rotating any document which was improperly scanned. This
contracting option would be specified in systems where the viewing
subsystem is not powerful enough to perform at display time any
rotation which may be required because of earlier
random-orientation scanning.
11.10 Uncompressed Bit Sense
Raster data represents each pel in the source document by a zero or

a one. Differing conventions exist in industry as to whether a one
represents a light or a dark picture element. The situation is
further confused by the existence of both photographic positive and
photographic negative source documents, ,
aperture cards,
blueprints, blue lines.
MIL-R-28002B states that an uncompressed image or tile shall

represent the "information" in a source document by one bits and
the "background" by zero bits. The "information" pels in an image
are those which make it differ from a blank image. Such pels are
typically (though not necessarily) grouped into run lengths shorter
(on average) than are "background" pels.
This representation assures harmony with T.6 encoding when such

images or tiles are later compressed. T.6 coding best compresses
short runs of ones and longer runs of zeros.
In T.6, the correct use of ones and zeros in compressed data is not
open to confusion. It specifies the coding unambiguously.
11.11 Database Issues
In ODA Raster DAP files, a document may contain multiple pages (as
pages are defined within ODA) . These pages may contain several
images of a multiple frame aperture card. They may also contain
the original image and a scaled down overview image. In this
latter case, the main image appears as the first page. The sheets
of a multiple sheet paper drawing or multiple card aperture card
drawing may also appear as pages within the same document. This
requires a prior agreement between the exchanging parties or in the
contracting document. This agreement identifies the allowed uses
of this mechanism and how these uses are to be distinguished from
each other.
74
Technical Concepts
11.12 Definite Versus Indefinite Length
When encoding various data objects in ASN.l, a choice exists

between using definite length encoding and indefinite length
encoding.
Definite length encoding has an explicit length specified for an

object. This applies to the entire containing object, even if it
is constructed of many smaller objects. A reader that may be
uninterested in the internal details of the object can safely skip
ahead a known number of bytes.
This will not work for writers. A writer must have foreknowledge
of the size of the entire object before even writing out any of its
contained objects, which may themselves have variable sizes. An
enormous stack may be required in order to buffer pending objects.
This contrasts with indefinite length encoding, where an explicit

length is not given. Instead, a flag indicates the end of the
object. A reader is then required to parse all the contained
objects in order to not miss the flag. This slows down readers.
It does, however, remove the need for a writer to have a large
stack as described above. This becomes particularly important when
creating interchange files containing tiled raster data. It may be
more advantageous for the creator to use indefinite length encoding
for the content-portion and the content-information (see Appendices D and E)
.
11.13 Basic Versus Non-basic Versus Default Values
Basic values are those commonly used values that may be placed by
encoders into a parameter without any explicit statement of the
intent to do so. Decoders are expected to be able to deal with all
basic values.
Non-basic values are non-commonly used values which may appear in

the associated parameter and must be called out by encoding
programs in a section near the beginning of the document (document
profile) well before they are used. This allows decoding programs
,
to quickly discern if they are able to process the file. The

non-basic values are specified in the non-basic document
characteristics portion of the document profile (see ODA
Constituents and Attributes, section 8, and ASN.l Definitions,
Appendix A) .Decoders may not be able to support non-basic values;
however, ISO encourages implementors to support both basic and non-
basic values.
A value not listed as basic or non-basic is not permitted, unless

it occurs via a default. This is not always as restrictive as it
—
might seem {ANY_VALUE} is sometimes listed as non-basic.
75
Technical Concepts
The defaulting mechanism operates as follows. If a parameter is

not specified where it occurs, the parameter assumes the
corresponding value specified for an object up in the hierarchy of
objects. These defaults, if not stated in the document profile,
are found in IS 8613.
For example, the presentation attribute, pel spacing, has a default

value in ISO 8613-7 of 4/1 BMUs (300 DPI) If not specified
.
anywhere in the data stream, then the '4/1' BMU value is used.
However, it could be specified in several different manners in the
data stream, that is, directly in the presentation attributes of a
specific block, in a presentation style which is referenced by a
specific block, or in the raster graphics content defaults of the
document profile. If the attribute is specified in the
presentation attributes of a specific block, then that value will
be used regardless of any referenced presentation styles or of an
entry in the document profile. If the attribute is not specified
in the presentation attributes of a specific block, then an
implementor must look for the possibility of it being specified in
a presentation style that is referenced by the specific block. If
it doesn't exist here, then the defaults in the document profile
are evaluated for a pel spacing entry. If it is not present in the
document profile, then the IS 8613 default of '4/1' is used.
11.14 Null Tiles
Each tile in a ODA Raster DAP file may be of a different type. It

may be a T.6 encoded, T.6 encoded-MSB, bitmap, null foreground, or
null background tile. A tile that has a tile type of "null
background" will have a null pointer in the tile index, if the tile
index is present, and will be imaged as background without a need
—
to draw raster content from the file in fact it has none.
11.15 Presentation Styles
There are two alternatives for designating the proper presentation

attributes which are to be used in presenting raster graphics
information on a page. These attributes include pel path, line
progression, clipping, and pel spacing. As can be seen in the
ASN.l Definitions (Appendix A), the presentation attributes are
used to describe the Layout-Object-Description-Body; in our case, the layout
object is the specific block. One alternative is to assign the
presentation attributes (with a tag of 6) directly to the specific
block.
A second alternative is to use a presentation style (having a tag

of 17) . Of course, if all the ODA default values are used, then no
presentation attributes will have to be designated at all. The
default values for these attributes are a pel path of 0 degrees, a
76
Technical Concepts
line progression of 270 degrees, a pel spacing of 4 BMUs (300 dpi) ,
and a clipping rectangle marked by the two points (0,0; N-1,L-1).

N is the number of pels per line and L is the number of lines.
If a document consists of only a single page or if a document has

multiple pages each with one unique presentation attribute
requirement, then the presentation attributes, if required, may be
assigned directly to the specific block. The presentation style
constituent need not be used.
If, on the other hand, a document consists of multiple pages with
several pages sharing the same presentation attribute description
(same pel path, line progression, etc.), then it may be more
practical to use the presentation style constituent.
The use of presentation style is illustrated in Appendix F. Note
that the style-identifier in the interchange data element for presentation
style is '5 0' and that the presentation-style attribute in interchange
data element for document layout block contains a value of '50'.
This identifier serves as a linking mechanism between the
presentation style constituent and the appropriate specific block
constituent. If the document illustrated had many pages, all
consisting of the same presentation characteristics, then all of
the additional block descriptions would reference the same
presentation style of '50'.
If a document consisted of many pages with three different

presentation styles, then there would have to be a presentation
style described for each: the first with a style-identifier of '50', the
second with '51', and the third with '52'. Then each block would
reference the appropriate presentation style with its presentation-style
attribute containing either '50', '51', or '52'.
In a multiple page document, the use of presentation styles allows

the user to define a set of presentation styles with each one being
unique. Then a block description refers to the appropriate
presentation style. If styles are not used, then the presentation
attributes would have to be repeated on every page even though they
may contain identical descriptions.
77
.
12 Tools
12 . 1 ODA Toolkit
An ODA toolkit is available from the ODA Consortium. The toolkit
is designed to aid in the development of ODA applications.
The ODA toolkit is new technology that could speed the development
of computer applications that promote the electronic interchange of
documents among different computer systems throughout the world.
The technology involves Application Programming Interfaces (APIs)
that the ODA Consortium includes in the toolkit. The toolkit is
software with consistent, published specifications that is openly
licensed to companies.
The ODA Consortium now has defined an ODA-Level API which provides
common services that define how data is stored and structured so it
can be formatted efficiently into a document. It also has defined
a DAP-Level API that helps structure documents according to well
defined ODA functional subsets.
More information can be obtained by writing to the: The Secretary,

ODA Consortium, Avenue Marcel Thiry 204, 1200 Brussels, Belgium.
12.2 The ISO Development Environment (ISODE)
An ASN.l tool that is publicly available exists within the ISO

Development Environment (ISODE) ISODE can be used to generate
.
routines to encode and decode structures given the ASN.l

definitions as input. Although ISODE is an openly available
implementation of the upper-layers of Open Systems Interconnection
(OSI) it is primarily a development environment.
, As such, it
contains many tools and libraries to aid the application
development process. Section 4 of the User's Manual, "The
Applications Cookbook" [18], has several ASN.l abstract syntax and
transfer notation tools for development of ASN.l based
applications
It should be noted that this tool would primarily benefit the

applications developer. ISODE need not be installed prior to use
of this tool, only the specific programs for processing the ASN.l
Definitions.
ISODE is publicly available. To access the files, log onto a

system with access to Internet and FTP software. The host is:
uu.psi.com. The file isode/ isode-8 tar should be retrieved in
.
BINARY mode.
78
. .
Tools
12.3 Free Value tool, ASN.l Compilers
The Free Value Tool is a set of development tools for working with
ASN.l defined protocols or profiles. It can improve the
programmer's understanding of ASN.l syntax by allowing parsing,
transformation of profile structures into actual C language data
structures, and conversions into and out of transfer format.
Because it is highly general, it is not suited to production
implementations
The term "free value" comes from the fact that the result of
running the tool is not a particular representation of one
document, but rather a set of data structures and operations
capable of properly encoding any of the defined class of documents.
The variables of the data structure are "free" to assume any one
value out of the allowed range of values.
The Free Value tool comes as part of the OSIkit which is a

collection of tools for the application of Estelle and ASN.l that
were developed by NIST. Documents for these tools are distributed
by the National Technical Information Service (NTIS) of the U.S.
Department of Commerce. This software is not supported. The
manual with the Free Value tool [7] (which is also available
without the program) contains a valuable introduction to ASN.l
notation.
ASN.l compilers are also available commercially from several

vendors
79
.
13 Glossary
All definitions are taken from IS 8 613, Part 1 , except where
otherwise specified.
Attribute An element of a constituent of a document that has a

.
name and a value and that expresses a characteristic of the

constituent or a relationship with one or more constituents of the
document
Basic value An attribute value that is unconditionally allowed in
.
document interchange in the context of a given application profile.

Bitmap . A two- or three-dimensional data field representing a pel
array.
Block. A basic layout object that corresponds to a rectangular

area within a frame and consisting of only a single type of
content, i.e., raster graphics content.
Clipping The actual pel array to be imaged as determined by

.
applying all clipping parameters.

Constituent A set of attributes that is one of the following
.
types: a document profile, an object description, a presentation

style, a layout style, or a content portion description.
Composite page A page that is subdivided into subordinate frames

.
consisting of blocks.
Compression An operation performed on raster image data to remove
.
redundant information and thus reduce the stored or interchanged

size. Negative compression is the case where this operation
results in an increase rather than a decrease in size.
Constraints Restriction conditions that are placed upon the use
.
of attributes within constituents.
Document Application Profile (DAP) The specification of a

.
combination of features defined in IS 8613, intended to form a

subset to fulfil the requirements of an application.
Decoding The process of parsing a file, extracting content

.
information, and deriving a bitmap from an octet string by

translating any compression algorithm used to create the octet
string.
Default value An attribute value that is the standard value in

.
the document interchange in the context of a given application

profile.
80
. .
Glossary
Document profile A set of attributes

. which specifies the
characteristics of the document as a whole.
Document layout root The composite object of the specific layout
.
structure at the highest level of the hierarchy.
Encoding The process of deriving compressed data from a bitmap by

.
applying a compression algorithm to the bitmap.

Formatted document architecture A form of representation of a
.
document that allows the presentation of the document as intended

by the originator and that does not support editing and
(re) formatting.
Formatted processable content architecture This is intended to be

.
laid out, reformatted and imaged by the recipient in accordance

with the originator's intent. (Part 7)
Frame. A type of composite layout object that corresponds to a

rectangular area within a page.
Image Frame A frame used in the context of the ODA Raster DAP
where the frame is coincident with the page.
Layout characteristics The attributes which guide the layout
.
structure of a layout object.

Line progression direction The direction of progression
. of
successive lines of pels within a basic layout object.
Non-basic value An attribute value that is only allowed in

.
document interchange in the context of a given application profile

if its use is declared in the document profile.
Octet A subdivision of eight bits numbered from 8 to 1 where bit

.
8 is the most significant bit and bit 1 is the least significant

bit. (Also known as a byte.)
Page .A type of layout object that corresponds to a rectangular

area used as a reference area for presenting the content of the
document
Partial tiles In a tiled image of a document, the incomplete
.
tiles which may occur on any or all of the four sides of the tile
array when the image has been positioned and clipped. Also known
as runt tiles.
Pel (picture element) The smallest graphic element that can be

.
individually addressed within a picture. Synonymous with pixel.
81
Glossary
Pel array. A two-dimensional array of pels used to represent a

pictorial image.
Pel path direction The direction of progression of successive
.
pels along a line within the basic layout object.
Pel spacing The distance between any two successive pels along a
.
scan line of an image. It is the inverse of such often used terms

as pel density, transmission density, or resolution.
Presentation attributes Attributes which guide the format and

.
appearance of an object's content.
Presentation style A constituent of the document, referred to

.
from a basic logical or layout component, which guides the format

and appearance of the document content.
Raster graphics The electronic data processing medium used to

.
depict any arbitrary assemblage of text characters, graphical

figures, or pictorial images with a pel array.
Raster graphics content The raster graphics portion of a document

.
that is intended for human perception.
Spacing ratio . The ratio of line spacing to pel spacing.
Specific Block . A block used in the context of the ODA Raster DAP.
Tile. A rectangular region in a layout object in which all such

regions have the same dimensions, no part of any region overlaps
any other region, and regions are positioned in a fixed grid,
determined by partitioning the layout object into region-sized
areas.
Tile index An application comment in ODA Raster DAP files which

.
contains a list of byte offsets from the beginning of the content

information (first tile) to the beginning of each tile in the page.
82
14 References
1. ANSI/AIIM MS-53 (Proposed), Bi-Level Image File Format Level 1.1

(All), 199X.
2. Appelt, Wolfgang, Document Architecture in Open Systems, The ODA

Standard, Springer-Verlag, New York, 1991.
3. CCITT Recommendation T.503, Document Application Profile for the

Interchange of Group 4 Facsimile Documents, 1984.
4. CCITT Recommendation T.6, Facsimile Coding Schemes and Coding

Control Functions for Group 4 Facsimile Apparatus, 1988.
5. Dawson, F., and F. Nielsen, 1990, ODA and Document Interchange,

Unix Review, vol.8, no. 3, March 1990, p.50.
6. FIPS PUB 150, Telecommunications: Facsimile Coding Schemes and

Coding Control Functions for Group 4 Facsimile Apparatus, 4
November 1988.
7. Gaudette, P. S. Trus, and S. Collins, 1989, The Free Value Tool
,
for ASN.l, Technical Report NCSL/SNA-89/ 1 National Computer

,
Systems Laboratory, National Institute of Standards and Technology,

Gaithersburg, MD 20899, February 1989.
8. Hobgood, A., CALS Implementation — Still a Few Questions,

Advanced Imaging, April 1990, pp 24-5.
9. IS 8613-1, Information processing - Text and office systems -
Open Document Architecture (ODA) and interchange format - Part 1:
Introduction and General Principles, 1989.
10. IS 8613-2, Information processing - Text and office systems -

Document structures, 1989.
11. Information processing - Text and office systems -

IS 8613-4,
Document profile, 1989.
12. Information processing - Text and office systems -

IS 8613-5,
Office Document Interchange Format (ODIF) 1989.
,
13. systems -
IS 8613-7, Information processing - Text and office
Open Document Architecture (ODA) and interchange format Part 7:-
Raster Graphics Content Architectures, 1989.
14. IS 8613-7 Addendum, Information processing - Text and office

systems - Open Document Architecture (ODA) and interchange format
83
References
- Part 7 Raster Graphics Content Architectures Tiled

: Raster
Graphics Addendum (ISO SC18 WG5 Draft Addendum), 1990.
15. IS 8813-7 Addendum,Information processing - Text and office

systems -Open Document Architecture (ODA) and interchange format -
Part 7: Raster Graphics Content Architectures Additional Bit Order
Mapping Addendum, Proposed Technical Corrigendum (PTC) Number 47,
ISO/IEC JTC 1/WG 3, dated July 1991.
16. IS 8824, Information processing-Open Systems Interconnection -

Specification of Abstract Syntax Notation One (ASN.l), 1987.
17. IS 8825, Information processing-Open Systems Interconnection -
Specification of basic encoding rules for Abstract Syntax Notation
One (ASN.l), 1987.
18. ISO Development Environment; User's Manual, Volume 4: The

Applications Cookbook, August 12, 1988.
19. MIL-R-28002B, Military Specification, Requirements for Raster
Graphics Representation in Binary Format, November 1992.
20. MIL-STD-1840B, Military Standard, Automated Interchange of

Technical Information, 3 November 1992.
21. NIST Special Publication 500-192, Government Open Systems

Interconnection Profile Users' Guide, Version 2, October 1991.
22. NIST Special Publication 500-206, Stable Implementation

Agreements for Open Systems Interconnection Protocols, Version 6,
Edition 1, December 1992.
23. Rose, M.T. The Open Book: A Practical Perspective on OSI,

,
Prentice Hall, Englewood Cliffs, NJ. 1990.

,
24. Sharpe, L. Tiling; Turning Unwieldy Drawings into Neat Little

,
Packets, Inform, Association for Image and Information Management,

March 1989.
84
Appendix A ASN.1 Definitions
This appendix contains the complete listing of the ASN.l

Definitions of an implementation of the ODA Raster DAP. The ASN.l
Definitions are defined in a single module referred to as "Raster
Interchange Format (RIF) Module."
The ASN.l Definitions are a subset of the ODA ASN.l Definitions

defined in IS 8613-5, IS 8613-7, and the Addenda to IS 8613-7.
These definitions were developed by the National Institute of
Standards and Technology using the Free Value tool. Some
constructions which may seem peculiar exist in order to work around
limitations in those tools such as their lack of support for
macros. For example, if macros were available to process object
identifiers, the commented-out line " --{ 2 8 2 7 2 } " found below
could have been properly pasted in without the use of a comment.
The files used in constructing the examples illustrated in the

appendices of this document are publicly available via anonymous
FTP on the Internet. The files are on speckle.ncsl.nist.gov in the
directory /pub/oda_raster
**'W*****************************'**
— * Interchange Data Element * —
” * ASN.l Definitions for Raster Interchange Format (RIF) * -
Rif-Module
DEFINITIONS :: =
BEGIN
Interchange-Data-Element :: = CHOICE {
document-profile [01 IMPLICIT Document-Profile-Descriptor,
}
DOCUMENT PROFILE DESCRIPTOR *************** ..
Document-Profile-Descriptor ::= SET {

specific-layout-structure [1] IMPLICIT NumericString OPTIONAL,
document-characteristics [2] IMPLICIT Document-Characteristics OPTIONAL,
document-management-attributes [3] IMPLICIT Document-Management-Attributes
OPTIONAL,
presentation-styles [6] IMPLICIT NumericString OPTIONAL
}
85
Appendix A - ASN . 1 Definitions
Document-Characteristics ::= SET{

document-architecture-class [1] IMPLICIT INTEGER {
formatted (0)}
OPTIONAL,
non-basic-doc-characteristics [2] IMPLICIT Non-Basic-Doc-Characteristics
OPTIONAL,
document-application-profile [4] IMPLICIT OBJECT IDENTIFIER,
-{1314111 1},
content-architecture-classes [5] IMPLICIT SET OF OBJECT IDENTIFIER
OPTIONAL - { 2 8 2 7 2 }-,
- Raster Formatted Processable -
interchange-format-class [6] IMPLICIT INTEGER {if-a (0)}, - Class A -
oda-version [8] IMPLICIT SEQUENCE {
standard Character-Data,
publication-date Date-and-Time) OPTIONAL,
doc-appl-profile-defaults [10] IMPLICIT Doc-Appl-Profile-Defaults
OPTIONAL
}
Doc-Appl-Profile-Defaults SET {
document-architecture-defaults [0] IMPLICIT Document-Architecture-Defaults,

raster-gr-content-defaults [2] IMPLICIT Raster-Gr-Content-Defaults
OPTIONAL
}
Document-Architecture-Defaults SET{
content-architecture-class [0] IMPLICIT Content-Architecture-Class
OPTIONAL,
- {2 8 2 7 2} Raster Formatted Processable -
page-dimensions [2] IMPLICIT Measure-Pair OPTIONAL,
medium-type [6] IMPLICIT Medium-Type OPTIONAL,

page-position [9] IMPLICIT Measure-Pair OPTIONAL,
type-of-coding [10] Type-Of-Coding OPTIONAL
-{2 8370 I
28375 |
2837 6}
- T6 encoding, tiled encoding, OR
- T6 encoding - MSB
- See note under Type-Of-Coding
}
Non-Basic-Doc-Characteristics ::= SET{

page-dimensions [2] IMPLICIT SET OF Dimension-Pair OPTIONAL,
ra-gr-coding-attributes [3] IMPLICIT SET OF Ra-Gr-Coding-Attribute
OPTIONAL,
ra-gr-presentation-features [4] IMPLICIT SET OF Ra-Gr-Presentation-Feature
OPTIONAL,
medium-types [8] IMPLICIT SET OF Medium-Type OPTIONAL
}
86
Document-Management-Attributes ::= SET{

document-description [7] IMPLICIT Document-Description OPTIONAL
}
Document-Description ::= SET{

document-reference [5] Document-Reference OPTIONAL
}
Document-Reference ;:= CHOICE {

unique-reference OBJECT IDENTIFIER,
descriptive-reference Character-Data
}
Character-Data :: = [APPLICATION 3] IMPLICIT OCTET STRING
Date-and-Time :: = [APPLICATION 4] IMPLICIT PrintableString
,_*************** layout OBJECT DESCRIPTOR ***************
Layout-Object-Descriptor SEOUENCE {
object-type Layout-Object-Type OPTIONAL,

descriptor-body Layout-Object-Descriptor-Body OPTIONAL
}
Layout-Object-Type ::= INTEGER {

document-layout-root (0),
page (2),
frame (3),
block (4)
Layout-Object-Descriptor-Body ::= SET{

object-identifier Object-or-Class-ldentifier OPTIONAL,
subordinates [0] IMPLICIT SEQUENCE OF
NumericString OPTIONAL,
content-portions [1] IMPLICIT SEQUENCE OF
NumericString OPTIONAL,
position [3] IMPLICIT Measure-Pair OPTIONAL,
dimensions [4] IMPLICIT Dimension-Pair OPTIONAL,
presentation-attributes [6] IMPLICIT Presentation-Attributes OPTIONAL,
user-readable-comments [8] IMPLICIT Comment-String OPTIONAL,
user-visible-name [14] IMPLICIT Comment- String OPTIONAL,
page-position [15] IMPLICIT Measure-Pair OPTIONAL,
medium-type [16] IMPLICIT Medium-Type OPTIONAL,
presentation-style [17] IMPLICIT Style-Identifier OPTIONAL,
application-comments [25] IMPLICIT OCTET STRING OPTIONAL
” 'application-comments' defined according to IS 8613-5, the ASN.1
87
— type definition for the containing tiling indexes within a block

-- layout object is: 'SEQUENCE OF INTEGER'. See ODA Raster DAP.
}
Object-or-Class-ldentifier :: = [APPLICATION 1] IMPLICIT PrintableString
Style-Identifier :: = [APPLICATION 5] IMPLICIT PrintableString
Comment- String ::= OCTET STRING
Dimension-Pair ::= SEQUENCE {

horizontal [0] IMPLICIT INTEGER,
vertical CHOICE {
fixed [0] IMPLICIT INTEGER,
variable [1] IMPLICIT INTEGER}
}
Medium-Type SEQUENCE!
nominal-page-size Measure-Pair OPTIONAL,
side-of-sheet INTEGER {
unspecified (0),
recto (1 ),
verso (2) }
OPTIONAL
}
*************** presentation STYLE DESCRIPTOR **************
Presentation-Style-Descriptor ::= SET{

style-identifier Style-Identifier,
user-readable-comments [0] IMPLICIT Comment-String OPTIONAL,
user-visible-name [1] IMPLICIT Comment- String OPTIONAL,
presentation-attributes [3] IMPLICIT Presentation-Attributes OPTIONAL
}
Presentation-Attributes ::= SET{

content-architecture-class Content-Architecture-Class OPTIONAL,
raster-graphics-attributes [1] IMPLICIT Raster-Graphics-Attributes
OPTIONAL
}
Content-Architecture-Class OBJECT IDENTIFIER

-{28272} Raster Formatted Processable -
88
** ^*******^****
4
TEXT UNITS *************** „
Text-Unit ::= SEQUENCE {

}

} OPTIONAL }
Content-Portion-Identifier :: = [APPLICATION 0] IMPLICIT PrintableString
Type-Of-Coding CHOICE {

{2 8 3 7 0} 'T6 encoding'
- or (2 8 3 7 1} 'T4 one dimensional encoding'
- or (2 8 3 7 2} 'T4 two dimensional encoding'
- or {2 8 3 7 3} 'bitmap encoding'
- or {2 8 3 7 5} 'tiled encoding'
- or {2 8 3 7 6} 'T6 encoding - MSB'
- or {2 8 3 7 7} 'T4 one dimensional encoding - MSB'
" or (2 8 3 7 8} 'T4 two dimensional encoding - MSB'
}
— CALS supports only the bitmap(28373), tiled(28375), and T6-MSB(28376) encodings.
— AIIM does not support tiled encoding.

— NOTE: Content-Information ::= OCTET STRING is defined in IS 8613-5 (1989),
but an eratta has been submitted to change the description to
a choice to support tiled raster graphics.
Alternative-Representation ::= OCTET STRING
” NOTE: String of characters from the sets designated by the document

profile attribute "alternative representation character sets",
plus carriage return and line feed.
89
1
Appendix A - ASN . Definitions
__ ************** definitions supporting raster graphics ********** ***
- ###### RASTER GRAPHIC PRESENTATION ATTRIBUTES ###### -
Raster-Graphics-Attributes = SET {
pel-path [0] IMPLICIT One-Of-Four-Angles OPTIONAL,
line-progression [1] IMPLICIT One-Of-Two-Angles OPTIONAL,
clipping [4] IMPLICIT Clipping OPTIONAL,
pel-spacing [5] Pel-Spacing OPTIONAL,
spacing-ratio [6] IMPLICIT Spacing-Ratio OPTIONAL
}
One-Of-Four-Angles INTEGER {
dO (0), - 0 degrees
d90 (1 ), - 90 degrees
d180 (2), - 180 degrees
d270 (3) - 270 degrees
}
One-Of-T wo-Angles ::= INTEGER {

d90 (1), - 0 degrees
d270 (3) -270 degrees
}
Measure-Pair ::= SEOUENCE {
horizontal [0] IMPLICIT INTEGER,

vertical [0] IMPLICIT INTEGER
}
Clipping ::= SEOUENCE {
first-coordinate-pair [0] IMPLICIT Coordinate-Pair OPTIONAL,

second-coordinate-pair [1] IMPLICIT Coordinate-Pair OPTIONAL
}
Coordinate-Pair SEOUENCE {
x-coordinate INTEGER,
y-coordinate INTEGER
}
Pel-Spacing ::= CHOICE {
spacing [0] IMPLICIT SEOUENCE {
length INTEGER,
pel-spaces INTEGER },
null [1] IMPLICIT NULL

- [1] null not supported
}
Spacing-Ratio SEOUENCE {
line-spacing-value INTEGER,
90
pel-spacing-value INTEGER
}
- ###### RASTER GRAPHICS CODING ATTRIBUTES ###### -
Raster-Gr-Coding-Attributes ::= SET{

" number-of-pels-per-tile-line [6] IMPLICIT INTEGER OPTIONAL,

number-of-pels-per-tile-line isalways a constant 512

}
Tile-Type ::= INTEGER {

encoded-t6 (2),
bitmap (5),
encoded-t6-msb (6)
}
Ra-Gr-Coding-Attribute ::= CHOICE {

compression [0] IMPLICIT Compression
}
- The tag value used above preserves compatibility with Group 4
- Class 1 facsimile data streams.
Compression ::= INTEGER {uncompressed (0), compressed (1)}

- The 'Compression' attribute is supported by AIIM but not by CALS.
” CALS data streams always uses the default value of 'compressed'.
“ It is not supported by CALS.
- ###### RASTER GRAPHICS PRESENTATION FEATURES ###### -
Ra-Gr-Presentation-Feature ::= CHOICE {
pel-spacing [5] Pel-Spacing,

spacing-ratio [6] IMPLICIT Spacing-Ratio,
pel-path [9] IMPLICIT One-Of-Four-Angles,
line-progression [10] IMPLICIT One-Of-Two-Angles
}
91
Appendix A ASN . 1 Definitions
- ###### RASTER GRAPHICS CONTENT DEFAULTS ###### -
Raster-Gr-Content-Defaults SET {
pel-path [0] IMPLICIT One-Of-Four-Angles OPTIONAL,
line-progression [1] IMPLICIT One-Of-Two-Angles OPTIONAL,
pel-spacing [5] Pel-Spacing OPTIONAL,
spacing-ratio [6] IMPLICIT Spacing-Ratio OPTIONAL,
compression [8] IMPLICIT Compression OPTIONAL
}
END
92
Appendix B Test Chart
This appendix describes a test chart to be used in illustrating

examples of ODA Raster DAP interchange files. The illustrations
are included in separate appendices where specific data values for
each attribute have been inserted into the ASN.l definitions as
shown in Appendix A. The test chart is illustrated in figure 17.
The test chart image used was created by the CALS Test Network and
was prepared and placed into the proper format by the National
Institute of Standards and Technology using the Free Value tool.
The bitmapped raster file representing the image is 2560 pels by

3584 lines and therefore has exactly 5 by 7, or 35 tiles. The
image of interest is actually 2550 pels by 3300 lines which will
fill an 8.5 by 11 inch page at 300 pels per inch with no margins.
Within this inner image are border lines at all its edges. Since
the containing bitmapped raster file comprises full tiles, there is
an excess white space of 10 pels per line to the right of the inner
image. Similarly, there are 284 unused (white) lines below the
inner image.
In figure 17, the hard copy illustration of the test chart has been
reduced for reproduction purposes.
If we imagine the tiles to be sequenced from left to right and top

to bottom (the proper tile ordering according to MIL-R-28002B)
every tile but 13, 14, 19, and 24 has its number rendered in text
in its upper right corner.
Tile 1 contains text which displays the size in inches, the

resolution in dpi, the width in pels, and the height in lines.
Tile 19 is an all white tile. Tile 24 is an all black tile. Tiles
8, 9, 13, and 14 have an X between them, running from the upper
left of 8 to the lower right of 14, and from the lower left of 13
to the upper right of 9. There are also 3 wedges in these 4 tiles,
one between 8 and 13, one between 9 and 14, and one between 13 and
14. The 24 other tiles are mostly white with each outlined in
black.
93
Appendix B - Test Chart Data
Figure 17 - Test Chart

Appendix C AIIM Document: With Clipping and Number of Lines
This appendix demonstrates the insertion of specific data values,

representing the image in Appendix B in an untiled format, for each
attribute into the ASN.l definitions as shown in Appendix A. It
represents an AIIM example that is illustrated in Annex B.2 of
ANSI/AIIM MS-53. It is an illustration showing the use of clipping
and number of lines. The data values inserted are shown in column
one and the transfer values are shown in column two.
95
1 <
• 1 1 .
• . * 1 1 .
1 — » 1 *I H4 1 • i • ^ <1i * 1
• . . i » 1
• 1
>
CM
OQ
U
o A
00
A V
A m
a> 00 r— ;h
i-H V V 4J
Cu CO A
E V-i S-i C v£)
nJ V •u o A V
u
CO to CJ 1— A
C C
— A A V 00
OA oo A o A V
>
CM CM 4-)
10 m o VD V V 1—
A VO to
(U
3 A V
1—1
— CMA CM
A 1—!
V —
<
r—
•
» r—
CM on
V V 4J
c
o
rH CSJ
m
VO V V VO > o
— o > A CO o
cd A A u
— u I-H •
oo o 1— Sh A )H A 1-H c
—
> CM V •u >— .
•u 2 'O ON z •u 1—1 4J 1— V o 1
in 1^
u C
to > o o
— O
CO
c
> 2^ CM cn •—
to V to V o o
—
1— 00 CM c C «—
CU i“< I-H
— —
i •
•U V V u o 2; T3 C7\ o 2 O CM O m o .
o o 1
n) CO o 2
— o 2
— CJ o u ON 1—1 in
— VO
Q A c CN CM rO 00 O o o — 1— 4..^
0 —
r—
%4
4J
)-4
V t-H 1
'
O CM OCO 1— •
O 00 00 o o on 1 —
.
o
•
V o CM 00
— -4'
— — oo
to to
(1) C A C o > <
O * <
t3 o CM •
I-H 1—1 o
r-H oo o
1—1
iw o 1—1 o 1
o 00 CO O on •
O o o o o o O o CtJ
CO o V o 1—1 CN
— o
C
— r— — • >
CtJ O
<4-1 on o o a^ cd in
nJ 1 » i
O CO o on O CO t“H CO CO CtJ
o
— f— CM
—
H
o o
1 I—* <
CM 00 on
o m ca ttj • ct) cd • • •
00 rH 1— m I-H CM
Ov cn o 00 CtJ
A
in
1-H 1—1 CM
00 00 CtJ
m
T— o
V ttJ •
2
0)
tu 2
rH •U 2
•iH C CtJ o
t4H a; E r--
O CO 2 CM
Sh (U O
Ph Sh 2
4-)
2 1 — CO
1
c 0)
CM tu
1
1
1
to - - — 2
• P o o o - 3
CQ 3 •2 o o CO 2 -
CJ 2 CM CM o 0) O P CO
—
Sh o - CO - CO 0) o o 2
2 2 P
O Q O •2 O i2 CM 3 * C
2 —
I-H CM
tw - 2 o •2 CO o 1 1 o
•2
oo
v.^ Sh 5 CO 0) OM -Td CO i2 1— •rH P p
2
•
O I-H CO 2 O 0)
— 1 Cd
2
2 2
2
O
w
CO •2
P
0) t4H : CtJ a r2 X OJ f-H (1) •iH
I-H I-H cn •iH 00 p Cd 0) 2 P 2 p P
(2 4-) — tj 2 c
CtJ
I-H 2 cd o o 2 Cd o P O 2 2
E C OJ 1
o
CtJ CtJ 2 M •fH to 1 ‘rH 2 00 P
0) Sh to 0) 2o •rHw 2 I-H to •r^ oo to P 2 O
2
1 1
CtJ
X E 3 o 2 P Cd 0) 1— 2 u p to P 2 2 OO
td tu 4-) •iH 3 C1
O a 2 cd O d) O •2
2
(1) M P
2
2 P
O 4J 2
O
o a;
o e
tsl •fH
2 2
P 2 > 1
O
2
2
P
2
1
P
•iH
o
to Cd 3 to •fH •iH 0) I
QJ Sh •iH CD 2 *rH 2 2 1
E 2 O E 22 P p
3 CtJ 4J Sh 2 1
2 O 0) E o •iH 1
o I 0) •fH 2
4J
— to tu •rH o 1
2 > 3 p M 2 O 2 2 I-H P
cd
Q
CtJ 1 4J 2o •fH 0) •
2
iH 00 00
2
1
> 4J U
2
to oo 1
p P P
0) 3 CtJ CtJ 0)
CtJ (U r-H O
CtJ
Sh CtJ 2 2 E 2 2 2
4J W) •n4 CtJ 1 1
Q
ttJ C
CtJ
CtH
O
Cd
1-1
2o 2P c
o
JZ Sh 1 1 0) c
0)
O
o
Sh
21
U 4J
c 3
E
Sh <U 4J MH 0) o
3 iJ 3 -H P o
O C tl)O 3 2
cn hH E Cl) o
3 2 o
O CO 2
1 1 o
1 1 2
96
LO
1—1 X
CO VD
CO CO CT*
A A
1^
CO VD CM
•
V V m x) 1—1 o CQ
ro CM A VD CM
1— *— O P
CNJ CSJ 1—1 CM V A CM <t O
CO CO A A CM 4-1
>
M > <r
P A
CM
o A
1— VO A 1— A 1—1 VD CM V CO 00
s z A A A CO o CO vD V CO<3“ o A V CM 0) V
•—
z A <r CN CO rH 1—1 c V VD r—
m
f—l
1..^ VO V CM V 00 V X) V A CM o
—o CM p CO X) PL p
V <—
V CO CM p <3* o o .
A V p VD VD e p A
S-l C/1 V — VO 00 to hJ 03 tor—
t— 1—1 o }-i v£) CM !-l CO o <r i— p c . w— CO CM i-i c CP a\ 'd' X c V
o o o o 1-^ P o 4-) CM CO W o <— o o o V pw o 0-1 r-* w A A o
w > z c CJ o o < o *—
— — CM
to 1—1 CO
A C M A c o «— o V
o m p Co
CSJ CM (U Cl^ 4-1 pu, CTv •
CO )-i cr> LO CO 1—1 rH
o o tn o o z o 1—1 o D-I <3" Cli CO
o
o o <
t
VD CM VD cu V r—
V
00
o z
•— CM
V o <c
p— CO 1 —
<c
OV — — CO VO VO
. 1
to
c
o LTJ
VO T— CM
OS
p
r—
CM 1^ (P
z
m o m o o UO O CO u
• • <— 1 1— CO o •
1—1 VD VO CO fp
>d* CO
v— CO — o
1—1
— o > CO > > <
c
VO <r 00 cr^ i-H (U
— 00 CO 1—1 j—
.
nj 1 •
• • 00 o m o o CO o 00 cO 1
CO o Z z
m nJ VO VO 1—o VO CO o o
CO
CO m
P
CT3
o z z 1—1
o CM o o o o i“l 'd- r— CO 1—1 cO *
Q CM
o
m
o o
\o CO CO o P 1—1 00
• • 00 CtJ CO o3 CO 1—1 o3
4-1
OJ o o
CO CO X CM T—
O o
1
• •
03 C A CO
03 in
U 1-1
H V
-
— p
.
r—
o p
o o
CM z o
1^ CO - X p
O CM rH 3 *.
m
p 1
o *
VD 3 3
o
p
T— 00 CM
vD
VD 3
r
3 o
O P VD 3
Z
3
o CM
CO r^
r*^
P3
1-H biO 3
03 1— VD 3 P
1—
•V
00 > - 3 Q E
3
1
CO if
i CM CO P VD •rH iJ
1 t ON 3 3
CM _ - 3 vD p E 3
'— CM 1 - r CO CO > O w 3
3 E
•» 1—1 •rH CM 3 -
—
>•
1
1— CO p P O 3 s
1—1
.
CO 1
CM CM — z CO
<3-
Q O fp
w- CO CM w
p M
•iH
p
P P X r
CO 1— 1—1 3 O
Q) CD W fO 1 f—l oo (D 3 uo P P 1
O f—l vD 1—1 3 p P W VD P
Ml" 01 »iH
(U
w o rO o^ — CO
CO
CO •rH 3 3 <!
to
3
1
3
a 4-1 w CO av P 03 00 Z X P
4J
3 —P •P
z:
p
co 0 CO
—
CO CO
O
1— W
P X o
QJ 1— 0 rH
P 3
O 3
I 1 to r V CM E E •P
bO 1—1 PL o 03 CM f—l 1 1 p 3 CM •rH
3 P
C CD 1 1 f—l pH CD 3 q; CD u p 3 3 rH — - X 3
(U a- c (1) V vd" 4H
P cO P CD 3 o 3 lT) 01
,
M o O 3
i-H 0 p
u
1 CO 03 3
P
r- 1
P p
•rH P VD Z X
P3
•rH C5 LO TJ CD 4J iJ <3* 1
3 1 ‘rH
p P 03 1
X u u o 3 PL 1
p 3 p 1
cO o e
u
<1“ C 1 (D
P V
(D (D rH 3 CO 3 P Z O P
P
o
•rH
QJ
P O
<-
•rH
0
1—
(D
*1—1 •rH
00
c
E P
o
P
1—1
Q 3
3 P
>v
Z
3
3
— 1
<D 1
p zo zo
1—1 •H 4h T) 4-> •p •rH bO w P vD 3 •'-1 1 •H -f—
CL zO 1
C
JH 03
U O P p
X
o
3 3
3 X
3
3
CM bX) Z
0
P
3
P
3 O
z
CL (U 03 r-* 3
CO P bO O 'O •rH P CO to o 3 1
E O 3 1
3 W
1 cO C •H C f—l Zp p ' 1
p
t
E P 3 CM Z3 p •’—> 3
p 1 CO to 03 z3 1
3 3 Q 3 Z X
c P Zo M 4J P 3 3 o P 3 O vD P o O
0) c CD CO CL PL <D CD t
3 E X CTx 3 >v
E cu
p
p > z e p (D 3 3 VD P 3
rH
p (U 1 to 3 3 PL E 3 Ov 3
o C p CO o o 3 O vD 1—
o o c X CJ 0 o P o X rH
X o •rH o O X o VD 1
T! T3
97
1
' * > 1 I ) I . 1 1 •> i1 > 1
' *1 ^
1'
A
CO
V
p
A p
CO CO
A A A c
V rH A CO o A
A V A V \o A T-^ o r—i
m 1—
p
p A
CO V 00 V A A V
V V f— V ^—4 CM CM
00 w CO CO p p V V
u C V p p A A p A A p r— — CM
p A A o u w rH p CM CM CO 1 1
U1 >
M
00 o CO > c V V CO V V c > o
H- — CO
o o >
c V c o
— c o '
z 2 2 2 On 2
'
o V o u «
o f— . »— o
o o u oCSJ
r--
r—
— k_p CO
hJ
o
CL,
o 2 —o
•
o
1.^
o o o
—
. 4 .
2
1— CM CM CO
2
»— p CO r— T3 o^ O
pL, O m .
CM o CO
o^
I— o >
c 1—
w > <c
o O rH O — 1— o
h-l o — CM CM CO OO O 1 .
1*^
« «
o o
o CO o z; 2; CM o CO o o o o o CM o CO o 00 oo o o
o o 2 (O 1— CO CM
CO Csl
o CO o !—
>
o
•
o oo o o T3 o
'
CM
o *—
CM
-1
o CO CO o CO 00 O CO o
o — CM Xi
«
o tp <r O
cd •
o o CM Mf 2 Cd td td
o CM CO
• •
A o
o
Ln CM
V «
4->
3
o
cfl
QJ
•P bO
C to
cu O-
1 (U
—
o u • ••
o •iH O O
o —OO o
a to
o rH - CM CM o
p 2 s -s
OO o 03 o p
o £ o rP N rH CM 3
s Ip o z - o • P CO 3
o p
o U
0)
Or -
CM
o
2
03
W rH
3
rH 2w
— o
1
— 3 1
— •fH
4_l — - o rH
•r^
X 03
bO
Pt— i-H
Cd 2
1
(U
£
1
fH C 1
— — rH 2 — 3 O o O
CO (U p CO o td
2
Cd 2 tsl •fH 1
0) rH - 2 C a; •p p u rH 0) > • iH 3
p u Csl O 0) 4J P 3 3 W c 3 2 *2 p 2
td
— 2 2 Cd •p o O 3 o 03 3 o <D •P
C
•P
td
p 0)
*
p
‘iH
1 •iH
c W
O -P
Cs] •P
P •p
o N
•tH
•rH
p
P 3
1 ‘P
2 > w
2 td P 2 O P 2 2 P P w p P £ E
P a a >s P o
2
P O QJ 3 o 03 3 O
O P
(D 0) O 0) 2 > 03 2 > •p 3
23 (1)
bO bO
0) •1—)
2 P
1 •P
P 2
•!— 23 bO
td •
E
tH
2
3
w C td o o O O w 2 2 £
td Put 1 (U w
2O OJ
p
3 2
-I—)
2
OJ
—
p p o o
(U -P
P W
MCOa.
03
r-l
£
< o
1 u
98
.
• 1
1 1 11 <t
i )
1 «' 1 ' 1 1 — 1 1 1 .
' C1I >' 11 • . 1 i — , 1
t 1 1 It t
A A
A T—
VO V V
V
A
00 U CM CM
A A A V 4J
CM
T— A
VO
oo A O !m
CO
P
>
hM
>
1—
V 1—1 V ro f— A A V 4J o Z z
A V
m r— A V
O cn
CM CO CJ Z z
V A A p
A CM V — —
!-i )M LfO !m
4-1A V 4J 1
V — 4J fH iH o 1
V) m CO CO V V O o
o
P V
CO
C V O u 1— H
1
VO CM
1
CO
C — — iH iH
m t— !m 1 • 1
o
O rH LO VO o o O o
A A O 4J A A o CO o r— ——
— 4-1 4-) .
1
T— o r— W > f— 1—1 o •
CO > W > CJ
1—1
V
V — o
t
C M
CM O Z
1—1
V
V 1
— rH o
CM
c
O
HM
z
c
0
hM
z o rH— r*^ CM
o O O
CM
1— hJ
Pm O
O
— .
r-'
O —
,-! CJ z
— a z
— CM iH o rH CO CO o
Pm CO —
CVJ r-4 ' '
!m CM Pm • '
4-> i 1 4-i Pm CO i r— O O o o o o CCJ
W >
M > <
1— — O —
o O ^n > > <
1— — o
rH
— O m
c
o lO CMa o
' 1—1 P h-1 ' • ( 1 '
CO rH
O S z; CM o CO o Z CM o CO CO CO cc3
O o
—
— — vn r— m CM
i «
1—1 CO CM VO f—
1
CM
o CO o 1^ .
CM
i
O ro O 1— ro O cd
I •— 1—1 —CJ O — rH
'
1— 1—i MD
o O o o o m
I
<0- cO <3“ ca cd • •
1—1 CM 1 — CM fH
A
ov
1-1 O on A vo
ro
O cn
i-l CM Ov CM
V to •
V CO
CM
4J
3
o
Layout
CCl
o
r--
z CM CM
4J
OO
p ,
(J 1
p:
CM
Document
o 3
O -
0) O O
Q
r
O w
O
Z
••
E CO
W)
cO
)M
I-M
z !m O —
- — CO
cd
CJ
4J 1 ro p iH
for C4-4 O .
iH 3 ' •1—
4M zo O CO o Z o
1
1 0)
o
r 4J o r— O
z Q)
4J
•
(1)
»H
u
C
O
ccJ
Z <J-
- to
0)
•H C rH S z i-l •H to o
CH — z Xi
::5
'
’H
OJ
e — •H 4J
i-l
CCJ
to
to z
cd
a
O
Element
4J w 0) 1 !m H a 1 CJ W) 4J to
- P 0) rH (
CJ to H 0) CO u P CvO 1
cn Z 0) 4J w •f— C H 4J CJ OJD •H P iH
o z cd IJM o ClJ »rM •iM x; O c o o;
z -I-l c tc3 '
»H •iM '
z ZZ 4J Jm CCJ I-M a
0) 1 1 •H 4J ij 4J P o CCJ Z Z
Data
4J CX U 4J z CCJ
- C JM O Jm CCJ Z 1 to
CJ O CJ u Q — <! z 01 o •fM ClJ U CJ 1
z
1
eu 4J 4J 0) o o z Z 4J 1 tiO p —
1
•I—)
ZO
1
4J
Z
•w
•>—
xy
z3 U
ofi 4J (J
Z 1
-H
1
1
4J
CCJ
4J
4J
C
1
IM
CD
Z
•H
iH
CJ
Z
CJ u o CO p (J Pu J4 4J c P !J <J
change 1 0) CJ CO (J O O (J (J 4J 4J
4J •!— CO Zo •'—) 4J 4J
Z
CJ 4J CO p CO
3 Z OJ zo 1 •'“1 c (J o CCJ
!-i o o z !m 4J r4 JO O iM O !m
(U
4J CO
CJ
4J
1
4J
CJ J4 O CJ Z
OJ CJ
Mc (U P zo 3 •'~1 CO
e
CO
MM
o
o zo Z
tj
Vj 1 iH ccJ
1
z iH
99
1 4» — 11 * 1 '
> . 1 * •» 1 '. .
• * -I 1 . . ' . .
• 1
> *1 . ’ »
A A A A
A rH rH A CN CN
V VO V CO V V o
A A A V «— — V — «—
ro
A rH 00 « I
VO V V rH 5-1 CM CM 5-1 CM CM O
V 1— — V iJ •U A A CM
1
cn > >
M
W > > CO O
u
u
CsJ CM C
5-1 1—
z Z
c hH
z
HH CM OO o
4Jo o CO V CO A
> p> W V z A A rH
——m
V) CJ CM
C M M — C OO «— •
CO VO rH 5-1 o rH
o z z o
o o
•
4H '
0) V V V 4J A CM V
o X — o rH o — CM a^ CM o
I—
A
W
o
(Jv
— — rH
'
l-i A !-i A A 5-1C V 5-1
t <
o o o o o o O O u> CM CM 4-i rH rH O)
—m
O •U
VO
— — VO CM CM CO CM CM to V V W V V M O W
rH rH rH p
— — C
— — c o o A VO C
O —
«
r—
o o oo o O O o O O o «
o
«
o o .
o
.
O
CM o (
o
a a
— a 0^ kJ V o
VO CM
O O O
CM CM
*—
o CO •
I —
CO < — CO
TJ
o —
'
•
1
o
— eu CO •— o T“H Cl^
4 1
OO > <
VO vd- • — CM CN ro
OO
— rH o rH o —
t
o OO l-H
v£) CM
cO • CO • •
o CM Oro o o o o z CM o
OO o o ^ o o o «— o^ rH 00 X)
O OO 00 O 00 CO rH o CO o in o
<)• OO CM QJ o \o CM
. • cc A CO rH CO cd
CM
m rH
Csl
CO CO CO •
CM
rH OO
V CC • •
OT
VO QJ
c O)
o d
XI
r-~- p •rH
•
p - - p
- o^ o z ro p
- .
- UO
CL, O -
p
T-^ 5-1 •rH CM cO
t— • rH
CO
o o cd
p-
CM CO p
c
O 00 1
bO
(U a 1
OO
p
o - d
d cu 1
QJ 0) 0) Q) 0) CM rH
r—l d 0) P u 4J 4H u c o — TO
CO rP p cO cd Cd Cd cd o O
> CO CO c C P P P o tP O
1
> C •rH iH •rH •rH •rH z bO 1
bO 1 TJ X3 TO TO TO p d P
P P P P •p
S
po
bO T) bO
•rH C U O
5-1
O o O o — P TO 1
— o •i—t O O O o o o o d O P
CO o o CJ O o O u o p CO o O cu
a cO o 1 1 1 1 1 CM c cu
p
Op
P
1 p
O CO P- 1
x T3 X ;>v - CO cu CO CO
•rH 1 CO p d o rH £ d ip CU CO
•P cu 1 CO o o cu X P
1
Xp p
CO C T— u o CM T3 rH •rH
U •rH cu •rH 0) o o; X p cu o w
1 r-H a bO <P CO t— X o o p
p
•p
p cu
p
bO c — •rH CO
C •iH rP p rH P
— cO •p bO d
X
'
•rH (Z CO Cd cO '
1 p d
O D- CO P rH u p Q c d •rH rH
CO iH c c CO P CO C o cu TO p
Cb rH o o CJ P o u cu o rH TO O p
CO o •P N •rH o N •p bO •p p •rH CJ p
CO ‘P p •r^ •tH p C p p 1 1 CO
C P p u p p CO p o p P 1
0) O QJ •rH o 0) Xo o &. d o bO
e X > to X > p- 1 cu 1
d
•rH o p 1 p p (U •rH
TO a cu p d d Cu TO
p C cu o OP O
C (U p o p O
p p d
c o
o o
o
100
VO
4-i
cS
TJ
0)
W
W
OJ
a
A e
CM o
crv o
CM
M-l
V O
A A
CM
A
CM
W
4J
V V V >
h-l
QJ
4J
r— •— »— s; O
CM
_^
4
o VO
;3 o
(4-1
(U
CM
o
1— CM Cv CM 00 o^
oo O OO o 4-1
CM CO
pq
CM
CO
o
00
f—
00
t-M
ro
S
CSJ
00 X)
0)
<t XI
o o
o
c
<D
X
A
A
cfl
u
n3
X
o
in
o
o
CQ
CO
m
CM
CO
m bO
S
C •
(U 5-1 X
C 4J 0)
•rH V) X
1 O
1 u a
5-1 
m t t •iH •
0) 5-1 5-1 •u
u (U 0) ca
o- XI E
E £ 5-1
O
X
'
o 3 p
o c c Cw .
C •
C
(U
J-)
C
o
o
101
Appendix D AIIM Document: Without Clipping and Number of Lines

representing the image in Appendix B in an untiled format, for each
represents an example that is illustrated in Annex B.3 of ANSI/AIIM
MS-53. It is an illustration without clipping and number of lines.
The data values inserted are shown in column one and the transfer
values are shown in column two.
102
1 1 11 1 »
• . > t 1 ^ I •1 1 ^ — i -1 1 1• • • * 1
CO
OQ
U
O
iw
A
00
V
A
00
a> >-i
V u A
a in A 1—1
s>4 C VO V
iJ o V
X in o A
Cd C A A 00 5-1 CM
A o A CM CM A V 4 J
m o o m VO V V A VO CO
0 )
A A rH CM CO U C
u O
3 A V cs CM V V V
Mo o
'
r-M
A A
CM
— V
VO V VO > —o > M A CO o
CO in t
— ;-i f-H oo < »

Vm A }-i A 1—1 C —
> CN
m—
rs. V U f— «
4 J •o ON 4-) -M 4-> 1—1 V O
o o
f
M O
1
rH > o
—o > 5 V V
——o
CO CO CO CO
CO T 1-^ c 00 1
C M —
1
CM CM en C — <—
c r— * * 1—1
U V V u o 2
O
; XJ ON o
o
2 ; O CM Om o
o o
o *—
o On
o
-M in
1 1
— VO CM
—— —
cO in
oo oo
1
Q 5-1 A C
— o CM ro
— 00 o ^ .^ i 1 •
oO
1
u J
4 1—1 o 1
C^J O CO 1
00 00 o CO 1 > t
V u
CM 00
— ’O o — !— — o CO 00 o
— — 00
;-i CO CO
0)
CH
C A
o 1—
C
o 1 — 1
o
o 00 t
1 t
O
00
•
o
•
cn •
CM
O oo OoO Oo
1 1 1—1 * 1 1—1 1—1
cO
V V o CM
CO 1—1
— o
O 00 o 00 00
CO o
C
Oo
ON in
cO —
1 1—-1 1 — •
O
CO
CO • •
M-l
CO • • i-M
cd
cO • •
o I—1— CM
—
H
Oo
1
<0 -
CM 00 CO
o CO CO • • CO • • • • • cO cO • • •
00 iH t-l m I— CM
o
I
cjv CO 00 cd
A CM
in 00 00 co-
in
I i-H o
I
V CO • • .
-o
0) 
c
0)
1
1
1
o . 1
B. §
o
o
CM o
o — O O o - CO bO
(for a - o
-
CO
o
CM
rr rH CM
ro — (0
P o CO
•u
•fH
d
4
,
£ o - CO (1) f-H rH r- d TJ o
o
C4-I
rH
r
CO
CO
•iH
P
o
o
1 —
•H
N
P
CO
r-H o
CO
(0 r-
- p
cO 1
d
o
cO
cu
cO CO CM CO C CO p (0 1 •rl CO
4J rH •iH O 0) > o O p d rH 4h CO length
Example c
(1>
0)
}H CO
o P
0)
rH
•rH
X (0
bO -H
CM mH
P
(0
0 )
X
•rH d d
1
>
CO
IV
bO
d
s d o
p
0)
o
p W' rH 4H cO P P X p o
p
o o p •^
o
0) •u •iH CO Cu O CO in •iH •rH bO
rH o p d cO cn P rH X > 1 p CO p X O cO
u d CO p P C c cO rH
•
4h cO CO cOP P cu
•fH u CO c o o CO O 1 (0 P cO CU CO
Values
CO
+J
•p
CO
P 0
0) p
) XV •r^CO N
•rH
•H
P
CO
<0 •r^
d 1
(0
p
bO
C cu
d
<0
Cu
1
1
(V rH
1
p p P d
S
x Eo
cO 1 *r^ 1
a- B d) *1^ CO rH (V
Q <v p o X o 0 ) o (U O •H IV (0 cu
0)
rH
•iH
d
o
CO
P p
o o E
•o •rH
X > p
1
c CO o o
o
P
cu
cu
bO 4-1 cO CO 1
v p
Data
c
CO
O cO
rH
XV 1
p •fH
o 1
0} •H
3 p
bO
p
bO
 cO cO
o
S-i
Sm
(1)
4J
c 4H
•iH c s
(U 3
X 1
Cu B P P
3 4 J 0 •H) £ o C
s o
CO
o
MC 3 (V
3 o
o X
o
c
o o- o
o CO TJ
1 TJ
I I
103
VO VO
VO
eo ov
A m 1-^ VO
V m
1— O
eg
vO
A VO CM
eg
m eg V A CM -d
A A CSI
> -d 5-1 -d eg A
M
z
VO A m VO
o A r— A
4-) VO
O
CM V O CO 00
A A A CO V CO -d A V — CM V
A CM 00 tH C V VO 1 1
VO V CM V 00 V 'd V 5-1 A CM o 1— CM 5-1 cn •o cn S-i
V 1—
V r— ro
— eg 4-) o A V
-d O o 4J VO VO 4J
•
5-1 CO V
— — CO 00 VO CO CO
rH o VO CM CO O C C c
o —o o
r™l S-i S-I <1- 4-1 CM 1 1 i 1
5-1 (14 CJv -d
oo rH 4-» O 4-) eg ro CO O V o PM 4-) VO A 1—1
m A o
> C o o u _< o
A
CO
M
CO H-J
— CM — -d 00 r-4 CQ
O m
zo A
eg c c i+g On o C rH V
o m 0)
o o o
D-i
P-i
PLi
CO CJ — o Om
1
0 —
1
5-4
4-»
<7v
VO CM vD V 1—
V o 5 V o < < o o m r-
— 00
*— CM
— — CO — ON — — •d 00 VO VO C — VO CO
CM eg 1—4
o —
' ' ' « •
t-4 5-1
• 1 »— o »— 1 1
LO o— o m O 00 1
1 VO n- v£) 4.)
LO
— VO 00
— o > >
— — 00
CO
od o
M
t
VO *
00 • 1
00 OV d d CO < •
c (—1
• 00 o m o o cn 00 d
CO
1— -d •
o
o
2: z
m od :=>
—
d
oO oo o d in
VO VO 1-g VO CO d" 1 • •
•
o CM o 1 — -d T— f—
•
d • >—
CM
m VO 00 d o — f— o 00
• •
• 00 d 00 •
d d • • • f— d • •
ooO
CO t3 eg 1—4
A O O
m
r-l CM
V •
- — 4J
4— 0
4—
0
CM ---
- X 4J 4J
10012 CO in d 0
- 1 — CM 05 VO 0 0
VO VO 0 r- 5-1
00 - 3 vo 3 03 1
- I-- 05 1—4 bO 4J
840, CM o 5-1 VO d 3
-
d CO
1— CM
-
C4-I
05 Q
VO •^g
e 4J
C
0
1
rt^
cn
00 C4-I 05 O' 0) d
2, •H 1 - 5-1 VO 4J 1—4
CM
- 1 00 00 1
0
CM
CO
3 0
1
4J
1,
1
1 — -
05
> •d 4J
Q
0 3
CM eg 1-1 3
S
{ - z
CO
4-» CO
4J
CM
cn
r-
5-1
3 M 3
X 1— 1 — tiO 05 •ig m 4J
/«N
Vi^
/I 1
'+H
3
0
CO CO 3 c 4J VO
0) - CO 1 — d
CO
CO •rg 3
5-1
0 -d
CO
d 4J
-3
CO o CO eg C4-I d •o X CO n-
0
5-1
C
CO 1—1 1—4 CO <u 1—4 0 •H 05
<D
1
d CO CO 4-) -O 0 0 •3 CM e
—
1
r— VO 1—1
1
—
5-1
4J CM iH
Q
o
CO
d
1 1 1 1 1
3 0
CO ON 3 05 u 4J r- *rg
1 1 — 00 Ov d
(1)
5-4 5-1 CD d 3 0 m cd
application-profile
0) o CO 1—1 C4-1
3 3 • 0 3 VO
M4 1
O r 05 4J4J gj 4J 1-1 3 •d 1
cd
-
3 4-) Cvl TJ 0 0 0 3 4J 5-1 4J >1
0
1
4-) d Cl) i 0) 05 05 CM 3 cn cd
*3
U
0)
e
u
-d
CO
gj
CO 1—
QJ
1 ‘rg
4J 4J
•i-g
bO
C
S 1-1
05 3 5-1
C4-I
1—4
Q X
0
•1-4
4-)
C*-l
o
— •
in
C7V
-o
1
•H
C4-4
X X CJ CJ
•iH
ts
bO CJ
d CO
5-1
1
VO
CM
0)
bO 4J
3
CM
1
5-4
1
-d c 0 5-1 5-1 0 3 4J Cl) pi c 0 ?n 0
O
u
CD C
o
- 0 5-4 d d 0 d TJ 3
3
0 cd 3 4J 4J
bO •H 0- ' 1 1
e • CM 1-) 1 CM
d C •H TS 4J 1 4J 4-5 C4-I 1 4J P Q 0 JD
0 3
-Ml •iH
1 d CO 5-1 CO 1-1 C c 0 4-) 3 3 VO u 54
i-i Xi 5-1d o PM 0) 05 1
3 0) 0 C3N <D 13 3
c o d T5 a i 4-1 0) 05 E 0 VO 4-> 4J •!—
3 X
CO
document- 05 5-1 > C
d
1— < d 3 3
0
a £ 3 •3 cri
4— MC
0 0 *3
3
4-) CD > ' 0 Jn 3 CJ VO
C 4J d 4J 3 0 0 0 4J CJ 0 1—4
O c TO CO PM 0 ’O 0 TJ VO 1 d
CJ •H O •3 d) - 1 1—4
104
1 1 « 1
* .
• 1 • 1 t 3 1
• 1* 1
1 1 * 1 1< 1
• * — *
A
CO
V
u
A p
CO Vi
A A A c
V f-H A CO o A
A V A V VD A rH o
CO U CO V oo V — A A V
A V 1— • 4-> A V — 1 1
V 1 1
CM CM
—
00 m CO 00 u p VO V V 1 1
V C V 1-^ •p A A U A A p T—l
— CM
U A A o — 4-) (0 rH P CM CM CQ •— * *
1— U > 00 o i 1
(0 > c V V CO V V c > o oo >M
rH S l-l V — 1—1 CO —
— c 1—1 0
— oo M 00 • •
Mt-
o z V —
o o
(
o o
o Z O 1 1
o z ON z
o
CM o
.
— — W— ——
1—1
o
00 —o —z — CM CM CO I—*
z
CO —
PLi pLi 1 • • « • *
pLi f— 4-) UO (Xi . i I

-o On vO o CM OCO
< o
— m > > oo — O — o iH o <} — CM 1—1
CM CO — 00 o
1—1
o
Oo C
oo
«
t-l 1— 1— 1
T—l • 1—1 1 • 1—1
CO o z
o
Z o CO o o O o O Csj CM o CO O 00 00 o
r—CO
Omo
CM
— 1
CO
O CO O
CO CM
o 00 o
VO o
00
00 O
o 00 1—1
o
oo
T) O
O CO •
CM
o
CM
o — I— CM XI
t
O 1 <t 1—1 C4-1 O
CO •
o o CM cO • CO cO • •
XI • •
O CM CO r-i
A CO O •
O CM
U-)
V CC • • •
4J
13
O
c«
hJ
4J
c
0)
O
o
Q 04
tiO
cd
U CM
o 04 O
M-l
•P
P
z o
o
CM
•.
<—
4J CO o o —O P
s c o CM 13200
1—1 <D CM 1p * m 04
B E o pN P
s <— ip
z
0)
rH
o
o z 1—
o
CM tj CO
cd
P
P o P o o
-
o
o
p 04 • G
O
px
(U £ 1 04 r 04
•tH •P bO
PN
1
(p Cd
4->
0) IP 1p p p cd
P
vertical
•iH bO •P G cd cd CM
P CO Cd
o cd - >0 P CO O P p p p PX > o
G o PM CM 'G G 04 •p G cd G cd 04
p O P P O o
po O CM
0) 0) Vi cd
•o cd
o (U
p
>— X T5 Cd •P N
CO P p
G N
O P
•p
p
G
p p
•r4 G 04 •H G (U
P P
1
b£)
1 *r4
C •p p a p • •H O P p p • E "O
P CO O >o O P ’G CM O 04 CO o 04 E o
G X
cd
o p o 04 P P o P ' X > > 5 G
0) o PM •1—) 1 CM 04 O 04 04 *p
••-1
XI
XG 0)
u E
O
X p o
•P —
P X
*1
XG bO E ’G
o o U cj
O 0
cd •rH 04
CO u P
1 04
*1—)
Vi CM "G E
c G X
CO
1— M o o -o
04
105
1 ) 1 1 1 « - 1 H 1 ^ 1 ^^ 1 — ^ . 1 1
A
A •
v£) V
<8>
A A
00
CM
!— A O A CM
V V ro A A f— V
A V A V CM <1-
u ro }-l o cn cn V Vi A A constr
iJ A V 1— * 4J A CM V •—I V r— •U rH
CO in 00 CO 00 CO V V
C o
m iJ V S-i C V o Vi VO CM
O
Vi C 1—
A A o A A o 00 4J 4J o ^—1
p'. o
•—
> -» CO ro T— o 1— CO > > CO y o rH [5]
V tH o c M cn V rH o C M C M 1—^
V f— 1— CM o z V 1— CM o z o z o 1—
-» hJ o •
p y p y p
4J
CM O
m 1—
«— Pli
PLI
*
!-l
4J
CM CL,
Cu
O
m •— »—
CM
O
•— *
oo
t—
o o
1 08
>
M > M < o o o > >
M <
CO rH VO
C c M o <— o «
o cn o m
00 00 o t—
0 z CM O cn o z z CM 00 00 a5
o ;=•
m t— m C^J
y p
t—
p
>— •
cn CM o VO r—\
1—
CM
•
omo 1—
CSJ
o cn o CM o 1— cO • •
rH fO o
ooo o 1—)
cO •
r™l
o O
<! o
ro <! cd •
VO
ca • • • •
rH CM m CM 1-^
....
O ro •
A
m
CO o cn •
CM lA CM
CC V ^
p
3 .
Layout
o
CM
CO
P -
P
c
y
CM o
a • CM
Document
3 00 'O
y
o
Q CM
1
.
p
for
b O
cp
-
~
CO CO O {
b CO y tJ
y o cO p »
a P o .. rP 3 CO
y
VI
,—1
r
C
y y o CO
y
1
P
•iH
'
spacing
CVJ a o = y y p 3
o
Element
s y rH ,p p p p O
1 P O rP
w p r E 3 3 p •P
1
y
•H 1
P p
•py
cO
1
CO
CO
(p 1 P
n
P y
P p
cn o y
p
^ •H cO
P y y
Data P CO
— •p 3 P •p •p bO
CO
>
•U
c
y
y
p
cO
Q
Cp
p o
•p
cO
1
Py PCL PP o
p
O "0
— - >o P p 3 p CO cO CL pel-spacing
— A •P
cO
C y '
'O’ T3 3 p O cO P CL
y 1 1 *H bO o y o *P 1 bO 1 y
•P Qu P P •n c p p t! CL P P 1 iP 3
H
p^
y o y p cO y y 1 •H 1 CO3 p y
y y p y o y CL p 1 p P y y CL rH
H •r-)
Po Py
1
O*
•p
’’—1
P p3 y •c-)
PO P
O P
p y
3
y
3 p
y 3
p
Interchange
CC!
p p
CO
Vi P o CO
y 1 CL y CO o cO
1 y y p • p 3 y y p
P "T— CO
— c p y p P o p
3 P y M 3 y y o y CL
o o T3 y O •’—) CO
fA o >oP y
cfl 1 rP cO O T3
1— Cd ?p
106
VO
cd
w
tfl
•o
•o
A A V — A
0) 1 — E
r CM 0
2] vO 05 <J
CVJ CM
(U 0 •U
V4-> CO •1-1
constr
> •tM
C 0 5-1
A
P-- •H
C iw
0
[UNIV
•U A V (MJ (4-1
14-1 CO cr. 05
c V 0
(l> A A 5-1 *0 CO
TJ 0
c 0 — Mc
CO CM 4-> t-H
[6]
M — 0 0 A VO C f— —
1
V V 1
CO 05
01 V 4-5
ooo V CM
1
0 0 1
— CJ
06 CM T—
hJ
0 V 0 CM
«—
0
— VO
1
0
CO — 0 —
«
5-1 <J-
o 4->
w > <
CL, r >
b-l
CM
CO — t— ^ CM
v£> > CM
c M 0 « < >
M <3N
0 0000
1
a6 02 0 2 CM 2
0 2 2 CM
— Ov 0 —
— 0 CO 0 00 m 0 CM
« ! 1
« 1—1
1
00 00
CO
— 0 VO CM
'
cC 0 1 o
A
00
— 1 00 cfl • • 00 1 o
CM 0 o
oo
....
<!•
00 CO • • • • •
0 o
CO o
o
V cfl •
CO
VO 3
SH 4J
0 - 3
•r^
•U
r-- 42
1-4
X
. .
5-1 - - 54 A
0 r CO 4-5 A
Cl4 0 -
44 - cd
3 44
u 0 00 1
3
c bO . "3
1, 05 0 « C bO
4-5
0
CM •H
3 0
m 3 CQ
1-M C •H CO
0 0 m ^4 s
0 1—1 0 CM 44
 CO 3 0 54 •r4 44 03
1 4-1 05 0 0 3 1-4 C4 0
{ -spacing-
bO
C
C
05
4-5
3 cd
>o 1
54
4J
3
1
54
0 0
• 3
•H e 42 1—1 05 3 3 3 3
C5 05 •f-l 1
42 54 O. 3
Cd 1-^ 5-1 5-1 4-5 1
0 VO
a u 4-5 05 0 3 •L
3 .
CO 4J •1-4 3 -^ 1 1-4 3 H
1 cd Cd 4-1 4-5 3 0 V
line
f— 4J
— 1 •r4 bO 3 3
XI 0
a i4
u -V
spacing-ratio
05 cd C 4J 3 1
CX a 0 c •H t4 •i4 44 3
C ‘H 05 T2 54 3 0 E
cu 0 4J •3 0 44 3 1 54
bO •H 44 •iH 0 44 3 U 0
C 4J 0 1 1 3 54 3 44
cd 54 O. 4J 4-1 1
D. 42 3
42 0 i
c 0 bOE •H ac
0 O. 4-5 05 1
C 0 1
5-1 C 4-5 3 0 3 44 •
05 4J C 05 D. •3 3 •
4-5 C 4J 0 0 3 •
S2 05 C 0 4-5 0 44 ~
1— 4J 0 3
C 0 0
1
0 0
1 C5
107
Appendix E CALS: Tiled Example Minimum Parameters
representing the image in Appendix B in a tiled format, for each
represents a CALS example using the minimum number of attributes in
the ODA Raster DAP. The data values inserted are shown in column
108
1
* 1 * 1> * 4 I1 '1I ^< » ^ 1 * - .
• 1 •
1 1• * 1 1 1 1
• 1
A
00
A V CO
ro
5-1 CO
V •U CO
n
5-1C m •d
4-)o A CO CNJ
W o -^
1
C A A V 1—1 CM
A O r— CM CM CO CO A
m CJ VO V V 1—
Parameters
fH fH CM VO A rH A
rH
A V I— 1— 1—1 A A A CO O CO VO V
Mo
> oo > A
Values
VO mJ- CM 00 iH
iH 5-1 rH 00 «_• M VO V CM V
oo V p A CM
V p
A V 4-) t3 o^ 2 V — V 1—
CO
— CM O
Image
A
CM CO >
M
1
o
1
<} iH
p CO V
p C 1—
00 5-1 c CVJ r- CM CO tH VO CM 5-1 5-1 CO
of CM V 40 o O CM O CO o •P o P CM CO COo
o O
rH to O > 10 CO hJ hJ C o
oO O
tH A S 1—— 00 rH o A iH c M A C Oi tP Cm Ov o 1.^ CM
o —
5-1
Transfer
Set V 4-> rH o I— 00 00 o o uo o o 2 O rH O Cm Mt Cm CO o 1
m V V V —o
Test
o 00 o o
— _< fO _< ON — 00
A C
oo — CM
XJ CM XI
— — m
1
5-1 1
4-) 1 o I— 1
CO • •
O r— o m o *— 1 I
CO o o in
tfl V o rH CM
— VO
— vt 00 1— 00
— 00 ov 1-M
C *— o Oo
iH 1—1
Minimum O — 1 t4-l
O CO • • •
o O m •
0) 1 t
o O
CO
CO 00
05
Raster
o rH <N
—
— iH o
«
t-M oo in rO VO VO o VO CO -O’ o o
1
o O o f— Cfl • • • • •
o CM oO oo f-4 <) -O’ 1— to •
Interchange
— CM rH CM m VO OO CO
Tiled
o CO m 00 cC • • • • • •
00 CO • 00 CO • CO • •
Using
A O rH <N
00 cC •
-- -- -- I-I o
V CO . . .
Td cn
05 (U rP CM
Image
H
H P p VO
c p CO -
(p <0 to
o
p
CO
(U
a
p •p
0) O
CO -
Test
CP p o
Cp
(p
•p
CO M CM
CM 1
p o tp 1 -
C 1 1

CO o fp
CO
fH 3 fp
•3 3
to CO
— to •v 1 CO
p
—o p
rP •p o VO fH
c 
a
P
3
CO
o
1
(U
0)
p 0)
CM
o o
o CM
•v
o
1
«-*-v cO
fp
00
CO fH
3
3
P P
3 3
of 0> P •p p o N iP CM 3 rH <1> CS] o O s tp P P
1p CJ
3
p 3
CO p
to
p — •P CO
—
o O p
p
1 CM 3
-3
CJ
3 3
3
Ed CO Ip 1 •H •V
3 Ei4 0)
p •p o CO CO p fH P to -O' 4J 1 P P
Set cO P p x: ~- P Ip rH o a CO Cd 3 •H *H
P — 0)
p o
OJ 0) cd
p
C
HO o
Values
CO 05 bO cO 05 •V in x) iP x: x:
Data
cO 1 p •p CO cO O O x: •V
p CM o <Ti 1 •P 3 3
—
1
a 0) P o x: O CD CM N •P CO •p tp -
C tp P P
rP d cO CJ O CM -P P CM r-l x: •V
o O 3 3
H
1 1 1
05 •H O p p TJ iP P P tp CM o CO 0) 3 P 1 1
Minimum bO •P to to 1 P tO o (U o CO •v
p bO O •3 p CM P P
Data
c O CO x: 1
O 1 c x: > 1 CO CO •V
3 •P P 3 3
1
3
CO P r— CJ p •p a •H 0) p 1 CM CO CO cO O rH 3 3
x: CM 1
c CO 3 a •o 3 •V
p x: p •3 •P CM E P
o 1 o p 0) -P
cO o •p (V fH 3 o 0) 3 fp CM 3 3
Interchange
p p -p c E JO *0 c CO 0) p > CO XI 3 3 O
<15 C tP 0) p 1 0) p tu 1 P 3 O 3
Source
P 0) Ip £ o c a o 3 p CO CO CM O •3
Using
c
M p o o o O 3 n O
•3
3 CM ro C3V TO
A
m V A
CO
V 00
A
m r— o A V «
}-i
4-) VO VO
5-1
4J A V 00
5-1
4J A —
V 00 1
V
C VO cn CO CO CO CO
o o V V
O V u Co C
en CM 04 i-i <3V C T-^ 5-1 r-4 5-1
o Pl, VO VO A A o
— 4-> A A o 4-) 4->
— <t 00 o CO
O
CO o r CO > m
CM V
o r— CO >
M
CO
V
o m um Coo 1— C C C
HH
CJN
— —
1
»-i
o VO CM V 1— 1
o S V — 1
o 2 o
rH
>— VO
in hJ (J ::> P o o o
C rH CM *—• CM I—
00 o 1—1 r-H
5-4
4J
r-H PVi
0-1 —
1
5-1
4.) PU CO —
CX4
1 —
1
o
— cn CO
C
>
M > < o
— o
CO >
M > ;< O o — O —
MS"
VO
—
1
CO h- « • 1
C h-i 1 1
o • 1
-d- o z o cn o Z 2 CM o cn
CO
cn
— in in
o
r— cn CM
o P
— P
— CO CO CM 00
— —
• 1 1
CO • t— cO • 1
CM
o O •
CM
o m o 1^ o
— —
o o O o
1
00 •
i-l CM -ct MS"
• • cO • •
o o Mt cO •
oo T— CCS
• CCS
cn •o CM T— C3V CM rH
• •
cO • • •
A
in
O O cn •
A >— 1 o cn • • *
<-l CM CM CM
V cC V «0 •
4-5 p CO p
O 3 •p 45
O
cd
O
So
p
p
P
3
•
CCS CO CO
4-5
3
4J P c
CO 3
05 O CCS Pi
O o O •rH
bO
C Jn 5-1
P P
3
PW 3
45 i c3 1
•rt
5-1 P 4-5 4)
4) 3 E
45 3 E 45 CCS
(4-1 4-5
O 3 bO •H E O 4J 45
—1 VO •rH o c Q P
C 4J Q 45 cp CO - CO 3
45
CO
CO <X VO 4-) P O r p 3
-o
o
0) •H Q CO
O 3 -
P
a O 45
3
O
CCS
4-) 5h VO 45 V E W 45 U •H
rn
o 3 O 4J o 3 o -
t in P CO
cy.
v£)
ur* p
f—
I — 4) o
r—
r 3 P
5-1 •H 4) o bO E O cC
o
O) - 5-1 4-^ •v CM C 1 45 1 s
O m P S o P3
P4J 4J
4J c 4)
•H 0)
c 1 5-1
45
o b3
1 P
45 r
n i—H
O w-
O CO o O CO H 45
-1-4 •fH
St T— P
cn 1 *H c r- 4J
m p
I
—1 -H
«4-4 P —1 CCS
a CO
tiO 4J 4-> 4)
cd 0) 3
c c P- 5-1 vO 1
CCS
4-> CO
cd
45
bO
-r-C
P CO p 4) p O
•f-< 00 0 3 45 CCS - 3 45 •P
TS
O
E 5-1
U
14-1
o CCS
o TS 45 P a CM P
P O
45 P <D
O
3
CO
C
O
05 45
Q — p
O TS CCS
PP
CCS
3
1
CM bO
cO
CO
(U
5-1
1
CM
45 45 1
-rl
1 •P
3 bO 4-> a 5-1 4J PP bX)
C •f-l p a U P p •H
P
O cO 1
C td c o O O cd CO O >o o o p 1 1
1
E 4-1 45 VO 45 4-5 jj 4) o X, o P45 P 45 o t 1
p3 Pa p
CCS
0)
a
1
G
4J o
S Ov PO 1—)
Po
1
Pa p
1—)
o a t—
P P
)
1
p3
3 VO
P
4J
u E P o
>0 c s o 5-1 y 5-1 O CO
o O o o CO
4-) 05 3 o VO 45 1 45 O 4J u 1 45 o
S o TJ cy 4J 4-> 1-) CO
c P "r-) CO
3 o VO 3 P M 3 P
M3
45 45
o T3 4— O O P O O P
o >0 >o
TO - 1 CCS 1 3
110
o
eo
ro
CO
ai
o
u
bO
C
0)
A
m <u
4-)
CO
A A CO H-i CO
CM 'O'
A o
m A V
cw CM
0) V
A V A V •O
ro O CO C U
M
•U A V CO 4J A CM V 00 4-)
CO m CO V CO
C V o c V o
CO
A A f— }-) 5m 1—1
c c
CM CM A
A 1-^ o ro A 1-^
A o
— CO 4J o 5m 0
V —
4-)
V V > 1
CO CTi CJ •
CO > o 4-> o
r— 1—1
1—1 V
V r— — O co M
1
2 cvj
1—1 V
V — 1—^
!— O
CM
C
O
M
Z —
CO
c •—*
— CO o o
o 2 o
r
hJ
f'' CJ r C'' l-J CJ
CM Ph O CM tH Pm O ro 1—1
m — —
*
5-1 CJ
-o On 4J Pl. 1
4J Pm CO 1
> M o o
> > > o >
—
CM 1^ CM cn
cn
C 1— — o « 1—1
CO
C M 1— —
1
•
rH O VO M
O CM cno o 2 2 <N o ro O 2 2 CM o ro i“M
o O o 2
— CJ
rO
—
•
iTl 1— CO CM
— 7—^ CO
O iH
Csl >
M
CO CO 1
CM
O CO o 1— 1
CM
o ro
2
— o — — 2
O O OV
1
I'H ro rH •
r-4 -O' OJ f— t ro r--
• •
'O' CO •
ooo cO •
A >— 1—1
tH CM t— CO CM r-4 CO 82 1—1
• •
A
CJN
1—4 O CO • • •
A >—1 o CO •
'O' ro
CM CM CM
cO V Cfl
4J 4-)
3
o o
a cO c
H-) o
•H
4^
4J 4->
c c o
0) (U Pm
"
§ § _
— o
o
o b
4-5
<3
o
— Q Q o
<1>
4J
.
— c
o
,
o s
-
5m o =
o
u
o o
CM
CO
M-l O (H rM o
o
•*
iH (1) O
s s 5m
O —
o U e 4J O cw
CM •o C cO tH
— C O Cm CO
O OJ 0) 5m r . .
OJ rH OJ CO 4J <3
rH X B I4M 6 x> •H c C 4-)
•H 0) r 0) (H O OJ :3
iH
CO
C4-I rH
IjJ
1
1
5m
OJ
O
r
iH
Cd
1
1
•H
•U
•H
4->
E
OJ
X
*H
4J rH •H C 5m iH 5m
c CO tw OJ O Cd X
o CJ
CCJ
rU
'
"H cO
x5 Or X
N •H
cd
4J CO
4-)
•H 1 cO cO
•rH 4-5
Q - c OJ
Q
cO
>v ' 4J 4-) 1
5-1 CO T) OJ •u -O' •o 4-) c Cfl G

O 0) o
-o CO
— o o OJ Q O
X > 0)
OJ
JD .H
•H
C (1)
0)
XJ
1—)
OJ 4J
c <3
c
o
•H
X
bO 1 1
bO 1
p 4-1 a 5m 4J 73 d 4J (X 5m X o bO •H X
o
cd CJ O O 5m CO O O O CJ C 4J
a) 05 iJ ,4-) 0) O (1) -U 4J cfl CM Or
S •I—) 1
'
di -r-) XI
rC
O ^ O
1—1 1
a Xo o
X
1
cO rO 4J •H Xi d V4 -D 4-> •H CJ-
5m o o 5m O CO m rH O CJ 5m 5m 1
C
^ C O
1 cO 1 CO 1 O
1 rH 1 iH 1 CJ
111
« 1 » i ^ 1
< 1 . o 1 1 1 H 1 1• . •
«
oi
O
4J
bO
S
0)
A
VO 0)
o
<}
4J
•rH cd Cd cd cd cd
CO c cfl cd cd cd cd Cd cd cd Cd 4J 4.) 4J 4J 4J
•H 4J 4.) i-> u 4J 4-) 4-) 4J 4J Cd cd cd cd cd
data
o V iw cd cd
z
cd
z
cd cd Cd cd cd Cd Z Z Z z z
CO A T3 0) t3 TJ Z •d A •d z A
u •o CO CQ A VO A 03 CQ A 03 A 03 -d- 03
o u C
M Ov CO
CO oo co 03 in OQ CC3 CM bq 00 03 CO VO CO CO CO o CO -MSB
CM ro CO
Z A a A a
CO CO CO CO CO CO "d- CO a a A a 00 a rH a A
00 VO
c V s f*-l A A a CM A a
a m iH a r- a A 1 CM 1 1 1 1
o 0 V 1
m 13 O
1
m
1 1 CO 1
V 1 1
V 1
V
VO 1
V VO
m z 1—V V CM
CO r) Ml VO CO CM "d z iH z 1— z CM
o A TJ 4-> 1-^ z "O CM z r— •d 1^ •d Td r— •d CM <1
d d d
z V z z z V
d d CM
'd' n (l> V V V
Cl> (V (U V 0) 0) V 0) -d- d d V ’0 •d" 'd- <»•
A CM V \o C T) •o TJ
O — O r— o
o T) Td z -d T5 o o o o o
o — V > o > o *—
encoded
a> o > o f— r •— o > o *— o > o > o »— CJ > r

V o U A o M o o <) O o o M o -d" o M CJ M o mJ- c M c c M c M c 'd- -d’
CO U CM
V > f— z
CO z—
c
(U >
c
ID >
c

c
0) >
c
0) 5
c
<0
c
> (U 5
c
d 5
c
d >
d d
5 VO >
d d z d
5 VO z VO >
o o A in
o o t: VO »— M M M M M M VO M VO i— M
CM
o o
VO z VO z VO z VO Z VO VO z VO VO VOz •
z •
z • • •
z Z z H z H ro H H «—
H z
o V •
z •
z • • • • • •
H z T.6
CM
CO •— o r—
VO
M o H
> CO H •— H H H CO H H d H o d -d"
CM CH -1
Z d O rH rH CM rH cn -d 15
< o
VO CM
CO — CM
z T— CM CO <1- in VO oo CTv rH rH rH iH iH
o O O
'
z>
o
CJv 0)
T) o TJ 0) r-H
o
rH VO CM
O
CM t—
o o ro
O
VO
O d
z
CM 0) (U cd a>
r—
C3N 0)
i-H
0) 0) 0) CJV 0)
f-H
o d d d d
iH rH
d
rH
C3V
rH rH
d
rH
d d
O'
o
tH<}• oo
CO o in O 00
O
<3-
<!
cO o
CM
00 4J 00
•H
4J 00 4-)
1-^
00 4J 00
•rHCM •rH tH •rH CM
4J 00 4J 00 4J CO
•rH
4->
CM
00
•r-l
4-)
iH
00
•rH
4J
CM
00
•rH
4->
fH •rH CM iH CM •H rH
00 4J 00 4J 00 4J 00
tile
00
o VO CM CM O
00 CO o
<1* 1
-d- 1 1 <! , 1
<t 1 , 1 <t 1 1 1 1 Mj- 1 <!• 1
'Jt' 00 cd • 1
o '
o '
O 1
o 1
O ' o '
o 1 O 1 o '
o 1 o ' o 1 O 1
o
30
CO
m 0)
3
z
•H
a a a a a a a a a a a a a a a
•V •V
Ml A A A A A A A A A A A A A A A
s cn 4-> A A A A A A A A A A A A A A A
o U ^ - « z z
z
z
z
z Z
z z Z
z z Z Z
z
z
z
z
z z
z
z
z
•»
cd CO CO Kn c/3 z z
o 00
00 ~
1
oo
a 1
a1
a 1
a a1
a1
a1
a a1
a1
a1
a 1
at
a1
a1
o •V
c c
ZO z
CM 1-4 •H z z z z z z z z z z z z z z
o in VO z d d d d d d d
zd d d
zd
d d d d
W- O in z z z z z z z z z z z z z z z
rH CMO 1 CO o o o o o o o o o o o o o o o
s 00 1 t3 1
o o o o CJ c; o o o o CJ o o o CJ
c Ml d z c c c c c c c c c c c c p c c
H bO (U -13 d d d d d d d d d d d d d d d d
4J
3
zo C O z
M4 1-1 O o VO VO z z z z z z z z z z z z z
O o d I-I c o •
>v t Z d 1 1
H H H h’ H H H H H H H H H H H
Cd Ml CO Ml cr
tH d cd d CO d 1 1 1 1 1 1 1 1 1 1 t 1 1 1 1
Ml
1
z4J Z CM d CO
• rH rH CN cn z z oo (Ov o rH CM cn in
d O CO
CO C •H iH r^ tH iH rH fH
1-1 d I-I z o
Cw Z
d •H d d d d d d d d d d d d d d d
•H 00 d CMrM z rH iH rH rH iH rH rH rH iH rH rH rH iH rH rH
4-) C Jo rH Cd •H 1-1 •H •H •H •H •H •H •H •H •H •H •H •H •H
c H iM Cm cd e
*
H H H H H H H H H H H H H H H
z
d zo Z
z o z V V V V V V V V V V V V V V V
Z Z
o 1 1
V V V V V V V V V V V V V V V
•H o CM 1
d
z •HC
1 1 Cd
4J CM •
c o 00 s 1
d 1
c 3 z
d
z c C
4J 1-4
c p- d
o o z
c; 4J o C
o
o
112
1* 1 » 1 1 1 1 <1 ( 1 »1 4 11 1 1 1 41 1 ^ 1 (I 41 4 1i 1 11 1 1 1 1 1I ^ 1 '
Cfl to cd cd cd cd cd cd cd cd cd cd cd Cd cd cd cd Cd cd
4J 4.) 4J 4-) 4-> 4J 4-) 4-> 4-> 4-) 4-) 4J 4J 4-) 4-» 4-) 4-) 4J
cO cd cd cd cd cd cd cd cd cd cd cd cd Cd Cd cd cd cd cd
tj *0 TS TJ P p P P P P P P P P p P p P P
A cOCQ CQ CO CQ OQ A cQ CQ oQ CQ A cQ CQ CQ CQ CQ CQ CQ cQ cQ A
CO w CO C/3 CO CO Ov CO CO CO CO CO <1- CO CO CO CO CO CO CO CO CO
00 a A s A s s S 00 S a A a A
a a a a Ov a a a A a A a A a O’
a
CM 1 1 1
A 1 CM A A A A A 1 t 1 CM 1 1 1
A A 1 00 1 1 1 1
V
T) m •o m "O
CJv CJv V o m mCJv V UO p m
00 CJv o cn CO CO V <1-
—
»— »
(U <U 0)
t3 CM
cu CM
P <u — P m p VO p CO p CM
f
0) CM
p — p m p »—
r-4 0) f— 0) r~4 CD O o f— o VO o —
i
o > o — o — o — — o > o — o — o 1—
< 1 1
CJ 1 1 1
o 1 — o —
1
o —
1
CJ 1— o f— CJ >
M c c c V c Mt c 1— C c c C -J-c C c G 'd- -d- <}• 1-4 <}• vd- c -d" c c Mt C c C 1-4
a>
>
(U 0)
— a> 0) z 0) z 0) 0/ (U IV cu (V cu IV CU cu cu cu (V z
VO 1— VO
>
M VO <! VO
> vO 1-4
p
•
> p
— VO M VO M VO VO M VO •— VO M VO M VO >
> > > > > 1-4 1-4 VO
> M VO >
M VO > 1-4 VO
>
M VO >
M VO p
—
•
• •
Z •
z z z z z •
z z z • . • •
z z Z • •
z •
z
H •—
5 H i..i^
H >M H fc—
p H f-H
p H p H p H p H VO H p H p H p
H «— > 1 1—
H p H H P E-i p H *
p H
1— 44
rH VO
r-l
00 Z
rH P I—
o
CM
CJV CM CM
CM
CO
CM
Csl CM
m CM VO r- 00
CN CM CM CM
-d- CJV
CM
o
CO CO
CM
CO
cn
CO
O’ O’
CO
rH
o 0)
CTi
On <1>
M-l
CJV <D
in
(V a> a>
t-4
O
Cw o r^
OO
Q) CJV o p cw 0) cO 0/ cu
(—1
0) (V
1-4
(U CJV (V (Jv 
CO
cC lU
<}•
cd <u
CO
cd cu
CO
O
!-M 1— 1— I— ?— I— 1—1 1—4 1—4 T— 1-4 1-4 1-4 r-4 1—4
CM 1-1 1-1 CO •1— f-M 1-1 CM r^ f— •1—1 r-H •H T— •iM f-4 1-1 CM •H r— •f4 1-4 •i4 1-4 •i4 1-4 •r4 •H 1-^ i4 1-4 •r4 •H CM
1-4
00 4J 00 4.) 00 4J <r 4-> OO 4-) OO 00 4-> OO 4-) CO 4-) 00 4-1 00 4J 00 4-> 00 4J 00 4J 00 4J CO 4J 00 4J CO 4J OO 00 V
Mt 1 <1- 1 <} 1 <} 1 1 <} 1
-d- 1 1
-d" <!• "d" 1
>d- 1
-d- 1 Mt 1 <}• 1 <*• 1 1 <) 1 O’
o
, 1 1
O I 1
o 1
o 1
o 1
o 1
o 1 O 1 o 1
O 1
o 1 O 1 o 1 O 1
O 1
o 1
o 1
O 1
o 1
o
a X a a a a a a a a a a a a a a a a a a
A A A A A A A A A A A A A A A A A A A A
A A A A A A A A A A A A A A A A A A A A
CQ cQ CQ oQ CQ cQ CQ cQ cQ CQ CQ CQ cQ cQ CQ CQ CQ cQ CQ CQ
CO CO CO CO CO CO CO CO CO CO CO CO CO CO CO CO CO CO CO CO
a1
a a a1
a 1
a 1
a 1
a 1
a 1
a t
a 1
a 1
a 1
a1
a 1
a 1
a 1
a1
a1
a1
p
(V
pIV
p p
lU
p IV
p p p p p p p p p p p p cu
pcu
pcu
p cu
(U lU 0) cu 0) IV IV IV (U CV CV cu
p p p po p p p p p p p p p p p p p p p p
o o o o o o o o o o o o o o o o o o o
o o o o o o o o o o o o o o o o o o o o
G G G G G G c G G G c G G c G G G G G G
(U CV (U cu 0) 0) cu cu lU (0 0) (U cu cu cu 0) cu cu cu cu
VO VO VO VO VO VO VO VO VO VO VO VO VO VO VO VO VO VO VO VO
H H E-i H H H H E-i E-i H E-i H H H H E-I H h" H H

VO 00 CJV o T — CM m <! m VO 00 CJV O 1—1 CM CO
CO
m
CO
1— CSJ CM CM CM CM CM CM CM CM CM CO CO CO CO
IV IV 0) <u (V CU (U cu lU IV CU IV CU CV IV cu cu cu cu cu
rH 1—1 — f— rH — i-H 1—1 rH 1— 1— 1-^ 1—1 1-H 1— 1—1 rH
•H •r^ H •H
r
•iH •H
T
•H •rH tH •H •rH •r^ •rH •rH •rH •rH •rH •rH

H H H H H H H H H H H H H H H E-h H H H H
V y y V V V V V V V V V V V V V y V y V
V V V V V V V V V V V V V V V V V V V V
113
0) (0
<0 «S
encode'
encoded
is
is
data
-MSB
-information
content_portion
encoded
content
T.6
35 <If <If
length>) length>)
00
tile
00
00
--
(00
(. indefinite indefinite
--
114
Appendix F CALS: Tiled Example All Parameters

representing the image in Appendix B in a tiled format, for each
represents a CALS example using all of the possible attributes in
the ODA Raster DAP. The data values inserted are shown in column
115
i • f
1 « 1 1» 1 * •
1 t> 1 .1 1 1• 4 .
1 1 1 1 *
• 1 1 1*
Null
and
A
00
A V
A CO
oo r-l 5-1
Parameters
V V 4J
n A
5^ 5-1 G V£>
4-) i-> O A
01 01 o -H
1
C C *— A A V <8>
A O A o CM CM A
o— o m CJ VO V V -O’
A — CMA 1 < A 1—1
— 1—1
«— 1—
CM CM
OV A V i
CM V 1
V
V V M o
> o > A
Values
in VO VO
z T3 o
m 1— — M
Avaiable
A 1—1 5^ r— 1.^ 00 1.^ 5-1 A -^

1
constr
CO V V . 4J 4J V
Image
1—1
CM 5-1
> o
C M — OO
5-1
01
1
oo 01
C
>
M CM CM CO
5
—
1 ^
01
G
V —
r
V o
J-)
o
•o ON o
o
O 'Z CM O CO o
1^
O f—
O a\ [5]
0)
C A C
01
— CM CM CO — 00 O o 1—1o I—* *—
o — oo —
5-1
Transfer
iJ o 1^ O CM .
o ro »— o 00 00 «
Test
01 o V o CM
— 00
— X) o — 1— o cn
Possible
C A
o 1—1
A
1— — •—
t — o OO
1
00 O •
o
00
•
o CO • «
CM
O oooO
• 1—1 08
o V V CM CM
— 1— — —
• t
1—1
1— — o
i
cO Cw o 00 ON cd
Raster
1
o
i
1—
1—
v£>
O CO • •
o CO • • • • 1-H 00 00 a5
all 1— i— — CO
XI
o
1—1
oo CO
CM
cO • • •
00
CO • • • •
CO • •
Interchange
Tiles
'OOcoocnoooo
^ 1—1 1—1 1—< CSl
ct
Tiled
Using
A
....
<— t »-• VO csi

VO oo 00 00 0)
i-H
-- -- -- CM O
V CO •
Ti
t
Cl
01 4J 4J 4-) •d 1
1—1 G G 4-> y
Image
•rH 01 01 cO 0
*4-1 01 01 E 4h
O Cl 01 5h H 0 CM
5-4 5-1 0 y 'd "d
Test
CM a a C4H y
CM 1 1
4-> 1 1 1 01 1 1
G
01
1 1 1
G
d
01
y {
Parameters
p - 5h
3 1
d - »
Raster
o • '
— - 1 4J 0 cn
Q
o - 0
0 — - CO
- - 0 01
y 0 -
y G
0
spacing
5-1
s
1—
z
1-H 01 •iH 0 — CM
0 0
0
— C4H
G
1 •H
O c r 4J CM
Tiled 4H
01
CO 01 - cn y
1-H
CM — 0
01
01
Available 4-> Cl
i-H
0
•iH
5h
0
0
1—4 N
•H
1—1
CO
en
1-H 0
-iH
4J
y
5h
G 5-1 01 1 y CM T) 01 4-) CO bO
<D d 0 Cl 4-) 0 y ' c 1—4 4J
y G
X4J 0
Elements
for e 4J •iH 5h y 1-H X y 0 CO 5h

O d iH bO N y y y CM pel-spacing
Cl
1— d 01
4-)
4J
cO
u C
01
1-H C4H — CO -H •tH X 01
CO
CM 1
Cd 5-i 01 •iH 0 CO 0 CO CM 5h 4.1 01 y I y

cO
4->
01
01
I—H
5h
01
Cl
4-1
Xy •iH01 4-»
G
1-H
CO
01
y
1
r-H X
0 5h
y 14H
1 5h
CM
1-H
y -iH
G
Values
4.) ' 1 4-1 iH G1 0 y CM CO > 0 1 CM 1-H
Data Possible
Tiles cO 4.) 4J 0 x; y Q> N •iH >^ G 1 !h
a 01 d 01 CO 0 0 E 4J 4-) •fH y bO
r-H O 1 5h 5h 73 •tH 5h 5h 1
E T5 1
01 •H G CO cO 1
•o 0 y p 0 •iH cO
Data
00
G
C4-1
0
CO
1-1
0
hH
iC
y
1
4-> •iH
y 1
y
X >
•H
3 G 01 5h
Null
all CO 5-1 • 4-> G 01 bO •d
4= Cl 0 cO 4->01 CO CO y
Interchange
O
5-1
1
4J
•H
4H
4J
G
G p
0 )3
X 1
0- E
O G irH 01 P y G
Source
4.) Cl 0 01 3 0 0
Using Using
G P Cl 01 0 T5 G
l-H d a 5h 0
1
0 01
0
a -d
1
116
A
tH 00
CO V
CO S-i
A
1—1
A
1—
CO 4->
CO
V V ro *13 G
A A CO CM A O A
1—1 A rH t-H A CO o f— A
CM CM VO V V rH CM 00 1— A A V VO
V — CO CO A V V CM CM V
>
M >
M
1—-1 r VO V V 1—
u A A A
OA
CM CM VO 1-H Ml- 1— Csl 1-1
4-» A A A CO CO m V 4J CM CM 4-> t— •— •p
5 CO >
M >
M A CM 00 1-^ CO V V CO
Mo
> oo > CO
1.^ G VO V V V V A G
o GOo 1— G
CM 00 ’G S-i CM 00 H-l
O g: V — V CO CM 4J r—% o z T3 o\ z O
V 5 r 1— »— V4 VCO o o
00 •— o
o p CM p o
r—(
oooo
<}• r-^ r—
1— o U o
•—
VO CM T—
4-) 4J
ro o
CM
<d- 1—
CO
( 4J c
CO o 1— o 1— *0 o\ 1— o CM
CM CO
o CO 1—
VO > CO CO hJ hJ G o o CM VO C3V
CM CO t— 00 o o
o o o o mA o oGO M A C O
oo
CM CM 1.^ 1— 1^ 1-^ 1”l r—i a< cw CTv CM CM * 1-^
o o
(
z o rH o <1- 0-1 CO o f— o O CM O CO o 00 00 o
VO CM CM
V c—
V o < CO
< Os
o 00 CO o O t3 o
r— «— CM VO
o O o *— x>
Csl
• •
o •—
m o VO
«—
oo
m CO O o m o 00 00 O CO
i-l
• •
o O
• •
VO
tfl •
o O tn
00 — Ci 4__l 00 Ov
o o
cd 1—
CO
t— Cw
CM 00
o CM
cd • •
VO
cd •
C3N
cd
m VO VO
oo o
VO CO
o XI XI
t-H
• • • •
CM o o o -d- <t cd •
m \o 00 cd
• • • • •
00 cd • 00 cd cd
CO
1—1
VO
• 00
o
CO
M
> .— cd
'
•V
-
- 0)
fp 1 CO *r^
Ip (p *
CO CO O o
tp
(U *p s p cd —— O o
« *r^
o
G CD Dd 1^ fp fp CM
iP G 1 CO G o • (U O CM 0)
- cd iP 1
CO 1 cd t o N fp cn o CL.
> cd CO CM (p 0)
p
•f
o o
•P fp
p
CO
G
1
> 1—1 1—1 OJ CM CO fp
1-H
G
bO 1
bO
CO
rH
1
-o G
P CM
o
fp
o
CM
t
a>
Cd
p
fp
Cd
01
0)
G
VO 1
-
CO
(U
— -P
O •P
G 0)
ip
CO
-
CO ON 0)
p a>
CJ
CO fp
CO
fp
bO
cd
c:
o
o
•p
XCO
1
01 00 f
'd- o o cd o •p CO o CO 1—1 G p
p G cd
p
a. N p 1
Xp
cd
cx
•p
P
&I
CO
cd
a
cp
o
- CO
cd CO
o
CM
z
p
CO
CJ XV
o
•p G
fp
cd
f
fp
•r^
p
p
G
Cp
o
G
O
CO cd 1 CO p rP CO Czh (V fp 0) CM CO O CJ 0) cd o > t •P
bO
G
1
fp
P (U
G ip
1 Ori r-4 o cd
tP
4J
Cd
G
cd
p P
.p cd •v
G N
0) •iH
•p
p
G
CL.
fp
X 0)
13
P
•P
• 1 1
CO
(U G - 0) o m ip X p f 00 E p P P E •p CO
fp Ou G rP a O rH p CM I
o^ 1 a> CJ •H o a> 1o CO o
•P
o p •>
C!
P «V
p
cd
C
o
TJ
1
P C
cd 0) CM
•G
1
X > E G CL
t
cd cd 1—1 o E •H (U 1p 0) •P 0)
a
CO
CJ
*p
1^ G
P •V
P
O
'O
u
4J
Cd
ip
•p G O
p G bO
cd
’G
G
bO
cd
rP •H CM cp cd o Cp G CJ CL. E CL
CL. .P
Xo 1
01 G c
*rH
1—1
o E
p 3
cd
1 •V
p
cd
00 bO
C
O Cd
•P 4J
x>
d
a Oo
1
p CO 1 •>
cd CO cn a fp T3
G
0) •*
p
G
CM Xo p
0)
a
CL.
£ G p > cd
3 p cu 1
o G p cd CJ
o O G Tl o
’G u •r^ o T)
117
f
t 1 . 1 . 1• — t 1 1 < 1 * . .> — 1 — i 1•
CO
m
VO
A A
A r^
VO V V o m
V 1— — A A CM VO
<6> A 1
A 1-H rH
00 :-i CM CM VO V V A
A V 4J V r— A VO VO
m <t W >
M >
M
1— » C3V rH
A CM c U CM CM iH V cu 1—
'd‘o V 4-) o z Z u A V VO VO
constr
V
A
CO o m >
M >
M
iH
— o •u rHA }-l c
— C CM u cn CJv •o
1
rH o 1
o 53 A V 4-) VO VO
VO
k— CO c
V (Q V o
c
o
1 >
r^ 1— rH
o 5 5 CO
CM u
CQ h4
Put o cyv
[10] o oo 1—
o o O o o 1—
1—
rH VO
1—
in
V 4J o Pm
o
VO VO A
A CO
<1-00 — VO CM CM — rH iH rH c 1—1
< • 1
S-i
CQ
CJv o
CJv
C3V V
o m 1—CM
O O O ooOO om 4-) VO CM V 1—1
— iH tn CJ
m
oo o oooo
06 VO 00 VO CM CM C 1
Mt- U
00 o O O 0
V
iH cd • • . 1
r- 4J
aa
00 o m vO
— — CO CO * 1
CO
c
i-J
o
• f— 00 00 cd • • ca • • 1 1—1 o cu CO
CO < o
. •
CM
CO • •
— m in • • • • • •
1
1—4 cfl
• ——O
•
CM
1 1
— CO m
'
O
'
.
i-H cO CO
CO A CO m
. • . • I— vo <)
I
cfl
o
rH
.
V td •
p
o — I-H
to
P" p P
CM 1— o K Vi
c
V
p m C
u
HO
1
4-^ 1 VO
p r--
-- iH C4H VO p p
rH p 1-H bO cd
in (U u VO ca p
other-coding
•v CO
O
*0 ^-1
3
1-H
0)
:3 p
1
a
VO
E
•iH
P
p
- rH >
4->
1— 1 * CO bO — Cd
> Cd *H VO
C3V
P
CO
P
CO
1 :3
cd
1
•iH
C
1-H
1
bO
>
1 1—1
p
p- CM
O CO
p
u
Pi
•V <4-1 c o
— C b£) •H p
CU o ca CO 1 klH C CO p P
100 •o •1-) Cu - CU o •H cu CJ fO bO O
CO CO O o ca O 4J CO C }-i ca CU CU bO -rH 0) 4-4 o c CM 1 P £
-of
O
•
cfl
Cu
a1
a
CO
i—H Cu
•iH
C r-H ca •H
1 4-)
p
u VO
1 rH
bJ 1—
>-l > cu 1 O 4.) Pi p W u
bO 1-1 C r-4 ca C •iH <4H VO cd p p
P
[
type
1 (1) •H CU cu CU P P CJv 1-H iiH
1
5-4
cu
a- 1-H a CO s o P
cu CO 1
VO
CJ)
cd
Q
>-,cp
P tH
4J bO CU P VO CO P
CO ca c •o CJV P • p
ca c p 1 VO bO p p
u ca 4-> p <r P o -o
£ S 3 cd •iH kiH
1 P o •i
JP P 1
4-) P o o ca p
c 3 •o u P I-H
cu
s o
o p
p
P
p
^
p
3 •o p CO CO
o I-H p
o u
'0 1 Cu
118
1 « i 1
' 1 1 1 • ^ 1
' » 1
* 1 1 1 ^ ^ 1 1 • 1
<r> o
vO vo A A A A A A
A 1—1 rH A CM CM A 1—1 rH
'd- o tH vO V V 00 V V vo V V
CM vo A V — V 1—
V A A
oo r— r 1—1 A 1—1 1—
A tH 1—
<f vo 5-1 CM CM 5-1 CM CM 00 5-1 CM CM vo V V
vo VO in A V 4-> 4-) V 4J V —
CM o 'O’
5-4
CQ
c
>
M >
M
(0
c
>
M >
M 5-1
CO
c
>
M >
M 5-1
•
CM
1—1
CM
CM A A V 4-) o z r^* O z 4J o z z 4J
CM
A A
to o z 5
«—
O z m 5 CQ o z CQ
C
>
M >
M
(U rH <) in V 5-1 C —
•^-1 CO C
vo vo V 4-) 1—1 1-^ o r
o
*— «4-l 0) o 1— o z z
m
f— CO V V o O o o z z
o
O Coo o 1— oo ooo o o o oo m— o o o o 1—
vo CM 4—^ 4.^ Ov CM 1— 1—
o CM
»-l 1—1 1-^ <1- 1—1
vo vo vo 4-) 1 1— r
A A W >
M 1.^
1-H
1— vo CM
vo
CO in c VO CM CM 00 CM CM CM rH rH 1—1 1—1
V
CM VO
0)
o z o —
1
oo O oO o o o o ooo o
mm V o
O oo o
cn CMi
CO
• 1—1 CM 1^ 00 o VO CM CM
r— vo «—-1 vo vo »—-»
oOo 1—1 cO o •
OO O cO • CO •
rH
CM
o (U VO in 1—
CO
<1" 00 o o m v£)
'd-
vo vo vo o m CM 00 00 cO • • • cO • • cO
oo m
•u <w ro in vo rH
m vo LO vo CO o cO •
00
o
00
CO
CO •
ro
1^
U
VO
m
vo
b
vo
m O
1''
CTi u CM CM -
VO vo
rH
Z
'O’
00
VO .
—
. .
,
1— VO 1 •V
vo in CM - 5-1 C3V C3V

-O’ o
CN
5-1
*H -
•H
3 in
CTv
CM tH
-
td
vO
-O’ o
TJ
cO o o O- CM cn
3
CQ CQ O-
m
1
u CQ 04 - 3 bO 3
vo vo CO 4-4 1 cn 04 04 3 3
4-4 3 G -
CO m — T— (
3 > 4J 4J 4-4 3 4J 4J •H 3 value
r-- o X4 CO CO 3 G 3 3 3 >
in tH G c G c •H c 3 iH
vo VO
CQ
05 CQ
1
04
•1-4
5-t o H •H
•3 3
•H "3 -H
52
•H a — 1
bO
CM CO vo 3 0) 5-1 4-4 •H •3 O -3 •3 3 52
r-. 4J vo «— 4J 3 4-4 CQ 5-4 5-1 O o u 5-4 - 3 O -H
O
m G in CO 3 4-4 CO - CQ O O O o o O -a- 3 •H O
— CO
0)
s
vo > rQ O
•H 04
>
CQ
O 04
5-1 --
O o
O o
o
o
o o
O>
O
CJ
bO
52
O
3
4J
3
3
52-
spacing-
C g •u 4J O bO •3 •H 42 O- 3
(U
s O O o rH
5-1
4-5 •H •H O bO 4-4
1 1 1
0 X
1 1
O 4-4 3
5-1
1 1
CO
G
•r^
4J
O
1
CM
-O’
3
CO
4.)
cO
ZO •C 4J
a- co
5-1
O-
G
•H 5-1
CQ O
O
3
o.
bO
G
1
iH
bO
0
3
52
-
vo pel
1 CO (U
CM
<4-4 1 5-4 CO 04 Oi 'H 3 3 3 3 •rH -H
<D 4-> i-M O) G CO 5-1 • 04 D- ‘H 3 1 iH O- O iH
<-( c X5 rH 1
Q O 1 txO iH G •H iH 3
0) CO *iH 4-4 a) •H f-H 3 0-
•H
CO
CO *0 VO
CO
Z 4J
cO
G
04
5-1
04
O- I— 04 Or 3
<v 5-4
vo
•H 5-4 (U
Cd cO
4-> 4-4 iJ
> 04 5-1
vO to G 3 CQ
1 1
G 04 O CO
5-1 1 5-1
vD CO CQ o 5-1
(U 1 0) 4-4 04
CO CQ r*^ CO 5-1
3 3 m
ir>
a
119
11 * * )
• 1' 1 •• ’1 51 1 1
• 1 1
t (» . 1 I . 1
A
00
V
}-i
A P
A m Cfl
00 A 'J- A A c
V t— V 1—1 A CO o
A V A V v£) A 1-^ o
P CO P CO V 00 V A
P A V r— P A V — 1 1
V 1— CM
CQ 1-H 00 CO
Cfl 00 p p
p
VD V
c V p C V P 1—1 p A A p A A fp
A A o — P A
A 1^ o P Cfl 1—1 rH p CM CM Cfl
1—
cn
f— V
o 1 1
OT
c
>
M o
m V o — 1
u >
M c V
o
V Cfl V V
M o
> C
o
— fp rH C c 00
—
V r—i z z
o— o 1—1 z
1 1
o V — <
o o f— 1— o I—* »— o
u <N
1^ hj
1p CP
o z
1— p o CN — O O 1—1 o tP CP
z o z o
00
z CM
CO —
( 1
p CU <—
o
p m D-. , -0 ON ID O CM
> >
M < > M < O o
>
w 1^
(0
— — — O tP— 1— o o — CN -a-
o O
c h-l ' ' 1—1 IP C • 1—1 i 1—1 1
CM CO oo O
o Z CO z o z CM o CO o o o o O CM O CO O 00
o 5 z o z CO
•— »— rP
o
rH CO CN
CO O 1—1 ——1
CO CM
•
o CO O i—
CD o
O 00 o00
•
00 O
o 00
1—) O
00
T) O
O CO •
CM CM
—
'
oo • 1—1 00 1p o — Tp CM z
t t
o (P 1-^ O
Oo cfl •
o o CM cO • cO • •
'd'
cfl
* •
Z • •
T) CM
A O O
t-H O CM CO r-l
cn A CO O •
in
i-l CM
O
m CM
V cfl .
V CO • • •
•p
Root
d
o
ca
p Z
o
Layout o P
p
1 c
p ID
d §
0
o
o
0
Document
cfl
iP Q 0)
W)
1
cfl
P u CP
C 0 ••
cu •>
4-] CD
E P s
for
d
CJ =
••
4J
•P
Cfl
o o
o ^-1
o
o
o ip c o 1—1 CM CM
•o : 0) CP s cn CD o
1 r
B
0)
B
o s -
O
o
tP N
•P
Ip
1 P O 1-^ o p O CM Z Cfl p
Element
o C
Cfl
CD
o
cO
bO
*
Cfl
CD M-i
O
p
cfl
Ip
cfl
P P CD
CP
PN
Data
o •O CD P
cfl
CP CM Z c:
CD P p c cfl C
Cfl cfl CP P P
— O TJ Cfl
— o z cfl •P O O C O
PO >1 cfl O
CD
Z 1
•H
1 •p
d (D
CD
P CD
jO •p
1 1 •P
C CflN
O •p
•P
P
O N
•P *P P
P C z
1 *r4
P> CP P P z c
tkO
•P p a p p ZP CP P P Cfl P P
o o o p o o C O o
Sn O
pd
Cfl CD 1 CD CD
1—
a> p
&i
P
•>—
CD
zd
o
cO
O
CP 1—)
P
CD
CP
P CD
zd
o CD
bO
Z > <D fC
B
>
z
c
1
o 1
Interchange
Zo )
P
o
.p
P O
z u B
o
Z z O
•P
P o
cfl
CP
•H
•d
CD
B
Cfl
o CD Cfl
P
• 
CM 4-) A 1
CM O A <N V *— V
V (A uo 00 CO O r- 00
<—
CM c V o !-i CM
— V— o fH 5-1 U A A
A A o CO 4J A
V fH 1
CO 4-) rH
4.) rH
o
—o >
M o f— (A > O' r
rH lH O c M
> CA W V V
V — rH o C M u V c — constr
•
V — 1
CM O Z •u
— CM o O
o o
m P o P^ tA •
M P
> dr o
o :d
CM
O O — CM 1^ I3h c CM
— 1—
CO •u Oi CO 1
o z Pm CO rH 1
M «— o o > [4]
O w > > < — o o p < o
— 1— CO
oo C M OooO
rW 1— fH
00 o o S s: CM O CO
•
.-1
—z
1
'
CM o
« »
oo
t-H
CM
o P p
— — m rH CO CM •
CM p
——
• •
CM rH CO CM VO o o 08
•
O CM
o CO O o CO O fH
05 O 00 00
— — CO o rH O
•
00 rH <1- rH fH iH CO
Ooo oo
t
• •
cO 0) 00 tc tc a4
CM fH A rH CM rH
• •
A I— O
o^
CO 1
•
CO
00 O CO • .
.-I CM CM CM
V cfl V ca
.
4-) 4-)
3 d
o o
to tc
p p
4.) 4J
c c
0) 05
O O
O O
Q Q
5-1
-
-
5-1 b
O O
P o IH o
05 o *— o
o
4-) G 4J s
c
05
CC
5-1
rH
r
C
05 iH
o fH
s
o
E
13200
o G
0)
tH E
05
p -
4J
iH 1 5-1
05
O
r
rH
P
1
1
5-1
0) tA -
o
1
(U •H •H G o
0)
rC
tA
cd
4J
4-1
•H
4-) 4-)
to —p
p
p
PO
P
p
to
{
tA
vertical
1
Cd
Q
- C 05
p
to
>v c P
— p p
<4-1
o
CO PO P 0) 4J P
O P
05 o
Pr
G
o
to
1 — '
P -H
ttS
C ,P rH G N
tj
•H
O p
r
05
Q)
bO 05 1 •H
05
hO 05 1 1 P p
p p
1
P c 4J
O
(O, 5-1 4J P p;
4-> Pr U P c
P o
p
•H O O 5-1 y >M O 05 05 05
dimensions
tA
cd
05 05 4J 4J 0) O Po
crt
05 4-5 P 05 P p p >
o G •1—)
PO
1
PPr P PP •r—)
PO
1
O-
•H
•'-0
P
G
o
tA
O
u ctS 4-» 4-)
P O o a
o Ch 5-1 O 5-1 O tA
a)
O
ij 1 05 O 05 O
H -T-, P "r— tA
Mc
tA
:3 p 05
p P P 05
1—
o o P O O P
121
A
m
M-l O VO
VD Cvl VO V
VO
VO
in
vO cs
o •p
w
c
VO VO VO O A A A A A A A A A A A A
O CM CM CM CM CM CM CM CM CM CM CM
CTv
<!•
a>
VO
rH o
VO VO — V V V V V V V V V V V V
VO t—t »— 1—^ r— r— r— 1— r— 1—^ f— f—
O 44 o CJV A 1-4 CM CM CM CM CM CM CM CM CM Csl CM CM
CM VO VO o
A A m OV o <) <!
<!
1-4
>
M >
M >
M >
M >
M >
M >
M >
M > >
h-
>
M >
M >
M
CM CM CM V Z z Z z
V V A A
m o O_ z z — —'VO Z 0O — 0 z
— — CO i-i mJ- 1-1 rO . 43 0)
O
. . (4_| '
ca
03
o V O 1-^
V VO o
• 1
CM VO CM VO VO Ov XI 44
o
•— 00 — o
V
T) —'OVi—l-4-CMr^CMOOCMOvCM<Jv CM CflCMXCvI OCMCOCMLOCM
•o ON
1
vo
tH
— voo CO vo ooOOOOOOOOOO OOOOOOOi-iOi-lO
1-1 i-i
vo '
00
'
•
VO CM 18
1-1 O
1— O'—'QT)'—'inoocM O
1—1
CM CM cn CM CM CM CM CM CM CM CM CM CM CM 1—1 CM
O CMo cn CM VO VO r- 1^ oo 00 o o o o O O O O O O O O
o o m OvCMOvvOLn4-li—lO
CO 00 O >a-rî—ivorovoooro
00 O'
ov 00 00 OV
«. •
0) 0)
m
m
*1—! (1) P p Xp X P
Cd r- E vD 1—1 VO
W E bO 1-4 CO
VO
b
P4
vO O
P 1—
•V •n
T—
1—1 0) CO
C (U
•HO
1-4
*14
3
iP
c
0)
CO
cO
3
1-4
VO VO 44 CM in 1—1 cn u P p c ,
•H jj X 1-4
OV VO 00 •V cd
C p (U CO ^ c •P
VO o (1)
•V
f-Hcn m CM o o
in H
0) CO 3 2 O bO
<! CM
m
1-4 v£) VO ON Omm <0N E
p
cr X
(U
C (U
r-' •r4 1—1 E <u •fM CO
1-4 VO P <1*
m
•V •V
CM c
1—1 O CU CO -O
C p
X XO
VO U CM in 1— 1^ o p u o
P
- -
Q
VO
VO r-
c^ X •V
in 1^
CO CM
o •V •V o
1
C o
o cO
O c
o
1l Q,
s CM VO in in On •v 1—1 <1* o CO
^ m y (U
o 1"' -O’ 1— o m 00 O •rH C Cd
o
o
ClH r-
o
0) CO
_< CM VO
•V •V
CM CM T— N p CO
p XP <l>
4J
in VO c m 00 00 CM 1—1 CM cO CO
CM : VO o p CM CO CM CM O 1—1 T—
q_j
o O CO 4J CO
00
CO VO
w
•i4S
P (U
r- a (Q
P
CO •V
VO On •t4 cO C Q\ X ^ c
54
0)
1-4
0 e
o p O
o o
3 E T} CM cn in c 3 < tiO txO
p aCO p 1— (V
cO CO 44 E c 1—1 CM C C c •
•iH CQ c CM
m
44 1 O O •p 00
•V
O
1-H 1^ • •
w
CO •H
p p
CO CO
p p
 <1>
1-4 o f-4 I"' iP VO C O ON - •V ON •H c O p CO W) P C 44
CO
o
•rH
p
X3 VO a> CO o o t-M vj* in in in 4-) o 0) Z p
a> 0) C i4 (V
4-) i4 (p TJ o
•H 1-4 W) -o VO •H 1
>d' Ov vO ON 00 CO (1)
horizontal
•H
P
cO Cfl VO cd cO 1-4 P 1-4
CM m
o r*^ o 1
X> 1
c X c O (U C &
u
P
c
•t4 Q
Ma <D
P
VO
O -
CO
o
a ON 1—1 1 cO 1 •H P -H Cu X) •H 4->
> VO Cu
0) a>
m P
1 OV 1
P
r-'
o K •rM CO
> 4t 1 fH
0) d) 1 0) CM <1- C4
p CO i m U a
a 3 3 VO
O
1-4
VO
cO
VO
in
VO
VO
122
, , , , 1 , 1 , . , , 1 , « — , , , 1 , , ,
A A A A A A A A A A A A A A A A A A A
CM CM CM CM CM CM CM CM CM CM CM CM CM CM CM CM CM
V V V V V V V V V V V V V V V V V V V
—
, , — , — —
, —
, —
, —
, , — —
, , , , — —
• —
, —
, . — —
, , — .—
CM CM CM CM CM CM CM <N CM CM CM CN CM CM CM CM CM CM CM
>
M >
M >
M > > > > > > > > > >
M > > > > >
M >
M
Z Z M M M M M M M M M
H- 1— 1— 1—
Z 2 2 2 2 2 2 z z z 2 2 2 2
P P p
—•<?>—'I—I'—-CM'—'t-l'—'TJ'P
P P P P P
—'4-1'—'f^'—'O'p 5 —'in'—'4^'—'4-1'—'iH'P
P 'I—I'P 5 P P —'CM P
—
a2
18
'
-QOOOOn — ^
' '
CM^CMCMCMCMCM<}-CM<l-r-40CMincMvOCMr''CMr''i-HOCMOOCM<?\CM n)<N^CMX>CM OCM'O

—
cOCMO-O
'O' — ' '
CT't'^CJNrOOOOvO '
• x>
Oi-HOCMOCMOCMOCMOOOCMOCMOCMOCMOOOCMOCMOCMOCMOCMOCMOCM
ooooooooooooooooooo
CMCMCMCMCMCMCMCMCMCMCMCMCNCMCMCMCMCMCM
123
o
00
CO
cfl
a:
o
V
bO A O
C CM CO
(B <t
A A A
A A V A A
o A A A A A
CM UO
CM CM CM CM OD 0) A 1^ i-H t-H
V V V V 4J S-i O A VOV V 1-H V V V V V
1- 1 r — r— Cl •H
Cl s 03
CO CO
CM
V 1—^ »—
V 1—1 1— 1—^ 1—^
CM CM CM CM •H c o rH 3-1 CM CM 3-1 CM CM CM CM CM
V 4-1 o A CM V 4-) 4J
>
M > > > Z
0) O ON 03 >
M >
M
03 > >
M >
M > >
1— h-l h-l V o U A A C c h- h-l h-l
u C CM CM z z z
— CO — o
M I-I r-
OO
03 V V :=> z> z z
V
o —
4d •
ca '
C .-H c
4-1 cy> O CM
o o 00 <y\
o o «— o o VO f— VO VO
2e CM
O
0)
CM
CM
O
4-1
CM
CM
O CO —
1
Cl
4-1
03
c
h-l
D
CM
<
PL,
CO —
VO
—
O CM 44
VO
o o oo
r--
1
. ,
-d-
0)
. .
VO
oOo OoOo OoO
VO 1—1
1-^ 1-^ t— O — CO — CM
0
o O O o oo O o O
CM CM CM CM CM VO CM CM '
CTv ON CM CM CM CM CM
O O O O o o o o o
•
0 CM vO
^ —.(13ON^-d-00J2O
•
cMvoooocoomrôo 00
00
c3
C7\
cO
-d’ O VO CM i-l
A CO > 00 00 -d- CQ
CM h-
in CM
CO 00
CO
D CO •
.-I CO
V «
•
VO VO
03
m 03
4-3
c G VO VO
o Z
-foreground
•rH 1
- •rH
4J VO VO
W
t •
3m
O b d 4J
J 1
Oh vO VO
4-)
o 00
cd
I
c o bO
r- VO 1-M
null
03
o Csl •iH
M o
m O
O - -
4J
C W m CO VO vO — 24
•»
O i-M CM CO
o : bO
f \
-
VO VO
-
3m — •H
C 3m
bO
03 —
O 4-3 C -
4m 03 G 0 •^ VO vO VO
O M
03
4J
0 03
i“H
- - - ••
4-> >0 1
C G c3
u
1
3m O o VO VO V£)
-background,
<1>
E
Z
•rH
I-M
1
0)
03
c3
03
CM - - •*
d) 3m 3m 4J 1 03 03 03
4M
VO o VO
i“H 4-3 03 o 03 03 03 4-3
u 4-3 •fM 03 i-M G 4-3 to to - - •*
CS 4m 4J 03 03 G G VO VO VO
03 1 •iM bO G C3- 03 •H •tM 03 null
4J
— G 4.3 C Z 1 1 44 ZU (13
- -
c3 O G •tH •rH 4m 44 4M 3m CM vO VO VO
Q •rH 03 z 3m O O O o o to 19
G 4J Z o 4-3 1 1 1
o
bO o
o
o
4J - - ••
03 O 3m •iM o 4J 3m 3m VO vO VO
bO •iM O 1 1 cC 03 03 G 1 1 03
C
cS
•U
3m
a
1
4J
G
4M
O bO
1 -C3 Z •tM
!-M
X 1—4
•H vO VO VO
- - •*
tile
Xo O
CM
4J
G
03
4J
1
03 •tM
G
G G
*iM
4J
4J
34 03G CM Z
03 •U 4M o >N o
V G C o 4-3 o
C 03 O
hM 4J O
G
1
o
1
O
124
, 1 , 1 , , , 1 , , , <
1, , , 1 . , 1 , ,
A
tH
A A A A A A A A A A A A A A rH
A A A A A
1-H rH rH 1-^ r— r-H t-H
V V V V V V V V V V V V V V V V V V V V
r-^ . — —
. —
, —
, —
, —
, , — —
, r— , — , — —
, —
, —
, —
,
CM CM CM CM CM (^Î CM CM CM CM CM CM CM CM CM CM CM CM
>
M >
M >
M >
M >
1—
>
M >
M >
h-
>
(—1
>
M >
1—
>
1—1
>
l-l
>
M >
l-l
>
l-l
>
l-i
>
l-l
>
1—
>
l-l
z Z Z z z z z z z z z z z z z z z
E.
:=> z z z z z
ooooooooooo
VD VO rH I— VO T— VO VO VO
o o o o o VO VO VO VO
o o O o o o O o o o o o VO
VO fH VO VO VO VO vO
1—1 1—1 1—1 1—1 1—1 1—1 1—1 1—1 1—1 1—1 1—1 1—1 1—1
oooo Oooooooo
CM CM CM CM CM CM CM CM CM CM
o o CM O O O O o o o o o CM
CM CM CM CM CM CM
o o o o O O o o o
CM
Csl
125
. . , 1 , 1 , i , *, 1 1 • 1 . 1 I* I 1 > 1 1 1 1 1
* ( 1 tI
1 1 1 1 1 1
ai
o
1 4J
bO
c
A
C3V
(V
r-^
CJv
rH a> cd cd cd cd cd cd cd cd
m 4-> 4-) 4-> 4-) 4J 4-) 4.) 4J 4J
!— « cd cd cd cd cd cd Cd
c A
V •H -0 •o T) "0 T3 •o •o •o A
A VO
3-1 (W GO OQ OQ oQ CO C4 m CQ CQ CM CO
A A A A A A A A A A 4J (V w CO CO CO CO CM
cy> r- CO CO CO
V V V
rH f— CO •o Z A Z o A Z A Z A Z Z mA Z z 1-H
V V V V V V V C c V 1 00 V V 1 1 1 1
m CO —
1
— o HH in VO
. — . , — , — —
, —
, —
, , ,
o V "C —
T5 f— T) i-H CM tj •o T} 1
t3
CM CM CM CM CM CM CM CM CM CM
1—-1
o V 0) V O V 0) V CD Ml" (l> V ll> mJ- (V
>
M >
M >
M > > > > > > > VO
i-l
4-> > o — O
•o T) ’O -o
O #— o — O
•o
— 1
>
T3
O 1— O
-o
>
-cd
o
Z z
1— 1— M 1-4 h-l H-l tH CO M <^ -d- O -d- O o O’ O H-l O O HH o
z z z z z Z Z c z c C c c c Z C c Z c
5
*“*
z
.^
z z z
1—
1=1
•—
z 5 >
M o 5 (U > 0) > cu > 0) > IV
— (V
* * *"** 1 -1
V 1.^ H-l H-l h- H-l 1.^ 1— 1 t
z vO z vO Z VO VO z VO VO VO VO
VO VO VO 1— vO VO VO
5
«—
1—
H —H
• •
H
•
H
•
z
— H
•
H
•
H
•
H
•
O o O o o o O o VO VO VO VO VO ro CO
r-l 1—4 1—1 1—1 1—1 1—1 1—1 » •
<v
O o OoooOo O oOo 1— U
1— CO in
1-^
VO 00
( CM Mf
CM CM CM
O O O o CM
CM CM CM
O O O o O CM
CM CM
O
tw
00
> O H-l 0)
t3
as a>
ocd cu
T)
On 0)
(1>
(1> cu
1—1
O 00 U 00 4-> 00 4J 00 4-> 00 4J oo 4J 00 4J
CM <t 1 1 1 ,
-cf 1 1 1 <!• 1
00 o
00
O 1 o 1
o 1
o 1
O 1 O 1
o 1 o 1
O o
ro CO • • • • • • • •
z z z z z z z z Z z z z z z Z z z
A A A A A A A A A A A A A A A A A
A A A A A A A A A A A A A A A A A
cQ CQ CQ OQ CQ CQ CQ CQ CQ cQ cQ cQ oQ CQ CQ CQ CQ
CO CO CO CO CO CO CO CO CO CO CO CO CO CO CO CO CO
Z Z Z Z Z Z Z Z z Z Z Z Z Z Z Z z
1 1 1 1 1 1 1 1 1 1 1
00 •o T) Td Z Td z Td Z •d •d Td •d •d •d •d •Cd •cd
c cv (V (V <v <v (V IV cv IV cv cv cv IV cv cv cv Od
•H "O Z z Td z z Td •d Td z •d •d •d •d •Cd •Cd
u o O o o o o o o o o o o o o o o o
4J o CJ o o o o o o o o o o Cd o o o o
W c c c c c c c c c c c c c c c c c
t <u <v 0) IV <v <v 0) <v <v (V cv IV cv cv cv cv Od
(V VO VO VO VO VO VO VO VO vO VO VO VO VO VO VO vO VO
o H H H H H H H H H H H H H H H H H
o
1 I 1 ' 1 1 ' 1 1 i 1 ' 1 ' ' t 1 1
cr
<v
CO
CM cn 'd- m VO 00 Os o
1-H
1—1CM CO
1— rH 1—1
'd-
—
1
m vO
1—1 1—1
c (V <V IV IV IV IV (V cv <V cv cv cv cv 0) CV IV IV
o f-^ 1-H 1—1 f-H 1-^ 1-^ rH rH 1—1 1-^ I— 1—
•H •t^ *r4 •tH •r^ •H •f-l f-l •r^ *H *H •r^ •tH
4J H H H H H H H H H H H H H H H H H
Cd V V V V V V V V V V V V V V V V V
B V V V V V V V V V V V V V V V V V
U
0
<4-1
c
•i-J
1
4-)
C
(V
4J
c
o
o
126
1 t 1 1 1 1 11 1 1 t
< 4 . 1 1 1
• 1 1 c • c * »
1 1 ' ( »' 1 1 '
to to to CO CO cO cO cO cO cO to cO CO CO CO cO cO cO
«C 4J 4.) 4J 4J 4J 4J 4J 4J 4J 4J 4J 4J 4J 4J 4J 4J 4J 4J
4-) CO to CO CO to CO to cfl to CO CO cO CO to cO CO CO to
td T) •o T3 T3 •o P P p P P P P P P P P P P
'Q A
A CO CO A CO A cO 'O’ CO CO A CO CO CO CO A BQ Qd CQ CO A(O cO OQ CQ
00 00
w
CO VO CO CO r'~ CO o CO CO <r> CO CO CO CO CJv CO CO CO CO 'd CO CO
a A a A
CO CO
S 00 s s 00 S VO s a 00 a a a A a A a CM a A a
a a 00 a cy.
s VO
A 1 CM 1
A 1 1 1
A 1 CM 1
A A 1
A A 1 CM 1 1 1 1
A 1 1
V V V V V V o m p V p m p m p m p o
1 VO CM CO CJv CT\ Cdi Ov 00
— CM TJ •o m •o
— •o
— tj CMp —p m m p CM
p rH p 1— p m p VO p CM cn
t
T) CM <V 1— (1> 0) 1
0) 1
0} CMo .
(U (U CM 0) CM r— y
(V a> CD 1-^ 0) a> 0) y y CM r-^
(U T) T3V V •o TJ 'O’ p V p p V 'd’ po V po V po Po V PO V po V Po po V Po 'd’ V P
o
V p V
O O o o o o o o —
o — o > o — — o > y — o
•o
> o < — CJ > O I—^ o > CJ > 1 I 1
o — — > o — O
1 1
c; 1 1
CJ 1 1 I—-« tj 1 1 1 1 f— o 1—1 y I •
M o c M C <! c 1— c M G c M c
'd’ -d’ c c Mt c M c 'd c G G M G -d C 'd G 'd G 'd
2 c (U Z 0) (U z 0) z 0) z 0) 0) (U z 0) o z y (Vy CD 0) a> y y
> > p > p VO > > > 5 > > >
VO M VO M VO — VO M VO M VO M VO
p VO > M VO >
> >
(1)
M VO 1 1
VO 1— VO VO 1— VO M VO M hM VO 1 i_— HM VO 1—
VOZ • .
z . •
z z .
z z
•
z z Z .
z • . • . • •
z Z Z • •
o —H
H Z
•
' '
<0
H —H m H « '
H p H
— p i
H H H p^ H H p^ H p —H P — H VO H p —H I'M « ' ' —H P HP
p
' — ' ' '
<0
<yi
O
i-M
rH CO CM T*-i
1—
'd’ •ct r— VO LT)
1*4
C'-
rH
00 O
CM
CM 1—
CM
CM
CM
CO
CM
m CM VO CM
CM CM
P'' 00
CM
cy\
CM
CM
O (V
CM
(1) <U o <u Ov
o
CD
CO
o tu
VO
o CP p
<u
CP o 0)
C^
C3V
Cw
0)
in
o
Cdv <u
o 1— O y p y
(U 0)
I'M
0)
t4M
<d\ 0) CO 0) 0) a)
I'M
CT\
<4M
Ov y Ov
y
y y
VO
rH i-M r'H r-H — 1— 1^ —
1 I'M rM 1— I'M I'M I'M 1-4 r— 1—4
— •H rH •tM CM •r4 1—
I
CM *rH 1^ •iM CM •tM rH Cs)•r4 CM •H CM r4 !— •r4 •fM I'M 'iM CM *iM 1— 1 1 •r4 T— •iM 1—4 1—4
00 4J 00 U 00 4-) OO 4-) 00 4J 00 4J 00 00 4J 00 4J 00 4J 00 4J 00 4J 00 XJ 00 4J 00 4J 00 4J 00 00 4J 00 4J 00
1 Mt 1
'O’ 1
cf 1 1
'O’ , ,
'd’ I 'd’ 1 'd’ 'd’ i 'd’ 1
'd 1
-d t
•d 1
'd ,
-d 1
•d 1
•d ,
-d
o
1
O 1 o 1 1 O 1 o 1 o 1
o 1
o 1 o 1
O 1
o o 1
o 1
o 1 o 1
o >
O 1 O 1 o 1 o
a a a a a a a a a a a a a a a a
A A A A A A A A A A A A A A A A
A A A A A A A A A A A A A A A A
ICQCQ CQ caQ CQ OQ OQ BQ BQ cQ cQ cQ BQ CQ CQ
CO CO CO CO CO CO CO CO CO CO CO CO CO CO CO CO
a a a a a a a a a a a a a a a a
1 1 1 1 1 I 1 1 t I 1 1 1 1 1 1
p p p p p p p p p p p p p p p p
p p p Py P py P py py py Py py Py py py py
y y y y y
o o o o o o oo o o o o o o o o
y y y y y y y y y y y y y y y y
G G G G G G G G G G s G G G G G
VO VO VO VO VO VO VO VO VO VO VO vO VO VO VO VO
H H H H H H H H H H E-i H H H H H
I I I I I I I I I I I I I I I I
00 o
|H CM CO VO r'. 00 (dl iH CM "d
1^ CM CM CM CM CM CM CM CM CM cn fO cn CO CO CO
m o m m
rH iH iH rH iH iH iH tH iH iH iH iH rH rH iH
•H •H •H *H •H •H •H •H •H •H •H •H •H •H •H •H
H H H H H H H H H H H H H H H H
V V V V V V V V V V V V V V V V
V V V V V V V V V V V V V V V V
127
U) 01
cd «d
tJ
 4J V c
cd cd cd
cd
T3
cd cd
Td Td
Q
•O •o •O *r<
4J c
cQ CO cO CO CO A co
Q
OT cn CO CO CO CO g
s S A S A S A S CO S ;4
tf-l
4J
A 1
m
1 1 1 1
0
cn cn
”0 CM Td VO Td VO -cd VO Td
V Q
T)
(V CM 0) 1— (U rH (1) rH 0) —
1
Cd
c
*iH
p
tj t5V Td T3 V Td V V <1- •Cd 1 4J
1
1
o o o o o o 4J
CJ 1— o — Cd »— Cd *— o > M
c C
1
Cd
C c c c c M wrti
4J
0) (U 0) 0) 01 Cd 4J c
M
>
M VO >M VO >
M VO >
M VO — VO C Q
VO '
0 M
•
H 5 H 5 H •_!
• • •
Z H • •
Q /--S
5 H 5 iw H A
O CM m m Mh XA•u 4H -5
fO CO cn m CO CO
V W)
V
Cw CO CO <n c c
di •0 0) o d 01 cC Cd O (D Cd 0)
rH
tH
rH rH rH rH rH
rH hH rH iH rH •r^ CM *iH O rH ^
O rH
4-) CO 00 4J 00 4J 00 4-) CO 4-)

O Cd O (1)
•p 4J
1 Mj- 1 1 Nf <)• 1
O •iH
o
1 1
1 o 1 O 1
O 1
o 1 o t
c
•iH O c
1-1
• cp
• • • >w^ 0) Cd
T3 Td
t
C • c
• • • • • t 1 •iH
128

Ni Stir 5108

Uploaded by

Document Information

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

Ni Stir 5108

Uploaded by

Copyright:

Available Formats

(Supersedes NISTIR 4567)

U.S. DEPARTMENT OF COMMERCE

U.S. DEPARTMENT OF COMMERCE

U.S. DEPARTMENT OF COMMERCE

NATIONAL INSTITUTE OF STANDARDS

This report examines the technical issues facing an implementor of

The motivation behind the development of the raster graphics file

CCITT had been collaborating with the International Organization

It fills two important needs: (1) storing complex documents

This document supersedes NISTIR 4567, Tiled Raster Graphics and

Many people contributed to the creation of this report. All the

The efforts of many other people too numerous to mention are

7 Views of Raster Data 15

8 ODA Constituents and Attributes 20

9 Technical Specification in the DAP 40

10 ASN.l Coding Concepts 49

11.10 Uncompressed Bit Sense 74

Appendix A ASN.l Definitions 85

Appendix B Test Chart 93

Appendix C AIIM Document: With Clipping and Number of

Appendix D AIIM Document: Without Clipping and Number of

Appendix E CALS: Tiled Example Minimum Parameters .... 108

Appendix F CALS: Tiled Example All Parameters 115

* • ®i' 5 T U3i - •% t.'

/^r. ., ^A:iiv.V t ,.i:?.i'5a ! . rI)i7aq4Al

First, this tutorial provides an overview of the pertinent

3) and an overview of ODA (section 4)

sections is a discussion of the organizations involved with ODA and

The tutorial examines the actual sequence of data elements found in

description of the ODA structure and its elements (section 8) and

In the latter portion of this document, the details of several

the basics of raster graphics is presented at the beginning of

Appendix A provides a complete list of the abstract syntax notation

This document is intended to be an aid to an implementor of the ODA

MIL-R-28002B restricts certain features of the ODA Raster DAP

1. Those that must be specified by the contracting officer

2. Those that a contracting officer may wish to specify,

Type I and Type II Data

MIL-R-28002B discusses two different possible representations

Type I data is simply CCITT T.6 encoded data for an entire

Type II data is a MIL-STD-1840 header wrapped around an

ODA DAPs describe a restricted subset of the wide range of objects

of having to support features not of use to their application. The

addition, a group of international delegates have agreed to a plan

obtaining an approved International Standard Profile (ISP) by

2.4 ANSI/AIIM MS-53

Compound documents are those electronic documents consisting of

Word processor vendors are developing ODA export and import

3.2 Relationship to Facsimile

Provisions exist in the international Profile Alignment Group for

ODA through ISO 8613-7 allows both T.4 encoding (commonly

3.3 Using ODA

The resistance some people have expressed after their first

A new era of connectivity is beginning as the Open Systems

Version 2 of GOSIP [21] contains information required to transport

4.2 ODA's Base Standard: IS 8613

IS 8613 has several parts, each of which addresses some portion of

Part 1; Introduction and General Principles [9] gives a great

Part 2 Document Structures [10] defines the basic elements of

a document architecture and the conceptual models necessary to

Part 4; Document Profile [11] describes the purpose and

Part 5; Office Document Interchange Format (PDIF) [12] shows

^ The ISO 8613 ODA Standard is scheduled to be republished in

Part 7 Raster graphics content architectures [13] is the