RD55 Document-Requirement Gathering

REQUIREMENTS DOCUMENT
(RD V3.1)
FOR GPOS
DIGITAL CONTENT SYSTEM (FDsys)
FINAL
June 7, 2007
GPOs Digital Content System (FDsys)
Requirements Document (RD) v.3.1
Office of the Chief Technical Officer (CTO)

FINAL
Table of Contents
1 Introduction ......................................................................................................................................................................... 6
2 Requirements for System, General..................................................................................................................................... 7
3 Requirements for Content Metadata................................................................................................................................... 8
3.1 Content Metadata Core Capabilities .......................................................................................................................... 8
3.2 Content Metadata Types ............................................................................................................................................ 8
3.3 Content Metadata Schema......................................................................................................................................... 9
3.4 Content Metadata Import and Export ....................................................................................................................... 10
3.5 Content Metadata Management............................................................................................................................... 11
4 Requirements for SIP........................................................................................................................................................ 11
4.1 SIP Deposited Content .......................................................................................................................................... 11
4.2 SIP Harvested Content.......................................................................................................................................... 11
4.3 SIP Converted Content.......................................................................................................................................... 11
4.4 Core SIP Requirements ........................................................................................................................................... 12
4.5 Requirements for sip.xml File ................................................................................................................................... 12
4.6 Structural Layout for SIPs......................................................................................................................................... 13
4.7 Packaging of SIPs .................................................................................................................................................... 13
4.8 SIP Descriptive Metadata Requirements ................................................................................................................. 13
4.9 SIP Administrative Metadata Requirements............................................................................................................. 14
5 Requirements for AIP........................................................................................................................................................ 14
5.1 AIP Core Capabilities ............................................................................................................................................... 14
5.2 Requirements for aip.xml File................................................................................................................................... 15
5.3 Structural Layout for AIPs......................................................................................................................................... 16
5.4 AIP Metadata............................................................................................................................................................ 16
5.5 AIP Unique ID........................................................................................................................................................... 17
6 Requirements for ACP ...................................................................................................................................................... 17
6.1 ACP Core Capabilities.............................................................................................................................................. 17
6.2 ACP Binding Metadata File ...................................................................................................................................... 18
6.3 ACP Metadata .......................................................................................................................................................... 18
7 Requirements for DIP ....................................................................................................................................................... 19
7.1 DIP Core Capabilities ............................................................................................................................................... 19
7.2 DIP Binding Metadata File........................................................................................................................................ 19
7.3 DIP Metadata............................................................................................................................................................ 20
8 Requirements for Pre-ingest Processes ........................................................................................................................... 20
8.1 Pre-ingest Processing .............................................................................................................................................. 20
9 Requirements for Ingest Processing................................................................................................................................. 21
9.1 Ingest Processing Core Capabilities ........................................................................................................................ 21
9.2 Ingest Processing ..................................................................................................................................................... 22
10 Requirements for Preservation Processing .................................................................................................................... 22
10.1 Preservation Processing Core Capabilities ............................................................................................................ 22
10.2 Preservation Processing ........................................................................................................................................ 23
10.3 Preservation Processing Assessment................................................................................................................. 26
10.4 Preservation Processing Administration.............................................................................................................. 26
10.5 Preservation Processing Storage ........................................................................................................................ 27
10.6 Preservation Processing Metadata ..................................................................................................................... 27
10.7 Preservation Processing Security ....................................................................................................................... 27
11 Requirements for Unique Identifier ................................................................................................................................. 27
11.1 Unique ID Core Capabilities ................................................................................................................................... 27
11.2 Job ID ..................................................................................................................................................................... 28
11.3 Content Package ID ............................................................................................................................................... 29
11.4 Interface for Unique ID ........................................................................................................................................... 29
12 Requirements for Persistent Name................................................................................................................................. 29
12.1 Persistent Name Core Capabilities ........................................................................................................................ 29
12.2 Persistent Name Resolution ................................................................................................................................... 30
12.3 Persistent Name Metadata ..................................................................................................................................... 30
13 Requirements for Authentication .................................................................................................................................... 30
13.1 Authentication Core Capabilities ............................................................................................................................ 30
13.2 Authentication Content Pre-ingest and Ingest..................................................................................................... 31
13.3 Authentication User Credentials .......................................................................................................................... 33
13.4 Authentication Content Integrity .......................................................................................................................... 33
13.5 Authentication Time Stamps ............................................................................................................................... 34
13.6 Authentication Integrity Marks ............................................................................................................................. 34
13.7 Authentication Content Delivery .......................................................................................................................... 35
13.8 Re-authentication of Content.................................................................................................................................. 36
13.9 Authentication Standards/Best Practices ............................................................................................................... 36
13.10 Authentication Records Management .................................................................................................................. 36

FINAL
13.11 Authentication Metadata....................................................................................................................................... 37
14 Requirements for Version Control................................................................................................................................... 37
14.1 Version Control Core Capabilities .......................................................................................................................... 37
14.2 Version Triggers ..................................................................................................................................................... 38
14.3 Version Detection ................................................................................................................................................... 38
14.4 Version Metadata ................................................................................................................................................... 38
14.5 Version Relationships............................................................................................................................................. 38
14.6 Version Notification................................................................................................................................................. 38
15 Requirements for Workflow............................................................................................................................................. 39
15.1 Workflow Core Capabilities .................................................................................................................................... 39
15.2 Workflow Control of Execution ............................................................................................................................ 40
15.3 Workflow Monitoring ............................................................................................................................................ 41
15.4 Workflow Resource Requirements ...................................................................................................................... 42
15.5 Workflow Notification ........................................................................................................................................... 42
15.6 Workflow Security................................................................................................................................................ 42
15.7 Workflow Interface............................................................................................................................................... 42
16 Requirements for Storage Management......................................................................................................................... 42
16.1 Storage Core Capabilities....................................................................................................................................... 42
16.2 Content Delivery Network Storage ......................................................................................................................... 43
16.3 Networked Moderate Performance Storage ........................................................................................................... 43
16.4 Low Criticality- Low Cost Storage........................................................................................................................... 43
16.5 Failover Storage ..................................................................................................................................................... 43
16.6 Backup Retrieval Media Storage ............................................................................................................................ 44
16.7 Mid-term Archival Storage ...................................................................................................................................... 44
16.8 Long-term Permanent Archival Storage ................................................................................................................. 44
16.9 Functional Data Storage......................................................................................................................................... 44
16.10 Storage System Standards .................................................................................................................................. 45
16.11 Storage Monitoring ............................................................................................................................................ 46
16.12 Storage Preventive Action ................................................................................................................................. 46
16.13 Storage Data Integrity ....................................................................................................................................... 46
16.14 Storage Allocation ............................................................................................................................................. 47
17 Requirements for Security .............................................................................................................................................. 47
17.1 Security System User Authentication .................................................................................................................. 47
17.2 Security User Access Control.............................................................................................................................. 48
17.3 Security Capture and Analysis of Audit Logs ...................................................................................................... 48
17.4 Security User Privacy .......................................................................................................................................... 50
17.5 Security Confidentiality ........................................................................................................................................ 50
17.6 Security Administration........................................................................................................................................... 50
17.7 Security Availability.............................................................................................................................................. 51
17.8 Security Integrity.................................................................................................................................................. 52
17.9 Security Standards ................................................................................................................................................. 52
18 Requirements for Enterprise Service Bus....................................................................................................................... 53
18.1 ESB Core Capabilities ............................................................................................................................................ 53
18.2 ESB Configuration .................................................................................................................................................. 54
18.3 ESB Administration................................................................................................................................................. 55
18.4 ESB Interface ......................................................................................................................................................... 55
19 Requirements for Data Mining ........................................................................................................................................ 55
19.1 Data Mining Data Extraction................................................................................................................................ 55
19.2 Data Mining Data Normalization.......................................................................................................................... 56
19.3 Data Mining Data Analysis and Modeling............................................................................................................ 56
19.4 Data Mining Report Creation and Data Presentation .......................................................................................... 57
19.5 Data Mining Security and Administration ............................................................................................................ 58
19.6 Data Mining Storage............................................................................................................................................ 59
20 Requirements for Content Submission ........................................................................................................................... 59
20.1 Content Submission Core Capabilities................................................................................................................... 59
20.2 Content Submission System Administration ....................................................................................................... 59
20.3 Content Submission Metadata ............................................................................................................................... 60
21 Requirements for Deposited Content ............................................................................................................................. 62
21.1 Deposited Content Core Capabilities ..................................................................................................................... 62
21.2 Deposited Content Metadata.................................................................................................................................. 62
21.3 Deposited Content Interfaces ................................................................................................................................. 62
22 Requirements for Converted Content ............................................................................................................................. 63
22.1 Converted Content Core Capabilities..................................................................................................................... 63
22.2 Converted Content Interfaces ................................................................................................................................ 63
23 Requirements for Harvested Content ............................................................................................................................. 63
23.1 Harvested Content Core Capabilities ..................................................................................................................... 63

FINAL
23.2 Harvested Content Metadata ................................................................................................................................. 63
23.3 Harvester Requirements ........................................................................................................................................ 63
23.4 Metadata Requirements for Harvester ................................................................................................................... 64
23.5 Harvester Rules and Instructions ........................................................................................................................... 65
23.6 Harvester Interface ................................................................................................................................................. 65
23.7 System Administration for Harvester ...................................................................................................................... 65
24 Requirements for Style Tools.......................................................................................................................................... 66
24.1 Style Tools Core Capabilities ................................................................................................................................. 66
24.2 Style Tools Automated Composition ................................................................................................................... 66
24.3 Style Tools System Administration ...................................................................................................................... 67
25 Requirements for Content Originator Ordering ............................................................................................................... 67
25.1 Content Originator Ordering Core Capabilities....................................................................................................... 67
25.2 Content Originator Ordering Job Management ................................................................................................... 68
25.3 Content Originator Ordering Job Tracking .......................................................................................................... 72
25.4 Requirements for Access Content Processing....................................................................................................... 73
25.4.1 Access Core Capabilities ............................................................................................................................... 73
25.4.2 Access to Content Packages ......................................................................................................................... 75
25.4.3 Access to the System .................................................................................................................................... 77
25.4.4 Access User Registration............................................................................................................................ 77
25.4.5 Access User Preferences ........................................................................................................................... 78
25.4.6 Access Processing......................................................................................................................................... 78
26 Requirements for Accessibility........................................................................................................................................ 79
26.1 Accessibility Core Capabilities ............................................................................................................................... 79
26.2 Accessibility Section 508 Technical Standards ................................................................................................... 79
27 Requirements for Search ................................................................................................................................................ 84
27.1 Search Core Capabilities........................................................................................................................................ 84
27.2 Search Query ...................................................................................................................................................... 85
27.3 Search Refine...................................................................................................................................................... 87
27.4 Search Results .................................................................................................................................................... 87
27.5 Saved Searches ..................................................................................................................................................... 88
27.6 Search Interface ..................................................................................................................................................... 89
27.7 Search Administration ............................................................................................................................................ 89
28 Requirements for Request .............................................................................................................................................. 89
28.1 Request Core Capabilities...................................................................................................................................... 89
28.2 No Fee Requests.................................................................................................................................................... 89
28.3 Fee-based Requests .............................................................................................................................................. 90
28.4 Request Delivery Options.................................................................................................................................... 92
28.5 Request User Accounts....................................................................................................................................... 92
28.6 Order Numbers and Request Status ...................................................................................................................... 93
29 Requirements for Cataloging and Reference Tools........................................................................................................ 93
29.1 Cataloging and Reference Tools Metadata Management................................................................................... 93
29.2 Cataloging and Reference Tools Metadata Delivery........................................................................................... 93
29.3 Reference Tools ..................................................................................................................................................... 94
29.4 Cataloging and Reference Tools Interoperability and Standards........................................................................ 94
30 Requirements for User Interface..................................................................................................................................... 96
30.1 User Interface Core Capabilities ............................................................................................................................ 96
30.2 User Interface Standards and Best Practices ........................................................................................................ 97
30.3 User Interface Customization and Personalization ................................................................................................ 97
30.4 User Interface Default Workbenches ..................................................................................................................... 98
31 Requirements for User Support ...................................................................................................................................... 98
31.1 User Support Core Capabilities .............................................................................................................................. 98
31.2 User Support Context Specific Help.................................................................................................................... 99
31.3 User Support Helpdesk ..................................................................................................................................... 100
31.4 User Support Knowledge Base ......................................................................................................................... 102
31.5 User Support Alerts ........................................................................................................................................... 103
31.6 User Support Training and Events .................................................................................................................... 103
31.7 Contact Management ........................................................................................................................................... 104
32 Requirements for Content Delivery and Processing..................................................................................................... 105
32.1 Content Delivery Core Capabilities ...................................................................................................................... 105
32.2 Content Delivery Processing ................................................................................................................................ 106
32.3 Content Delivery Mechanisms.............................................................................................................................. 106
33 Requirements for Hard Copy Output ............................................................................................................................ 107
33.1 Hard Copy Output Core Capabilities .................................................................................................................... 108
34 Requirements for Electronic Presentation .................................................................................................................... 109
34.1 Electronic Presentation Core Capabilities ............................................................................................................ 109
35 Requirements for Digital Media..................................................................................................................................... 111

FINAL
35.1 Digital Media Core Capabilities ............................................................................................................................ 111
Appendix A References .................................................................................................................................................. 113
Appendix B Acronyms and Glossary .............................................................................................................................. 123
Acronyms...................................................................................................................................................................... 123
Glossary ....................................................................................................................................................................... 127

FINAL
1 Introduction
This document defines the requirements for the U.S. Government Printing Office's Digital
Content System (FDsys) and is intended to communicate those requirements to the
technical development community which will build the system.
System Purpose:
FDsys will be a comprehensive, systematic, and dynamic means to create, ingest,
authenticate, preserve, manage, and provide access to Government information from all
three branches of the Federal Government. The system will automate and integrate
lifecycle processes of Government information and deliver that information in formats
suited to customer needs and desires.
System Scope:
FDsys will be built to include all known Federal Government publications falling within
the scope of GPO's Federal Depository Library Program (FDLP), including text,
graphics, video, audio, numeric, and other emerging forms of content. The full body of
these publications will be available for searching, viewing, download, and printing, and
will also be available for the production of document masters for conventional and ondemand printing.
System Releases:
FDsys is being implemented in a series of incremental releases, each of which builds on
those preceding it, and add improvements to system capability and underlying
infrastructure.
Requirements:
The requirements documented here are the product of a development process that has
as its basis the Future Digital System Concept of Operations (ConOps) (rev. 2006) and
previous versions of this document. Thirty-Four major system capabilities are described,
each with multiple subsections arranged hierarchically. Each requirement is assigned a
release in which we expect its implementation, as well as a ranking of criticality to that
release:
Must indicates a requirement essential to the successful function of the system;
Should denotes functionality users will expect, and which should be implemented
in as many cases as possible;
Could indicates functionality that, although desirable, is not viewed as critical to
system function or user experience.

FINAL
ID
Object Number
RD-1
RD-2
RD-3
2
2.0-1
2.0-1.0-1
RD-4
2.0-2
RD-5
2.0-3
RD-6
2.0-4
RD-7
RD-8
RD-9
2.0-4.0-1
2.0-4.0-2
2.0-4.0-3
RD-10
2.0-4.0-4
RD-11
2.0-4.0-5
RD-12
2.0-4.0-6
RD-13
2.0-4.0-7
RD-14
2.0-4.0-8
RD-15
2.0-4.0-9
RD-16
2.0-4.0-10
RD-17
2.0-4.0-11
RD-18
2.0-5
RD-19
2.0-6
RD-20
2.0-6.0-1
RD-21
2.0-6.0-2
RD-22
2.0-6.0-3
RD-23
2.0-7
RD-24
2.0-8
RD-25
2.0-8.0-1
RD-26
2.0-8.0-2
RD-27
2.0-9
RD-28
2.0-9.0-1
RD-29
RD-30
2.0-9.0-2
2.0-9.0-3
RD-31
2.0-9.0-4
RD-32
2.0-9.0-5
2007-05-08 Requirements Baseline
RC
2 Requirements for System, General

The system shall provide for the use of internal and external open interfaces.
The system may provide for the use of proprietary interfaces only when open
interfaces are not available or do not meet system requirements.
The system shall provide an architecture that allows preservation of content
independent of any specific hardware and software that was used to produce
them.
The system shall use plug-in components that can be replaced with minimal
impact to remaining components as workload and technology change.
The system shall accommodate changes in technologies and policies without
requiring major re-engineering or design changes.
The system shall support multiple user roles.
The system shall support the assignment of one or more roles to a user.
The system shall support the management of the functions permitted by a
user role.
The system shall prevent a user from performing a function unless the user
possesses a user role permitting that function.
The system shall support the capability to change key parameters affecting
the operation of the system without redesigning the system.
The system shall support the capability to accommodate changes in hardware
technologies without requiring major reengineering or design changes.
The system shall support the capability to accommodate changes in software
technologies without requiring major reengineering or design changes.
The system shall support the capability to accommodate changes in
processes without requiring major reengineering or design changes.
The system shall support the capability to accommodate changes in policies
without requiring major reengineering or design changes.
The system shall support the capability to accommodate changes in
personnel without requiring major reengineering or design changes.
The system shall support the capability to accommodate changes in system
locations without requiring major reengineering or design changes.
The system shall provide the capability to scale to 50 petabytes of storage
without requiring redesign of the system.
The system shall have the ability to handle additional kinds of content over
time, not limited to specific types that exist today.
The system shall provide the ability to ingest content independently of its
digital format.
The system shall provide the ability to store content independently of its digital
format.
The system shall provide the ability to deliver content independently of its
digital format.
The system shall provide support for content management lifecycle processes
for harvested, converted and deposited content.
The system shall enable GPO to tailor content-based services to suit its
customers needs and enable GPO to implement progressive improvements in
its business process over time.
The system shall enable GPO to tailor content-based services to suit its
customers needs.
The system shall enable GPO to tailor content-based services to implement
progressive improvements in business process.
The system shall assemble content and metadata files into content packages
that are compliant with open standards.
The system shall provide the capability for a content package to contain one
binding file.
The binding file of the content package shall be expressed in XML.
The binding file of the content package shall contain an inventory of all the
content files in the package.
The binding file of the content package shall contain an inventory of all the
metadata files in the package.
The binding file of the content package shall contain the relationships between
R1B; Must
R1B; Must
R1B; Must
R2; Must
R1C; Must
R1C; Must
R1C; Must
R1C; Must
R1C; Must
R1C; Must
R1C; Must
R1C; Must
R1C; Must
R1C; Must
R1C; Must
R1C; Must
R1C; Must
R1B; Must
R1B; Must
R1B; Must
R1B; Must
R2; Must
R2; Must
R3; Must
R3; Must
R1B; Must
R1B; Must
R1B; Must
R1B; Must
R1B; Must
R1B; Must

FINAL
RD-33
2.0-9.0-6
RD-34
2.0-9.0-7
RD-35
2.0-9.0-8
RD-36
RD-37
2.0-10
2.0-11
RD-38
2.0-12
RD-39
RD-42
2.0-13
2.0-14
RD-43
RD-44
3
3.1
RD-45
3.1.0-1
RD-46
3.1.0-1.0-1
RD-47
3.1.0-1.0-2
RD-48
3.1.0-1.0-3
RD-49
3.1.0-1.0-4
RD-50
3.1.0-2
RD-51
3.1.0-3
RD-52
3.1.0-4
RD-53
3.1.0-5
RD-54
3.1.0-6
RD-55
3.2
RD-56
3.2.0-1
RD-57
3.2.0-1.0-1
RD-58
3.2.0-2
the content files and metadata files in the package.

The system shall provide the capability for one or more metadata files to be
related to each content file in a content package.
The system shall provide the capability for each metadata file to be related to
one or more content files in a content package.
The system shall support the capability to transform the binding file of the
content package into other formats.
The system shall be available for use at all GPO locations.
The system is considered available when all critical system functions are
operational. The critical functions of the system are those needed to support
the submission, processing, access, and delivery of Priority 1 documents. The
rationale for this definition is to insure that the system is considered
operational when these top priority operations can be performed and not
considered operational when they can not be performed. The functions are
priority 1 document submission, pre-ingest, ingest, storage in AIP and ACP
storage, index for search, search results, and electronic presentation delivery.
This implies that the FDsys web site, workflow engine, content management
system, search engine, and storage systems are also operational.
The system shall provide the capability to maintain required response times
when there are 20,000 concurrent users performing a mix of operations that
represents peak time operational use.
The system shall support an average peak time availability of 99.7%.
The system shall provide a response to the user within 2 seconds of a user on
the GPO intranet initiating an operation.
R1B; Must
R1B; Must
R3; Must
R1C; Must
R1C; Must
R1C; Must
R1C; Must
R1C; Must
3 Requirements for Content

Metadata
3.1 Content Metadata Core Capabilities
The system shall have a central functionality which collects, edits, and shares
content metadata among the broad functions of the system.
The system shall allow authorized users to edit content metadata residing
within a SIP.
within an AIP.
within an ACP.
within WIP.
The system shall have the capability to employ multiple content metadata
schema, and to process and preserve multiple sets of content metadata for a
digital object.
The system shall provide mechanisms to share content metadata and provide
linkages and interoperability between extension schema and input standards.
The Application Programmer Interfaces of the system shall be based on open
standards
The system shall provide the capability to link content metadata with system
metadata.
The system shall provide the capability to link content metadata with business
process information.
R1B; Must
R1B; Must
R1B; Must
R1B; Must
R1B; Must
R1B; Must
R1B; Must
R1B; Must
R1B; Must
R1B; Must
3.2 Content Metadata Types

The system shall employ metadata which relates descriptive information
related to a target digital object(s) and its associated content package.
All metadata files shall be encoded in XML and conform to schema that are
adopted by FDsys.
The system shall employ metadata which relates representation information
R1B; Must
R1B; Must
R1B; Must

FINAL
RD-59
3.2.0-3
RD-60
3.2.0-3.0-1
RD-61
3.2.0-3.0-2
RD-62
3.2.0-3.0-2.0-1
RD-63
3.2.0-3.0-2.0-2
RD-64
3.2.0-3.0-3
RD-65
3.2.0-3.0-4
RD-66
3.2.0-3.0-5
RD-67
3.2.0-4
RD-68
3.2.0-5
RD-69
3.2.0-6
RD-70
3.2.0-7
RD-71
3.2.0-8
RD-72
3.3
RD-73
3.3.0-1
RD-74
3.3.0-2
RD-75
3.3.0-3
RD-76
3.3.0-3.0-1
RD-77
3.3.0-3.0-2
RD-78
3.3.0-3.0-3
RD-79
3.3.0-3.0-4
RD-80
3.3.0-3.0-5
RD-81
3.3.0-3.0-6
RD-82
3.3.0-3.0-7
RD-83
3.3.0-3.0-8
RD-84
3.3.0-3.0-9
RD-85
3.3.0-3.0-10
RD-86
3.3.0-3.0-11
RD-87
3.3.0-3.0-12

The system shall employ metadata which relates administrative information
The system shall employ metadata which relates technical information related
to a target digital object(s) and its associated content package.
The system shall employ metadata which relates the structure of a target
digital object(s) and its associated content package.
The system shall employ publication-specific metadata as required to support
existing and future publications.
The system shall employ document-specific metadata as required to support
existing and future publications
The system shall employ metadata which relates the rights information of a
target digital object(s) and its associated content package.
The system shall employ metadata which relates the source information of a
target digital object(s) and its associated content package.
The system shall employ metadata which relates the provenance information
of a target digital object(s) and its associated content package.
The system shall employ metadata which relates the Preservation Description
Information (PDI) of a target digital object(s) and its associated content
package.
The system shall employ metadata which relates the context of a digital object
and relationship to other objects.
The system shall employ metadata which relates the fixity and authority (e.g.,
official, certified, etc) of the digital object and its associated content package.
The system shall employ metadata which describes and provides reference
information about the digital object and its associated content package.
The system shall employ metadata which relates packaging information
R1B; Must
R1B; Must
R1B; Must
R1C; Must
R1C; Must
R1C; Must
R1B; Must
R1B; Must
R1B; Must
R1B; Must
R1B; Must
R1B; Must
R1B; Must
3.3 Content Metadata Schema

GPO shall adopt the most current version of the Metadata Encoding and
Transmission Standard (METS) as the encoding standard for content
packages in the system.
In general, GPO shall refer to metadata schema rather than embed data
elements in the METS wrapper.
The system shall have the capability to employ multiple established extension
schema and input standards for expressing metadata when possible.
The system shall support the capability to employ additional established
extension schema for expressing metadata in the future.
The system shall support the capability to translate metadata conforming to
registered input standards to an XML representation for storage in the system.
The system shall have the capability to employ Dublin Core version 1.1 as an
extension schema.
The system shall have the capability to employ PREMIS version 1.0 as an
extension schema.
The system shall have the capability to employ Machine Readable Cataloging
(MARC) as an input standard.
The system shall have the capability to employ Metadata Object Description
Schema (MODS) version 3.2 as an extension schema.
The system shall support the capability to employ additional input standards
for expressing metadata in the future.
The system shall have the capability to employ Encoded Archival Description
(EAD) version 2002 as an extension DTD.
The system shall have the capability to employ Text Encoding Initiative (TEI)
TEI P4 DTD as an extension DTD.
The system shall have the capability to employ Data Document Initiative (DDI)
version 2.1 as an extension DTD.
The system shall have the capability to employ Federal Geographic Data
Committee (FGDC) CSDGM Document Type Declaration as an extension
DTD.
The system shall have the capability to employ multiple established extension
schema and input standards for expressing metadata when possible,
R1B; Must
R1B; Must
R2; Must
R2; Must
R2; Must
R1B; Must
R1B; Must
R1B; Must
R1B; Must
R2; Must
R2; Could
R2; Could
R2; Could
R2; Could
R1C; Must

FINAL
RD-88
3.3.0-3.0-13
RD-89
3.3.0-3.0-14
RD-90
3.3.0-3.0-15
RD-91
3.3.0-3.0-16
RD-92
3.3.0-4
RD-93
3.3.0-5
RD-94
3.3.0-5.0-1
RD-95
3.3.0-5.0-2
RD-96
3.3.0-5.0-3
RD-97
RD-98
3.3.0-5.0-4
3.3.0-5.0-5
RD-99
3.3.0-5.0-6
RD-100
3.3.0-5.0-7
RD-103
RD-104
3.3.0-8
3.3.0-9
RD-105
RD-106
RD-107
RD-110
3.3.0-9.0-1
3.3.0-9.0-2
3.3.0-9.0-3
3.3.0-12
RD-111
3.3.0-13
RD-112
3.4
including Premis.
The system shall have the capability to employ MPEG 21 as an input
standard.
The system shall have the capability to employ JPEG 2000 as an input
standard.
The system shall have the capability to employ ONIX as an extension
schema.
The system shall have the capability to employ MIX (NISO Metadata for
Images) as an extension schema.
The system shall employ a registry of extension schema and input standards
in use.
Authorized users shall have the capability to manage the registry of schema
employed by the system.
The system shall provide the capability for users to add new XML schemas to
the Schema Registry,
The system shall provide the capability for users to remove XML schemas
from the Schema Registry,
The system shall provide the capability for users to update XML schemas in
The system shall allow users to add new XML DTDs to the Schema Registry,
The system shall provide the capability for users to remove XML DTDs from
The system shall provide the capability for users to update XML DTDs in the
Schema Registry,
The system shall provide a GUI interface for users to edit the Schema
Registry
Any schema registered in FDsys shall act as an extension schema to METS
The schema shall map to specific function(s), content type, or content formats
within the system.
The schema shall map to specific function(s).
The schema shall map to content type(s).
The schema shall map to content format(s).
The system shall provide the capability to add extension schema developed
by GPO to the Schema Registry.
Specific schema for each digital object shall be based on the specific needs of
the target digital object or content package.
R2; Should
R2; Should
R2; Must
R1C; Must
R1C; Must
R1C; Must
R1C; Must
R1C; Must
R1C; Must
R1C; Must
R1C; Must
R1C; Must
R2; Must
R1C; Must
R1C; Must
R1C; Must
R1C; Must
R1C; Must
R1C; Must
R1C; Must
3.4 Content Metadata Import and Export

RD-113
3.4.0-1
RD-114
3.4.0-1.0-1
RD-115
3.4.0-1.0-2
RD-116
3.4.0-1.0-3
RD-117
3.4.0-1.0-4
RD-118
3.4.0-2
RD-119
3.4.0-2.0-1
RD-120
3.4.0-2.0-1.0-1
RD-121
3.4.0-2.0-1.0-2
RD-122
3.4.0-2.0-1.0-3
RD-123
3.4.0-2.0-2
RD-124
3.4.0-2.0-2.0-1
The system shall have the capability to receive and record existing metadata
from sources external to the system.
The system shall have the capability to receive existing MARC metadata from
sources external to the system.
The system shall have the capability to record existing MARC metadata from
sources external to the system.
The system shall have the capability to receive existing COSATI metadata
The system shall have the capability to record existing COSATI metadata
The system shall provide the capability to deliver DIPs that contain only
metadata.
The system shall provide the capability to export metadata from a single
publication.
The system shall provide the capability to export content along with metadata
from a single publication.
The system shall provide the capability to export metadata from one or more
renditions of a single publication.
The system shall provide the capability to export one or more metadata files
from a single publication.
The system shall provide the capability to export metadata in the form of a
series of DIPs for the publications matching a user specified search.
The system shall provide the capability to export content along with metadata
from multiple publications.
R3; Must
R2; Must
R2; Must
R3; Must
R3; Must
R1C; Must
R1C; Must
R1C; Must
R1C; Must
R1C; Must
R1C; Must
R1C; Must
10

FINAL
RD-125
3.4.0-2.0-2.0-2
RD-126
3.4.0-2.0-2.0-3
RD-127
3.4.0-3
RD-128
3.5
RD-129
3.5.0-1
RD-130
3.5.0-2
RD-131
3.5.0-2.0-1
RD-132
3.5.0-2.0-2
RD-133
RD-134
3.5.0-2.0-3
3.5.0-3
RD-135
3.5.0-4
RD-136
3.5.0-5
RD-137
3.5.0-6
RD-138
RD-139
4
4.1
RD-140
4.1.0-1
RD-141
4.1.0-2
RD-142
4.2
RD-143
4.2.0-1
RD-144
4.2.0-2
RD-145
4.2.0-2.0-1
RD-146
4.3
RD-147
4.3.0-1
RD-148
4.3.0-2
RD-149
4.3.0-2.0-1
The system shall provide the capability to export metadata from one or more
renditions of multiple publications.
The system shall provide the capability to export one or more metadata files
from multiple publications.
The system shall provide the capability to transform metadata from one
standard to another prior to exporting it.
R1C; Must
R1C; Must
R2; Must
3.5 Content Metadata Management

The system shall have the ability to manage metadata regardless of its
source.
The system shall have the ability to create metadata meeting the
requirements of one or more schema.
The system shall provide the capability for an authorized user to enter
metadata.
The system shall provide the capability to transform metadata from one
standard to another.
The system shall provide the capability to extract metadata from content.
The system shall provide the capability for GPO to designate metadata
elements as mandatory.
The system shall have the capability to automatically record in system
metadata information about the actions performed by the system on content.
The system shall have the capability to automatically record in BPI information
about the actions performed by business processes on content.
The system shall log all additions, deletions, and changes to content metadata
within the system.
R1B; Must
R2; Must
R1B; Must
R2; Must
R2; Must
R1B; Must
R1B; Must
R1B; Must
R1B; Must
4 Requirements for SIP

4.1 SIP Deposited Content
The SIP for Deposited Content shall contain one or more renditions of the
publication being submitted in the SIP.
The metadata for deposited content in the SIP shall consist of fundamental
representation information, any necessary DTDs (or schema), style sheets,
and submission level metadata for each rendition.
R1B; Must
R1B; Must
4.2 SIP Harvested Content

The SIP for Harvested Content shall contain zero or more rendition consisting
of the original harvested digital objects.
The metadata for harvested content in the SIP shall consist of representation
information, documentation of harvest & transformation(s), submission level
metadata for each rendition.
The metadata for harvested content in the SIP shall include information about
the harvest process.
R1B; Must
R2; Must
R2; Must
4.3 SIP Converted Content

The SIP for Converted Content shall contain, at a minimum, a rendition
consisting of the digital object(s) as produced by the conversion process.
The SIP for converted Content shall support the inclusion of representation
information and metadata describing the conversion process for each
rendition.
The metadata for converted content in the SIP shall include full technical
information on the conversion, as specified by NISO Z 39.87-2002.
R1B; Must
R1B; Must
R1B; Must
11

FINAL
RD-150
4.4
4.4 Core SIP Requirements

RD-151
RD-152
4.4.0-1
4.4.0-1.0-1
RD-153
4.4.0-1.0-2
RD-154
4.4.0-1.0-3
RD-155
RD-156
RD-157
4.4.0-1.0-4
4.4.0-1.0-5
4.4.0-1.0-6
RD-158
4.4.0-1.0-7
RD-159
4.4.0-1.0-8
RD-160
4.4.0-1.0-9
RD-161
4.4.0-1.0-10
RD-162
4.4.0-1.0-11
RD-163
4.4.0-1.0-12
RD-164
RD-165
RD-166
RD-167
4.4.0-2
4.4.0-2.0-1
4.4.0-2.0-2
4.4.0-2.0-3
RD-168
4.4.0-2.0-4
RD-169
4.4.0-2.0-5
RD-170
RD-171
4.4.0-3
4.4.0-3.0-1
RD-172
4.4.0-3.0-2
RD-173
RD-174
4.4.0-4
4.4.0-4.0-1
RD-175
4.4.0-5
RD-176
RD-177
RD-178
4.4.0-5.0-1
4.4.0-5.0-2
4.4.0-5.0-3
RD-179
4.5
A SIP shall contain one or more renditions of one publication.

A SIP that describes a publication which only exists in tangible form shall
contain a surrogate digital object that describes its tangible expression.
A SIP shall have the capability to contain metadata indicating if the publication
it contains is in scope for GPO's dissemination programs.
Each rendition of a publication in a SIP shall be contained in its own
subdirectory of the content directory.
A rendition of a publication in a SIP shall contain one or more digital objects.
A rendition of a publication in a SIP shall contain one or more subdirectories.
Each rendition of a publication in the SIP shall contain metadata that indicates
if that rendition is a copy of the original file in which the publication was
created.
if that rendition is the highest fidelity rendition of the publication being
submitted in the SIP.
if that rendition is in a screen optimized format.
if that rendition is in a print optimized format.
if that rendition is in a press optimized format.
if that rendition is a complete representation of the publication.
if that rendition can be successfully edited using the software that created the
rendition.
A SIP shall contain a METS file named sip.xml.
The sip.xml file shall contain an inventory of all the content files in a SIP.
The sip.xml file shall contain an inventory of all the metadata files in a SIP.
The sip.xml file shall contain the relationships between the content files and
metadata files in a SIP.
related to each content file in a SIP.
one or more content files in a SIP.
A SIP shall contain one or more metadata files associated with the content.
The system shall provide the capability to store an XML schema that
describes the format of a content file in a SIP.
The system shall provide the capability to store an XML DTD that describes
the format of a content file in a SIP.
Metadata files in a SIP shall be encoded in XML.
Metadata files in a SIP shall conform to an XML Schema or XML DTD that is
registered in the FDsys Metadata Schema Registry.
The SIP specified in this document shall apply to all content types specified
and accepted by FDsys: converted, deposited and harvested.
The SIP requirements shall apply to deposited content.
The SIP requirements shall apply to converted content.
The SIP requirements shall apply to harvested content.
R1B; Must
R1B; Must
R1B; Must
R1B; Must
R1B; Must
R1B; Must
R1B; Must
R1B; Must
R1B; Must
R1B; Must
R1B; Must
R1B; Must
R1B; Must
R1B; Must
R1B; Must
R1B; Must
R1B; Must
R1B; Must
R1B; Must
R1B; Must
R1B; Must
R1B; Must
R1B; Must
R1C; Must
R2; Must
R1B; Must
R1C; Must
R1C; Must
4.5 Requirements for sip.xml File

RD-180
RD-181
RD-182
RD-183
4.5.0-1
4.5.0-2
4.5.0-3
4.5.0-3.0-1
RD-184
RD-185
4.5.0-4
4.5.0-4.0-1
The sip.xml file shall conform to the METS version 1.5.

The sip.xml file shall conform to the GPO METS Profile version 1.0.
Digital objects in the SIP shall be stored outside the sip.xml file.
Digital objects in the SIP shall be referred to in the sip.xml file using their
filename and full path relative to the root of the SIP.
Metadata files in the SIP shall be stored outside the sip.xml file.
Metadata files in the SIP shall be referred to in the sip.xml file using their
filename and full path relative to the root of the SIP.
R1B; Must
R1B; Must
R1B; Must
R1B; Must
R1B; Must
R1B; Must
12

FINAL
RD-187
4.6
4.6 Structural Layout for SIPs

RD-188
RD-189
4.6.0-1
4.6.0-1.0-1
RD-190
4.6.0-1.0-2
RD-191
4.6.0-2
RD-192
4.6.0-2.0-1
RD-194
RD-195
4.6.0-3
4.6.0-3.0-1
RD-196
4.6.0-3.0-1.0-1
RD-197
4.6.0-4
RD-198
4.6.0-4.0-1
RD-199
4.6.0-4.0-2
RD-200
4.6.0-5
RD-201
4.6.0-5.0-1
RD-202
4.7
The SIP shall contain the sip.xml at the top level of the SIP directory structure.
The SIP shall contain a directory named content at the top level of the SIP
directory structure.
The SIP shall contain a directory named metadata at the top level of the SIP
The content files for each rendition of a publication in a SIP shall be placed in
its own subdirectory under the content directory.
The folder structure of the digital objects in a rendition folder shall be recorded
in the sip.xml file.
All metadata files shall be placed in the metadata directory.
The metadata files for each rendition of a publication in a SIP shall be placed
in its own subdirectory under the metadata directory.
The metadata subdirectory for a rendition shall have the same name as the
content subdirectory for that rendition.
A SIP shall contain a least one metadata file containing descriptive metadata
for the publication that shall be considered mandatory.
The mandatory descriptive metadata file for a publication shall be stored in
MODS format.
The mandatory descriptive metadata file for a publication shall be located in
the top level directory.
Each rendition of a publication shall have one or more metadata files that
include administrative metadata about the rendition.
Each content file in a rendition shall have, at a minimum, a metadata file
specifying the file format of the content file.
R1B; Must
R1B; Must
R1B; Must
R1B; Must
R1B; Must
R1B; Must
R1B; Must
R1B; Must
R1B; Must
R1B; Must
R1B; Must
R1B; Must
R1B; Must
4.7 Packaging of SIPs

RD-203
4.7.0-1
RD-204
RD-205
4.7.0-1.0-1
4.7.0-1.0-2
RD-206
4.7.0-1.0-3
RD-207
4.7.0-1.0-4
RD-208
4.7.0-1.0-5
RD-209
4.8
The system shall provide the capability to aggregate all the files and
directories in a SIP into a single package.
The system shall provide the capability to aggregate the SIP into a ZIP file.
The system shall provide the capability to ingest into FDsys a SIP that is
aggregated in a ZIP file.
The system shall support the capability to aggregate the SIP into additional
file formats in the future.
The system shall support the capability to ingest into Fdsys a SIP that is
aggregated in additional file formats in the future.
The system shall provide the capability to support batch input of multiple
digital objects and metadata for multiple publications.
R1B; Must
R1C; Must
R1C; Must
R3; Must
R3; Must
R1C, Must
4.8 SIP Descriptive Metadata

Requirements
RD-210
4.8.0-1
RD-211
4.8.0-1.0-1
RD-212
4.8.0-1.0-2
RD-213
4.8.0-1.0-3
RD-214
4.8.0-1.0-4
RD-215
4.8.0-1.0-5
RD-216
4.8.0-2
RD-217
4.8.0-3
The system shall have the capability to store descriptive metadata in multiple
extension schema and records in the SIP.
The system shall have the capability to store descriptive metadata in ONIX
format in the SIP.
The system shall have the capability to store descriptive metadata in Dublin
Core format in the SIP.
The system shall have the capability to store descriptive metadata in PREMIS
format in the SIP.
The system shall have the capability to store descriptive metadata in COSATI
format in the SIP.
The system shall have the capability to store descriptive metadata in
additional descriptive metadata formats in the future in the SIP.
The system shall employ descriptive metadata elements in the SIP in MODS
version 3.1 format.
The system shall allow all MODS elements to be stored in the MODS file in
the SIP.
R1B; Must
R2; Must
R1B; Must
R1B; Must
R3; Must
R3; Must
R1B; Must
R1B; Must
13

FINAL
RD-218
4.8.0-3.0-1
RD-219
4.8.0-4
RD-220
4.8.0-4.0-1
RD-221
4.8.0-4.0-2
RD-222
4.8.0-4.0-3
RD-223
4.8.0-4.0-4
RD-224
4.8.0-4.0-5
RD-225
4.8.0-4.0-6
RD-226
4.8.0-4.0-7
RD-227
4.8.0-4.0-8
RD-228
4.8.0-4.0-9
RD-229
4.8.0-4.0-10
RD-230
4.8.0-4.0-11
RD-231
4.9
The system shall allow all MODS sub-elements to be stored in the MODS file
in the SIP.
The system shall verify that all mandatory MODS descriptive metadata
elements are present and valid in order for a SIP to be eligible for ingest into
FDsys.
The OriginInfo:publisher MODS descriptive metadata element shall be
considered mandatory.
The OriginInfo:dateIssued, Captured, Created, Modified, Valid, or Other
MODS descriptive metadata elements shall be considered mandatory.
The Language MODS descriptive metadata elements shall be considered
mandatory.
The Identifier MODS descriptive metadata elements shall be considered
mandatory.
The Location MODS descriptive metadata elements shall be considered
mandatory.
The PhysicalDescription:internetMediaType MODS descriptive metadata
elements shall be considered mandatory.
The PhysicalDescription:digitalOrigin MODS descriptive metadata elements
shall be considered mandatory.
The PhysicalDescription:extent MODS descriptive metadata elements shall be
The TypeOfResource MODS descriptive metadata elements shall be
The RecordInfo MODS descriptive metadata elements shall be considered
mandatory.
The TitleInfo:title MODS descriptive metadata elements shall be considered
mandatory
R1B; Must
R1B; Must
R1B; Must
R1B; Must
R1B; Must
R1B; Must
R1B; Must
R1B; Must
R1B; Must
R1B; Must
R1B; Must
R1B; Must
R1C, Must
4.9 SIP Administrative Metadata

Requirements
RD-232
4.9.0-1
RD-233
4.9.0-1.0-1
RD-234
4.9.0-1.0-2
RD-235
4.9.0-1.0-3
RD-236
4.9.0-1.0-4
RD-237
4.9.0-1.0-5
RD-238
4.9.0-1.0-6
RD-239
4.9.0-1.0-7
RD-240
4.9.0-1.0-8
RD-241
RD-242
5
5.1
The system shall support the capability for the SIP to contain administrative
metadata that conform to a METS extension schema.
The SIP shall identify the extension schema to which each administrative
metadata file conforms.
The METS extension schema identified for an administrative metadata file in
the SIP shall be registered in the Metadata Registry.
The system shall verify that each administrative metadata file in the SIP
conforms to its identified METS extension schema.
The system shall have the capability to include technical metadata about each
rendition in the SIP.
The system shall have the capability to include source metadata about each
The system shall have the capability to include rights metadata about each
The system shall have the capability to include provenance metadata about
each rendition in the SIP.
The system shall have the capability to include system metadata about each
R1B; Must
R1B; Must
R1B; Must
R1B; Must
R1B; Must
R1B; Must
R1B; Must
R1B; Must
R1B; Must
5 Requirements for AIP

5.1 AIP Core Capabilities
RD-243
RD-244
5.1.0-1
5.1.0-1.0-1
RD-245
5.1.0-1.0-2
RD-246
5.1.0-1.0-3
An AIP shall contain one or more renditions of one publication.

An AIP shall only be created for SIPs that contain a publication that is in
scope for GPOs dissemination programs.
The AIP shall provide the capability to contain a rendition of the publication in
the format in which it was created.
The system shall provide the capability for authorized users to add renditions
of a publication to an AIP.
R1B; Must
R2; Must
R1B; Must
R1B; Must
14

FINAL
RD-247
5.1.0-1.0-4
RD-248
5.1.0-2
RD-249
5.1.0-2.0-1
RD-250
RD-251
RD-252
5.1.0-2.0-2
5.1.0-2.0-3
5.1.0-2.0-4
RD-253
5.1.0-2.0-5
RD-254
5.1.0-2.0-6
RD-255
5.1.0-2.0-7
RD-256
5.1.0-2.0-8
RD-257
5.1.0-2.0-9
RD-258
5.1.0-2.0-10
RD-259
5.1.0-3
RD-260
5.1.0-4
RD-261
5.1.0-4.0-1
RD-262
5.1.0-4.0-2
RD-263
5.1.0-4.0-3
RD-264
5.1.0-5
RD-265
5.1.0-5.0-1
RD-266
5.1.0-5.0-2
RD-268
RD-269
RD-270
RD-271
5.1.0-7
5.1.0-7.0-1
5.1.0-7.0-2
5.1.0-7.0-3
RD-272
5.1.0-7.0-4
RD-273
5.1.0-7.0-5
RD-274
RD-275
5.1.0-8
5.1.0-8.0-1
RD-276
5.1.0-8.0-2
RD-277
RD-278
5.1.0-9
5.1.0-9.0-1
RD-279
5.1.0-9.0-2
RD-280
5.2
The system shall provide the capability for authorized users to delete
renditions of a publication from an AIP.
The AIP shall provide the capability to include more than one rendition of a
publication.
Each rendition of a publication in an AIP shall be contained in its own
subdirectory of the content directory.
A rendition of a publication in an AIP shall contain one or more files.
A rendition of a publication in an AIP shall contain one or more subdirectories.
Each rendition of a publication in an AIP shall contain metadata that indicates
if that rendition is a copy of the original file in which the publication was
created.
if that rendition is the highest fidelity rendition of the publication in the AIP.
if that rendition is in a screen optimized format.
if that rendition is in a print optimized format.
if that rendition is in a press optimized format.
if that rendition is a complete representation of the publication.
if that rendition can be successfully edited using the software that created the
rendition.
The AIP shall contain Representation Information metadata for every rendition
of the publication in the AIP.
The system shall support the creation of AIPs which are independent of any
particular hardware and software component.
The system shall provide the capability to add content to an AIP independent
of the contents digital format.
The system shall provide the capability to store content in an AIP independent
of the contents digital format.
The system shall provide the capability to deliver content stored in an AIP
regardless of the contents digital format.
The system shall provide the capability for authorized users to access AIPs for
the purpose of executing preservation processes or dissemination of DIPs
from AIPs.
the purpose of executing preservation processes on AIPs.
the purpose of disseminating DIPs from AIPs.
An AIP shall contain a METS file named aip.xml.
The aip.xml file shall contain an inventory of all the content files in an AIP.
The aip.xml file shall contain an inventory of all the metadata files in an AIP.
The aip.xml file shall contain the relationships between the content files and
metadata files in an AIP.
related to each content file in an AIP.
one or more content files in an AIP.
The AIP shall contain one or more metadata files associated with the content.
The system shall provide the capability to store an XML schema that
describes the format of a content file in an AIP.
The system shall provide the capability to store an XML DTD that describes
the format of a content file in an AIP.
The system shall provide the capability for authorized users to delete AIPs.
In order to delete an AIP, two authorized users shall be required to approve
the deletion.
The system shall provide a user the capability to restrict an AIP, disabling the
capability to create an ACP from it.
R1C; Must
R1B; Must
R1B; Must
R1B; Must
R1B; Must
R1B; Must
R1B; Must
R1B; Must
R1B; Must
R1B; Must
R1B; Must
R1B; Must
R1B; Must
R1B; Must
R1B; Must
R1B; Must
R1B; Must
R1B; Must
R1B; Must
R1B; Must
R1B; Must
R1B; Must
R1B; Must
R1B; Must
R1B; Must
R1B; Must
R1B; Must
R1B; Must
R1B; Must
R1C; Must
R1C; Must
R1C; Must
5.2 Requirements for aip.xml File
15

FINAL
RD-281
RD-282
RD-283
RD-284
5.2.0-1
5.2.0-2
5.2.0-3
5.2.0-3.0-1
RD-285
RD-286
5.2.0-4
5.2.0-4.0-1
RD-287
5.2.0-5
RD-288
5.3
The aip.xml file shall conform to the METS version 1.5.

The aip.xml file shall conform to the GPO METS Profile version 1.0.
Digital objects in the AIP shall be stored outside the aip.xml file.
Digital objects in the AIP shall be referred to in the aip.xml file using their
filename and full path relative to the root of the AIP.
Metadata files in the AIP shall be stored outside the aip.xml file.
Metadata files in the AIP shall be referred to in the aip.xml file using their
filename and full path relative to the root of the AIP.
A metadata file shall be associated with one or more digital objects inside the
aip.xml file.
R1B; Must
R1B; Must
R1B; Must
R1B; Must
R1B; Must
R1B; Must
R1B; Must
5.3 Structural Layout for AIPs

RD-289
RD-290
5.3.0-1
5.3.0-1.0-1
RD-291
5.3.0-1.0-2
RD-292
5.3.0-2
RD-293
5.3.0-2.0-1
RD-295
RD-296
5.3.0-3
5.3.0-3.0-1
RD-297
5.3.0-3.0-1.0-1
RD-298
5.3.0-4
RD-299
5.4
RD-300
RD-301
5.4.0-1
5.4.0-1.0-1
RD-302
5.4.0-2
RD-303
5.4.0-3
RD-304
5.4.0-3.0-1
RD-305
5.4.0-3.0-2
RD-306
5.4.0-3.0-3
RD-307
5.4.0-3.0-4
RD-308
5.4.0-3.0-5
RD-309
5.4.0-3.0-6
RD-310
RD-311
5.4.0-3.0-7
5.4.0-4
RD-312
5.4.0-5
RD-313
5.4.0-5.0-1
RD-314
5.4.0-5.0-2
RD-315
5.4.0-5.0-3
The AIP shall contain the aip.xml at the top level of the AIP directory structure.
The SIP shall contain a directory named content at the top level of the AIP
The AIP shall contain a directory named metadata at the top level of the AIP
The content files for each rendition of a publication in an AIP shall be placed
in its own subdirectory under the content directory.
The hierarchical structure of the digital objects in a rendition folder shall be
recorded in the aip.xml file.
All metadata files shall be placed in the metadata directory.
The metadata files for each rendition of a publication in an AIP shall be placed
in its own subdirectory under the metadata directory.
The metadata subdirectory for a rendition shall have the same name as the
content subdirectory for that rendition.
Each content file in a rendition shall have, at a minimum, a metadata file
specifying technical parameters of the content file.
R1B; Must
R1B; Must
R1B; Must
R1B; Must
R1B; Must
R1B; Must
R1B; Must
R1B; Must
R1B; Must
5.4 AIP Metadata

Metadata files in a SIP shall be encoded in XML.
Metadata files in an AIP shall conform to an XML Schema or XML DTD that is
registered in the Fdsys Metadata Schema Registry.
The AIP shall include preservation metadata to record preservation
processes, from ingest into the repository through disposal.
The system shall store descriptive metadata elements in the AIP in MODS
version 3.1 format.
The system shall have the capability to store descriptive metadata in ONIX
format in the AIP.
The system shall have the capability to store descriptive metadata in Dublin
Core format in the AIP.
The system shall have the capability to store descriptive metadata in PREMIS
format in the AIP.
The system shall have the capability to store descriptive metadata in COSATI
format in the AIP.
The system shall have the capability to store descriptive metadata in MODS
format in the AIP.
The system shall have the capability to store descriptive metadata in
additional descriptive metadata formats in the future in the AIP.
The AIP shall incorporate all descriptive metadata elements from the SIP.
The AIP shall include metadata that expresses Preservation Description
Information (PDI) according to the PREMIS Data Dictionary and extension
schema which implement it.
The system shall support the capability for the AIP to contain administrative
metadata that conform to a METS extension schema.
The AIP shall identify the METS extension schema to which each
administrative metadata file conforms.
the AIP shall be registered in the Metadata Registry.
The system shall verify that each administrative metadata file in the AIP
R1B; Must
R1C; Must
R1C; Must
R1B; Must
R2; Must
R1B; Must
R1B; Must
R3; Must
R1B; Must
R3; Must
R1B; Must
R1C; Must
R1B; Must
R1B; Must
R1B; Must
R1B; Must
16

FINAL
RD-316
5.4.0-5.0-4
RD-317
5.4.0-5.0-5
RD-318
5.4.0-5.0-6
RD-319
5.4.0-5.0-7
RD-320
5.4.0-5.0-8
RD-321
5.5
RD-322
5.5.0-1
RD-323
RD-324
6
6.1

The AIP shall have the capability to include Preservation Description
Information (PDI) about each rendition included in the AIP.
rendition in the AIP.
each rendition in the AIP.
R1B; Must
R1B; Must
R1C; Must
R1B; Must
R1B; Must
5.5 AIP Unique ID

The AIP shall include the unique identification number assigned to the content
in the SIP.
R1B; Must
6 Requirements for ACP

6.1 ACP Core Capabilities
RD-325
RD-326
6.1.0-1
6.1.0-1.0-1
RD-327
6.1.0-1.0-2
RD-328
6.1.0-1.0-3
RD-329
6.1.0-1.0-4
RD-330
6.1.0-1.0-5
RD-331
6.1.0-1.0-6
RD-332
RD-333
6.1.0-2
6.1.0-2.0-1
RD-334
6.1.0-2.0-2
RD-335
6.1.0-2.0-3
RD-337
6.1.0-3
RD-338
6.1.0-4
RD-339
6.1.0-5
RD-340
6.1.0-6
RD-341
RD-344
6.1.0-7
6.1.0-10
RD-345
6.1.0-11
RD-346
6.1.0-11.0-1
RD-347
6.1.0-11.0-2
An ACP shall contain copies of one or more renditions of one publication.

The system shall provide the capability for authorized users to add renditions
of a publication to an ACP.
The ACP shall have the capability to be retained in the system for period of
time as is indicated in metadata.
The system shall provide the user the capability to alter the length of time to
retain an ACP in the system.
The system shall provide the capability for an authorized user to transform
renditions of ACPs.
The system shall create an ACP from its corresponding AIP when the AIP is
accessed at a rate more than a user configurable frequency.
The system shall provide the capability for authorized users to delete
renditions of a publication from an ACP.
The ACP shall have the capability to include the following:
The ACP shall have the capability to include renditions of publications that are
not in scope of GPOs dissemination programs.
The ACP shall have the capability to include renditions derived from AIP
renditions.
The system shall create one or more access derivative renditions for an ACP
if its corresponding AIP has no access derivative renditions.
The ACP shall have the capability to contain one content unit (e.g.,
publication, report, issue, bill, document, volume) that may consist of one or
more digital objects.
The ACP shall have the capability to include all digital objects included in its
corresponding AIP.
The ACP shall contain a copy of the metadata files for each rendition which
was copied from its corresponding AIP.
The access time for an ACP shall be as less than or equal to the access time
for its corresponding AIP.
The ACP shall have the capability to replicate the structural layout of an AIP.
The ACP shall have the capability to be linked to one AIP, known as its
corresponding AIP.
The ACP shall have the capability to include copies of one or more renditions
from its corresponding AIP.
The ACP shall include copies of renditions from its corresponding AIP based
on business rules.
The ACP shall have the capability to include copies of all renditions from its
corresponding AIP whose metadata indicates they are screen optimized
renditions.
R1C; Must
R1C; Must
R1C; Must
R2; Must
R2; Must
R2; Must
R1C; Must
R1C; Must
R1C; Must
R1C; Must
R2; Must
R1C; Must
R1C; Must
R1C; Must
R1C; Must
R1C; Could
R1C; Must
R1C; Must
R1C; Must
R1C; Must
17

FINAL
RD-348
6.1.0-11.0-3
RD-349
6.1.0-11.0-4
RD-350
6.1.0-12
RD-351
6.2
corresponding AIP whose metadata indicates they are press optimized
renditions.
corresponding AIP whose metadata indicates they are print optimized
renditions.
The system provide the capability for authorized users to delete entire ACPs.
R1C; Must
R1C; Must
R1C; Must
6.2 ACP Binding Metadata File

RD-352
RD-353
RD-354
RD-355
RD-356
6.2.0-1
6.2.0-1.0-1
6.2.0-1.0-1.0-1
6.2.0-1.0-2
6.2.0-1.0-3
RD-357
6.2.0-1.0-4
RD-358
6.3
RD-359
RD-361
6.3.0-1
6.3.0-3
RD-363
6.3.0-5
RD-364
6.3.0-5.0-1
RD-365
6.3.0-5.0-2
RD-366
6.3.0-5.0-3
RD-367
6.3.0-5.0-4
RD-368
6.3.0-5.0-5
RD-369
6.3.0-5.0-6
RD-370
6.3.0-6
RD-371
6.3.0-7
RD-372
6.3.0-8
RD-373
6.3.0-8.0-1
RD-374
6.3.0-8.0-2
RD-375
6.3.0-8.0-3
RD-376
6.3.0-8.0-4
RD-377
6.3.0-8.0-5
RD-378
6.3.0-8.0-6
RD-379
6.3.0-8.0-7
RD-380
6.3.0-9
An ACP shall have the capability to contain a METS file named acp.xml.
The acp.xml file shall conform to the METS version 1.5.
The acp.xml file shall conform to the GPO METS Profile version 1.0.
Digital objects in the ACP shall be stored outside the acp.xml file.
The system shall provide the capability to include metadata files as required to
support access and delivery
The system shall provide the capability to associate metadata files with one or
more digital objects in the ACP.
R1C; Must
R1C; Must
R1C; Must
R1C; Must
R1C; Must
R1C; Must
6.3 ACP Metadata

Metadata files in an ACP shall be encoded in XML.
The system shall provide the capability to add structural and descriptive
metadata for digital objects at a level of granularity that facilitates access.
The system shall have the capability to use descriptive metadata extension
schema to support access to publications.
The system shall provide the capability to use descriptive metadata in MODS
format to support access to publications.
The system shall provide the capability to use descriptive metadata in ONIX
format to support access to publications.
The system shall provide the capability to use descriptive metadata in Dublin
Core format to support access to publications.
The system shall provide the capability to use descriptive metadata in
PREMIS format to support access to publications.
The system shall provide the capability to use descriptive metadata in
COSATI format to support access to publications.
The system shall support the capability to use additional descriptive metadata
formats in the future to support access to publications.
The ACP shall have the capability to include mandatory descriptive metadata
elements from the AIP and SIP.
The ACP shall have the capability to refer to extension schema for additional
structural metadata as appropriate to the class of object and as necessary for
access and delivery.
The ACP shall contain administrative metadata that conform to a METS
extension schema
The ACP shall identify the METS extension schema to which each
administrative metadata file conforms.
the ACP shall be registered in the Metadata Registry.
The system shall verify that each administrative metadata file in the ACP
rendition in the ACP.
each rendition in the ACP.
The system shall provide the capability to generate metadata that enables
access to special publications at a level of granularity less than a single
publication.
R1C; Must
R1C; Must
R1C; Must
R1B; Must
R2; Must
R1B; Must
R1B; Must
R3; Must
R3; Must
R1C; Must
R1C; Must
R1C; Must
R1C; Must
R1C; Must
R1C; Must
R1C; Must
R1C; Must
R1C; Must
R1C; Must
R1C; Must
18

FINAL
RD-381
6.3.0-9.0-1
RD-382
RD-383
7
7.1
RD-384
RD-385
7.1.0-1
7.1.0-1.0-1
RD-386
7.1.0-1.0-2
RD-387
7.1.0-1.0-3
RD-388
7.1.0-1.0-4
RD-389
7.1.0-1.0-5
RD-390
7.1.0-1.0-6
RD-391
7.1.0-2
RD-392
7.1.0-3
RD-393
7.1.0-4
RD-394
7.1.0-5
RD-395
7.1.0-6
RD-396
RD-397
7.1.0-7
7.1.0-8
RD-398
7.1.0-8.0-1
RD-399
7.1.0-8.0-2
RD-400
7.1.0-8.0-3
RD-401
7.1.0-8.0-4
RD-402
7.1.0-8.0-5
RD-403
7.1.0-8.0-6
RD-405
7.1.0-10
RD-406
7.1.0-11
RD-408
7.2
The ACP shall have the capability to include the unique ID assigned to the
SIP and AIP in metadata.
R1C; Must
7 Requirements for DIP

7.1 DIP Core Capabilities
The system shall create a DIP in response to a user request for a publication.
A DIP shall provide the capability to contain copies of one or more renditions
of one publication.
A DIP shall provide the capability to contain copies of the metadata about
each rendition it contains.
The system shall copy content and metadata to a DIP from the publications
ACP.
The system shall copy content and metadata to a DIP from the publications
AIP when the information needed is not present in the ACP.
The system shall provide the capability to generate screen optimized versions
of renditions for inclusion in the DIP.
A DIP created for a service provider shall have the capability to contain the
order information for the publication.
The DIP shall have the capability to include transient copies of digital objects
that are optimized for delivery from the system.
The DIP shall have the capability to contain one content unit (e.g., publication,
report, issue, bill, document, volume) that may consist of one or more digital
objects.
The DIP shall have the capability to refer to or embed one or more metadata
files associated with the content.
The DIP shall have the capability to refer to or embed one or more digital
objects associated with metadata.
The system shall provide the capability to deliver DIPs that only include
content metadata.
The DIP shall have the capability to be an exact replica of the AIP.
The DIP Metadata shall have the capability to include descriptive, structural,
technical, administrative, and packaging metadata necessary for delivery from
the system.
The DIP Metadata shall have the capability to include descriptive metadata
necessary for delivery from the system.
The DIP Metadata shall have the capability to include structural metadata
The DIP Metadata shall have the capability to include technical metadata
The DIP Metadata shall have the capability to include administrative metadata
The DIP Metadata shall have the capability to include packaging metadata
The DIP Metadata shall have the capability to include system metadata
The system shall have the capability to assemble optimally packaged DIPs
based on the content type desired by the user.
The system shall provide the capability to deliver DIPs that only include one or
more digital objects.
R1B; Must
R1B; Must
R1B; Must
R1B; Must
R1B; Must
R1C; Must
R1C; Must
R1B; Must
R1B; Must
R1B; Must
R1B; Must
R1B; Must
R1B; Must
R1B; Must
R1B; Must
R1B; Must
R1B; Must
R1B; Must
R1B; Must
R1B; Must
R1C; Must
R1C; Must
7.2 DIP Binding Metadata File

RD-409
RD-410
RD-411
RD-412
7.2.0-1
7.2.0-1.0-1
7.2.0-1.0-1.0-1
7.2.0-1.0-2
RD-413
7.2.0-1.0-2.0-1
A DIP shall provide the capability to contain a METS file named dip.xml.
The dip.xml file shall conform to the METS version 1.5.
The dip.xml file shall conform to the GPO METS Profile version 1.0.
The system shall provide the capability to refer to digital objects (e.g., XML,
OCR-ed text) as required to support delivery.
The system shall provide the capability to embed digital objects (e.g., XML,
R1B; Must
R1B; Must
R1B; Must
R1B; Must
R2; Must
19

FINAL
RD-414
7.2.0-1.0-3
RD-415
7.2.0-1.0-3.0-1
RD-416
7.2.0-1.0-4
RD-417
7.3
OCR-ed text) as required to support delivery

The system shall provide the capability to refer to metadata files (e.g., MARC,
ONIX, Dublin Core, MODS) as required to support delivery.
The system shall provide the capability to embed metadata files (e.g., MARC,
ONIX, Dublin Core, MODS) as required to support delivery.
The system shall provide the capability to associate content metadata files
with one or more digital objects in the DIP.
R1B; Must
R2; Must
R1B; Must
7.3 DIP Metadata

RD-418
7.3.0-1
RD-420
7.3.0-3
RD-421
RD-422
7.3.0-4
7.3.0-4.0-1
RD-423
7.3.0-4.0-2
RD-424
7.3.0-4.0-3
RD-425
7.3.0-4.0-4
RD-426
7.3.0-4.0-5
RD-427
7.3.0-4.0-6
RD-430
7.3.0-7
RD-431
7.3.0-8
RD-432
7.3.0-9
RD-433
7.3.0-10
RD-434
7.3.0-11
RD-435
RD-436
8
8.1
The system shall have the capability to encode metadata files in XML and
conform to schema that are adopted by Fdsys, according to Fdsys Content
Metadata requirements.
The DIP shall have the capability to include mandatory descriptive metadata
elements from the SIP, ACP, and AIP.
The system shall provide the capability to copy descriptive metadata to a DIP.
The system shall provide the capability to copy descriptive metadata in MODS
format to a DIP.
The system shall provide the capability to copy descriptive metadata in ONIX
format to a DIP.
The system shall provide the capability to copy descriptive metadata in Dublin
Core format to a DIP.
The system shall provide the capability to copy descriptive metadata in
PREMIS format to a DIP.
The system shall provide the capability to copy descriptive metadata in
COSATI format to a DIP.
The system shall support the capability to copy additional descriptive
metadata formats to the DIP in the future.
The DIP shall have the capability to include Business Process Information,
including information collected about orders from the CO Ordering function
and requests made by end users.
The system shall provide the capability to include information generated as a
result of Content Originator ordering.
The system shall provide the capability to include information generated as a
result of a user request.
The DIP shall have the capability to include the unique ID for any content or
metadata being delivered in the DIP.
The system shall provide the capability to support the Open Archives Initiative
Metadata Harvesting Protocol version (TBD-434A).
R1B; Must
R1B; Must
R1B; Must
R1B; Must
R2; Must
R2; Must
R2; Must
R3; Must
R3; Must
R1B; Must
R1B; Must
R1B; Must
R1C; Must
R3; Must
8 Requirements for Pre-ingest

Processes
8.1 Pre-ingest Processing
RD-437
8.1.0-1
RD-438
RD-439
RD-440
RD-441
8.1.0-2
8.1.0-3
8.1.0-4
8.1.0-5
RD-442
RD-443
RD-444
RD-445
8.1.0-6
8.1.0-7
8.1.0-8
8.1.0-9
RD-446
8.1.0-9.0-1
The system shall have the capability to read registered metadata schema to
extract metadata for use by the system.
The system shall accept content from Content Originators.
The system shall accept jobs from Content Originator ordering.
The system shall accept deposited content created without using style tools.
The system shall accept deposited content created using style tools.
The system shall accept converted content.
The system shall accept harvested content.
The system shall have the capability to apply version control.
The system shall detect duplicate content in the system and notify authorized
users.
The system shall determine if the version of content is already in the system,
using, at a minimum: Version Information, bibliographic information,
R1B; Must
R1B; Must
R1B; Must
R1B; Must
R2; Could /
R3; Must
R1B; Must
R1B; Must
R1B; Must
R1B; Must
R1B; Must
20

FINAL
RD-447
8.1.0-9.0-1.0-1
RD-448
8.1.0-9.0-1.0-2
RD-449
8.1.0-9.0-1.0-3
RD-450
RD-451
RD-452
RD-453
RD-454
8.1.0-9.0-1.0-4
8.1.0-9.0-2
8.1.0-9.0-2.0-1
8.1.0-9.0-2.0-2
8.1.0-10
RD-455
RD-456
8.1.0-11
8.1.0-11.0-1
RD-457
RD-458
RD-459
8.1.0-11.0-2
8.1.0-12
8.1.0-13
RD-460
8.1.0-14
RD-461
RD-462
8.1.0-15
8.1.0-15.0-1
RD-463
8.1.0-15.0-2
RD-464
8.1.0-15.0-3
RD-465
8.1.0-15.0-4
RD-466
8.1.0-15.0-5
RD-467
RD-468
RD-469
RD-470
8.1.0-16
8.1.0-17
8.1.0-18
8.1.0-18.0-1
RD-471
8.1.0-18.0-2
RD-472
8.1.0-19
RD-473
8.1.0-20
RD-474
8.1.0-21
RD-475
RD-476
8.1.0-22
8.1.0-23
RD-477
8.1.0-24
RD-407
8.1.0-25
RD-478
RD-479
9
9.1
authentication information, content (e.g., hashes)

The system shall determine if the version of content is already in the system
using version information.
using bibliographic information.
based on its content.
The system shall have the capability to detect near duplicate documents.
The system shall have the capability to reject duplicate content.
The system shall notify users when duplicate content is detected.
The system shall notify users when near duplicate content is detected.
The system shall have the capability to store content in WIP before job order
information is received.
The system shall have the capability to assign a unique ID to content.
The system shall have the capability to assign a unique ID to content
packages.
The system shall have the capability to assign a unique ID to digital objects.
The system shall have the capability to assign a unique ID to jobs.
The system shall populate the Identifier field in the corresponding MODS
record with the content unique ID.
The system shall link related jobs, business process information (BPI), and
content.
The system shall allow Content Evaluators to make scope determinations.
The system shall have the capability to make automatic scope determinations
based on metadata.
based on BPI
based on content.
The system shall allow users to modify the criteria by which the system makes
automatic scope determinations.
The system shall provide a GUI interface for users to modify the criteria for
automatic scope determinations
The system shall have the capability to perform integrity checking.
The system shall have the capability to apply a digital time stamp to content.
The system shall have the capability to perform accessibility assessments.
The system shall have the capability to allow users to manually perform 508
accessibility assessments on content.
The system shall have the capability to automatically perform 508 accessibility
assessments on content.
The system shall have the capability to support the creation of a pre-ingest
bundle (PIB).
The system shall have the capability to accept modified packages from the
Service Provider after publisher approval.
The system shall have the capability to accept modified digital objects from
the Service Provider after publisher approval.
The system shall accept publisher approval information for SIP creation.
The system shall have the capability to assemble content and metadata to
create SIPs.
The system shall have the capability to create a log of all transactions and
activities.
The system shall have the capability to make automatic scope determinations.
R1B; Must
R1B; Must
R1B; Must
R3; Must
R1B; Must
R1B; Must
R3; Must
R1B; Must
R1B; Must
R1B; Must
R1B; Must
R1B; Must
R1B; Must
R1B; Must
R1B; Must
R1C; Must
R1C; Must
R3; Must
R1C; Must
R2; Must
R1B; Must
R1B; Must
R2; Must
R1B; Must
R2; Must
R1C; Must
R1C; Must
R1C; Must
R1B; Must
R1B; Must
R1B; Must
R1C; Must
9 Requirements for Ingest

Processing
9.1 Ingest Processing Core Capabilities
RD-480
RD-481
9.1.0-1
9.1.0-1.0-1
Ingest processing performs the following functions:

Accept and validate SIPs
R1B; Must
21

FINAL
RD-482
RD-483
RD-484
RD-485
RD-486
9.1.0-1.0-1.0-1
9.1.0-1.0-1.0-2
9.1.0-1.0-2
9.1.0-1.0-3
9.1.0-1.0-4
RD-487
9.2
Ingest processing shall accept SIPs.

Ingest Processing shall validate SIPs.
Ingest processing shall have the capability to create AIPs from SIPs.
Ingest Processing shall have the capability to create ACPs from SIPs.
Ingest Processing shall apply a digital time stamp to content. Clarification:
This item is meant to refer to recording a timestamp in metadata whenever
content is received.
R1B; Must
R1B; Must
R1B; Must
R1B; Must
R1B; Must
9.2 Ingest Processing

RD-488
9.2.0-1
RD-489
9.2.0-2
RD-490
9.2.0-3
RD-491
9.2.0-3.0-1
RD-492
9.2.0-4
RD-493
9.2.0-4.0-1
RD-494
RD-495
RD-497
RD-498
RD-499
9.2.0-4.0-2
9.2.0-4.0-3
9.2.0-5
9.2.0-5.0-1
9.2.0-5.0-1.0-1
RD-500
9.2.0-6
RD-501
9.2.0-7
RD-502
9.2.0-8
RD-503
9.2.0-9
RD-506
9.2.0-12
RD-507
RD-508
10
10.1
The system shall have the capability to transform textual content metadata
into XML.
The system shall support the capability to conform to future requirements for
SIP validation.
The system shall allow authorized users to submit content to ingest once
content has been approved for release by the publisher.
The system shall provide a prompt to confirm that the user intends to submit
the SIP to ingest.
The system shall validate that SIPs conform to requirements for a system
compliant SIP.
The system shall verify that the SIP includes all mandatory metadata
elements.
The system shall verify that the METS file is valid.
The system shall verify that at least one digital object is present.
The system shall provide the capability to reject non-conforming SIPs.
The system shall direct exceptions to authorized users.
The system shall provide the capability for authorized users to process SIPs
to conform to SIP validation.
The system shall provide the capability to notify users that a SIP is
nonconforming.
The system shall provide the capability to notify users of the reasons a SIP is
nonconforming.
The system shall verify the file format of a digital object by a means other than
mime type or file extension.
The system shall have the capability to verify content integrity (e.g.,
checksum).
The system shall have the capability to create a log of all transactions and
activities.
R2; Must
R3; Must
R1B; Must
R1B;
Should
R1B; Must
R1B; Must
R1B; Must
R1B; Must
R1B; Must
R1B; Must
R1B; Must
R1B; Must
R1B; Must
R1C; Must
R1B; Must
R1B; Must
10 Requirements for Preservation

Processing
10.1 Preservation Processing Core
Capabilities
RD-509
10.1.0-1
RD-510
10.1.0-1.0-1
RD-511
10.1.0-1.0-1.0-1
RD-512
10.1.0-1.0-1.0-2
RD-513
10.1.0-2
RD-515
10.1.0-3
The system shall have the ability to store AIPs in a preservation repository
environment.
AIPs shall remain free from corruption and remain accessible as GPO
undergoes changes in information technology and infrastructure.
AIPs shall remain free from corruption as GPO undergoes changes in
information technology and infrastructure.
AIPs shall remain accessible as GPO undergoes changes in information
technology and infrastructure.
The system shall manage preservation processes, including scheduled
assessments and resulting actions, based on the attributes of the digital
objects and apply the specified processes.
The system shall maintain the integrity of content throughout preservation
processes.
R1B; Must
R1B; Must
R1B; Must
R1B; Must
R2; Must
R2; Must
22

FINAL
RD-516
10.1.0-3.0-1
RD-517
10.1.0-4
RD-518
10.1.0-4.0-1
RD-519
10.1.0-5
RD-520
10.1.0-5.0-1
RD-521
10.1.0-5.0-2
RD-522
10.1.0-5.0-3
RD-523
10.1.0-5.0-3.0-1
RD-525
10.1.0-6.0-1
RD-526
10.1.0-7
RD-527
10.1.0-7.0-1
RD-528
10.1.0-7.0-2
RD-529
10.1.0-7.0-3
RD-530
10.1.0-7.0-4
RD-531
10.2
The system shall ensure content is fully intelligible and unchanged in meaning
and representation, compared to the original AIP, when a digital object goes
through preservation processes
The system shall preserve essential behaviors of digital content when a digital
object goes through a preservation process.
The system shall maintain content functionality associated with content
presentation when a digital object goes through a preservation process.
The system shall preserve significant properties and attributes of digital
content as a digital object goes through a preservation process.
The system shall maintain content structure when a digital object goes
through a preservation process
The system shall maintain content structure when a digital object goes
through a preservation process.
The system shall maintain hyperlinks to content within the target document
when a digital object goes through a preservation process.
The system shall have the capability to notify users that they are leaving
GPOs website when a user selects a hyperlink that takes them to an external
site.
The system shall have the capability to produce DIPs which are interoperable
with other OAIS-based repositories.
The system shall be capable of scheduling or executing preservation
processes on individual AIPs or on selected groups of archival content.
The system shall be capable of scheduling preservation processes on
individual AIPs.
The system shall be capable of scheduling preservation processes on
selected groups of archival content.
The system shall be capable of executing preservation processes on
individual AIPs.
The system shall be capable of executing preservation processes on selected
groups of archival content.
R2; Must
R2; Must
R2; Must
R2; Must
R2; Must
R2; Must
R2; Must
R2; Must
R1C; Could
/ R2; Must
R2; Must
R2; Must
R2; Must
R2; Must
R2; Must
10.2 Preservation Processing

RD-532
10.2.0-1
RD-533
10.2.0-2
RD-534
10.2.0-3
RD-535
10.2.0-3.0-1
RD-536
10.2.0-3.0-2
RD-537
10.2.0-3.0-3
RD-538
10.2.0-3.0-4
RD-539
10.2.0-3.0-5
RD-540
10.2.0-3.0-6
RD-541
10.2.0-3.0-7
RD-542
10.2.0-3.0-8
RD-543
10.2.0-4
RD-544
10.2.0-4.0-1
The system shall have the capability to transform digital object(s) into a digital
object of another format.
The system shall have the ability to migrate data to formats other than those
in which the files were created or received.
The system shall support the transformation of Quark digital objects as
defined below:
The system shall ensure that the files resulting from migrations will be in a
format free of proprietary restrictions to the possible extent.
The system shall have the ability to verify that a file migrated from one format
to another retains specified attributes and behaviors, i.e. is authentic and
faithful.
The system shall support the transformation of Quark digital objects in
previous versions of Quark into Quark digital objects of the current shipping
version of Quark as of 10-13-06.
The system shall support the transformation of Quark digital objects into
HTML digital objects.
The system shall support the transformation of Quark digital objects into
ASCII digital objects.
The system shall support the transformation of Quark digital objects into XML
digital objects.
The system shall support the transformation of Quark digital objects into PDF
digital objects.
The system shall support the ability to set parameters of the output file of the
transformation (resolution, color depth, etc).
The system shall support the transformation of InDesign digital objects as
defined below:
The system shall support the transformation of InDesign digital objects in
previous versions of InDesign into InDesign digital objects of the current
shipping version of InDesign as of 10-13-06.
R3; Must
R2; Must
R2; Must
R1C;
Should /
R2; Must
R2; Must
R2; Must
R2; Must
R2; Must
R2; Must
R2; Must
R2; Must
R2; Must
R2; Must
23

FINAL
RD-545
10.2.0-4.0-2
RD-546
10.2.0-4.0-3
RD-547
10.2.0-4.0-4
RD-548
10.2.0-4.0-5
RD-549
10.2.0-5
RD-550
10.2.0-5.0-1
RD-551
10.2.0-5.0-2
RD-552
10.2.0-5.0-3
RD-553
10.2.0-5.0-4
RD-554
10.2.0-5.0-5
RD-555
10.2.0-5.0-6
RD-557
10.2.0-5.0-7
RD-558
10.2.0-5.0-7.0-1
RD-559
10.2.0-5.0-7.0-2
RD-556
10.2.0-6
RD-560
10.2.0-6.0-1
RD-561
10.2.0-6.0-2
RD-562
10.2.0-6.0-3
RD-563
10.2.0-6.0-4
RD-564
10.2.0-6.0-5
RD-565
10.2.0-6.0-6
RD-566
10.2.0-7
RD-567
10.2.0-7.0-1
RD-568
10.2.0-7.0-2
RD-569
10.2.0-7.0-3
RD-570
10.2.0-7.0-4
RD-571
10.2.0-7.0-5
RD-572
10.2.0-7.0-6
RD-573
10.2.0-8
RD-574
10.2.0-8.0-1
The system shall support the transformation of InDesign digital objects into
XML digital objects.
PDF digital objects.
The system shall support the transformation of Microsoft Word digital objects
as defined below:
in previous versions of Microsoft Word into Microsoft Word digital objects of
the current shipping version of Microsoft Word as of 10-13-06.
into HTML digital objects.
into ASCII digital objects.
into XML digital objects.
into PDF digital objects.
into Open Document digital objects.
The system shall have the ability to produce notification of incomplete or
unsuccessful migrations.
The system shall have the ability to identify incomplete or unsuccessful
migrations.
unsuccessful migrations.
The system shall support the transformation of Microsoft Excel digital objects
as defined below:
in previous versions of Microsoft Excel into Microsoft Excel digital objects of
the current shipping version of Microsoft Excel as of 10-13-06.
into HTML digital objects.
into ASCII digital objects.
into XML digital objects.
into PDF digital objects.
into Open Document digital objects.
The system shall support the transformation of Microsoft PowerPoint digital
objects as defined below:
objects in previous versions of Microsoft PowerPoint into Microsoft
PowerPoint digital objects of the current shipping version of Microsoft
PowerPoint as of 10-13-06.
objects into HTML digital objects.
objects into ASCII digital objects.
objects into XML digital objects.
objects into PDF digital objects.
objects into Open Document digital objects.
The system shall support the transformation of PDF digital objects as defined
below:
The system shall support the transformation of PDF digital objects in previous
versions of PDF into PDF digital objects of the current shipping version of
PDF as of 10-13-06.
R2; Must
R2; Must
R2; Must
R2; Must
R2; Must
R2; Must
R2; Must
R2; Must
R2; Must
R2; Must
R2; Must
R2; Must
R2; Must
R2; Must
R2; Must
R2; Must
R2; Must
R2; Must
R2; Must
R2; Must
R2; Must
R2; Must
R2; Must
R2; Must
R2; Must
R2; Must
R2; Must
R2; Must
R2; Must
R2; Must
24

FINAL
RD-575
10.2.0-8.0-2
RD-576
10.2.0-8.0-3
RD-577
10.2.0-8.0-4
RD-578
10.2.0-8.0-5
RD-579
10.2.0-8.0-6
RD-580
10.2.0-9
RD-581
10.2.0-9.0-1
RD-582
10.2.0-9.0-2
RD-583
10.2.0-9.0-3
RD-584
10.2.0-10
RD-585
10.2.0-10.0-1
RD-586
10.2.0-10.0-2
RD-587
10.2.0-10.0-3
RD-588
10.2.0-10.0-4
RD-589
10.2.0-10.0-5
RD-590
10.2.0-10.0-6
RD-591
10.2.0-11
RD-592
10.2.0-12
RD-593
10.2.0-13
RD-594
10.2.0-14
RD-595
10.2.0-14.0-1
RD-596
10.2.0-14.0-2
RD-597
10.2.0-14.0-3
RD-598
10.2.0-14.0-4
RD-599
10.2.0-14.0-5
RD-600
10.2.0-14.0-6
RD-601
10.2.0-15
RD-602
10.2.0-15.0-1
RD-603
10.2.0-15.0-2
RD-604
10.2.0-15.0-3
The system shall support the transformation of PDF digital objects into HTML
digital objects.
The system shall support the transformation of PDF digital objects into ASCII
digital objects.
The system shall support the transformation of PDF digital objects into XML
digital objects.
The system shall support the transformation of HTML digital objects into PDF
digital objects.
The system shall support the transformation of HTML digital objects into
XHTML digital objects.
The system shall support the transformation of HTML digital objects as
defined below:
The system shall support the transformation of HTML digital objects in
previous versions of HTML into HTML digital objects of the current version of
HTML as of 10-13-06.
The system shall support the transformation of HTML digital objects into
The system shall support the transformation of HTML digital objects into XML
digital objects.
The system shall support the transformation of TIFF digital objects as defined
below:
The system shall support the transformation of TIFF digital objects in previous
versions of TIFF into TIFF digital objects of the current version of TIFF as of
10-13-06.
The system shall support the transformation of the full text index of any TIFF
digital object into an ASCII digital object.
digital object into an XML digital object.
digital object into an HTML digital object.
The system shall support the transformation a TIFF digital object into a JPG
digital object.
digital object into an PDF digital object.
The system shall provide an interface to integrate transforming technologies
as required.
Where formats containing images are transformed to formats that do not
support images (e.g. ASCII, XML) the descriptive text of said images, if any,
will be stored in the new format.
Where formats containing images are transformed to XML the placement of
said images, if any, will be stored in the new format
The system shall support the transformation of WordPerfect digital objects as
defined below:
The system shall support the transformation of WordPerfect digital objects in
previous versions of WordPerfect into WordPerfect digital objects of the
current shipping version of WordPerfect as of as of 10-13-06.
The system shall support the transformation of WordPerfect digital objects into
Microsoft Word digital objects.
XML digital objects.
PDF digital objects.
The system shall support the transformation of EPS digital objects as defined
below:
The system shall support the transformation of EPS digital objects in previous
versions of EPS into EPS digital objects of the current version of EPS as of as
of 10-13-06.
The system shall support the transformation of the full text index of any EPS
digital object into an ASCII digital object
digital object into an XML digital object
R2; Must
R2; Must
R2; Must
R2; Must
R2; Must
R2; Must
R2; Must
R2; Must
R2; Must
R2; Must
R2; Must
R2; Must
R2; Must
R2; Must
R2; Must
R2; Must
R1B; Must
R2; Must
R2; Must
R2; Must
R2; Must
R2; Must
R2; Must
R2; Must
R2; Must
R2; Must
R2; Must
R2; Must
R2; Must
R2; Must
25

FINAL
RD-605
10.2.0-15.0-4
RD-606
10.2.0-15.0-5
RD-607
10.2.0-16
RD-608
RD-609
10.2.0-17
10.2.0-17.0-1
RD-610
10.2.0-17.0-2
RD-611
10.2.0-17.0-3
RD-612
10.2.0-18
RD-613
10.2.0-19
RD-614
RD-615
10.2.0-20
10.2.0-20.0-1
RD-616
10.2.0-20.0-2
RD-617
10.2.0-20.0-3
RD-618
10.2.0-20.0-3.0-1
RD-619
10.2.0-20.0-3.0-2
RD-620
10.2.0-21
RD-621
10.2.0-21.0-1
RD-622
RD-623
10.2.0-22
10.2.0-23
RD-624
10.3
digital object into an HTML digital object
digital object into an PDF digital object
The system shall support the transformation of JPG digital objects in previous
versions of JPG into JPG digital objects of the current version of JPG as of
10-13-06.
The system shall support the transformation of XML as defined below:
The system shall support the transformation of XML digital objects into other
registered XML digital objects.
The system shall support the transformation of XML metadata into other
registered XML metadata.
The system shall support the transformation of system metadata into other
registered XML metadata.
The system shall have the capability to perform transformations without
deleting the content that has been acted upon.
The system shall provide the capability to apply quality metrics to format
transformations.
The system shall ensure content submitted is not changed by refreshment.
The system shall have the ability to verify that the refreshed file is authentic
and faithful.
The system shall provide logs that record the results of refreshment
processes.
The system shall have the ability to notify users of incomplete or unsuccessful
refreshment processes.
The system shall have the ability to identify incomplete or unsuccessful
refreshments processes.
unsuccessful refreshments processes.
The system shall have the ability to support emulation to preserve access to
content.
The system shall have the ability to verify that the emulated file retains
specified attributes and behaviors, i.e. is authentic and faithful.
The system shall support the transformation of AIPs into ACPs.
When a preservation process results in the creation of an additional rendition
in an AIP, the system shall be capable of retaining the as-ingested rendition of
the content in the AIP.
R2; Must
R2; Must
R2; Must
R2; Must
R2; Must
R2; Must
R2; Must
R2; Must
R2; Must
R1C; Must
R1C; Must
R1C; Must
R1C; Must
R1C; Must
R1C; Must
R2; Must
R2; Must
R2; Must
R2; Must

Assessment
RD-625
10.3.0-1
RD-626
10.3.0-1.0-1
RD-627
RD-628
RD-629
10.3.0-1.0-2
10.3.0-1.0-3
10.3.0-2
RD-630
10.4
The system shall have the ability to assess ingested content and determine
preservation processes based on the assessments.
The system shall allow scheduling of preservation assessments. Content
attributes include, at a minimum, completeness, determination of structure, file
format, file size, and fitness for use.
There shall be no limit set on the number or frequency of assessments.
The system shall have the ability to re-assess content stored in the system.
The system shall present a range of options to the Service Specialist for
decision if the system is unable to make a determination.
R2; Must
R2; Must
R2; Must
R2; Must
R3; Could

Administration
RD-631
10.4.0-1
RD-632
RD-633
RD-634
RD-635
10.4.0-2
10.4.0-3
10.4.0-4
10.4.0-5
The system shall support scheduling the automatic execution of preservation

processes.
The system shall support batch Content Preservation of content.
The system shall support Content Preservation on an item-by-item basis.
The system shall maintain an audit trail of preservation processes.
The system shall support the ability for authorized users to request
R2; Must
R2; Must
R2; Must
R2; Must
R2; Must
26

FINAL
preservation processes.
RD-636
10.5
10.5 Preservation Processing Storage

RD-637
10.5.0-1
RD-638
10.5.0-1.0-1
RD-639
10.5.0-1.0-2
RD-640
10.5.0-1.0-3
RD-641
10.6
The system shall provide a digital archival repository environment which is

based on open-standards architecture.
The repository environment shall keep AIPs separate from working or
production copies.
The system shall ensure that when content in AIP is changed, the content in
the ACP is changed.
The system shall maintain one on more backups of the repository
environment consistent with the overall Fdsys storage requirements.
R1C; Must
R1C; Must
R1C; Must
R1C; Must
10.6 Preservation Processing Metadata

RD-642
10.6.0-1
RD-643
RD-644
10.6.0-2
10.6.0-3
RD-645
10.7
RD-646
10.7.0-1
The system shall capture or generate metadata which specifies the

relationship of files resulting from preservation processes to their
predecessors.
The system shall use the PREMIS Preservation Metadata Schema version 1.0
The system shall employ PREMIS Preservation Metadata Schema version 1.0
for facilitating preservation processes.
R2; Must
R1C; Must
R1C; Must
10.7 Preservation Processing Security
RD-647
RD-648
11
11.0-1
RD-649
RD-650
RD-651
RD-652
RD-653
11.0-2
11.0-3
11.0-4
11.0-5
11.0-6
RD-654
RD-655
RD-656
11.0-7
11.0-8
11.0-9
RD-657
RD-658
11.0-10
11.0-11
RD-659
11.1
The system shall enable varying levels of access to preserved objects (e.g.
limiting access to authorized user classes, or denying or restoring access to
security-restricted content).
R2; Must
11 Requirements for Unique

Identifier
The system shall allow an authorized user to apply a new level of granularity
to content without affecting previously applied levels.
The system shall assign unique IDs.
Unique ID shall be human-readable.
Unique ID shall be expressible in XML ID.
Unique ID shall be an alphanumeric identifier (ANI).
The system shall allow for the pre-assignment of unique IDs to external
entities.
The system shall only accept unique IDs created by the system.
The system shall provide the capability to apply unique IDs to digital objects.
Unique ID characters shall include numbers 0-9 and letters A (minus I and
O).
Unique ID shall be stored in Metadata.
Unique ID shall be unique.
R1C; Must
R1B; Must
R1B; Must
R1B; Must
R1B; Must
R1B; Must
R1B; Must
R1B; Must
R1B; Must
R1B; Must
R1B; Must
11.1 Unique ID Core Capabilities

RD-660
11.1.0-1
RD-661
11.1.0-1.0-1
RD-662
11.1.0-2
RD-663
11.1.0-2.0-1
The system shall support granularity of any content based on the natural
granularity boundaries of that content.
The system shall support granularity of GPO Access content referenced in
RD-2596 based on the natural granularity boundaries of that content.
The system shall allow GPO to define the level of granularity that content can
be retrieved at.
The system shall have the capability for a user to decide the level of
granularity that should be applied to a publication.
R2; Must
R1C; Must
R1B; Must
R1C; Must
27

FINAL
RD-664
11.1.0-2.0-1.0-1
RD-665
RD-666
RD-667
11.1.0-2.0-1.0-2
11.1.0-2.0-2
11.1.0-2.0-3
RD-668
11.1.0-2.0-4
RD-669
11.1.0-2.0-5
RD-671
RD-673
11.1.0-2.0-7
11.1.0-2.0-9
RD-679
11.1.0-3.0-5
RD-685
11.1.0-7
RD-686
11.1.0-8
RD-687
11.1.0-9
RD-688
11.1.0-10
RD-689
11.1.0-11
RD-690
11.1.0-12
RD-691
11.1.0-13
RD-692
11.1.0-14
RD-693
11.1.0-15
RD-694
11.1.0-16
RD-695
11.1.0-17
RD-696
11.1.0-18
RD-697
11.1.0-19
RD-698
11.1.0-20
RD-699
11.1.0-21
RD-700
11.2
RD-701
RD-702
RD-703
11.2.0-1
11.2.0-2
11.2.0-2.0-1
RD-704
11.2.0-2.0-2
RD-705
11.2.0-2.0-3
RD-706
11.2.0-3
The system shall have the capability for a user to apply multiple levels of
granularity to a publication (e.g. the whole publication can be found, every
paragraph in the publication can be found but images can not be separately
found).
The system shall allow elements to be retrieved by at all levels of granularity
The system shall support granularity to the level of a publication.
The system shall support granularity down to the level of any paragraph in a
publication.
The system shall support granularity down to the level of any individual
graphic
The system shall support granularity down to the level of any embedded
graphical element in a publication
The system shall support granularity down to the level of any frame of a video.
The system shall support granularity of audio down to smallest segment of
time the audios encoding allows.
The system shall provide the capability to support 1 trillion Digital Objects
without software redesign.
The system shall support granularity down to the level of any section in a
publication, as appropriate based on natural content boundaries.
The system shall support granularity down to the level of any article in a
publication, as appropriate based on natural content boundaries.
The system shall provide the capability to display granular content in search
results
The system shall provide the capability to associate granular content in search
results with the entire publication.
The system shall provide the capability to associate granular content in the
content detail with the entire publication.
The system shall provide the capability to deliver granular content separate
from the entire publication.
The system shall provide the capability to deliver granular content in
conjunction with the entire publication.
The system shall provide the capability to deliver text-based granular content
in a PDF format that has been optimized for rapid access and delivery.
in a HTML format that has been optimized for rapid access and delivery.
in a text format that has been optimized for rapid access and delivery.
in a XML format that has been optimized for rapid access and delivery.
The system shall provide the capability to transform text-based granular
content into formats that have been optimized for access and delivery if these
formats are not already present in the ACP.
The system shall provide the capability to deliver PDF granules at a page
level of granularity.
The system shall provide the capability to deliver PDF granules at a page
range level of granularity if the granules span multiple pages.
The system shall provide the capability to deliver PDF access renditions that
are identical in formatting to the print rendition, if a print rendition is available.
R1C; Must
R1C; Must
R1B; Must
R1C;
Should /
R2; Must
R1C; Must
R1C;
Should /
R2; Must
R3; Must
R3; Should
R1C; Must
R1C; Must
R1C; Must
R1C; Must
R1C; Must
R1C; Must
R1C; Must
R1C; Must
R1C; Must
R1C; Must
R1C; Must
R1C; Must
R1C; Must
R1C; Must
R1C; Must
R1C; Must
R1C; Must
11.2 Job ID
The system shall create and assign a unique ID for each job.
The system shall provide the capability to assign a unique IDs to each job.
The system shall provide the capability to assign unique IDs to Content
Originator orders of content jobs.
The system shall provide the capability to assign unique IDs to Content
Originator orders of service jobs.
The system shall provide the capability to assign unique IDs to non-Content
Originator order related jobs.
The system shall not re-use Job unique IDs.
R1B; Must
R1B; Must
R1B; Must
R1B; Must
R1B; Must
R1B; Must
28

FINAL
RD-707
11.3
11.3 Content Package ID

RD-708
RD-709
RD-710
RD-711
RD-712
RD-713
RD-715
RD-716
11.3.0-1
11.3.0-1.0-1
11.3.0-1.0-2
11.3.0-1.0-2.0-1
11.3.0-1.0-2.0-2
11.3.0-1.0-3
11.3.0-2
11.3.0-3
RD-717
11.4
RD-718
11.4.0-1
RD-719
11.4.0-1.0-1
RD-720
11.4.0-1.0-2
RD-721
11.4.0-1.0-3
RD-722
11.4.0-1.0-4
RD-723
11.4.0-1.0-5
The system shall create and assign a unique ID for each Content Package.
The system shall create and assign a unique ID to each SIP.
The system shall create and assign a unique ID to each AIP.
The AIP shall inherit the unique ID from the SIP if an ACP is not created.
The ACP shall inherit the unique ID from the SIP if an AIP is not created.
The system shall create and assign a unique ID to each ACP.
Content Package unique IDs shall be unique.
The system shall record package unique IDs in metadata.
R1B; Must
R1B; Must
R1B; Must
R1B; Must
R1B; Must
R1B; Must
R1B; Must
R1B; Must
11.4 Interface for Unique ID
RD-724
RD-725
12
12.1
RD-726
12.1.0-1
RD-727
RD-728
12.1.0-1.0-1
12.1.0-2
RD-729
12.1.0-2.0-1
RD-730
12.1.0-2.0-2
RD-731
12.1.0-2.0-3
RD-732
RD-733
RD-734
12.1.0-2.0-4
12.1.0-2.0-5
12.1.0-3
RD-735
12.1.0-4
RD-736
12.1.0-5
RD-737
12.1.0-5.0-1
RD-738
RD-739
RD-740
RD-741
12.1.0-6
12.1.0-7
12.1.0-8
12.1.0-9
The system shall allow the capability for a user to input a unique ID and
retrieve content and information about the content associated with that ID.
The system shall allow the capability for an authorized user to input a unique
ID.
The system shall allow the capability for an authorized user to retrieve content
and information about the content associated with a unique ID.
The system shall allow the capability for an authorized user to input an agency
supplied ID.
The system shall allow the capability for an authorized user to retrieve content
and information about the content associated with an agency supplied ID.
The system shall restrict access to information about content associated with
unique IDs according to user profiles and the FDsys security requirements
(e.g., End User inputting an internal Job ID).
R1B; Must
R1B; Must
R1B; Must
R1B; Must
R1B; Must
R1B; Must
12 Requirements for Persistent

Name
12.1 Persistent Name Core Capabilities
The system shall assign persistent names to all in-scope published versions
during access processing.
Persistent name shall not conflict with other identifiers within FDsys.
The system shall comply with the following standards and best practices
pertaining to persistent naming.
Persistent Identification: A Key Component Of An E-Government
Infrastructure. CENDI Persistent Identification Task Group (March 10, 2004)
Interagency Committee on Government Information Recommendations to the
Office of Management and Budget (December 17, 2004)
RFC 1737 Functional Requirements for Uniform Resource Names (December
1994)
RFC 2141 URN Syntax (May 1997)
RFC 2396 Uniform Resource Identifiers (URI): Generic Syntax (August 1998)
The system shall support interoperability across different naming systems to
allow one system to access a resource within another.
The system shall accommodate OpenURL syntax to enable federated
searching.
The system shall support the persistent name supplied by GPO as the
definitive persistent name.
The system shall allow GPO to elect other systems or agencies to become
recognized GPO naming authorities.
The system shall assign persistent names that are location independent.
The system shall assign persistent names that are protocol independent.
Persistent names shall be unique.
The system shall have the capability to assign intelligent persistent names.
R1C; Must
R1C; Must
R1C; Must
R1C; Must
R1C; Must
R1C; Must
R1C; Must
R1C; Must
R3; Should
R3; Must
R1C; Must
R1C; Must
R1C; Must
R3; Must
R1C; Must
R1C; Must
29

FINAL
RD-742
RD-743
12.1.0-9.0-1
12.1.0-10
RD-745
12.1.0-12
RD-746
RD-747
12.1.0-12.0-1
12.1.0-13
RD-748
RD-749
RD-750
RD-751
RD-752
RD-753
12.1.0-14
12.1.0-14.0-1
12.1.0-14.0-2
12.1.0-14.0-3
12.1.0-14.0-4
12.1.0-15
RD-754
12.2
The system shall have the capability to assign predictable persistent names.
The system shall have the capability to assign non-intelligent persistent
names.
The system shall have the capability to record the date and time of persistent
name creation.
Date and time of the persistent name creation shall be recorded in metadata.
The system shall have the capability to create reports about persistent name
management.
The system shall resolve legacy existing GPO naming schemes.
The system shall resolve existing PURLs.
The system shall resolve existing URLS that were constructed using GetDoc.
The system shall resolve existing URLS that were constructed using GetPage.
The system shall resolve existing URLS that were constructed using GetCFR.
The system shall support one persistent name per AIP.
R1C; Must
R1C; Could
R1C; Must
R1C; Must
R2; Could
R1C; Must
R1C; Must
R1C; Must
R1C; Must
R1C; Must
R1C; Must
12.2 Persistent Name Resolution

RD-755
12.2.0-1
RD-756
12.2.0-1.0-1
RD-757
12.2.0-1.0-2
RD-758
12.2.0-2
RD-759
12.2.0-3
RD-760
12.2.0-3.0-1
RD-761
12.2.0-4
RD-762
12.2.0-4.0-1
RD-763
12.3
The system shall use a resolution system to locate and provide access to
content with persistent names.
The resolution process shall resolve an assigned name into a resource or the
resource metadata.
The resolution process shall allow for persistent name recognition within
standard browsers.
The system shall have the capability to support distributed persistent naming
and resolution at the local and global level.
The system shall support resolution of a single persistent name to multiple
distributed locations.
The system shall be able to identify and resolve to multiple identical copies of
a resource at multiple locations through a single persistent name.
The system shall support resolution of a single persistent name to multiple
content versions.
The system shall determine the most appropriate rendition based on attributes
of the request.
R1C; Must
R1C; Must
R1C; Must
R1C; Must
R1C;
Should
R1C;
Should
R1C;
Should
R1C;
Should
12.3 Persistent Name Metadata

RD-764
RD-765
RD-766
12.3.0-1
12.3.0-2
12.3.0-3
RD-767
RD-768
13
13.1
RD-769
RD-776
RD-777
13.1.0-1
13.1.0-4
13.1.0-4.0-1
RD-778
13.1.0-5
RD-779
13.1.0-6
RD-780
13.1.0-7
RD-783
13.1.0-10
The system shall record persistent names associated with content.

The system shall record existing persistent names associated with content.
The system shall provide the capability to associate metadata with the
persistent name
R1C; Must
R1C; Must
R1C; Must
13 Requirements for Authentication

13.1 Authentication Core Capabilities
The system shall provide the capability to certify content as authentic.
The system shall provide the capability to certify content as official.
In some situations, Content Originators direct that specific content delivery
methods, file formats, or content presentations must be used for the purpose
of legal citation. As directed by a Content Originator, GPO shall record
information about this designation (intended use) in metadata.
The system shall provide the capability to certify content at levels of
granularity defined by GPO.
The system shall provide the capability to convey certification by means of an
integrity mark.
The system shall provide the capability to use GPOs Public Key Infrastructure
(PKI).
The system shall provide the capability to use public key cryptography, digital
certificates, encryption or other widely accepted information security
R1C; Must
R1C; Must
R1C; Must
R2; Must
R1C; Must
R1C; Must
R1C; Must
30

FINAL
mechanisms for providing authentication services within Fdsys.
RD-784
13.2
13.2 Authentication Content Pre-ingest

and Ingest
RD-785
13.2.0-1
RD-786
13.2.0-1.0-1
RD-787
13.2.0-1.0-2
RD-788
13.2.0-1.0-3
RD-789
RD-790
RD-791
13.2.0-1.0-4
13.2.0-1.0-5
13.2.0-1.0-6
RD-792
13.2.0-1.0-7
RD-793
13.2.0-1.0-7.0-1
RD-794
13.2.0-1.0-7.0-2
RD-795
13.2.0-1.0-7.0-3
RD-796
13.2.0-1.0-8
RD-797
13.2.0-1.0-8.0-1
RD-798
13.2.0-1.0-8.0-2
RD-799
RD-800
RD-801
13.2.0-1.0-8.0-3
13.2.0-1.0-9
13.2.0-1.0-10
RD-802
13.2.0-2
RD-803
13.2.0-2.0-1
RD-804
13.2.0-2.0-2
RD-805
13.2.0-2.0-3
RD-806
13.2.0-2.0-4
RD-807
13.2.0-2.0-5
RD-808
13.2.0-2.0-6
RD-809
13.2.0-2.0-6.0-1
RD-810
13.2.0-2.0-6.0-2
RD-811
13.2.0-2.0-6.0-3
The system shall provide the capability to verify and validate the authenticity,
integrity, and official status of deposited content.
The system shall provide the capability to validate the authenticity of
deposited content.
The system shall provide the capability to validate the integrity of deposited
content.
The system shall provide the capability to validate the official status of
deposited content.
The system shall verify the identity and authority of authorized users.
Valid proof of the user's identity shall be logged by the system.
The source (e.g., OriginInfo:publisher) of the deposited content shall be
recorded in metadata.
The system shall ensure that deposited content has not been altered or
destroyed in an unauthorized manner during transmission from the authorized
user to the system, and information about content integrity should be recorded
in metadata.
The system shall validate that deposited content has not been altered in an
unauthorized manner during transmission from the authorized user to the
system.
The system shall validate that deposited content has not been destroyed in an
unauthorized manner during transmission from the authorized user to the
system.
The system shall record information about deposited content integrity in
metadata.
The system shall verify that the sender and the recipient were, in fact, the
parties who claimed to send or receive content, respectively, and this
information should be recorded in metadata.
The system shall verify that the content sender is, in fact, the party who
claimed to have sent the content.
The system shall verify that the content recipient is, in fact, the party who
claimed to have received the content.
The system shall record content sender and recipient information in metadata.
The system shall have the capability to record intended use in metadata.
The system shall have the capability to use PKI for the establishment of a
trust model for deposited content.
integrity, and official status of harvested content.
harvested content.
The system shall provide the capability to validate the integrity of harvested
content.
harvested content.
The system shall examine harvested content for the purpose of verifying the
source of the harvested content.
The source (e.g., OriginInfo:publisher) of harvested content shall be recorded
in metadata.
The system shall ensure that harvested content has not been altered or
destroyed in an unauthorized manner as compared to the source from which
the content was harvested, and information about content integrity should be
The system shall validate that harvested content has not been altered in an
unauthorized manner as compared to the source from which the content was
harvested.
The system shall validate that harvested content has not been destroyed in an
unauthorized manner as compared to the source from which the content was
harvested.
The system shall record information about the harvested content integrity in
R1C; Must
R1C; Must
R1C; Must
R1C; Must
R1C; Must
R1C; Must
R1B; Must
R1C; Must
R1C; Must
R1C; Must
R1C; Must
R1C; Must
R1C; Must
R1C; Must
R1C; Must
R1C; Must
R1C; Must
R2; Must
R2; Must
R2; Must
R2; Must
R2; Must
R2; Must
R2; Must
R2; Must
R2; Must
R2; Must
31

FINAL
RD-812
13.2.0-3
RD-813
13.2.0-3.0-1
RD-814
13.2.0-3.0-2
RD-815
13.2.0-3.0-3
RD-816
13.2.0-3.0-4
RD-817
13.2.0-3.0-5
RD-818
13.2.0-3.0-6
RD-819
13.2.0-3.0-6.0-1
RD-820
13.2.0-3.0-6.0-2
RD-821
13.2.0-3.0-6.0-3
RD-822
13.2.0-3.0-7
RD-823
13.2.0-3.0-7.0-1
RD-824
13.2.0-3.0-7.0-2
RD-825
RD-826
RD-827
13.2.0-3.0-7.0-3
13.2.0-3.0-8
13.2.0-3.0-9
RD-828
13.2.0-4
RD-829
13.2.0-4.0-1
RD-830
13.2.0-4.0-2
RD-831
13.2.0-4.0-3
RD-832
13.2.0-4.0-4
RD-833
13.2.0-4.0-4.0-1
RD-834
13.2.0-4.0-4.0-2
RD-835
13.2.0-5
RD-836
RD-837
RD-838
13.2.0-6
13.2.0-6.0-1
13.2.0-6.0-2
RD-839
13.2.0-6.0-2.0-1
metadata.
integrity, and official status of converted content.
converted content.
The system shall provide the capability to validate the integrity of converted
content.
converted content.
The source (e.g., OriginInfo:publisher) of converted content shall be recorded
in metadata.
The source (e.g., OriginInfo:publisher) of tangible content that was used to
create the converted content shall be recorded in metadata.
The system shall ensure that converted content has not been altered or
destroyed in an unauthorized manner during transmission from authorized
users to the system, and information about content integrity should be
The system shall validate that converted content has not been altered in an
unauthorized manner during transmission to the system.
The system shall validate that converted content has not been destroyed in an
unauthorized manner during transmission to the system.
The system shall record information about converted content integrity in
metadata.
The system shall verify that the sender and the recipient were, in fact, the
parties who claimed to send or receive content, respectively, and this
information should be recorded in metadata.
The system shall verify that the sender is, in fact, the party who claimed to
have sent the converted content.
The system shall verify that the recipient is, in fact, the party who claimed to
have received the converted content.
The system shall record the sender and the recipient information in metadata.
The system shall have the capability to record intended use in metadata.
The system shall have the capability to use PKI for the establishment of a
trust model for converted content.
The system shall provide the capability to recognize and validate integrity
marks at pre-ingest.
The system shall provide the capability to recognize integrity marks at preingest.
The system shall provide the capability to validate integrity marks at preingest.
The system shall have the capability to retain integrity marks in accordance
with GPO business rules.
Where public key cryptography and digital certificates are used by a Content
Originator to create a digital signature integrity mark on content that is
submitted to GPO for ingest into the system, the system shall record in
metadata that a digital signature was present and make this information
available to End Users.
submitted to GPO for ingest into the system, the system shall record in
metadata that a digital signature was present.
submitted to GPO for ingest into the system, the system shall make metadata
information concerning the presence of a digital signature available to End
Users.
The system shall provide the capability to process encrypted files at preingest.
The system shall record chain of custody information.
Chain of custody information shall be recorded in metadata.
The system shall have the capability to gather relevant information from
integrity marks (e.g., digital signatures, digital certificates) for use as part of
the chain of custody.
The system shall have the ability to gather Distinguished Name information
from integrity marks for use as part of the chain of custody.
R1C; Must
R1C; Must
R1C; Must
R1C; Must
R1B; Must
R1B; Must
R1C; Must
R1C; Must
R1C; Must
R1C; Must
R1C; Must
R1C; Must
R1C; Must
R1C; Must
R1B; Must
R1C; Must
R1C; Must
R1C; Must
R1C; Must
R1C; Must
R1C; Must
R1C; Must
R1C; Must
R1C; Could
/ R2; Must
R1C; Must
R1C; Must
R1C; Must
R1C; Must
32

FINAL
RD-840
13.2.0-6.0-2.0-2
RD-841
13.2.0-6.0-2.0-3
RD-842
RD-843
13.2.0-6.0-2.0-4
13.2.0-6.0-2.0-5
RD-844
RD-845
13.2.0-6.0-2.0-6
13.2.0-7
RD-846
13.2.0-7.0-1
RD-847
RD-848
RD-849
13.2.0-7.0-1.0-1
13.2.0-7.0-1.0-2
13.2.0-8
RD-851
13.3
The system shall have the ability to gather information from integrity marks
regarding the date the integrity mark was applied for use as part of the chain
of custody.
The system shall have the ability to gather information from integrity marks
regarding the time the integrity mark was applied for use as part of the chain
of custody.
The system shall have the capability to record chain of custody in WIP.
The system shall have the ability to gather chain of custody from content
metadata when it is not available from integrity marks.
The system shall update chain of custody information in metadata at ingest.
The system shall provide the capability to perform redundancy checking (e.g.,
checksum) on content at ingest.
The system shall provide the capability to record checksum type and value in
metadata.
The system shall provide the capability to record checksum type in metadata.
The system shall provide the capability to record checksum value in metadata.
The system shall provide the capability to apply a digital timestamp to content
at ingest.
R1C; Must
R1C; Must
R1C; Must
R1C; Must
R1C; Must
R1C; Must
R1C; Must
R1C; Must
R1C; Must
R1C; Must
13.3 Authentication User Credentials

RD-855
13.4
RD-856
13.4.0-1
RD-857
13.4.0-1.0-1
RD-858
13.4.0-1.0-2
RD-859
13.4.0-1.0-3
RD-860
13.4.0-1.0-4
RD-863
13.4.0-2.0-2
RD-864
13.4.0-2.0-2.0-1
RD-865
13.4.0-2.0-2.0-2
RD-866
13.4.0-2.0-3
RD-867
RD-868
RD-869
RD-870
13.4.0-3
13.4.0-3.0-1
13.4.0-3.0-2
13.4.0-3.0-3
RD-871
13.4.0-3.0-4
RD-872
RD-873
13.4.0-4
13.4.0-4.0-1
RD-874
13.4.0-4.0-2
RD-875
13.4.0-4.0-2.0-1
RD-876
13.4.0-4.0-2.0-2
13.4 Authentication Content Integrity

The system shall provide the capability to maintain content integrity by
ensuring that content has not been altered or destroyed in an unauthorized
manner.
The system shall provide the capability to certify content integrity within the
system by ensuring that content has not been altered in an unauthorized
manner.
The system shall provide the capability to certify content integrity within the
system by ensuring that content has not been destroyed in an unauthorized
manner.
The system shall have the capability to ensure integrity of content within the
system at a definable frequency.
The system shall have the capability to ensure integrity of work in progress
content.
The system shall not allow critical transaction and system log files to be
adjusted by any unauthorized party.
The system shall not allow critical transaction files to be adjusted by any
unauthorized party.
The system shall not allow system log files to be adjusted by any
unauthorized party.
The system shall have the capability to certify integrity of content during
backup and other system processes.
The system shall certify integrity of pre-ingested and ingested content.
The system shall certify integrity of pre-ingested content.
The system shall certify integrity of ingested content.
Content integrity shall be maintained during transmission from the Content
Originator to the system.
The system shall have the capability to validate a cryptographic digital
signature, in accordance with IETF RFC 3447 on content in pre-ingest, to
ensure that the content has not been altered, and that the signers certificate
is valid before ingesting the content.
The system shall have the capability to certify integrity of delivered content.
The system shall have the capability to apply a cryptographic digital signature,
in accordance with IETF RFC 3447, to content delivered from the system.
The system shall have the capability to verify that the electronic content is
valid, uncorrupted, and free of malicious code.
valid.
R1B; Must
R1B; Must
R1B; Must
R1B; Must
R1B; Must
R1B; Must
R1B; Must
R1B; Must
R1B; Must
R1C; Must
R1C; Must
R1C; Must
R1C; Must
R1C; Must
R2; Must
R2; Must
R2; Must
R2; Must
R2; Must
33

FINAL
RD-877
13.4.0-4.0-2.0-3
RD-878
13.4.0-5
RD-879
13.4.0-5.0-1
RD-880
13.4.0-5.0-1.0-1
RD-881
13.4.0-5.0-1.0-2
RD-882
13.4.0-5.0-2
RD-883
13.4.0-5.0-2.0-1
RD-884
13.4.0-5.0-2.0-2
RD-885
13.4.0-5.0-3
RD-886
13.4.0-5.0-4
RD-887
13.4.0-5.0-5
RD-888
13.4.0-5.0-6
RD-889
RD-890
13.4.0-5.0-7
13.4.0-6
RD-891
13.5
uncorrupted.
The system shall have the capability to verify that the electronic content is free
of malicious code.
The system shall provide the capability to provide notification that a change
has occurred to content within the system.
The system shall provide the capability to notify designated users if content
has been altered or destroyed in an unauthorized manner.
has been altered in an unauthorized manner.
has been destroyed in an unauthorized manner.
has been altered or destroyed in an authorized manner.
has been altered in an authorized manner.
has been destroyed in an authorized manner.
The system shall provide the capability to notify designated users when
changes were made to content.
The system shall provide the capability to notify designated users where
The system shall provide the capability to notify designated users by whom
The system shall provide the capability to notify designated users what
The system shall log changes to content in metadata.
The system shall provide the capability of demonstrating continued integrity of
content packages when authorized changes are made (such as to the
metadata).
R2; Must
R2; Must
R2; Must
R2; Must
R2; Must
R2; Must
R2; Must
R2; Must
R2; Must
R2; Must
R2; Must
R2; Must
R2; Must
R2; Must
13.5 Authentication Time Stamps

RD-892
RD-893
RD-894
13.5.0-1
13.5.0-2
13.5.0-3
RD-895
13.5.0-3.0-1
RD-896
13.5.0-3.0-2
RD-897
13.5.0-3.0-3
RD-898
13.6
RD-899
RD-900
RD-901
13.6.0-1
13.6.0-2
13.6.0-3
RD-902
13.6.0-4
RD-903
13.6.0-5
RD-904
RD-905
RD-906
13.6.0-6
13.6.0-7
13.6.0-8
RD-907
13.6.0-8.0-1
RD-908
13.6.0-8.0-2
The system shall support digital time stamping.

The system shall provide the capability to provide date and time verification.
The system shall be flexible enough to provide date and time verification
through various mechanisms including a time certification authority, network
server, or the signerstem.
through a time certification authority.
through a network time server.
through the signer's system.
R1C; Must
R1C; Must
R1C; Must
R1C; Must
R1C; Must
R1C; Must
13.6 Authentication Integrity Marks

The system shall support the use of integrity marks.
Integrity marks shall include certification information.
Integrity marks shall employ widely accepted information security mechanisms
(e.g., public key cryptography, digital certificates, digital signatures, XML
signatures, digital watermarks, or traditional watermarks).
The system shall support the capability to manually add integrity marks to
content.
The system shall support the capability to automatically add integrity marks to
content.
The system shall support the use of visible integrity marks.
The system shall support the use of invisible integrity marks.
The system shall provide flexibility regarding where the integrity mark is
applied through automated and manual processes.
applied through automated processes.
R2; Must
R2; Must
R2; Must
R2; Could
R2; Must
R1C; Must
R1C; Must
R2; Must
R2; Must
R2; Must
34

FINAL
RD-909
13.6.0-9
RD-910
13.6.0-10
RD-911
13.6.0-11
RD-912
13.7
RD-913
13.7.0-1
RD-914
13.7.0-1.0-1
RD-915
13.7.0-1.0-2
RD-916
13.7.0-1.0-3
RD-917
13.7.0-2
RD-918
13.7.0-2.0-1
RD-919
13.7.0-2.0-2
RD-920
13.7.0-2.0-3
RD-921
13.7.0-2.0-4
RD-922
13.7.0-2.0-5
RD-923
13.7.0-3
RD-924
13.7.0-3.0-1
RD-925
RD-926
RD-927
RD-928
RD-929
RD-930
RD-931
RD-932
RD-933
RD-934
13.7.0-3.0-2
13.7.0-3.0-2.0-1
13.7.0-3.0-2.0-2
13.7.0-3.0-2.0-3
13.7.0-3.0-2.0-4
13.7.0-3.0-2.0-5
13.7.0-3.0-2.0-6
13.7.0-3.0-2.0-7
13.7.0-3.0-2.0-8
13.7.0-3.0-2.0-9
RD-935
13.7.0-3.0-2.0-10
RD-936
13.7.0-3.0-2.0-11
RD-937
13.7.0-3.0-3
RD-939
13.7.0-3.0-5
RD-940
13.7.0-3.0-5.0-1
applied through manual processes.

The system shall provide the capability to automatically position the exact
location (x, y coordinates) of where an integrity mark is applied for any set
number of documents.
The system shall support the application of multiple integrity marks on the
same content.
The system shall support the application of security policies, such that
integrity marks can be applied to content in particular sequences depending
on levels of authority.
R2; Must
R2; Must
R2; Must
13.7 Authentication Content Delivery

The system shall provide the capability for users to validate the authenticity,
integrity, and official status of the content packages that are delivered from the
system.
The system shall provide the capability for users to validate the authenticity of
the content packages that are delivered from the system.
The system shall provide the capability for users to validate the integrity of the
content packages that are delivered from the system.
The system shall provide the capability for users to validate the official status
of the content packages that are delivered from the system.
The system shall enable GPO to add integrity marks to FDsys content that is
delivered to End Users in the form of electronic presentation, hard copy
output, and digital media.
delivered to End Users in the form of electronic presentation.
delivered to End Users in the form of hard copy output.
delivered to End Users in the form of digital media.
When electronic content in PDF format has been authenticated prior to ingest
into FDsys (e.g., via the bulk signing tool), the system shall maintain that
externally provided authentication.
When electronic content in PDF format has been authenticated prior to ingest
into FDsys (e.g., via the bulk signing tool), the system shall deliver the
integrity mark to End Users with that externally provided authentication still
intact.
Where public key cryptography and digital certificates are used to create a
digital signature integrity mark on delivered content the following shall apply:
The integrity mark shall provide the capability to include the GPO Seal of
Authenticity logo if the digital signature is a visible digital signature.
The integrity mark shall include certification information.
The integrity mark shall include the name of the certifying organization.
The integrity mark shall include the date on the signer's digital certificate.
The integrity mark shall include the digital time stamp.
The integrity mark shall include the public key value of the signer.
The integrity mark shall include identification of the hash algorithm used.
The integrity mark shall include the reason for signing.
The integrity mark shall include the signer's location.
The integrity mark shall include the signer's contact information.
The integrity mark shall include the name of the entity that certified the
content.
The integrity mark shall include the expiration date of the digital certificate
used to sign the content.
The integrity mark shall be flexible enough to include additional, GPO-defined
certification information.
The values for the integrity mark fields shall be extracted from the digital
certificate that was used to create the digital signature.
The system shall have the capability to confirm that the digital certificate that
was used to create the digital signature is valid and accurate. As a result of
the validation check, the system should notify users if the digital certificate is
valid, invalid, or can not be validated.
The system shall have the capability to confirm that the digital certificate that
R2; Must
R2; Must
R2; Must
R2; Must
R2; Must
R2; Must
R2; Must
R2; Must
R1C; Must
R1C; Must
R2; Must
R2; Could
R2; Must
R2; Must
R2; Must
R2; Must
R2; Must
R2; Must
R2; Must
R2; Must
R2; Must
R2; Must
R2; Must
R2; Must
R2; Must
R2; Must
R2; Must
35

FINAL
was used to create the digital signature is valid and accurate.
As a result of the digital signature validation check, the system should notify
users if the digital certificate is valid, invalid, or cannot be validated.
The system shall have the capability to perform a bit for bit comparison of the
digital object as it was at the time of signing against the document as it was at
the time of the validation check. As a result of the validation check, the system
should notify users if the content has been modified, has not been modified, or
if the system cannot determine if the content has been modified.
The system shall have the capability to perform a bit for bit comparison of the
digital object as it was at the time of signing against the document as it was at
the time of the validation check.
As a result of the validation check, the system should notify users if the
content has been modified, has not been modified, or if the system cannot
determine if the content has been modified.
The digital signature shall include the date and time that the digital signature
was applied to content, and the expiration date of the digital certificate.
The digital signature shall include the date and time that the digital signature
was applied to content.
The digital signature shall include the expiration date of the digital certificate.
Non-revoked certificates shall display a valid status regardless of the
expiration date of the digital certificate. The validity of the digital certificate
shall be based on the certificate validity at the time and date the content was
digitally signed.
Non-revoked certificates shall display a valid status regardless of the
expiration date of the digital certificate.
RD-941
13.7.0-3.0-5.0-2
RD-942
13.7.0-3.0-6
RD-943
13.7.0-3.0-6.0-1
RD-944
13.7.0-3.0-6.0-2
RD-945
13.7.0-3.0-7
RD-946
13.7.0-3.0-7.0-1
RD-947
RD-948
13.7.0-3.0-7.0-2
13.7.0-3.0-8
RD-949
13.7.0-3.0-8.0-1
RD-950
13.7.0-3.0-8.0-2
The validity of the digital certificate shall be based on the certificate validity at
the time and date the content was digitally signed.
RD-951
13.7.0-3.0-9
For electronic presentation, validation shall be done automatically without End

User intervention.
RD-952
13.8
RD-953
13.8.0-1
RD-954
13.8.0-2
RD-955
13.8.0-3
RD-956
13.9
R2; Must
R2; Must
R2; Must
R2; Must
R2; Must
R2; Must
R2; Must
R1C;
Should /
R2; Must
R1C;
Should /
R2; Must
R1C;
Should /
R2; Must
R1C;
Should /
R2; Must
13.8 Re-authentication of Content

The system shall provide the capability to re-authenticate content that has
already been authenticated (e.g., expired certificate).
The system shall provide the capability to notify GPO System Administrators
when content needs to be re-authenticated.
The system shall provide the capability for GPO to change or revoke the
authentication status of content.
R1B; Could
/ R2; Must
R1B; Could
/ R2; Must
R1B; Must
13.9 Authentication Standards/Best

Practices
RD-978
13.10
13.10 Authentication Records

Management
RD-979
RD-980
RD-981
RD-982
RD-983
13.10.0-1
13.10.0-2
13.10.0-3
13.10.0-4
13.10.0-5
RD-984
13.10.0-5.0-1
RD-985
13.10.0-5.0-2
The system shall create administrative records of authentication processes.

The system shall create transaction records of administrative processes.
The system shall support an audit capability for content certification.
The system shall support an audit capability for content validation.
The system shall comply with GPO and Federal records management
policies.
The system shall comply with GPO records management policies, as
document in GPO Publication 840.7.
The system shall comply with Federal records management policies (e.g.,
NARAs Records Management Guidance for Agencies Implementing
R2; Must
R2; Must
R2; Must
R2; Must
R2; Must
R2; Must
R2; Must
36

FINAL
Electronic Signature Technologies, 2000).
RD-986
13.11
13.11 Authentication Metadata

RD-987
13.11.0-1
RD-988
13.11.0-1.0-1
RD-989
13.11.0-1.0-1.0-1
RD-990
13.11.0-1.0-1.0-2
RD-991
13.11.0-1.0-1.0-3
RD-992
13.11.0-1.0-1.0-4
RD-993
13.11.0-1.0-2
RD-994
13.11.0-1.0-2.0-1
RD-995
13.11.0-1.0-2.0-2
RD-996
13.11.0-1.0-2.0-3
RD-997
13.11.0-1.0-2.0-4
RD-998
13.11.0-1.0-2.0-5
RD-999
13.11.0-1.0-2.0-6
RD-1000
13.11.0-1.0-3
RD-1001
13.11.0-1.0-3.0-1
RD-1002
13.11.0-1.0-3.0-2
RD-1003
13.11.0-1.0-4
RD-1004
13.11.0-1.0-4.0-1
RD-1005
13.11.0-1.0-4.0-2
RD-1006
13.11.0-1.0-4.0-3
RD-1007
RD-1008
14
14.1
RD-1013
14.1.0-5
RD-1014
14.1.0-5.0-1
RD-1015
RD-1016
14.1.0-5.0-1.0-1
14.1.0-5.0-1.0-2
The system shall provide the capability to include authentication and

certification information in metadata.
The system shall provide the capability to include authenticity information in
metadata.
Authenticity metadata shall have the capability to include the source of
deposited, harvested, and converted content.
Authenticity metadata shall have the capability to include the Content
Originator identity and authority to publish deposited content.
Authenticity metadata shall have the capability to include the source of
tangible content that was used to create converted content.
Authenticity metadata shall have the capability to include the chain of custody
information excluding information about End User chain of custody.
The system shall provide the capability to include integrity information in
metadata.
Integrity metadata shall have the capability to include information about any
pre-ingest and ingest integrity checks for transmission to the system.
Integrity metadata shall have the capability to include information about any
integrity checks within the system.
Integrity metadata shall have the capability to include information about
changes that are made.
Integrity metadata shall have the capability to include information about who
makes a change.
Integrity metadata shall have the capability to include information about where
a change is made.
Integrity metadata shall have the capability to include information about when
a change is made.
The system shall provide the capability to include non-repudiation information
in metadata.
Non-repudiation metadata shall have the capability to include the sender's
identity and proof.
Non-repudiation metadata shall have the capability to include the recipient's
identity and proof.
The system shall provide the capability to include intended use information in
metadata.
Intended Use metadata shall have the capability to identify the content
delivery method designated by the Content Originator that must be used for
the purpose of citation in court.
Intended Use metadata shall have the capability to identify the file format
designated by the Content Originator that must be used for the purpose of
citation in court.
Intended Use metadata shall have the capability to identify the content
presentation designated by the Content Originator that must be used for the
purpose of citation in court.
R1C; Must
R1C; Must
R1C; Must
R1C; Must
R1C; Must
R1C; Must
R1C; Must
R1C; Must
R1C; Must
R1C; Must
R1C; Must
R1C; Must
R1C; Must
R1C; Must
R1C; Must
R1C; Must
R1C; Must
R1C; Must
R1C; Must
R1C; Must
14 Requirements for Version

Control
14.1 Version Control Core Capabilities
The system shall allow authorized users to input, view, and manage version
information.
information.
The system shall allow authorized users to input version information.
The system shall allow authorized users to view version information.
R1C; Must
R1C; Must
R1C; Must
R1C; Must
37

FINAL
RD-1017
RD-1018
14.1.0-5.0-1.0-3
14.1.0-5.0-2
RD-1019
RD-1020
RD-1021
RD-1022
14.1.0-5.0-2.0-1
14.1.0-5.0-2.0-2
14.1.0-5.0-2.0-3
14.1.0-6
RD-1023
RD-1024
14.1.0-7
14.1.0-7.0-1
RD-1029
14.2
RD-1030
RD-1031
14.2.0-1
14.2.0-1.0-1
RD-1032
RD-1033
RD-1034
RD-1035
RD-1036
RD-1037
RD-1038
RD-1039
RD-1040
RD-1041
RD-1042
RD-1043
14.2.0-1.0-2
14.2.0-2
14.2.0-2.0-1
14.2.0-2.0-2
14.2.0-2.0-3
14.2.0-2.0-4
14.2.0-2.0-5
14.2.0-2.0-6
14.2.0-2.0-7
14.2.0-2.0-8
14.2.0-2.0-9
14.2.0-3
RD-1045
14.2.0-5
RD-1046
14.3
RD-1047
14.3.0-1
RD-1048
14.3.0-1.0-1
RD-1049
14.4
RD-1050
RD-1051
RD-1052
14.4.0-1
14.4.0-1.0-1
14.4.0-2
RD-1053
14.5
RD-1054
RD-1056
RD-1057
14.5.0-1
14.5.0-1.0-1
14.5.0-1.0-2
RD-1055
14.5.0-2
RD-1058
14.6
The system shall allow authorized users to manage version information.

identifiers.
The system shall allow authorized users to input version identifiers.
The system shall allow authorized users to view version identifiers.
The system shall allow authorized users to manage version identifiers.
The system shall have the capability to alert authorized users when duplicate
content is rejected.
The system shall log all version history.
The version history log shall be incorporated into the packages metadata.
R1C; Must
R1C; Must
R1C; Must
R1C; Must
R1C; Must
R1C; Must
R2; Must
R2; Must
14.2 Version Triggers

The system shall apply rules for version triggers.
The system shall apply rules for version triggers to groups of related content
as defined in the GPO document Version Control in Relation to Government
Documents.
Authorized users shall be able to modify rules for version triggers.
The system shall detect the following version triggers.
Modifications to content
Changes to the "last updated" data provided within the document
Changes to a flat date provided within the document
Changes to a publication's title
Changes to a publication's edition statement and/or metadata
Changes in the issuing agency of a publication
Changes in file size or format
Changes in the publication's numbering scheme
Notification of the publisher (i.e., issuing agency)
The system shall provide the capability to notify users when version triggers
have been activated.
The system shall provide the capability to notify designated authorized users
when a version cannot be determined.
R2; Must
R2; Must
R2; Must
R2; Must
R2; Must
R2; Must
R2; Must
R2; Must
R2; Must
R2; Must
R2; Must
R2; Must
R2; Must
R2; Must
14.3 Version Detection

The system shall determine if version identifiers are present in content
packages.
Version identifiers shall be stored in metadata.
R2; Must
R1C; Must
14.4 Version Metadata

The system shall express version information in metadata.
The system shall update the metadata to indicate changes to attributes.
The system shall record chain of custody information in metadata .
R1C; Must
R1C; Must
R1C; Must
14.5 Version Relationships

The system shall determine and record relationships between versions.
The system shall make links to related documents permanently available.
The system shall be able to render relationship information so that it is
human-readable.
The system shall establish links to related documents identified through
version information in metadata.
R2; Must
R2; Must
R2; Must
R2; Must
14.6 Version Notification

RD-1059
14.6.0-1
The system shall have the capability to notify users which version of content
R2; Must
38

FINAL
RD-1060
14.6.0-1.0-1
RD-1061
14.6.0-1.0-2
RD-1062
14.6.0-1.0-3
RD-1063
14.6.0-1.0-4
RD-1064
14.6.0-1.0-5
RD-1065
RD-1066
15
15.1
they are accessing.

The system shall have the capability to notify users of the number of available
versions of selected content.
The system shall have the capability to notify users that they are not viewing
the latest available version of selected content.
The system shall have the capability to notify users of the relationship
between the version of the content they are accessing and the latest version.
The system shall have the capability for users to view the difference in the
content between versions.
The system shall have the capability to notify users that access to a version is
restricted.
R2; Must
R2; Must
R2; Must
R3; Must
R2; Must
15 Requirements for Workflow

15.1 Workflow Core Capabilities
RD-1067
RD-1068
15.1.0-1
15.1.0-1.0-1
RD-1069
15.1.0-1.0-2
RD-1070
15.1.0-2
RD-1071
15.1.0-3
RD-1072
15.1.0-4
RD-1073
15.1.0-4.0-1
RD-1074
15.1.0-5
RD-1075
15.1.0-5.0-1
RD-1076
15.1.0-5.0-2
RD-1077
RD-1078
15.1.0-6
15.1.0-6.0-1
RD-1079
RD-1080
RD-1081
RD-1082
RD-1083
15.1.0-7
15.1.0-8
15.1.0-9
15.1.0-9.0-1
15.1.0-9.0-2
RD-1084
15.1.0-9.0-3
RD-1085
RD-1086
RD-1087
15.1.0-10
15.1.0-10.0-1
15.1.0-10.0-2
RD-1088
15.1.0-10.0-2.0-1
RD-1089
15.1.0-10.0-3
RD-1090
15.1.0-10.0-4
RD-1091
15.1.0-11
The system shall provide the capability to define workflows.

The workflow definition shall be in the XML form conforming to a well
established schema, such as XML Process Definition Language (XPDL) of
Workflow Management Coalition (WfMC) or the Business Process Execution
Language (BPEL) schema.
The system shall provide the capability to validate workflow definitions against
the established schema.
The system shall provide the capability to create new versions of workflow
definitions.
The system shall provide the capability to test new versions of workflow
definitions without interfering with any existing workflow instances.
The system shall provide the capability to place new versions of workflow
definitions into production.
The system shall provide the capability to deploy newly developed or modified
workflow definitions without interfering with existing workflow instances.
The system shall provide the capability to revert to previous workflow
definitions without interfering with existing workflow instances or other noncompleted instances of workflows.
definitions without interfering with existing workflow instances.
definitions without interfering with other non-completed instances of
workflows.
The system shall provide the capability to manage business rules.
The workflow-related business rules shall be configurable by the user to
control the order in which the rules are applied.
The system shall provide the capability to manage manual activities.
The system shall provide the capability to manage automated activities.
The system shall provide the capability to assign comments on jobs/activities.
The system shall provide the capability to assign optional comments on jobs.
The system shall provide the capability to assign optional comments on
activities.
The system shall provide the capability to assign optional comments on
workflow instances.
The system shall prevent the loss of workflow data.
The system shall replicate workflow data to failover location(s).
The system shall allow the frequency of backup processes to be controlled by
the user.
The system shall allow the backup processes to be controlled automatically or
manually.
The system shall backup all necessary data required to retrieve workflow data
to its original state in the event of a system failure.
The system shall perform workflow backup processes without interruption to
users.
The system shall store information related to workflows in BPI.
R1B; Must
R1B; Must
R1B; Must
R1B; Must
R1B; Must
R1B; Must
R1B; Must
R1B; Must
R1B; Must
R1B; Must
R1B; Must
R2; Must
R1B; Must
R2; Must
R1B; Must
R1B; Must
R1B; Must
R1B; Must
R1B; Must
R1C; Must
R1C; Must
R2; Must
R1C; Must
R1C; Must
R1B; Must
39

FINAL
RD-1092
RD-1093
RD-1094
15.1.0-11.0-1
15.1.0-11.0-2
15.1.0-11.0-3
RD-1095
15.2
RD-1096
15.2.0-1
RD-1097
15.2.0-1.0-1
RD-1098
15.2.0-1.0-2
RD-1099
15.2.0-1.0-2.0-1
RD-1100
15.2.0-1.0-2.0-1.01
15.2.0-1.0-2.0-1.02
15.2.0-1.0-2.0-2
The system shall store information about workflows in BPI.

The system shall store information about jobs in BPI.
The system shall store information about activities in BPI.
R1B; Must
R1B; Must
R1B; Must
15.2 Workflow Control of Execution
RD-1101
RD-1102
RD-1103
RD-1105
15.2.0-1.0-2.0-2.01
15.2.0-1.0-2.0-2.02
15.2.0-1.0-3
RD-1106
15.2.0-1.0-4
RD-1107
RD-1108
RD-1109
15.2.0-1.0-4.0-1
15.2.0-1.0-4.0-2
15.2.0-1.0-5
RD-1110
RD-1111
RD-1112
RD-1113
RD-1114
RD-1115
RD-1116
RD-1117
RD-1118
15.2.0-1.0-5.0-1
15.2.0-1.0-5.0-2
15.2.0-1.0-6
15.2.0-1.0-6.0-1
15.2.0-1.0-6.0-2
15.2.0-1.0-7
15.2.0-1.0-7.0-1
15.2.0-1.0-7.0-2
15.2.0-1.0-7.0-3
RD-1119
15.2.0-1.0-7.0-4
RD-1120
RD-1121
15.2.0-1.0-8
15.2.0-1.0-8.0-1
RD-1122
15.2.0-1.0-8.0-2
RD-1123
15.2.0-1.0-9
RD-1124
RD-1125
RD-1126
15.2.0-2
15.2.0-2.0-1
15.2.0-2.0-1.0-1
RD-1127
RD-1128
RD-1129
RD-1130
RD-1131
15.2.0-2.0-2
15.2.0-2.0-2.0-1
15.2.0-2.0-2.0-2
15.2.0-2.0-3
15.2.0-2.0-4
RD-1132
15.2.0-2.0-4.0-1
RD-1104
The system shall provide the capability to control the execution of workflow
instances.
The system shall provide the capability to assign priorities to workflow
instances.
The system shall provide the capability to schedule for manual and automated
activities.
The system shall provide the capability to assign deadlines for jobs/activities.
The system shall provide the capability to assign deadlines for jobs.
The system shall provide the capability to assign deadlines for activities.
The system shall provide the capability to assign estimated completion times
for jobs/activities.
for jobs.
for activities.
The system shall provide the capability to assign human resources to manual
activities.
The system shall provide the capability to suspend activities/workflow
instances.
The system shall provide the capability to suspend activities.
The system shall provide the capability to suspend workflow instances.
The system shall provide the capability to resume activities/workflow
instances.
The system shall provide the capability to resume activities.
The system shall provide the capability to resume workflow instances.
The system shall provide the capability to cancel activities/workflow instances.
The system shall provide the capability to cancel activities.
The system shall provide the capability to cancel workflow instances.
The system shall provide the capability to log activities.
The system shall provide the capability to log activity start time.
The system shall provide the capability to log activity end time.
The system shall provide the capability to log the person(s) performing the
activity.
The system shall provide the capability to log the resources associated with
an activity .
The system shall provide the capability to manage lists of workflow instances.
The system shall provide the capability for a user to view lists of workflow
instances.
The system shall provide the capability for a user to assign lists of workflow
instances to other users.
The system shall provide the capability to perform actions on a batch of
workflow instances.
The system shall provide the capability to control the execution of jobs.
The system shall provide the capability to assign priorities to jobs.
The priority of a job shall be inherited by workflow instances associated with
the job.
The system shall provide the capability to suspend and resume jobs.
The system shall provide the capability to suspend jobs.
The system shall provide the capability to resume jobs.
The system shall provide the capability to cancel a job.
The system shall provide the capability to adjust the priority of a job at any
time.
The system shall provide the capability to adjust the priority of a job manually
or automatically.
R1B; Must
R1B; Must
R1B; Could
/ R1C; Must
R1B; Could
/ R1C; Must
R1B; Could
/ R1C; Must
R1B; Could
/ R1C; Must
R1B; Could
/ R1C; Must
R1B; Could
/ R1C; Must
R1B; Could
/ R1C; Must
R1C; Must
R1B; Must
R1B; Must
R1B; Must
R1B; Must
R1B; Must
R1B; Must
R1B; Must
R1B; Must
R1B; Must
R1B; Must
R1B; Must
R1B; Must
R1B; Must
R1B; Must
R1B; Must
R1B; Must
R1B; Must
R2; Must
R1B; Must
R1C; Must
R1C; Must
R1B; Must
R1B; Must
R1B; Must
R1B; Must
R2; Must
R2; Must
40

FINAL
RD-1133
RD-1134
RD-1135
15.2.0-2.0-5
15.2.0-2.0-6
15.2.0-2.0-7
RD-1136
15.3
RD-1137
RD-1138
15.3.0-1
15.3.0-1.0-1
RD-1139
15.3.0-1.0-1.0-1
RD-1140
15.3.0-1.0-1.0-2
RD-1141
15.3.0-1.0-2
RD-1142
15.3.0-1.0-3
RD-1143
15.3.0-1.0-4
RD-1144
15.3.0-1.0-4.0-1
RD-1145
15.3.0-1.0-5
RD-1146
RD-1147
RD-1148
RD-1149
15.3.0-1.0-5.0-1
15.3.0-1.0-5.0-2
15.3.0-1.0-5.0-3
15.3.0-1.0-5.0-4
RD-1150
15.3.0-2
RD-1151
RD-1152
RD-1153
RD-1154
15.3.0-2.0-1
15.3.0-2.0-2
15.3.0-2.0-3
15.3.0-2.0-4
RD-1155
15.3.0-2.0-4.0-1
RD-1156
15.3.0-2.0-4.0-2
RD-1157
15.3.0-2.0-4.0-3
RD-1158
RD-1159
15.3.0-2.0-5
15.3.0-3
RD-1160
15.3.0-3.0-1
RD-1161
15.3.0-3.0-2
RD-1162
15.3.0-3.0-3
RD-1163
15.3.0-3.0-4
RD-1164
15.3.0-3.0-4.0-1
RD-1165
15.3.0-3.0-4.0-2
RD-1166
15.3.0-3.0-5
RD-1167
15.3.0-4
The system shall provide the capability to log jobs.

The system shall provide the capability to manage work lists of jobs.
The system shall provide the capability to perform actions on a batch of jobs.
R1B; Must
R1B; Must
R2; Must
15.3 Workflow Monitoring

The system shall provide a monitoring tool for all workflow instances.
The monitoring tool shall provide the capability to see how many instances of
a workflow exist as well as the status of the workflow instances.
The monitoring tool shall provide the capability to see how many instances of
a workflow exist.
The monitoring tool shall provide the capability to see the status of the
workflow instances.
The monitoring tool shall provide the capability for the user to customize
views.
The monitoring tool shall provide the capability to save customized views for
future use.
The monitoring tool shall provide the capability for users to monitor processing
history of workflow instances.
The monitoring tool shall provide the capability for users to monitor processing
history over a specified time period.
The monitoring tool shall report throughput, delay, load, and additional
performance measures in the future.
The monitoring tool shall report the throughput for workflow instances.
The monitoring tool shall report any delays for workflow instances.
The monitoring tool shall report the loads for workflow instances.
The monitoring tool shall report additional performance measures in the
future.
The system shall provide the capability for users to monitor jobs or a list of
jobs.
The system shall provide the capability for users to monitor jobs.
The system shall provide the capability for users to monitor a list of jobs.
The system shall provide the capability for users to monitor a batch of jobs.
The system shall provide the capability to monitor planned, scheduled and
actual times for selected jobs.
The system shall provide the capability to monitor planned times for selected
jobs.
The system shall provide the capability to monitor scheduled times for
selected jobs.
The system shall provide the capability to monitor actual times for selected
jobs.
The system shall provide the capability to group jobs with a defined status.
The system shall provide the capability for users to monitor workflow
instances or a list of workflow instances.
instances.
instances or a list of workflow instances.
The system shall provide the capability for users to monitor a batch of
workflow instances.
The system shall provide the capability to monitor planned, scheduled and
actual times for selected workflow instances.
The system shall provide the capability to monitor planned times for selected
workflow instances.
The system shall provide the capability to monitor scheduled times for
selected workflow instances.
The system shall provide the capability to monitor actual times for selected
workflow instances.
The system shall provide the capability to group workflow instances with a
defined status.
R1B; Must
R1C; Must
R1C; Must
R1C; Must
R1B; Could
/ R1C; Must
R1B; Could
/ R1C; Must
R1B; Must
R1B; Could
/ R1C; Must
R2; Must
R1C; Must
R1C; Must
R1C; Must
R2; Must
R1B; Must
R1B; Must
R1B; Must
R1B; Must
R2; Must
R2; Must
R2; Must
R2; Must
R1B; Must
R1B; Must
R1B; Must
R1B; Must
R1B; Must
R2; Must
R2; Must
R2; Must
R2; Must
R2; Must
41

FINAL
RD-1168
15.4
15.4 Workflow Resource Requirements

RD-1169
15.4.0-1
RD-1170
15.4.0-2
RD-1171
15.4.0-3
RD-1172
15.4.0-3.0-1
RD-1173
15.4.0-3.0-2
RD-1174
15.5
The system shall provide the capability to estimate resource requirements

associated with internal workflow.
The system shall provide the capability to estimate resource requirements
associated with external workflow.
The system shall provide the capability to estimate resource requirements for
automated and manual activities.
automated activities.
manual activities.
R1B; Could
/ R1C; Must
R1C; Could
/ R2; Must
R1C; Could
/ R2; Must
R1C; Could
/ R2; Must
R1C; Could
/ R2; Must
15.5 Workflow Notification

RD-1175
15.5.0-1
RD-1176
15.5.0-2
RD-1177
15.5.0-3
RD-1178
RD-1179
RD-1180
RD-1181
15.5.0-3.0-1
15.5.0-3.0-2
15.5.0-3.0-3
15.5.0-4
RD-1182
15.5.0-5
RD-1183
15.6
The system shall provide the capability to associate notifications with

workflows.
The system shall provide the capability to manage notifications attached to
workflows.
The system shall send notifications via e-mail, the user's screen, and
additional methods in the future.
The system shall send notifications via e-mail.
The system shall send notifications via the user's screen.
The system shall send notifications via additional methods in the future.
The system shall provide the capability to configure the list of recipients of
notifications.
The system shall provide the capability to escalate notifications.
R1B; Must
R1B; Must
R2; Must
R1B; Must
R1B; Must
R2; Must
R1B; Must
R3; Should
15.6 Workflow Security

RD-1184
15.6.0-1
RD-1185
RD-1186
15.6.0-1.0-1
15.6.0-1.0-2
RD-1187
15.7
The system shall provide the capability to have security controls on workflow
activities.
The security control (allow or deny actions) shall be rule based.
Manual activities in the workflows shall be assigned with one or more security
rules.
R1B; Must
R2; Must
R2; Must
15.7 Workflow Interface

RD-1188
15.7.0-1
RD-1189
15.7.0-2
RD-1190
RD-1191
16
16.1
The system shall provide a Graphical User Interface (GUI) edit tool to manage
workflow definitions and executions.
The Monitoring Tool shall contain a GUI for all workflow monitoring
capabilities.
R1B; Must
R1B; Must
16 Requirements for Storage

Management
16.1 Storage Core Capabilities
RD-1192
16.1.0-1
RD-1193
16.1.0-2
RD-1194
16.1.0-2.0-1
RD-1195
16.1.0-2.0-2
The system shall support retrieval of data from online storage at error rates of
(TBR-1192a).
The system shall be capable of providing a secure repository environment for
all storage.
Near-line storage media shall preserve data integrity and quality for no less
than 10 years in a data center environment.
Each data center in the system shall be housed in a facility protected by
R1B; Must
R1C; Must
R1C; Must
R1C; Must
42

FINAL
RD-1196
16.1.0-2.0-3
RD-1197
16.1.0-2.0-4
RD-1198
16.1.0-2.0-5
RD-1199
16.1.0-2.0-6
RD-1200
RD-1201
16.1.0-3
16.1.0-3.0-1
RD-1202
16.1.0-3.0-2
RD-1203
16.1.0-3.0-3
RD-1204
16.1.0-3.0-4
RD-1205
16.2
RD-1206
16.2.0-1
RD-1207
16.2.0-2
RD-1210
16.2.0-5
RD-1220
16.3
physical security measures.

Each data center in the system shall be protected from power failures for the
time required to safely power down all system components.
Each data center in the system shall be equipped with power failure sensors
capable of notifying users when grid power has failed.
Each data center in the system shall be equipped with HVAC capacity equal
to 50% greater than the sum of the BTUs produced by all system equipment
located in that data center.
Each data center in the system shall be equipped with environment sensors
capable of notifying users when out of tolerance conditions are imminent.
The system shall support the capability to include multiple storage classes.
The system shall support the capability to add additional storage classes in
the future without a major redesign.
The system shall support the capability to transparently migrate data from one
storage class to another based on system policies.
The system shall support the capability for authorized users to configure the
policies used by the system to migrate data from one class of storage to
another.
The system shall support the capability for authorized users to set storage
policies for selected content packages.
R1C; Must
R1C; Must
R1C; Must
R1C; Must
R1C; Must
R1C; Must
R1C; Must
R1C; Must
R1C; Must
16.2 Content Delivery Network Storage

The system shall have the capability to store data dynamically in external
Content Delivery Networks (CDN) based on hit rate/criticality of content.
The system shall support the capability for authorized users to designate data
for storage in a Content Delivery Network.
The system shall have the capability to utilize external storage Service
Providers.
R2; Must
R1C; Must
R1C; Must
16.3 Networked Moderate Performance

Storage
RD-1226
16.4
16.4 Low Criticality- Low Cost Storage

RD-1232
16.5
16.5 Failover Storage

RD-1233
16.5.0-1
RD-1234
16.5.0-2
RD-1235
RD-1236
16.5.0-2.0-1
16.5.0-2.0-2
RD-1237
16.5.0-2.0-2.0-1
RD-1238
16.5.0-2.0-2.0-2
RD-1239
RD-1240
RD-1241
16.5.0-2.0-3
16.5.0-2.0-4
16.5.0-2.0-5
RD-1243
16.5.0-4
Failover Storage shall provide the fault tolerance required to allow the system
to survive a localized disaster.
Failover Storage shall be able to reconstitute and switch-over to alternate
systems at a remote site in the event of local catastrophic damage.
The system shall replicate all system data to a disaster recovery site.
Failover Storage shall allow the switchover to redundant components via
either user action or automatic in case of failure.
Failover Storage shall allow the switchover to redundant components via user
action.
Failover Storage shall allow the switchover to redundant components
automatically in case of failure.
The system shall replicate all content packages to a disaster recovery site.
The system shall replicate all BPI to a disaster recovery site.
The system shall provide the capability to switchover operations from the
primary to the backup site in the event of a disaster.
Failover Storage shall support alternate pathing (e.g., ability to automatically
switch between input/output (I/O) paths in the event of a failure in one of the
paths).
R1C; Must
R1C; Must
R1C; Must
R1C; Must
R1C; Must
R1C; Must
R1C; Must
R1C; Must
R1C; Must
R1C; Must
43

FINAL
RD-1244
16.6
16.6 Backup Retrieval Media Storage

RD-1245
16.6.0-1
RD-1246
16.6.0-1.0-1
RD-1247
16.6.0-1.0-2
RD-1248
16.6.0-2
RD-1249
16.6.0-2.0-1
RD-1250
16.6.0-2.0-2
RD-1251
16.6.0-2.0-3
RD-1253
16.6.0-4
RD-1254
16.6.0-4.0-1
RD-1255
16.6.0-5
RD-1256
16.6.0-5.0-1
RD-1257
16.6.0-6
RD-1258
16.7
Back-up Retrieval Media Storage shall be able to accomplish periodic backup

on mass removable storage media.
Back-up Retrieval Media Storage shall allow users to manage periodic backup
schedules.
Back-up Retrieval Media Storage shall allow backups on multiple types of
mass removable storage media.
Back-up Retrieval Media Storage shall be able to accomplish a full back-up of
all critical data in less than six hours or scheduled periodically over 24 hours.
Back-up Retrieval Media Storage shall allow users to manage which data is
listed as critical.
Back-up Retrieval Media Storage shall allow users to manage the backup
schedule.
Back-up Retrieval Media Storage shall not interfere with current system
processes.
Back-up Retrieval Media Storage shall support mirroring the write data in
cache as a method of data protection.
Back-up Retrieval Media Storage shall allow users to manage which data
should be backed up.
Back-up Retrieval Media Storage shall support proactively testing data for
errors even when the cache or disk is inactive, so that problems can be
detected before they can disrupt data flow.
Back-up Retrieval Media Storage shall allow users the ability to both schedule
and manually test data for errors even when the cache or disk is inactive.
Back-up Retrieval Media Storage shall support the process of copying data to
a second disk array, often housed in a separate location from the originating
disk array.
R1B; Must
R1B; Must
R1C; Must
R1B; Must
R1C; Must
R1B; Must
R1B; Must
R1C; Must
R1C; Must
R3; Must
R3; Must
R1C; Must
16.7 Mid-term Archival Storage

RD-1261
16.8
16.8 Long-term Permanent Archival

Storage
RD-1262
16.8.0-1
RD-1263
16.8.0-1.0-1
RD-1264
16.8.0-1.0-2
RD-1265
16.8.0-2
RD-1266
16.8.0-3
RD-1267
16.9
Long-term Permanent Archival Storage shall have off-line storage and

indexing capability for multiple Petabytes of data.
Long-term Permanent Archival Storage shall have off-line storage capacity for
multiple Petabytes of data.
Long-term Permanent Archival Storage shall have indexing capability for
multiple Petabytes of data.
Long-term Permanent Archival Storage shall have a remote storage site over
600 miles from the main GPO facility.
Long-term Permanent Archival Storage site shall preserve physical data
integrity and quality for no less than 100 Years under controlled storage
conditions (e.g., 70 F, 60% Humidity).
R1C; Must
R1C; Must
R1C; Must
R1C; Must
R3; Must
16.9 Functional Data Storage

RD-1268
RD-1269
RD-1270
RD-1275
RD-1276
RD-1277
RD-1278
16.9.0-1
16.9.0-1.0-1
16.9.0-1.0-2
16.9.0-1.0-7
16.9.0-2
16.9.0-2.0-1
16.9.0-2.0-2
RD-1279
16.9.0-2.0-3
Work In Progress (WIP) Storage

The average access time for WIPs shall be 2 seconds or less.
WIPs shall be protected from unauthorized alteration by user actions.
WIP Storage shall contain both content and metadata.
Archival Information Package (AIP) Storage
The system shall write all AIPs to archival media for off site storage.
The average access time for SIPs after submission to the system shall be 2
seconds or less.
The average access time for AIPs stored in on line storage shall be 2 seconds
R1C; Must
R1C; Must
R1C; Must
R1C; Must
R1C; Must
R1C; Must
R1C; Must
R1C; Must
44

FINAL
RD-1281
RD-1282
RD-1287
RD-1288
16.9.0-2.0-5
16.9.0-2.0-6
16.9.0-2.0-11
16.9.0-2.0-12
RD-1289
RD-1290
RD-1291
RD-1292
RD-1300
RD-1301
RD-1302
RD-1303
RD-1309
16.9.0-2.0-13
16.9.0-3
16.9.0-3.0-1
16.9.0-3.0-2
16.9.0-3.0-10
16.9.0-4
16.9.0-4.0-1
16.9.0-4.0-2
16.9.0-4.0-8
RD-1311
16.10
RD-1312
16.10.0-1
RD-1313
RD-1314
RD-1315
16.10.0-1.0-1
16.10.0-1.0-2
16.10.0-1.0-3
RD-1316
16.10.0-2
RD-1317
16.10.0-2.0-1
RD-1318
RD-1319
RD-1320
RD-1321
RD-1322
RD-1323
RD-1324
RD-1325
RD-1326
RD-1327
RD-1328
RD-1329
16.10.0-2.0-1.0-1
16.10.0-2.0-1.0-2
16.10.0-2.0-1.0-3
16.10.0-2.0-1.0-4
16.10.0-2.0-1.0-5
16.10.0-2.0-1.0-6
16.10.0-2.0-1.0-7
16.10.0-2.0-1.0-8
16.10.0-2.0-1.0-9
16.10.0-2.0-1.0-10
16.10.0-2.0-1.0-11
16.10.0-3
RD-1330
RD-1331
16.10.0-4
16.10.0-4.0-1
RD-1332
16.10.0-4.0-2
RD-1333
16.10.0-4.0-3
RD-1334
16.10.0-5
RD-1335
16.10.0-5.0-1
RD-1336
16.10.0-5.0-2
RD-1337
16.10.0-6
RD-1338
16.10.0-7
or less.
SIPs shall be protected from unauthorized alteration by user actions.
AIPs shall be protected from unauthorized alteration by user actions.
AIP Storage shall exist in isolation of other system stores.
The system shall support the capability to migrate AIP content to future
storage technologies.
AIP Storage shall contain both content and metadata.
Access Content Storage (ACS)
The average access time for ACPs shall be 2 seconds or less.
ACPs shall be protected from unauthorized alteration by user actions.
ACS shall contain both content and metadata.
Business Process information (BPI) Storage.
The average access time for BPI shall be 2 seconds or less.
BPI shall be protected from unauthorized alteration by user actions.
BPS shall contain Failover Storage.
R1C; Must
R1C; Must
R1C; Must
R1C; Must
R1C; Must
R1C; Must
R1C; Must
R1C; Must
R1C; Must
R1C; Must
R1C; Must
R1C; Must
R1C; Must
16.10 Storage System Standards

The system shall integrate with Unix and Windows based Directory Services
(Lightweight Directory Access Protocol, Active Directory), and role based
access.
The system shall integrate with Lightweight Directory Access Protocol (LDAP).
The system shall control access to data in storage based on the users role.
The system shall prefer the use of Lightweight Directory Access Protocol over
Active Directory wherever possible.
The system shall be able to ingest files stored on disk systems connected
directly to the system.
The system shall provide the capability to read files stored in common
operating system formats.
The system shall be able to ingest files stored in a FAT filesystem.
The system shall be able to ingest files stored in a FAT32 filesystem.
The system shall be able to ingest files stored in a VFAT filesystem.
The system shall be able to ingest files stored in a NTFS filesystem.
The system shall be able to ingest files stored in a HPFS filesystem.
The system shall be able to ingest files stored in a EXT2 filesystem.
The system shall be able to ingest files stored in a HFS Plus filesystem.
The system shall be able to ingest files stored in a JFS2 filesystem.
The system shall be able to ingest files stored in a UFS filesystem.
The system shall utilize common Redundant Array of Independent Disks
(RAID) Disk Data Format (DDF) architecture.
The system shall conform to commonly used, industry standard protocols.
The system shall support the capability to interface with industry standard
protocols.
The system shall use industry standard protocols when there is one that
meets the system requirements.
The system shall use of non-standard protocols only when there is no industry
standard that meets the system requirements.
The system shall allow interaction with management information bases (MIB)
via SNMP, and shall conform to or interoperate within Object-based Storage
Device (OSD) specification.
The system shall allow interaction with management information bases (MIB)
via SNMP.
The system shall conform to or interoperate within Object-based Storage
Device (OSD) specification.
The system storage shall support ANSI INCITS 388-2004 Storage
Management Initiative Specification.
The system back-up tapes shall conform to Linear Tape-Open (LTO)
standard.
R1B; Must
R1B; Must
R1C; Must
R1C; Must
R2; Must
R2; Must
R2; Must
R2; Must
R2; Must
R2; Must
R2; Must
R2; Must
R2; Must
R2; Must
R2; Must
R2; Must
R2; Must
R1C; Must
R2; Must
R2; Must
R2; Must
R2; Must
R1C; Must
R1C; Must
R1C; Must
R2; Must
R1C; Must
45

FINAL
RD-1339
16.11
16.11 Storage Monitoring

RD-1340
16.11.0-1
RD-1341
RD-1342
RD-1343
RD-1344
RD-1345
RD-1346
16.11.0-1.0-1
16.11.0-1.0-2
16.11.0-1.0-3
16.11.0-1.0-4
16.11.0-1.0-5
16.11.0-2
RD-1347
16.11.0-3
RD-1348
16.11.0-3.0-1
RD-1349
16.11.0-3.0-2
RD-1350
RD-1351
16.11.0-3.0-3
16.11.0-3.0-4
RD-1352
RD-1353
RD-1354
RD-1355
16.11.0-3.0-4.0-1
16.11.0-3.0-4.0-2
16.11.0-3.0-4.0-3
16.11.0-3.0-5
RD-1356
16.11.0-4
RD-1357
16.11.0-5
RD-1358
16.11.0-6
RD-1359
16.11.0-7
RD-1360
16.12
RD-1361
16.12.0-1
RD-1362
16.12.0-2
RD-1363
16.12.0-2.0-1
RD-1364
16.12.0-2.0-2
RD-1365
16.12.0-2.0-3
RD-1366
16.12.0-2.0-4
RD-1367
16.12.0-3
RD-1368
16.12.0-4
RD-1369
16.13
RD-1370
RD-1371
16.13.0-1
16.13.0-2
The system shall provide the capability to monitor the health of system
components in real time.
The system shall monitor the health of the network components in real-time.
The system shall monitor the health of the system applications in real-time.
The system shall monitor the health of the storage components in real-time.
The system monitor the health of the processing components in real-time.
The system shall monitor the health of the operating system in real-time.
The system shall provide the capability for the user to configure the upper and
lower bounds for system parameters being monitored.
The system shall have the ability to send alerts to users via multiple channels
should a performance problem, failure condition or impending failure be
detected.
The system shall send a notification to users when a performance problem is
detected.
The system shall send a notification to users when a failure condition is
detected.
The system shall send a notification to users when a failure is impending.
The system shall send notifications to appropriate user screen, e-mail, and via
additional methods in the future.
The system shall send notifications to the appropriate user screen.
The system shall send notifications to the appropriate e-mail.
The system shall send notifications via additional methods in the future.
The system shall allow the users to configure the problem severity level that
triggers a user notification.
The system shall have the capability to monitor real-time performance of the
system in terms of service levels.
The system shall provide storage usage metrics that allow projection of future
storage needs.
The system shall monitor a Service Level Agreement for an externally hosted
data store.
The system shall allow users to reconfigure RAID levels without vendor
assistance.
R1C; Must
R1C; Must
R1C; Must
R1C; Must
R1C; Must
R1C; Must
R1C; Must
R1C; Must
R1C; Must
R1C; Must
R1C; Must
R2; Must
R1C; Must
R1C; Must
R2; Must
R1C; Must
R1C; Must
R3; Must
R1C; Must
R2; Must
16.12 Storage Preventive Action

The system shall automatically allocate stand-by drives to replace drives that
have failed.
The system shall have the ability to allow hot swapping of components should
a failure condition be detected.
The system shall provide the capability to hot swap power supplies when a
power supply has failed.
The system shall provide the capability to hot swap cooling fans when a
cooling fan has failed.
The system shall provide the capability to hot swap disk drives in disk storage
systems when a disk drive has failed.
The system shall provide the capability to hot swap blade servers when a
blade server has failed.
The system shall have the ability to dynamically move data to improve system
performance.
The storage systems shall provide the capability to upgrade controller
microcode without shutting down the storage system.
R1C; Must
R1C; Must
R1C; Must
R1C; Must
R1C; Must
R1C; Must
R1C; Must
R2; Must
16.13 Storage Data Integrity

The system shall allow for securing of partitions.
The system shall allow encryption of logical content.
R1C; Must
R1C; Must
46

FINAL
RD-1373
16.14
16.14 Storage Allocation

RD-1374
16.14.0-1
RD-1375
16.14.0-2
RD-1376
16.14.0-3
RD-1377
16.14.0-4
RD-1378
16.14.0-5
RD-1379
RD-1380
17
17.1
The system shall support the management of heterogeneous storage

architectures (e.g. direct attached storage (DAS), network attached storage
(NAS), storage area network (SAN)).
The system shall provide the capability to automatically allocate additional
storage when a user configurable threshold is crossed.
The system shall be able to manage any infrastructure storage device
attached to the system.
The system shall allow both manual and automated compression of data at
various compression levels for infrequently accessed data.
The system shall provide the capability to allocate storage on new devices
after they have been identified by the system and formatted for use.
R1C; Must
R1C; Must
R1C; Must
R1C; Must
R1C; Must
17 Requirements for Security

17.1 Security System User
Authentication
RD-1381
17.1.0-1
RD-1382
RD-1383
RD-1384
RD-1385
RD-1386
17.1.0-1.0-1
17.1.0-1.0-2
17.1.0-1.0-3
17.1.0-1.0-4
17.1.0-1.0-5
RD-1387
17.1.0-1.0-6
RD-1388
17.1.0-2
RD-1389
17.1.0-2.0-1
RD-1390
17.1.0-2.0-2
RD-1391
17.1.0-2.0-2.0-1
RD-1392
17.1.0-2.0-2.0-1.01
RD-1393
17.1.0-2.0-2.0-1.02
RD-1394
17.1.0-2.0-3
RD-1395
RD-1396
17.1.0-3
17.1.0-4
RD-1398
RD-1399
17.1.0-6
17.1.0-6.0-1
RD-1400
RD-1401
17.1.0-6.0-2
17.1.0-7
RD-770
17.1.0-8
The system shall have the capability to authenticate users based on a unique
user identity.
The system shall authenticate system and security administrators.
The system shall authenticate system administrators.
The system shall authenticate security administrators.
The system shall support user ID and password authentication.
The system shall support a configurable minimum password length
parameter, settable by authorized system administrators. The minimum value
allowable for this parameter is eight (8).
The system shall permit stronger authentication techniques to be used for
system and security administrators (such as longer and/or more complex
passwords, public key certificate, and token based authentication).
The system shall permit users to create a unique user identity for access to
the system.
The system shall enforce uniqueness of user identity so that no two users can
use the exact same identity.
The system shall be capable of Identity Management system functionality to
facilitate provisioning of user identities for users and system administrators.
provide users and system administrators with one single interface and control
point for provisioning and managing user identities.
provide users and system administrators with one single interface and control
point for provisioning and managing user identities that will be used to support
the systems access control decisions.
The system shall deploy an initial Identity Management capability to provide
users and system administrators with one single interface and control point for
provisioning and managing user identities.
A user shall only be allowed to manage attributes associated with their own
user identity.
The system shall display a message to users if they fail to authenticate.
The system shall permit access to a default workbench for public End Users,
which does not require them to login.
The system shall comply with GPO and Federal authentication policies.
The system shall comply with GPO authentication policies specified in
P825.33.
The system shall comply with Federal authentication policies.
The system shall have the capability to support up to 2048-bit RSA
public/private key generation (asymmetric algorithm).
The system shall provide the capability to use passwords to verify the identity
of authorized users.
R1B; Must
R1B; Must
R1B; Must
R1B; Must
R1B; Must
R1C; Must
R1C; Must
R1B; Must
R1B; Must
R1B; Must
R2; Must
R2; Must
R1C; Must
R1C; Must
R1B; Must
R1B; Must
R1C; Must
R1C; Must
R1C; Must
R1C; Must
R1B; Must
47

FINAL
RD-771
17.1.0-9
RD-772
17.1.0-10
RD-773
17.1.0-11
RD-1402
17.2
RD-1403
17.2.0-1
RD-1404
17.2.0-1.0-1
RD-1405
17.2.0-1.0-1.0-1
RD-1406
17.2.0-1.0-1.0-2
RD-1407
RD-1408
17.2.0-1.0-1.0-3
17.2.0-1.0-2
RD-1409
17.2.0-1.0-2.0-1
RD-1410
17.2.0-1.0-2.0-2
RD-1411
17.2.0-1.0-3
RD-1412
RD-1413
RD-1414
17.2.0-2
17.2.0-3
17.2.0-3.0-1
RD-1415
RD-1416
RD-1417
RD-1418
17.2.0-4
17.2.0-5
17.2.0-6
17.2.0-7
RD-1419
RD-1420
RD-1421
RD-1422
17.2.0-8
17.2.0-9
17.2.0-10
17.2.0-11
RD-1423
17.2.0-12
RD-1424
17.2.0-12.0-1
RD-1425
17.2.0-12.0-2
RD-1426
17.2.0-13
RD-1427
17.2.0-14
RD-1428
17.2.0-15
RD-1429
17.3
The system shall provide the capability to use PKI certificates to verify the
identity of authorized users.
The system shall provide the capability to verify the authorization level of
authorized users to perform requested functions.
The system shall provide the capability to validate credentials (e.g. digital
certificate) of authorized users.
R1C; Must
R1B; Must
R1C; Must
17.2 Security User Access Control

The system shall have the capability to arbitrate access based on a rolebased access model driven by policy.
The system shall permit authorized system administrators to create and
assign customized roles.
The system shall permit authorized system administrators to create
customized roles.
The system shall permit authorized system administrators to assign
customized roles.
The system shall provide access control limitations to support data mining .
The system shall allow authorized system administrators to assign and
customize roles for access to system data objects and transactions.
The system shall allow authorized system administrators to assign roles for
access to system data objects and transactions.
The system shall allow authorized system administrators to customize roles
for access to system data objects and transactions.
The system shall allow the use of standards based LDAP technology for the
role based access model.
The system shall manage user accounts.
The system shall provide the capability to create user accounts.
The system shall provide the capability to create group accounts. This will
allow individual users to log into the system but provide access to an entire
group of users.
The system shall provide the capability to access user accounts.
The system shall provide the capability to delete user accounts.
The system shall provide the capability to suspend user accounts.
The system shall provide the capability to reactivate suspended user
accounts.
The system shall provide the capability for the renewal of user registrations.
The system shall have the capability to expire user accounts.
The system shall provide the capability for users to cancel their accounts.
The system shall provide the capability for users to update their account
information.
The system shall provide a means to ensure that users cannot view or modify
information of other users unless authorized.
The system shall provide a means to ensure that users cannot view
The system shall provide a means to ensure that users cannot modify
The system shall securely store personal information (e.g. user names and
passwords).
The system shall provide the capability for authorized users to manage (add,
modify, delete) information.
The system shall have the capability to provide secure interfaces for FDsys
operations.
R1C; Must
R1C; Must
R1C; Must
R1C; Must
R2; Must
R1C; Must
R1C; Must
R1C; Must
R1B; Must
R1B; Must
R1B; Must
R1B; Must
R1B; Must
R1B; Must
R1C; Must
R1C; Must
R1C; Must
R1C; Must
R1C; Must
R1C; Must
R1B; Must
R1B; Must
R1B; Must
R1B; Must
R1B; Must
R1C; Must
17.3 Security Capture and Analysis of

Audit Logs
RD-1430
RD-1431
17.3.0-1
17.3.0-1.0-1
The system shall keep an audit log of all transactions in the system.
The system shall create audit logs which contain sufficient information to
establish what events occurred, the source(s) of the events, and the outcomes
of the events.
R1C; Must
R1C; Must
48

FINAL
RD-1432
17.3.0-1.0-1.0-1
RD-1433
17.3.0-1.0-1.0-2
RD-1434
17.3.0-1.0-1.0-3
RD-1435
17.3.0-1.0-1.0-4
RD-1436
17.3.0-1.0-1.0-5
RD-1437
17.3.0-1.0-1.0-6
RD-1438
RD-1439
17.3.0-1.0-2
17.3.0-1.0-2.0-1
RD-1440
17.3.0-1.0-2.0-2
RD-1441
17.3.0-1.0-2.0-3
RD-1442
17.3.0-1.0-2.0-4
RD-1443
17.3.0-1.0-2.0-5
RD-1444
17.3.0-1.0-2.0-6
RD-1445
17.3.0-1.0-2.0-7
RD-1446
17.3.0-1.0-3
RD-1447
17.3.0-1.0-4
RD-1448
RD-1449
17.3.0-1.0-4.0-1
17.3.0-1.0-5
RD-1450
RD-1451
17.3.0-1.0-5.0-1
17.3.0-1.0-5.0-2
RD-1452
17.3.0-1.0-5.0-3
RD-1453
17.3.0-1.0-6
RD-1454
RD-1455
17.3.0-1.0-6.0-1
17.3.0-1.0-7
RD-1456
RD-1457
17.3.0-1.0-7.0-1
17.3.0-1.0-8
RD-1458
RD-1459
RD-1460
RD-1461
RD-1462
RD-1463
RD-1464
RD-1465
RD-1466
RD-1467
RD-1468
RD-1469
17.3.0-1.0-8.0-1
17.3.0-1.0-9
17.3.0-1.0-10
17.3.0-1.0-11
17.3.0-1.0-12
17.3.0-1.0-13
17.3.0-1.0-13.0-1
17.3.0-1.0-13.0-2
17.3.0-1.0-13.0-3
17.3.0-1.0-14
17.3.0-1.0-15
17.3.0-1.0-16
Audit logs shall contain logged events which each contain the date the event
occurred.
Audit logs shall contain logged events which each contain the time the event
occurred.
Audit logs shall contain logged events which each contain the software
module (source) that logged the event, which can be either an application
name or a component of the system or of a large application, such as a
service name.
Audit logs shall contain logged events which each contain a classification of
the event by the event source.
Audit logs shall contain logged events which each contain a classification of
the event severity: Error, Information, or Warning in the system and
application logs; Success Audit or Failure Audit in the security log.
Audit logs shall contain logged events which each contain a number
identifying the particular event type.
Audit logs shall contain a description of the event.
Audit logs shall contain a description of the event containing the user name of
the user on whose behalf the event occurred.
Audit logs shall contain a description of the event containing the name (IP
address and DNS name) of the system on which the event occurred.
Audit logs shall contain a description of the event containing a description of
any significant problems, such as a loss of data or loss of functions.
Audit logs shall contain a description of the event containing information about
infrequent significant events that describe successful operations of major
server services.
Audit logs shall contain a description of the event containing warnings, events
that are not necessarily significant, but that indicate possible future problems.
Audit logs shall contain a description of the event containing an audit of the
security access attempts that were successful.
Audit logs shall contain a description of the event containing an audit of the
security access attempts that failed.
Audit logs shall contain additional data fields where binary data can be
displayed in bytes or words.
The system shall maintain a system log containing events logged by the
system components.
The system shall allow system logs to be viewed by all authorized users.
The system shall maintain a security log containing valid and invalid logon
attempts as well as events related to resource use, such as creating, opening,
or deleting files or other objects.
The system shall allow security logs to be viewed by all authorized users.
The system shall maintain a security log containing logon attempts (both valid
and invalid).
The system shall maintain a security log containing events related to resource
use, such as creating, opening, or deleting files or other objects.
The system shall maintain an application log containing events logged by
applications.
The system shall allow applications logs to be viewed by all authorized users.
The system shall have an Audit Log manager for system administrator
functions.
The Audit Log manager shall be searchable.
The system shall provide the capability to log completed transaction
information.
The system shall provide the capability to view completed transaction.
The system shall keep an audit log of user ordering (request) transactions.
The system shall keep an audit log of system administration transactions.
The system shall keep an audit log of security administrator transactions.
The system shall keep an audit log of system access rights.
The system shall keep an audit log of preservation processes.
The system shall keep an audit log of deposited content activities.
The system shall keep an audit log of harvested content activities.
The system shall keep an audit log of converted content activities.
The system shall keep an audit log of Content Originator ordering activities.
The system shall keep an audit log of content authentication activities.
The system shall keep an audit log of version control activities.
R1C; Must
R1C; Must
R1C; Must
R1C; Must
R1C; Must
R1C; Must
R1C; Must
R1C; Must
R1C; Must
R1C; Must
R1C; Must
R1C; Must
R1C; Must
R1C; Must
R2; Must
R1B; Must
R1B; Must
R1C; Must
R1C; Must
R1C; Must
R1C; Must
R1C; Must
R1C; Must
R1C; Must
R1C; Must
R1C; Must
R1C; Must
R1C; Must
R1C; Must
R1C; Must
R1C; Must
R1C; Must
R1C; Must
R1C; Must
R1C; Must
R1C; Must
R1C; Must
R1C; Must
49

FINAL
RD-1470
RD-1471
RD-1472
RD-1473
RD-1474
RD-1475
RD-1476
RD-1477
17.3.0-1.0-17
17.3.0-1.0-18
17.3.0-1.0-19
17.3.0-2
17.3.0-2.0-1
17.3.0-2.0-2
17.3.0-3
17.3.0-3.0-1
RD-1478
17.3.0-4
RD-1479
RD-1480
RD-1481
RD-1482
17.3.0-4.0-1
17.3.0-4.0-2
17.3.0-4.0-3
17.3.0-4.0-4
RD-1483
17.4
RD-1484
17.4.0-1
RD-1485
RD-1486
17.4.0-1.0-1
17.4.0-1.0-2
RD-1487
17.4.0-1.0-3
RD-1488
17.4.0-1.0-4
RD-1489
17.4.0-1.0-5
RD-1490
17.4.0-1.0-6
RD-1491
17.5
The system shall keep an audit log of cataloging activities.

The system shall keep an audit log of support activities (e.g., support status).
The system shall keep an audit log for data mining.
The system shall have the capability to maintain integrity of audit logs.
The system shall protect the audit log from unauthorized user modification.
The system shall detect user attempts to edit audit logs.
The system shall keep an audit log of attempts to access the system.
The system shall keep an audit log of any detected breaches of security
policy.
The system shall keep and store audit logs (e.g. audit trails) and utilize
records management processes on these stores.
The system shall keep audit logs (e.g. audit trails) per GPO P825.33.
The system shall store audit logs (e.g. audit trails) per GPO P825.33.
The system shall utilize records management processes on audit log stores.
The system shall save audit logs as specified in GPO Publication 825.33.
R1C; Must
R1C; Must
R2; Must
R1C; Must
R1C; Must
R1C; Must
R1C; Must
R1C; Must
R1C; Must
R1C; Must
R1C; Must
R1C; Must
R1C; Must
17.4 Security User Privacy

The system shall support the capability of maintaining user privacy in
accordance with GPO's privacy policy and Federal privacy laws and
regulations.
The system shall conform to guidelines set forth in GPO Publication 825.33.
The system shall support compliance outlined in Title 5 USC Sec. 552a
(Records maintained on individuals).
The system shall support the capability of maintaining access privacy (e.g.,
Search, Request).
The system shall support the capability of maintaining support privacy (e.g.,
user identity).
The system shall support the capability of maintaining Content Originator
ordering privacy.
The system shall provide measures that preclude a single authorized
administrator from listing an end user's orders.
R1C; Must
R1C; Must
R1C; Must
R1C; Must
R1C; Must
R1C; Must
R1C; Must
17.5 Security Confidentiality

RD-1492
17.5.0-1
RD-1493
17.5.0-1.0-1
RD-1496
17.5.0-1.0-1.0-3
RD-1497
17.5.0-1.0-2
RD-1498
17.5.0-2
RD-1499
17.5.0-2.0-1
RD-1502
17.6
RD-1503
17.6.0-1
RD-1504
17.6.0-1.0-1
RD-1505
17.6.0-1.0-2
RD-1506
17.6.0-2
The system shall support the capability of maintaining confidentiality of user

data (e.g., passwords).
The system shall have the capability to provide confidentiality of user data,
including user authentication data exchanged through external interfaces.
The system shall use a minimum 128 bit key length for all symmetric
encryption operations.
The system shall have the capability to provide confidentiality of user data,
including confidentiality of user authentication data stored within the system
(e.g., passwords).
The system shall support the capability of maintaining confidentiality of
sensitive content in accordance with NIST and FIPS requirements for
Sensitive But Unclassified (SBU) content.
The system shall provide a method of protecting confidential and private
Fdsys system data. (e.g., passwords, private user data, PII, credit cards
numbers)
R1B; Must
R1C; Must
R1C; Must
R1B; Must
R1C; Must
R1C; Must
17.6 Security Administration

The system shall provide an administrative graphical user interface to perform
user administration and security administration.
user administration.
security administration.
The system shall have the capability for authorized security administrators to
R1C; Must
R1C; Must
R1C; Must
R1C; Must
50

FINAL
RD-1507
17.6.0-2.0-1
RD-1508
17.6.0-2.0-2
RD-1509
17.6.0-2.0-2.0-1
RD-1510
17.6.0-2.0-2.0-2
RD-1511
RD-1512
17.6.0-2.0-2.0-3
17.6.0-2.0-2.0-4
RD-1513
17.6.0-2.0-2.0-5
RD-1514
17.6.0-2.0-3
RD-1515
17.6.0-3
RD-1516
17.6.0-3.0-1
RD-1517
17.6.0-3.0-2
RD-1518
17.6.0-4
RD-1519
17.6.0-4.0-1
RD-1520
17.6.0-4.0-2
RD-1521
17.6.0-4.0-3
RD-1522
17.7
set and maintain system security policy.

set system security policy.
System security policy parameters shall include the capability to support
various authentication methods.
System security policy parameters shall include authorized user
authentication methods.
System security policy parameters shall include administrator authentication
methods.
System security policy parameters shall include minimum passwords lengths.
System security policy parameters shall include authorized encryption
algorithms.
The system shall be flexible enough to incorporate additional, GPO-defined
system security policy parameters.
maintain system security policy.
The system shall provide the capability for authorized security administrators
to monitor system security policy settings and policy enforcement.
to monitor system security policy settings.
to monitor system security policy enforcement.
The system shall provide the capability to define tasks that require more than
one authorized administrator to perform (e.g., setting or changing critical
system security policies, two person integrity (TPI)).
The system shall have the capability to enforce the separation of functions
through assigned roles.
The system shall provide the capability to partition security administration into
logical elements such that security administrators can be assigned
accordingly.
The system shall provide the capability to limit security administrator's
authority to assigned logical elements.
R1C; Must
R1C; Must
R1C; Must
R1C; Must
R1C; Must
R1C; Must
R1C; Must
R1C; Must
R1C; Must
R1C; Must
R1C; Must
R1C; Must
R1C; Must
R1C; Must
R1C; Must
17.7 Security Availability

RD-1523
17.7.0-1
RD-1524
17.7.0-1.0-1
RD-1525
17.7.0-1.0-2
RD-1526
17.7.0-1.0-3
RD-1527
RD-1528
RD-1529
17.7.0-1.0-3.0-1
17.7.0-1.0-4
17.7.0-1.0-4.0-1
RD-1530
17.7.0-1.0-4.0-2
RD-1531
RD-1532
RD-1533
17.7.0-1.0-5
17.7.0-1.0-6
17.7.0-1.0-7
RD-1534
17.7.0-1.0-7.0-1
RD-1535
17.7.0-1.0-7.0-2
RD-1536
17.7.0-1.0-7.0-3
RD-1537
RD-1538
RD-1539
17.7.0-1.0-7.0-4
17.7.0-1.0-7.0-5
17.7.0-1.0-8
The system shall provide appropriate backup and redundant components to

ensure availability to meet customer and GPO needs.
The system shall provide appropriate backup components to ensure
availability to meet customer and GPO needs.
The system shall provide appropriate redundant components to ensure
availability to meet customer and GPO needs.
The system shall be operational in the event of disaster situations with
minimal business interruption to business functions.
The system shall return to normal operations post-disaster.
The system shall adhere to GPOs Continuity of Operations (COOP) plans.
The system shall adhere to system development guidelines set forth in Office
of Management and Budget Circular A-130.
The system shall adhere to guidelines set forth in Federal Preparedness
Circular 65.
The system shall have appropriate failover components.
The system shall be operational at appropriate GPO alternate facilities.
The system shall back up system applications and data at a frequency as
determined by business requirements.
The system shall back up system applications at a frequency as determined
by business requirements.
The system shall back up system data at a frequency as determined by
business requirements.
The system applications and data shall be backed up at off-site storage
location.
The system applications shall be backed up at off-site storage location.
The system data shall be backed up at off-site storage location.
The system shall interface with designated GPO Service Providers (e.g.
Oracle).
R1C; Must
R1C; Must
R1C; Must
R1C; Must
R1C; Must
R1C; Must
R1C; Must
R1C; Must
R1C; Must
R1C; Must
R1C; Must
R1C; Must
R1C; Must
R1C; Must
R1C; Must
R1C; Must
R1C; Must
51

FINAL
RD-1540
RD-1541
17.7.0-1.0-9
17.7.0-1.0-10
RD-1542
17.7.0-1.0-11
RD-1543
17.7.0-1.0-11.0-1
RD-1544
17.7.0-1.0-11.0-2
RD-1545
17.8
The system shall maintain data integrity during backup processing.

The system shall have no restrictions that would prevent the system from
being operated at a hosting vendor site, at GPOs sole discretion, at any point
in the future.
The system shall have the following security capabilities to permit the system
to be operated at a hosting vendor site, at GPOs sole discretion.
Mutually authenticated, high speed connection between GPO offices and
hosting site shall be utilized.
Encrypted connection using industry standard IPSEC Virtual Private Network
(VPN) and strong (128 bit key minimum) encryption shall be utilized.
R1B; Must
R1B; Must
R1C; Must
R1C; Must
R1C; Must
17.8 Security Integrity

RD-1546
17.8.0-1
RD-1547
17.8.0-2
RD-1548
RD-1549
17.8.0-2.0-1
17.8.0-2.0-2
RD-1550
17.9
The system shall have the capability to assure integrity of business process
information (BPI).
The system shall check content for malicious code (e.g., worms and viruses)
prior to ingest to maintain integrity.
The system shall utilize GPO virus scanner technology.
If malicious code is detected in content, it shall be placed into a quarantine
area for GPO inspection.
R1C; Must
R1B; Must
R1B; Must
R1B; Must
17.9 Security Standards

RD-1551
17.9.0-1
RD-1552
17.9.0-1.0-1
RD-1553
17.9.0-1.0-2
RD-1554
17.9.0-1.0-3
RD-1555
17.9.0-1.0-4
RD-1556
17.9.0-1.0-5
RD-1557
17.9.0-1.0-6
RD-1558
17.9.0-1.0-7
RD-1559
17.9.0-1.0-8
RD-1560
17.9.0-1.0-9
RD-1561
17.9.0-1.0-10
RD-1562
17.9.0-1.0-11
RD-1563
17.9.0-1.0-12
RD-1564
17.9.0-1.0-13
RD-1565
17.9.0-1.0-14
RD-1566
17.9.0-2
RD-1567
17.9.0-2.0-1
RD-1568
17.9.0-2.0-2
RD-1569
17.9.0-2.0-3
The system shall have the capability to support the following industry integrity
standards.
The system shall have the capability to support the RSA Digital Signature in
accordance with IETF RFC 3447.
The system shall have the capability to support Public Key Infrastructure (PKI)
PKCS #1 standards.
PKCS #7 standards.
PKCS #11 standards.
PKCS #12 standards.
The system shall have the capability to support the International Telephone
Union (ITU) X.509 v3 standard for certificate format.
The system shall have the capability to support the IETF Public Key
Infrastructure Exchange (PKIX) X.509 v3 standards for certificate
compatibility.
The system shall have the capability to support the Keyed-Hash Message
Authentication Code (HMAC) standard as specified in FIPS Pub 198.
The system shall have the capability to support the Cyclical Redundancy
Checking (CRC) 32 (CRC-32) standard, to include Cyclic Redundancy
Checking (CRC) and checksum.
The system shall have the capability to support the FIPS 180-2 Secure Hash
Algorithm (SHA) SHA-1 standard.
The system shall the capability to support the FIPS 180-2 Secure Hash
The system shall have the capability to support the XML Digital Signature
standards defined in RFC 3275 and XMLDSIG.
The system shall have the capability to support the following confidentiality
standards.
The system shall have the capability to support the FIPS 197 Advanced
Encryption Standard (AES).
The system shall have the capability to support the ANSI X9.52 Triple Data
Encryption Standard (TDES).
The system shall have the capability to support the Secure Sockets Layer
R1C; Must
R1C; Must
R1C; Must
R1C; Must
R1C; Must
R1C; Must
R1C; Must
R1C; Must
R1C; Must
R1C; Must
R1C; Must
R1C; Must
R3; Must
R1C; Must
R1C; Must
R1C; Must
R1C; Must
R1C; Must
52

FINAL
RD-1570
RD-1571
17.9.0-2.0-4
17.9.0-2.0-5
RD-1572
17.9.0-3
RD-1573
17.9.0-3.0-1
RD-1574
17.9.0-3.0-2
RD-1575
17.9.0-3.0-3
RD-1576
RD-1577
18
18.1
RD-1578
18.1.0-1
RD-1579
RD-1580
RD-1581
RD-1582
RD-1583
RD-1584
RD-1585
RD-1586
18.1.0-1.0-1
18.1.0-1.0-2
18.1.0-1.0-3
18.1.0-1.0-4
18.1.0-1.0-5
18.1.0-1.0-5.0-1
18.1.0-1.0-5.0-2
18.1.0-1.0-6
RD-1587
RD-1588
RD-1589
RD-1590
RD-1591
18.1.0-1.0-6.0-1
18.1.0-1.0-6.0-2
18.1.0-1.0-6.0-3
18.1.0-1.0-6.0-4
18.1.0-2
RD-1592
18.1.0-2.0-1
RD-1593
18.1.0-2.0-2
RD-1594
18.1.0-3
RD-1595
18.1.0-3.0-1
RD-1596
18.1.0-4
RD-1597
RD-1598
18.1.0-4.0-1
18.1.0-5
RD-1599
18.1.0-6
RD-1600
18.1.0-6.0-1
RD-1601
18.1.0-6.0-2
RD-1602
18.1.0-6.0-3
RD-1603
18.1.0-6.0-4
(SSL) version 3 / Transport Layer Security (TLS) standards per the guidelines
in NIST SP 800-52.
The system shall have the capability to comply with FIPS 140-2.
The system shall have the capability to support the W3C XML Encryption
standard XMLENC.
The system shall have the capability to support the following access control
standards.
The system shall have the capability to support the Lightweight Directory
Access Protocol (LDAP) Internet Engineering Task Force (IETF) Request for
Comments (RFC) 2251.
The system shall have the capability to support the International Telephone
Union (ITU) X.500 standards.
The system shall have the capability to support the Security and Access
Markup Language (SAML) version 2 standard as specified by OASIS.
R1C; Must
R1C; Must
R1C; Must
R1C; Must
R1C; Must
R1C; Must
18 Requirements for Enterprise

Service Bus
18.1 ESB Core Capabilities
The system shall provide the capability to interoperate with services or
applications deployed in different hardware and software platforms.
The ESB shall support interoperability with Java Enterprise Edition (JEE).
The ESB shall support interoperability with .Net.
The ESB shall support interoperability with Web Services.
The ESB shall support interoperability with Java Message Service (JMS).
The ESB shall support common operating systems.
The ESB shall support Microsoft Windows Server 2003.
The ESB shall support Red Hat Enterprise Advanced Server 2.1.
The ESB shall support application programmer interfaces in common
programming languages.
The ESB shall support application programmer interfaces in C.
The ESB shall support application programmer interfaces in C++.
The ESB shall support application programmer interfaces in Java.
The ESB shall support application programmer interfaces in C#.
The system shall support the ability to authenticate applications and services
and control which applications can invoke a service.
The system shall support the capability to authenticate internal processes
attempting to invoke a service provided by the system.
The system shall support the capability to authenticate external processes
attempting to invoke a service provided by the system.
The system shall provide the capability to integrate newly developed (or
acquired) services or applications (e.g. ILS, Oracle).
The system shall provide the capability to integrate with Oracle applications
and services.
The system shall provide the capability to integrate existing (or legacy)
services or applications.
The system shall provide the capability to integrate with the ILS.
The system shall provide the capability to coordinate and manage services or
applications in the form of enterprise business processes.
The system shall provide the capability to support synchronous and
asynchronous communications between services or applications.
The system shall provide the capability to support synchronous
communications between services or applications.
The system shall provide the capability to support asynchronous
The system shall provide the capability to support reliable communications
between services or applications.
The system shall provide the capability to specify the quality of service for
R1C; Must
R1B; Must
R1C; Must
R1B; Must
R1B; Must
R1B; Must
R1B; Must
R1B; Must
R1C; Must
R1B; Must
R1B; Must
R1B; Must
R1C; Must
R2; Must
R2; Must
R2; Must
R1C; Must
R1C; Must
R1B; Must
R1B; Must
R1C; Must
R1C; Must
R1B; Must
R1C; Must
R1C; Must
R1C; Must
53

FINAL
RD-1604
18.1.0-6.0-5
RD-1605
RD-1606
18.1.0-7
18.1.0-7.0-1
RD-1607
18.1.0-7.0-1.0-1
RD-1608
18.1.0-7.0-1.0-2
RD-1609
18.1.0-7.0-2
RD-1610
18.1.0-7.0-3
RD-1611
18.1.0-8
RD-1612
18.1.0-8.0-1
RD-1613
18.1.0-8.0-2
RD-1614
18.1.0-9
RD-1615
18.1.0-10
RD-1616
18.1.0-10.0-1
RD-1617
18.1.0-10.0-2
RD-1618
18.1.0-10.0-3
RD-1619
18.1.0-10.0-4
RD-1620
RD-1621
18.1.0-11
18.1.0-11.0-1
RD-1622
RD-1623
RD-1624
RD-1625
RD-1626
RD-1627
18.1.0-12
18.1.0-12.0-1
18.1.0-12.0-1.0-1
18.1.0-12.0-1.0-2
18.1.0-12.0-1.0-3
18.1.0-12.0-2
RD-1628
18.1.0-12.0-2.0-1
RD-1629
RD-1630
18.1.0-12.0-3
18.1.0-12.0-3.0-1
RD-1631
RD-1632
18.1.0-12.0-4
18.1.0-12.0-4.0-1
RD-1633
18.2
RD-1634
RD-1635
18.2.0-1
18.2.0-1.0-1
RD-1636
18.2.0-1.0-2
RD-1637
18.2.0-1.0-3
RD-1638
18.2.0-2
The system shall provide the capability to queue communications between

services and applications.
The system shall provide the capability to run process transactions.
The system shall provide the capability to manage process transactions
declaratively via system configurations.
The system shall provide the capability to manage process transactions
declaratively using a GUI.
The system shall provide the capability to store process transactions
configuration information in XML.
The system shall provide the capability to execute pre-defined process
transactions.
The system shall provide the capability to manually commit and roll back
process transactions.
The system shall provide the capability to create communications between
services or applications, internal or external, in XML form with published
schemas.
The system shall provide the capability to validate communications against
the appropriate published schema.
The system shall provide the capability to transform communications to
different published schemas.
The system shall provide the capability to perform XML document-based
routing between services or applications.
The system shall provide the capability to support incremental
implementations.
The ESB shall support the capability to deploy services without disrupting
system operations.
The ESB shall support the capability to undeploy services without disrupting
system operations that do not rely on the service which is being undeployed.
The ESB shall support the capability to deploy applications without disrupting
system operations.
The ESB shall support the capability to undeploy applications without
disrupting system operations that do not rely on the application which is being
undeployed.
The system shall provide the capability to support exception handling.
The system shall provide the capability to generate compensating
transactions for exceptions where possible.
The system shall store information related to the ESB in metadata.
The system shall store information about schemas in metadata.
The ESB shall support WSDL.
The ESB shall support WS-Security.
The ESB shall support WS-Reliability or WS-Reliable Messaging
The system shall store information about transactional operations in
metadata.
The system shall support the capability to record information about
transactions in logs.
The system shall store information about communications in metadata.
The system shall support the capability to record information about message
traffic in logs.
The system shall store information about business processes in metadata.
The system shall support the capability to record information about business
process execution in logs.
R1C; Must
R1C; Must
R1C; Must
R1C; Must
R1C; Must
R1C; Must
R1C; Must
R1C; Must
R1C; Must
R1C; Must
R1B; Must
R1C; Must
R1C; Must
R1C; Must
R1C; Must
R1C; Must
R1C; Must
R3; Should
R1B; Must
R1C; Must
R1B; Must
R1C; Must
R1C; Must
R1B; Must
R1B; Must
R1B; Must
R1B; Must
R1B; Must
R1B; Must
18.2 ESB Configuration

The system shall provide the capability to perform integration configurations.
The system shall provide the capability to manage integration configurations
using a GUI.
The system shall provide the capability to perform integration configurations in
XML.
The system shall provide the capability to store integration configuration
information in XML.
The system shall provide the capability to add redundancy to critical ESB
functions.
R1C; Must
R1C; Must
R1C; Must
R1C; Must
R2; Must
54

FINAL
RD-1639
18.3
18.3 ESB Administration

RD-1640
18.3.0-1
RD-1641
18.3.0-2
RD-1642
18.3.0-3
RD-1643
RD-1644
RD-1645
RD-1646
18.3.0-3.0-1
18.3.0-3.0-2
18.3.0-4
18.3.0-4.0-1
RD-1647
18.3.0-5
RD-1648
18.3.0-5.0-1
RD-1649
18.3.0-5.0-2
RD-1650
18.3.0-5.0-3
RD-1651
18.3.0-6
RD-1652
18.3.0-6.0-1
RD-1653
RD-1654
18.3.0-6.0-2
18.3.0-6.0-3
RD-1655
18.4
The system shall provide the capability to impose rule-based security control
over administrative tasks.
The system shall provide the capability to manage services or applications
dynamically.
The system shall provide the capability to enable and disable services
dynamically.
The system shall provide the capability to enable services dynamically.
The system shall provide the capability to disable services dynamically.
The system shall provide the capability to manage business processes.
The system shall provide the capability to support business process
orchestration.
The system shall provide the capability to terminate, suspend and resume
business processes.
The system shall provide the capability to terminate business processes that
are being orchestrated.
The system shall provide the capability to suspend business processes that
are being orchestrated.
The system shall provide the capability to resume business processes that are
suspended.
The system shall provide the capability to monitor ESB processes that are
being orchestrated.
The system shall provide the capability to monitor the business processes at
all available statuses: active, suspended, terminated, and completed.
The system shall provide the capability to monitor communication latencies.
The system shall provide the capability to send notifications in the event of
problems with ESB functions.
R3; Must
R1C; Must
R2; Must
R2; Must
R2; Must
R1C; Must
R1C; Must
R1C; Must
R1C; Must
R1C; Must
R1C; Must
R1C; Must
R1C; Must
R1C; Must
R1C; Must
18.4 ESB Interface

RD-1656
18.4.0-1
The system shall provide the capability to perform configuration tasks via a
Graphical User Interface (GUI) tool.
The system shall provide the capability to perform administrative tasks via a
GUI tool.
RD-1657
18.4.0-2
RD-1658
RD-1659
19
19.1
RD-1660
19.1.0-1
RD-1661
19.1.0-2
RD-1662
19.1.0-3
RD-1663
RD-1664
19.1.0-3.0-1
19.1.0-3.0-2
RD-1665
19.1.0-4
RD-1666
RD-1667
19.1.0-5
19.1.0-6
The system shall be able to extract data according to user defined queries.
The system shall be able to extract random samples of data.
RD-1668
19.1.0-7
The system shall allow users to input data to supplement system data (e.g.,
Web log, historical sales data).
R1C; Must
R1C; Must
19 Requirements for Data Mining

19.1 Data Mining Data Extraction
The system shall be capable of extracting data from the entire collection of
BPI.
The system shall be capable of extracting data from the entire collection of
metadata.
The system shall be capable of extracting data from select GPO data sources
(e.g., Oracle).
The system shall be capable of extracting data from Oracle.
The system shall be capable of extracting data from additional GPO data
sources in the future.
The system shall be capable of extracting data according to a schedule
defined by users.
R2; Must
R2; Must
R3; Must
R2; Must
R3; Must
R1C;
Should /
R2; Must
R2; Must
R1C; Could
/ R2; Must
R1C;
Should /
R2; Must
55

FINAL
RD-1669
19.1.0-7.0-1
The system shall allow users to upload files from which data will be extracted
for analysis.
RD-1670
19.1.0-7.0-2
The system shall allow users to enter supplemental historical data.
RD-1671
19.1.0-7.0-3
The system shall allow users to restrict access to supplemental data.
RD-1672
19.1.0-7.0-4
The system shall allow users to store supplemental data for future use.
RD-1673
RD-1674
19.1.0-8
19.1.0-8.0-1
RD-1675
19.1.0-8.0-2
RD-1676
19.1.0-8.0-3
RD-1677
19.1.0-8.0-4
RD-1678
19.1.0-8.0-5
RD-1679
19.1.0-9
The system shall be capable of extracting data from multiple formats.

The system shall be capable of extracting data from data sources in XML
format.
The system shall be capable of extracting data from data sources in PDF
format.
The system shall be capable of extracting data from data sources in XLS
format.
The system shall be capable of extracting data from data sources in CSV
format.
The system shall be support the capability of extracting data from data
sources in additional formats in the future.
The system shall be capable of data extraction at speeds sufficient to support
the creation of real-time reports.
RD-1680
19.2
RD-1681
19.2.0-1
RD-1682
RD-1683
RD-1684
RD-1685
RD-1686
RD-1687
RD-1688
19.2.0-1.0-1
19.2.0-1.0-2
19.2.0-1.0-3
19.2.0-1.0-4
19.2.0-1.0-5
19.2.0-1.0-6
19.2.0-2
RD-1689
19.3
R1C;
Should /
R2; Must
R1C;
Should /
R2; Must
R1C;
Should /
R2; Must
R1C;
Should /
R2; Must
R2; Must
R2; Must
R2; Must
R2; Must
R2; Must
R3; Must
R1C;
Should /
R2; Must
19.2 Data Mining Data Normalization

The system shall be able to normalize data based on additional administrator
defined parameters in the future.
The system shall be able to identify missing values or metadata elements.
The system shall be able to identify data anomalies in BPI and metadata.
The system shall be able to identify data formats.
The system shall be able to identify format discrepancies.
The system shall be able to identify standard data elements.
The system shall be able to identify data types.
The system shall be able to merge and separate data sets based on
administrator defined parameters (e.g., joining or separating fields, removing
NULL values, string conversion of date data).
R2; Must
R2; Must
R2; Must
R2; Must
R2; Must
R2; Must
R2; Must
R2; Must
19.3 Data Mining Data Analysis and

Modeling
RD-1690
19.3.0-1
RD-1691
19.3.0-1.0-1
RD-1692
19.3.0-1.0-2
RD-1693
RD-1694
RD-1695
RD-1696
RD-1697
19.3.0-1.0-3
19.3.0-1.0-3.0-1
19.3.0-1.0-3.0-2
19.3.0-1.0-3.0-3
19.3.0-1.0-4
The system shall be able to perform single variable and multivariable analysis
operations on extracted data.
The system shall be able to perform single variable analysis operations on
extracted data.
The system shall be able to perform multivariable analysis operations on
extracted data.
The system shall be able to calculate averages (mean, median, mode).
The system shall be able to calculate means.
The system shall be able to calculate medians.
The system shall be able to calculate modes.
The system shall be able to perform cross tabulations.
RD-1698
19.3.0-1.0-5
The system shall be able to perform clusterization.
RD-1699
19.3.0-1.0-6
The system shall be able to perform categorization.
RD-1700
19.3.0-1.0-7
The system shall be able to perform association and link analyses.
R2; Must
R2; Must
R2; Must
R2; Must
R2; Must
R2; Must
R2; Must
R1C; Could
/ R2; Must
R1C; Could
/ R2; Must
R1C; Could
/ R2; Must
R1C; Could
56

FINAL
RD-1701
19.3.0-1.0-8
The system shall be able to perform regression analysis.
RD-1702
19.3.0-1.0-9
The system shall be able to expose hierarchical or parent/child relationships.
RD-1703
19.3.0-1.0-10
The system shall be able to expose sequential relationships and patterns.
RD-1704
19.3.0-1.0-10.0-1
The system shall be able to expose sequential relationships.
RD-1705
19.3.0-1.0-10.0-2
The system shall be able to expose sequential patterns.
RD-1706
19.3.0-1.0-11
The system shall be able to expose temporal relationships and patterns.
RD-1707
19.3.0-1.0-11.0-1
The system shall be able to expose temporal relationships.
RD-1708
19.3.0-1.0-11.0-2
The system shall be able to expose temporal patterns.
RD-1709
19.3.0-1.0-12
RD-1710
19.3.0-2
RD-1711
19.3.0-2.0-1
RD-1712
19.3.0-3
The system shall be able to expose inferences and rules that led to a result
set.
The system shall be able to warn users attempting illogical operations (e.g.,
calculating averages out of categorical data).
The system shall be capable of showing the user the rule violation that led to
the warning.
The system shall allow users to suspend, resume, or restart analysis
RD-1713
19.3.0-3.0-1
The system shall allow users to suspend an analysis that is in progress.
RD-1714
19.3.0-3.0-2
The system shall allow users to resume a suspended analysis.
RD-1715
19.3.0-3.0-3
The system shall allow users to restart an analysis from the beginning.
RD-1716
19.3.0-4
The system shall be capable of providing the user with an estimated analysis
time.
RD-1717
19.4
/ R2; Must
R1C; Could
/ R2; Must
R1C; Could
/ R2; Must
R1C; Could
/ R2; Must
R1C; Could
/ R2; Must
R1C; Could
/ R2; Must
R1C; Could
/ R2; Must
R1C; Could
/ R2; Must
R1C; Could
/ R2; Must
R2; Could /
R3; Must
R2; Could
R2; Could
R1C;
Should /
R2; Must
R1C;
Should /
R2; Must
R1C;
Should /
R2; Must
R1C;
Should /
R2; Must
R2; Could
19.4 Data Mining Report Creation and

Data Presentation
RD-1718
19.4.0-1
The system shall be able to produce reports summarizing the analysis of BPI
and metadata.
The system shall allow users to choose from the data types available in BPI
and metadata and choose operations performed on that data.
The system shall be able to produce a report summarizing system usage for a
user-defined time range.
The system shall be able to produce a report analyzing the usage of search
terms.
The system shall be capable of including graphical analysis in reports,
including charts, tables, and graphs.
RD-1719
19.4.0-1.0-1
RD-1720
19.4.0-1.0-2
RD-1721
19.4.0-1.0-3
RD-1722
19.4.0-2
RD-1723
19.4.0-2.0-1
The system shall be capable of including charts in reports.
RD-1724
19.4.0-2.0-2
The system shall be capable of including tables in reports.
RD-1725
19.4.0-2.0-3
The system shall be capable of including graphs in reports.
RD-1726
19.4.0-3
The system shall allow a set of default report templates to be accessible for
each user class.
R2; Must
R2; Must
R2; Must
R2; Must
R1C;
Should /
R2; Must
R1C;
Should /
R2; Must
R1C;
Should /
R2; Must
R1C;
Should /
R2; Must
R2; Must
57

FINAL
RD-1727
RD-1728
19.4.0-3.0-1
19.4.0-4
The system shall allow users to manage the default templates.

The system shall allow users to create custom reports and report templates
based on access rights to BPI and metadata.
RD-1729
19.4.0-4.0-1
The system shall allow users to create custom report templates.
RD-1730
19.4.0-4.0-2
The system shall allow users to update custom report templates.
RD-1731
19.4.0-4.0-3
The system shall allow users to delete custom report templates.
RD-1732
19.4.0-5
The system shall be capable of real-time population of report templates.
RD-1733
19.4.0-6
RD-1734
19.4.0-6.0-1
RD-1735
19.4.0-6.0-2
RD-1736
19.4.0-6.0-2.0-1
RD-1737
19.4.0-6.0-2.0-2
RD-1738
19.4.0-7
The system shall be capable of automatically creating reports using report

templates according to a schedule defined by users.
The system shall allow users to request notification that a scheduled report is
available.
The system shall enable GPO users to restrict view/modify access to
customized report templates.
The system shall enable GPO users to control which users can view a report
template.
The system shall enable GPO users to control which users can modify a
report template.
The system shall be capable of delivering reports to users.
RD-1739
19.4.0-7.0-1
RD-1740
19.4.0-7.0-1.0-1
RD-1741
19.4.0-7.0-1.0-2
The system shall allow users to specify delivery method (e.g., e-mail, RSS,
FTP).
The system shall support the capability to deliver reports to users using Email.
The system shall support the capability to deliver reports to users using RSS.
RD-1742
19.4.0-7.0-1.0-3
The system shall support the capability to deliver reports to users using FTP.
RD-1743
19.4.0-8
The system shall be capable of supporting real-time reporting.
RD-1744
19.4.0-9
The system shall allow users to create notifications based on real-time

analysis of BPI or metadata.
RD-1745
RD-1746
RD-1747
19.4.0-10
19.4.0-11
19.4.0-12
RD-1748
RD-1749
19.4.0-12.0-1
19.4.0-13
RD-1750
19.4.0-13.0-1
RD-1751
19.4.0-13.0-2
The system shall be able to link analysis results to data.

The system shall be able to expose analysis criteria and algorithms.
The system shall be able to export results in a format specified by the user
(e.g., HTML, MS Word, MS Excel, character-delimited text file, XML, PDF).
The system shall be able to export reports in HTML format.
The system shall support customization and personalization functions as
defined in the FDsys access, search, request, interface, cataloging and
reference tools, and user support requirements.
The system shall support user interface customization and personalization
based on the interactions of a user with the system.
The system shall support user interface customization by aggregating the
interactions of many users with the system.
RD-1752
19.5
R2; Must
R1C;
Should /
R2; Must
R1C;
Should /
R2; Must
R1C;
Should /
R2; Must
R1C;
Should /
R2; Must
R1C;
Should /
R2; Must
R1C; Could
/ R2; Must
R1C; Could
/ R2; Must
R1C; Could
/ R2; Must
R1C; Could
/ R2; Must
R1C; Could
/ R2; Must
R1C; Could
/ R2; Must
R1C; Could
/ R2; Must
R1C; Could
/ R2; Must
R1C; Could
/ R2; Must
R1C; Could
/ R2; Must
R1C;
Should /
R2; Must
R1C;
Should /
R2; Must
R2; Could
R2; Could
R2; Must
R2; Must
R2; Must
R2; Must
R2; Must
19.5 Data Mining Security and

Administration
RD-1753
RD-1754
19.5.0-1
19.5.0-1.0-1
RD-1767
19.5.0-14
The system shall restrict access to extracted data based on user groups.
The system shall allow users to extract data from security audit logs for data
mining
The system shall perform records management functions on logs.
R2; Must
R2; Must
R2; Must
58

FINAL
RD-1768
19.6
19.6 Data Mining Storage

RD-1769
RD-1770
19.6.0-1
19.6.0-1.0-1
RD-1771
RD-1772
19.6.0-1.0-1.0-1
19.6.0-1.0-1.0-2
RD-1773
19.6.0-1.0-1.0-3
RD-1774
19.6.0-2
RD-1775
RD-1776
RD-1777
RD-1778
RD-1779
RD-1780
RD-1781
19.6.0-2.0-1
19.6.0-2.0-2
19.6.0-2.0-3
19.6.0-2.0-4
19.6.0-2.0-5
19.6.0-2.0-6
19.6.0-2.0-7
RD-1782
RD-1783
20
20.1
The system shall store extracted data.

Extracted data shall be held in temporary storage. Once analysis is complete,
extracted data is deleted from temporary storage.
The system shall provide the capability to store the corpus of extracted data.
The system shall provide the capability to delete selected portions of the
corpus of extracted data.
The system shall provide the capability to reload selected portions of the
corpus of extracted data by re-extracting the data.
The system shall store metadata, supplemental data, reports, report
templates, analysis criteria, and algorithms in Business Process Storage.
The system shall store metadata in Business Process Storage.
The system shall store supplemental data in Business Process Storage.
The system shall store reports in Business Process Storage.
The system shall store report templates in Business Process Storage.
The system shall store analysis criteria in Business Process Storage.
The system shall store algorithms in Business Process Storage.
The system shall have a records management process (e.g., delete files and
reports at a defined time).
R2; Must
R2; Must
R2; Must
R2; Must
R2; Must
R2; Must
R2; Must
R2; Must
R2; Must
R2; Must
R2; Must
R2; Must
R2; Must

Submission
20.1 Content Submission Core
Capabilities
RD-1784
RD-1785
20.1.0-1
20.1.0-2
RD-1786
20.2
The system shall accept digital content and metadata.

The system shall create a SIP from content and metadata.
R1B; Must
R1B; Must
20.2 Content Submission System

Administration
RD-1787
RD-1788
20.2.0-1
20.2.0-2
RD-1789
RD-1790
20.2.0-2.0-1
20.2.0-3
RD-1791
RD-1792
RD-1793
20.2.0-4
20.2.0-4.0-1
20.2.0-5
RD-1794
20.2.0-5.0-1
RD-1795
20.2.0-5.0-2
RD-1796
20.2.0-5.0-3
RD-1797
20.2.0-5.0-4
RD-1798
RD-1799
RD-1800
RD-1803
20.2.0-5.0-5
20.2.0-6
20.2.0-7
20.2.0-7.0-3
The system shall to be able to accept, store, and deliver encrypted files.
The system shall provide notification to the submission agency/authority that
the content has been received by Fdsys.
The system shall notify submission agency/authority if content is not received.
The system shall have the capability to provide notification to the submission
agency/authority that the content has been released to the intended users.
The system shall identify files with security restrictions upon submission.
Information about the files will be recorded in metadata.
The system shall have the capability to allow users to indicate that content
contains copyrighted material.
The system shall have the capability to allow users to specify what the
intended use and access rights to the content should be.
The system shall have the capability to allow users to specify what the
intended distribution of the content should be.
The system shall have the capability to allow authorized users to modify
access rights to content based on copyright information provided by Content
Originators.
The system shall have the capability to notify authorized users that
copyrighted content has been submitted.
Copyright information will be recorded in metadata.
The system shall provide WIP storage for content prior to ingest.
The system shall check content prior to ingest.
Zipped files (.zip) shall be unzipped.
R2; Could
R1C; Must
R1C; Must
R1B; Could
/ R1C; Must
R1C; Must
R1B; Must
R1C; Must
R1C; Must
R1C; Must
R1C; Must
R1C; Must
R1C; Must
R1B; Must
R1B; Must
R1C; Must
59

FINAL
RD-1804
RD-1805
20.2.0-7.0-4
20.2.0-8
Stuffed files (.sit) shall be unstuffed.

The system shall accept content with specialized character sets (e.g., nonRoman, scientific notations)
RD-1806
20.3
RD-1807
20.3.0-1
RD-1808
RD-1809
20.3.0-1.0-1
20.3.0-1.0-2
RD-1810
20.3.0-1.0-2.0-1
RD-1811
20.3.0-1.0-2.0-2
RD-1812
20.3.0-1.0-2.0-3
RD-1813
20.3.0-1.0-2.0-4
RD-1814
20.3.0-1.0-2.0-5
RD-1815
20.3.0-1.0-3
RD-1816
20.3.0-1.0-4
RD-1817
RD-1818
20.3.0-1.0-5
20.3.0-1.0-6
RD-1819
20.3.0-1.0-7
RD-1820
20.3.0-1.0-7.0-1
RD-1821
20.3.0-1.0-8
RD-1822
20.3.0-1.0-9
RD-1823
20.3.0-1.0-10
RD-1824
20.3.0-1.0-11
RD-1825
20.3.0-1.0-12
RD-1826
20.3.0-2
RD-1827
RD-1828
20.3.0-3
20.3.0-4
RD-1829
20.3.0-4.0-1
RD-1830
20.3.0-4.0-2
The system shall ascertain the page size of the publication.
RD-1888
RD-1831
20.3.0-4.0-3
20.3.0-4.0-4
The system shall record the page size of the publication.

The system shall ascertain the trim size of the publication.
RD-1889
RD-1832
20.3.0-4.0-5
20.3.0-4.0-6
The system shall record the trim size of the publication.

The system shall ascertain the number of pages.
RD-1890
20.3.0-4.0-7
The system shall record the number of pages.
R1C; Must
R1B; Must
20.3 Content Submission Metadata

The system shall accept all administrative and descriptive metadata supplied
by the submission agency/authority.
The system shall provide the capability to record Title or caption of content.
The system shall provide the capability to record content identifiers assigned
to content.
The system shall provide the capability to record the Persistent names
assigned to content.
The system shall provide the capability to record the filenames assigned to
content.
The system shall provide the capability to record the ISBN/ISSNs assigned to
content.
The system shall provide the capability to record the Agency requisition
numbers assigned to content.
The system shall support the capability to record additional content identifiers
in the future.
The system shall provide the capability to record Author/Creator of the
content.
The system shall provide the capability to record Publisher/Authority of the
content.
The system shall provide the capability to record Rights Owner of the content.
The system shall provide the capability to record version information of the
content.
The system shall provide the capability to record relationships between
content packages and digital objects.
The system shall provide the capability to record superseded document
information (i.e. publication title(s), series number, and stock number(s) of
replaced versions).
The system shall provide the capability to record content description
information (e.g., abstract, summary).
The system shall provide the capability to record Structure Information of the
content.
The system shall provide the capability to record Intended Output of the
content.
The system shall provide the capability to record Intended Audience of the
content.
The system shall provide the capability to record 13 Digit ISBN Numbers to
content.
The system shall record or ascertain the following information when available
and applicable.
The system shall record or ascertain elements relating to documents.
The system shall record the software applications and versions used to create
the digital objects.
The system shall ascertain the software applications and versions used to
create the digital objects.
R1B; Must
R1B; Must
R1B; Must
R1B; Must
R1B; Must
R1B; Must
R1B; Must
R3; Must
R1B; Must
R1B; Must
R1B; Must
R1B; Must
R1B; Must
R1B; Must
R1B; Must
R1B; Must
R1B; Must
R1B; Must
R1B; Must
R2; Must
R1B; Must
R1B; Must
R1C;
Should/ R2;
Must
R1C;
Should/ R2;
Must
R1B; Must
R1C;
Should/ R2;
Must
R1B; Must
R1C;
Should/ R2;
Must
R1B; Must
60

FINAL
RD-1833
20.3.0-4.0-8
The system shall ascertain the file formats.
RD-1891
RD-1834
20.3.0-4.0-9
20.3.0-4.0-10
The system shall record the file formats.

The system shall ascertain file sizes.
RD-1892
RD-1835
20.3.0-4.0-11
20.3.0-4.0-12
The system shall record file sizes.

The system shall ascertain what fonts are used in the publication.
RD-1893
RD-1836
20.3.0-4.0-13
20.3.0-4.0-14
The system shall record what fonts are used in the publication.
The system shall ascertain if the fonts are furnished or embedded.
RD-1894
RD-1837
20.3.0-4.0-15
20.3.0-4.0-16
The system shall record if the fonts are furnished or embedded.

The system shall ascertain font types.
RD-1895
RD-1838
20.3.0-4.0-17
20.3.0-4.0-18
The system shall record font types.

The system shall ascertain what color mode(s) are used in the publication.
RD-1896
RD-1839
20.3.0-4.0-19
20.3.0-4.0-20
The system shall record what color mode(s) are used in the publication.
The system shall ascertain whether bleed is required/provided for.
RD-1897
RD-1840
20.3.0-4.0-20.0-1
20.3.0-4.0-21
The system shall record whether bleed is required/provided for.

The system shall ascertain information about the construction of a publication.
RD-1898
RD-1841
20.3.0-4.0-22
20.3.0-4.0-23
The system shall record information about the construction of a publication.

The system shall ascertain image resolutions.
RD-1899
RD-1842
20.3.0-4.0-24
20.3.0-4.0-25
The system shall record image resolutions.

The system shall ascertain the language of the publication.
RD-1900
RD-1843
20.3.0-4.0-26
20.3.0-4.0-27
The system shall record the language of the publication.

The system shall ascertain file compression information.
RD-1901
RD-1844
20.3.0-4.0-28
20.3.0-4.0-29
The system shall record file compression information.

The system shall ascertain audio file formats.
RD-1904
RD-1845
20.3.0-4.0-30
20.3.0-4.0-31
The system shall record audio file formats.

The system shall ascertain the size of audio files.
RD-1905
RD-1846
20.3.0-4.0-32
20.3.0-4.0-33
The system shall record the size of audio files.

The system shall ascertain audio playing time.
RD-1906
RD-1847
20.3.0-4.0-34
20.3.0-4.0-35
The system shall record audio playing time.

The system shall ascertain the language of audio.
RD-1907
RD-1848
20.3.0-4.0-36
20.3.0-4.0-37
The system shall record the language of audio.

The system shall ascertain audio file compression information.
RD-1908
20.3.0-4.0-38
The system shall record audio file compression information.
R1C;
Should/ R2;
Must
R1B; Must
R1C;
Should/ R2;
Must
R1B; Must
R1C;
Should/ R2;
Must
R1B; Must
R1C;
Should/ R2;
Must
R1B; Must
R1C;
Should/ R2;
Must
R1B; Must
R1C;
Should/ R2;
Must
R1B; Must
R1C;
Should/ R2;
Must
R1B; Must
R1C;
Should/ R2;
Must
R1B; Must
R1C;
Should/ R2;
Must
R1B; Must
R1C;
Should/ R2;
Must
R1B; Must
R1C;
Should/ R2;
Must
R1B; Must
R1C;
Should/ R2;
Must
R1C; Must
R1C;
Should/ R2;
Must
R1C; Must
R1C;
Should/ R2;
Must
R1C; Must
R1C;
Should/ R2;
Must
R1C; Must
R1C;
Should/ R2;
Must
R1C; Must
61

FINAL
RD-1849
20.3.0-4.0-39
The system shall support the capability to ascertain the bit rate of audio.
RD-1909
RD-1850
20.3.0-4.0-40
20.3.0-4.0-41
The system shall support the capability to record the bit rate of audio.
The system shall ascertain video file formats.
RD-1912
RD-1851
20.3.0-4.0-42
20.3.0-4.0-43
The system shall record video file formats.

The system shall ascertain video file sizes.
RD-1913
RD-1852
20.3.0-4.0-44
20.3.0-4.0-45
The system shall record video files sizes.

The system shall ascertain closed captioning information.
RD-1914
RD-1853
20.3.0-4.0-46
20.3.0-4.0-47
The system shall record closed captioning information.

The system shall ascertain video runtime.
RD-1915
RD-1854
20.3.0-4.0-48
20.3.0-4.0-49
The system shall record video runtime.

The system shall ascertain video encoding scheme.
RD-1916
RD-1855
20.3.0-4.0-50
20.3.0-4.0-51
The system shall record video encoding scheme.

The system shall ascertain the language of the video.
RD-1917
RD-1856
20.3.0-4.0-52
20.3.0-4.0-53
The system shall record the language of the video.

The system shall ascertain video file compression information.
RD-1918
RD-1902
RD-1903
RD-1910
RD-1911
RD-1919
RD-1920
20.3.0-4.0-54
20.3.0-5
20.3.0-6
20.3.0-7
20.3.0-8
20.3.0-9
20.3.0-10
The system shall record video file compression information.

The system shall record and ascertain other document elements in the future.
The system shall record or ascertain elements relating to audio.
The system shall record or ascertain additional audio elements in the future.
The system shall record or ascertain elements relating to video.
The system shall record or ascertain additional video elements in the future.
The system shall provide the capability to support other formats in the future.
RD-1921
RD-1922
21
21.1
RD-1923
21.1.0-1
RD-1924
21.1.0-2
RD-1925
21.2
RD-1926
21.2.0-1
RD-1927
21.3
RD-1928
21.3.0-1
R1C;
Should/ R2;
Must
R1C; Must
R1C;
Should/ R2;
Must
R1C; Must
R1C;
Should/ R2;
Must
R1C; Must
R1C;
Should/ R2;
Must
R1C; Must
R1C;
Should/ R2;
Must
R1C; Must
R1C;
Should/ R2;
Must
R1C; Must
R1C;
Should/ R2;
Must
R1C; Must
R1C;
Should/ R2;
Must
R1C; Must
R3; Must
R1C; Must
R3; Must
R2; Must
R3; Must
R3; Must
21 Requirements for Deposited

Content
21.1 Deposited Content Core Capabilities
The system shall accept digital content and metadata provided by Content
Originators.
The system shall have the capability to notify Content Evaluators that new
content has been received by the system.
R1C; Must
R1C; Must
21.2 Deposited Content Metadata

The system shall accept approved for release information for release
rmation provided by the content originating agency.
R1C; Must
21.3 Deposited Content Interfaces

Deposited content interface shall enable Congressional Content Originators
and Agency Content Originators to:
R1C; Must
62

FINAL
RD-1929
RD-1930
RD-1931
RD-1932
RD-1933
RD-1934
21.3.0-1.0-1
21.3.0-1.0-2
21.3.0-1.0-3
21.3.0-1.0-4
21.3.0-1.0-5
21.3.0-1.0-6
RD-1935
RD-1937
21.3.0-1.0-7
21.3.0-2
RD-1938
RD-1939
RD-1940
21.3.0-2.0-1
21.3.0-2.0-2
21.3.0-2.0-3
RD-1942
RD-1943
22
22.1
Submit digital content and metadata

Submit content chain of custody information to the system
Submit intended use information to the system
Submit aved for release rmation
Receive notification of receipt of content and content ID
Receive notification if content is not received, explanation for why content was
not received, and options for proceeding
Receive notification of release of content
Deposited content interface shall enable GPO Service Providers and external
Service Providers to:
Submit digital content and metadata
R1C; Must
R1C; Must
R1C; Must
R1C; Must
R1C; Must
R1C; Must
R1C; Must
R1C; Must
R1C; Must
R1C; Must
R1C; Must
22 Requirements for Converted

Content
22.1 Converted Content Core Capabilities
RD-1944
RD-1945
22.1.0-1
22.1.0-1.0-1
RD-1946
22.2
RD-1947
22.2.0-1
RD-1948
RD-1949
RD-1950
RD-1951
22.2.0-1.0-1
22.2.0-1.0-2
22.2.0-1.0-3
22.2.0-1.0-4
RD-1952
22.2.0-1.0-5
The system shall have capability to accept converted content.

Digital content may be provided in file formats for digitized tangible documents
as specified in Appendix B: Operational Specification for Converted Content.
R1C; Must
R1C; Must
22.2 Converted Content Interfaces
RD-1953
RD-1954
23
23.1
Converted content interface shall enable GPO Service Providers and external
Service Providers to:
Submit approved content and metadata.
Provide notification of release of content
Manage converted content
R1C; Must
R1C; Must
R1C; Must
R1C; Must
R1C; Must
R1C; Must
23 Requirements for Harvested

Content
23.1 Harvested Content Core Capabilities
RD-1955
23.1.0-1
RD-1956
23.2
The system shall accept digital content and metadata delivered by the
harvesting function.
R2; Must
23.2 Harvested Content Metadata

RD-1957
23.2.0-1
RD-1958
23.3
The system shall provide the capability to record the date and time of harvest
of content.
R2; Must
23.3 Harvester Requirements

RD-1959
23.3.0-1
The harvester shall have the capability to discover, assess, and harvest inscope content from targeted Web sites.
R2; Must
63

FINAL
RD-1960
23.3.0-2
RD-1961
23.3.0-3
RD-1962
RD-1963
23.3.0-4
23.3.0-5
RD-1964
23.3.0-6
RD-1965
23.3.0-7
RD-1966
23.3.0-8
RD-1967
23.3.0-9
RD-1968
23.3.0-10
RD-1969
23.3.0-11
RD-1970
RD-1971
23.3.0-11.0-1
23.3.0-11.0-2
RD-1972
23.3.0-12
RD-1973
23.3.0-13
RD-1974
23.3.0-14
RD-1975
RD-1976
23.3.0-15
23.3.0-15.0-1
RD-1977
23.3.0-15.0-2
RD-1978
23.3.0-15.0-3
RD-1979
RD-1980
23.3.0-15.0-4
23.3.0-15.0-5
RD-1981
RD-1982
23.3.0-15.0-6
23.3.0-16
RD-1983
23.3.0-17
RD-1984
23.4
The harvester shall have the capability to ensure that it does not harvest the
same content more than once.
The harvester shall have the capability to perform the discovery, assessment,
and harvesting processes on target Web sites based on update schedules.
The harvester shall have capability to perform simultaneous harvests.
The harvester shall locate and harvest all levels of Web pages within a Web
site.
The harvester shall go outside the target domains or Web sites only when the
external domain contains in-scope content.
The harvester shall stop the discovery process when a Robots.txt is present
and prevents the harvester from accessing a Web directory, consistent with
GPO business rules.
The harvester shall stop the discovery process when a linked Web page does
not contain in-scope content.
The harvester shall flag content and URLs that are only partially harvested by
the automated harvester for manual follow-up.
The harvester shall determine if the discovered content is within the scope of
GPO dissemination programs as defined in 44USC1901, 1902, 1903, and by
GPO.
The harvester shall collect in-scope discovered content and available
metadata.
The harvester shall deliver all in-scope content and metadata to WIP storage.
The harvester shall have the ability to discover and collect all file types that
may reside on target Web sites.
The harvester shall be able to harvest and transfer a complete, fully faithful
copy of the original content (e.g., publication, digital object, audio and video
streams).
The harvester shall have the ability to maintain the directory structure of Web
sites that constitute entire publications.
The harvester shall have the capability to re-configure directory structures of
harvested content based on GPO rules and instructions (e.g., all PDF files are
placed in one folder).
The harvester shall be able to harvest hidden Web information.
The harvester shall be able to harvest content contained in query-based
databases.
The harvester shall be able to harvest content contained in agency content
management systems.
The harvester shall be able to harvest content contained on dynamically
generated Web pages.
The harvester shall be able to harvest content contained on FTP servers.
The harvester shall be able to harvest content contained behind proxy
servers.
The harvester shall be able to harvest content contained behind firewalls.
The harvester shall provide the capability to automatically route specific
content for which scope determinations could not be made to Content
Evaluators. These situations include, but are not limited to:
. Content that could not be reached by the harvester (e.g., content behind
robots.txt files and firewalls, restricted access databases, etc).
. Duplicate content that appears on more than one official Federal
Government Web site.
. Content for which not enough information or metadata exists to make scope
determinations based on harvester rules and instructions alone.
The harvester shall have the capability to time and date stamp content that
has been harvested.
R2; Must
R2; Must
R2; Must
R2; Must
R1C;
Should /
R2; Must
R2; Must
R2; Must
R2; Must
R2; Must
R2; Must
R2; Must
R2; Must
R2; Must
R2; Must
R2; Must
R2; Must
R2; Must
R2; Must
R2; Must
R2; Must
R2; Must
R2; Must
R2; Must
R2; Must
23.4 Metadata Requirements for

Harvester
RD-1985
23.4.0-1
RD-1986
23.4.0-2
The harvester shall have the ability to locate and collect all metadata
associated with harvested content, including identity, responsibility, reference
information, version/fixity, technical, administrative and life cycle dates.
The harvester shall have the ability to locate and collect unique ID and
R2; Must
R2; Must
64

FINAL
RD-1987
23.4.0-3
RD-1988
23.4.0-4
RD-1989
23.4.0-5
RD-1990
23.4.0-6
RD-1991
23.4.0-7
RD-1992
23.4.0-8
RD-1993
23.5
title/caption information.
The harvester shall have the ability to locate and collect author/creator,
publisher/authority, and rights owner information.
The harvester shall have the ability to locate and collect topical information
and bibliographic descriptions.
The harvester shall have the ability to locate and collect version, fixity,
relationship, and provenance information.
The harvester shall have the ability to locate and collect technical, structural,
file format, packaging and representation information.
The harvester shall have the ability to locate and collect administrative
metadata
The harvester shall have the capability to record the time and date of harvest.
R2; Must
R2; Must
R2; Must
R2; Must
R2; Must
R2; Must
23.5 Harvester Rules and Instructions

RD-1994
23.5.0-1
RD-1995
23.5.0-2
RD-1996
23.5.0-3
RD-1997
23.6
The harvester shall discover and identify Federal content (e.g., publications,
digital objects, audio and video) on Web sites using criteria specified by GPO
Business Units.
The harvester shall accept and apply rules and instructions that will be used to
assess whether discovered content is within scope of GPO dissemination
programs.
The harvester shall be able to create and store rule and instruction profiles for
individual targeted Web sites.
R2; Must
R2; Must
R1C; Could
/ R2; Must
23.6 Harvester Interface

RD-1998
23.6.0-1
RD-1999
23.6.0-2
RD-2000
23.6.0-2.0-1
RD-2001
23.6.0-3
RD-2002
23.7
The harvester shall provide a user interface to accommodate workflow

management and scheduling of harvesting activities.
The user interface shall allow authorized users (GPO-specified) to schedule
harvesting activities based on update schedules for targeted sites to be
harvested.
Shall accommodate the scheduling of harvests, including but not limited to
hourly, daily, weekly, biweekly, monthly, and yearly.
The user interface shall be able to manage rule and instruction profiles.
R2; Must
R2; Must
R2; Must
R2; Must
23.7 System Administration for Harvester

RD-2003
23.7.0-1
RD-2004
23.7.0-2
RD-2005
23.7.0-2.0-1
RD-2006
23.7.0-2.0-1.0-1
RD-2007
23.7.0-2.0-1.0-2
RD-2008
23.7.0-2.0-1.0-3
RD-2009
23.7.0-2.0-1.0-4
RD-2010
23.7.0-2.0-1.0-5
RD-2011
23.7.0-2.0-1.0-5.01
RD-2012
23.7.0-2.0-1.0-5.02
The harvester shall provide quality control functions to test accuracy/precision

of rule application.
The harvester shall be able to incorporate results of quality control functions
into rule and instruction creation/refinement.
The harvester shall have the capability to log and produce reports on
harvesting activities.
The harvester shall have the capability to log and report on Web sites visited
by the harvester (e.g., date, time, frequency).
The harvester shall have the capability to log and report on content
discovered, including location, title, description, and other relevant
information.
The harvester shall have the capability to log and report on scope assessment
decisions made by the harvester.
The harvester shall have the capability to log and report on target Web site
structure, hierarchy, relationships, and directories.
The harvester shall have the capability to log and report on harvester failure or
error rates (e.g. network problems, broken links, security rules, firewalls,
corrupted content).
The harvester shall have the capability to log harvester failure or error rates
(e.g. network problems, broken links, security rules, firewalls, corrupted
content).
The harvester shall have the capability to report on harvester failure or error
rates (e.g. network problems, broken links, security rules, firewalls, corrupted
content).
R2; Must
R2; Must
R2; Must
R2; Must
R2; Must
R2; Must
R2; Must
R2; Must
R2; Must
R2; Must
65

FINAL
RD-2013
23.7.0-2.0-1.0-6
The harvester shall have the capability to log and report comparing target
Web sites at different points in time (e.g., different times of harvest)
The discovery and harvesting tools shall have the ability to identify GPO as
the owner of the tools.
The harvesters method of identification shall not be intrusive to targeted Web
site.
The harvester shall have the ability to collect integrity marks associated with
content as it is being harvested.
RD-2014
23.7.0-3
RD-2015
23.7.0-4
RD-2016
23.7.0-5
RD-2017
RD-2018
24
24.1
RD-2019
24.1.0-1
RD-2020
24.1.0-2
RD-2021
24.1.0-3
RD-2022
24.1.0-4
RD-2023
24.1.0-4.0-1
RD-2024
24.1.0-4.0-2
RD-2025
24.1.0-4.0-3
RD-2026
24.1.0-5
RD-2027
24.1.0-5.0-1
RD-2028
24.1.0-5.0-1.0-1
RD-2029
24.1.0-5.0-1.0-2
Style tools shall provide the capability for users to create new content for
document creation.
Style tools shall provide the capability for users to compose content for
document creation including but not limited to text, images, and graphics.
Style tools shall allow users to compose content based on pre-defined design
rules.
Style tools shall allow users to compose content using templates based on
rules (e.g., agency style manuals).
Style tools shall have the capability to prompt users to define layout
parameters from best available or system presented options.
Style tools shall allow multiple users to work collaboratively on the same
content, prior to publication.
Style tools shall allow authorized users to approve/reject content changes
made by collaborators.
Style tools shall track approval/rejection of changes to content, prior to
publication.
Style tools shall allow for approval of content.
RD-2030
24.1.0-5.0-1.0-3
Style tools shall allow for approval of content presentation.
RD-2031
24.1.0-6
RD-2032
24.1.0-7
RD-2033
24.1.0-8
RD-2034
24.1.0-9
Style tools shall provide the capability to revert to a previously saved version
of a working file (e.g., History palette).
Style tools shall provide the capability to track and undo changes to WIP
content.
Style tools shall allow users to select output methods for viewing preliminary
composition (i.e. Preparatory representation of content format or structure).
Style tools shall interface with Content Originator ordering.
RD-2035
24.2
R2; Must
R2; Must
R2; Must
R2; Must
24 Requirements for Style Tools

24.1 Style Tools Core Capabilities
Style tools shall accept content from authorized Content Originators, Service
Providers, and Service Specialists for document creation.
Style tools shall accept metadata from authorized users (e.g., title, author).
R2; Could
R3; Must
R2; Could
R3; Must
R2; Could
R3; Must
R2; Could
R3; Must
R2; Could
R3; Must
R2; Could
R3; Must
R2; Could
R3; Must
R2; Could
R3; Must
R2; Could
R3; Must
R2; Could
R3; Must
R2; Could
R3; Must
R2; Could
R3; Must
R2; Could
R3; Must
R2; Could
R3; Must
R2; Could
R3; Must
R2; Could
R3; Must
/
/
/
/
/
/
/
/
/
/
/
/
/
/
/
/
24.2 Style Tools Automated

Composition
RD-2036
24.2.0-1
Style tools shall have the capability to automatically compose content.
RD-2037
24.2.0-1.0-1
RD-2038
24.2.0-1.0-2
RD-2039
24.2.0-1.0-3
RD-2040
24.2.0-2
Style tools shall have the capability to automatically compose content and
place graphical elements in locations using GPO or Agency guidelines.
Style tools shall have the capability to automatically compose content based
on user preferences.
Style tools shall have the capability to automatically compose content based
on content analysis.
Style tools shall allow users to modify automatically composed content.
R2; Could
R3; Must
R2; Could
R3; Must
R2; Could
R3; Must
R2; Could
R3; Must
R2; Could
R3; Must
66
/
/
/
/
/

FINAL
RD-2041
24.3
24.3 Style Tools System Administration

RD-2042
24.3.0-1
RD-2043
24.3.0-2
The system shall accept content based on the access rights and privileges of
the user submitting the content.
The system shall assign unique IDs to digital objects created by style tools.
RD-2044
24.3.0-3
The system shall provide storage for WIP style tools content.
RD-2045
24.3.0-3.0-1
RD-2046
24.3.0-3.0-2
The system shall allow management of WIP content based on access rights
and privileges.
The system shall provide tracking of all WIP activities.
RD-2047
24.3.0-3.0-3
The system shall provide search and retrieval capabilities for WIP content.
RD-2048
24.3.0-4
RD-2049
24.3.0-4.0-1
RD-2050
24.3.0-4.0-2
RD-2051
24.3.0-4.0-3
RD-2052
24.3.0-4.0-4
RD-2053
24.3.0-4.0-5
RD-2054
24.3.0-4.0-6
The system shall provide search and retrieval capabilities for content stored
within ACP storage (e.g., to allow Content Originators to pull unique digital
objects into the style tools creative process).
The system shall have the capability to provide authorized users with the
ability to cancel a job.
The system shall have the capability to send or log notification of fulfillment to
single or multiple users.
The system shall have the capability to provide notification of fulfillment based
on the log of activities.
The system shall have the capability for users to specify the methods in which
they receive fulfillment notification (e.g., email, alerts).
The system shall have the capability for users to elect not to receive
notification of fulfillment.
The system shall allow authorized users to manage fulfillment notification.
RD-2055
24.3.0-4.0-7
RD-2056
24.3.0-4.0-8
RD-2057
24.3.0-4.0-9
RD-2058
RD-2059
25
25.1
The system shall have the capability to store multiple tracking numbers for
each order.
The system shall provide a hyperlink to a fulfillment provider tracking website.
The system shall have the capability to receive multiple confirmations of
fulfillment.
R2; Could
R3; Must
R2; Could
R3; Must
R2; Could
R3; Must
R2; Could
R3; Must
R2; Could
R3; Must
R2; Could
R3; Must
R2; Could
R3; Must
R2; Should
/ R3; Must
R2; Should
/ R3; Must
R2; Should
/ R3; Must
R2; Should
/ R3; Must
R2; Should
/ R3; Must
R2; Should
/ R3; Must
R2; Should
/ R3; Must
R2; Should
/ R3; Must
R2; Should
/ R3; Must

Originator Ordering
25.1 Content Originator Ordering Core
Capabilities
RD-2060
RD-1867
25.1.0-1
25.1.0-1.0-1
RD-1868
RD-1869
25.1.0-1.0-2
25.1.0-1.0-3
RD-1870
25.1.0-1.0-4
RD-1871
25.1.0-1.0-5
RD-1872
25.1.0-1.0-6
RD-2061
25.1.0-2
RD-1857
25.1.0-2.0-1
RD-1858
25.1.0-2.0-2
The system shall provide a user interface for Content Originator ordering.
The system shall have the capability to interface with select external agency
systems in order to accept content.
The system shall provide the capability to write specifications for jobs
The system shall provide the capability to create common phrases used in
specifications.
The system shall provide the capability to save common phrases used in
specifications.
The system shall provide the capability to edit common phrases used in
specifications.
The system shall provide the capability to insert common phrases into
specifications.
The system shall have the capability to process jobs prior to content being
approved for ingest.
Users shall have the capability to submit jobs prior to content being approved
for ingest.
Users shall have the capability to write specifications for jobs prior to content
R1B; Must
R3; Could
R3; Must
R3; Must
R3; Must
R3: Must
R3; Must
R3; Must
R1C; Must
R3; Must
67
/
/
/
/
/
/
/

FINAL
RD-1859
25.1.0-2.0-3
RD-1860
25.1.0-2.0-4
RD-2062
25.1.0-3
RD-1861
RD-1862
25.1.0-3.0-1
25.1.0-3.0-2
RD-1863
RD-1864
25.1.0-3.0-3
25.1.0-3.0-4
RD-2063
RD-1865
25.1.0-4
25.1.0-4.0-1
RD-2064
25.1.0-5
RD-2065
25.1.0-6
RD-2066
25.1.0-7
RD-2067
25.1.0-8
RD-2068
RD-1866
25.1.0-9
25.1.0-9.0-1
RD-2069
25.1.0-10
RD-2070
25.1.0-11
RD-2071
25.2
being approved for ingest.

Users shall have the capability to award jobs prior to content being approved
for ingest.
Users shall have the capability to send awarded jobs to service providers prior
to content being approved for ingest.
The system shall have the capability to process jobs prior to content being
received.
Users shall have the capability to submit jobs prior to content being received.
Users shall have the capability to write specifications for jobs prior to content
being received.
Users shall have the capability to award jobs prior to content being received.
Users shall have the capability to send awarded jobs to service providers prior
to content being received.
The system shall have the capability to track jobs using the job ID.
The system shall have the capability to track job submission status using the
job ID.
The system shall have the capability to accept and store a Content Originator
supplied job tracking number in metadata.
The system shall have the capability to link the Content Originator supplied
job tracking number to the Job ID.
The system shall allow users to update the Content Originator supplied job
tracking number at any time.
The system shall notify authorized allow users that a Content Originator
supplied job tracking number has been updated.
The system shall allow users to search job BPI.
The system shall allow users to search job BPI related to a user account or
agency.
The system shall have the capability to interface with select external agency
systems in order to retrieve jobs.
The system shall adhere to policies set forth in GPO Publication 305.3.
R3; Must
R3; Must
R3; Must
R1C; Must
R3; Must
R3; Must
R3; Must
R3; Must
R1C; Must
R1B; Could
/ R1C; Must
R1B; Could
/ R1C; Must
R1C; Must
R1B; Could
/ R1C; Must
R1C; Must
R1C; Must
R3; Could
R3; Must
25.2 Content Originator Ordering Job

Management
RD-2072
25.2.0-1
RD-1873
RD-1874
RD-1875
RD-2073
25.2.0-1.0-1
25.2.0-1.0-2
25.2.0-1.0-3
25.2.0-1.0-4
RD-1876
25.2.0-1.0-4.0-1
RD-1877
25.2.0-1.0-4.0-2
RD-1878
25.2.0-1.0-4.0-3
RD-2074
25.2.0-1.0-5
RD-1879
25.2.0-1.0-5.0-1
RD-1880
25.2.0-1.0-5.0-2
RD-1881
25.2.0-1.0-5.0-3
RD-2075
25.2.0-1.0-6
RD-1882
25.2.0-1.0-6.0-1
RD-1883
25.2.0-1.0-6.0-2
RD-1884
25.2.0-1.0-6.0-3
The system shall provide the capability to acquire, store and edit BPI data on
standard forms.
The system shall provide the capability to acquire BPI data on standard forms.
The system shall provide the capability to store BPI data on standard forms.
The system shall provide the capability to edit BPI data on standard forms.
The system shall provide the capability to acquire, store and edit BPI data
specific fields contained on the Standard Form 1 (SF1).
The system shall provide the capability to acquire BPI data specific fields
contained on the Standard Form 1 (SF1).
The system shall provide the capability to store BPI data specific fields
The system shall provide the capability to edit BPI data specific fields
specific fields contained on the GPO Form 952.
contained on the GPO Form 952.
R1C; Must
R1C; Must
R1C; Must
R1C; Must
R1C; Must
R1C; Must
R1C; Must
R1C; Must
R1C; Must
R1C; Must
R1C; Must
R1C; Must
R1C; Must
R1C; Must
R1C; Must
R1C; Must
68

FINAL
RD-2076
25.2.0-1.0-7
RD-1885
25.2.0-1.0-7.0-1
RD-1886
25.2.0-1.0-7.0-2
RD-1887
25.2.0-1.0-7.0-3
RD-2077
RD-2078
25.2.0-1.0-8
25.2.0-1.0-9
RD-2080
RD-2081
RD-2084
25.2.0-3
25.2.0-3.0-1
25.2.0-6
RD-2085
25.2.0-6.0-1
RD-2086
RD-2087
25.2.0-7
25.2.0-7.0-1
RD-2088
25.2.0-7.0-1.0-1
RD-2089
25.2.0-7.0-2
RD-2090
25.2.0-8
RD-2091
25.2.0-8.0-1
RD-2092
25.2.0-9
RD-2093
25.2.0-9.0-1
RD-2094
25.2.0-9.0-2
RD-2095
25.2.0-9.0-3
RD-2096
25.2.0-9.0-4
RD-2097
25.2.0-9.0-5
RD-2098
25.2.0-10
RD-2099
25.2.0-11
RD-2100
25.2.0-12
RD-2101
RD-2102
25.2.0-13
25.2.0-13.0-1
RD-2103
25.2.0-14
RD-2104
25.2.0-14.0-1
RD-2105
25.2.0-15
RD-2106
25.2.0-15.0-1
RD-2107
25.2.0-15.0-2
RD-2108
25.2.0-15.0-3
RD-2109
25.2.0-15.0-4

The system shall allow authorized users to add new BPI fields.
The system shall provide the capability for a Content Originator to save BPI
prior to submission to GPO.
The system shall ensure users are authorized to submit jobs.
The system shall ensure users are authorized to spend funds.
The system shall provide the capability for users to search all job
specifications.
The system shall provide the capability for users to search job specifications
related to a user account or agency.
The system shall have the capability to strap jobs.
The system shall have the capability to detect similar jobs that have not been
awarded for the purpose of strapping.
The system shall have the capability to notify users of similar jobs that have
not been awarded for the purpose of strapping.
The system shall have the capability to allow users to indicate that two or
more jobs should be strapped.
The system shall have the capability to inform Content Evaluators and Service
Specialists that a new job has been placed by a Content Originator.
The system shall have the capability to send jobs to appropriate Service
Specialists and Content Evaluators based upon business rules.
The system shall have the capability to support job riders.
The system shall have the capability for Content Evaluators to add rider
information to BPI.
The system shall have the capability to add Content Evaluator rider quantity
information to the Content Originator job.
The system shall have the capability to add Content Evaluator rider fulfillment
The system shall have the capability to add Content Evaluator rider billing
The system shall have the capability for users to submit rider information to
GPO.
The system shall provide the capability to notify authorized users that riders
have been placed on their job.
The system shall provide the capability to notify users that GPO is accepting
riders for a job.
The system shall have the capability to determine contract types (e.g.,
onetime bids, SPA, term contract) based upon BPI and business rules.
The system shall allow authorized users to specify a contract type.
The system shall provide the capability for Content Originators to specify an
existing contract (e.g., SPA, Term contract).
The system shall allow authorized users to view a history of all previous jobs
based on user rights.
The system shall allow authorized users to view a history of their previous
jobs based on user rights.
The system shall provide estimated costs for GPO products and services for
jobs to users based upon user provided BPI.
The system shall have the capability to allow authorized users to enter an
estimate when submitting a job.
The system shall have the capability to allow Content Originators to enter an
The system shall have the capability to allow Service Specialists to enter an
The system shall have the capability to allow Content Originators to enter a
not to exceed price when submitting a job.
R1C; Must
R1C; Must
R1C; Must
R1C; Must
R1C; Must
R1C; Must
R1C; Must
R1C; Must
R3; Must
R3; Must
R3; Must
R3; Could
R3; Could
R1C; Must
R1C; Must
R1C; Must
R2; Should
/ R3; Must
R1C; Must
R1C; Must
R1C; Must
R1C; Must
R2; Should
/ R3; Must
R2; Should
/ R3; Must
R2; Should
/ R3; Must
R3; Could
R1C; Must
R1C; Must
R1C; Must
R1C; Must
R2; Should
/ R3; Must
R1C; Must
R1C; Must
R1C; Must
R1C; Must
69

FINAL
RD-2110
25.2.0-15.0-5
RD-2111
RD-2112
RD-2113
25.2.0-15.0-6
25.2.0-15.0-7
25.2.0-16
RD-2114
25.2.0-16.0-1
RD-2115
25.2.0-16.0-2
RD-2116
RD-2117
25.2.0-16.0-3
25.2.0-16.0-4
RD-2118
RD-2119
25.2.0-16.0-5
25.2.0-17
RD-2124
RD-2125
25.2.0-22
25.2.0-22.0-1
RD-2126
25.2.0-22.0-2
RD-2127
RD-2128
25.2.0-22.0-2.0-1
25.2.0-22.0-2.0-2
RD-2129
25.2.0-22.0-2.0-3
RD-2130
25.2.0-22.0-2.0-4
RD-2135
25.2.0-22.0-2.0-5
RD-2136
RD-2131
25.2.0-22.0-2.05.0-1
25.2.0-22.0-2.05.0-2
25.2.0-22.0-3
RD-2138
25.2.0-22.0-3.0-1
RD-2132
25.2.0-22.0-3.0-2
RD-2133
25.2.0-22.0-3.0-3
RD-2134
25.2.0-22.0-3.0-4
RD-2139
25.2.0-22.0-4
RD-2140
25.2.0-22.0-5
RD-2141
25.2.0-22.0-6
RD-2142
RD-2143
25.2.0-23
25.2.0-23.0-1
RD-2144
25.2.0-23.0-2
RD-2145
25.2.0-23.0-2.0-1
RD-2146
25.2.0-23.0-2.0-2
RD-2147
RD-2148
RD-2149
RD-2150
RD-2151
25.2.0-23.0-2.0-3
25.2.0-23.0-2.0-4
25.2.0-23.0-2.0-5
25.2.0-23.0-2.0-6
25.2.0-23.0-2.0-7
RD-2137
The system shall have the capability to allow authorized users to provide an
estimate for a job.
The system shall have the capability for users to request a price approval.
The system shall have the capability for users to approve/disapprove a price.
The system shall provide the capability for authorized users to edit job
specifications prior to contract award.
The system shall provide the capability for authorized users to edit BPI prior to
contract award.
The system shall provide the capability for authorized users to edit BPI prior to
submission to GPO.
The system shall have the capability to display BPI edits.
The system shall have the capability to display the user name of who edited
BPI.
The system shall have the capability to save all BPI edits.
The system shall have the capability to notify users that BPI for a job has
been edited.
The system shall allow users to select fulfillment options for content delivery.
The system shall provide the capability to configure the tangible content
delivery options.
The system shall provide the capability to enter multiple fulfillment
destinations.
The system shall allow users to attach distribution list files to a job.
The system shall compile fulfillment destination into multiple standardized
formats.
The system shall be capable of extracting fulfillment destinations from
attached distribution list files.
The system shall provide the capability for users to store fulfillment
destinations in their user profile.
The system shall be able to provide distribution list information to authorized
users.
The system shall provide the capability for authorized users to download
distribution list information.
The system shall provide the capability for Service Providers to download
distribution list information for jobs that have been awarded to them.
The system shall provide the capability for Content Originators to select ship,
delivery, mail, or pickup dates.
The system shall provide the capability for users to select zero or more mail
dates for each destination in an job.
The system shall provide the capability for users to select zero or more ship
The system shall provide the capability for users to select zero or more
delivery dates for each destination in an job.
The system shall provide the capability for users to select zero or more pickup
The system shall provide the capability for users to select shipping providers
from a configurable list.
The system shall have the capability to provide estimated shipping costs
based upon BPI.
The system shall have the capability to allow Content Originators and Service
Specialists to select the method for content fulfillment.
The system shall maintain Service Provider information.
Authorized users shall have the capability to access Service Provider
information.
The system shall provide the capability for users to create Service Provider
information.
The system shall provide the capability for authorized users to edit Service
Provider information.
The system shall provide the capability for authorized users to delete Service
Provider information.
Service Provider contact information shall include the company name.
The system shall allow users to submit feedback on Service Providers.
Service Provider contact information shall include the physical address.
Service Provider contact information shall include the mailing address.
Service Provider contact information shall include the shipping address.
R3; Must
R1C; Must
R3; Must
R3; Must
R1C; Must
R1C; Must
R1C; Must
R1C; Must
R1C; Must
R3; Must
R3; Must
R3; Must
R1C; Must
R1C; Must
R3; Must
R3; Must
R1C; Must
R3; Must
R1C; Must
R3; Must
R1C; Must
R1C; Must
R1C; Must
R1C; Must
R1C; Must
R3; Must
R3; Could
R1C; Must
R3; Must
R3; Must
R3; Must
R3; Must
R3; Must
R3; Must
R3; Could
R3; Must
R3; Must
R3; Must
70

FINAL
RD-2152
25.2.0-23.0-2.0-8
RD-2153
25.2.0-23.0-2.0-9
RD-2154
25.2.0-23.0-2.0-10
RD-2155
25.2.0-23.0-2.0-11
RD-2156
RD-2157
RD-2158
RD-2161
25.2.0-23.0-2.0-12
25.2.0-23.0-2.0-13
25.2.0-23.0-2.0-14
25.2.0-23.0-4
RD-2162
25.2.0-23.0-4.0-1
RD-2163
25.2.0-23.0-4.0-2
RD-2164
25.2.0-23.0-4.0-3
RD-2165
25.2.0-23.0-5
RD-2166
25.2.0-23.0-5.0-1
RD-2167
25.2.0-23.0-5.0-2
RD-2169
25.2.0-23.0-7
RD-2170
25.2.0-23.0-7.0-1
RD-2171
25.2.0-23.0-7.0-2
RD-2172
RD-2173
25.2.0-23.0-7.0-3
25.2.0-23.0-7.03.0-1
25.2.0-23.0-7.03.0-2
25.2.0-23.0-7.03.0-3
25.2.0-23.0-7.0-4
25.2.0-23.0-7.04.0-1
25.2.0-23.0-7.04.0-2
25.2.0-23.0-7.04.0-3
25.2.0-23.0-7.0-5
25.2.0-23.0-7.05.0-1
25.2.0-23.0-7.05.0-2
25.2.0-23.0-7.05.0-3
25.2.0-23.0-7.05.0-4
25.2.0-23.0-7.05.0-5
25.2.0-23.0-7.05.0-6
25.2.0-23.0-7.05.0-7
25.2.0-23.0-7.05.0-8
25.2.0-23.0-7.05.0-9
RD-2174
RD-2175
RD-2176
RD-2177
RD-2178
RD-2179
RD-2180
RD-2181
RD-2182
RD-2183
RD-2184
RD-2185
RD-2186
RD-2187
RD-2188
RD-2189
Service Provider contact information shall include the names of zero or more
contact personnel.
Service Provider contact information shall include zero or more phone
numbers.
Service Provider contact information shall include zero or more cell phone
numbers.
Service Provider contact information shall include zero or more e-mail
address.
Service Provider contact information shall include zero or more fax numbers.
Service Provider contact information shall include the state code.
Service Provider contact information shall include the contractor code.
The system shall allow authorized users to manage a list of equipment
categories.
Service Providers shall be able to specify the equipment categories they meet
from a predefined list.
Service Providers shall be able to manage their equipment categories from a
predefined list.
The system shall provide a text field for Service Providers to specify specific
equipment they utilize.
Service Providers shall be able to specify products and services that they are
capable of providing from a configurable list.
The system shall allow authorized users to manage a configurable list of
products and services.
The system shall allow Service Providers to input customized capabilities not
included on the configurable list in a note field.
The system shall maintain Service Provider performance information
comprised of quality history, quality level, compliance history, and notices.
The system shall allow authorized users to manage Service Provider
performance information.
Quality levels shall be assigned by authorized GPO personnel in accordance
with GPO Publication 310.1.
Service Provider information shall include quality history data.
Quality history data shall include the number of jobs completed at given
quality levels.
Quality history data shall include the number of jobs inspected at given quality
level
Quality history data shall include the number of jobs rejected at given quality
levels
Service Provider information shall include compliance history data.
Compliance history shall include the number of jobs completed.
R3; Must
R3; Must
R3; Must
Compliance history shall include the number of jobs completed late
R3; Must
Compliance history shall include the percentage of job completed late.
R3; Must
Service Provider information shall include notices.

Notices received shall include the number of cure notices.
R3; Must
R3; Must
Notices received shall include the number of show-cause notices.
R3; Must
Notices received shall include the number of shipped short letters.
R3; Must
Notices received shall include the number of do not condone letters.
R3; Must
Notices received shall include the number of terminations for default

(program).
Notices received shall include the number of terminations for default (jobs).
R3; Must
R3; Must
Notices received shall include the number of erroneous information letters.
R3; Must
Notices received shall include the number of non-responsible quality history

letters.
Notices received shall include the number of non-responsible performance
letters.
R3; Must
R3; Must
R3; Must
R3; Must
R3; Must
R3; Must
R3; Must
R3; Must
R3; Must
R3; Must
R3; Must
R3; Must
R3; Must
R3; Must
R3; Must
R3; Must
R3; Must
R3; Must
R3; Must
R3; Must
R3; Must
R3; Must
71

FINAL
RD-2190
RD-2192
RD-2193
25.2.0-23.0-7.05.0-10
25.2.0-23.0-7.05.0-11
25.2.0-23.0-7.0-6
25.2.0-24
RD-2194
25.2.0-25
RD-2196
RD-2197
RD-2198
RD-2199
RD-2200
RD-2201
25.2.0-26
25.2.0-26.0-1
25.2.0-27
25.2.0-27.0-1
25.2.0-27.0-2
25.2.0-27.0-3
RD-2202
RD-2203
RD-2204
RD-2205
25.2.0-27.0-4
25.2.0-27.0-4.0-1
25.2.0-27.0-4.0-2
25.2.0-27.0-4.0-3
RD-2206
RD-2207
25.2.0-27.0-5
25.2.0-28
RD-2209
25.2.0-30
Service Provider information shall include note text field.

The system shall provide the capability to search Service Provider
information.
The system shall generate a list of Service Providers in response to a user
search request.
The system shall allow authorized users to generate solicitations.
The system shall distribute solicitations.
The system shall accept bids from Service Providers for jobs.
The system shall allow authorized users to submit bid information.
The system shall accept bids with zero to many line items.
The system shall be able to accept bids in the form of a quantity based upon a
fixed price (e.g., Service Provider submits quantity of a bid for a fixed dollar
amount, How many copies can you print for $100).
The system shall electronically stamp bids with the time it was received.
The system shall electronically stamp bids with the date it was received.
The system shall electronically stamp bids with user profile information.
The system shall allow authorized users to enter electronic stamp information
when tangible bids are received.
The system shall allow authorized users to electronically post bid results.
The system shall allow Service Specialists and Content Originators to award
jobs to Service Providers.
The system shall allow authorized users to request contract modifications.
RD-2210
25.2.0-31
The system shall allow authorized users to approve contract modifications.
RD-2211
25.2.0-31.0-1
The system shall allow authorized users to manage contract modifications.
RD-2213
25.2.0-33
The system shall provide the capability for users to request re-orders.
RD-2214
25.3
RD-2191
Notices received shall include the number of non-responsible other letters.
R3; Must
Notices received shall include the number of exception clause letters
R3; Must
R3; Must
R3; Must
R3; Must
R3; Must
R3; Must
R3; Must
R3; Must
R3; Must
R3; Must
R3; Must
R3; Must
R3; Must
R3; Must
R3; Must
R3; Must
R2; Should
/ R3; Must
R2; Should
/ R3; Must
R2; Should
/ R3; Must
R3; Must
25.3 Content Originator Ordering Job

Tracking
RD-2215
25.3.0-1
RD-2216
RD-2217
RD-2218
RD-2219
RD-2220
RD-2221
RD-2222
RD-2223
RD-2224
25.3.0-1.0-1
25.3.0-1.0-2
25.3.0-1.0-3
25.3.0-1.0-4
25.3.0-1.0-5
25.3.0-1.0-6
25.3.0-1.0-7
25.3.0-1.0-8
25.3.0-1.0-9
RD-2225
RD-2226
RD-2227
RD-2228
RD-2229
RD-2230
RD-2231
RD-2232
RD-2233
RD-2235
RD-2236
RD-2239
RD-2240
25.3.0-1.0-10
25.3.0-1.0-11
25.3.0-1.0-12
25.3.0-1.0-13
25.3.0-1.0-14
25.3.0-1.0-15
25.3.0-1.0-16
25.3.0-1.0-17
25.3.0-1.0-18
25.3.0-1.0-20
25.3.0-1.0-21
25.3.0-1.0-22
25.3.0-2
The system shall have the capability for a user to inform the system that they
have completed an activity.
Activities include that the job was made available to Service Provider.
Activities include that the job was received by Service Provider.
Activities include that the proofs were sent to Content Originator
Activities include that the proofs were received by Content Originator
Activities include that the proofs were approved.
Activities include that the proofs were approved with author's alterations.
Activities include that the proofs were approved with Service Provider's errors.
Activities include that new proofs were requested due to author's alterations.
Activities include that new proofs were requested due to Service Provider's
errors.
Activities include that proofs were sent to Service Provider.
Activities include that proofs were received by Service Provider.
Activities include that changes were made by Content Originator.
Activities include that changes were made by Service Provider.
Activities include that the job is complete.
Activities include that the job is delivered to each individual destination.
Activities include job shipped to all destinations.
Activities include job delivered to all destinations.
Activities include job delivery receipts are available.
Activities include Job ID referenced,
Activities include approved for publication.
The system shall provide a means to add notes to each job.
The system shall provide the capability to automatically request job status
information from users.
Release 1;
Must
R3; Must
R3; Must
R3; Must
R3; Must
R3; Must
R3; Must
R3; Must
R3; Must
R3; Must
R3; Must
R3; Must
R3; Must
R3; Must
R3; Must
R3; Must
R3; Must
R3; Must
R3; Must
R3; Must
R3; Must
R3; Must
R3; Must
72

FINAL
RD-2242
25.3.0-2.0-2
RD-2243
25.3.0-3
RD-2244
25.3.0-3.0-1
RD-2245
RD-2246
RD-2247
RD-2248
25.3.0-3.0-2
25.3.0-3.0-3
25.3.0-3.0-4
25.3.0-4
RD-2249
25.3.0-4.0-1
RD-2250
25.3.0-4.0-2
RD-2251
RD-2252
25.3.0-4.0-3
25.3.0-4.0-4
RD-2253
25.3.0-4.0-5
RD-2254
25.3.0-4.0-6
RD-2256
25.3.0-5.0-1
RD-2257
25.3.0-5.0-2
RD-2258
RD-2259
25.3.0-6
25.3.0-7
RD-2260
25.3.0-7.0-1
RD-2261
25.3.0-7.0-2
RD-2262
25.3.0-7.0-3
RD-2263
25.3.0-7.0-4
RD-2237
25.3.0-8
RD-2238
25.3.0-9
RD-2264
25.4
The system shall have the capability for authorized users to request
automated notifications of job activities.
The system shall allow Service Specialists to generate notifications to Service
Providers and Content Originators.
The system shall allow Service Specialists to distribute notification to Service
Providers and Content Originators.
Notifications include show cause notices.
Notifications include cure notices.
Notifications include GPO Form 907.
The system shall have the capability to provide shipping notification to
authorized users.
The system shall have the capability to provide delivery notification to
authorized users.
Notification of delivery shall include tracking numbers from the Service
Provider.
Notification of delivery shall include signed delivery receipts.
The system shall have the capability to upload digitized signed delivery
receipts.
Notification of delivery shall include confirmation of delivery from agency
recipients.
The system shall have the capability to provide users with options in response
to undelivered content (e.g., resubmit content, cancel fulfillment).
The system shall have the capability to receive and store product delivery
tracking numbers (e.g., Fed-Ex Tracking Number) from Service Providers.
The system shall have the capability to receive confirmation of delivery from
the agency or end user.
The system shall have the capability to support Job Definition Format (JDF).
The system shall provide the capability for BPI to be rendered on the GPO
forms.
Standard Form 1 (SF-1).
Form 952.
Form 2511.
Form 3868.
The system shall allow the capability for authorized users to attach files and a
description of the files to a job.
The system shall have the capability to apply a timestamp to a job upon
submission.
R3; Must
R3; Must
R3; Must
R3; Must
R3; Must
R3; Must
R3; Must
R3; Must
R3; Must
R3; Must
R3; Must
R3; Must
R2; Should
/ R3; Must
R2; Should
/ R3; Must
R2; Should
/ R3; Must
R3; Could
R1C; Must
R1C; Must
R1C; Must
R1C; Must
R1C; Must
R1C; Must
R1C; Must
25.4 Requirements for Access Content

Processing
RD-2265
25.4.1
25.4.1 Access Core Capabilities

RD-2266
RD-2267
RD-2268
25.4.1.0-1
25.4.1.0-2
25.4.1.0-3
RD-2269
25.4.1.0-4
RD-2270
25.4.1.0-5
RD-2271
25.4.1.0-6
RD-2272
25.4.1.0-7
RD-2273
25.4.1.0-8
The system shall provide open and interoperable access to content.

The system shall provide open and interoperable access to metadata.
The system shall provide access to content at the minimum level of granularity
that is specified in the Fdsys unique ID requirements.
The system shall provide the capability for users to use persistent names to
access content.
The system shall provide the capability for users to access content that has
been published in non-English languages and non-Roman character sets.
The system shall provide the capability for users to access information about
content relationships.
relationships between content packages.
relationships between digital objects.
R1B; Must
R1B; Must
R1B; Must
R1C; Must
R3; Must
R1B; Must
R1B; Must
R1B; Must
73

FINAL
RD-2274
25.4.1.0-9
RD-2275
RD-2276
25.4.1.0-10
25.4.1.0-11
RD-2277
25.4.1.0-11.0-1
RD-2278
25.4.1.0-11.0-2
RD-2279
25.4.1.0-11.0-2.01
25.4.1.0-11.0-2.02
25.4.1.0-11.0-2.03
25.4.1.0-11.0-2.04
25.4.1.0-11.0-2.05
25.4.1.0-11.0-2.06
25.4.1.0-11.0-2.07
25.4.1.0-11.0-2.08
25.4.1.0-11.0-2.09
25.4.1.0-11.0-2.010
25.4.1.0-11.0-2.011
25.4.1.0-11.0-2.012
25.4.1.0-11.0-2.013
25.4.1.0-11.0-2.014
25.4.1.0-11.0-2.015
25.4.1.0-11.0-2.016
25.4.1.0-11.0-2.017
25.4.1.0-11.0-2.018
25.4.1.0-11.0-3
RD-2280
RD-2281
RD-2282
RD-2283
RD-2284
RD-2285
RD-2286
RD-2287
RD-2288
RD-2289
RD-2290
RD-2291
RD-2292
RD-2293
RD-2294
RD-2295
RD-2296
RD-2297
RD-2298
RD-2299
RD-2300
RD-2301
RD-2302
25.4.1.0-11.0-3.01
25.4.1.0-11.0-3.02
25.4.1.0-11.0-3.03
25.4.1.0-11.0-3.04
RD-2303
25.4.1.0-11.0-3.05
25.4.1.0-11.0-4
RD-2304
25.4.1.0-11.0-4.0-
relationships between digital objects and content packages.
The system shall enforce the continuity of content in context.
The system shall provide the capability to access content based on
relationships between versions of a Congressional bill.
The system shall provide notification to users about all bill versions available
for access.
relationships between publications that are used in the Federal legislative
process.
The system shall provide notification to users about related legislative
publications.
The system shall provide the capability to access public laws based on public
law citations in the House Calendar.
law citations in the Senate Calendar of Business.
The system shall provide the capability to access Congressional bills based
on bill citations in the House Calendar.
on bill citations in the Senate Calendar of Business.
The system shall provide the capability to access bill versions based on
entries in the history of bills.
The system shall provide the capability to access Congressional Record
pages based on Congressional Record citations in the history of bills.
on bill citations in the Congressional Record.
law citations in the history of bills.
The system shall provide the capability to access history of bill entries based
on bill citations in public laws.
The system shall provide the capability to access Congressional Record
entries based on Congressional Record citations in public laws.
The system shall provide the capability to access U.S. Code entries based on
U.S. Code citations in public laws.
law citations in the U.S. Code.
The system shall provide the capability to access Congressional Reports
based on Congressional Report citations in Congressional Documents.
The system shall provide to capability to access Congressional Reports from
related Congressional bills.
The system shall provide access to Congressional hearings related to
Congressional bills.
The system shall provide the capability access entities referenced in the
Congressional Record Index from the Congressional Record Index.
The system shall provide the capability to access Statutes at Large entries
based on Statutes at Large citations in public laws.
relationships between publications that are used in the Federal regulatory
process.
The system shall provide notification to users about related regulatory
publications.
The system shall provide the capability to access Code of Federal Regulation
sections based on Code of Federal Regulation citation in the Federal
Register.
The system shall provide the capability to access Federal Register entries
based on Federal Register citations in the List of CFR Sections Affected.
sections based on Code of Federal Regulation citations in the List of CFR
Sections Affected.
sections based on Code of Federal Regulation citations in the Unified Agenda.
relationships between Supreme Court publications that are part of the opinion
process.
The system shall provide notification to users about related Supreme Court
R1B; Must
R1B; Must
R1C; Must
R1C; Must
R1C; Must
R1C; Must
R1C; Must
R1C; Must
R1C; Must
R1C; Must
R1C; Must
R1C; Must
R1C; Must
R1C; Must
R1C; Must
R1C; Must
R1C; Must
R1C; Must
R1C; Must
R1C; Must
R1C; Must
R1C; Must
R1C; Must
R1C; Must
R1C; Must
R1C; Must
R1C; Must
R1C; Must
R1C; Must
R1C; Must
R1C; Must
74

FINAL
RD-2310
1
25.4.1.0-11.0-4.02
25.4.1.0-11.0-4.03
25.4.1.0-11.0-4.04
25.4.1.0-11.0-4.05
25.4.1.0-11.0-4.06
25.4.1.0-12
RD-2311
25.4.1.0-13
RD-2312
25.4.1.0-13.0-1
RD-2313
25.4.1.0-13.0-2
RD-2314
25.4.1.0-13.0-3
RD-2315
25.4.1.0-13.0-4
RD-2316
25.4.1.0-13.0-5
RD-2317
25.4.1.0-13.0-6
RD-2318
25.4.1.0-13.0-7
RD-2319
25.4.2
RD-2320
25.4.2.0-1
RD-2321
RD-2322
25.4.2.0-2
25.4.2.0-3
RD-2323
25.4.2.0-4
RD-2324
25.4.2.0-5
RD-2325
25.4.2.0-6
RD-2326
25.4.2.0-7
RD-2327
25.4.2.0-8
RD-2328
25.4.2.0-9
RD-2329
25.4.2.0-10
RD-2330
25.4.2.0-10.0-1
RD-2331
25.4.2.0-11
RD-2332
25.4.2.0-11.0-1
RD-2305
RD-2306
RD-2307
RD-2308
RD-2309
publications that are part of the opinion process.

The system shall provide notification to users that informs them of the current
version of an opinion.
The system shall provide notification to users that informs them of
uperceded versions of an opinion.
The system shall provide notification to users when a bench opinion has been
uperceded by a slip opinion.
The system shall provide notification to users when a slip opinion has been
uperceded by a preliminary print of the U.S. Reports.
The system shall provide notification to users when a preliminary print of the
U.S. Reports has been uperceded by the Bound Volume of U.S. Reports. _
The system shall provide the capability to use GPOs ILS to access metadata
repositories not resident within the system.
The system shall provide the capability to provide access to select external
repositories with which GPO has formal partnership agreements including the
following:
Census 200 data (U.S. Census Bureau/Case Western Reserve University):
Established a Web site specifically for depository library access to Census
2000 data issued by the Census Bureau in comma-delimited ASCII format.
A partnership between GPO and the Indiana University, Bloomington Libraries
on behalf of the Committee on Institutional Cooperation, making publications
that were distributed to Federal Depository Libraries on floppy disk available
over the Internet.
CyberCemetery (University of North Texas): Provide permanent online access
to electronic publications of selected federal Government agencies which
have ceased operation.
FRASER (Federal Reserve Bank of St. Louis): Provides for public access to
content in the Federal Reserve Archival System for Economic Research
(FRASER) service.
National Library of Medicine: Provides permanent public access to Medline,
Medical Subject Headings, and NLM LocatorPlus.
National Renewable Energy Laboratory: Provides permanent public access to
NRELs laboratory and outreach publications.
The system shall provide the capability to provide access to additional select
external repositories with which GPO has formal partnership agreements.
R1C; Must
R1C; Must
R1C; Must
R1C; Must
R1C; Must
R2; Must
R1C; Must
R1C; Must
R1C; Must
R1C; Must
R1C; Must
R1C; Must
R1C; Must
R2; Must
25.4.2 Access to Content Packages

The system shall provide the capability for GPO to manage access to content
packages according to GPO business rules.
The system shall accept access rules for content packages.
The system shall provide the capability to limit access to content with redissemination restrictions as specified by authorized users.
The system shall provide the capability to limit access to content with limited
distribution as specified by authorized users.
The system shall provide the capability to limit access to Sensitive But
Unclassified (SBU) content as specified by authorized users.
The system shall provide the capability to limit access to copyrighted content
as specified by authorized users.
The system shall provide the capability to limit access to content that is out of
scope for GPO's dissemination programs.
The system shall provide the capability to limit access to content that has not
been approved by authorized users for public release.
The system shall provide the capability to limit access to embargoed content
until the appropriate release date and time as specified by authorized users.
The system shall provide the capability to limit access to content based on
criteria specified by the Content Originator.
The system shall provide the capability to limit access to content based on
criteria specified by authorized users.
The system shall provide access to content currently available on GPO
Access.
The system shall provide the capability for users to access select publications
enumerated in RD-2596 (list of GPO Access applications) at a level of
R2; Must
R1C; Must
R1C; Must
R1C; Must
R1C; Must
R1C; Must
R1C; Must
R1C; Must
R1C; Must
R1C; Must
R1C; Must
R1C; Must
R1C; Must
75

FINAL
RD-2333
25.4.2.0-11.0-2
RD-2334
25.4.2.0-11.0-2.01
RD-2335
25.4.2.0-11.0-2.02
RD-2336
25.4.2.0-11.0-2.03
RD-2337
25.4.2.0-11.0-2.04
RD-2338
25.4.2.0-11.0-2.05
RD-2339
25.4.2.0-11.0-2.06
25.4.2.0-11.0-2.07
RD-2340
RD-2341
RD-2342
RD-2343
RD-2344
RD-2345
RD-2346
RD-2347
RD-2348
RD-2349
25.4.2.0-11.0-2.08
25.4.2.0-11.0-2.09
25.4.2.0-11.0-2.010
25.4.2.0-11.0-2.011
25.4.2.0-11.0-2.012
25.4.2.0-11.0-2.013
25.4.2.0-11.0-2.014
25.4.2.0-11.0-2.015
25.4.2.0-11.0-2.016
RD-2350
25.4.2.0-11.0-2.017
RD-2351
25.4.2.0-11.0-2.018
RD-2352
25.4.2.0-11.0-2.019
25.4.2.0-11.0-2.020
25.4.2.0-11.0-2.021
RD-2353
RD-2354
RD-2356
25.4.2.0-11.0-2.023
RD-2357
RD-2358
25.4.2.0-11.0-2.024
25.4.2.0-12
RD-2359
25.4.2.0-13
granularity that is less than a publication.

The system shall provide the capability to create persistent links to renditions
of publications listed in RD-2596 (list of GPO Access applications).
of the Code of Federal Regulations based on natural content boundaries at a
level of granularity that is less than a publication.
of the Federal Register based on natural content boundaries at a level of
of the Congressional Record based on natural content boundaries at a level of
of the Congressional Bills based on natural content boundaries at a level of
of the United States Code based on natural content boundaries at a level of
The system shall provide the capability to create predictable links to renditions
of publications listed in RD-2596 (list of GPO Access applications).
The system shall provide the capability for internal linking of publications listed
in RD-2596 (list of GPO Access applications) at all available levels of
granularity.
The system shall provide the capability to link Congressional bill citations in
digital objects to appropriate versions of Congressional bill renditions.
The system shall provide the capability to link public law citations in digital
objects to appropriate versions of public law renditions.
The system shall provide the capability to link United States Code citations in
digital objects to appropriate versions of United States Code renditions.
The system shall provide the capability to link Statutes at Large citations in
digital objects to appropriate versions of Statutes at Large renditions.
The system shall provide the capability to link Code of Federal Regulations
citations in digital objects to appropriate versions of Code of Federal
Regulations renditions.
The system shall provide the capability to link Congressional Record citations
in digital objects to appropriate versions of Congressional Record renditions.
The system shall provide the capability to link Congressional Record page
number citations in digital objects to appropriate versions of Congressional
Record pages in renditions.
The system shall provide the capability to link Federal Register citations in
digital objects to appropriate versions of Federal Register renditions.
The system shall provide the capability to link Federal Register page number
citations in digital objects to appropriate versions of Federal Register pages in
renditions.
The system shall provide the capability to link articles listed in the Federal
Register Table of Contents to articles in the appropriate versions of Federal
Register renditions.
The system shall provide the capability to link Bound Congressional Record
citations in digital objects to appropriate versions of Bound Congressional
Record renditions.
The system shall provide the capability to link Congressional Hearing citations
in digital objects to appropriate versions of Congressional Hearing renditions.
The system shall provide the capability to link Congressional Report citations
in digital objects to appropriate versions of Congressional Report renditions.
The system shall provide the capability to link Congressional Document
citations in digital objects to appropriate versions of Congressional Document
renditions.
The system shall provide the capability to link Congressional Committee Print
citations in digital objects to appropriate versions of Congressional Committee
Print renditions.
The system shall provide the capability to manage links as managed objects.
The system shall provide the capability to notify users of limitations on access
to content.
The system shall provide the capability to provide customized access to
R1C; Must
R1C; Must
R1C; Must
R1C; Must
R1C; Must
R1C; Must
R1C; Must
R1C; Must
R1C; Must
R1C; Must
R1C; Must
R1C; Must
R1C; Must
R1C; Must
R1C; Must
R1C; Must
R1C; Must
R1C; Must
R1C; Must
R1C; Must
R1C; Must
R1C; Must
R1C; Must
R1C; Must
R1C; Must
R1C;
76

FINAL
content packages.
RD-2360
25.4.2.0-14
RD-2361
25.4.2.0-15
RD-2362
25.4.2.0-16
RD-2363
25.4.3
RD-2364
25.4.3.0-1
RD-2365
25.4.3.0-2
RD-2366
25.4.3.0-2.0-1
RD-2367
25.4.3.0-2.0-2
RD-2368
25.4.3.0-3
RD-2369
25.4.3.0-3.0-1
RD-2370
25.4.3.0-3.0-2
RD-2371
25.4.3.0-3.0-2.0-1
RD-2372
25.4.3.0-3.0-2.01.0-1
25.4.3.0-3.0-2.01.0-2
The system shall provide the capability to provide personalized access to

content packages.
The system shall provide the capability for users to access in scope final
published versions of ACPs.
The system shall provide the capability for authorized users to access final
approved versions of ACPs that are not in scope for GPO's dissemination
programs.
Should /
R2; Must
R1C; Could
/ R2; Must
R1B; Could
/ R1C; Must
R1C; Must
25.4.3 Access to the System
RD-2373
RD-2374
RD-2375
25.4.3.0-3.0-2.01.0-3
25.4.3.0-3.0-3
RD-2376
25.4.3.0-3.0-4
RD-2379
25.4.4
The system shall have the capability to provide access to system functions by
user class.
The system shall provide access to public End Users that does not require
them to log-in or register with the system.
them to log-in to the system.
them to register with the system.
The system shall provide the capability for authorized users to access WIP
storage.
The system shall have the capability to allow authorized users to authorize
access to content in WIP.
The system shall provide check in and check out capabilities for content in
WIP.
The system shall provide check out of work in progress content
The system shall not allow other users to modify content when one user has
checked it out
The system shall provide notification when content has been checked out for
longer than the allowed period defined by the workflow for the work in
progress
The system shall allow authorized users to release locks on content
The system shall link all versions of work in progress content
The system shall allow users to check in content.
R1C; Must
R1B; Must
R1B; Must
R1B; Must
R1B; Must
R1B; Must
R1B; Could
/ R1C; Must
R1B; Could
/ R1C; Must
R1B; Could
/ R1C; Must
R1B; Could
/ R1C; Must
R1B; Could
/ R1C; Must
R1B; Could
/ R1C; Must
R1B; Could
/ R1C; Must
25.4.4 Access User Registration

RD-2380
RD-2381
25.4.4.0-1
25.4.4.0-2
RD-2382
25.4.4.0-3
RD-2383
25.4.4.0-4
RD-2384
25.4.4.0-4.0-1
RD-2385
25.4.4.0-4.0-2
RD-2386
25.4.4.0-5
RD-2387
25.4.4.0-6
RD-2388
25.4.4.0-7
RD-2389
25.4.4.0-8
RD-2390
25.4.4.0-8.0-1
The system shall provide the capability for users to register with the system.
The system shall provide the capability to establish a user account for each
registered user.
The system shall provide the capability to create user records for registered
users.
The system shall provide the capability to store and manage a number of user
records that is only limited by available storage.
The system shall have the capability to store an unlimited number of user
records without software re-design.
The system shall have the capability to manage an unlimited number of user
records without software redesign.
The system shall provide the capability for authorized users to access user
records.
The system shall provide the capability for authorized users to set required
fields in user records.
The system shall provide the capability to record information submitted by
users during registration with system.
The system shall provide the capability for GPO to customize what information
is collected during user registration.
The system shall have the capability to collect name from the user during
R1B; Must
R1B; Must
R1B; Must
R1B; Must
R1B; Must
R1B; Must
R1B; Must
R1C; Must
R1B; Must
R2; Must
R1C; Must
77

FINAL
registration (e.g., honorific title, first name, last name, job title).
The system shall have the capability to collect contact information from the
user during registration (e.g., address, city, state, zip code, country, phone
number, fax number, email address).
The system shall provide the capability to collect information identifying the
individual as a member of a user class during registration (e.g., agency,
department, office, library, depository number, company, contractor code).
Users may be members of multiple user classes simultaneously.
The system shall associate registered users with at least one user class.
The system shall provide the capability to collect role-based information from
the user during registration.
The system shall provide the capability to collect proof of identity information
from the user during registration.
The system shall provide the capability to collect authority to publish
information from the user during registration.
The system shall provide the capability to perform records management
functions on user records.
RD-2391
25.4.4.0-8.0-2
RD-2393
25.4.4.0-8.0-4
RD-2394
RD-2395
RD-2396
25.4.4.0-8.0-4.0-1
25.4.4.0-8.0-4.0-2
25.4.4.0-9
RD-2397
25.4.4.0-10
RD-2398
25.4.4.0-11
RD-2399
25.4.4.0-12
RD-2400
25.4.5
RD-2401
25.4.5.0-1
The system shall provide the capability for authorized users to manage the
following user preferences:
RD-2402
RD-2403
RD-2404
RD-2405
RD-2406
RD-2407
RD-2408
RD-2409
25.4.5.0-1.0-1
25.4.5.0-1.0-2
25.4.5.0-1.0-3
25.4.5.0-1.0-4
25.4.5.0-1.0-5
25.4.5.0-1.0-6
25.4.5.0-1.0-7
25.4.5.0-1.0-8
RD-2410
25.4.5.0-2
Preferred contact methods

Delivery options
User interfaces
Alert services
Help features
Frequently accessed tools
Search preferences
The system shall provide the capability for authorized users to manage future
user preferences.
The system shall provide the capability for authorized users to manage other
users preferences.
RD-2411
25.4.5.0-3
The system shall provide the capability for GPO to establish and manage
default user preferences.
RD-2412
25.4.5.0-4
The system shall have the capability to provide recommendations for content
and services based on preferences and queries of users and groups of similar
users.
RD-2415
25.4.6
R1C; Must
R2; Must
R1B; Must
R1C; Must
R1C; Must
R2; Must
R2; Must
R1C; Must
25.4.5 Access User Preferences

R1C;
Should /
R2; Must
R2; Must
R2; Must
R2; Must
R2; Must
R2; Must
R2; Must
R2; Must
R1C;
Should /
R2; Must
R1C;
Should /
R2; Must
R1C; Could
/ R2; Must
25.4.6 Access Processing

RD-2416
RD-2417
25.4.6.0-1
25.4.6.0-1.0-1
RD-2418
25.4.6.0-1.0-2
RD-2419
RD-2422
25.4.6.0-2
25.4.6.0-5
RD-2423
RD-2424
RD-2425
25.4.6.0-5.0-1
25.4.6.0-5.0-2
25.4.6.0-6
RD-2426
25.4.6.0-6.0-1
RD-2427
25.4.6.0-6.0-2
The system shall provide the capability to process and manage ACPs.
The system shall provide the capability to process and manage digital objects
that are used for access.
The system shall provide the capability to manage metadata that are used for
access.
The system shall provide the capability to create access derivatives.
The system shall provide the capability for access processing to request that
an ACP be modified or created from an AIP.
The system shall provide the capability for an ACP to be created from an AIP.
The system shall provide the capability for an existing ACP to be modified.
The system shall provide the capability for access processing to provide
content and/or metadata and/or business process information to delivery
processing for the purpose of fulfilling an End User request or Content
Originator order.
The system shall provide content to delivery processing for the purpose of
fulfilling an End User request.
The system shall provide metadata to delivery processing for the purpose of
fulfilling an End User request.
R1C; Must
R1C; Must
R1C; Must
R1C; Must
R1C; Must
R1C; Must
R1C; Must
R2; Must
R1C; Must
R1C; Must
78

FINAL
RD-2428
25.4.6.0-6.0-3
RD-2429
25.4.6.0-6.0-4
RD-2430
25.4.6.0-6.0-5
RD-2431
25.4.6.0-6.0-6
RD-2432
25.4.6.0-6.0-7
RD-2433
25.4.6.0-6.0-8
RD-2434
25.4.6.0-7
RD-2435
25.4.6.0-7.0-1
RD-2436
25.4.6.0-7.0-2
RD-2437
25.4.6.0-8
RD-2438
25.4.6.0-8.0-1
RD-2439
25.4.6.0-8.0-2
RD-2440
RD-2441
26
26.1
The system shall provide business process information to delivery processing

for the purpose of fulfilling an End User request.
The system shall provide content, metadata and business process information
in any combination to delivery processing for the purpose of fulfilling an End
User request.
The system shall provide content to delivery processing for the purpose of
fulfilling an Content Originator order.
The system shall provide metadata to delivery processing for the purpose of
fulfilling an Content Originator order.
The system shall provide business process information to delivery processing
for the purpose of fulfilling a Content Originator order.
The system shall provide content, metadata and business process information
in any combination to delivery processing for the purpose of fulfilling an
Content Originator order.
functions on ACPs.
Records management functions shall comply with GPO and Federal records
management policies.
Records management functions shall be performed according to records
management schedules for content and metadata within the system.
The system shall provide the capability to identify and manage relationships
between digital objects, between content packages, and between digital
objects and content packages.
between digital objects based on changes in content that occur as a result of
the legislative process.
between digital objects based on changes in content that occur as a result of
the regulatory process.
R2; Must
R2; Must
R2; Must
R2; Must
R2; Must
R2; Must
R2; Must
R2; Must
R2; Must
R2; Must
R2; Must x
R2; Must
26 Requirements for Accessibility

26.1 Accessibility Core Capabilities
RD-2442
26.1.0-1
RD-2443
26.1.0-1.0-1
RD-2444
26.1.0-1.0-2
RD-2445
26.1.0-2
RD-2446
26.1.0-3
RD-2447
26.1.0-4
RD-2448
RD-2449
26.1.0-5
26.1.0-6
RD-2450
26.1.0-7
RD-2451
26.2
The system shall provide the capability to assess content for compliance with
Section 508 technical standards.
The system shall provide the capability to assess all content for compliance
with Section 508 technical standards.
The system shall provide the capability to assess content available in R1C for
compliance with Section 508 technical standards.
The system shall provide the capability to create content that is compliant with
The system shall provide the capability to validate content for compliance with
The system shall accept accessibility requirements and implementation
guidance from Content Originators.
The system shall provide Section 508 compliant access to the system.
In order to achieve compliance with Section 508 technical standards,
established best practices shall be followed.
The system shall create content that contains well formed code which
conforms to World Wide Web Consortium (W3C) Guidelines.
R2; Must
R2; Must
R1C; Must
R2; Must
R2; Must
R2; Must
R1C; Must
R2; Could
R2; Must
26.2 Accessibility Section 508

Technical Standards
RD-2452
26.2.0-1
RD-2453
26.2.0-1.0-1
Fdsys software applications and operating systems shall be Section 508

compliant according to 36 CFR Part 1194.21.
When software is designed to run on a system that has a keyboard, product
functions shall be executable from a keyboard where the function itself or the
result of performing a function can be discerned textually.
R2; Should
R2; Should
79

FINAL
RD-2454
26.2.0-1.0-2
RD-2455
26.2.0-1.0-3
RD-2456
26.2.0-1.0-3.0-1
RD-2457
26.2.0-1.0-4
RD-2458
26.2.0-1.0-5
RD-2459
26.2.0-1.0-6
RD-2460
26.2.0-1.0-7
RD-2461
26.2.0-1.0-8
RD-2462
26.2.0-1.0-9
RD-2463
26.2.0-1.0-10
RD-2464
26.2.0-1.0-11
RD-2465
26.2.0-1.0-12
RD-2466
26.2.0-2
RD-2467
26.2.0-2.0-1
RD-2468
26.2.0-2.0-2
RD-2469
26.2.0-2.0-3
RD-2470
26.2.0-2.0-4
RD-2471
26.2.0-2.0-5
RD-2472
26.2.0-2.0-6
RD-2473
RD-2474
26.2.0-2.0-7
26.2.0-2.0-8
RD-2475
26.2.0-2.0-9
RD-2476
26.2.0-2.0-10
RD-2477
26.2.0-2.0-11
RD-2478
26.2.0-2.0-12
Applications shall not disrupt or disable activated features of other products

that are identified as accessibility features, where those features are
developed and documented according to industry standards. Applications also
shall not disrupt or disable activated features of any operating system that are
identified as accessibility features where the application programming
interface for those accessibility features has been documented by the
manufacturer of the operating system and is available to the product
developer.
An on-screen indication of the current focus shall be provided that moves
among interactive interface elements as the input focus changes.
The focus shall be programmatically exposed so that assistive technology can
track focus and focus changes.
Sufficient information about a user interface element including the identity,
operation and state of the element shall be available to assistive technology.
When an image represents a program element, the information conveyed by
the image shall also be available in text.
When images are used to identify controls, status indicators, or other
programmatic elements, the meaning assigned to those images shall be
consistent throughout an applications performance.
Textual information shall be provided through operating system functions for
displaying text. The minimum information that shall be made available is text
content, text input caret location, and text attributes.
Applications shall not override user selected contrast and color selections and
other individual display attributes.
When animation is displayed, the information shall be displayable in at least
one non-animated presentation mode at the option of the user.
Color coding shall not be used as the only means of conveying information,
indicating an action, prompting a response, or distinguishing a visual element.
When a product permits a user to adjust color and contrast settings, a variety
of color selections capable of producing a range of contrast levels shall be
provided.
Software shall not use flashing or blinking text, objects, or other elements
having a flash or blink frequency greater than 2 Hz and lower than 55 Hz.
When electronic forms are used, the form shall allow people using assistive
technology to access the information, field elements, and functionality
required for completion and submission of the form, including all directions
and cues.
Fdsys Web-based intranet and internet information and applications shall be
Section 508 compliant according to 36 CFR Part 1194.22.
A text equivalent for every non-text element shall be provided (e.g., via alt,
longdesc, or in element content).
Equivalent alternatives for any multimedia presentation shall be synchronized
with the presentation.
Web pages shall be designed so that all information conveyed with color is
also available without color, for example from context or markup.
Documents shall be organized so they are readable without requiring an
associated style sheet.
Redundant text links shall be provided for each active region of a server-side
image map.
Client-side image maps shall be provided instead of server-side image maps
except where the regions cannot be defined with an available geometric
shape.
Row and column headers shall be identified for data tables.
Markup shall be used to associate data cells and header cells for data tables
that have two or more logical levels of row or column headers.
Frames shall be titled with text that facilitates frame identification and
navigation.
Pages shall be designed to avoid causing the screen to flicker with a
frequency greater than 2 Hz and lower than 55 Hz.
A text-only page, with equivalent information or functionality, shall be provided
to make a web site comply with the provisions of this part, when compliance
cannot be accomplished in any other way. The content of the text-only page
shall be updated whenever the primary page changes
When pages utilize scripting languages to display content, or to create
interface elements, the information provided by the script shall be identified
R2; Should
R2; Should
R2; Should
R2; Should
R2; Should
R2; Should
R2; Should
R2; Should
R2; Should
R2; Should
R2; Should
R2; Should
R2; Should
R2; Should
R2; Should
R2; Should
R2; Should
R2; Should
R2; Should
R2; Should
R2; Should
R2; Should
R2; Should
R2; Should
R2; Should
80

FINAL
RD-2479
26.2.0-2.0-13
RD-2480
26.2.0-2.0-13.0-1
RD-2481
26.2.0-2.0-13.0-2
RD-2482
26.2.0-2.0-13.0-3
RD-2483
26.2.0-2.0-13.0-4
RD-2484
26.2.0-2.0-13.0-5
RD-2485
26.2.0-2.0-13.0-6
RD-2486
26.2.0-2.0-13.0-7
RD-2487
26.2.0-2.0-13.0-8
RD-2488
26.2.0-2.0-13.0-9
RD-2489
26.2.0-2.0-14
RD-2490
26.2.0-2.0-15
RD-2491
26.2.0-2.0-16
RD-2492
26.2.0-3
RD-2493
26.2.0-3.0-1
RD-2494
26.2.0-3.0-2
RD-2495
26.2.0-3.0-3
RD-2496
26.2.0-3.0-4
RD-2497
26.2.0-3.0-5
RD-2498
26.2.0-3.0-6
RD-2499
26.2.0-3.0-7
RD-2500
26.2.0-3.0-8
with functional text that can be read by assistive technology.

When a web page requires another application be present on the client
system to interpret page content the page shall provide a link to the required
tool that complies with 1194.21(a) through (l).
When a web page requires that an applet, plug-in or other application be
present on the client system to interpret page content, the page shall provide
a link to a plug-in or applet that complies with 1194.21(a).
a link to a plug-in or applet that complies with 1194.21(b).
a link to a plug-in or applet that complies with 1194.21I.
a link to a plug-in or applet that complies with 1194.21(d).
a link to a plug-in or applet that complies with 1194.21(e).
a link to a plug-in or applet that complies with 1194.21(f).
a link to a plug-in or applet that complies with 1194.21(g).
a link to a plug-in or applet that complies with 1194.21(h).
a link to a plug-in or applet that complies with 1194.21(i).
When electronic forms are designed to be completed on-line, the form shall
allow people using assistive technology to access the information, field
elements, and functionality required for completion and submission of the
form, including all directions and cues.
A method shall be provided that permits users to skip repetitive navigation
links.
When a timed response is required, the user shall be alerted and given
sufficient time to indicate more time is required.
Fdsys telecommunications products shall be Section 508 compliant according
to 36 CFR Part 1194.23.
Telecommunications products or systems which provide a function allowing
voice communication and which do not themselves provide a TTY functionality
shall provide a standard non-acoustic connection point for TTYs. Microphones
shall be capable of being turned on and off to allow the user to intermix
speech with TTY use.
Telecommunications products which include voice communication
functionality shall support all commonly used cross-manufacturer
nonproprietary standard TTY signal protocols.
Voice mail, auto-attendant, and interactive voice response
telecommunications systems shall be usable by TTY users with their TTYs.
Voice mail, messaging, auto-attendant, and interactive voice response
telecommunications systems that require a response from a user within a time
interval, shall give an alert when the time interval is about to run out, and shall
provide sufficient time for the user to indicate more time is required.
Where provided, caller identification and similar telecommunications functions
shall also be available for users of TTYs, and for users who cannot see
displays.
For transmitted voice signals, telecommunications products shall provide a
gain adjustable up to a minimum of 20 dB. For incremental volume control, at
least one intermediate step of 12 dB of gain shall be provided.
If the telecommunications product allows a user to adjust the receive volume,
a function shall be provided to automatically reset the volume to the default
level after every use.
Where a telecommunications product delivers output by an audio transducer
R2; Should
R2; Should
R2; Should
R2; Should
R2; Should
R2; Should
R2; Should
R2; Should
R2; Should
R2; Should
R2; Should
R2; Should
R2; Should
R2; Should
R2; Should
R2; Should
R2; Should
R2; Should
R2; Should
R2; Should
R2; Should
R2; Should
81

FINAL
RD-2501
26.2.0-3.0-9
RD-2502
26.2.0-3.0-10
RD-2503
26.2.0-3.0-10.0-1
RD-2504
26.2.0-3.0-10.0-2
RD-2505
26.2.0-3.0-11
RD-2506
26.2.0-3.0-11.0-1
RD-2507
26.2.0-3.0-11.0-2
RD-2508
26.2.0-3.0-11.0-3
RD-2509
26.2.0-3.0-11.0-4
RD-2510
26.2.0-4
RD-2511
26.2.0-4.0-1
RD-2512
26.2.0-4.0-1.0-1
RD-2513
26.2.0-4.0-1.0-2
RD-2514
26.2.0-4.0-1.0-3
RD-2515
26.2.0-4.0-1.0-4
RD-2516
RD-2517
26.2.0-4.0-1.0-5
26.2.0-4.0-1.0-6
RD-2518
26.2.0-4.0-2
RD-2519
26.2.0-4.0-3
RD-2520
26.2.0-4.0-4
which is normally held up to the ear, a means for effective magnetic wireless
coupling to hearing technologies shall be provided.
Interference to hearing technologies (including hearing aids, cochlear
implants, and assistive listening devices) shall be reduced to the lowest
possible level that allows a user of hearing technologies to utilize the
telecommunications product.
Products that transmit or conduct information or communication, shall pass
through cross-manufacturer, non-proprietary, industry-standard codes,
translation protocols, formats or other information necessary to provide the
information or communication in a usable format. Technologies which use
encoding, signal compression, format transformation, or similar techniques
shall not remove information needed for access or shall restore it upon
delivery.
Products that transmit or conduct information or communication, shall pass
through cross-manufacturer, non-proprietary, industry-standard codes,
translation protocols or formats necessary to provide the information or
communication in a usable format.
Technologies which use encoding, signal compression or format
transformation shall not remove information needed for access or shall restore
it upon delivery.
Products which have mechanically operated controls or keys, shall comply
with the following:
Controls and keys shall be tactilely discernible without activating the controls
or keys.
Controls and keys shall be operable with one hand and shall not require tight
grasping, pinching, or twisting of the wrist. The force required to activate
controls and keys shall be 5 lbs. (22.2 N) maximum.
If key repeat is supported, the delay before repeat shall be adjustable to at
least 2 seconds. Key repeat rate shall be adjustable to 2 seconds per
character.
The status of all locking or toggle controls or keys shall be visually discernible,
and discernible either through touch or sound.
Fdsys video and multimedia products shall be Section 508 compliant
according to 36 CFR Part 1194.24
All analog television displays 13 inches and larger, and computer equipment
that includes analog television receiver or display circuitry, shall be equipped
with caption decoder circuitry which appropriately receives, decodes, and
displays closed captions from broadcast, cable, videotape, and DVD signals.
As soon as practicable, but not later than July 1, 2002, widescreen digital
television (DTV) displays measuring at least 7.8 inches vertically, DTV sets
with conventional displays measuring at least 13 inches vertically, and
standalone DTV tuners, whether or not they are marketed with display
screens, and computer equipment that includes DTV receiver or display
circuitry, shall be equipped with caption decoder circuitry which appropriately
receives, decodes, and displays closed captions from broadcast, cable,
videotape, and DVD signals.
All analog television displays 13 inches and larger shall be equipped with
caption decoder circuitry which displays closed captioning.
All computer equipment that includes analog television receiver or display
circuitry shall be equipped with caption decoder circuitry which displays closed
captioning.
Widescreen digital television (DTV) displays measuring at least 7.8 inches
vertically shall display closed captions.
DTV sets with conventional displays measuring at least 13 inches vertically
shall display closed captions.
standalone DTV tuners shall display closed captions.
Computer equipment that includes DTV receiver or display circuitry shall
display closed captions.
Television tuners, including tuner cards for use in computers, shall be
equipped with secondary audio program playback circuitry.
All training and informational video and multimedia productions which support
the agencys mission, regardless of format, that contain speech or other audio
information necessary for the comprehension of the content, shall be open or
closed captioned.
All training and informational video and multimedia productions which support
R2; Should
R2; Should
R2; Should
R2; Should
R2; Should
R2; Should
R2; Should
R2; Should
R2; Should
R2; Should
R2; Should
R2; Should
R2; Should
R2; Should
R2; Should
R2; Should
R2; Should
R2; Should
R2; Should
R2; Should
82

FINAL
RD-2521
26.2.0-4.0-5
RD-2522
26.2.0-5
RD-2523
26.2.0-5.0-1
RD-2524
26.2.0-5.0-2
RD-2525
26.2.0-5.0-3
RD-2526
26.2.0-5.0-3.0-1
RD-2527
26.2.0-5.0-3.0-2
RD-2528
26.2.0-5.0-3.0-3
RD-2529
26.2.0-5.0-3.0-4
RD-2530
26.2.0-5.0-4
RD-2531
26.2.0-5.0-5
RD-2532
26.2.0-5.0-6
RD-2533
26.2.0-5.0-7
RD-2534
26.2.0-5.0-8
RD-2535
26.2.0-5.0-9
RD-2536
26.2.0-5.0-10
RD-2537
26.2.0-5.0-10.0-1
RD-2538
26.2.0-5.0-10.0-2
RD-2539
26.2.0-5.0-10.0-3
RD-2540
26.2.0-5.0-10.0-4
RD-2541
26.2.0-6
RD-2542
26.2.0-6.0-1
RD-2543
26.2.0-6.0-1.0-1
RD-2544
26.2.0-6.0-1.0-2
RD-2545
26.2.0-6.0-1.0-3
RD-2546
26.2.0-6.0-1.0-4
the agencys mission, regardless of format, that contain visual information

necessary for the comprehension of the content, shall be audio described.
Display or presentation of alternate text presentation or audio descriptions
shall be user-selectable unless permanent.
Fdsys self contained, closed products shall be Section 508 compliant
according to 36 CFR Part 1194.25
Self contained products shall be usable by people with disabilities without
requiring an end-user to attach assistive technology to the product. Personal
headsets for private listening are not assistive technology.
When a timed response is required, the user shall be alerted and given
sufficient time to indicate more time is required.
Where a product utilizes touch screens or contact-sensitive controls, an input
method shall be provided that complies with 1194.23 (k) (1) through (4).
method shall be provided that complies with 1194.23 (k) (1).
When biometric forms of user identification or control are used, an alternative
form of identification or activation, which does not require the user to possess
particular biological characteristics, shall also be provided.
When products provide auditory output, the audio signal shall be provided at a
standard signal level through an industry standard connector that will allow for
private listening. The product shall provide the ability to interrupt, pause, and
restart the audio at anytime.
When products deliver voice output in a public area, incremental volume
control shall be provided with output amplification up to a level of at least 65
dB. Where the ambient noise level of the environment is above 45 dB, a
volume gain of at least 20 dB above the ambient level shall be user
selectable. A function shall be provided to automatically reset the volume to
the default level after every use.
Color coding shall not be used as the only means of conveying information,
indicating an action, prompting a response, or distinguishing a visual element.
When a product permits a user to adjust color and contrast settings, a range
of color selections capable of producing a variety of contrast levels shall be
provided.
Products shall be designed to avoid causing the screen to flicker with a
frequency greater than 2 Hz and lower than 55 Hz.
Products which are freestanding, non-portable, and intended to be used in
one location and which have operable controls shall comply with the following:
The position of any operable control shall be determined with respect to a
vertical plane, which is 48 inches in length, centered on the operable control,
and at the maximum protrusion of the product within the 48 inch length.
Where any operable control is 10 inches or less behind the reference plane,
the height shall be 54 inches maximum and 15 inches minimum above the
floor.
Where any operable control is more than 10 inches and not more than 24
inches behind the reference plane, the height shall be 46 inches maximum
and 15 inches minimum above the floor.
Operable controls shall not be more than 24 inches behind the reference
plane
Fdsys desktop and portable computer products shall be Section 508
compliant according to 36 CFR Part 1194.26.
All mechanically operated controls and keys shall comply with 1194.23 (k)
(1) through (4).
(1).
(2).
(3).
R2; Should
R2; Should
R2; Should
R2; Should
R2; Should
R2; Should
R2; Should
R2; Should
R2; Should
R2; Should
R2; Should
R2; Should
R2; Should
R2; Should
R2; Should
R2; Should
R2; Should
R2; Should
R2; Should
R2; Should
R2; Should
R2; Should
R2; Should
R2; Should
R2; Should
R2; Should
83

FINAL
RD-2547
26.2.0-6.0-2
RD-2548
26.2.0-6.0-2.0-1
RD-2549
26.2.0-6.0-2.0-2
RD-2550
26.2.0-6.0-2.0-3
RD-2551
26.2.0-6.0-2.0-4
RD-2552
26.2.0-6.0-3
RD-2553
26.2.0-6.0-4
RD-2554
RD-2555
27
27.1
RD-2556
27.1.0-1
RD-2557
27.1.0-2
RD-2558
27.1.0-3
RD-2559
27.1.0-3.0-1
RD-2560
27.1.0-3.0-2
RD-2561
27.1.0-4
RD-2562
27.1.0-5
RD-2563
27.1.0-6
RD-2564
27.1.0-7
RD-2565
27.1.0-8
RD-2566
27.1.0-9
RD-2567
27.1.0-10
RD-2568
27.1.0-11
RD-2569
27.1.0-11.0-1
RD-2570
27.1.0-11.0-2
RD-2571
27.1.0-12
RD-2572
RD-2573
27.1.0-12.0-1
27.1.0-12.0-2
RD-2574
27.1.0-12.0-3
RD-2575
RD-2576
27.1.0-12.0-4
27.1.0-12.0-5
(4).
If a product touch-operated controls, an input method shall be provided that
complies with 1194.23 (k) (1) through (4).
If a product utilizes touch screens or touch-operated controls, an input method
shall be provided that complies with 1194.23 (k) (1).
When biometric forms of user identification or control are used, an alternative
form of identification or activation, which does not require the user to possess
particular biological characteristics, shall also be provided.
Where provided, at least one of each type of expansion slots, ports and
connectors shall comply with publicly available industry standards.
R2; Should
R2; Should
R2; Should
R2; Should
R2; Should
R2; Should
R2; Should
27 Requirements for Search

27.1 Search Core Capabilities
The system shall provide the capability to search for and retrieve content from
the system.
The system shall provide the capability to search for and retrieve metadata
from the system.
The system shall provide the capability to search across multiple internal
content and metadata repositories simultaneously and separately.
The system shall provide the capability to search across multiple internal
content and metadata collections simultaneously.
The system shall provide the capability to search internal content and
metadata collections separately.
The system shall provide the capability to search content that is currently
available on the GPO Access public Web site.
The system shall provide the capability to search cataloging records in order
to provide access to select external repositories with which GPO has formal
partnership agreements as specified in requirement RD-2311 and its sub
requirements.
The system shall provide the capability to search and retrieve unstructured
content (e.g., text).
The system shall provide the capability to match character strings (e.g.,
search exact phrases).
The system shall provide the capability to search and retrieve semi-structured
content (e.g., inline markup).
The system shall provide the capability to search and retrieve structured
content (e.g., fielded).
The system shall provide the capability to search for content by means of
querying metadata.
The system shall provide the capability for users to search collections based
on user class, user role, and access rights.
on user role.
on access rights.
The system shall provide the capability to return content packages in any form
simultaneously or separately.
The system shall provide the capability to search for digital objects.
The system shall provide the capability to search for only work in progress
content.
The system shall provide the capability to search for work in progress content
simultaneously with other content.
The system shall provide the capability to search for only SIPs.
The system shall provide the capability to search for SIPs simultaneously with
R1B; Must
R1B; Must
R1C; Must
R1C; Must
R1C; Must
R1C; Must
R2; Must
R1C; Must
R1B; Must
R1C; Must
R1B; Must
R1B; Must
R1C; Must
R1C; Must
R1C; Must
R1C; Must
R1C; Must
R1C; Must
R1C; Must
R1C; Must
R1C; Must
84

FINAL
RD-2577
RD-2578
27.1.0-12.0-6
27.1.0-12.0-7
RD-2579
RD-2580
27.1.0-12.0-8
27.1.0-12.0-9
RD-2581
27.1.0-13
RD-2582
27.1.0-14
RD-2583
27.1.0-15
RD-2584
27.1.0-16
RD-2585
27.1.0-17
RD-2586
27.1.0-18
RD-2587
27.1.0-19
RD-2588
27.2
other content.
The system shall provide the capability to search for only AIPs.
The system shall provide the capability to search for AIPs simultaneously with
other content.
The system shall provide the capability to search for only ACPs.
The system shall provide the capability to search for ACPs simultaneously
with other content.
The system shall provide the capability to ingest PDF files containing "post-it"
note comments.
The system shall provide the capability to maintain "post-it" note comments on
ingested PDF files as the files are processed through the system.
The system shall provide the capability to maintain PDF features (e.g.
bookmarks, comments, links, thumbnails) when PDF files go through a
segmentation process.
bookmarks, comments, links, thumbnails) when PDF files go through a
parsing process.
bookmarks, comments, links, thumbnails) when individual PDF files are
combined into a single PDF file.
The system shall provide the capability to index content within a PDF "post-it"
note comment.
The system shall provide the capability to deliver PDF files that contain "postit" note comments.
R1C; Must
R1C; Must
R1C; Must
R1C; Must
R1C; Must
R1C; Must
R1C; Must
R1C; Must
R1C; Must
R1C; Must
R1C; Must
27.2 Search Query

RD-2589
27.2.0-1
RD-2590
27.2.0-2
RD-2591
27.2.0-3
RD-2592
27.2.0-3.0-1
RD-2593
27.2.0-3.0-2
RD-2594
RD-2595
27.2.0-4
27.2.0-4.0-1
RD-2596
27.2.0-4.0-2
RD-2597
RD-2598
27.2.0-4.0-2.0-1
27.2.0-4.0-2.0-2
RD-2599
27.2.0-4.0-2.0-3
RD-2600
RD-2601
RD-2602
RD-2603
RD-2604
RD-2605
RD-2606
RD-2607
RD-2608
27.2.0-4.0-2.0-4
27.2.0-4.0-2.0-5
27.2.0-4.0-2.0-6
27.2.0-4.0-2.0-7
27.2.0-4.0-2.0-8
27.2.0-4.0-2.0-9
27.2.0-4.0-2.0-10
27.2.0-4.0-2.0-11
27.2.0-4.0-2.0-12
RD-2609
RD-2610
RD-2611
27.2.0-4.0-2.0-13
27.2.0-4.0-2.0-14
27.2.0-4.0-2.0-15
The system shall provide the capability for users to select content collections
to search.
The system shall provide the capability to apply business rules to user queries
so that content is searched based on query (e.g., intelligent search).
The system shall provide the capability for users to select search complexity
levels (e.g., simple search, advanced/fielded search).
The system shall allow a simple search, which allows the user to input a
search term to search across one or multiple content collections.
The system shall allow an advanced/fielded search, which allows the user to
input multiple fields to filter both content and metadata in addition to the
search term.
The system shall allow searching on any number of collections of content.
The system shall allow users to search any collection based on the metadata
associated with that collection.
The system shall allow users to search collections currently available on GPO
Access including the following:
Public and Private Laws
Congressional Reports including House, Senate, and Senate Executive
Reports.
Congressional Documents including House Documents, Senate Documents,
Senate Executive Documents, and Senate Treaty Documents.
Congressional Bills
Federal Register
History of Bills
Congressional Record
Congressional Record Index
United States Code
Code of Federal Regulations
List of Sections Affected (LSA)
Congressional Hearings (including House and Senate Appropriations
Hearings)
Congressional Committee Prints
Congressional Calendars (including House, Senate, and Committee)
Weekly Compilation of Presidential Documents
R1B; Must
R1B;
Should /
1C; Should
/ R2; Must
R1B; Must
R1B; Must
R1C; Must
R1C; Must
R1C; Must
R1C; Must
R1C; Must
R1C; Must
R1C; Must
R1C; Must
R1C; Must
R1C; Must
R1C; Must
R1C; Must
R1C; Must
R1C; Must
R1C; Must
R1C; Must
R1C; Must
R1C; Must
R1C; Must
85

FINAL
RD-2612
RD-2613
RD-2614
RD-2615
RD-2616
RD-2617
RD-2618
RD-2619
RD-2620
RD-2621
RD-2622
RD-2623
RD-2624
RD-2625
RD-2626
RD-2627
RD-2628
RD-2629
RD-2630
RD-2631
RD-2632
RD-2633
RD-2634
RD-2636
RD-2637
RD-2638
27.2.0-4.0-2.0-16
27.2.0-4.0-2.0-17
27.2.0-4.0-2.0-18
27.2.0-4.0-2.0-19
27.2.0-4.0-2.0-20
27.2.0-4.0-2.0-21
27.2.0-4.0-2.0-22
27.2.0-4.0-2.0-23
27.2.0-4.0-2.0-24
27.2.0-4.0-2.0-25
27.2.0-4.0-2.0-26
27.2.0-4.0-2.0-27
27.2.0-4.0-2.0-28
27.2.0-4.0-2.0-29
27.2.0-4.0-2.0-30
27.2.0-4.0-2.0-31
27.2.0-4.0-2.0-32
27.2.0-4.0-2.0-33
27.2.0-4.0-2.0-34
27.2.0-4.0-2.0-35
27.2.0-4.0-2.0-36
27.2.0-4.0-2.0-37
27.2.0-4.0-2.0-38
27.2.0-4.0-2.0-39
27.2.0-4.0-2.0-40
27.2.0-4.0-2.0-41
RD-2639
RD-2640
RD-2641
RD-2642
27.2.0-4.0-2.0-42
27.2.0-4.0-2.0-43
27.2.0-4.0-2.0-44
27.2.0-4.0-2.0-45
RD-2643
RD-2644
RD-2645
27.2.0-4.0-2.0-46
27.2.0-4.0-2.0-47
27.2.0-4.0-2.0-48
RD-2646
RD-2647
RD-2648
RD-2649
RD-2650
27.2.0-4.0-2.0-49
27.2.0-4.0-2.0-50
27.2.0-4.0-2.0-51
27.2.0-4.0-2.0-52
27.2.0-4.0-2.0-53
RD-2651
27.2.0-4.0-2.0-54
RD-2652
27.2.0-4.0-2.0-55
RD-2653
27.2.0-4.0-2.0-56
RD-2654
RD-2655
RD-2656
RD-2657
RD-2658
RD-2659
RD-2660
RD-2661
RD-2662
RD-2663
27.2.0-4.0-2.0-57
27.2.0-4.0-2.0-58
27.2.0-4.0-2.0-59
27.2.0-4.0-2.0-60
27.2.0-4.0-2.0-61
27.2.0-4.0-2.0-62
27.2.0-4.0-2.0-63
27.2.0-4.0-2.0-64
27.2.0-4.0-2.0-65
27.2.0-4.0-2.0-66
RD-2664
RD-2665
RD-2666
27.2.0-4.0-2.0-67
27.2.0-4.0-2.0-68
27.2.0-4.0-2.0-69
Budget of the United States Government

Congressional Record (Bound)
House Journal
Semiannual regulatory Agenda (Unified Agenda)
U.S. Constitution Analysis and Interpretation
Economic Indicators
Economic Report of the President
Congressional Directory
U.S. Government Manual
Public Papers of the President of the United States
House Ways and Means Committee Prints
GAO Comptroller General Decisions
GAO Reports
House Practice
Senate Manual
House Rules and Manual
Privacy Act Issuances
Department of Interior Inspector General Reports
U.S. Government Printing Office Style Manual
Cannons Precedents of the U.S. House of Representatives
Hinds Precedents of the House of Representatives
Independent Counsels Reports
Government Information Locator Service Records (GILS)
Davis-Bacon Wage Determinations
Commerce Business Daily
Congressional Publications (including Miscellaneous House and Senate
Publications)
Statutes at Large
Deschlers Precedents of the U.S. House of Representatives
eCFR (Electronic Code of Federal Regulations)
Background Material and Data on Programs within the Jurisdiction of the
Committee on Ways and Means (Green Book)
Conference Reports
Education Reports from ERIC
History of Line Item Veto Notices, Prior to Supreme Court Opinion No. 971374
Overview and Compilation of U.S. Trade Statutes (Blue Book)
Riddicks Senate Procedures
United States Government Policy and Support Positions (Plum Book)
Citizens Guide to the Federal Budget
Challenger Space Shuttle Accident Selected Congressional Hearings and
Reports
Comprehensive Revised Report with Addendums on Iraqs Weapons of Mass
Destruction (Duelfur Report)
Final Report of the National Commission on Terrorist Attacks Upon the United
States, Official Government Edition (9/11 Report)
Report of the Select Committee on Intelligence U.S. Intelligence Communitys
Pre-was Assessments on Iraq
State of New York, ex rel. Eliot Spitzer, et al. v. Microsoft
Export Administration Regulations
Bureau of Land Management Publications
State of Union Addresses
National Labor Relations Board Publications
Federal Bulletin Board
In-scope publications on GPOs Permanent Server
In-scope publications on GPOs Web Servers
200 Notable Days: Senate Stories, 1787 to 2002
Unclassified Version of the Report of the Commission on the Intelligence
Capabilities of the United States Regarding Weapons of Mass Destruction
Supreme Court Nomination Hearings
Supreme Court Decisions 1937-1975
Joint Inquiry into Intelligence Community Activities before and after the
Terrorist Attacks of September 11, 2001
R1C; Must
R1C; Must
R1C; Must
R1C; Must
R1C; Must
R1C; Must
R1C; Must
R1C; Must
R1C; Must
R1C; Must
R1C; Must
R1C; Must
R1C; Must
R1C; Must
R1C; Must
R1C; Must
R1C; Must
R1C; Must
R1C; Must
R1C; Must
R1C; Must
R1C; Must
R1C; Must
R1C; Must
R1C; Must
R1C; Must
R1C; Must
R1C; Must
R1C; Must
R1C; Must
R1C; Must
R1C; Must
R1C; Must
R1C; Must
R1C; Must
R1C; Must
R1C; Must
R1C; Must
R1C; Must
R1C; Must
R1C; Must
R1C; Must
R1C; Must
R1C; Must
R1C; Must
R1C; Must
R1C; Must
R1C; Must
R1C; Must
R1C; Must
R1C; Must
R1C; Must
R1C; Must
R1C; Must
86

FINAL
RD-2667
RD-2668
RD-2669
RD-2670
RD-2672
27.2.0-4.0-2.0-70
27.2.0-4.0-2.0-71
27.2.0-4.0-2.0-72
27.2.0-4.0-2.0-73
27.2.0-6
RD-2673
RD-2674
RD-2675
RD-2676
RD-2677
27.2.0-6.0-1
27.2.0-6.0-1.0-1
27.2.0-6.0-1.0-2
27.2.0-6.0-1.0-3
27.2.0-6.0-1.0-4
RD-2678
RD-2679
27.2.0-6.0-1.0-4.01
27.2.0-6.0-1.0-5
RD-2682
RD-2683
27.2.0-7
27.2.0-7.0-1
RD-2684
RD-2685
RD-2686
RD-2687
RD-2688
RD-2689
RD-2690
RD-2691
27.2.0-7.0-2
27.2.0-7.0-3
27.2.0-7.0-4
27.2.0-8
27.2.0-9
27.2.0-9.0-1
27.2.0-10
27.2.0-10.0-1
RD-2692
RD-2693
27.2.0-10.0-2
27.2.0-11
RD-2694
RD-2695
RD-2696
RD-2697
RD-2699
27.2.0-12
27.2.0-13
27.2.0-14
27.2.0-15
27.2.0-17
RD-2701
RD-2702
RD-2703
RD-2704
27.2.0-19
27.2.0-20
27.2.0-21
27.2.0-22
RD-2705
27.3
Featured House Documents

Featured Senate Documents
Congressional Serial Set
Congressional Committee Materials
The system shall allow users to perform a search for conceptually related
terms (e.g., search for World Series returns articles on the Red Sox).
The system shall allow authorized users to manage concept relationships.
The system shall allow authorized users to add concept relationships.
The system shall allow authorized users to delete concept relationships.
The system shall allow authorized users to modify concept relationships.
The system shall suggest new concept relationships based on ingested
content.
The system shall automatically create new concept relationships based on an
authorized users acceptance of suggested new concept relationships
The system shall use new concepts without requiring previously indexed
content is reindexed.
The system shall support standard Boolean search language.
The system shall support full Boolean operators, including AND, OR, NOT,
BEFORE, NEAR, and ADJACENT.
The system shall support implied Boolean operators, including + and -.
The system shall support the nesting of Boolean operators via parentheses.
No user shall be required to enter case sensitive operators.
The system shall allow users to perform a natural language search.
The system shall support a customizable list of stop words.
The system shall support a customizable list of idioms.
The system shall allow for stemming of search terms.
The system shall allow for left side stemming.
The system shall allow for right side stemming.
The system shall allow users to use wildcard characters to replace characters
within words.
The system shall support proximity searching.
The system shall support synonyms searching.
The system shall provide the capability for contextual searching.
The system shall conform to ISO 239.50.
The system shall have a documented interface (e.g., API) to allow search by
non-GPO systems.
The system shall allow users to select specified search functionality.
The system shall support queries of variable lengths.
The system shall have the ability to limit search query length.
The system shall provide the capability to weight search terms (e.g., term
must appear, term must not appear, term is part of an exact phrase).
R1C; Must
R1C; Must
R1C; Must
R1C; Must
R1C; Must
R1C; Must
R1C; Must
R1C; Must
R1C; Must
R1C; Must
R1C; Must
R1C; Must
R1C; Must
R1B; Must
R1C; Must
R1C; Must
R1B; Must
R1C; Must
R1C; Must
R1C; Must
R1C; Must
R1C;
Should
R1C; Must
R1B; Must
R1C; Must
R1C; Must
R1C; Could
R1C; Must
R1C; Must
R1B; Must
R1B; Must
R1C; Must
R1C; Must
27.3 Search Refine

RD-2706
27.3.0-1
RD-2707
27.3.0-1.0-1
RD-2708
27.3.0-1.0-2
RD-2709
27.3.0-2
RD-2710
27.3.0-2.0-1
RD-2711
RD-2712
27.3.0-3
27.3.0-3.0-1
RD-2713
27.4
The system shall provide the capability for users to modify previous search
queries to enable execution of subsequent searches.
The system shall provide the capability to direct subsequent queries against
different content collections.
The system shall provide the capability for users to retain selected targets
from a result set and modify said query to be rerun against the result.
The system shall provide the capability to display a list of terms that are
conceptually related to the original search term.
The system shall provide users with the ability to directly execute a search
from conceptually related terms.
The system shall be able to recognize alternate spellings of terms.
The system shall suggest corrected spellings of terms.
R1C; Must
R2; Must
R2; Must
R2; Must
R1C; Must
R1C; Must
R2; Must
27.4 Search Results

RD-2714
27.4.0-1
The system shall have the capability to take users to the exact occurrence of
R1C; Must
87

FINAL
the search term or its conceptual equivalent in a result.
The system shall allow a user to navigate the levels of granularity applied to a
result from within that result.
The system shall provide the capability for users to bookmark individual
search results.
The system shall provide search results to users.
The system shall provide the capability to group versions, renditions, and
formats into one entry in a search results list.
RD-2715
27.4.0-2
RD-2716
27.4.0-3
RD-2717
RD-2718
27.4.0-4
27.4.0-5
RD-2719
27.4.0-6
RD-2720
RD-2721
27.4.0-7
27.4.0-8
RD-2722
RD-2723
RD-2724
RD-2725
27.4.0-9
27.4.0-10
27.4.0-11
27.4.0-12
RD-2726
27.4.0-13
RD-2727
27.4.0-13.0-1
RD-2728
27.4.0-13.0-2
RD-2729
27.4.0-14
RD-2732
27.4.0-17
RD-2733
27.4.0-17.0-1
The system shall provide the capability to highlight query terms in the
document.
RD-2734
27.4.0-17.0-2
The system shall provide the capability to highlight query terms in the
document abstract or document summary that appears results list.
RD-2735
RD-2736
27.4.0-18
27.4.0-19
RD-2737
27.4.0-20
The system shall provide feedback to the user in the event of an error.
The system shall provide the capability to display inline image thumbnails of
content in a results list.
The system shall allow users to save search results individually or as a batch
(e.g., without selecting each result individually) for export.
RD-2738
27.4.0-21
RD-2739
27.4.0-22
RD-2740
RD-2741
27.4.0-23
27.4.0-23.0-1
RD-2742
27.4.0-23.0-2
RD-2743
27.5
RD-2744
27.5.0-1
The system shall allow users with an established user account and profile to
enter or store queries, preferences, and results sets or portions of results sets.
RD-2745
27.5.0-1.0-1
RD-2746
27.5.0-1.0-2
RD-2747
27.5.0-1.0-3
enter or store and recall queries.
enter or store and recall preferences.
The system shall provide the capability to sort results lists on displayable
attributes in the result set.
The system shall provide the capability to categorize results.
The system shall provide the capability to cluster results.
The system shall provide the capability to analyze results.
The system shall provide the capability to display results graphically.
The system shall provide the capability to apply one or multiple taxonomies.
The system shall provide the capability for users to limit the number of results
displayed.
The system shall provide the capability to display the total number of results in
the result set returned by the search.
The system shall allow the user to select the number of results in a result set
from available options.
The system shall allow a result set equal to the size of all records in all
indexes.
The system shall allow authorized users to select which metadata attributes
are viewable for each collection.
The system shall provide the capability to highlight query terms.
The system shall provide the capability to return search results at the lowest
level of granularity supported by the content package.
The system shall provide the capability for authorized users to modify
relevancy ranking factors.
The system shall provide the capability to filter search results.
The system shall provide the capability for users to return to their original
search results after results have been filtered.
The system shall provide the capability for authorized users to define search
filters.
R1C; Must
R1C; Must
R1B; Must
R1B;
Should /
R1C; Must
R1C; Must
R1C; Must
R1C;
Should
R2; Could
R2; Could
R1C; Must
R1C; Must
R2; Must
R2; Must
R2; Must
R1B; Must
R1C;
Could / R2;
Must
R1C;
Could / R2;
Must
R1C;
Could / R2;
Must
R1B; Must
R2; Must
R1B;
Should /
R1C; Must
R1C; Must
R1B;
Should /
R1C; Must
R1C; Must
R1C; Must
R1C; Must
27.5 Saved Searches

R1C;
Should /
R2; Must
R2; Must
R2; Must
R2; Must
88

FINAL
RD-2748
27.5.0-1.0-4
RD-2749
27.5.0-2
RD-2750
27.5.0-3
RD-2751
27.6
RD-2752
27.6.0-1
RD-2754
27.6.0-3
RD-2755
27.6.0-4
RD-2756
27.6.0-5
RD-2757
27.7
enter or store and recall results sets as a whole.

enter or store and recall portions of results sets.
The system shall provide the capability to automatically execute saved
searches on a schedule defined by the user.
The system shall provide the capability to notify users when automatically
executed searches return results that were not included in the original search.
R2; Must
R1C;
Should /
R2; Must
R1C;
Should /
R2; Must
27.6 Search Interface

The system shall provide a search interface that allows users to submit
queries to the system and receive results.
The system shall provide the capability to have customizable search
interfaces based on user preferences.
The system shall provide the capability to have navigational elements to allow
users to navigate through results.
Deleted.
R1B; Must
R1B;
Should /
R1C; Must
R1B; Must
27.7 Search Administration

RD-2758
27.7.0-1
RD-2759
27.7.0-2
RD-2761
27.7.0-4
RD-2762
27.7.0-5
RD-2763
27.7.0-6
RD-2764
RD-2765
28
28.1
The system shall provide the capability to manage an unlimited number of

collections.
The system shall provide a Web-based administrator graphical user interface
(GUI).
The system shall provide for the control of search run times, including the
ability to preempt runtimes by an administrator-defined limit.
The system shall provide the capability to support user search while other
system functions are being performed (e.g., re-indexing databases, updating
content).
The system shall provide the capability to log search activities.
R1B; Must
R1B; Must
R2; Must
R1B; Must
R1B; Must
28 Requirements for Request

28.1 Request Core Capabilities
RD-2766
28.1.0-1
RD-2767
28.1.0-2
RD-2769
28.2
The system shall provide the capability for users to request delivery of
content.
The system shall provide the capability for users to request delivery of
metadata.
R1B; Must
R1C; Must
28.2 No Fee Requests

RD-2770
28.2.0-1
RD-2771
28.2.0-1.0-1
RD-2772
28.2.0-1.0-2
RD-2773
28.2.0-1.0-2.0-1
RD-2774
28.2.0-1.0-2.0-2
RD-2775
28.2.0-2
The system shall provide the capability for End Users to request no-fee
content delivery.
The system shall not restrict or otherwise diminish access to items that are
currently available through GPO Access.
The system shall provide the capability for users to print and download
information currently available through GPO Access.
The system shall maintain printing functionality currently available within GPO
Access content collections.
The system shall maintain downloading functionality currently available within
GPO Access content collections.
The system shall provide the capability for Federal Depository Library End
Users to select and request content and metadata for delivery to their library
R1B; Must
R1C; Must
R1C; Must
R1C; Must
R1C; Must
R2; Must
89

FINAL
RD-2776
28.2.0-3
RD-2777
28.2.0-4
RD-2778
28.2.0-5
RD-2779
28.2.0-6
RD-2780
RD-2781
28.2.0-7
28.2.0-8
RD-2782
28.2.0-8.0-1
RD-2783
28.2.0-8.0-2
RD-2784
28.2.0-9
RD-2785
28.2.0-9.0-1
RD-2786
28.2.0-10
RD-2788
28.2.0-12
RD-2789
28.3
RD-2790
28.3.0-1
RD-2791
28.3.0-2
RD-2792
28.3.0-3
RD-2793
28.3.0-4
RD-2794
28.3.0-5
RD-2795
28.3.0-5.0-1
RD-2796
28.3.0-5.0-2
RD-2797
RD-2798
RD-2799
28.3.0-5.0-3
28.3.0-5.0-4
28.3.0-6
RD-2800
28.3.0-7
RD-2801
28.3.0-8
RD-2802
28.3.0-9
RD-2803
28.3.0-10
based on their unique profile and preferences.

The system shall comply with GPO policies related to selection of tangible and
electronic titles by Federal Depository Library End Users.
The system shall provide the capability to interface with Authorized
Representatives designated by GPOs Library Services and Content
Management business unit for processing of no-fee delivery requests.
The system shall provide the capability to interface with GPOs Integrated
Library System and other legacy systems as defined by GPO business units
for processing of no-fee requests.
The system shall provide the capability to process no-fee requests for delivery
of content with access restrictions.
The system shall support the delivery of serials and periodicals.
The system shall provide the capability for users to cancel full or partial
requests prior to fulfillment.
The system shall provide the capability for users to cancel full requests prior
to fulfillment.
The system shall provide the capability for users to cancel partial requests
prior to fulfillment.
The system shall provide the capability to deliver personalized offers to
registered users based on user request history or users with similar request
histories. (e.g. you may also be interested in).
The system shall provide the capability for users to opt-out of personalized
offers.
The system shall provide the capability to provide authorized users with a
detailed transaction summary.
The system shall provide the capability to generate reports for no-fee
transactions.
R2; Must
R2; Must
R2; Must
R2; Must
R2; Must
R1C; Must
R1C; Must
R1C; Must
R1C; Could
/ R2; Must
R1C; Could
/ R2; Must
R1C;
Should /
R2; Must
R1C; Must
28.3 Fee-based Requests

The system shall provide the capability for users to request fee-based content
delivery.
The system shall have the capability to interface with external Athorized
Representatives as designated by GPO's Publication and Information Sales
business unit for processing of fee-based delivery requests.
The system shall provide the capability to interface with GPO's financial and
inventory systems for processing of fee-based requests.
The system shall have the capability to retrieve price information from external
systems.
The system shall have the capability to adjust price information for fee-based
content delivery.
Pricing structures shall comply with GPO's legislative mandates under Title 44
of the United States Code and GPO's Sales Program policies.
The system shall provide the capability for authorized users to manually adjust
the price.
The system shall provide the capability to dynamically adjust the price.
The system shall provide the capability to apply price schedules.
The system shall adhere to industry best practices for performance of a Webaccessible e-commerce system.
The system shall include an online bookstore web interface that complies with
the FDsys interface requirements and includes a shopping cart, order
tracking, backorder capabilities, third party ordering, thumbnail cover images,
and a fully browsable and searchable catalog of items available for purchase
that is updated at least daily.
The system shall provide the capability to process international and domestic
requests for hard copy, electronic presentation, digital media, and service
product lines as designated by GPO's Publication and Information Sales
business unit.
The system shall provide the capability to process fee-based requests for the
delivery of content with access restrictions.
The system shall support the collection of information (order taking) and pass
this information to external systems for processing.
R2; Must
R2; Must
R2; Must
R2; Must
R2; Must
R2; Must
R2; Must
R2; Must
R2; Must
R2; Must
R2; Must
R2; Must
R2; Must
R2; Must
90

FINAL
RD-2804
28.3.0-10.0-1
RD-2805
RD-2806
28.3.0-10.0-1.0-1
28.3.0-10.0-1.0-2
RD-2807
RD-2808
RD-2809
RD-2810
RD-2811
RD-2812
RD-2813
RD-2814
28.3.0-10.0-1.0-3
28.3.0-10.0-1.0-4
28.3.0-10.0-1.0-5
28.3.0-10.0-1.0-6
28.3.0-10.0-1.0-7
28.3.0-10.0-1.0-8
28.3.0-10.0-1.0-9
28.3.0-10.0-2
RD-2815
28.3.0-10.0-3
RD-2816
RD-2817
RD-2818
28.3.0-10.0-4
28.3.0-10.0-5
28.3.0-10.0-6
RD-2819
28.3.0-10.0-7
RD-2820
28.3.0-11
RD-2821
28.3.0-11.0-1
RD-2822
28.3.0-11.0-2
RD-2823
28.3.0-12
RD-2824
28.3.0-13
RD-2825
28.3.0-13.0-1
RD-2826
28.3.0-14
RD-2827
28.3.0-14.0-1
RD-2828
28.3.0-14.0-2
RD-2829
28.3.0-15
RD-2830
28.3.0-15.0-1
RD-2831
28.3.0-16
RD-2832
28.3.0-17
RD-2833
28.3.0-18
RD-2834
28.3.0-19
RD-2835
28.3.0-19.0-1
RD-2836
28.3.0-20
The system shall support the collection of payment information via the
following methods:
Check/electronic transfer
Major credit cards including Visa, MasterCard, Discover/NOVUS, and
American Express
Debit cards
Purchase orders
Requests for invoicing
Deposit accounts
Government Account
Cash
Gift card
The system shall securely pass information to external systems for
processing.
The system shall comply with the Federal Trade Commission's Mail or
Telephone Order Merchandise Rule.
The system shall comply with the Fair Credit Billing Act.
The system shall comply with the Fair Credit Reporting Act.
The system shall comply with the Children's Online Privacy Protection Act
(COPPA).
The system shall comply with the FTC's rules for implementing the Children's
Online Privacy Protection Act (COPPA).
The system shall provide the capability to automatically verify and validate
payment information submitted by users prior to delivery fulfillment.
The system shall provide the capability to validate payment information in
real-time via external GPO systems.
The system shall provide the capability to validate payment information in
real-time via the U.S. Treasury Department's Pay.gov credit card processing
system
The system shall provide the capability for users to delegate requests to other
users (e.g. user's "hand-off" orders to other authorized officials to submit
payment).
The system shall provide the capability to display lists of new and popular
titles, best sellers, and other lists as defined by GPO business rules.
The system shall provide the capability to display lists of all hard copy,
electronic presentation, digital media, and service product lines as designated
by GPO's Publication and Information Sales business unit.
The system shall support delivery of content by subscriptions (i.e. an
agreement by which a user obtains access to requested content by payment
of a periodic fee or other agreed upon terms.)
The system shall provide the capability to manage, secure, and maintain End
User information associated with subscriptions.
The system shall provide the capability to notify End Users when their
subscriptions are about to end (e.g., renewal notices).
The system shall provide the capability to deliver personalized offers based on
individual user request history or users with similar request histories. (e.g.
"you may also be interested in").
The system shall provide the capability for users to opt-out of personalized
offers.
The system shall provide the capability for users to cancel full or partial
requests prior to fulfillment.
The system shall provide the capability to provide authorized users with a
detailed transaction summary.
The system shall provide the capability for authorized users to configure
transaction summaries.
The system shall provide the capability to manage transaction records
according to GPO, Federal, and FTC regulations in accordance with GPO
privacy and required records retention policies.
The system shall securely maintain electronic copies of orders, shipments,
and financial records for at least seven years.
The system shall provide the capability to generate reports for fee-based
transactions (e.g., order histories, sales transactions, inventory data).
R2; Must
R2; Must
R2; Must
R2; Must
R2; Must
R2; Must
R2; Must
R2; Must
R2; Must
R2; Must
R2; Must
R2; Must
R2; Must
R2; Must
R2; Must
R2; Must
R2; Must
R2; Must
R2; Must
R2; Must
R1C;
Should /
R2; Must
R2; Must
R2; Must
R2; Must
R2; Must
R2; Must
R2; Must
R2; Must
R2; Must
R2; Must
R2; Must
R2; Must
R2; Must
91

FINAL
RD-2837
28.4
28.4 Request Delivery Options

RD-2838
28.4.0-1
RD-2839
28.4.0-2
RD-2840
28.4.0-3
RD-2841
28.4.0-4
RD-2842
28.4.0-5
RD-2843
28.4.0-6
RD-2844
28.4.0-7
RD-2845
28.4.0-8
RD-2846
28.4.0-9
RD-2847
28.4.0-10
RD-2848
28.4.0-11
RD-2849
28.4.0-12
RD-2850
28.4.0-13
RD-2851
28.4.0-14
RD-2852
28.4.0-15
RD-2853
28.4.0-16
RD-2854
28.4.0-17
RD-2855
28.4.0-18
RD-2856
28.4.0-19
RD-2857
28.4.0-20
RD-2858
28.4.0-21
RD-2859
28.4.0-22
RD-2860
28.4.0-22.0-1
RD-2861
28.4.0-22.0-2
RD-2862
28.4.0-23
RD-2863
28.5
The system shall have the capability to determine what options are available
for delivery of particular content or metadata.
The system shall provide the capability for users to request delivery of content
or metadata from available options as defined by GPO business units.
The system shall provide the capability for users to select format from
available options (e.g., text based document or publication, audio, video,
integrated resource such as a web page, geospatial).
The system shall provide the capability for users to select file type from
available options (e.g., DOC, MP3, PDF).
The system shall provide the capability for users to select resolution (e.g.,
images, video) from available options.
The system shall provide the capability for users to select color space from
available options (e.g. RGB, CMYK).
The system shall provide the capability for users to select compression and
size from available options.
The system shall provide the capability for users to select transfer rate from
available options.
The system shall provide the capability for users to select platform from
available options.
The system shall provide the capability for users to select the version of
content from available options.
The system shall provide the capability for users to select delivery of related
content from available options.
The system shall provide the capability for users to select metadata schema
or input standards from available supported options (e.g. ONIX, Advanced
Book Information, MARC, OAI-PMH).
The system shall provide the capability for users to select quantity of items
requested for delivery (e.g., one, five, batch).
The system shall provide the capability for users to select output type from
available options (e.g., hard copy, electronic presentation, digital media).
The system shall provide the capability for users to select data storage device
from available options (e.g., CD, DVD, server).
The system shall provide the capability for users to select level of granularity
from available options (e.g., title, part, section, paragraph, graphic, page).
The system shall provide the capability for users to select electronic delivery
method from available options (e.g., FTP, RSS, email, download, broadcast).
The system shall provide the capability for users to schedule delivery from the
system.
The system shall provide the capability for users to select tangible delivery
method from available options (e.g., air transportation, ground transportation,
pickup, overnight, priority, freight).
The system shall provide the capability for GPO to offer users separate bill
to and ship to options for delivery or shipment of tangible content.
The system shall provide the capability for users to submit multiple address
options for delivery or shipment of tangible content.
The system shall provide the capability to preview requested content.
The system shall provide the capability to view the access copy of content
where available.
The system shall provide the capability for authorized users to preview
publications that have been created from custom composition and content
formatting.
The system shall have the capability to support custom composition and
content formatting from available options (e.g., 2 columns, cover stock, font).
R1C; Must
R2; Must
R1C; Must
R1C; Must
R1C; Could
/ R2; Must
R1C; Could
/ R2; Must
R1C; Could
/ R2; Must
R1C; Could
/ R2; Must
R2; Must
R1B; Must
R1C;
Should /
R2; Must
R1C; Must
R1C; Must
R1C; Must
R1C; Must
R1B; Must
R1C; Must
R1C; Must
R2; Must
R2; Must
R2; Must
R2; Should
/ R3; Must
R1C; Must
R3; Must
R2; Should
/ R3; Must
28.5 Request User Accounts
92

FINAL
RD-2864
28.6
28.6 Order Numbers and Request Status

RD-2865
28.6.0-1
RD-2866
RD-2867
RD-2868
RD-2869
28.6.0-2
28.6.0-3
28.6.0-4
28.6.0-5
RD-2870
RD-2871
29
29.1
The system shall provide the capability to assign an order number for
requests.
The system shall not repeat an order number.
The system shall record order numbers in metadata.
The system shall have the capability to provide order numbers to users.
The system shall provide the capability for users to track the status of their
requests.
R2; Must
R2; Must
R2; Must
R2; Must
R2; Must
29 Requirements for Cataloging and

Reference Tools
29.1 Cataloging and Reference Tools
Metadata Management
RD-2873
29.1.0-2
RD-2874
29.1.0-3
RD-2875
RD-2876
29.1.0-4
29.1.0-4.0-1
RD-2877
29.1.0-4.0-2
RD-2878
29.1.0-5
RD-2879
RD-2881
29.1.0-6
29.1.0-8
RD-2882
29.1.0-9
RD-2883
RD-2884
RD-2885
RD-2886
RD-2887
RD-2888
RD-2889
29.1.0-10
29.1.0-11
29.1.0-11.0-1
29.1.0-11.0-2
29.1.0-11.0-3
29.1.0-12
29.1.0-13
RD-2890
29.1.0-14
RD-2891
29.1.0-15
RD-2892
29.2
The system shall support creation of metadata according to specified

cataloging rules.
The system shall apply authority control to certain fields to provide crossreferencing of terms.(e.g., a user enters any form of a name, title, or subject in
a search and all database items associated with that form must be retrieved).
The system shall support the creation of ONIX metadata
The system shall support the creation of ONIX metadata from existing
metadata.
Fdsys shall notify users that content is available for selection for the sales
program.
The system shall support the creation of library standard bibliographic records
(e.g., MARC).
The system shall support the extraction of metadata from content.
The system shall provide for the creation of new metadata records based on
existing metadata records.
The system shall provide the capability to acquire and integrate metadata
from external sources.
The system shall relate descriptive metadata with the content described.
The system shall provide capability for authorized users to manage metadata.
The system shall provide capability for authorized users to add metadata.
The system shall provide capability for authorized users to modify metadata.
The system shall provide capability for authorized users to delete metadata.
System shall record the change history of cataloging metadata.
The system shall have the ability to provide access to metadata throughout
the lifecycle of the content.
The system shall provide the capability to add metadata specifically for GPO
sales purposes (e.g., book jacket art, reviews, summaries).
The system shall have the capability to record and manage relationships
among the issues or volumes of serially-issued publications.
R1B; Must
R1C; Must
R2; Must
R2; Must
R2; Must
R1B; Must
R2; Must
R1B; Must
R2; Must
R1B; Must
R1B; Must
R1B; Must
R1B; Must
R1B; Must
R2; Must
R1B; Must
R2; Could
R1B; Must

Metadata Delivery
RD-2893
29.2.0-1
RD-2894
RD-2895
RD-2896
RD-2897
RD-2898
29.2.0-2
29.2.0-3
29.2.0-4
29.2.0-5
29.2.0-6
The system shall provide the capability to export metadata as individual

records or in batch based on user-defined parameters.
The system will provide for display and output of brief citations.
The system will provide for display and output of basic bibliographic citations.
The system will provide for display and output of full records.
The system will provide for display and output of MARC records.
The system will provide for the delivery of output in a variety user-specified
R1C; Must
R1B; Must
R1C; Must
R1B; Must
R1B; Must
R2; Must
93

FINAL
RD-2899
29.2.0-6.0-1
RD-2900
RD-2901
29.2.0-6.0-2
29.2.0-6.0-3
RD-2902
29.2.0-7
RD-2903
29.2.0-7.0-1
RD-2904
29.2.0-7.0-2
RD-2905
29.2.0-7.0-3
RD-2906
29.2.0-7.0-4
RD-2907
29.2.0-7.0-5
RD-2908
29.3
methods or formats, including electronic mail or Web pages.

The system will be capable of delivering metadata to users in electronic mail
messages.
The system will be capable of delivering metadata to users in Web pages.
The system shall support the capability to deliver metadata to users in
additional formats in the future.
The system shall output metadata in formats specified by the user, including
MARC, ONIX, ASCII text, or comma delimited text.
The system shall output metadata in MARC format when requested by the
user.
The system shall output metadata in ONIX format when requested by the
user.
The system shall output metadata in ASCII text format when requested by the
user.
The system shall output metadata in comma-delimited format when requested
by the user.
The system shall support the capability to output metadata in additional
formats in the future.
R2; Must
R2; Must
R2; Must
R2; Must
R2; Must
R2; Must
R2; Must
R2; Must
R2; Must
29.3 Reference Tools

RD-2909
29.3.0-1
RD-2910
29.3.0-2
RD-2911
29.3.0-3
RD-2912
29.3.0-4
RD-2913
29.3.0-5
RD-2914
RD-2915
29.3.0-6
29.3.0-7
RD-2916
RD-2917
RD-2918
RD-2919
29.3.0-8
29.3.0-9
29.3.0-9.0-1
29.3.0-9.0-2
RD-2920
29.3.0-9.0-3
RD-2921
29.3.0-10
The system shall have the ability to generate lists based on any metadata
field.
The system shall have the capability to generate lists based on search query
(e.g., that match a librarys item selection profile).
The system should have the capability to generate lists that point to content
(e.g., electronic journals, lists of products that are available for purchase from
the GPO Sales Program).
The system should have the capability to generate lists that point to metadata
(e.g., lists of publications available for selection by depository libraries).
The system should have the capability to generate lists that point to related
resources or other reference tools (e.g., Browse Topics).
The system shall have the capability to link to external content and metadata.
The system shall be interoperable with third party reference tools (e.g., search
catalogs of other libraries).
The system shall have the capability to dynamically generate reference tools.
The system will allow GPO to manage reference tools.
The system will allow GPO to add reference tools.
The system will allow GPO to update reference tools with capability of saving
previous versions
The system will allow GPO to delete reference tools, with capability of saving
previous versions.
The system shall be able to generate lists based on user preferences.
RD-2922
29.3.0-11
The system shall provide the capability for users to customize reference tools.
RD-2923
29.3.0-12
The system shall support interactive processes so users can create reference
tools.
RD-2924
29.4
R2; Must
R2; Must
R2; Must
R2; Must
R2; Should
R2; Must
R3; Should
R3; Could
R2; Must
R2; Must
R2; Must
R2; Must
R1C;
Should /
R2; Must
R1C;
Should /
R2; Must
R2; Should

Interoperability and Standards
RD-2925
29.4.0-1
RD-2926
29.4.0-2
RD-2927
29.4.0-2.0-1
RD-2928
29.4.0-2.0-2
The system shall interface with, and allow full functionality of, the GPO
Integrated Library System.
The system shall be compliant with NISO and ISO standards commonly used
in the information industry.
The system shall be compliant with NISO standard Z39.2 - Information
Interchange Format
The system shall be compliant with NISO standard Z39.9 - International
R2; Must
R2; Must
R2; Must
R2; Must
94

FINAL
RD-2929
29.4.0-2.0-3
RD-2930
29.4.0-2.0-4
RD-2931
29.4.0-2.0-5
RD-2932
29.4.0-2.0-6
RD-2933
29.4.0-2.0-7
RD-2934
29.4.0-2.0-8
RD-2935
29.4.0-2.0-9
RD-2936
RD-2937
RD-2938
29.4.0-2.0-10
29.4.0-3
29.4.0-3.0-1
RD-2939
29.4.0-3.0-2
RD-2940
29.4.0-3.0-3
RD-2941
29.4.0-3.0-4
RD-2942
29.4.0-3.0-5
RD-2943
29.4.0-3.0-6
RD-2944
29.4.0-3.0-7
RD-2945
29.4.0-3.0-8
RD-2946
29.4.0-3.0-9
RD-2947
29.4.0-3.0-10
RD-2948
29.4.0-3.0-11
RD-2949
29.4.0-3.0-12
RD-2950
29.4.0-3.0-13
RD-2951
29.4.0-3.0-14
RD-2952
29.4.0-4
RD-2953
29.4.0-5
Standard Serial Numbering-ISSN

The system shall be compliant with NISO standard Z39.29 - Bibliographic
References
The system shall be compliant with NISO standard Z39.43 -Standard
Address Number (SAN) for the Publishing Industry
The system shall be compliant with NISO standard Z39.50 -Information
Retrieval: Application Service Definition & Protocol Specification
The system shall be compliant with NISO standard Z39.56 - Serial Item and
Contribution Identifier (SICI)
The system shall be compliant with NISO standard Z39.69 - Record Format
for Patron Records
The system shall be compliant with NISO standard Z39.71 - Holding
Statements for Bibliographic Items
The system shall be compliant with NISO standard Z39.85 - Dublin Core
Metadata Element Set.
The system shall support commonly used cataloging standards.
The system shall support the creation of ONIX records.
The system shall provide the capability to support search of GPO local data
elements that identify unique attributes of the FDLP (e.g., GPO
Superintendent of Documents (SuDocs) classification number, Item number,
Depository Library number).
The system shall support the use of the following and support all subsequent
modifications, updates and revisions to the Library of Congress Classification.
modifications, updates and revisions to the Library of Congress Cataloging
Rules.
modifications, updates and revisions to the AACR2 Rev.
modifications, updates and revisions to the LC Rule Interpretations.
modifications, updates and revisions to the Cooperative Online Serials
(CONSER).
modifications, updates and revisions to the CONSER Access Level Record
Guidelines.
modifications, updates and revisions to the Cataloging Guidelines.
modifications, updates and revisions to the Superintendent of Documents
Classification Manual.
modifications, updates and revisions to the Library of Congress Subject
Headings.
modifications, updates and revisions to the NASA Subject Headings.
modifications, updates and revisions to the MESH Subject Headings.
modifications, updates and revisions to all MARC Formats.
modifications, updates and revisions to the other GPO specified standards
and best practices.
The system shall be compliant with the following NISO and ISO standards:
Z39.2 - Information Interchange Format, Z39.9 - International Standard Serial
Numbering-ISSN, Z39.29 - Bibliographic References, Z39.43 -Standard
Address Number (SAN) for the Publishing Industry, Z39.50 -Information
Retrieval: Application Service Definition & Protocol Specification, Z39.56 Serial Item and Contribution Identifier (SICI), Z39.69 - Record Format for
Patron Records, Z39.71 - Holding Statements for Bibliographic Items, Z39.85
- Dublin Core Metadata Element Set.
The system shall be compliant with the following NISO and ISO standards:
Z39.2 - Information Interchange Format, Z39.9 - International Standard Serial
Numbering-ISSN, Z39.29 - Bibliographic References, Z39.43 -Standard
Address Number (SAN) for the Publishing Industry, Z39.50 -Information
R2; Must
R2; Must
R2; Must
R2; Must
R2; Must
R2; Must
R2; Must
R2; Must
R1C; Must
R1C; Must
R1C; Must
R1C; Must
R1C; Must
R1C; Must
R1C; Must
R1C; Must
R1C; Must
R1C; Must
R1C; Must
R1C; Must
R1C; Must
R1C; Must
R1C; Must
R2; Must
R2; Must
95

FINAL
Retrieval: Application Service Definition & Protocol Specification, Z39.56 Serial Item and Contribution Identifier (SICI), Z39.69 - Record Format for
Patron Records, Z39.71 - Holding Statements for Bibliographic Items, Z39.85
- Dublin Core Metadata Element Set.
RD-2954
RD-2955
30
30.1
30 Requirements for User Interface

30.1 User Interface Core Capabilities
RD-2956
30.1.0-1
RD-2957
30.1.0-2
RD-2959
30.1.0-2.0-2
RD-2960
30.1.0-2.0-3
RD-2961
30.1.0-2.0-4
RD-2962
30.1.0-2.0-4.0-1
RD-2963
RD-2964
RD-2965
30.1.0-2.0-5
30.1.0-2.0-5.0-1
30.1.0-2.0-6
RD-2966
30.1.0-2.0-7
RD-2967
30.1.0-3
RD-2968
RD-2969
RD-2970
30.1.0-3.0-1
30.1.0-4
30.1.0-5
RD-2972
30.1.0-7
RD-2973
RD-2974
RD-2975
30.1.0-8
30.1.0-9
30.1.0-10
RD-2976
30.1.0-11
RD-2977
30.1.0-11.0-1
RD-2978
30.1.0-11.0-2
RD-2979
30.1.0-12
RD-2980
30.1.0-13
RD-2981
RD-2982
RD-2983
30.1.0-13.0-1
30.1.0-13.0-2
30.1.0-13.0-3
RD-2984
30.1.0-13.0-4
RD-2985
30.1.0-13.0-5
The system shall provide a default Graphical User Interface (GUI) for each
functional element as required in accordance with the system release
schedule.
The system shall provide a default workbench for each user class as required
in accordance with the system release schedule.
The system shall provide the capability for GPO to create workbenches for
subsets of user classes.
The system shall provide the capability for GPO to manage the toolsets that
are available on default workbenches.
The system shall provide a default public End User workbench that allows
users to access the system without registering.
The system shall allow all user to perform the actions allowed to unregistered
users.
Public End User GUIs shall be section 508 compliant.
Content Originator GUIs shall be section 508 compliant.
The system shall provide a default Service Specialist workbench that provides
the capability for Service Specialists to handle exception processing.
The system shall provide the capability for GPO to designate if users are
required to register with the system to access certain internal default
workbenches such as the default workbench for the System Administrator
user class.
The system shall provide the capability to maintain a consistent look and feel
throughout workbenches and GUIs to the extent possible.
GUIs shall conform to GPO design guidelines.
The system shall support web-based GUIs.
The system shall support non web-based GUIs, as necessary.
The system shall provide for non-English language extensibility such that
GUIs could contain non-English language text.
The system shall provide GUIs that accept input of information by users.
The system shall provide GUIs that accept submission of content by users.
The system shall provide GUIs that allow users to input and submit
registration information and login to the system.
The system shall only display GUI functionality appropriate to the user and the
actions the user is taking.
The system shall have the capability to assign access to system functionality
based on a user role.
The system shall have the capability to assign access to system functionality
based on user security settings.
The system shall provide the capability to integrate search tools, cataloging
and reference tools, request tools, and user support tools seamlessly into an
End User interface.
The system shall provide GUIs that can be displayed on Macintosh, Linux,
and Windows environments.
The system shall provide R1B GUIs that are displayable in Firefox 1.5.x.
The system shall provide R1B GUIs that are displayable in IE 6.x.
The system shall provide R1C GUIs that are fully functional in Mozilla Firefox
1.5.x.
The system shall provide R1C GUIs that are fully functional in Microsoft
Internet Explorer 6.x.
The system shall provide R1C GUIs that are fully functional in Mozilla Firefox
2.0.x.
R1B; Must
R1B; Must
R2; Must
R1C; Must
R1B; Must
R1B; Must
R1C; Must
R1C; Must
R1B; Must
R1B; Must
R1C; Must
R1C; Must
R1B; Must
R1B;
Should
R1C; Could
/ R2; Must
R1B; Must
R1B; Must
R1B; Must
R1B; Must
R1B; Must
R1B; Must
R1B; Must
R1B; Must
R1B; Must
R1B; Must
R1C; Must
R1C; Must
R1C; Must
96

FINAL
RD-2986
30.1.0-13.0-6
RD-2987
30.1.0-13.0-7
RD-2988
30.1.0-13.0-8
The system shall provide R1C GUIs that are fully functional in Microsoft
Internet Explorer 7.x.
The system shall provide R1C GUIs that are fully functional in Netscape
Navigator 7.x.
The system shall provide R1C GUIs that are fully functional in Safari 1.x.
RD-2989
30.1.0-13.0-9
The system shall provide R1C GUIs that are fully functional in Konqueror 2.x.
RD-2990
30.1.0-13.0-10
RD-2991
RD-2992
30.1.0-13.0-11
30.1.0-14
RD-2993
30.1.0-15
RD-2994
30.1.0-16
RD-2995
30.1.0-17
The system shall provide Web pages that are designed based on Web
standards.
The system shall provide static Web pages that are designed using templates.
The system shall provide GUIs that are capable of providing feedback, alerts,
or notices to users.
The system shall provide GUIs that are capable of providing context specific
help and user support.
The system shall provide GUIs that allow users to browse content by
collection.
The system shall provide GUIs that allow users to drill-down into collections.
RD-2996
30.2
R1C;
Should
R1C;
Should
R1C;
Should
R1C;
Should
R1C; Must
R1C; Must
R1B; Must
R1B; Must
R1C; Must
R1C; Must
30.2 User Interface Standards and Best

Practices
RD-2997
30.2.0-1
RD-2998
30.2.0-1.0-1
RD-2999
30.2.0-1.0-2
RD-3000
30.2.0-2
RD-3001
RD-3002
RD-3003
RD-3004
RD-3005
RD-3006
RD-3007
RD-3008
30.2.0-2.0-1
30.2.0-2.0-2
30.2.0-2.0-3
30.2.0-2.0-3.0-1
30.2.0-2.0-3.0-2
30.2.0-2.0-4
30.2.0-2.0-5
30.2.0-2.0-6
RD-3009
RD-3010
RD-3011
30.2.0-2.0-7
30.2.0-2.0-8
30.2.0-2.0-9
RD-3012
30.3
The system shall comply with best practices and guidelines regarding usability
for graphical user interface design.
GUIs shall be developed in accordance with the Research Based Web Design
& Usability Guidelines, 2006 edition.
nd
Web GUIs shall be developed in accordance with the Web Style Guide, 2
edition.
Where the system uses the following technologies for interoperability it will
use the stated standards as follows:
The system shall conform to Extensible Markup Language (XML).
The system shall conform to Extensible Style sheet Language (XSL).
The system shall conform to Document Type Definition (DTD) and schema.
The system shall conform to Document Type Definition (DTD).
The system shall conform to schema.
The system shall conform to XSL Transformations (XSLT).
The system shall conform to XML Path Language (Xpath).
The system shall conform to Extensible HyperText Markup Language
(XHTML).
The system shall conform to Cascading Style Sheets (CSS).
The system shall conform to DHTML.
The system shall conform to WML.
R1B;
Should
R1B;
Should
R1B;
Should
R1B; Must
R1B; Must
R1B; Must
R1B; Must
R1B; Must
R1B; Must
R1B; Must
R1B; Must
R1B; Must
R1B; Must
R1B; Must
R2; Must
30.3 User Interface Customization and

Personalization
RD-3013
30.3.0-1
The system shall provide the capability for authorized users who have
registered with the system to customize GUIs.
RD-3014
30.3.0-1.0-1
The system shall provide the capability to add tools.
RD-3015
30.3.0-1.0-2
The system shall provide the capability to remove tools.
RD-3016
30.3.0-1.0-3
The system shall provide the capability to hide tools.
RD-3017
30.3.0-1.0-4
The system shall provide the capability to modify the placement of tools.
R1C;
Should /
R2; Must
R1C;
Should /
R2; Must
R1C;
Should /
R2; Must
R1C;
Should /
R2; Must
R1C;
Should /
97

FINAL
RD-3018
30.3.0-1.0-5
The system shall provide the capability to modify the size of tools.
RD-3019
30.3.0-1.0-6
The system shall provide the capability to select text size from available
options.
RD-3020
30.3.0-1.0-7
The system shall provide the capability to select color scheme from available
options.
RD-3021
30.3.0-2
RD-3022
30.3.0-3
RD-3023
30.3.0-4
The system shall provide the capability to provide personalized GUIs and
workbenches to users that have registered with the system.
The system shall provide the capability to provide personalized GUIs and
workbenches that are created from user histories as analyzed through data
mining.
The system shall provide the capability for users to revert to their original
default GUIs and workbenches.
RD-3024
30.3.0-5
RD-3025
30.4
RD-3026
30.4.0-1
RD-3027
30.4.0-2
RD-3028
30.4.0-3
RD-3029
30.4.0-4
RD-3030
30.4.0-5
RD-3031
30.4.0-6
RD-3032
30.4.0-7
RD-3033
30.4.0-8
RD-3042
30.4.0-17
RD-3043
RD-3044
31
31.1
The system shall provide the capability to maintain interface configurations

across user sessions.
R2; Must
R1C;
Should /
R2; Must
R1C;
Should /
R2; Must
R1C;
Should /
R2; Must
R1C; Could
/ R2; Must
R1C; Could
/ R2; Must
R1C;
Should /
R2; Must
R1C;
Should /
R2; Must
30.4 User Interface Default Workbenches

The system shall provide the capability to configure workbenches according to
criticality and release schedules specified in individual requirements.
The system must provide a workbench for Content Originators that is based
on their user role.
The system must provide a workbench for GPO Content Evaluators that is
based on their user role.
The system must provide a default interface for GPO Service Specialists that
is based on their user role.
The system must provide a workbench for Service Providers (e.g., GPO
Service Providers and External Service Providers) that is based on their user
role.
The system must provide a workbench for End Users (e.g., Public End Users,
Library End Users, Small Business End Users, Congressional End Users,
Agency End Users, Information Industry End Users) that is based on their
user role.
The system must provide a workbench for GPO Business Managers that is
The system shall provide a default interface for System Administrators that is
The system shall provide a default interface for Operations Managers that is
R2; Must
R2; Must
R1B; Must
R1B; Must
R1B; Must
R1B; Must
R1C; Could
/ R2; Must
R1B; Must
R1B; Must
31 Requirements for User Support

31.1 User Support Core Capabilities
RD-3045
RD-3046
31.1.0-1
31.1.0-1.0-1
RD-3047
31.1.0-1.0-1.0-1
RD-3048
31.1.0-1.0-1.0-2
RD-3049
31.1.0-1.0-1.0-3
The system shall provide multiple methods of contact for user assistance.
The system shall provide multiple methods for users to contact authorized
users for user assistance.
The system shall provide web form for users to contact authorized users for
user assistance.
The system shall provide phone numbers for users to contact authorized
users for user assistance based on their user profile and the function they are
performing.
The system shall provide e-mail addresses for users to contact authorized
R2; Must
R2; Must
R1C; Must
R2; Could
R2; Must
98

FINAL
RD-3050
31.1.0-1.0-1.0-4
RD-3051
31.1.0-1.0-1.0-5
RD-3052
31.1.0-1.0-1.0-6
RD-3053
31.1.0-1.0-1.0-7
RD-3054
31.1.0-1.0-1.0-8
RD-3055
31.1.0-1.0-2
RD-3056
31.1.0-1.0-2.0-1
RD-3057
31.1.0-1.0-2.0-2
RD-3058
31.1.0-1.0-2.0-3
RD-3059
31.1.0-1.0-2.0-4
RD-3060
31.1.0-1.0-2.0-5
RD-3061
31.1.0-2
RD-3062
31.1.0-2.0-1
RD-3063
31.1.0-2.0-2
RD-3064
31.1.0-2.0-2.0-1
RD-3065
31.1.0-2.0-2.0-2
RD-3066
31.1.0-2.0-2.0-3
RD-3067
31.1.0-2.0-2.0-4
RD-3068
31.2
performing.
The system shall provide mailing addresses for users to contact authorized
performing.
The system shall provide real-time text chat for users to contact GPO Service
Specialists for user assistance.
The system shall provide Facsimile numbers for users to contact authorized
performing.
The system shall provide desktop facsimile for users to contact authorized
The system shall provide users with information on how to contact GPO for
assistance.
The system shall provide multiple methods for authorized users to contact
The system shall provide phone numbers for authorized users to contact
The system shall provide e-mail addresses for GPO Service Specialists to
contact users for user assistance.
The system shall provide real-time text chat for authorized users to contact
The system shall provide facsimile numbers for authorized users to contact
The system shall provide desktop facsimile for GPO Service Specialists to
contact users for user assistance.
The system shall provide users with the ability to opt-out of user support
features.
The system shall provide users with the ability to enable or disable context
specific help that consists of customizable descriptive text displayed when a
user points the mouse over an item on the user interface.
The system shall provide users with the ability to enable or disable context
specific help that consists of clickable help icons or text on the user interface.
The system shall have the capability to provide for address hygiene utilizing
CASS certified and National Change of Address certified software to minimize
delivery risks.
The system shall have the capability for Computer Telephone Integration
(CTI) with auto screen pop-ups to integrate the agencys telephone and order
management systems.
The system shall have the capability to integrate with GPOs Automated Call
Dialer (ACD) system to allow for automatic consumer telephone access to
account and transaction data.
The system shall have the capability to process e-mail marketing campaigns
R2; Could
R2; Could
R2; Could
R2; Could
R1C; Must
R2; Could
R2; Could
R2; Must
R2; Could
R2; Could
R2; Could
R1C; Must
R1C; Must
R1C; Must
R2; Could
R2; Could
R2; Could
R2; Could
31.2 User Support Context Specific

Help
RD-3069
31.2.0-1
The system shall provide context-specific help on user interfaces.
RD-3070
31.2.0-1.0-1
RD-3072
31.2.0-1.0-3
Content of context specific help shall be related to what is being viewed on the
screen and shall be dynamically generated.
Context specific help shall consist of help menus.
RD-3073
31.2.0-1.0-3.0-1
RD-3074
31.2.0-1.0-3.0-2
RD-3075
31.2.0-1.0-3.0-3
RD-3076
31.2.0-1.0-3.0-4
Help menus shall contain user support information related to what is on the
current user interface.
Help menus shall provide access to all available user support information for
the entire system.
Authorized uses shall have the ability to manage information (text, images,
audio, video, multimedia) in the help menu.
All users shall have the ability to search the help menu.
RD-3077
31.2.0-1.0-3.0-5
The system shall return search results to the user.
RD-3078
31.2.0-1.0-3.0-6
All users shall have the ability to navigate the help menu using an index.
R1B; Could
/ R1C; Must
R2; Could /
R3; Must
R1B; Could
/ R1C; Must
R1B; Could
/ R1C; Must
R1B; Could
/ R1C; Must
R1B; Could
/ R1C; Must
R1B; Could
/ R1C; Must
R1B; Could
/ R1C; Must
R1B; Could
99

FINAL
RD-3079
31.2.0-1.0-4
RD-3080
31.2.0-1.0-4.0-1
RD-3081
31.2.0-1.0-5
RD-3082
31.2.0-1.0-5.0-1
RD-3083
31.2.0-1.0-5.0-2
RD-3084
31.2.0-1.0-5.0-3
RD-3085
31.2.0-1.0-5.0-4
RD-3086
31.2.0-1.0-5.0-5
RD-3087
31.3
Context specific help shall consist of customizable descriptive text displayed

when a user points the mouse over an item on the user interface.
Authorized users shall have the ability to manage customizable descriptive
text.
Context specific help shall consist of clickable help icons or text on the user
interface.
All users shall have the ability to click on help icons or text.
Upon clicking on help icons or text, the system shall display text, images,
audio, video or multimedia components.
Authorized users shall have the ability to manage information (text, images,
audio, video, multimedia) displayed as a result of clicking on help icons or
text.
Authorized users shall have the ability to place help icons or text where
needed on the user interface.
All users shall have the ability to view information displayed by clickable help
icons.
/ R1C; Must
R1B; Could
/ R1C; Must
R1B; Could
/ R1C; Must
R1B; Could
/ R1C; Must
R1B; Could
/ R1C; Must
R1B; Could
/ R1C; Must
R1C; Could
/ R2; Must
R1C; Could
/ R2; Must
R1B; Could
/ R1C; Must
31.3 User Support Helpdesk

RD-3088
31.3.0-1
RD-3089
31.3.0-2
RD-3090
31.3.0-2.0-1
RD-3091
31.3.0-2.0-2
RD-3092
31.3.0-3
RD-3093
31.3.0-3.0-1
RD-3094
31.3.0-4
RD-3095
31.3.0-4.0-1
RD-3096
31.3.0-4.0-2
RD-3097
31.3.0-5
RD-3098
31.3.0-6
RD-3099
31.3.0-7
RD-3100
31.3.0-8
RD-3101
31.3.0-9
RD-3102
31.3.0-9.0-1
RD-3103
31.3.0-9.0-2
RD-3104
31.3.0-9.0-3
RD-3105
31.3.0-9.0-4
RD-3106
31.3.0-9.0-5
RD-3107
31.3.0-9.0-6
The system shall have the capability to support a helpdesk to route, track,
prioritize, and resolve user inquiries to authorized users.
Information collected and maintained shall comply with GPO and Federal
privacy policies.
Information collected and maintained shall comply with Records maintained
on individuals, Title 5 U.S. Code Sec. 552a, 2000 edition.
Information collected and maintained shall comply with H.R. 2458, EGovernment Act of 2002.
The system shall have the capability to receive inquiries from registered and
non-registered users.
The system shall have the capability to maintain user identification for
inquiries and responses after a user no longer has a registered account in the
system.
Users shall have the capability to select from lists of categories when
submitting inquiries.
Users shall have the capability to select from subgroups of categories when
submitting inquiries.
Authorized users shall have the capability to manage categories and
subcategories.
A user shall have the capability to attach files when submitting inquiries.
The system shall have the capability to notify users that their inquiry has been
received.
The system shall have the capability to time and date stamp all inquiries and
responses.
The system shall have the capability to notify a user that they have been
assigned an inquiry.
The system shall have the capability to route, track, and prioritize inquiries
and responses received.
The helpdesk shall have the capability to support multiple departments and
additional future departments, when needed.
The helpdesk and knowledge base shall have the capability to synchronize
with data entered into the system while not connected to the internet.
The helpdesk shall have the capability to integrate with user account
information and additional sources of business process information stored
outside of the helpdesk. (e.g., Oracle, user accounts in Storage/Access)
Other systems/functional elements shall have the capability to access
information stored in the helpdesk.
The helpdesk shall have the capability to access information stored in other
systems/functional elements.
The system shall allow users to specify job numbers (e.g., CO Ordering
numbers, Request Ordering numbers) and other identifiers (e.g., voucher
R2; Must
R1C; Must
R1C; Must
R1C; Must
R2; Must
R2; Must
R1C; Could
/ R2; Must
R1C; Could
/ R2; Must
R1C; Could
/ R2; Must
R1C; Could
/ R2; Must
R1C; Could
/ R2; Must
R1C; Could
/ R2; Must
R1C; Could
/ R2; Must
R2; Must
R2; Must
R2; Must
R2; Must
R2; Must
R2; Must
R2; Must
100

FINAL
RD-3108
31.3.0-9.0-7
RD-3109
31.3.0-9.0-8
RD-3110
31.3.0-9.0-9
RD-3111
31.3.0-9.0-10
RD-3112
31.3.0-9.0-11
RD-3113
31.3.0-10
RD-3114
31.3.0-11
numbers, ISBN numbers) in inquiry fields.

The system shall allow users to select from various templates for submission
of inquiries. (e.g., complaint template for CO Order, template for phone
conversation, template for contract modification request)
The system shall assign unique identifiers based on the type of template
used. (e.g., to track complaints, modification requests)
The system shall allow authorized GPO users to manage templates for
submission of inquiries.
The system shall have the capability for role based access to individual fields
on individual helpdesk inquiries and responses. (e.g., Notes field with access
to GPO employees only)
The system shall have the capability to display all inquiries and responses
related to a particular job number (e.g., Request order number, CO Order
number) or other unique identifier. (e.g., voucher numbers, ISBN numbers)
The system shall allow authorized users to manually create a new inquiry in
order to accommodate inquiries that do not enter the system electronically.
The system shall provide the capability to queue inquiries.
RD-3115
31.3.0-12
The system shall support priority processing.
RD-3116
31.3.0-13
RD-3117
31.3.0-14
RD-3118
31.3.0-15
RD-3119
31.3.0-15.0-1
RD-3120
31.3.0-15.0-2
RD-3121
31.3.0-15.0-3
The system shall allow authorized users to manage the status categories for
inquires.
The system shall provide the capability for authorized users to restrict access
to inquiry tracking.
The system shall provide automated routing of inquiries to the
departments/individuals according to workflow guidelines, including the
following.
Automated inquiry routing shall be based on selections made by the user
when an inquiry is made.
Automated inquiry routing shall be based on keywords in the inquiry sent by
the user.
Automated inquiry routing shall be based on the user class of the inquirer.
RD-3123
31.3.0-16
RD-3124
31.3.0-16.0-1
RD-3125
31.3.0-16.0-2
RD-3126
31.3.0-16.0-3
RD-3127
31.3.0-17
RD-3128
31.3.0-17.0-1
RD-3129
RD-3130
31.3.0-17.0-2
31.3.0-18
RD-3131
31.3.0-19
RD-3132
RD-3133
31.3.0-20
31.3.0-21
RD-3134
31.3.0-22
RD-3135
RD-3136
31.3.0-23
31.3.0-24
RD-3137
31.3.0-25
RD-3138
31.3.0-25.0-1
RD-3139
31.3.0-25.0-2
Authorized users shall have the capability to route inquiries to other

authorized users.
Authorized users shall have the ability to route an inquiry to a selected
individual.
Authorized users shall have the ability to route an inquiry to a selected
department.
Authorized users shall have the ability to route inquiries to users who do not
have access to the system using e-mail.
The system shall allow the user to determine the departments or individuals
they wish to request answers from.
The system shall allow the user to determine the departments they wish to
request answers from.
The system shall allow the user individuals they wish to request answers from.
The system shall provide the capability to request user feedback regarding
quality of response given.
The system shall provide users with access to history of their inquiries and
responses.
The system shall store inquiries and responses.
The system shall have the capability to allow authorized users to amend
inquiries and responses.
The system shall have the capability for users to search inquiries and
responses.
The system shall allow authorized users to search for inquiries by any field.
The system shall support the capability to monitor the quality of responses
given by helpdesk staff.
The system shall have the capability to provide users with access to inquiries
from other users related to their queries.
The system shall allow for search of inquiries from other users.
The system shall provide the capability to assign user access rights to
individual questions and answers.
R2; Must
R2; Must
R2; Must
R2; Must
R2; Must
R2; Must
R1C; Could
/ R2; Must
R1C; Could
/ R2; Must
R1C; Could
/ R2; Must
R2; Must
R1C; Could
/ R2; Must
R1C; Could
/ R2; Must
R1C; Could
/ R2; Must
R1C; Could
/ R2; Must
R1C; Could
/ R2; Must
R1C; Could
/ R2; Must
R1C; Could
/ R2; Must
R1C; Could
/ R2; Must
R1C; Could
/ R2; Must
R2; Must
R2; Must
R1C; Could
/ R2; Must
R1C; Could
/ R2; Must
R2; Must
R1C; Could
/ R2; Must
R2; Must
R2; Must
R1C;
Could; / R2;
Must
R1C; Could
/ R2; Must
R1C; Could
/ R2; Must
R1C; Could
/ R2; Must
101

FINAL
RD-3140
31.3.0-26
RD-3141
RD-3142
31.3.0-27
31.3.0-27.0-1
RD-3143
31.3.0-28
RD-3144
31.4
The system shall provide the capability to record users responding to

inquiries.
The system shall provide the capability to log information exchanges.
Information exchange logs shall store metadata relating to what is being
discussed.
The system shall provide the capability to spell-check inquiries and responses
before submission.
R2; Must
R2; Must
R2; Must
R1B; Could
/ R2; Must
31.4 User Support Knowledge Base

RD-3145
31.4.0-1
RD-3146
31.4.0-2
RD-3147
31.4.0-3
RD-3148
31.4.0-3.0-1
RD-3149
31.4.0-4
RD-3150
31.4.0-5
RD-3151
31.4.0-6
RD-3152
31.4.0-6.0-1
RD-3153
31.4.0-6.0-2
RD-3154
31.4.0-7
RD-3155
31.4.0-8
RD-3156
31.4.0-9
RD-3157
31.4.0-9.0-1
RD-3158
31.4.0-9.0-2
RD-3159
RD-3160
31.4.0-9.0-2.0-1
31.4.0-9.0-2.0-2
RD-3161
31.4.0-9.0-2.0-3
RD-3162
31.4.0-9.0-2.0-4
RD-3163
RD-3164
RD-3165
31.4.0-9.0-2.0-5
31.4.0-9.0-2.0-6
31.4.0-9.0-2.0-7
RD-3166
31.4.0-10
RD-3167
31.4.0-10.0-1
RD-3168
31.4.0-10.0-2
RD-3169
31.4.0-10.0-3
RD-3170
31.4.0-11
RD-3171
RD-3172
RD-3173
31.4.0-11.0-1
31.4.0-11.0-2
31.4.0-11.0-3
The system shall allow authorized users to add information to a knowledge

base.
The system shall provide the ability for an authorized user to add electronic
files to the knowledge base as attachments.
The system shall provide the capability to create customized templates for
knowledge base entries.
The system shall provide the capability for authorized users to choose from a
list of templates when creating knowledge base entries.
The system shall have the capability to time and date stamp all knowledge
base entries.
The system shall provide the ability for authorized users to manage
information in the knowledge base.
The system shall provide the capability to add inquiries and answers from the
helpdesk to the knowledge base.
The system shall allow authorized users to edit and approve inquiries and
responses for addition to the knowledge base.
The system shall have the capability for GPO users to recommend helpdesk
inquiries and responses for the knowledge base.
The system shall provide the ability for authorized users to create categories
and subcategories for information stored in the knowledge base.
The system shall provide the capability to store standard responses for use by
specific user groups or subgroups.
The system shall allow for information stored in the knowledge base to have
role-based access restrictions.
The system shall allow for access restrictions to be applied to complete
categories.
The system shall allow for access restrictions to be applied to individual
knowledge base entries.
The system shall allow users to assign key words to knowledge base entries.
The system shall allow for fields (e.g., subject, title) with an unlimited number
of characters.
The system shall have the capability for role based access to individual fields
on individual knowledge base entries. (e.g., notes field with access to certain
GPO employees only)
The system shall have the capability for intelligent searching of knowledge
base. (e.g., when searching, system asks, did you mean xxx?)
The system shall have the capability to search by title.
The system shall have the capability to search by unique identifiers.
The system shall provide the capability to store standard responses for
knowledge base entries for use by specific user groups or subgroups.
The system shall provide the capability for all users to search the knowledge
base.
The system shall provide the capability for all users to perform a full-text
search the knowledge base.
base by phrase.
base by identification number.
The system shall provide the capability to sort results of knowledge base
searches.
The system shall provide the capability to sort search results by category.
The system shall provide the capability to sort search results by subject.
The system shall provide the capability to sort search results by a default sort.
R2; Must
R2; Must
R2; Could
R2; Could
R2; Must
R2; Must
R2; Must
R2; Must
R2; Must
R2; Must
R1C; Could
/ R2; Must
R2; Must
R2; Must
R2; Must
R2; Must
R2; Must
R2; Must
R2; Must
R2; Must
R2; Must
R2; Must
R2; Must
R2; Must
R2; Must
R2; Must
R2; Must
R2; Must
R2; Must
R2; Must
102

FINAL
RD-3174
31.4.0-12
The system shall provide the capability for a user to receive e-mail updates
when the content of information stored in a knowledge base entry is updated.
functions on knowledge base data.
The system shall provide the capability to spell-check knowledge base entries
before submission.
RD-3175
31.4.0-13
RD-3176
31.4.0-14
RD-3177
31.5
RD-3178
RD-3179
31.5.0-1
31.5.0-1.0-1
The system shall have the capability to provide alert services.

The system shall allow all users to subscribe and unsubscribe to alert services
RD-3180
31.5.0-1.0-2
Alert services shall be provided via the following channels.
RD-3181
RD-3182
RD-3183
RD-3184
31.5.0-1.0-2.0-1
31.5.0-1.0-2.0-2
31.5.0-1.0-2.0-3
31.5.0-1.0-3
RD-3185
31.5.0-1.0-4
E-mail messages
RSS Feeds conforming to the RSS 2.0 Specification.
Messages while logged into Fdsys
The system shall allow users to chose the method an alert is delivered in from
a list of available options.
The system shall provide alerts based on user profiles and history.
RD-3186
31.5.0-1.0-5
RD-3187
31.5.0-1.0-6
RD-3188
31.5.0-1.0-7
RD-3189
31.5.0-1.0-8
RD-3190
31.5.0-1.0-9
RD-3191
31.5.0-1.0-10
RD-3192
31.6
R1B; Could
/ R2; Must
R2; Must
R2; Must
31.5 User Support Alerts
The system shall have the capability to automatically send alerts based on
system events.
The system shall have the capability to automatically send alerts based on
business events (e.g., new version of publication available, new services
available).
The system shall have the capability to automatically send notifications to
users based on job processing events.
Authorized users shall be able to create new alert categories where new alerts
are manually generated.
The system shall have the capability to populate the knowledge base with
alerts.
The system shall provide the capability for users to add alerts to the
knowledge base.
R1B; Must
R1B; Could
/ R1C; Must
R1B; Could
/ R1C; Must
R1C; Must
R1C; Must
R1C; Must
R1B; Could
/ R1C; Must
R1C; Could
/ R2; Must
R1B; Could
/ R1C; Must
R1B; Could
/ R1C; Must
R1C; Must
R1B; Could
/ R1C; Must
R1C; Could
/ R2; Must
R1C; Could
/ R2; Must
31.6 User Support Training and Events

RD-3193
31.6.0-1
RD-3194
31.6.0-1.0-1
RD-3195
31.6.0-1.0-2
RD-3196
31.6.0-1.0-3
RD-3197
31.6.0-1.0-4
RD-3198
31.6.0-1.0-5
RD-3199
31.6.0-2
RD-3200
31.6.0-3
RD-3201
RD-3202
RD-3203
RD-3204
RD-3205
RD-3206
RD-3207
RD-3208
31.6.0-3.0-1
31.6.0-3.0-2
31.6.0-4
31.6.0-5
31.6.0-6
31.6.0-6.0-1
31.6.0-6.0-2
31.6.0-7
The system shall provide users access to training materials and training
history.
The system shall provide access to training materials available as digital
video.
documents.
audio.
multimedia.
The system shall provide access to training materials available in other
formats.
The system shall allow authorized users to manage training materials and
training history.
The system shall have the capability for authorized users to restrict access to
training material and training history.
Access restrictions to training materials shall be based on user class.
Access restrictions to training materials shall be based on individual users.
The system shall allow users to enroll in training and events.
The system shall allow authorized users to manage training and events.
The system shall provide interactive training.
The system shall provide interactive self-paced training.
The system shall provide interactive instructor-led training.
The system shall provide users verification of enrollment in training and
events.
R2; Could
R2; Could
R2; Could
R2; Could
R2; Could
R2; Could
R2; Could
R2; Could
R2; Could
R2; Could
R2; Could
R2; Could
R2; Could
R2; Could
R2; Could
R2; Could
103

FINAL
RD-3209
31.6.0-8
RD-3210
31.6.0-9
RD-3211
31.6.0-9.0-1
RD-3212
31.7
The system shall provide the capability for users to measure their progress
and performance.
The system shall provide the capability for users to provide feedback on
training.
The system shall provide online tutorials.
R2; Could
R2; Could
R2; Could
31.7 Contact Management

RD-3213
31.7.0-1
RD-3214
31.7.0-2
RD-3215
31.7.0-3
RD-3216
31.7.0-4
RD-3217
31.7.0-5
RD-3218
31.7.0-6
RD-3219
31.7.0-7
RD-3220
RD-3221
RD-3222
RD-3223
31.7.0-8
31.7.0-9
31.7.0-10
31.7.0-11
RD-3224
31.7.0-12
RD-3225
31.7.0-13
RD-3226
31.7.0-14
RD-3227
RD-3228
31.7.0-15
31.7.0-16
RD-3229
RD-3230
31.7.0-17
31.7.0-18
RD-3231
RD-3232
31.7.0-19
31.7.0-20
RD-3233
31.7.0-21
RD-3234
31.7.0-22
RD-3235
31.7.0-23
RD-3236
31.7.0-24
RD-3237
31.7.0-25
RD-3238
31.7.0-26
RD-3239
31.7.0-27
RD-3240
31.7.0-28
RD-3241
RD-3242
RD-3243
RD-3244
RD-3245
31.7.0-29
31.7.0-30
31.7.0-31
31.7.0-32
31.7.0-33
The system shall enable GPO users to view and manage contact data while
not connected to the internet or internal server.
The system shall have the capability to synchronize data managed offline with
the contact database when reconnected.
The system shall enable GPO users to track contact data (e.g., name,
company, address, phone, e-mail, last meeting date, and status).
The system shall enable GPO users to create customizable fields for contact
data (e.g., billing address code, GPO Express Customer).
The system shall enable GPO users to manage notes, history, sales, and
attached files to each contact record.
The system shall allow each contact to have an owner associated with the
contact record.
The system shall enable GPO users to manage groups of related contact
records (e.g., all contacts at a single agency).
The system shall enable GPO users to hierarchically group contact records.
The system shall enable GPO users to track sales opportunities.
The system shall enable GPO users to generate sales opportunities reports.
The system shall have the capability to integrate with GPOs e-mail client
(e.g., Microsoft Outlook).
The system shall have the capability to integrate with handheld devices used
by GPO employees (e.g., Blackberry devices).
The system shall have a calendar which synchronizes with GPOs e-mail
client calendar.
The system shall enable GPO users to schedule calls, meetings and tasks
associated with each contact record.
The system shall enable users to prioritize tasks.
The system shall enable GPO users to generate mail merges using
information stored in contact records.
The system shall enable GPO users to search records with any field.
The system shall enable GPO users to search for empty fields or non-empty
fields.
The system shall enable GPO users to generate reports.
The system shall enable GPO users to create customized report
templates/layouts.
The system shall allow users to record and store meeting minutes with
internal and external contacts.
The system shall allow users to associate multiple internal and external
contacts with the meeting minutes.
The system shall allow users to associate meeting minutes with a list of
hierarchical categories.
The system shall allow users to record the date, time, location and subject of
the meeting.
The system shall allow users to record the content of the meeting using an
unlimited number of characters.
The system shall allow users to create reports with details of all meeting
minutes.
The system shall allow users to filter the data for the report by contact,
department, and category.
The system shall allow users to create reports including the following
elements:
Meeting subject
List of all contacts associated with the meeting
Date, time and location of meeting
Full meeting minutes
List of all categories associated with the meeting
R2; Must
R2; Must
R2; Must
R2; Must
R2; Must
R2; Must
R2; Must
R2; Must
R2; Must
R2; Must
R2; Must
R2; Must
R2; Must
R2; Must
R2; Must
R2; Must
R2; Must
R2; Must
R2; Must
R2; Must
R2; Could
R2; Could
R2; Could
R2; Could
R2; Could
R2; Could
R2; Could
R2; Could
R2; Could
R2; Could
R2; Could
R2; Could
R2; Could
104

FINAL
RD-3246
RD-3247
32
32.1
RD-3248
32.1.0-1
RD-3249
32.1.0-2
RD-3250
32.1.0-3
RD-3251
32.1.0-4
RD-3252
RD-3253
32.1.0-4.0-1
32.1.0-4.0-2
RD-3254
32.1.0-5
RD-3255
32.1.0-5.0-1
RD-3256
32.1.0-5.0-2
RD-3257
32.1.0-5.0-3
RD-3258
32.1.0-5.0-4
RD-3259
32.1.0-5.0-5
RD-3260
32.1.0-5.0-6
RD-3261
32.1.0-6
RD-3262
32.1.0-6.0-1
RD-3263
32.1.0-6.0-2
RD-3264
RD-3265
32.1.0-7
32.1.0-7.0-1
RD-3266
32.1.0-7.0-2
RD-3267
32.1.0-7.0-3
RD-3268
32.1.0-7.0-4
RD-3269
32.1.0-7.0-5
RD-3270
32.1.0-8
RD-3271
32.1.0-9
RD-3272
32.1.0-9.0-1
RD-3273
32.1.0-9.0-2

Delivery and Processing
32.1 Content Delivery Core Capabilities
The system shall have the capability to retrieve ACPs from Access Content
Storage based on user request.
The system shall have the capability to create DIPs from ACPs in delivery
processing based upon a user request.
The system shall have the capability to create pre-ingest bundles in delivery
processing.
The system shall have the capability to deliver DIPs and pre-ingest bundles
based on user requests.
The system shall have the capability to deliver DIPs based on user requests.
The system shall have the capability to deliver pre-ingest bundles based on
user requests.
Users shall have the ability to pull DIPs and pre-ingest bundles from the
system.
The system shall provide the capability for a user to request the download of a
DIP from the system.
The system shall provide the capability for a user to perform an FTP get on a
DIP from the system.
The system shall support the capability for a user to pull a DIP from the
system using additional methods in the future.
The system shall provide the capability for a user to request the download of a
PIB from the system.
The system shall provide the capability for a user to perform an FTP get on a
PIB from the system.
The system shall support the capability for a user to pull a PIB from the
system using additional methods in the future.
The system shall have the capability to restrict Service Providers' access to
DIPs and pre-ingest bundles for jobs that they have not been awarded.
DIPs for jobs that they have not been awarded.
pre-ingest bundles for jobs that they have not been awarded.
The system shall have the capability to determine if delivery is possible.
The system shall have the capability to determine if delivery is possible based
upon business rules.
upon limitations of delivery mechanisms.
upon limitations of content formats.
The system shall have the capability to inform users that delivery is not
possible.
The system shall have the capability to inform users why delivery is not
possible.
The system shall have the capability to provide users with estimated transfer
time for delivery.
The system shall have the capability to provide notification of fulfillment to
users.
The system shall have the capability to provide notification based on user
preferences.
The system shall have the capability to provide notification based on
information gathered at time of request.
R1C; Must
R1C; Must
R1C; Must
R1C; Must
R1C; Must
R1C; Must
R1C; Must
R1C; Must
R1C; Must
R3; Must
R1C; Must
R1C; Must
R3; Must
R1C; Must
R1C; Must
R1C; Must
R1C; Must
R1C; Must
R1C; Must
R1C; Must
R1C; Must
R1C; Must
R1C; Could
R1B; Must
R1B;
Should /
R1C; Must
R1B; Must
105

FINAL
RD-3274
32.2
32.2 Content Delivery Processing

RD-3275
32.2.0-1
The system shall have the capability to create DIPs containing zero or more
digital objects, zero or more metadata files, and zero or more BPI files.
The system shall have the capability to package DIPs containing digital
objects.
The system shall have the capability to package DIPs containing metadata.
The system shall have the capability to package DIPs containing BPI.
The system shall have the capability to assemble pre-ingest bundles
containing digital objects, business process information and metadata
required for service providers to output proofs and produce end product or
service.
containing digital objects required for service providers to output proofs and
produce end products or services.
containing BPI required for service providers to output proofs and produce
end products or services.
containing metadata required for service providers to output proofs and
produce end products or services.
The system shall have capability to transform digital objects to different
formats.
RD-3276
32.2.0-1.0-1
RD-3277
RD-3278
RD-3279
32.2.0-1.0-2
32.2.0-1.0-3
32.2.0-2
RD-3280
32.2.0-2.0-1
RD-3281
32.2.0-2.0-2
RD-3282
32.2.0-2.0-3
RD-3283
32.2.0-3
RD-3284
32.2.0-4
RD-3285
32.2.0-4.0-1
The system shall have the capability to make adjustments to digital objects for
delivery based on digital object format.
The system shall have the capability to adjust the resolution of digital objects.
RD-3286
32.2.0-4.0-2
The system shall have the capability to resize digital objects.
RD-3287
32.2.0-4.0-3
RD-3288
32.2.0-4.0-4
RD-3289
32.2.0-4.0-5
RD-3290
32.2.0-4.0-6
The system shall have the capability to adjust the compression of digital
objects.
The system shall have the capability to adjust the color space of digital
objects. (e.g., CMYK to RGB)
The system shall have the capability to adjust the image quality settings of
digital objects. (e.g., transparency, dithering, anti-aliasing)
The system shall have the capability to rasterize digital objects.
RD-3291
RD-3292
32.2.0-5
32.2.0-6
RD-3293
32.3
The system shall have the capability to process DIPs based on user request.
The system shall have the capability to repurpose content from multiple
packages into a single DIP.
R1B; Must
R1B; Must
R1B; Must
R1B; Must
R1C; Must
R1C; Must
R1C; Must
R1C; Must
R1C;
Should /
R2; Must
R1B; Could
/ R2; Must
R1B; Could
/ R2; Must
R1B; Could
/ R2; Must
R1B; Could
/ R2; Must
R1B; Could
/ R2; Must
R1B; Could
/ R2; Must
R1B; Could
/ R2; Must
R1C; Must
R2; Must
32.3 Content Delivery Mechanisms

RD-3294
32.3.0-1
RD-3295
32.3.0-1.0-1
RD-3296
32.3.0-1.0-1.0-1
RD-3297
32.3.0-1.0-1.0-2
RD-3298
RD-3299
32.3.0-1.0-2
32.3.0-1.0-2.0-1
RD-3300
32.3.0-1.0-2.0-2
RD-3301
32.3.0-1.0-2.0-3
RD-3302
32.3.0-1.0-3
RD-3303
32.3.0-1.0-3.0-1
The system shall have the capability to push DIPs and PIBs to users using
various delivery mechanisms.
The system shall have the capability to push DIPs to users using an RSS
feeds conforming to the RSS 2.0 Specification.
The system shall have the capability for users to sign up to receive DIPS via
RSS feed for new publications added to GPO defined collections.
The system shall have the capability for users to sign up to receive DIPS via
RSS feed for new publications added by user defined criteria.
The system shall have the capability to push DIPs to users using E-mail.
Users shall have the capability to request an e-mail of a DIP containing a
single publication.
Users shall have the capability to sign up to receive e-mails of new
publications added to GPO defined collections.
Users shall have the capability to sign up to receive e-mails of new
publications added by user defined criteria.
The system shall have the capability to push DIPs to users using File Transfer
Protocol.
Users shall have the capability to request that files be transferred via FTP to
R1C; Must
R1C; Must
R1C; Must
R2; Must
R1C; Must
R1C; Must
R1C; Must
R2; Must
R1C; Must
R1C; Must
106

FINAL
RD-3304
32.3.0-1.0-3.0-2
RD-3305
32.3.0-1.0-4
RD-3306
32.3.0-1.0-5
RD-3308
RD-3309
32.3.0-1.0-7
32.3.0-1.0-7.0-1
RD-3310
32.3.0-1.0-7.0-2
RD-3311
32.3.0-1.0-8
RD-3312
32.3.0-1.0-8.0-1
RD-3313
32.3.0-1.0-8.0-2
RD-3314
32.3.0-1.0-9
RD-3315
32.3.0-1.0-10
RD-3316
32.3.0-1.0-11
RD-3317
32.3.0-1.0-12
RD-3318
32.3.0-1.0-13
RD-3320
32.3.0-1.0-15
RD-3321
32.3.0-1.0-16
RD-3322
32.3.0-1.0-17
RD-3323
32.3.0-1.0-18
RD-3324
32.3.0-1.0-19
RD-3325
32.3.0-1.0-20
RD-3326
32.3.0-1.0-21
RD-3327
32.3.0-1.0-22
RD-3328
32.3.0-1.0-23
RD-3329
32.3.0-1.0-24
RD-3330
32.3.0-2
RD-3331
33
their server for a DIP containing a single publication.

Users shall have the capability to request that files be transferred via FTP to
their server for a DIP based on user defined criteria.
The system shall have the capability to push DIPs to users using Secure File
Transfer Protocol.
The system shall support the capability to push DIPs to users using additional
methods in the future.
The system shall have the capability to push PIBs to users using E-mail.
Users shall have the capability to request an e-mail of a PIB for a single order
they have been awarded.
Users shall have the capability to sign up to receive PIBS by e-mail for new
orders they have been awarded.
The system shall have the capability to push PIBs to users using File Transfer
Protocol.
Users shall have the capability to request an FTP of a PIB for a single order
they have been awarded.
Users shall have the capability to sign up to receive PIBS by FTP for new
orders they have been awarded.
The system shall have the capability to push PIBs to users using Secure File
Transfer Protocol.
The system shall support the capability to push PIBs to users using additional
methods in the future.
The maximum size DIP delivered by HTTP download shall be configurable by
an authorized user.
The maximum size PIB delivered by HTTP download shall be configurable by
an authorized user.
The maximum size DIP delivered by RSS feed shall be configurable by an
authorized user.
The maximum size DIP delivered by e-mail shall be configurable by an
authorized user.
The maximum size PIB delivered by e-mail shall be configurable by an
authorized user.
The maximum size DIP delivered by FTP shall be configurable by an
authorized user.
The maximum size PIB delivered by FTP shall be configurable by an
authorized user.
The maximum size DIP delivered by a future electronic channel shall be
configurable by an authorized user.
The maximum size PIB delivered by a future electronic channel shall be
configurable by an authorized user.
The time required to deliver via http download a DIP created from an ACP that
contains a 100 KB (TBS) screen optimized PDF to an average PC (TBS)
connected to the GPO Intranet running Internet Explorer 6 shall be 15
seconds (TBS) or less.
The time required to deliver via http download a DIP created from an AIP in
online storage that contains a 100 KB (TBS) screen optimized PDF to an
average PC (TBS) connected to the GPO Intranet running Internet Explorer 6
shall be 18 seconds (TBS) or less.
The time required to deliver via FTP a DIP created from an ACP that contains
a 10 MB (TBS) set of files to an average PC (TBS) connected to the GPO
Intranet running an FTP server shall be 60 seconds (TBS) or less.
The time required to deliver via FTP a DIP created from an AIP in online
storage that contains a 10 MB (TBS) set of files to an average PC (TBS)
connected to the GPO Intranet running Internet Explorer 6 shall be 65
seconds (TBS) or less.
The system shall provide the capability for users to pull DIPs and PIBs from
the system using various delivery mechanisms, including, but not limited to
Transfer Control Protocol/Internet Protocol.
R1C; Must
R3; Must
R3; Must
R1C; Must
R1C; Must
R2; Must
R1C; Must
R1C; Must
R2; Must
R3; Must
R3; Must
R1C; Must
R1C; Must
R1C; Must
R1C; Must
R1C; Must
R1C; Must
R1C; Must
R3; Must
R3; Must
R3; Must
R3; Must
R3; Must
R3; Must
R1B; Must
33 Requirements for Hard Copy

Output
107

FINAL
RD-3332
33.1
33.1 Hard Copy Output Core Capabilities

RD-3333
33.1.0-1
RD-3334
33.1.0-1.0-1
RD-3335
33.1.0-1.0-1.0-1
RD-3336
33.1.0-1.0-1.0-2
RD-3337
33.1.0-2
RD-3338
33.1.0-2.0-1
RD-3339
33.1.0-2.0-2
RD-3340
33.1.0-3
RD-3341
33.1.0-4
RD-3342
RD-3343
RD-3344
33.1.0-4.0-1
33.1.0-4.0-2
33.1.0-4.0-3
RD-3345
33.1.0-5
RD-3346
33.1.0-5.0-1
RD-3347
RD-3348
RD-3349
RD-3350
33.1.0-5.0-1.0-1
33.1.0-5.0-2
33.1.0-5.0-2.0-1
33.1.0-5.0-2.0-2
RD-3351
33.1.0-5.0-3
RD-3352
33.1.0-5.0-3.0-1
RD-3353
33.1.0-5.0-3.0-2
RD-3354
33.1.0-5.0-3.0-3
RD-3355
33.1.0-5.0-3.0-4
RD-3356
33.1.0-5.0-3.0-5
RD-3357
RD-3358
RD-3359
33.1.0-5.0-4
33.1.0-5.0-5
33.1.0-5.0-6
RD-3360
33.1.0-5.0-6.0-1
RD-3361
33.1.0-5.0-6.0-2
RD-3362
33.1.0-5.0-6.0-3
RD-3363
33.1.0-5.0-6.0-4
RD-3364
RD-3365
RD-3366
33.1.0-5.0-7
33.1.0-5.0-7.0-1
33.1.0-5.0-7.0-2
The system shall have the capability to deliver DIPs and pre-ingest bundles to
users from which hard copy output can be created.
The system shall have the capability to provide DIPs and pre-ingest bundles
that support the production of hard copy on any required hard copy output
technology (e.g., offset press, digital printing).
The system shall have the capability to provide DIPs that support the
production of hard copy on any required hard copy output technology.
The system shall have the capability to provide pre-ingest bundles that
support the production of hard copy on any required hard copy output
technology.
The system shall have the capability to deliver DIPs and pre-ingest bundles
that support static text and images.
The system shall have the capability to deliver DIPs that support static text
and images.
The system shall have the capability to deliver pre-ingest bundles that support
static text and images.
The system shall have the capability to support hard copy output for variable
data printing processes.
The system shall have the capability to add the GPO Imprint line to DIPs and
pre-ingest bundles per the GPO Publication 310.2 and the New Imprint Line
Announcement.
The system shall allow users to manually add the Imprint line.
The system shall automatically add the Imprint Line.
The system shall allow users to manually adjust the location of the Imprint
line.
Files for hard copy output shall be delivered in file formats that conform to
industry best practices
The system shall have the capability to deliver files in their native application
file format.
The system shall have the capability to convert native files to PDF.
The system shall have the capability to deliver optimized (print, press) PDFs.
Optimized PDFs shall have fonts and images embedded.
Image resolution of PDFs shall conform to industry best practices as defined
in GPOs press optimized PDF settings.
The system shall have the capability to deliver page layout files containing
images, fonts, and linked text files.
images, fonts, and linked text files formatted in Adobe InDesign.
images, fonts, and linked text files formatted in QuarkXPress.
images, fonts, and linked text files formatted in Adobe Framemaker.
images, fonts, and linked text files formatted in Adobe Pagemaker.
The system shall support the capability to deliver page layout files containing
images, fonts, and linked text files in additional formats in the future.
The system shall have the capability to deliver vector graphics.
The system shall have the capability to deliver raster images.
The system shall have the capability to deliver Microsoft Office Suite
application files.
application files in Microsoft Word.
application files in Microsoft PowerPoint.
application files in Microsoft Excel.
application files in Microsoft Visio.
The system shall have the capability to deliver XML.
The system shall support cascading style sheets.
The system shall support document type definition/schema.
R1C; Must
R1C; Must
R1B; Must
R1C; Must
R1C; Must
R1B; Could
R1C; Could
R3; Could
R2; Could
R2; Could
R2; Could
R2; Could
R1B; Must
R1B; Must
R1C; Must
R1B; Must
R1B; Must
R1B; Must
R1B; Must
R1B; Must
R1B; Must
R1B; Must
R1B; Must
R3; Must
R1B; Must
R1B; Must
R1B; Must
R1B; Must
R1B; Must
R1B; Must
R1B; Must
R1B; Must
R1B; Must
R1B; Must
108

FINAL
RD-3367
RD-3368
33.1.0-5.0-8
33.1.0-5.0-8.0-1
RD-3369
RD-3370
RD-3371
33.1.0-5.0-8.0-2
33.1.0-5.0-8.0-3
33.1.0-5.0-8.0-4
RD-3372
33.1.0-5.0-8.0-5
RD-3373
33.1.0-5.0-9
RD-3374
RD-3375
33.1.0-5.0-9.0-1
33.1.0-6
RD-3376
RD-3377
34
34.1
The system shall have the capability to deliver text files.

The system shall have the capability to deliver text files in Rich Text (RTF)
format.
The system shall have the capability to deliver text files in ASCII text format.
The system shall have the capability to deliver text files in Unicode format.
The system shall have the capability to deliver text files in Universal MultiOctet Coded Character Set that is equivelent to the native file.
The system shall support the capability to deliver text files in additional file
formats in the future.
The system shall have the capability to deliver OASIS Open Document
Format for Office Applications (OpenDocument) v1.0.
The system shall have the capability to deliver postscript files.
The system shall have the capability to generate DIPs and pre-ingest bundles
that contain Job Definition Format (JDF) data.
R1B; Must
R1B; Must
R1B; Must
R1B; Must
R1B; Must
R3; Must
R1B; Must
R1B; Must
R3; Could
34 Requirements for Electronic

Presentation
34.1 Electronic Presentation Core
Capabilities
RD-3378
34.1.0-1
RD-3379
34.1.0-1.0-1
RD-3380
34.1.0-1.0-2
RD-3381
34.1.0-1.0-3
RD-3382
34.1.0-1.0-4
RD-3383
34.1.0-2
RD-3384
34.1.0-3
RD-3385
34.1.0-3.0-1
RD-3386
34.1.0-3.0-2
RD-3387
34.1.0-3.0-3
RD-3388
34.1.0-4
RD-3389
34.1.0-4.0-1
RD-3390
34.1.0-4.0-2
RD-3391
34.1.0-4.0-3
RD-3392
34.1.0-4.0-4
RD-3393
34.1.0-5
RD-3394
34.1.0-6
RD-3395
34.1.0-6.0-1
RD-3396
34.1.0-6.0-2
The system shall have the capability to create DIPs for electronic presentation
that comply with the FDsys accessibility requirements.
The system shall have the capability to manually check digital objects for
compliance with FDsys accessibility requirements.
The system shall have the capability to automatically check digital objects for
compliance with FDsys accessibility requirements.
The system shall have the capability to manually transform digital objects so
that they are compliant with FDsys accessibility requirements.
The system shall have the capability to automatically transform digital objects
so that they are compliant with FDsys accessibility requirements.
The system shall have the capability to render content for presentation on end
user devices.
The system shall have the capability to render content for presentation on
multiple computer platforms, including but not limited to Windows, Macintosh,
and Unix.
The system shall have the capability to render content for presentation on a
Windows platform.
Macintosh platform.
The system shall have the capability to render content for presentation on a
Unix platform.
non-desktop devices.
Digital Assistants (PDAs).
Digital Audio Players.
Electronic Books (E-Books).
The system shall have the capability to render content for presentation on Cell
Phones.
The system shall have the capability to determine and deliver the file format
needed for non-desktop electronic devices.
The system shall provide the capability to deliver DIPs that support static and
dynamic text in multiple formats.
The system shall have the capability to deliver electronic content in XML that
is equivelent to the native file.
The system shall have the capability to deliver electronic content in HTML with
linked files (e.g., JPEG, GIF, MPEG, MP3) referenced in the HTML code that
R1C; Must
R1C; Must
R2; Must
R1C; Must
R2; Must
R2; Must
R2; Must
R1C; Must
R1C; Must
R2; Must
R2; Should
/ R3; Must
R2; Should
/ R3; Must
R2; Should
/ R3; Must
R2; Should
/ R3; Must
R2; Should
/ R3; Must
R2; Could
R2; Must
R1B; Must
R1B; Must
109

FINAL
RD-3397
34.1.0-6.0-3
RD-3398
34.1.0-6.0-4
RD-3399
34.1.0-6.0-4.0-1
RD-3400
RD-3401
34.1.0-6.0-4.0-1.01
34.1.0-6.0-5
RD-3402
34.1.0-6.0-5.0-1
RD-3403
RD-3404
34.1.0-6.0-5.0-1.01
34.1.0-6.0-6
RD-3405
RD-3406
34.1.0-6.0-7
34.1.0-6.0-7.0-1
RD-3407
34.1.0-6.0-7.0-2
RD-3408
34.1.0-6.0-7.0-3
RD-3409
34.1.0-6.0-7.0-4
RD-3410
34.1.0-6.0-8
RD-3411
34.1.0-6.0-9
RD-3412
34.1.0-7
RD-3413
34.1.0-7.0-1
RD-3414
34.1.0-7.0-2
RD-3415
34.1.0-7.0-3
RD-3416
34.1.0-7.0-4
RD-3417
34.1.0-7.0-5
RD-3418
34.1.0-7.0-6
RD-3419
34.1.0-8
RD-3420
34.1.0-8.0-1
RD-3421
34.1.0-8.0-2
RD-3422
34.1.0-8.0-3
RD-3423
34.1.0-8.0-4
RD-3424
34.1.0-9
RD-3425
34.1.0-10
RD-3426
34.1.0-10.0-1
RD-3427
34.1.0-10.0-2

The system shall have the capability to deliver electronic content in XHTML
with linked files (e.g., JPEG, GIF, MPEG, MP3) referenced in the XHTML
code that is equivelent to the native file.
The system shall have the capability to deliver electronic content in ASCII text
that is equivelent to the native file.
The system shall have the capability to convert images to descriptive ASCII
text.
The system shall have the capability to replace images with descriptive text
when available while converting digital objects to ASCII.
The system shall have the capability to deliver electronic content in Unicode
text that is equivelent to the native file.
The system shall have the capability to convert images to descriptive Unicode
text.
The system shall have the capability to replace images with descriptive text
when available while converting digital objects to Unicode.
The system shall have the capability to deliver electronic content in Open
Document Format that is equivelent to the native file.
The system shall have the capability to deliver content in MS Office formats.
The system shall have the capability to deliver electronic content in Microsoft
Excel (.xls) format.
Word Document File Format (.doc).
PowerPoint File Format (.ppt).
Publisher File Format (.pub).
The system shall have the capability to deliver electronic content in PDF that
is equivelent to the native file
The system shall have the capability to deliver electronic content in Open
eBook Publication Structure (OEBPS) in accordance with Open eBook
Publication Structure Specification Version 1.2.
The system shall provide the capability to deliver DIPs that support static and
dynamic images in multiple formats.
The system shall have the capability to deliver electronic content in JPEG that
The system shall have the capability to deliver electronic content in JPEG
2000 that is equivelent to the native file.
The system shall have the capability to deliver electronic content in TIFF that
is equivelent to the native file
The system shall have the capability to deliver electronic content in GIF that is
equivelent to the native file.
The system shall have the capability to deliver electronic content in SVG
conforming to Scalable Vector Graphic (SVG) 1.1 Specification.
The system shall have the capability to deliver electronic content in EPS
conforming to Encapsulated PostScript File Format Specification Version 3.0.
The system shall provide the capability to deliver DIPs that support audio
information in multiple formats, including, but not limited to:
The system shall have the capability to deliver audio content in MPEG 1 Audio Layer 3 (MP3) that is equivelent to the native file.
The system shall have the capability to deliver audio content in FLAC (Free
Lossless Audio Codec) that is equivelent to the native file.
The system shall have the capability to deliver audio content in Ogg Vorbis
that is equivelent to the native file.
The system shall have the capability to deliver audio content in CDDA
(Compact Disc Digital Audio) that is equivelent to the native file.
The system shall provide the capability to deliver DIPs that support
audiovisual content (e.g., video, multimedia) in MPEG format.
The system shall have the capability to deliver electronic content that
maintains desired user functionality.
The system shall deliver electronic content that maintains hyperlinks to the
extent possible.
The system shall deliver electronic content that maintains interactive content
functionality.
R1B; Must
R1B; Must
R2; Must
R1C; Must
R1B; Must
R2; Must
R1C; Must
R1B; Must
R1B; Must
R1B; Must
R1B; Must
R1B; Must
R1B; Must
R1B; Must
R2; Could
R1B; Must
R1B; Must
R1B; Must
R1B; Must
R1B; Must
R1B; Must
R1B; Must
R1B; Must
R1C; Must
R1C; Could
R1C; Could
R1C; Must
R1B;
Should /
R1C; Must
R1B; Must
R1B; Must
R1B; Must
110

FINAL
RD-3428
RD-3429
35
35.1
RD-3430
35.1.0-1
RD-3431
35.1.0-1.0-1
RD-3432
35.1.0-2
RD-3433
35.1.0-2.0-1
RD-3434
35.1.0-2.0-2
RD-3435
35.1.0-2.0-2.0-1
RD-3436
35.1.0-2.0-2.0-2
RD-3437
35.1.0-2.0-2.0-2.01
35.1.0-2.0-2.0-3
35 Requirements for Digital Media

35.1 Digital Media Core Capabilities
RD-3438
RD-3439
RD-3440
35.1.0-2.0-2.0-3.01
35.1.0-2.0-2.0-4
RD-3441
35.1.0-2.0-2.0-5
RD-3442
35.1.0-3
RD-3443
35.1.0-3.0-1
RD-3444
35.1.0-3.0-2
RD-3445
35.1.0-3.0-3
RD-3446
35.1.0-3.0-4
RD-3447
35.1.0-3.0-5
RD-3448
35.1.0-3.0-6
RD-3449
35.1.0-4
RD-3450
35.1.0-4.0-1
RD-3451
35.1.0-4.0-2
RD-3452
35.1.0-4.0-3
The system shall have the capability to deliver DIPs for digital media
containing electronic content for electronic presentation, hard copy output or
data storage.
The system shall have the capability to deliver pre-ingest bundles for digital
media containing electronic content for electronic presentation, hard copy
output or data storage.
The system shall have the capability to deliver DIPs that support the creation
of removable digital media.
The system shall have the capability to deliver pre-ingest bundles that support
the creation of removable digital media.
of removable optical digital media.
The system shall have the capability to deliver pre-ingest bundles that
support the creation of removable optical digital media.
support the creation of Compact Discs (CD).
The system shall have the capability to deliver and DIPs that support the
creation of Compact Discs (CD).
support the creation of Digital Versitile Disc (DVD) .
of Digital Versital Discs (DVD).
The system shall have the capability to deliverDIPs that support the creation
of Blue Ray Discs (BD).
support the creation of Blue Ray Discs (BD).
The system shall have the capability to deliver pre ingest bundles and DIPs
that are portable (i.e. can be viewed on other systems) via removable
magnetic digital media supported by the client environment.
The system shall have the capability to deliver pre-ingest bundles that are
portable (i.e. can be viewed on other systems) via magnetic tapes supported
by the client environment.
portable (i.e. can be viewed on other systems) via magnetic hard disks
supported by the client environment.
portable (i.e. can be viewed on other systems) via magnetic floppy disks
The system shall have the capability to deliver DIPs that are portable (i.e. can
be viewed on other systems) via magnetic tapes supported by the client
environment.
be viewed on other systems) via magnetic hard disks supported by the client
environment.
be viewed on other systems) via magnetic floppy disks supported by the client
environment.
portable (i.e. can be viewed on other systems) via removable semiconductor
digital media supported by the client environment.
portable (i.e. can be viewed on other systems) via Universal Serial Bus (USB )
flash drives supported by the client environment.
portable (i.e. can be viewed on other systems) via flash memory cards
R1C; Must
R1B; Must
R1C; Must
R1B; Must
R1C; Must
R1C; Must
R1C; Must
R1C; Must
R1C; Must
R1C; Must
R3; Could
R3; Could
R1C; Must
R1C; Must
R1C; Must
R1C; Must
R1B; Must
R1B; Must
R1B; Must
R1C; Must
R1C; Must
R1C; Must
R1B; Must
111

FINAL
RD-3453
35.1.0-4.0-4
RD-3454
35.1.0-5
RD-3455
35.1.0-5.0-1
be viewed on other systems) via Universal Serial Bus (USB ) flash drives
be viewed on other systems) via flash memory cards supported by the client
environment.
The system shall have the capability to generate image files that can be used
to duplicate/replicate the content that will be stored on removable digital
media.
The system shall have the capability to generate ISO image files.
RD-3456
35.1.0-5.0-2
The system shall have the capability to generate VCD image files.
RD-3457
35.1.0-5.0-3
The system shall have the capability to generate UDF image files.
RD-3458
35.1.0-6
The system shall have the capability to generate autorun files for use on
removable digital media.
RD-3459
35.1.0-6.0-1
Users shall have the capability to specify the file that will open when the
removable digital media is inserted into a computer.
RD-3460
35.1.0-7
digital media.
RD-3461
35.1.0-7.0-1
RD-3462
RD-3463
RD-3464
35.1.0-7.0-1.0-1
35.1.0-7.0-1.0-2
35.1.0-7.0-2
RD-3465
35.1.0-7.0-2.0-1
RD-3466
35.1.0-7.0-2.0-2
RD-3467
35.1.0-7.0-3
RD-3468
35.1.0-7.0-3.0-1
RD-3469
35.1.0-7.0-3.0-2
GPO storage devices. (e.g., GPO servers).
The system shall have the capability to deliver DIPs to GPO storage devices.
The system shall have the capability to deliver PIBs to GPO storage devices.
non-GPO storage devices. (e.g., customer servers, service provider servers)
The system shall have the capability to deliver DIPs to non-GPO storage
devices.
The system shall have the capability to deliver PIBs to non-GPO storage
devices.
non-desktop electronic devices, including, but not limited to:
Personal digital assistants (PDAs)
Digital audio players
Electronic books (E-Books)
Cell phones
The system shall have the capability to deliver DIPs to Digital Assistants
(PDAs).
The system shall have the capability to deliver DIPs to Digital Audio Players.
RD-3470
35.1.0-7.0-3.0-3
RD-3471
35.1.0-7.0-3.0-4
The system shall have the capability to deliver DIPs to Electronic Books (EBooks).
The system shall have the capability to deliver DIPs to Cell Phones.
R1B; Must
R1C;
Could / R2;
Should
R1C;
Could / R2;
Should
R1C;
Could / R2;
Should
R1C;
Could / R2;
Should
R1C; Could
/ R2;
Should
R1C; Could
/ R2;
Should
R1C; Could
/ R2;
Should
R1C; Must
R1C; Must
R1C; Must
R1C; Must
R1C; Must
R1C; Must
R2; Should
/ R3; Must
R2; Should
/ R3; Must
R2; Should
/ R3; Must
R2; Should
/ R3; Must
R2; Should
/ R3; Must
112
Appendix A References
Adobe Systems Incorporated. Encapsulated PostScript File Format Specification Version 3.0. Mountain
View, CA: Adobe Systems Incorporated .1 May 1992.
Adobe Systems Incorporated. PDF Reference, Fifth Edition, Version 1.6. Mountain View, CA: Adobe
Systems Incorporated. Nov. 2004.
Adobe Systems Incorporated. TIFF Revision 6.0. Mountain View, CA: Adobe Systems Incorporated. 3
June 1992.
American National Standards Institute. Audio Recording Compact disc digital audio system. (IEC 60908
Ed. 2.0). 1999.
American National Standards Institute. Information Systems - Coded Character Sets - 7-Bit American
National Standard Code for Information Interchange (7-Bit ASCII). (ANSI INCITS 4-1986
(R2002)). American National Standards Institute. 2002.
American National Standards Institute. Triple Data Encryption Algorithm Modes of Operation (TDES)
(ANSI X9.52-1998). ANSI, 1998.
Association for Automatic Identification and Mobility. ANSI/AIM BC1-1995, Uniform Symbology
Specification - Code 39. AIM. 20 Mar. 2006
<http://www.aimglobal.org/aimstore/linearsymbologies.asp>. (Reference only. Bar Coding Digital
Conversions Service Tracking)
Australia. National Library of Australia. Emulation. Preserving Access to Digital Information. 29 Mar.
2006. <http://www.nla.gov.au/padi/topics/19.html>.
Berners-Lee, T, R. Fielding, and L. Masinter. 3986 Uniform Resource Identifier (URI): Generic Syntax. T.
Jan. 2005.
Blanchette, J.-F., "The Digital signature dilemma", Annals of Telecommunications (accepted with
revisions).<http://polaris.gseis.ucla.edu/blanchette/papers/annals.pdf>. (PDF preprint)
Bradley, Jim. New Imprint Line Announcement. May 2 2005. GPO. 22 Mar 2006
<http://www.gpo.gov/bidupdates/pdfs/GPOimprint.pdf>
Brauer, Michael, Patrick Durusau, and Gary Edwards. New Imprint Line Announcement Office
Applications (OpenDocument) v1.0. May 2005. OASIS. 22 Mar 2006. <http://www.oasisopen.org/committees/download.php/12572/OpenDocument-v1.0-os.pdf>.
Brauer, Michael, Patrick Durusau, Gary Edwards, et al. OpenDocument Format for Office Applications
(OpenDocument) v1.0. Organization for the Advancement of Structured Information Standards. 1
May 2005.
CENDI Persistent Identification Task Group. Persistent Identification: A Key Component of an EGovernment Infrastructure. 2004.
Center for Internet Security. Benchmarks, CIS. 22 Mar 2006. <http://www.cisecurity.org/bench.html>.
Coalson, Josh. Free Lossless Audio Codec. 2004. 23 March 2006. <http://flac.sourceforge.net>
Collaborative Digitization Project Scanning Working Group. General Guidelines for Scanning. Spring
1999. Collaborative Digitization Project. 22 Mar 2006 <http://www.cdpheritage.org>.
CompuServe Incorporated. Graphics Interchange Format: Version 89a. Columbus, OH: CompuServe
Incorporated. 31 July 1990.
Computer Security Division. Standards for Security Categorization of Federal Information and Information
Systems: Federal Information Processing Standards Publication 199. Feb 2004. National Institute

FINAL
of Standards and Technology. 22 Mar 2006. <http://csrc.nist.gov/publications/fips/fips199/FIPSPUB-199-final.pdf>.
Consultative Committee for Space Data Systems. Reference Model for an Open Archival Information
System (OAIS). Washington, DC: 2002. 29 Mar. 2006.
<http://public.ccsds.org/publications/archive/650x0b1.pdf>.
Cornell University Library. Digital Preservation Strategies. 2003. Digital Preservation Management:
Implementing Short-term Strategies for Long-term Problems. 29 Mar. 2006
<http://www.library.cornell.edu/iris/tutorial/dpm/terminology/strategies.html>.
Cornwell Consultants in Management and IT. Model Requirements for the Management of Electronic
Records (MoReq). 2001. Electronic Document and Records Management (EDRM). 29 Mar. 2006.
<http://www.cornwell.co.uk/moreq>.
Data Documentation Initiative Alliance. Data Documentation Initiative. 22 Mar. 2006
<http://www.icpsr.umich.edu/DDI/>.
Digital Imaging Working Group. Western States Digital Imaging Best Practices Version 1.0. Jan 2003.
Western States Digital Standards Group. 22 Mar 2006
<http://www.cdpheritage.org/digital/scanning/documents/WSDIBP_v1.pdf>.
Digital Library Federation Benchmark Working Group. Benchmark for Faithful Digital Reproductions of
Monographs and Serials. Dec. 2002. Digital Library Federation. 29 Mar. 2006.
<http://www.diglib.org/standards/bmarkfin.htm>.
Dublin Core Metadata Initiative. [Website]. 13 Mar. 2006. 22 Mar. 2006 <http://dublincore.org/>.
Eastlake 3rd, D., J. Reagle J., and D. Solo, "(Extensible Markup Language) XML-Signature Syntax and
Processing." RFC 3275. March 2002.
Eastlake 3rd, D., J. Reagle J., and D. Solo. "XML Encryption Syntax and Processing." December 2002.
<http://www.w3.org/TR/2001/RED-xmlenc-core-20021210/>.
Eastlake 3rd, D., J. Reagle, and D. Solo. "XML-Signature Syntax and Processing. "XMLDSIG. February
2002. <http://www.w3.org/TR/xmldsig-core/>.
Ex Libris. MetaLib. MetaLib, The Library Portal, Ex Libris Group. 29 Mar. 2006.
<http://www.exlibrisgroup.com/metalib.htm>.
Ex Libris. SFX Overview. SFX Context Sensitive Linking, Ex Libris Group. 29 Mar. 2006.
<http://www.exlibrisgroup.com/sfx.htm>.
Experts on Digital Preservation. Report from the Meeting of Experts on Digital Preservation. March 12,
2004. GPO <http://www.gpoaccess.gov/about/reports/preservation2.pdf>.
Farquhar, Adam, and Sean Martin, Richard Boulderstone, Vince Dooher, Richard Masters, and Carl
Wilson. Design for the Long Term: Authenticity and Object Representation. Boston Spa: United
Kingdom. The British Library, 2005. <http://www.bl.uk/about/policies/dom/pdf/archiving2005l.pdf>.
Federal Emergency Management Agency. Federal Preparedness Circular 65 (FPC 65). Jul 1999. FEMA.
22 Mar 2006 <http://www.fas.org/irp/offdocs/pdd/fpc-65.htm>.
Federal Geographic Data Committee. Content Standard for Digital Geospatial Metadata. 1998. 22 Mar.
2006 <http://www.fgdc.gov/standards/standards_publications/>.
Ferraiolo, Jon, Dean Jackson, and Fujisawa Jun. Scalable Vector Graphics (SVG) 1.1 Specification.
World Wide Web Consortium. 14 Jan. 2003.
Foundations for Technical Standards. 1999. Image Permanence Institute, Rochester Institute of
Technology. 22 Mar 2006 <http://www.rit.edu/~661www1/sub_pages/digibook.pdf>.
114

FINAL
Freed, N, and Borenstein, N. Multipurpose Internet Mail Extensions (MIME) Part Five: Conformance
Criteria and Examples (IETF RFC 2049). Nov. 1996.
The Internet Engineering Task Force, Network Working Group.
Freed, N., J. Klensin, and J. Postel. Multipurpose Internet Mail Extensions (MIME) Part Four: Registration
Procedures (IETF RFC 2048). Nov. 1996.
Frey, Franziska, and James Reilly. Digital Imaging for Photographic Collections
Garrett, John. Important Concepts from the draft ISO standard Reference Model for an Open Archival
Information System (OAIS). College Park, MD: National Archives and Records Administration,
1998. 21 Mar. 2006. <http://nost.gsfc.nasa.gov/isoas/dads/OAISOverview.html>.
Grance, Tim, Joan Hash, and Marc Stevens. Security Considerations in the Information Systems
Development Lifecycle: NIST Special Publication 800-64, Rev. 1. Jun 2004. National Institute of
Standards and Technology. 22 Mar 2006. <http://csrc.nist.gov/publications/nistpubs/800-64/NISTSP800-64.pdf>.
Granger, Stewart. Emulation as a Digital Preservation Strategy. D-Lib Magazine Oct 2000. 29 Mar.
2006. <http://www.dlib.org/dlib/october00/granger/10granger.html>.
IBM. Business Process Execution Language for Web Services version 1.1. 30 Jul. 2002. IBM. 20 Mar.
2006 <http://www-128.ibm.com/developerworks/library/specification/ws-bpel/>.
Information Technology Laboratory. Security Requirements for Cryptographic Modules: Federal
Information Processing Standards Publication 140-2. May 2001. National Institute of Standards
and Technology. 22 Mar 2006. <http://csrc.nist.gov/publications/fips/fips140-2/fips1402.pdf>.
International Cooperation for the Integration of Processes in Prepress, Press and Postpress (CIP4).Job
Definition Format Specification, Release 1.3, 2005. <http://www.cip4.org>
International Organization for Standardization Committee JTC 1/SC 2. Information Technology -Universal Multiple-Octet Coded Character Set (ISO/IEC 10646:2003). International Organization
for Standardization, 2003.
International Organization for Standardization Committee JTC 1/SC 29. Information technology -- Digital
compression and coding of continuous-tone still images: Requirements and guidelines (ISO/IETC
10918-1: 1994). International Organization for Standardization, 1994.
International Organization for Standardization Committee JTC 1/SC 29. Information technology -- Coding
of moving pictures and associated audio for digital storage media at up to about 1,5 Mbit/s -- Part
3: Audio (ISO/IEC 11172-3:1993). International Organization for Standardization, 1993.
International Organization for Standardization Committee JTC 1/SC 29. Information technology -- JPEG
2000 image coding system -- Part 6: Compound image file format (ISO/IEC 15444-6:2003).
International Organization for Standardization, 2003.
International Organization For Standardization. ISO 17421:2003 Space Data and Information Transfer
Systems -- Open Archival Information System -- Reference Model. International Organization for
Standardization, 2003. 22 Mar. 2006
<http://www.iso.org/iso/en/CatalogueDetailPage.CatalogueDetail?CSNUMBER=24683&ICS1=49
&ICS2=140&ICS3>.
International Telephone Union (ITU). Information technology - Open Systems Interconnection - The
Directory: Overview of concepts, models and services: ITU X.500. Feb 2001. ITU.
International Telephone Union (ITU). Information technology - Open Systems Interconnection - The
Directory: Public-key and attribute certificate frameworks: ITU X.509. Mar 2000. ITU.
115

FINAL
ITU-T. ITU-T Recommendation X.509 (1997 E): Information Technology - Open Systems Interconnection
- The Directory: Authentication Framework(Certificate Format Standard). June 1997.
J. Jonsson and B. Kaliski. RFC 3447. Public-Key Cryptography Standards (PKCS) #1: RSA Cryptography
Specifications Version 2.1. IETF. February 2003. <http://www.ietf.org/rfc/rfc3447.txt>.
J. Postel and Reynolds, J. File Transfer Protocol (IETF RFC 959). Oct. 1985.
Joint Photographic Experts Group. "JPEG 2000:Our New Standard." JPEG [Website]. 2004. 22 Mar. 2006
<http://www.jpeg.org/jpeg2000/index.html>.
Koyani, Sanjay J., Robert W. Bailey, Janice R. Nall, Susan Allison, et al. Research-based web design &
usability guidelines. Washington, D.C.: U.S. Department of Health and Human Services,
2003.<http://usability.gov/pdfs/guidelines.html>.
Kuhn, D. Richard, Vincent Hu, W. Timothy Polk, and Shu-Jen Chang. Introduction to Public Key
Technology and the Federal PKI Infrastructure: NIST Special Publication 800-32. Feb 2001.
National Institute of Standards and Technology. 22 Mar 2006.
<http://www.csrc.nist.gov/publications/nistpubs/800-32/sp800-32.pdf>.
Lavoie, Brian. The Open Archival Information System Reference Model: Introductory Guide. Dublin, Ohio:
OCLC Online Computer Library Center, Inc., 2004. 21 Mar. 2006.
<http://www.dpconline.org/docs/lavoie_OAIS.pdf>.
Lynch, Patrick J., Sarah Horton, Web Style Guide 2nd Edition, New Haven, CT: Yale University Press,
2001. <http://www.webstyleguide.com/>.
Maler, Eve, John Cowan, Jean Paoli, et al. Extensible Markup Language (XML) 1.1. World Wide Web
Consortium. 4 Feb. 2004.
Moats, R. 2141 URN Syntax. May 1997.
Moore, K. MIME (Multipurpose Internet Mail Extensions) Part Three: Message Header Extensions for
Non-ASCII Text (IETF RFC 2047). Nov. 1996.
Network Working Group. Lightweight Directory Access Protocol (LDAP) v.3. Dec 1997. Internet
Engineering Task Force (IETF). 22 Mar 2006 <http://www.ietf.org/rfc/rfc2251.txt>.
Network Working Group. Public-Key Cryptography Standards (PKCS) #1: RSA Cryptography
Specifications Version 2.1 IETF RFC 3447. Feb 2003. RSA Laboratories. 22 Mar 2006
<http://www.ietf.org/rfc/rfc3447.txt>.
NISO Framework Advisory Group. A Framework of Guidance for Building Good Digital Collections, 2nd
edition. 2004. National Information Standards Organization. 22 Mar 2006
<http://www.niso.org/framework/framework2.pdf>.
OCLC Worldwide. PREMIS (Preservation Metadata: Implementation Strategies) Working Group. 29 Mar.
2006. <http://www.oclc.org/research/projects/pmwg/>.
Office of Management and Budget. Management of Federal Information Resources: Circular A-130. OMB
22 Mar 2006 <http://www.whitehouse.gov/omb/circulars/a130/a130trans4.html>.
Open eBook Forum. Open eBook Publication Structure Specification Version 1.2. 27 August 2002. 23
March 2006. <http://www.idpf.org/oebps/oebps1.2/download/oeb12.pdf>
Organisation Internationale de Normalisation. ISO/IEC JTC1/SC29/WG11 Coding of Moving Pictures and
Audio. MPEG-21 Overview V.5. Oct. 2002. 22 Mar. 2006
<http://www.chiariglione.org/mpeg/standards/mpeg-21/mpeg-21.htm>.
Pemberton, Steven. XHTML 1.0 The Extensible HyperText Markup Language (Second Edition). World
Wide Web Consortium.1 Aug. 2002.
116

FINAL
PKIX Working Group. Public Key Infrastructure Exchange (PKIX). Dec 2005. Internet Engineering Task
Force (IETF). 22 Mar 2006. <http://www.ietf.org/html.charters/pkix-charter.html>.
Postel, Jonathan. Simple Mail Transfer Protocol (IETF RFC 821). Marina del Rey, CA: Information
Sciences Institute. Aug. 1982. The Internet Engineering Task Force, Network Working Group.
Preservation Metadata Implementation Strategies (PREMIS) Working Group. Data Dictionary for
Preservation Metadata: Final Report of the PREMIS Working Group. May 2005. 22 Mar. 2006
<http://www.oclc.org/research/projects/pmwg/premis-final.pdf>.
Preservation Metadata Implementation Strategies (PREMIS) Working Group. Official Web Site. 7 Feb.
2006. 22 Mar. 2006 <http://www.loc.gov/standards/premis/>.
Puglia, Steven, Reed, Jeffrey, and Rhodes, Erin. Technical Guidelines for Digitizing Archival Materials for
Electronic Access: Creation of Production Master Files-Raster Images. Jun 2004. United States.
National Archives and Records Administration (NARA), 22 Mar 2006.
<http://www.archives.gov/research/arc/digitizing-archival-materials.pdf>.
Purvis, Lisa. A Genetic Algorithm Approach to Automated Custom Document Assembly. Xerox
Corporation, 2003.
R. Housley, W. Ford, W. Polk, D. Solo. Internet X. 509 Public Key Infrastructure Certificate and CLR
Profile (IETF PKIXX.509 v3). RFC 3280. Internet Engineering Task Force (IETF), April 2002.
<http://www.ietf.org/rfc/rfc3280.txt>.
R. Rivest, A. Shamir, L. Adleman. A Method for Obtaining Digital Signatures and Public-Key
Cryptosystems. Communications of the ACM, Vol. 21 (2), pp.120126. 1978. Previously released
as an MIT "Technical Memo" in April 1977. Initial publication of the RSA scheme.
Raggett, David, Arnaud Le Hors, and Ian Jacobs. HTML 4.01 Specification. World Wide Web Consortium.
24 December 1999.
Resnick, P. Internet Message Format (IETF RFC 2822). The Internet Society. Apr. 2001. The Internet
Engineering Task Force, Network Working Group.
Ross, Ron, Stu Katzke, and Arnold Johnson. Recommended Security Controls for Federal Information
Systems: NIST Special Publication SP 800-53. Feb 2005. National Institute of Standards and
Technology. 22 Mar 2006. <http://csrc.nist.gov/publications/nistpubs/800-53/SP800-53.pdf>.
RSA Security Inc. Public-Key Cryptography Standards (PKCS) #1: RSA Cryptography Specifications.
Version 2.1. February 2003.
RSA Security Inc. Public-Key Cryptography Standards (PKCS) #11: Cryptographic Token Interface
Standard. Version 2.20. June 2004.
RSA Security Inc. Public-Key Cryptography Standards (PKCS) #12: Personal Information Exchange
Syntax Standard. Version 1.0, June 1999.
RSA Security Inc. Public-Key Cryptography Standards (PKCS) #7: Cryptographic Message Syntax
Standard. Version 1.4. June 1991.
SANS Institute. Configuration Benchmarks. SANS. 22 Mar 2006 <http://www.sans.org>.
Security Services Technical Committee (SSTC). Security and Access Markup Language (SAML) v.2. Mar
2005. OASIS. 22 Mar 2006 <http://www.oasis-open.org/specs/index.php#samlv2.0>.
Social Security Administration, SSA Privacy Policy. SSA. 22 Mar 2006 <http://www.ssa.gov/privacy.html>.
Society of American Archivists. EAD Application Guidelines for Version 1.0. Library of Congress. 01
Nov. 2000. Library of Congress 21 Mar. 2006 < http://www.loc.gov/ead/ag/agcontxt.html>.
Sollins, K and L. Masinter. RFC 1737 Functional Requirements for Uniform Resource Names. Dec. 1994.
117

FINAL
Swanson, Marianne, Joan Hash, and Pauline Bowen. Guide for Developing Security Plans for Federal
information Systems: NIST Special Publication 800-18. Feb 2006. National Institute of Standards
and Technology. 14 Mar 2006.<http://csrc.nist.gov/publications/nistpubs/800-18-Rev1/sp800-18Rev1-final.pdf>.
Swanson, Marianne. Security Self-Assessment Guide for Information Technology Systems: NIST Special
Publication 800-26.Nov. 2001. National Institute of Standards and Technology. 14 Mar. 2006
<http://csrc.nist.gov/publications/nistpubs/800-26/sp800-26.pdf>.
Technical Advisory Service for Images. Establishing a Digital Preservation Strategy. Technical Advisory
Service for Images. 29 Mar 2006. <http://www.tasi.ac.uk/advice/delivering/digpres2.html>.
Text Encoding Initiative. [Website]. 22 Mar. 2006 <http://www.tei-c.org/>.
Thatcher, Jim, Michael Burks, Sarah Swierenga, Cynthia Waddell, Bob Regan, Paul Bohman, Shawn
Lawton Henry, Mark Urban, Constructing Accessible Web Sites, United States: Glasshaus, 2002.
The Digital Library Federation Benchmark Working Group (2001-2002). Benchmark for Faithful Digital
Reproductions of Monographs and Serials v.1. Dec 2002. Digital Library Federation. 22 Mar 2006
<http://www.diglib.org/standards/bmarkfin.pdf>.
The Netherlands. National Archives and the Ministry of the Interior and Kingdom Relations. Emulation:
Context and Current Status, Digital Preservation Testbed White Paper. Jun 2003. Digital
Preservation Testbed. The Haag: 29 Mar. 2006.
<http://www.digitaleduurzaamheid.nl/bibliotheek/docs/White_paper_emulation_UK.pdf>.
The Unicode Consortium. The Unicode Standard, Version 4.0. Boston, MA, Addison-Wesley Developers
Press, 2003.
Transport Layer Security Working Group. The Secure Sockets Layer (SSL) Protocol Version 3.0.Nov
1996. Internet Engineering Task Force (IETF). 22 Mar 2006.
<http://wp.netscape.com/eng/ssl3/draft302.txt>.
Transport Layer Security Working Group. Transport Layer Security (TLS). Feb 2002. Internet Engineering
Task Force (IETF). 22 Mar 2006.<http://www.ietf.org/html.charters/tls-charter.html>.
United Kingdom. National Archives. The PRONOM Technical Registry. The National Archives. The U.K.
National Archives. 21 Mar. 2006.
<http://www.nationalarchives.gov.uk/aboutapps/pronom/default.htm>.
United States. Congress. Records Maintained on Individuals. Title 5 United States. Code, Sec. 552a.
Jan 7, 2003.
United States. Congress. "Access to Federal Electronic Information" Title 44 U.S. Code, Chapter 41, 2000
edition
United States. Congress. "Records About Individuals: Privacy Act." Title 5 U.S. Code, Sec. 552a (2000).
United States. Congress. "Vocational Rehabilitation and Other Rehabilitation Services--Rights and
Advocacy" Title 29 U.S. Code Chapter 16, Subchapter V", 2000 edition.
United States. Congress. Electronic and Information Technology Accessibility Standards Title 36 Code
of Federal Regulations, Chapter 11, Part 1194, 2004 edition.
United States. Congress. E-Government Act of 2002" (PL 107-347, 17 Dec. 2002). United States.
Statutes at Large 116(2002): 2899.
United States. Congress." Depository Library Program" Title 44 U.S. Code, Chapter 19, 2000 edition.
United States. Congress." Distribution and Sale of Public Documents" Title 44 U.S. Code, Chapter 17,
2000 edition.
118

FINAL
United States. Department of Justice. Information Technology and People with Disabilities: The Current
State of Federal Accessibility. Washington, DC: U.S. Department of Justice. 2000.
<http://www.usdoj.gov/crt/508/report/content.htm>.
United States. Department of the Treasury. IRS Privacy Policy. IRS. 22 Mar 2006
<http://www.irs.gov/privacy/index.html>.
United States. General Accounting Office. Internet Privacy: Agencies Efforts to Implement OMBs Privacy
Policy (GAO/GGD-00-191). Washington, DC: General Accounting Office, 2000. 21 Mar. 2006
<http://www.gao.gov/new.items/d03304.pdf>.
United States. General Services Administration Section 508 Acquisition FAQ's. Section508.gov 2002.
General Services Administration. 20 March 2006.
<http://www.section508.gov/index.cfm?FuseAction=Content&ID=75>.
United States. Government Accounting Office. Internet Privacy -- Agencies Efforts to Implement OMBs
Privacy Policy: GAO/GGD-00-191. Sep 2000. GAO. 22 Mar 2006
<http://www.gao.gov/new.items/gg00191.pdf>.
United States. Government Printing Office. "FDLP Selection Mechanisms: Item Numbers and
Alternatives." FDLP Desktop. 14 February 2006. Government Printing Office. 14 March 2006.
<http://www.access.gpo.gov/su_docs/fdlp/selection/index.html>
United States. Government Printing Office. FDLP Guidelines for Determining Supersede Materials. GPO
Access. 10 Jun. 2004. U.S. Government Printing Office 21 Mar. 2006
<http://www.access.gpo.gov/su_docs/fdlp/coll-dev/supersede.html>.
United States. Government Printing Office. GPO Access Web Design. GPO Instruction 705.27.
Washington, D.C.: U.S. Government Printing Office, 2003.
United States. Government Printing Office. Legal Information. GPO Access. 27 Sep. 2003. U.S.
Government Printing Office. 21 Mar. 2006 <http://www.gpoaccess.gov/about/legal.html>.
United States. Government Printing Office. Requirements Document (RD V2.1) for the Future Digital
System. 18 Apr. 2006. U.S. Government Printing Office. 12 Oct. 2006 <
http://www.gpo.gov/projects/pdfs/FDsys_RD_v2.1.pdf>.
United States. Government Printing Office. A Strategic Vision for the 21st Century. Washington: U.S.
Government Printing Office, 2004. <http://www.gpo.gov/congressional/pdfs/04strategicplan.pdf>
United States. Government Printing Office. Authentication White Paper. Washington: U.S. Government
Printing Office, 2005.
<http://www.gpoaccess.gov/authentication/AuthenticationWhitePaperFinal.pdf>.
United States. Government Printing Office. Concept of Operations for the Future Digital System V2.0. 16
May 2005. 22 Mar. 2006 <http://www.gpo.gov/projects/pdfs/FDsys_ConOps_v2.0.pdf>.
United States. Government Printing Office. Government Printing Office Style Manual. 2000.
United States. Government Printing Office. GPO Access Biennial Report to Congress. Washington: U.S.
Government Printing Office, 2000.
United States. Government Printing Office. GPO Contract Terms: GPO Publication 310.2. Jun 2001.
GPO. 22 Mar 2006 <http://www.gpo.gov/printforms/pdf/terms.pdf>.
United States. Government Printing Office. GPO Form 714 - Record of Visit, Conference, Telephone Call.
Washington, DC: Government Printing Office. Feb. 1991.
United States. Government Printing Office. GPO METS Profile. <to be developed>.
United States. Government Printing Office. ILS Statement of Work, Request for Information, and Related
Files. U.S. Government Printing Office Jan. 2004 (unpublished 2 CD set).
119

FINAL
United States. Government Printing Office. Information Technology Security Program Statement of Policy:
GPO Publication 825.33. Jul 2004.GPO.
United States. Government Printing Office. List of Classes of United States. Government Publications
Available for Selection by Depository Libraries. October 2005 issue. Washington: Government
Printing Office, 2005. <http://www.access.gpo.gov/su_docs/fdlp/pubs/loc/index.html>
United States. Government Printing Office. Oracle Legacy Administrative Systems Replacement Concept
of Operations (GPO-OA-OCIO-00001-CONPOS). Mar. 2004.
United States. Government Printing Office. Printing Procurement Regulation: GPO Publication 305.3.
May 1999. GPO. 22 Mar 2006 <http://www.gpo.gov/printforms/pdf/ppr.pdf>.
United States. Government Printing Office. Quality Assurance through Attributes Program (QATAP): GPO
Publication 310.1. Aug 2002. GPO. 22 Mar 2006 <http://www.gpo.gov/printforms/pdf/qatap.pdf>.
United States. Government Printing Office. The Guidelines - Best Practices for Submitting Electronic
Design & Prepress Files: GPO Publication 300.6. Jul 2004. GPO. 22 Mar 2006.
<http://www.gpo.gov/forms/pdfs/3006_10_2004.pdf>.
United States. Government Publishing Services Opportunity Request for Information: Solicitation 01:
Solicitation number: Reference-Number-ID2005. 21 October 2005. <http://www.fbo.gov>.
United States. Internal Revenue Service. IRS Privacy Policy. Internal Revenue Service. U.S. Internal
Revenue Service. 21 Mar. 2006 <http://www.irs.gov/privacy/index.html>.
United States. Library of Congress. Archival Information Package (AIP) Design Study. Library of
Congress. Washington, D.C.: Library of Congress, 2001. 15 Mar. 2006
<http://www.loc.gov/rr/mopic/avprot/AIP-Study_v19.pdf>.
United States. Library of Congress. METS Metadata Encoding & Transmission Standard Official Web
Site. 9 Mar. 2006. Library of Congress. Network Standards and MARC Development Office. 15
Mar. 2006 <http://www.loc.gov/standards/mets/>.
United States. Library of Congress. MODS Metadata Object Description Schema Official Website. 9 Sept.
2005. Library of Congress. Network Standards and MARC Development Office. 15 Mar. 2006
<http://www.loc.gov/standards/mods/>.
United States. Library of Congress. National Digital Information Infrastructure and Preservation Program
(NDIIPP). The Library of Congress Digital Preservation. 29 Mar. 2006.
<http://www.digitalpreservation.gov>.
United States. Library of Congress. Network Development and MARC Standards Office. Encoded
Archival Description (EAD). 14 Nov. 2005. 22 Mar. 2006 <http://www.loc.gov/ead/>.
United States. Library of Congress. Network Development and MARC Standards Office. MIX NISO
Metadata for Images in XML Standard Official Web Site. 30 Aug. 2005. 22 Mar. 2006
<http://www.loc.gov/standards/mix/>.
United States. National Archives and Records Administration Program Management Office. Electronic
Records Archives (ERA) Concept of Operations (CONOPS v 4.0). 27 Jul. 2004. National Archives
and Records Administration. 29 Mar. 2006. <http://www.archives.gov/era/pdf/concept-ofoperations.pdf>.
United States. National Archives and Records Administration. Electronic and Information Technology
Accessibility Standards Title 36 Code of Federal Regulations, Chapter 21, Part 1194, 2005
edition.
United States. National Archives and Records Administration. Federal Acquisition Regulations Title 48
Code of Federal Regulations, 2005 edition.
120

FINAL
United States. National Archives and Records Administration. Trustworthy Repositories Audit &
Certification: Criteria and Checklist. College Park, MD: 2005. Research Libraries Group. Feb.
2007 <http://www.crl.edu/content.asp?l1=13&l2=58&l3=162&l4=91>.
United States. National Archives and Records Administration. Records Management Guidance for
Agencies Implementing Electronic Signature Technologies. Washington: U.S., 2000.
<http://www.archives.gov/records-mgmt/policy/electronic-signature-technology.html>.
United States. National Institutes of Standards and Technology. Advanced Encryption Standard (AES):
Federal Information Processing Standards Publication 197. Nov 2001. NIST. 22 Mar 2006
<http://csrc.nist.gov/publications/fips/fips197/fips-197.pdf>.
United States. National Institutes of Standards and Technology. Bibliographic References (ANSI/NISO
Z39.29). 9 Jun. 2005. NIST. 29 Mar 2006 <http://www.niso.org/standards/resources/Z39-292005.pdf>.
United States. National Institutes of Standards and Technology. Dublin Core Metadata Element Set.
(Z.39.85). NIST. 26 Mar 1999.
United States. National Institutes of Standards and Technology. Federal Information Processing Standard
Publication 197 (FIPS 197). Advanced Encryption Standard (AES). NIST. November 2001.
<http://csrc.nist.gov/publications/fips/index.html>
Publication 198, The Keyed-Hash Message Authentication Code, NIST, March 6, 2002.
Publication 180-2, Secure Hash Standard (SHS), NIST, August 2002.
<http://csrc.nist.gov/publications/fips/index.html>.
United States. National Institutes of Standards and Technology. Holding Statements for Bibliographic
Items (Z.39.71). 13 Apr. 1994. NIST. 26 Mar 1999.
<http://www.niso.org/standards/resources/Z39-71.pdf>.
United States. National Institutes of Standards and Technology. Information Interchange Format
(ANSI/NISO Z39.2). 13 Apr. 1994. NIST. 29 Mar 2006
United States. National Institutes of Standards and Technology. Information Retrieval: Application Service
Definition & Protocol Specification (Z.39.50). 27 Nov. 2002. NIST. 29 Mar 2006
<http://www.niso.org/standards/resources/Z39-50-2003.pdf>.
United States. National Institutes of Standards and Technology. International Standard Serial Numbering
(ISSN) (ANSI/NISO Z39.9). 20 Jan. 1992. NIST. 29 Mar 2006 <
http://www.niso.org/standards/resources/Z39-9.pdf>.
United States. National Institutes of Standards and Technology. Message Authentication Code (MAC)
Validation System - Requirements and Procedures: Standards Publication 500-156. NIST. May
1988.
United States. National Institutes of Standards and Technology. Public Key Interoperability Test Suite
(PKITS), Certification Path Validation, NIST, September 2, 2004.
United States. National Institutes of Standards and Technology. Record Format for Patron Records.
(Z.39.69). 13 Apr. 1994. NIST. 26 Mar 1999. <http://www.niso.org/standards/resources/Z3971.pdf>.
United States. National Institutes of Standards and Technology. Secure Hash Standard (SHS): Federal
Information Processing Standards Publication 180-2. Aug 2001. NIST. 22 Mar 2006
<http://csrc.nist.gov/publications/fips/fips180-2/fips180-2.pdf>.
121

FINAL
United States. National Institutes of Standards and Technology. Serial Item and Contribution Identifier
(SICI) Z.39.56). 13 Apr. 1994. NIST. 29 Mar 2006 <http://www.niso.org/standards/resources/Z392.pdf>.
United States. National Institutes of Standards and Technology. Space Data and Information Transfer
Systems Open Archival Information System, -- Reference Model (ISO 14721). 24 Feb. 2006.
NIST. 29 Mar 2006.
United States. National Institutes of Standards and Technology. Standard Address Number (SAN) for the
Publishing Industry (Z.39.43). 28 Jan. 1993. NIST. 29 Mar 2006
United States. National Institutes of Standards and Technology. System Questionnaire with NIST SP 80053 References and Associated Security Control Mappings. Apr 2005. National Institute of
Standards and Technology. 14 Mar 2006 <http://csrc.nist.gov/publications/nistpubs/>.
United States. Office of Personnel Management, OPM Web Privacy Policy. OPM. 22 Mar 2006
<http://www.opm.gov/html/privacy.asp>.
United States. Social Security Administration. Our Internet Privacy Policy. Social Security Online. U.S.
Social Security Administration. 21 Mar. 2006 <http://www.ssa.gov/privacy.html>.
United States. Government Printing Office. GPO's Press Optimized PDF Settings. GPO. 18 April
2006.<http://www.gpo.gov/epub/files/AcrobatDistiller-JobOptions.zip>
Virtual Private Network Consortium. IPSEC Virtual Private Network (VPN). <http://www.vpnc.org/vpnstandards.html>.
W3C. Web content accessibility guidelines 1.0. World Wide Web Consortium. 1999. W3C. 20 March
2006. <http://www.w3.org/TR/WCAG10/>.
W3C. World Wide Web Consortium (W3C) Guidelines. 2006. World Wide Web Consortium. 20 March
2006. <http://www.w3.org/>.
Winder, Dave. RSS 2.0 Specification. Berkman Center for Internet & Society at Harvard Law School 15
July 2003.
Workflow Management Coalition. Process Definition Interface -- XML Process Definition Language. 3 Oct.
2005. Workflow Management Coalition. 20 Mar. 2006 <http://www.wfmc.org/standards/docs/TC1025_xpdl_2_2005-10-03.pdf>.
Xiph.org Foundation. Vorbis I Specification. Xiph.org: Documentation. 20 July 2004. Xiph.org
Foundation. 23 March 2006. <http://www.xiph.org/vorbis/doc/Vorbis_I_spec.html>
Yergeau, Francois, and Others. Extensible Markup Language (XML) 1.0. 3rd ed. W3C (World Wide Web
Consortium), 2004. W3C Recommendation 04 February 2004. 22 Mar. 2006
<http://www.w3.org/TR/2004/REC-xml-20040204>.
122

FINAL
Appendix B Acronyms and Glossary

Acronyms
ACRONYM
DEFINITION
ABLS
ACES
ACP
ACS
ACSIS
AES
AIP
AIS
ANSI
AP
ARK
ASCII
ASP
BAC
BPEL
BPI
BPS
CA
CCSDS
CD
CDN
CDR
CD-ROM
CE
CFR
CGP
CMS
CMYK
CO
COOP
CP
CPI
CRC
CSV
DARD
DES
DIP
DNS
DO
DOI
DoS
DPI
Automated Bid List System

Access Certificates for Electronic Services
Access Content Package
Access Content Storage
Acquisition, Classification, and Shipment Information System
Advanced Encryption Standard
Archival Information Package
Archival Information Storage
American National Standards Institute
Access Processor
Archival Resource Key
American Standard Code for Information Interchange
Application Service Provider
Billing Address Code
Business Process Execution Language
Business Process Information
Business Process Storage
Certification Authority
Consultative Committee for Space Data Systems
Compact Disk
Content Delivery Network
Critical Design Review
Compact Disk Read Only Memory
Content Evaluator
Code of Federal Regulations
Catalog of U.S. Government Publications
Content Management System
Cyan, Magenta, Yellow, Black
Content Originator
Continuity of Operations Plan
Content Processor
Content Packet Information
Cyclic Redundancy Checks
Comma Separated Variable
Departmental Account Representative
Data Encryption Standard
Dissemination Information Package
Domain Name System
Digital Objects
Digital Object Identifier
Denial of Service
Dots Per Inch
123

FINAL
ACRONYM
DEFINITION
DSR
DVD
EAD
EAP
EAP
ePub
FAQ
FBCA
FDLP
FICC
FIFO
FIPS
FOB
FOIA
FTP
GAO
GAP
GFE
GFI
GILS
GPEA
GPO
HMAC
HSM
HTML
Hz
ID
IDD
IEEE
IETF
ILS
IP
IPR
IPSEC
ISBN
ISO
ISSN
IT
ITU
JDF
LDAP
LOC
LPI
MAC
MARC
METS
MMAR
MOCAT
MODS
Deployment System Review

Digital Versatile Disc
Encoded Archival Description
Estimate at Completion
Enterprise Application Platform
Electronic Publishing Section
Frequently Asked Question
Federal Bridge Certificate Authority
Federal Depository Library Program
Federal Identity Credentialing Committee
First In First Out
Federal Information Processing Standard
Free on Board
Freedom of Information Act
File Transfer Protocol
General Accounting Office
GPO Access Package
Government Furnished Equipment
Government Furnished Information
Government Information Locator System
Government Paperwork Elimination Act
Government Printing Office
Key Hashed Message Authentication Code
Hardware Security Module
Hypertext Markup Language
Hertz
Information Dissemination
Interface Design Description
Institute of Electronics and Electrical Engineers
Internet Engineering Task Force
Integrated Library System
Internet Protocol
Internal Progress Review
Internet Protocol Security
International Standard Book Number
International Organization for Standardization
International Standard Serial Number
Information Technology
International Telecommunication Union
Job Definition Format
Lightweight Directory Access Protocol
List of Classes
Lines Per Inch
Message Authentication Code
Machine Readable Cataloging
Metadata Encoding and Transmission Standard
Materials Management Procurement Regulation
Monthly Catalog of Government Publications
Metadata Object Descriptive Schema
124

FINAL
ACRONYM
DEFINITION
MPCF
NARA
NB
NC
NDIIPP
NET
NFC
NIST
NLM
OAI
OAI-PMH
OAIS
OCLC
OCR
OLTP
PCCS
PDA
PDF
PDI
PDR
PICS
PICSWEB
PKI
PKITS
PKIX
PKSC
POD
PPR
PREMIS
PRONOM
PTR
PURL
RAID
RFC
RGB
RI
RMA
ROI
RPPO
RSA
RVTM
SAML
SDR
Section 508
SF
SGML
SHA
SIP
SMP
Marginally Punched Continuous Forms

National Archives and Records Administration
National Bibliography
National Collection
National Digital Information Infrastructure and Preservation Program
New Electronic Titles
National Finance Center
National Institutes of Standards and Technology
National Library of Medicine
Open Archives Initiative
Open Archives Initiative Protocol for Metadata Harvesting
Open Archival Information Systems
Online Computer Library Center
Optical Character Recognition
On-line Transaction Processing
Printing Cost Calculating System
Personal Data Assistant
Portable Document Format
Preservation Description Information
Preliminary Design Review
Procurement Information and Control System
Procurement Information Control System Web
Public Key Infrastructure
Public Key Interoperability Test Suite
Public Key Infrastructure Exchange Group within the IETF
Public-Key Cryptography Standard
Print On Demand
Printing Procurement Regulation
PREservation Metadata: Implementation Strategies
Practical Online Compendium of File Formats
Program Tracking Report
Persistent URL
Redundant Array of Inexpensive Disks
Request for Comments
Red, Green, Blue
Representation Information
Reliability, Maintainability, Availability
Return on Investment
Regional Printing Procurement Office
Rivest, Shamir, Adleman
Requirements Verification Traceability Matrix
Security Assertion Markup Language
System Design Review
Section 508 of the Rehabilitation Act
Standard Form
Markup Language
Secure Hash Algorithm
Submission Information Package
Storage Management Processor
125

FINAL
ACRONYM
DEFINITION
SMS
SPA
SSL
SSP
SSR
SuDocs
TDES
TLS
U.S.C.
URL
USGPO
VPN
W3C
WAIS
WAP
WIP
WML
WMS
XML
XMLDSIG
XMLENC
Storage Management System

Simplified Purchase Agreement
Secure Socket Layer
System Security Plan
Software Specification Review
Superintendent of Documents
Triple Data Encryption Standard
Transport Layer Security
United States Code
Uniform Resource Locator
United States Government Printing Office
Virtual Private Network
World Wide Web Consortium
Wide Area Information Service
Wireless Application Protocol
Work in Process
Wireless Markup Language
Workflow Management System
eXtensible Markup Language
XML Signature
XML Encryption
126

FINAL
Glossary
Access: Services and functions that allow users to determine the existence, description, location, and
availability of content, and request delivery of content and metadata.
Access aids: Tools and processes that allow users to locate, analyze, and order content and metadata.
Access Content Package (ACP): An information package that includes renditions of content and
metadata that are optimized for access and delivery. See also OAIS
Access (or service) copy: A digital publication whose characteristics (for example a screen-optimized
PDF file) are designed for ease or speed of access rather than preservation. See also Derivative.
Accessibility: Making tools and content available and usable for all users including those with
disabilities; the degree to which the public is able to retrieve or obtain Government publications, either
through the FDLP or directly through an digital information service established and maintained by a
Government agency or its authorized agent or other delivery channels, in a useful format or medium and
in a time frame whereby the information has utility.
Access Time: Time needed to confirm availability and location of requested data and start the process of
returning data to the user.
Activity: A task that is to be completed or has been completed.
Application Security: The protection of application data and systems against unauthorized access to or
modification of information, whether in storage, processing or transit, and against the denial of service to
authorized users or the provision of service to unauthorized users, including those measures necessary
to detect, document, and counter such threats at the application level. See also Security.
Archival Information Package (AIP): An information package that includes all content, metadata and
associated Preservation Description Information (PDI) needed to preserve the content in perpetuity. See
also OAIS
Archive: A collection with related systems and services, organized to emphasize the long-term
preservation of information.
Archive management - See Preservation.
Assessment: A pre-defined task that evaluates whether the original attributes of a digital object are
correct. The purpose of this assessment is to provide with information needed to identify necessary
preservation processes.
Attribute - A feature or characteristic; a property. Often used to describe the nature of electronic data.
For example, a data value's attributes may include its data type (numeric, character, or date), range of
values, or length.
Authentic: Describes content that is verified by GPO to be complete and unaltered when compared to
the version approved or published by the Content Originator.
Authentication: Validation of a user, a computer, or some digital object to ensure that it is what it claims
to be. In the specific context of the Future Digital System, the assurance that an object is as the author or
issuer intended it. See also Certification.
127

FINAL
Authenticity: The identity, source, ownership and/or other attributes of content are verified.
Automated Activity: An activity conducted under the direct control of the system.
Availability: The degree to which information is obtainable through an intentional or unintentional
provision of information and services.
Batch of Jobs: A set of Jobs selected by the user.
Batch of Workflow Instances: A set of Workflow Instances selected by the user.
Beta Testing: Testing that validates that the system meets the mission and business needs for the
capabilities allocated to that release that involve end users. This is the last test and is part of the decision
for determining if the system is ready to be deployed to public. This testing involves real-world, internal
exposure or operation to the system.
Born digital: In the Future Digital System context, digital objects, created in a digital environment, with
the potential of multiple output products, including hard copy, electronic presentation, and digital media.
Browse: To explore a body of information on the basis of the organization of the collections or by
scanning lists, rather than by direct searching.
Business Manager: A user class that makes policy decisions and develops business plans to meet
Content Originator and End User expectations.
Business process: A set of one or more linked activities which collectively realize a business objective
or policy goal, normally within the context of an organizational structure defining functional roles and
relationships.
Business Process Execution Language (BPEL): An XML-based language to allow the sharing of tasks
across a system.
Business process information: Administrative, non-content-specific information that is used or created
by a business process.
Cataloging and indexing: Cataloging is comprised of the processes involved in constructing a catalog:
describing information or documents to identify or characterize them, providing "entry points" (terms)
peculiar to the information or document, e.g., author, title, subject, and format information, by which the
information can be located and retrieved. The immediate product of cataloging is bibliographic records,
which are then compiled into catalogs. Indexing is the process of compiling a set of identifiers that
characterize a document or other piece of information by analyzing the content of the item and expressing
it in the terms of a particular system of indexing. In GPO context, cataloging and indexing is the statutory
term for the processes that produce the Catalog of U.S. Government Publications and its indexes. In the
FDsys context, it is the process or results of applying bibliographic control to final published versions.
Certification: 1. Proof of verification, validation, or authority. Process associated with ensuring that a
digital object is authentically the content issued by the author or issuer. 2. An assessment against a
known standard.
Certified: Providing proof of verification of authenticity or official status.
Chain of custody: Physical possession or intellectual ownership of content. Provides details of changes
of ownership or custody that are significant in terms of authenticity, integrity, and official status.
128

FINAL
Collaboration: Allowing for multiple authors or content sources while maintaining digital asset and
document control and provenance.
Collection: A GPO defined group of related content.
Collection plan or Collection management plan: The policies, procedures, and systems developed to
manage and ensure current and permanent public access to remotely accessible digital Government
publications maintained in the National Collection.
Composition: The process of applying a standard style or format to content.
Content: Information presented for human understanding. In FDsys, it is the target of preservation.
Content Delivery Network (CDN): An external service provider utilized for distributed storage and
delivery.
Content Evaluator: A user class that determines whether submitted content is in scope for GPOs
dissemination programs.
Content Originator: A user class that develops content, submits content to the system, and submits
orders to GPO for services.
Converted content: Digital content created from a tangible publication.
Cooperative Publication: Publications excluded from GPOs dissemination programs because they are
produced with non-appropriated funds or must be sold in order to be self-sustaining. See 44 USC 1903.
Customization: Providing the ability for users to tailor options to meet their needs and preferences.
Customization is not delivered dynamically (e.g., personalization); it is managed by users and is static
until changed.
Dark archive (digital): The site or electronic environment wherein a second copy or instance of all
master and derivative digital files, data, and underlying enabling code resides and is maintained, under
the control of the managing organization or its proxy. The dark archive must be inaccessible to the
general public. Access to the dark repository contents and resources (lighting the archive) is triggered
only by a specified event or condition.
Dark archive (tangible): A collection of tangible materials preserved under optimal conditions, designed
to safeguard the integrity and important artifactual characteristics of the archived materials for specific
potential future use or uses. Eventual use of the archived materials (lighting the archives) is to be
triggered by a specified event or condition. Such events might include failure or inadequacy of the
service copy of the materials; lapse or expiration of restrictions imposed on use of the archives content;
effect of the requirements of a contractual obligation regarding maintenance or use; or other events as
determined under the charter of the dark archives.
Data Center: A facility containing enterprise-grade FDsys equipment.
Data mining: Discovery method applied to large collections of data, which proceeds by classifying and
clustering data (by automated means) often from a variety of different databases, then looking for
associations. Specifically applied to the analysis of use and user data for GPO systems, data mining
includes the tools and processes for finding, aggregating, analyzing, associating, and presenting BPI and
metadata to enhance internal and external business efficiencies.
129

FINAL
Delivery time: Time needed to deliver requested data to user.
Deposited content: Content received from Content Originators in digital form.
Derivative: A alternate presentation of content, often optimized for a specific function (e.g., access,
preservation, print). Language translations are not derivatives; they are a separate publication.
Device: Content delivery mechanisms for digital media, such as data storage devices (e.g., CD, DVD,
etc.), wireless handheld devices, future media, and storage at user sites.
Digital media: An intermediary mechanism consisting of data storage devices to deliver content to users
storage or display devices.
Digital object: An item stored in a digital library or other digital collection of information, consisting of
data, metadata, and an identifier. A digital object may be an entire document or discrete unit of a
document.
Digital signature: A cryptographic code consisting of a hash, to indicate that data has not changed,
encrypted with the public key of the creator or the signer.
Dissemination: The transfer from the stored form of a digital object in a repository to the client or user.
Dissemination Information Package (DIP): An information package that consists of one or more
renditions of content or metadata from an AIP or ACP that is delivered to users in response to a request.
See also OAIS
Distribution: Applying GPO processes and services to a tangible publication and sending a tangible
copy to depository libraries.
Document: A digital object that is the analog of a physical document, especially in terms of logical
arrangement and use.
Draft: A preliminary version of content, not yet in its finalized form.
Dynamically Changed Workflow: Workflow process that is changed during executing.
Electronic presentation: The dynamic and temporary representation of content in digital format; strongly
dependent upon file format and users presentation device
Emulation: Replication of a computing system to process programs and data from an earlier system that
is no longer is available.
End User: A user class that uses the system to access content and metadata.
Ensure: Instruction to make sure an action takes place.
External Activity: An activity that requires manual or automated processing external to FDsys.
Faithful digital reproduction: Digital objects that are optimally formatted and described with a view to
their quality (functionality and use value), persistence (long-term access), and interoperability (e.g. across
platforms and software environments). Faithful reproductions meet these criteria, and are intended to
accurately render the underlying source document, with respect to its completeness, appearance of
original pages (including tonality and color), and correct (that is, original) sequence of pages. Faithful
130

FINAL
digital reproductions will support production of legible printed facsimiles when produced in the same size
as the originals (that is, 1:1).
FDLP Electronic Collection (EC): The digital Government publications that GPO holds in storage for
permanent public access through the FDLP or are held by other institutions operating in partnership with
the FDLP.
FDLP partner: A depository library or other institution that stores and maintains for permanent access
segments of the Collection.
Final Published Version: Content in a specific presentation and format approved by its Content
Originator for release to an audience. (See also Government Publication; Publication).
Fixity: the quality of being unaltered (e.g. "fixity of the text" refers to the durability of the printed word).
Format: In a general sense, the manner in which data, documents, or literature are organized, structured,
named, classified, and arranged. Specifically, the organization of information for storage, printing, or
display. The format of floppy disks and hard disks is the magnetic pattern laid down by the formatting
utility. In a document, the format includes margins, font, and alignment used for text, headers, etc. In a
database, the format comprises the arrangement of data fields and field names.
Format management -See Preservation.
Fugitive document: A U.S. Government publication that falls within the scope of the Federal Depository
Library Program, but has not been included in the FDLP. These publications include tangible products
such as ink-on-paper, microforms, CD-ROM, or DVDs. Fugitive documents most commonly occur when
Federal agencies print or procure the printing of their publications on their own, without going through
GPO.
Fulfillment: the processes related to the packaging and delivery of tangible goods for delivery.
Government publication: A work of the United States Government, regardless of form or format, which
is created or compiled in whole or in part at Government expense, or as required by law, except that
which is required for official use only, is for strictly operational or administrative purposes having no public
interest or educational value, or is classified for reasons of national security.
Granularity: The degree or level of detail available within content in the system
Handle System: A comprehensive system for assigning, managing, and resolving persistent identifiers,
known as "handles," for digital objects and other resources on the Internet. Handles can be used as
Uniform Resource Names (URNs).
Hard copy: Tangible printed content.
Harvest: The identification and replication of content resident on web servers outside GPO's control.
Harvested content: Digital content within the scope of dissemination programs that is gathered from
Federal agency Web sites.
History: A record of all system activities.
Hybrid: A package containing selected content from multiple information packages.
131

FINAL
Information granularity: The degree or level of detail available in an information system. With reference
to authentication, the level of detail or specificity (e.g., page, chapter, paragraph, line) to which veracity
can be certified.
Ingest: The OAIS entity that contains the services and functions that accept SIPs from Producers,
prepare Archival Information packages for storage, and ensure that information packages and their
supporting descriptive information packages are established within OAIS.
Integrity: Content has not been altered or destroyed in an unauthorized manner.
Integrity Mark: Conveys authentication information to users.
Interoperability: Compatibility of workflow across standards (e.g., WFMC to BPEL) and, compatibility of
workflow within a standard and across programming languages (e.g., Java and C++ working in WFMC).
Internal Activity: An activity conducted within FDsys.
Item: A specific piece of material in a digital library or collection; a single instance, copy, or manifestation.
Job: A set of manual and automated activities that produce a product or service.
Light archive: A collection of tangible materials preserved under optimal conditions, designed to
safeguard the integrity and important artifactual characteristics of the archived materials while supporting
ongoing permitted use of those materials by the designated constituents of the archives. A light archive
normally presupposes the existence of a dark archive, as a hedge against the risk of loss or damage to
the light archives content through permitted uses. A light archive is also distinct from regular collections of
like materials in that it systematically undertakes the active preservation of the materials as part of a
cooperative or coordinated effort that may include other redundant or complementary light archives.
List of Jobs: A list of Jobs assigned to a particular user.
List of Workflow Instances: A list of Workflow Instances assigned to a particular user.
Localized presentation: Temporary representation of layout or structure on a users local presentation
device.
Locate (discover): The organized process of finding Web-based documents or publications that are
within scope for a particular collection.
Manage: In Information Technology contexts, to add, modify, or delete content.
Manifestation: Form given to an expression of a work, e.g., by representing it in digital form.
Manual Activity: An activity conducted in such a manner that the system cannot exert direct control.
Message: Communication between a process and the Workflow Management System.
Metadata: Metadata is a structured representation of information that facilitates interpretation,
management, and location by describing essential attributes and significant properties. Metadata
describes the content, quality, condition, or other characteristics of other data. Metadata describes how,
when, and by whom information was collected, where it resides, and how it is formatted. Metadata helps
locate, interpret, or manage. In current usage several types of metadata are defined: descriptive, which
aids in locating information; structural/technical, which records structures, formats, and relationships;
132

FINAL
administrative, which records responsibility, rights, and other information for managing the information;
and preservation, which incorporates elements of the other types specific to preserving the information
for the long term.
Metadata Encoding and Transmission Standard (METS): An XML schema for encoding metadata
associated with objects in a digital library.
Migration: Preservation of digital content where the underlying information is retained but older formats
and internal structures are replaced by newer.
Modified workflow: Workflow process that is changed during process development or, not at runtime.
National Collection of U.S. Government Publications (NC): A comprehensive collection of all
publications in scope for GPOs dissemination programs, content that should be in the Federal Depository
Library Program, regardless of form or format. The NC will consist of multiple collections of tangible and
digital publications, located at multiple sites, and operated by various partners within and beyond the U.S.
Government.
Natural Granularity Boundaries: The structure that is set in a document's native format, including
volumes, chapters, parts, sections, and paragraphs.
No-fee access: There are no charges to individual or institutional users for searching, retrieving, viewing,
downloading, printing, copying, or otherwise using digital publications in scope for the FDLP.
Non-repudiation: Verification that the sender and the recipient were, in fact, the parties who claimed to
send or receive content, respectively.
Notification: A message in Workflow between a process and the WMS that indicates when an identified
event or condition, such as an exception, has been met.
Open Archival Information System Reference Model (OAIS): ISO 14721:2003 - A reference model for
an archive, consisting of an organization of people and systems that has accepted the responsibility to
preserve information and make it available for a designated community. The model defines functions,
activities, responsibilities, and relationships within this archive, sets forth common terms and concepts,
and defined component functions which serve as the basis for planning implementation.
Official: A version that has been approved by someone with authority.
Official content: Content that falls within the scope of the FDLP EC and is approved by, contributed by,
or harvested from an official source in accordance with accepted program specifications
Official source: The Federal publishing agency, its business partner, or other trusted source.
Online Information eXchange (ONIX): A standard format that publishers can use to distribute electronic
information about their books to wholesale, e-tail and retail booksellers, other publishers, and anyone else
involved in the sale of books.
Online: A digital publication that is published at a publicly accessible Internet site.
Online dissemination: Applying GPO processes and services to an online publication and making it
available to depository libraries and the public.
133

FINAL
Operations Manager: A user class that develops and optimizes workflow processes and monitors the
quality of system products.
Permanent Public Access (PPA): Government publications within the scope of the FDLP remain
available for continuous, no-fee public access through the program.
Persistent Name: Provides permanence of identification, resolution of location, and is expected to be
globally (e.g., internationally) registered, validated, and unique
Personalization: Dynamically tailoring options to match user characteristics, behavior, or preferences.
Personalization is often implemented by analyzing data and predicting future needs.
Policy neutral: Refers to a system which is sufficiently flexible to accommodate changes in hardware,
software, communication technology, processes, policy, personnel, locations, etc. without requiring major
re-engineering or design changes. FDsys is envisioned as being responsive to policy, but it is not
intended to be policy-constrained.
Pre-Ingest Bundle (PIB): Digital objects, related metadata, and BPI, gathered for transfer to a service
provider in the event of a Content Originator request for a proof. After approval the PIB becomes a SIP for
ingest.
Preliminary Composition: Preparatory representation of content format or structure
Presentation Device: A device that can present content for comprehension
Preservation: The activities associated with maintaining publications for use, either in their original form
or in some verifiable, usable form. Preservation may also include creation of a surrogate for the original
by a conversion process, wherein the intellectual content and other essential attributes of the original are
retained. For digital materials, preservation includes the management of formats of information (including
possible migration to newer versions), the storage environment, and the archival arrangement of
information to facilitate preservation.
Preservation description information: Information necessary for adequate preservation of content
information, including information on provenance, reference, fixity, and context. See also OAIS
Preservation master: A copy which maintains all of the characteristics of the original publication, from
which true copies can be made.
Preservation master requirement: A set of attributes for a digital object of sufficient quality to be
preserved and used as the basis for derivative products and subsequent editions, copies, or
manifestations. Requirements for use, users, and state/condition/format of the source of the original
object need to be noted.
Preservation processes: Activities necessary to keep content accessible and usable, including
Migration, Refreshment, and Emulation.
Print on demand (POD): Hard copy produced in a short production cycle time and typically in small
quantities.
Process: A formalized view of a "business process", represented as a coordinated (parallel and/or serial)
set of process activities that are connected in order to achieve a common goal.
134

FINAL
Provenance: The chain of ownership and custody which reflects the entities that accumulated, created,
used, or published information. In a traditional archival sense, provenance is an essential factor in
establishing authenticity and integrity.
Public Key Infrastructure (PKI): A system of digital certificates, Certificate Authorities, and other
registration authorities that verify and authenticate the validity of each party involved in an Internet
transaction.
Publication: Content approved by its Content Originator for release to an audience.
See also Government publication.
Pull: Downloading content on an as-needed basis. Content is made available for users to select and
retrieve (pull) to local servers or computers. For example, currently users may be said to pull documents
from GPO Access.
Push: Intentionally and specifically serving out information to a target recipients. Content is automatically
sent (pushed) from GPO to a list of interested users. This is analogous to shipping a box of depository
documents, only with electronic content instead of tangible copy.
Redundant Array of Inexpensive Disks (RAID): A set of different hardware storage configurations
where multiple hard disk drives share and/or replicate data.
Reference tools: Finding aids, bibliographies, and other services to assist in the locating and use of
information, often less formally organized than catalogs and indexes.
Refreshment: A preservation process for data extraction, cleaning and integration, and the triggering
events of these activities.
Relationship: A statement of association between instances of entities. In PREMIS, the association(s)
between two or more object entities, or between entities of different types, such as an object and an
agent.
Render: To transform digital information in the form received from a repository into a display on a
computer screen or other presentation to a user.
Rendition: Instance of a publication expressed using a specific digital format
Replication: Make copies of digital material for backup, performance, reliability, or preservation.
Representation Information: The information that maps a data object into more meaningful concepts.
An example is the ASCII definition that describes how a sequence of bits (i.e., a Data Object) is mapped
into a symbol.
Repository: A computer system used to store digital collections and disseminate them to users.
Requirements: In system planning, a requirement describes what users want and expect according to
their various needs. Requirements draw a comprehensible picture to facilitate communications between
all stakeholders in the development of a system, and outline the opportunities for development of
successful products to satisfy user needs.
Rich media: Electronic presentation that uses enhanced sensory features such as images, video, audio,
animation and user interactivity
135

FINAL
Rider: Request by GPO, agency, or Congress that adds copies to a Request or C.O. Order placed by a
publishing agency or Congress.
Search: Process or activity of locating specific information in a database or on the World Wide Web. A
search involves making a statement of search terms and refining the terms until satisfactory result is
returned. Searching is distinct from browsing, which facilitates locating information by presenting
references to information in topical collections or other logical groupings or lists.
Section 508 - Section 508 of the Rehabilitation Act requires access to electronic and information
technology procured by Federal agencies. The Access Board developed accessibility standards for the
various technologies covered by the law. These standards have been folded into the Federal
government's procurement regulations. http://www.access-board.gov/508.htm
Secondary dark archive (digital): Multiple copies or instances of the dark repository, maintained as
assurance against the failure or loss of the original dark repository. The secondary dark repository must
provide redundancy of content to the original dark repository, and the systems and resources necessary
to support access to and management of that content must be fully independent of those supporting the
original dark repository content.
Secondary service repository (digital): The secondary service archive is a mirror of the service
archive, created to provide instantaneous and continuous access to all designated constituents when the
access copy or service archive is temporarily disabled.
Security: The protection of systems against unauthorized access to or modification of information,
whether in storage, processing or transit, and against the denial of service to authorized users or the
provision of service to unauthorized users, including those measures necessary to detect, document, and
counter such threats. The measures and controls, including physical controls in conjunction with
management, technical and procedural controls, that ensure the confidentiality, integrity and availability of
information processed and stored by a system. See also Application Security.
Service archive (digital): The site or electronic environment wherein the derivative, or use, files and
metadata created from source objects (here, tangible government documents), as well as the software,
systems, and hardware necessary to transmit and make those files and metadata accessible, are
maintained for public display and use. The service repository contains the current and most
comprehensive electronic versions of those source materials.
Service Provider: A user class that delivers the expected services and products.
Service Specialist: A user class that supports Content Originators and End users to deliver expected
products and services.
Shared repository: A facility established, governed, and used by multiple institutions to provide storage
space and, in some instances limited service for low-use library materials, primarily paper-based
materials that do not have to be readily available for consultation in campus libraries.
Status: A representation of the internal conditions defining the state of a process or activity at a particular
point in time.
Storage: The functions associated with saving digital publications on physical media, including magnetic,
optical, or other alternative technologies.
Storage management - See Preservation.
Submission information package (SIP): The information package submitted by a Content Originator for
ingest the system. See also OAIS
136

FINAL
Subscription: An agreement by which a user obtains access to requested content by payment of a
periodic fee or other agreed upon terms.
System: An organized collection of components that have been optimized to work together in a functional
whole.
System metadata: Data generated by the system that records jobs, processes, activities, and tasks of
the system.
Systems Administration: A user class that directly supports the use, operation, and integrity of the
system
Tangible publication: Products such as ink-on-paper, microforms, CD-ROM, or DVDs, characterized by
content recorded or encoded on a physical substrate.
Transformation: A process that produces one or more content packages from another; e.g., SIPs are
transformed into Access Content Packages (ACPs) and Archival Information Packages (AIPs).
Test Case: 1. A set of test inputs, execution conditions, and expected results developed for a particular
objective, such as to exercise a particular program path or to verify compliance with a specific
requirement. 2. Documentation specifying inputs, predicted results, and a set of execution conditions for a
test item.
A document describing a single test instance in terms of input data, test procedure, test execution
environment and expected outcome. Test cases also reference test objectives such as verifying
compliance with a particular requirement or execution of a particular program path
Trusted content: Official content that is provided by or certified by a trusted source.
Trusted source: The publishing agency or a GPO partner that provides or certifies official FDLP content.
Unique Identifier: A character string that uniquely identifies digital objects, content packages and jobs
within the system.
Use Case: A description of the behavior of a system or part of a system; a set of sequences or actions,
including variants that a system performs to yield an observable result of value.
User acceptance testing: Testing that validates that the system meets GPO's mission and business
needs for the capabilities allocated to that release, in order to expose issues before the system is
released to a wider audience in beta testing. This testing involves real-world, internal exposure or
operation to the system.
Validation: A process that ensures (e.g., proves) that data conforms to standards for format, content and
metadata.
Variable Data Printing: A form of printing where elements such as text and images may be pulled from a
database for use in creating the final package. Each printed piece can be individualized without stopping
or slowing the press.
Verification: The process of determining and assuring accuracy and completeness. There is a known
input and an expected output is confirmed (e.g. check).
Version: Unique manifestation of content within a content package.
137

FINAL
Version control: The activity of identifying and managing versions.

Version detection: Activity of inspecting a content package for changes and responding to version
triggers. Also, activity of polling the system to identify if an identical version already exists in the system.
Version identifier: Information stored in metadata that identifies version.
Version trigger: Changes to content beyond an agreed upon threshold in certain categories (e.g., title,
edition statement, language translation) which constitute a new version or help a Service Specialist make
a version determination.
Version information: Information stored in metadata that describes the relationship between versions.
Viable application: Application software which retains all of its original functionality.
Workbench: A set of available tools for each user class (e.g., Content Originator, End User) that are
displayed on a graphical user interface. A user's role (e.g., cataloger, Federal depository librarian)
determines which of the tools available to his or her class will be displayed on the graphical user
interface.
Work Item: The representation of the work to be processed (by a workflow participant) in the context of
an activity within a process.
Workflow: The automation of a business process, in whole or part, during which documents, information
or tasks are passed from one participant to another for action, according to a set of procedural rules.
Workflow Definition: A document that defines the activities, business rules, data flows, and personnel
roles that specify how a GPO business process will be performed within FDsys.
Workflow Instance: A workflow definition that is being executed on a specific entities by a specific
person.
Workflow Management System (WMS): A system that defines, creates, and manages the execution of
workflows through the use of software, running on one or more workflow engines, which is able to
interpret the process definition, interact with workflow participants and, where required, invoke the use of
IT tools and applications.
Workflow Participant: A resource, human or computer tool/application, which performs the work
represented in an activity.
138

RD55 Document-Requirement Gathering

Uploaded by

Copyright:

Available Formats

RD55 Document-Requirement Gathering

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

RD55 Document-Requirement Gathering

Uploaded by

Copyright:

Available Formats

What are the core capabilities of content metadata?

What are the core capabilities of content metadata?

What are the requirements for SIPs?

What are the requirements for SIPs?

REQUIREMENTS DOCUMENT

GPOs Digital Content System (FDsys)

Requirements Document (RD) v.3.1

Office of the Chief Technical Officer (CTO)

GPOs Digital Content System (FDsys)

Requirements Document (RD) v.3.1

Office of the Chief Technical Officer (CTO)

GPOs Digital Content System (FDsys)

Requirements Document (RD) v.3.1

Office of the Chief Technical Officer (CTO)

GPOs Digital Content System (FDsys)

Requirements Document (RD) v.3.1

Office of the Chief Technical Officer (CTO)

GPOs Digital Content System (FDsys)

Requirements Document (RD) v.3.1

Office of the Chief Technical Officer (CTO)

GPOs Digital Content System (FDsys)

Requirements Document (RD) v.3.1

Office of the Chief Technical Officer (CTO)

2007-05-08 Requirements Baseline

2 Requirements for System, General

GPOs Digital Content System (FDsys)

Requirements Document (RD) v.3.1

Office of the Chief Technical Officer (CTO)

the content files and metadata files in the package.

3 Requirements for Content

3.2 Content Metadata Types

GPOs Digital Content System (FDsys)

Requirements Document (RD) v.3.1

Office of the Chief Technical Officer (CTO)

related to a target digital object(s) and its associated content package.

3.3 Content Metadata Schema

GPOs Digital Content System (FDsys)

Requirements Document (RD) v.3.1

Office of the Chief Technical Officer (CTO)

3.4 Content Metadata Import and Export

GPOs Digital Content System (FDsys)

Requirements Document (RD) v.3.1

Office of the Chief Technical Officer (CTO)

3.5 Content Metadata Management

4 Requirements for SIP

4.2 SIP Harvested Content

4.3 SIP Converted Content

GPOs Digital Content System (FDsys)

Requirements Document (RD) v.3.1

Office of the Chief Technical Officer (CTO)

4.4 Core SIP Requirements

A SIP shall contain one or more renditions of one publication.

4.5 Requirements for sip.xml File

The sip.xml file shall conform to the METS version 1.5.

GPOs Digital Content System (FDsys)

Requirements Document (RD) v.3.1

Office of the Chief Technical Officer (CTO)

4.6 Structural Layout for SIPs

4.7 Packaging of SIPs

4.8 SIP Descriptive Metadata