> **EDGAR PROGRAM**
>
> **EDGAR Release 9.0**
>
> **XFDL Reduced Content Filing Specification\
> \
> \
> **

![](media/image1.wmf){width="4.489583333333333in"
height="2.2291666666666665in"}

June 2005

**TABLE OF CONTENTS**

[1. PURPOSE 1](#purpose)

[1.1 Release Notes 2](#release-notes)

[2. Organization of this Specification
3](#organization-of-this-specification)

[3. XFDL Templates 3](#xfdl-templates)

[4. Reduced Content File Format 4](#reduced-content-file-format)

[5. Reduced Content XFDL Elements 5](#reduced-content-xfdl-elements)

[5.1 VERSION NODES 5](#version-nodes)

[5.2 END XFDL NODE 5](#end-xfdl-node)

[5.3 PAGE NODES 6](#page-nodes)

[5.4 VALID SCOPE (NODE) IDENTIFIERS 7](#valid-scope-node-identifiers)

[5.4.1 VALID EDGAR SCOPE IDENTIFIERS (*sid*s)
7](#valid-edgar-scope-identifiers-sids)

[5.5 SUBMISSION DATA NODES 8](#submission-data-nodes)

[5.6 FIELD NODES 9](#field-nodes)

[5.7 CHECKBOX NODES 9](#checkbox-nodes)

[5.8 RADIO BUTTON NODES 10](#radio-button-nodes)

[5.9 POPUP NODES 10](#popup-nodes)

[5.10 COMBOBOX NODES 10](#combobox-nodes)

[5.11 DATA NODES -- (ENCLOSED DOCUMENTS)
11](#data-nodes-enclosed-documents)

[6. Verifying Reduced Content Structure
11](#verifying-reduced-content-structure)

[7. How to use THE Appendices 12](#how-to-use-the-appendices)

[8. Sample Forms 14](#sample-forms)

[8.1 Sample 24F-2NT from Subtemplate1.xfd
14](#sample-24f-2nt-from-subtemplate1.xfd)

[8.2 Sample S-1 from Subtemplate1.xfd
15](#sample-s-1-from-subtemplate1.xfd)

[8.3 Sample N-1 from Subtemplate1.xfd
16](#sample-n-1-from-subtemplate1.xfd)

[8.4 Sample 144 submission from Subtemplate2.xfd
17](#sample-144-submission-from-subtemplate2.xfd)

[8.5 Sample PREM14A submission from Subtemplate2.xfd
18](#sample-prem14a-submission-from-subtemplate2.xfd)

[8.6 Sample 10-12B from Subtemplate3.xfd
19](#sample-10-12b-from-subtemplate3.xfd)

[8.7 Sample CORRESP from Subtemplate4.xfd
20](#sample-corresp-from-subtemplate4.xfd)

[8.8 Sample MODULE from Subtemplate5.xfd
21](#sample-module-from-subtemplate5.xfd)

[8.9 Sample BULK from Subtemplate6.xfd
22](#sample-bulk-from-subtemplate6.xfd)

# PURPOSE

The EDGARLink portion of the EDGAR web-based filing environment is based
on the PureEdge (formerly UWI.COM) XFDL forms specification, which is an
extension of the XML specification. An EDGAR filer, from his or her
client machine, must use the PureEdge Viewer application to open an XFDL
Template and construct a file that he or she can then submit via the
EDGAR Filing web site. The EDGAR server-side software uses the PureEdge
Application Programming Interface (API) to parse the pertinent
submission data from the filer's XFDL file.

XFDL forms are XML documents; the form definition is encoded using XML
elements and attributes. The XFDL specification uses DTD notation to
express nesting and sequence relationships between the elements and
attributes; while the constraints on element contents and attribute
values are given in the BNF notation found in the XML specification.

Roughly 99 percent of the XFDL content of each EDGAR Template, as well
as any submission file saved from the Template, is needed only for the
rendering of the Graphical User Interface (GUI). The EDGAR submission
processing software is concerned with the one percent of the XFDL
content that contains the submission-related data. All the GUI-related
items are ignored.

This document provides a specification for creating XFDL filings without
the use of the PureEdge Viewer. The expectation is that software
developers, working on behalf of filers, will construct software that
will generate submissions that can be successfully parsed by EDGAR.
These generated submissions should contain only the minimum set of XFDL
data needed by the EDGAR, hence the term "Reduced Content" submission is
used to describe submissions compliant with this specification.[^1]

The benefits of reduced content are twofold. First, these smaller files
require less bandwidth for upload to the EDGAR Filing web site and
therefore should upload quicker. Second, the server-side parser can
process the filing quicker since all the GUI-related content is not in
the file.

This specification, by itself, is not sufficient to generate correct
reduced content filings. We assume the reader is already familiar with
XML, the various SEC form types, filing act requirements, and SEC syntax
rules. The following documents provide additional filing information and
provide a resource for the XFDL specification.

-   The EDGAR Filer Manual may be obtained from *http://www.sec.gov*.
    Chapter 5 specifically addresses the forms templates and data fields
    on the forms.

-   The Extensible Forms Definition Language (XFDL) 4.0 Specification
    may be obtained from
    *http://www.w3.org/TR/1998/NOTE-XFDL-19980902.html*.

NOTE: Although the PureEdge product suite was used to develop the EDGAR
electronic forms, PureEdge did not participate in this process. Do NOT
contact PureEdge for information specific to the SEC form templates or
this reduced content specification.

## Release Notes

This release introduces minor updates to submission Templates 1, 2, 3,
and 5 and EDGARLink software that are based on recent SEC requests and
rulemaking activities. EDGAR 9.0 server software supports all of the
field identifiers that were valid in the 8.10 version of the PureEdge
templates.

Changes By Template

The following changes are called out in the appendices. Please refer to
the appendices for details.

Template 1

1.  Additional exhibit types are allowed in the
    SubDocument_conformedDocumentType\_ field and the
    ModSegReferenceData_documentType\_ field:

EX-33, EX-34, EX-35

Template 2

1.  Additional exhibit types are allowed in the
    SubDocument_conformedDocumentType\_ field and the
    ModSegReferenceData_documentType\_ field:

EX-33, EX-34, EX-35

Template 3

1.  Additional exhibit types are allowed in the
    SubDocument_conformedDocumentType\_ field and the
    ModSegReferenceData_documentType\_ field:

EX-33, EX-34, EX-35

2.  Additional submission types are allowed in the
    SubTable_submissionType\_ field:

> 10-D, 10-D/A, NT 10-D, NT 10-D/A

3.  Additional items are allowed in the SubItem_itemId\_ field:

6.01, 6.02, 6.03, 6.04, 6.05

4.  In order to specify the depositor information for a new Asset-Backed
    Securities Issuing Entity, the new SubTable_depositorCik\_ and
    SubTable_depositorFileNumber\_ fields are now allowed for the
    following submission types:

8-K, 8-K/A, 8-K15D5, 8-K15D5/A

Template 5

1.  Additional exhibit types are allowed in the SubModSeg_ModSegType\_
    field:

EX-33, EX-34, EX-35

# Organization of this Specification

The remaining sections of this specification provide the framework for
successfully constructing a "reduced content" XFDL-based submission.

-   Section 3 provides an overview of the six XFDL templates to which
    this specification applies.

-   Section 4 provides general rules concerning the XFDL file being
    created.

-   Section 5 details the specific rules for each type of XFDL node used
    to pass data to EDGAR.

-   Section 6 describes a means of verifying that the structure of an
    XFDL file is correct. For example, you can use the described
    technique to find a missing end tag.

-   Section 7 describes the many appendices to this specification and
    how to use them. These appendices provide all the details concerning
    how to create a specific SEC form, which templates create which form
    types, and the set of valid values for several input fields.

-   Section 8 provides several examples (at least one for each template)
    of reduced content submissions.

# XFDL Templates

The six XFDL templates to which this EDGAR Reduced Content XFDL Filing
Specification apply are:

  --------------- ----------------------- --------------------------------
  **EDGAR         **Filename on the EDGAR **Purpose**
  Template Name** Filing Web Site**       

  Template1       Subtemplate1.xfd        107 submission types

  Template2       Subtemplate2.xfd        120 submission types

  Template3       Subtemplate3.xfd        172 submission types

  Template4       Subtemplate4.xfd        CORRESPONDENCE submission

  Template5       Subtemplate5.xfd        MODULE or SEGMENT submission

  Template6       Subtemplate6.xfd        BULK submission
  --------------- ----------------------- --------------------------------

Template6 allows a filer to collect multiple XFDL files created with the
other five templates into a single bundle for a BULK submission. The
only constraint here is that one BULK submission cannot include another
BULK submission.

The controlled master versions of these templates that are available for
download on the EDGAR Filing Web Site. The master templates are saved in
a PureEdge proprietary compressed file format to improve file upload and
download efficiency and as a measure of security. As such, they cannot
be viewed or manipulated without the PureEdge Viewer. All submission
files created via the Viewer and the EDGAR templates are also saved in
this same proprietary compressed file format.

In addition, each template is composed of multiple "pages" denoted
within the template by XFDL page nodes. Section 5.3 of this
specification describes the standard page nodes that apply to each
template.

# Reduced Content File Format

Reduced content submissions must conform to the following file
formatting requirements.

a.  A reduced content XFDL submission file must be ASCII text in either
    DOS or UNIX format.

That is, lines must be terminated with either a carriage return and line
feed (\\r\\n) or with just a line feed (\\n). The PureEdge API does not
support the Macintosh format of just a carriage return (\\r). Do not
submit files with only carriage returns as end-of-line delineators.

b.  Because the PureEdge compression methodology is proprietary, you can
    only compress a reduced content submission by using the PureEdge
    Designer product.

When you use the Designer to compress a submission, use ASCII
compression rather than binary.

c.  A reduced content submission file cannot be digitally signed.

d.  A reduced content submission file name must end with either an .xfd,
    .xfdl, or .frm extension.

We recommend the .xfd extension, since several commercial software
products use the .frm file type (for example, Visual Basic). Under
Microsoft Windows, a user may find the .frm file type already registered
with another software program on his workstation.

e.  The names of attached document files must follow the internal EDGAR
    file naming convention. The file naming convention is:

-   File names can be no longer than 32 characters, including the file
    extension.

-   The following are valid characters:

```{=html}
<!-- -->
```
-   **Lowercase** letters

-   Digits 0-9

-   Up to one underscore

-   Up to one hyphen

-   Up to one period.

```{=html}
<!-- -->
```
-   The first character must be a letter.

-   Space characters are not allowed.

-   Each file name must have a file type extension.

-   File extensions must be .txt, .htm, .pdf, .fil, .jpg, .gif, .xml,
    and .xsd.

f.  Module and segment names referenced on PAGE4 of submissions must
    follow the internal EDGAR module/segment naming convention. The
    module/segment naming convention is:

-   The module/segment name must be no longer than 15 characters.

-   Valid characters are:

```{=html}
<!-- -->
```
-   **Uppercase** letters

-   Digits 0-9

-   Underscores

-   Hyphens (not periods)

```{=html}
<!-- -->
```
-   The first character must be a letter.

-   Space characters are not allowed.

g.  Date values can be specified in any of the following formats:

-   MM/DD/YY 10/10/01

-   MM/DD/YYYY 10/10/2001

-   MM-DD-YY 10-10-01

-   MM-DD-YYYY 10-10-2001

-   MMM DD, YY October 10, 01

-   MMM DD, YYYY October 10, 2001

# Reduced Content XFDL Elements

An XFDL scope identifier, or *sid*, uniquely identifies an element
within the scope of its logical parent. An XFDL element may have a *sid*
attribute which uniquely identifies the form within a system of forms in
a large deployment. A form may be composed of pages. Each page element
must have a *sid* attribute that uniquely identifies the page within the
surrounding XFDL form element. Pages may be composed of items. An item
element must have a *sid* attribute that uniquely identifies the item
within the surrounding page element. The minimal set of XFDL elements
required to create reduced content submissions are discussed in the
following sections. Other XFDL elements used in the master EDGAR XFDL
templates, such as those for GUI rendering, are not discussed in this
specification, and should not be provided when creating a reduced
content submission.

NOTE: The following reduced content element definitions use example data
to illustrate typical values. Remember to change these values as
required when creating your reduced content submissions. If EDGAR
restricts the value of a particular node, the list of valid values is
provided.

## VERSION NODES

Two version tags must be included as the first two lines of each
submission. These tags should not appear elsewhere in the submission.
The current valid values are:

\<?xml version=\"1.0\"?\>

\<XFDL version=\"5.0.0\"\>

## END XFDL NODE

To properly end a submission, this tag must be the last line of the
submission. This tag should not appear elsewhere in the submission.

\</XFDL\>

## PAGE NODES

The \<page\> nodes are critical to EDGAR processing and must be
included. The following table describes the data provided on each page
and provides a mapping of pages to EDGARLink templates. An "x" in the
cell indicates the page node is present in that template.

+----+----------+--------+--------+--------+--------+--------+--------+
| Pa | Des      | Tem    | Tem    | Tem    | Tem    | Tem    | Tem    |
| ge | cription | plate1 | plate2 | plate3 | plate4 | plate5 | plate6 |
|    |          |        |        |        |        |        |        |
|    |          |        |        |        | (C     | (M     | (Bulk) |
|    |          |        |        |        | orre-\ | odule/ |        |
|    |          |        |        |        | spon   | Se     |        |
|    |          |        |        |        | dence) | gment) |        |
+====+==========+========+========+========+========+========+========+
| 1  | Su       | x      | x      | x      | x      | x      |        |
|    | bmission |        |        |        |        |        |        |
|    | Header   |        |        |        |        |        |        |
|    | Data     |        |        |        |        |        |        |
+----+----------+--------+--------+--------+--------+--------+--------+
| 2  | Enclosed | x      | x      | x      | x      | x      | x      |
|    | D        |        |        |        |        |        |        |
|    | ocuments |        |        |        |        |        |        |
+----+----------+--------+--------+--------+--------+--------+--------+
| 3  | Noti     | x      | x      | x      | x      | x      |        |
|    | fication |        |        |        |        |        |        |
|    | Data     |        |        |        |        |        |        |
+----+----------+--------+--------+--------+--------+--------+--------+
| 4  | Module/  | x      | x      | x      | x      |        |        |
|    | Segment  |        |        |        |        |        |        |
|    | Re       |        |        |        |        |        |        |
|    | ferences |        |        |        |        |        |        |
+----+----------+--------+--------+--------+--------+--------+--------+
| 5  | Offset   | x      | x      |        |        |        |        |
|    | Payments |        |        |        |        |        |        |
|    | Data     |        |        |        |        |        |        |
+----+----------+--------+--------+--------+--------+--------+--------+
| 6  | Offering | x      | x      |        |        |        |        |
|    | Data     |        |        |        |        |        |        |
+----+----------+--------+--------+--------+--------+--------+--------+
| 7  | Sales    | x      |        |        |        |        |        |
|    | Shares   |        |        |        |        |        |        |
|    | Data     |        |        |        |        |        |        |
+----+----------+--------+--------+--------+--------+--------+--------+

The rules governing the \<page\> nodes are:

a.  Valid values for a \<page\> *sid* are "PAGE1", "PAGE2", "PAGE3",
    "PAGE4", "PAGE5", "PAGE6", and "PAGE7".

```{=html}
<!-- -->
```
h.  Pages must appear in sequential order, starting at PAGE1.

i.  All nodes except the two version nodes and the end XFDL node
    described in Sections 5.1 and 5.2 must be bounded by \<page sid= \>
    \</page\> nodes.

j.  You may completely exclude a page if none of the fields on that page
    contain any data.

For example, if an S-1 submission has no module or segment references,
the reduced content submission does not need to contain a PAGE4.

## VALID SCOPE (NODE) IDENTIFIERS

This section lists the valid node, or scope (*sid*), identifiers. Only
these *sid*s may be included in a submission. If any other *sid* is
detected during processing, EDGAR will suspend the submission.

### VALID EDGAR SCOPE IDENTIFIERS (*sid*s)

The following is a list of valid reduced content EDGAR scope
identifiers. Appendix II provides a more detailed breakout of the valid
*sid*s by Template and Page. The table provided here is an alphabetical
listing of the valid *sid*s.

  ------------------------------------- --------------------------------------
  ModSegReferenceData_ccc\_             SubInternet_internetAddress\_

  ModSegReferenceData_cik\_             SubItem_itemId\_

  ModSegReferenceData_documentType\_    SubModSeg_ModSegDescription\_

  ModSegReferenceData_modOrSegFlag\_    SubModSeg_ModSegFileName\_

  ModSegReferenceData_nickName\_        SubModSeg_ModSegMasterCIK\_

  SubCompany_fileNumber\_               SubModSeg_ModSegName\_

  SubCompany_filerId\_                  SubModSeg_ModSegType\_

  SubCompany_filerName\_                SubOffering_aggregatePrice\_

  SubCompany_irsNumber\_                SubOffering_offeringAmountPerShare\_

  SubContact_contactName\_              SubOffering_offeringShares\_

  SubContact_contactPhoneNumber\_       SubOffering_securityName\_

  SubCoreg_fileNumber\_                 SubOffset_offsetAmount\_

  SubCoreg_filerCcc\_                   SubOffset_offsetFileNumber\_

  SubCoreg_filerId\_                    SubOffset_offsetFilingDate\_

  SubCoreg_formType\_                   SubOffset_offsetForm\_

  SubDate_effectivenessDateOfReport\_   SubOffset_offsetId\_

  SubDocument_conformedDocumentType\_   SubPayor_payorCcc\_

  SubDocument_conformedName\_           SubPayor_payorId\_

  SubDocument_description\_             SubRef429_fileNumber\_

  SubFee_feeAmount\_                    SubSalesShares_redeemedValue\_

  SubFee_feeBasis\_                     SubSalesShares_salesProceeds\_

  SubFee_paymentMethod\_                SubSalesShares_series\_

  SubFiler_fileNumber\_                 SubSerial_companyName\_

  SubFiler_filerCcc\_                   SubSro_sroId\_

  SubFiler_filerId\_                    SubTable_act\_

  SubFiler_filerRelationship\_          SubTable_depositorCik\_

  SubFiler_formType\_                   SubTable_depositorFileNumber\_

  SubFlag_confirmingCopyFlag\_          SubTable_depository\_

  SubFlag_delayingAmendmentFlag\_       SubTable_fiscalYear\_

  SubFlag_overrideInternetFlag\_        SubTable_itemSubmissionType\_

  SubFlag_returnCopyFlag\_              SubTable_live\_

  SubFlag_serialFlag\_                  SubTable_periodOfReport\_

  SubGlobal_enclosedFileCount\_         SubTable_reference462b\_

  SubGroup_groupName\_                  SubTable_submissionType\_
  ------------------------------------- --------------------------------------

## SUBMISSION DATA NODES

All data related to the submission is stored in five types of XFDL
nodes. These five node types are:

  ------------------ ----------------------------------------------------
  **Node Type**      **Description**

  \<field\>          Text Field in the Viewer and/or the EDGARLink
                     template

  \<check\>          Checkbox in the Viewer and/or the EDGARLink template

  \<radio\>          Radio Button in the Viewer and/or the EDGARLink
                     template

  \<popup\>          Popup in the Viewer and/or the EDGARLink template

  \<combobox\>       Combo Box in the Viewer and/or the EDGARLink
                     template
  ------------------ ----------------------------------------------------

The rules for specifying one of these nodes are:

a.  EDGAR parsing is case-sensitive. You must use the *sid* names and
    valid values exactly as they are prescribed in the appendices and
    the attached master templates when constructing these nodes.

```{=html}
<!-- -->
```
k.  A node must have a unique *sid* and a \<value\>.

\<combobox
sid="SubTable_submissionType\_"\>\<value\>S-1\</value\>\</combobox\>

l.  The \<value\> tag is optional if a field has no value. However, we
    suggest including the \<value\>\</value\> tag for consistency.

m.  A \<value\> tag may only contain a single data item.

n.  The *sid* for these nodes must be of the form:

className_tagName_recordNumber

The className and tagName portions must exactly match the names provided
in the Appendices and the underscores must always be present. Append the
recordNumber to a *sid* only when you need to report multiple values for
a particular category of data, e.g., SRO values. The recordNumber is
simply an increasing integer number used to uniquely identify the
multiple values for a particular field. The first instance of any field
does not get a recordNumber; zero is implied. The second instance gets a
recordNumber of 1, the third instance a recordNumber of 2, and so on. A
couple of examples will make this clear.

Example 1:

For a field that has only a single value, such as the Submission Type
combobox, the *sid* for the node will not have a recordNumber component.
For this example, the node *sid* (field name) will be:

SubTable_submissionType\_ (the trailing underscore must be present)

Example 2:

To report multiple values for a particular field, use the recordNumber
to differentiate these values. For example, to report three SRO values,
you would create these three node *sid*s:

SubSro_sroId\_

SubSro_sroId_1

SubSro_sroId_2

o.  White space between nodes is ignored. These two specifications are
    equivalent.

\<field
sid="SubTable_submissionType\_"\>\<value\>S-1\</value\>\</field\>

\<field sid="SubTable_submissionType\_"\>

\<value\>S-1\</value\>

\</field\>

For human readability of the XFDL, the latter case is preferred.

p.  The order of the nodes within a page only matters in two cases.

    1.  For enclosed documents in Templates 1, 2, 3, 4, and 6,
        SubDocument_conformedName\_ must precede the document's \<data\>
        node.

    2.  For enclosed documents in Template 5,

> SubModSeg_ModSegFileName\_ must precede the document's \<data\> node.

q.  The ampersand (&) and left angle bracket (\<) are not permitted in
    character data content of XML elements. If there is a need to
    include these characters in character data, such as a value, you
    must enclose the character data in an XML CDATA section. For
    example, a value for a form name which contains an embedded
    ampersand would need to be expressed as:

\<value\>\<\![CDATA\[EX-99.2I O&D BENEFTS\]\]\>\</value\>

## FIELD NODES

The only information required for a \<field\> node is a valid name and
\<value\>. Appendix II lists all valid text field names.

\<field sid=\"SubFiler_filerId\_\"\>

\<value\>0000000129\</value\>

\</field\>

## CHECKBOX NODES

The only information required for a \<check\> node is a valid name and a
\<value\>. Appendix II lists all valid checkbox names. It is recommended
that you always include a \<value\> tag for consistency. This prevents a
scenario where a checkbox is mandatory but the user provides no value.
The only valid values for a \<check\> node are "on" and "off".

\<check sid=\"SubFlag_confirmingCopyFlag\_\"\>

\<value\>on\</value\>

\</check\>

## RADIO BUTTON NODES

The minimum information required for a \<radio\> node is a valid name
and \<value\>. The only radio button in any of the templates is used to
indicate if the submission is LIVE or TEST. A value of "on" means it is
a LIVE submission. A value of "off" means it is a TEST submission. It is
recommended that you always include a \<value\> tag for consistency. The
only valid values for a \<radio\> node are "on" and "off".

\<radio sid=\" SubTable_live\_\"\>

\<value\>on\</value\>

\</radio\>

## POPUP NODES

The only information required for a \<popup\> node is a valid name and
\<value\>. Appendices IX--XIII list the valid values for all \<popup\>
nodes.

\<popup sid=\"SubFiler_formType\_\"\>

\<value\>S-1\</value\>

\</popup\>

## COMBOBOX NODES

The only information required for a \<combobox\> node is a valid name
and \<value\>. Appendices IX--XIII list the valid values for all
\<combobox\> nodes.

\<combobox sid=\"SubTable_submissionType\_\"\>

\<value\>S-4EF/A\</value\>

\</combobox\>

## DATA NODES -- (ENCLOSED DOCUMENTS)

Each document enclosed on Page 2 of the submission must have a \<data\>
node of the following format:

> \<data sid=\"data1\"\>
>
> \<filename\>cover.txt\</filename\>
>
> \<mimedata\>
>
> VGhpcyBpcyBteSBjb3ZlciBsZXR0ZXIuDQpJdCBpcyBmb3IgYS
>
> B0ZXN0IG9mIGEgY29ycmVzcG9uZGVuY2Ugc3VibWlzc2lvbi4N
>
> Cg0KSSBob3BlIHRoaXMgd29ya3Mu
>
> \</mimedata\>
>
> \</data\>

You may supply whatever you want as the *sid* for a data node, just as
long as it is a valid XML name and it is unique to PAGE2 of the
submission.

The \<filename\> is really the key item when defining a data node. It is
the link to the SubDocument_conformedName\_ or
SubModSeg_ModSegFileName\_ field that corresponds to this data node.

The \<mimedata\> block contains the MIME encoded document. A document
must be encoded before you put it into the submission file. The MIME
algorithm used by the PureEdge product is not proprietary, so any
standard 64-character set based MIME encoding algorithm can be used.

Section 8.7 of this specification provides a sample CORRESP submission
with one enclosed document. Section 8.9 provides a sample BULK
submission with three enclosed documents. In the case of a bulk
submission using Template6, each enclosed MIME document is a complete
XFDL submission file.

# Verifying Reduced Content Structure

To verify that a Reduced Content submission file does not contain any
structural errors, you can simply take advantage of the fact that the
file is really XML. To verify the content:

a.  Rename the file, giving it an .xml suffix.

```{=html}
<!-- -->
```
r.  Open the file in your browser.

s.  If the file contains structural errors, the browser will give you
    the offending line numbers.

Other commercially-available XML development tools can be used to
identify syntax errors in your submission file.

# How to use THE Appendices

This specification contains several appendices that define what is
required for each electronic SEC form.

a.  Appendix I is a mapping of all EDGAR form types to the EDGARLink
    submission templates.

```{=html}
<!-- -->
```
t.  Appendix II is a complete list of all the unique *sid*s used in the
    six submission templates. This list also provides, for each *sid*,
    the node type (field, popup, combobox, check, or radio), a mapping
    of the node to the template(s) that use it, and whether the node is
    repeatable.

> **NOTE:** You should never have a *sid* that is not in this list in a
> reduced content submission file.

u.  Appendices III through VIII show which PAGE1 header fields, or
    *sid*s, are applicable to each form type for Templates 1 through 6.

  ------------------------ ----------------------------------------------
  Appendix III             Template1 form-type field dependencies

  Appendix IV              Template2 form-type field dependencies

  Appendix V               Template3 form-type field dependencies

  Appendix VI              Template4 form-type field dependencies

  Appendix VII             Template5 form-type field dependencies

  Appendix VIII            Template6 form-type field dependencies
  ------------------------ ----------------------------------------------

The following table explains the numeric codes that appear in the
matrices in these six appendices.

  ----------- -----------------------------------------------------------
  **Code**    **Status**

  1           Required

  2           Conditionally Required (if any field in group has a value,
              all fields in the group must have a value)

  3           When specifying a SubOffering entry, both the securityName
              and aggregatePrice are Required. The offeringShares and
              offeringAmountPerShare fields are optional.

  4           Optional

  5           Required for a confirming copy submission (i.e., for
              electronic submissions which are copies of official filings
              previously made in paper under a hardship exemption)

  6           Required for all serial companies
  ----------- -----------------------------------------------------------

The fields in Appendix II that have one of these numbers assigned are
not included in Appendices III through VIII. These appendices indicate
which of a template's conditional fields are applicable to each form
type handled by the template.

To determine the complete set of valid *sid*s for a given form type, you
must refer to both Appendix II as well as one of these template-specific
Appendices.

v.  Appendices IX through XIII show the valid values for the \<field\>,
    \<combobox\>, and \<popup\> nodes that are limited to a set of
    prescribed values.

  ------------------------ ----------------------------------------------
  Appendix IX              Template1 choice lists

  Appendix X               Template2 choice lists

  Appendix XI              Template3 choice lists

  Appendix XII             Template4 choice lists

  Appendix XIII            Template5 choice lists
  ------------------------ ----------------------------------------------

# Sample Forms

The sample reduced content submissions in this section demonstrate
submissions constructed following the guidelines in this specification.
There is at least one example for each of the six submission templates.
All data in these examples is fictitious. These examples only include
*sid*s which are applicable to the given submission type.

## Sample 24F-2NT from Subtemplate1.xfd

This is an example of a fee-bearing submission. The example excludes
pages with no data. PAGE3, PAGE4, PAGE5, and PAGE6 are entirely absent.

\<?xml version=\"1.0\"?\>

\<XFDL version=\"5.0.0\"\>

\<page sid=\"PAGE1\"\>

\<combobox
sid=\"SubTable_submissionType\_\"\>\<value\>24F-2NT\</value\>\</combobox\>

\<check
sid=\"SubFlag_confirmingCopyFlag\_\"\>\<value\>on\</value\>\</check\>

\<radio sid=\"SubTable_live\_\"\>\<value\>on\</value\>\</radio\>

\<check
sid=\"SubFlag_returnCopyFlag\_\"\>\<value\>off\</value\>\</check\>

\<check
sid=\"SubFlag_delayingAmendmentFlag\_\"\>\<value\>off\</value\>\</check\>

\<field
sid=\"SubFiler_filerId\_\"\>\<value\>0101010101\</value\>\</field\>

\<field
sid=\"SubFiler_filerCcc\_\"\>\<value\>a#ofcorn\</value\>\</field\>

\<field
sid=\"SubFiler_fileNumber\_\"\>\<value\>033-04577\</value\>\</field\>

\<field sid=\"SubContact_contactName\_\"\>\<value\>Joe
Filer\</value\>\</field\>

\<field
sid=\"SubContact_contactPhoneNumber\_\"\>\<value\>br549\</value\>\</field\>

\<popup sid=\"SubSro_sroId\_\"\>\<value\>AMEX\</value\>\</popup\>

\<field
sid=\"SubTable_periodOfReport\_\"\>\<value\>11/8/2000\</value\>\</field\>

\</page\>

\<page sid=\"PAGE2\"\>

\<field
sid=\"SubDocument_conformedName\_\"\>\<value\>primary.txt\</value\>\</field\>

\<combobox sid=\"SubDocument_conformedDocumentType\_\"\>

\<value\>24F-2NT\</value\>\</combobox\>

\<field sid=\"SubDocument_description\_\"\>\<value\>primary
document\</value\>\</field\>

\<data sid=\"data1\"\>

\<filename\>primary.txt\</filename\>

\<mimedata\>

U1BFQ0lNRU4gLSBUSElTIElTIEEgVEVTVCAtIE5PVCBBIExFR0

FMIEZJTElORyANCg0KKioqKioqKioqKioqKioqKioqKioqKioq

KioqKioqKioqKioqKioqKioqKioqKioqKioqKioqKioqKioqKi

oqKioqKioqDQo=

\</mimedata\>

\</data\>

\</page\>

\<page sid=\"PAGE7\"\>

\<field
sid=\"SubPayor_payorId\_\"\>\<value\>0101010101\</value\>\</field\>

\<field sid=\"SubPayor_payorCcc\_\"\>\<value\> a#ofcorn
\</value\>\</field\>

\<combobox
sid=\"SubFee_paymentMethod\_\"\>\<value\>LOCKBOX\</value\>\</combobox\>

\<field sid=\"SubFee_feeAmount\_\"\>\<value\>7.58\</value\>\</field\>

\<field
sid=\"SubSalesShares_salesProceeds\_\"\>\<value\>100000\</value\>\</field\>

\<field
sid=\"SubSalesShares_redeemedValue\_\"\>\<value\>7500\</value\>\</field\>

\</page\>

\</XFDL\>

## Sample S-1 from Subtemplate1.xfd

This is another example of a fee-bearing submission. Note that it also
excludes pages with no data.

\<?xml version=\"1.0\"?\>

\<XFDL version=\"5.0.0\"\>

\<page sid=\"PAGE1\"\>

\<combobox
sid=\"SubTable_submissionType\_\"\>\<value\>S-1\</value\>\</combobox\>

\<check
sid=\"SubFlag_confirmingCopyFlag\_\"\>\<value\>off\</value\>\</check\>

\<radio sid=\"SubTable_live\_\"\>\<value\>on\</value\>\</radio\>

\<check
sid=\"SubFlag_returnCopyFlag\_\"\>\<value\>off\</value\>\</check\>

\<check
sid=\"SubFlag_delayingAmendmentFlag\_\"\>\<value\>off\</value\>\</check\>

\<field
sid=\"SubFiler_filerId\_\"\>\<value\>0101010101\</value\>\</field\>

\<field
sid=\"SubFiler_filerCcc\_\"\>\<value\>a#ofcorn\</value\>\</field\>

\<field sid=\"SubContact_contactName\_\"\>\<value\>Joe
Filer\</value\>\</field\>

\<field
sid=\"SubContact_contactPhoneNumber\_\"\>\<value\>br549\</value\>\</field\>

\<popup sid=\"SubSro_sroId\_\"\>\<value\>AMEX\</value\>\</popup\>

\</page\>

\<page sid=\"PAGE2\"\>

\<field
sid=\"SubDocument_conformedName\_\"\>\<value\>primary.txt\</value\>\</field\>

\<combobox sid=\"SubDocument_conformedDocumentType\_\"\>

\<value\>S-1\</value\>\</combobox\>

\<field sid=\"SubDocument_description\_\"\>\<value\>primary
document\</value\>\</field\>

\<data sid=\"data1\"\>

\<filename\>primary.txt\</filename\>

\<mimedata\>

U1BFQ0lNRU4gLSBUSElTIElTIEEgVEVTVCAtIE5PVCBBIExFR0

FMIEZJTElORyANCg0KKioqKioqKioqKioqKioqKioqKioqKioq

KioqKioqKioqKioqKioqKioqKioqKioqKioqKioqKioqKioqKi

oqKioqKioqDQo=

\</mimedata\>

\</data\>

\</page\>

\<page sid=\"PAGE6\"\>

\<field
sid=\"SubPayor_payorId\_\"\>\<value\>0101010101\</value\>\</field\>

\<field sid=\"SubPayor_payorCcc\_\"\>\<value\> a#ofcorn
\</value\>\</field\>

\<combobox
sid=\"SubFee_paymentMethod\_\"\>\<value\>LOCKBOX\</value\>\</combobox\>

\<field sid=\"SubFee_feeAmount\_\"\>\<value\>6.56\</value\>\</field\>

\<combobox
sid=\"SubOffering_securityName\_\"\>\<value\>Equity\</value\>\</combobox\>

\<field
sid=\"SubOffering_offeringShares\_\"\>\<value\>2000\</value\>\</field\>

\<field
sid=\"SubOffering_offeringAmountPerShare\_\"\>\<value\>40.00\</value\>\</field\>

\<field
sid=\"SubOffering_aggregatePrice\_\"\>\<value\>80000.00\</value\>\</field\>

\</page\>

\</XFDL\>

## Sample N-1 from Subtemplate1.xfd

This is an example of a non-fee-bearing submission.

\<?xml version=\"1.0\"?\>

\<XFDL version=\"5.0.0\"\>

\<page sid=\"PAGE1\"\>

\<combobox
sid=\"SubTable_submissionType\_\"\>\<value\>N-1\</value\>\</combobox\>

\<check
sid=\"SubFlag_confirmingCopyFlag\_\"\>\<value\>on\</value\>\</check\>

\<radio sid=\"SubTable_live\_\"\>\<value\>on\</value\>\</radio\>

\<check
sid=\"SubFlag_returnCopyFlag\_\"\>\<value\>off\</value\>\</check\>

\<check
sid=\"SubFlag_delayingAmendmentFlag\_\"\>\<value\>on\</value\>\</check\>

\<field
sid=\"SubFiler_filerId\_\"\>\<value\>0101010101\</value\>\</field\>

\<field
sid=\"SubFiler_filerCcc\_\"\>\<value\>a#ofcorn\</value\>\</field\>

\<field
sid=\"SubFiler_fileNumber\_\"\>\<value\>333-30266\</value\>\</field\>

\<field
sid=\"SubCoreg_filerId\_\"\>\<value\>2020202020\</value\>\</field\>

\<field
sid=\"SubCoreg_filerCcc\_\"\>\<value\>a#ofbeef\</value\>\</field\>

\<field
sid=\"SubCoreg_fileNumber\_\"\>\<value\>033-04577\</value\>\</field\>

\<field
sid=\"SubContact_contactName\_\"\>\<value\>JoeFiler\</value\>\</field\>

\<field
sid=\"SubContact_contactPhoneNumber\_\"\>\<value\>123-456-7890\</value\>\</field\>

\<combobox sid=\"SubTable_act\_\"\>\<value\>33\</value\>\</combobox\>

\<field
sid=\"SubRef429_fileNumber\_\"\>\<value\>333-30266\</value\>\</field\>

\<popup sid=\"SubSro_sroId\_\"\>\<value\>AMEX\</value\>\</popup\>

\</page\>

\<page sid=\"PAGE2\"\>

\<field
sid=\"SubDocument_conformedName\_\"\>\<value\>doc01.txt\</value\>\</field\>

\<combobox
sid=\"SubDocument_conformedDocumentType\_\"\>\<value\>N-1\</value\>\</combobox\>

\<field
sid=\"SubDocument_description\_\"\>\<value\>doc1\</value\>\</field\>

\<data sid=\"data1\"\>

\<filename\>doc01.txt\</filename\>

\<mimedata\>

U1BFQ0lNRU4gLSBUSElTIElTIEEgVEVTVCAtIE5PVCBBIExFR0

FMIEZJTElORyANCg0KKioqKioqKioqKioqKioqKioqKioqKioq

KioqKioqKioqKioqKioqKioqKioqKioqKioqKioqKioqKioqKi

oqKioqKioqDQo=

\</mimedata\>

\</data\>

\<field
sid=\"SubDocument_conformedName_1\"\>\<value\>cover01.txt\</value\>\</field\>

\<combobox
sid=\"SubDocument_conformedDocumentType_1\"\>\<value\>COVER\</value\>\</combobox\>

\<field
sid=\"SubDocument_description_1\"\>\<value\>doc2\</value\>\</field\>

\<data sid=\"data2\"\>

\<filename\>cover01.txt\</filename\>

\<mimedata\>

U1BFQ0lNRU4gLSBUSElTIElTIEEgVEVTVCAtIE5PVCBBIExFR0

FMIEZJTElORyANCg0KKioqKioqKioqKioqKioqKioqKioqKioq

KioqKioqKioqKioqKioqKioqKioqKioqKioqKioqKioqKioqKi

oqKioqKioqDQo=

\</mimedata\>

\</data\>

\</page\>

\<page sid=\"PAGE3\"\>

\<field
sid=\"SubInternet_internetAddress\_\"\>\<value\>joefiler@mailme.com\</value\>\</field\>

\</page\>

\</XFDL\>

## Sample 144 submission from Subtemplate2.xfd

This is an example of a Subject Company/Ownership filing that references
a previously uploaded Module submission on PAGE4.

\<?xml version=\"1.0\"?\>

\<XFDL version=\"5.0.0\"\>

\<page sid=\"PAGE1\"\>

\<combobox
sid=\"SubTable_submissionType\_\"\>\<value\>144\</value\>\</combobox\>

\<radio sid=\"SubTable_live\_\"\>\<value\>on\</value\>\</radio\>

\<check
sid=\"SubFlag_returnCopyFlag\_\"\>\<value\>off\</value\>\</check\>

\<field
sid=\"SubFiler_filerId\_\"\>\<value\>2020202020\</value\>\</field\>

\<field
sid=\"SubFiler_filerCcc\_\"\>\<value\>a#ofbeef\</value\>\</field\>

\<field sid=\"SubFiler_fileNumber\_\"\>\<value\>\</value\>\</field\>

\<combobox
sid=\"SubFiler_filerRelationship\_\"\>\<value\>OWNER\</value\>\</combobox\>

\<popup sid=\"SubFiler_formType\_\"\>\<value\>\</value\>\</popup\>

\<field
sid=\"SubCompany_filerId\_\"\>\<value\>0101010101\</value\>\</field\>

\<field
sid=\"SubCompany_irsNumber\_\"\>\<value\>12-3456789\</value\>\</field\>

\<field sid=\"SubCompany_fileNumber\_\"\>\<value\>\</value\>\</field\>

\<field sid=\"SubCompany_filerName\_\"\>\<value\>Acme
Inc\</value\>\</field\>

\<field sid=\"SubContact_contactName\_\"\>\<value\>Joe
Filer\</value\>\</field\>

\<field
sid=\"SubContact_contactPhoneNumber\_\"\>\<value\>br549\</value\>\</field\>

\<popup sid=\"SubSro_sroId\_\"\>\<value\>AMEX\</value\>\</popup\>

\</page\>

\<page sid=\"PAGE2\"\>

\<field
sid=\"SubDocument_conformedName\_\"\>\<value\>primary.txt\</value\>\</field\>

\<combobox
sid=\"SubDocument_conformedDocumentType\_\"\>\<value\>144\</value\>\</combobox\>

\<field sid=\"SubDocument_description\_\"\>\<value\>primary
document\</value\>\</field\>

\<data sid=\"data1\"\>

\<filename\>primary.txt\</filename\>

\<mimedata\>

PT09PT09PT09PT09PT09PT09PT09PT09PT09PT09PT09PT09PT09PQ0KPT0g

VGhpcyBpcyBhIGR1bW15IEFTQ0lJIGRvY3VtZW50IGZvciA9PQ0KPT0gdGhl

IFJlZHVjZWQgQ29udGVudCBTcGVjaWZpY2F0aW9uLiA9PQ0KPT09PT09PT09

PT09PT09PT09PT09PT09PT09PT09PT09PT09PT09PQ==

\</mimedata\>

\</data\>

\</page\>

\<page sid=\"PAGE3\"\>

\<field
sid=\"SubInternet_internetAddress\_\"\>\<value\>joefiler@mailme.com\</value\>\</field\>

\<check
sid=\"SubFlag_overrideInternetFlag\_\"\>\<value\>on\</value\>\</check\>

\</page\>

\<page sid=\"PAGE4\"\>

\<popup
sid=\"ModSegReferenceData_modOrSegFlag\_\"\>\<value\>M\</value\>\</popup\>

\<field
sid=\"ModSegReferenceData_nickName\_\"\>\<value\>MOD2020202020-1\</value\>\</field\>

\<field
sid=\"ModSegReferenceData_cik\_\"\>\<value\>2020202020\</value\>\</field\>

\<field
sid=\"ModSegReferenceData_ccc\_\"\>\<value\>a#ofbeef\</value\>\</field\>

\<combobox
sid=\"ModSegReferenceData_documentType\_\"\>\<value\>EX-3\</value\>\</combobox\>

\</page\>

\</XFDL\>

## Sample PREM14A submission from Subtemplate2.xfd

This is an example of a fee-bearing submission with multiple offsets.

\<?xml version=\"1.0\"?\>

\<XFDL version=\"5.0.0\"\>

\<page sid=\"PAGE1\"\>

\<combobox
sid=\"SubTable_submissionType\_\"\>\<value\>PREM14A\</value\>\</combobox\>

\<check
sid=\"SubFlag_confirmingCopyFlag\_\"\>\<value\>off\</value\>\</check\>

\<radio sid=\"SubTable_live\_\"\>\<value\>on\</value\>\</radio\>

\<check
sid=\"SubFlag_returnCopyFlag\_\"\>\<value\>off\</value\>\</check\>

\<field
sid=\"SubFiler_filerId\_\"\>\<value\>0101010101\</value\>\</field\>

\<field
sid=\"SubFiler_filerCcc\_\"\>\<value\>a#ofcorn\</value\>\</field\>

\<field
sid=\"SubCoreg_filerId\_\"\>\<value\>2020202020\</value\>\</field\>

\<field
sid=\"SubCoreg_filerCcc\_\"\>\<value\>a#ofbeef\</value\>\</field\>

\<field
sid=\"SubContact_contactName\_\"\>\<value\>JoeFiler\</value\>\</field\>

\<field
sid=\"SubContact_contactPhoneNumber\_\"\>\<value\>123-456-7890\</value\>\</field\>

\<field
sid=\"SubTable_periodOfReport\_\"\>\<value\>1/1/02\</value\>\</field\>

\<popup sid=\"SubSro_sroId\_\"\>\<value\>AMEX\</value\>\</popup\>

\</page\>

\<page sid=\"PAGE2\"\>

\<field
sid=\"SubDocument_conformedName\_\"\>\<value\>doc01.txt\</value\>\</field\>

\<combobox
sid=\"SubDocument_conformedDocumentType\_\"\>\<value\>PREM14A\</value\>\</combobox\>

\<data sid=\"data1\"\>

\<filename\>doc01.txt\</filename\>

\<mimedata\>

PT09PT09PT09PT09PT09PT09PT09PT09PT09PT09PT09PT09PT09PQ0KPT0g

VGhpcyBpcyBhIGR1bW15IEFTQ0lJIGRvY3VtZW50IGZvciA9PQ0KPT0gdGhl

IFJlZHVjZWQgQ29udGVudCBTcGVjaWZpY2F0aW9uLiA9PQ0KPT09PT09PT09

PT09PT09PT09PT09PT09PT09PT09PT09PT09PT09PQ==

\</mimedata\>

\</data\>

\</page\>

\<page sid=\"PAGE5\"\>

\<field
sid=\"SubOffset_offsetId\_\"\>\<value\>0101010101\</value\>\</field\>

\<combobox
sid=\"SubOffset_offsetForm\_\"\>\<value\>F-1\</value\>\</combobox\>

\<field
sid=\"SubOffset_offsetFileNumber\_\"\>\<value\>333-32068\</value\>\</field\>

\<field
sid=\"SubOffset_offsetFilingDate\_\"\>\<value\>5/15/2001\</value\>\</field\>

\<field
sid=\"SubOffset_offsetAmount\_\"\>\<value\>5.00\</value\>\</field\>

\<field
sid=\"SubOffset_offsetId_1\"\>\<value\>2020202020\</value\>\</field\>

\<combobox
sid=\"SubOffset_offsetForm_1\"\>\<value\>F-2\</value\>\</combobox\>

\<field
sid=\"SubOffset_offsetFileNumber_1\"\>\<value\>333-12345\</value\>\</field\>

\<field
sid=\"SubOffset_offsetFilingDate_1\"\>\<value\>6/21/2001\</value\>\</field\>

\<field
sid=\"SubOffset_offsetAmount_1\"\>\<value\>3.00\</value\>\</field\>

\</page\>

\<page sid=\"PAGE6\"\>

\<field
sid=\"SubPayor_payorId\_\"\>\<value\>0000303030\</value\>\</field\>

\<field
sid=\"SubPayor_payorCcc\_\"\>\<value\>a#ofdirt\</value\>\</field\>

\<combobox
sid=\"SubFee_paymentMethod\_\"\>\<value\>LOCKBOX\</value\>\</combobox\>

\<field sid=\"SubFee_feeAmount\_\"\>\<value\>10.00\</value\>\</field\>

\<field sid=\"SubFee_feeBasis\_\"\>\<value\>50000\</value\>\</field\>

\</page\>

\</XFDL\>

## Sample 10-12B from Subtemplate3.xfd

This example shows two SEGMENT and one MODULE references on PAGE4.
Notice that the CIK and CCC fields should not be included for a SEGMENT
reference.

\<?xml version=\"1.0\"?\>

\<XFDL version=\"5.0.0\"\>

\<page sid=\"PAGE1\"\>

\<combobox
sid=\"SubTable_submissionType\_\"\>\<value\>10-12B\</value\>\</combobox\>

\<check
sid=\"SubFlag_confirmingCopyFlag\_\"\>\<value\>off\</value\>\</check\>

\<radio sid=\"SubTable_live\_\"\>\<value\>on\</value\>\</radio\>

\<check
sid=\"SubFlag_returnCopyFlag\_\"\>\<value\>off\</value\>\</check\>

\<field
sid=\"SubFiler_filerId\_\"\>\<value\>2020202020\</value\>\</field\>

\<field
sid=\"SubFiler_filerCcc\_\"\>\<value\>a#ofbeef\</value\>\</field\>

\<field
sid=\"SubCoreg_filerId\_\"\>\<value\>0101010101\</value\>\</field\>

\<field
sid=\"SubCoreg_filerCcc\_\"\>\<value\>a#ofcorn\</value\>\</field\>

\<field sid=\"SubContact_contactName\_\"\>\<value\>Joe
Filer\</value\>\</field\>

\<field
sid=\"SubContact_contactPhoneNumber\_\"\>\<value\>br549\</value\>\</field\>

\<popup sid=\"SubSro_sroId\_\"\>\<value\>AMEX\</value\>\</popup\>

\</page\>

\<page sid=\"PAGE2\"\>

\<field
sid=\"SubDocument_conformedName\_\"\>\<value\>cover.txt\</value\>\</field\>

> \<combobox sid=\"SubDocument_conformedDocumentType\_\"\>
>
> \<value\>10-12B\</value\>\</combobox\>

\<field sid=\"SubDocument_description\_\"\>\<value\>doc
one\</value\>\</field\>

\<data sid=\"data1\"\>

\<filename\>primary.htm\</filename\>

\<mimedata\>

U1BFQ0lNRU4gLSBUSElTIElTIEEgVEVTVCAtIE5PVCBBIExFR0

AgICAgICAgICAgICAgICAgIEZPUk0gWFhYWFhYWA0KDQoqKioq

KioqKioqKioqKioqKioqKioqKioqKioqKioqKioqKioqKioqKi

oqKioqKioqDQo=

\</mimedata\>

\</data\>

\</page\>

\<page sid=\"PAGE3\"\>

\<field
sid=\"SubInternet_internetAddress\_\"\>\<value\>\</value\>\</field\>

\<check
sid=\"SubFlag_overrideInternetFlag\_\"\>\<value\>on\</value\>\</check\>

\</page\>

\<page sid=\"PAGE4\"\>

\<popup
sid=\"ModSegReferenceData_modOrSegFlag\_\"\>\<value\>S\</value\>\</popup\>

\<field
sid=\"ModSegReferenceData_nickName\_\"\>\<value\>SEG2020202020-1\</value\>\</field\>

\<combobox
sid=\"ModSegReferenceData_documentType\_\"\>\<value\>EX-1\</value\>\</combobox\>

\<popup
sid=\"ModSegReferenceData_modOrSegFlag_1\"\>\<value\>S\</value\>\</popup\>

\<field
sid=\"ModSegReferenceData_nickName_1\"\>\<value\>SEG2020202020-2\</value\>\</field\>

\<combobox
sid=\"ModSegReferenceData_documentType_1\"\>\<value\>EX-2\</value\>\</combobox\>

\<popup
sid=\"ModSegReferenceData_modOrSegFlag_2\"\>\<value\>M\</value\>\</popup\>

\<field
sid=\"ModSegReferenceData_nickName_2\"\>\<value\>MOD0101010101-1\</value\>\</field\>

\<field
sid=\"ModSegReferenceData_cik_2\"\>\<value\>0101010101\</value\>\</field\>

\<field
sid=\"ModSegReferenceData_ccc_2\"\>\<value\>a#ofcorn\</value\>\</field\>

\<combobox
sid=\"ModSegReferenceData_documentType_2\"\>\<value\>EX-3\</value\>\</combobox\>

\</page\>

\</XFDL\>

## Sample CORRESP from Subtemplate4.xfd

This is an example of a correspondence submission as defined by Template
4.

\<?xml version=\"1.0\"?\>

\<XFDL version=\"5.0.0\"\>

\<page sid=\"PAGE1\"\>

\<combobox
sid=\"SubTable_submissionType\_\"\>\<value\>CORRESP\</value\>\</combobox\>

\<radio sid=\"SubTable_live\_\"\>\<value\>on\</value\>\</radio\>

\<check
sid=\"SubFlag_returnCopyFlag\_\"\>\<value\>on\</value\>\</check\>

\<field
sid=\"SubFiler_filerId\_\"\>\<value\>2020202020\</value\>\</field\>

\<field
sid=\"SubFiler_filerCcc\_\"\>\<value\>a#ofbeef\</value\>\</field\>

\<field sid=\"SubCoreg_filerId\_\"\>\<value\>\</value\>\</field\>

\<field sid=\"SubCoreg_filerCcc\_\"\>\<value\>\</value\>\</field\>

\<field sid=\"SubContact_contactName\_\"\>\<value\>Joe
Filer\</value\>\</field\>

\<field
sid=\"SubContact_contactPhoneNumber\_\"\>\<value\>br549\</value\>\</field\>

\</page\>

\<page sid=\"PAGE2\"\>

\<field
sid=\"SubDocument_conformedName\_\"\>\<value\>corresp1.txt\</value\>\</field\>

\<combobox sid=\"SubDocument_conformedDocumentType\_\"\>

\<value\>CORRESP\</value\>\</combobox\>

\<field sid=\"SubDocument_description\_\"\>\<value\>first
document\</value\>\</field\>

\<data sid=\"data1\"\>

\<filename\>corresp1.txt\</filename\>

\<mimedata\>

PT09PT09PT09PT09PT09PT09PT09PT09PT09PT09ICAgY29ycm

09PT09PT09PT09PT0NCg==

\</mimedata\>

\</data\>

\</page\>

\<page sid=\"PAGE3\"\>

\<field
sid=\"SubInternet_internetAddress\_\"\>\<value\>joefiler@mailme.com\</value\>\</field\>

\<check
sid=\"SubFlag_overrideInternetFlag\_\"\>\<value\>off\</value\>\</check\>

\</page\>

\</XFDL\>

## Sample MODULE from Subtemplate5.xfd

This example shows how to submit a Type 1 and a Type 2 MODULE document
as defined by Template 5.

\<?xml version=\"1.0\"?\>

\<XFDL version=\"5.0.0\"\>

\<page sid=\"PAGE1\"\>

\<combobox
sid=\"SubTable_submissionType\_\"\>\<value\>MODULE\</value\>\</combobox\>

\<field sid=\"SubContact_contactName\_\"\>\<value\>Joe
Filer\</value\>\</field\>

\<field
sid=\"SubContact_contactPhoneNumber\_\"\>\<value\>br549\</value\>\</field\>

\<field
sid=\"SubFiler_filerId\_\"\>\<value\>2020202020\</value\>\</field\>

\<field
sid=\"SubFiler_filerCcc\_\"\>\<value\>a#ofbeef\</value\>\</field\>

\<radio sid=\"SubTable_live\_\"\>\<value\>off\</value\>\</radio\>

\<check
sid=\"SubFlag_returnCopyFlag\_\"\>\<value\>off\</value\>\</check\>

\</page\>

\<page sid=\"PAGE2\"\>

\<field
sid=\"SubModSeg_ModSegName\_\"\>\<value\>MOD2020-5\</value\>\</field\>

\<field
sid=\"SubModSeg_ModSegFileName\_\"\>\<value\>corresp.txt\</value\>\</field\>

\<field
sid=\"SubModSeg_ModSegMasterCIK\_\"\>\<value\>\</value\>\</field\>

\<field sid=\"SubModSeg_ModSegDescription\_\"\>\<value\>ascii
module\</value\>\</field\>

\<combobox
sid=\"SubModSeg_ModSegType\_\"\>\<value\>CORRESP\</value\>\</combobox\>

\<field
sid=\"SubModSeg_ModSegName_1\"\>\<value\>MOD2020-6\</value\>\</field\>

\<field
sid=\"SubModSeg_ModSegFileName_1\"\>\<value\>exhibit.txt\</value\>\</field\>

\<field
sid=\"SubModSeg_ModSegMasterCIK_1\"\>\<value\>\</value\>\</field\>

\<field sid=\"SubModSeg_ModSegDescription_1\"\>\<value\>TYPE1
module\</value\>\</field\>

\<combobox
sid=\"SubModSeg_ModSegType_1\"\>\<value\>TYPE1\</value\>\</combobox\>

\<data sid=\"firstmoduledocument\"\>

\<filename\>corresp.txt\</filename\>

\<mimedata\>

PT09PT09PT09PT09PT09PT09PT09PT09PT09PT09ICAgY29ycm

VzcG9uZGVuY2UgICA9PT09PT09PT09PT09PT09PT09PT09PT09

PT09PT0NCg0KVGhpcyBpcyBhIHByaXZhdGUgY29ycmVzcG9uZG

09PT09PT09PT09PT0NCg==

\</mimedata\>

\</data\>

\<data sid=\"secondmoduledocument\"\>

\<filename\>exhibit.txt\</filename\>

\<mimedata\>

PT09PT09PT09PT09PT09PT09PT09PT09PT09PT09ICAgY29ycm

VzcG9uZGVuY2UgICA9PT09PT09PT09PT09PT09PT09PT09PT09

PT09PT0NCg0KVGhpcyBpcyBhIHByaXZhdGUgY29ycmVzcG9uZG

09PT09PT09PT09PT0NCg==

\</mimedata\>

\</data\>

\</page\>

\<page sid=\"PAGE3\"\>

\<field
sid=\"SubInternet_internetAddress\_\"\>\<value\>joefiler@mailme.com\</value\>\</field\>

\<check
sid=\"SubFlag_overrideInternetFlag\_\"\>\<value\>off\</value\>\</check\>

\</page\>

\</XFDL\>

## Sample BULK from Subtemplate6.xfd

This example illustrates a BULK submission as defined by Template 6.

\<?xml version=\"1.0\"?\>

\<XFDL version=\"5.0.0\"\>

\<page sid=\"PAGE2\"\>

\<field
sid=\"SubGlobal_enclosedFileCount\_\"\>\<value\>3\</value\>\</field\>

\<field
sid=\"SubDocument_conformedName\_\"\>\<value\>rw.xfd\</value\>\</field\>

\<field
sid=\"SubDocument_description\_\"\>\<value\>doc1\</value\>\</field\>

\<field
sid=\"SubDocument_conformedName_1\"\>\<value\>pre14a.xfd\</value\>\</field\>

\<field
sid=\"SubDocument_description_1\"\>\<value\>doc2\</value\>\</field\>

\<field
sid=\"SubDocument_conformedName_2\"\>\<value\>sb-2.xfd\</value\>\</field\>

\<field
sid=\"SubDocument_description_2\"\>\<value\>doc3\</value\>\</field\>

\<data sid=\"data3\"\>

\<filename\>rw.xfd\</filename\>

\<mimedata\>

PD94bWwgdmVyc2lvbj0iMS4wIj8+DQo8WEZETCB2ZXJzaW9uPS

I0LjMuMCI+DQoJPHBhZ2Ugc2lkPSJQQUdFMSI+DQoJCTxjZWxs

ZhbHVlPjwvZmllbGQ+DQoJCTxmaWVsZCBzaWQ9IlN1YlRhYmxl

RkRMPiAgDQo=

\</mimedata\>

\</data\>

\<data sid=\"data1\"\>

\<filename\>pre14a.xfd\</filename\>

\<mimedata\>

PD94bWwgdmVyc2lvbj0iMS4wIj8+DQo8WEZETCB2ZXJzaW9uPS

Ij48dmFsdWU+MDAwMDM1MDAwMTwvdmFsdWU+PC9maWVsZD4NCg

kJPGZpZWxkIHNpZD0iTW9kU2VnUmVmZXJlbmNlRGF0YV9jY2Nf

Ij48dmFsdWU+bGVhdmVzIzE8L3ZhbHVlPjwvZmllbGQ+DQoJCT

xjZWxsIHNpZD0iQ0VMTDM1Ij48Z3JvdXA+TW9kU2VnUmVmZXJl

bmNlRGF0YV9tb2RPclNlZ0ZsYWdfR1JPVVA8L2dyb3VwPjx2YW

x1ZT5NPC92YWx1ZT48L2NlbGw+DQoJPC9wYWdlPiANCjwvWEZE

TD4gICANCg==

\</mimedata\>

\</data\>

\<data sid=\"data2\"\>

\<filename\>sb-2.xfd\</filename\>

\<mimedata\>

PD94bWwgdmVyc2lvbj0iMS4wIj8+DQo8WEZETCB2ZXJzaW9uPS

I0LjMuMCI+DQoJPHBhZ2Ugc2lkPSJQQUdFMSI+DQoJCTxjZWxs

IHNpZD0iQ0VMTDM0Ij48Z3JvdXA+U3ViU3JvX3Nyb0lkX0dST1

VQPC9ncm91cD48dmFsdWU+Tk9ORTwvdmFsdWU+PC9jZWxsPg0K

TDM1Ij48Z3JvdXA+TW9kU2VnUmVmZXJlbmNlRGF0YV9tb2RPcl

NlZ0ZsYWdfR1JPVVA8L2dyb3VwPjx2YWx1ZT5NPC92YWx1ZT48

L2NlbGw+DQoJPC9wYWdlPiANCjwvWEZETD4gICANCg==

\</mimedata\>

\</data\>

\</page\>

\</XFDL\>

**ACRONYMS**

  -------------- --------------------------------------------------------
  API            Application Programming Interface

  ASCII          American Standard Code for Information Interchange

  BNF            Backus Naur Form

  DOS            Disk Operating System

  DTD            Document Type Definition

  EDGAR          Electronic Data Gathering, Analysis, and Retrieval

  SEC            Securities and Exchange Commission

  *sid*          Scope Identifier

  XFDL           Extensible Forms Description Language

  XML            Extensible Markup Language
  -------------- --------------------------------------------------------

[^1]: The specific submission types that this specification supports are
    called out in Appendix I. Note that there may be other "Reduced
    Content" specifications for form types not supported here. For
    example, the EDGAR Reduced Content XML Specification covers Section
    16 Forms 3, 4, and 5. XFDL versions of those forms are not supported
    by EDGAR.