Pds Dissemination Spec 064938
Pds Dissemination Spec 064938
EDGAR
ELECTRONIC DATA GATHERING, ANALYSIS, AND RETRIEVAL
EDGAR
Public Dissemination
Service (PDS) Technical
Specification
1
Table of Contents
Summary of Changes ................................................................................................................................ 3
1. PDS OVERVIEW ............................................................................................................................. 4
2. SUBMISSION INTERFACE FILE FORMAT .................................................................................... 5
2.1 Control Block ..................................................................................................................................................... 9
2.2 Submission Header Format ............................................................................................................................ 10
2.3 Supported Document Formats ....................................................................................................................... 10
2.3.1 ASCII/SGML (*.txt or *.fil) ...................................................................................................................... 10
2.3.2 HTML or Inline XBRL (*.htm).................................................................................................................. 10
2.3.3 JPEG/GIF (*.jpg or *.gif) ......................................................................................................................... 11
2.3.4 XML (*.xml) ............................................................................................................................................ 11
2.3.5 XBRL (*.xml and *.xsd) ........................................................................................................................... 11
2.3.6 PDF (*.pdf) .............................................................................................................................................. 11
2.3.7 PROCESSED XBRL (*.xml,*.htm,*.xlsx,*.css,*.js,*.json,*.png,*.zip) .................................................... 11
3. EDGAR PUBLIC SUBMISSION TYPES ........................................................................................ 13
3.1 EDGAR Public Document Types .................................................................................................................... 13
3.2 EDGAR Header and Document SGML Tag Identification ............................................................................ 14
3.2.1 Symbology ..................................................................................................................................................... 14
3.2.2 Submission Header Tag Elements ................................................................................................................ 14
3.2.3 Document Header Tag Elements .................................................................................................................. 36
3.2.4 Document Text Tag Elements ....................................................................................................................... 36
3.3 EDGAR Header and Document Tag Definitions ........................................................................................... 37
3.3.1 Submission Header Tags ........................................................................................................................ 37
3.3.2 Document Header and Text Tags........................................................................................................... 63
3.4 EDGAR SGML Document Type Definition..................................................................................................... 67
3.5 EDGAR Dissemination Notices ...................................................................................................................... 76
4. ACRONYMS .................................................................................................................................. 77
Table of Tables
Table 1 - Publicly Disseminated Submissions ................................................................................................................... 7
Table 2 - Publicly Disseminated Paper Submissions ......................................................................................................... 8
Table 3 - Public-Ready Disseminations ............................................................................................................................. 8
Table 4 - Post-Acceptance Corrections ............................................................................................................................. 9
Table 5 - Daily Audit File ................................................................................................................................................... 9
Table 6 - Control Block Field Definitions ......................................................................................................................... 10
Table 7 - Symbology ........................................................................................................................................................ 14
Table 8 - Submission Header Tag Elements .................................................................................................................... 35
Table 9 - Document Header Tag Elements ..................................................................................................................... 36
Table 10 - Document Text Tag Elements ........................................................................................................................ 37
2
Summary of Changes
The following changes have been implemented:
3
1. PDS OVERVIEW
The United States Securities and Exchange Commission (SEC) has designed the Electronic Data
Gathering, Analysis, and Retrieval (EDGAR) System to support the assembly, transmission, validation,
acceptance, and dissemination of public documents as filed by public companies, management firms, and
individuals pursuant to SEC securities regulations. Once received and accepted by EDGAR, public
submissions are disseminated to all interested parties (subscribers) external to the SEC EDGAR network.
The EDGAR Public Dissemination Service (PDS) receives a direct feed from the EDGAR Host and
initiates the data -dissemination to Subscribers as soon as reasonably feasible. All PDS Subscribers are
managed through this remote site.
This document describes the format for various files disseminated to the Subscribers. It also provides the
definitions for each element in the file.
Attain, LLC is the primary contractor in support of the development of the SEC's PDS System. The
original PDS was developed in 1992. Attain, LLC assumed full responsibility for support of PDS on
July 1, 2014.
EDGAR accepts and disseminates approximately 2,000-4,000 live public submissions per day during
non-peak periods and 4,000-15,000 live submissions per day during peak periods1. During these "high-
activity" periods, EDGAR may receive up to 500-1500 MB of live, public data in one hour or up to 12
GB of data in a single business day. Disseminated submissions may be as small as 1 KB or as large as
400 MB, depending on their purpose, and contain only public documents2. The average submission size is
approximately 800 KB. Submissions, which are composed of a header and concatenated documents, are
disseminated in ASCII text (no binary is disseminated without being UUencoded first). Concatenated
documents can have ASCII/SGML, HTML, XML, XBRL, or UUencoded PDF, JPG, or GIF formats.
Rendered XBRL documents may also be concatenated, which may be of the following types: HTML,
XML, CSS, JS, UUencoded PNG, UUencoded XLSX or UUencoded ZIP.
ASCII/SGML documents are no wider than 80 characters per line, except in specifically designated
sections of document text, identified as tables (<TABLE>), where a 132-character width limit is
1
There are several peak submission periods throughout the calendar year, including the following:
• Four 10-Q peaks (40-45 days after the 1st – 4th calendar quarter: May, August, November, and February, respectively, with each
quarterly peak having an accelerated filing period 30-35 days after the quarter end).
• One 10-K/24F-2NT peak (from March 26-31, usually consisting of very large 10-K submissions, with an associated accelerated filing
period from March 15-16).
• Two N-SAR peaks (February 25-28 and August 28-31).
• One SC 13G William's Act peak (February 10-14, usually the highest volume of submissions, but they are very small).
• Four Ownership peaks (Two business days following the end of each calendar quarter).
• One N-PX peak (at the end of August).
See the SEC Public Website, www.sec.gov, for more information on peak submission periods.
2
Private documents that are part of Filer submissions are not disseminated with the original submission (*.dissem file). They are stored internally
at the SEC for a period of time, and then upon SEC discretion, some are released as a separate dissemination file (*.pr file).
4
supported. HTML, XML, and XBRL document text has no inherent width limits. UUencoded document
text is 64 characters wide.
After receiving a submission via the internet or SSH, EDGAR assigns an Accession Number (ex:
000035001-05-00100) to the submission, then parses it to extract key information from the header and
document. This information is then loaded into the EDGAR database and subsequently run through a
rigorous series of syntactic and semantic validation rules before being accepted by EDGAR. After
acceptance, the submission is then reassembled with informative header tags and the original public
documents before being disseminated to the PDS and the SEC.gov site.
EDGAR transmits the dissemination stream to the PDS server, and PDS disseminates EDGAR files to the
Subscribers.
3
[ACCESSION-NUMBER] has the following format: ##########-YY-SSSSSS, where ########## is the unique 10-digit Central Index Key
(CIK) of the entity (the Filer or a filing agent – not necessarily related to the CIKs within the filing) that has submitted the filing and is
composed of the digits 0-9, YY is the last two digits of the year the submission was filed, and SSSSSS is the sequence number (up to 6
digits, left-padded by zeros) of the submission within the year it was filed.
4
Electronically-transmitted by the Filer to EDGAR over the internet or Leased Line.
5
submission header, and a set of one (1) or more public document(s). There are 421electronic form types
supported by the SEC, each of which contains a mandatory primary document (i.e., a 10-Q submission
must contain a 10-Q document) and various supplemental documents (e.g., an attached exhibit (EX-*)
document). See Section 3.0 EDGAR Public Submission Types for a complete listing of all active form
types accepted by EDGAR. See Section 3.1 EDGAR Public Document Types for a complete listing of all
active public document types that may accompany these form types. For a comprehensive update and
definition of all active form types and document types, see the SEC website, https://www.sec.gov/, and go
to the EDGAR information page ( https://www.sec.gov/info/edgar.shtml).
Submissions received in paper are entered into EDGAR by the SEC. After acceptance, EDGAR will
generate and disseminate an official abbreviated version of the paper submission (i.e., 0000350001-05-
001234.paper). These submissions will have a control-block and header that is similar to their electronic
submission counterparts, but will not contain the actual documents received. Only one “stub” document
will represent the actual documents attached. Paper submissions are disseminated (or made available) via
another SEC service5. Subscribers will need to use the enclosed film-number (Document Control Number
(DCN) when contacting the SEC’s paper-dissemination service to properly reference all associated
documents for that paper submission.
5
Subscribers will need to contact the SEC for more information about obtaining hard copies of accepted paper submissions.
6
*.pr, respectively) are 31 characters long. Daily audit filenames (dissem*.EOD) are 21 characters long.
The Subscriber's server must be able to support 31-character filenames.
All EDGAR transmissions, except for the daily audit file, use a Standard Generalized Markup Language
(SGML) tagging scheme to deliver company and submission information to the SEC and all Subscribers.
See Section 4.3.1 for a complete listing and description of all active SGML tags used in EDGAR
submissions. EDGAR disseminates submission information in the following format to all PDS
Subscribers.
Section Length
Control Block 266 Bytes
7
Publicly disseminated paper submissions (*.paper):
Section Length
Control Block 266 Bytes
Section Length
Control Block 266 Bytes
8
Post-Acceptance corrections (*.pc):
Section Length
Control Block 266 Bytes
Section Length
Submission name (*.dissem or *.pc); repeated for each Up to 31 characters +CR/LF for each submission
disseminated submission for that day
Table 5 - Daily Audit File
The control block is a 266-byte block that identifies the associated submission and provides key
information about the submission. There are fourteen (14) fields contained within the control block,
each of which is blank-padded. The fields are described in the following table in their exact order:
Size
Field Description
(bytes)
Accession Number 20 EDGAR accession number
Public/Private Flag 1 A flag indicating whether the submission is public or private; format is
binary. Values are:
Public
Private
Transaction Type 1 An indicator describing the transaction type; format is binary. Values
are:
Submission
Retransmission
Correction
Deletion
Submission Form Type Transfer
Document Type Transfer
SRO Distribution List 4 [OBE, Unused]
Reserved 65 Unused, Blank-filled
Each ASCII/SGML document consists of free-formatted text (i.e., 10-Q, 10-K, S-1, etc.), SGML-
formatted text (i.e., EX-27 documents), or columnar formatted text (i.e., N-SAR documents). All
document text is 80-characters wide except when between <TABLE> tags, where the width is set to 132
characters. All EDGAR SGML document tags are identified and defined in Sections 4.2 EDGAR Header
and Document SGML Tag Identification and 4.3 EDGAR Header and Document Tag Definitions.
11
Included in a .dissem File
File Names with XBRL documents <TYPE>
FilingSummary.xml Always XML
R1.htm,R2.htm,…,R9999.htm Always XML
Report.css Always XML
Show.js Always XML
Financial_Report.xlsx Always, except for 485BPOS and 497 EXCEL
submissions
BarChart1.png, BarChart2.png, Only for 485BPOS and 497 submissions GRAPHIC
BarChart3.png, etc …
{accession_number}-xbrl.zip Always ZIP
MetaLinks.json Only when there is an Inline XBRL .htm XML
document.
{...}_htm.xml Only when there is an Inline XBRL .htm XML
document
Note: {accession_number}-xbrl.zip contains all filer-submitted XBRL, all Inline XBRL formatted documents, and
all .jpg and .gif files referenced from XBRL text blocks, footnotes, and Inline XBRL elements. It does not contain
any processing outputs.
Note: When the primary document with name xyz.htm or any attached exhibit is an Inline XBRL file,
then: (a) there are no input attachments named "EX-*.INS", and a file xyz_htm.xml is part of the
processing output.
Note: *.pdf, *.gif, *.jpg, *.png,*.xlsx and *.zip files are uuencoded.
Here is an example of what a rendered XBRL document may look in the .dissem file:
<DOCUMENT>
<TYPE>XML
<SEQUENCE>12
<FILENAME>R2.htm
<DESCRIPTION>IDEA: XBRL DOCUMENT
<TEXT>
</TEXT>
</DOCUMENT>
12
3. EDGAR PUBLIC SUBMISSION TYPES
All live, accepted public submissions (electronic and paper) are disseminated to Subscribers through PDS.
For a complete definition of these form types, see the SEC website,
https://www.sec.gov/info/edgar/forms/edgform.pdf
All live, accepted public documents are disseminated as part of a total submission and are
disseminated to Subscribers through PDS. The following is a list of all active public documents that
are accepted and disseminated by the EDGAR system.
A. Official Document Types Supported by EDGAR are *.txt or *.htm attachments to a submission:
[For electronic submissions (*.dissem), primary documents are the same type as the submission
type.].
[For paper submissions (*.paper), the single document type supported will be the same as their
respective paper submission type. These documents are only stub representations of the actual
documents that were submitted to the SEC in paper format. The actual paper documents must be
retrieved from an SEC paper dissemination service].
The following exhibit document types are considered supplemental/optional to the submission.
These document types can include an optional suffix consisting of a "." and free text up to a total
document type length of 20 characters:
EX-1 EX-2 EX-3 EX-4 EX-5 EX-6 EX-7 EX-8 EX-9 EX-10 EX-11 EX-12 EX-13 EX-14 EX-15
EX-16 EX-17 EX-18 EX-19 EX-20 EX-21 EX-22 EX-23 EX-24 EX-25 EX-25/AEX-26 EX-28
EX-29 EX-31 EX-32 EX-33 EX-34 EX-35 EX-36 EX-95 EX-99 EX-101 EX-102 EX-103 EX-
106
B. Official GRAPHIC Document Types Supported as *.jpg or *.gif attachments to a submission:
GRAPHIC [May only be attached if there is a reference to the GRAPHIC document from within
an HTML document].
C. Official Private Document Types such as COVER, CORRESP etc may be disseminated in a *.pr
file upon SEC approval.
D. Unofficial Public Document Types Disseminated in a *.dissem file:
[All *.pdf attachments, which may be unofficial versions of any document type referenced in
section 1 above].
13
3.2 EDGAR Header and Document SGML Tag Identification
The following is a list of all SGML tags used within EDGAR submission headers and ASCII/SGML
documents. For a complete definition of these tags, see Section 4.3 EDGAR Header and Document
Tag Definitions.
3.2.1 Symbology
Symbol Definition
Blank Required
? Optional
+ Tag and element are required and repeatable.
*. Tag and element are optional and repeatable.
1 Each of these fields/tags, which include FILER, FILED-BY, SUBJECT-COMPANY,
REPORTING-OWNER, ISSUER, SERIAL-COMPANY, FILED-FOR, and SERIES-AND-
CLASSES-CONTRACTS-DATA elements may be exclusive with respect to one or more of the
others depending on the submission type.
2 Selection and placement of tag and tag value is at the discretion of author of filing
text.
Table 7 - Symbology
? CORRECTION <SUBMISSION>
<CORRECTION>
? PAPER <PAPER>
? PRIVATE-TO-PUBLIC <PRIVATE-TO-PUBLIC>
? DELETION <DELETION>
? CATEGORY <CATEGORY>
14
? CONFIRMING COPY <CONFIRMING COPY>
CALENDAR-YEAR-ENDING <CALENDAR-YEAR-ENDING>
15
1+ FILER <FILER>
? DELETION <DELETION>
CIK <CIK>
SIC <ASSIGNED-SIC
RELATIONSHIP <RELATIONSHIP>
? DELETION <DELETION>
? STREET1 <STREET1>
? STREET2 <STREET2>
? CITY <CITY>
? STATE <STATE>
16
? ZIP <ZIP>
? PHONE <PHONE>
? STREET1 <STREET1>
? STREET2 <STREET2>
? CITY <CITY>
? STATE <STATE>
? ZIP <ZIP>
1 DEPOSITOR <DEPOSITOR>
CIK <CIK>
SIC <ASSIGNED-SIC>
17
? FISCAL YEAR END <FISCAL-YEAR-END>
? STREET1 <STREET1>
? STREET2 <STREET2>
? CITY <CITY>
? STATE <STATE>
? ZIP <ZIP>
? PHONE <PHONE>
? STREET1 <STREET1>
? STREET2 <STREET2>
? CITY <CITY>
? STATE <STATE>
? ZIP <ZIP>
18
* FORMER COMPANY <FORMER-COMPANY>
CIK <CIK>
SIC <ASSIGNED-SIC>
? STREET1 <STREET1>
19
? STREET2 <STREET2>
? CITY <CITY>
? STATE <STATE>
? ZIP <ZIP>
? PHONE <PHONE>
? STREET1 <STREET1>
? STREET2 <STREET2>
? CITY <CITY>
? STATE <STATE>
? ZIP <ZIP>
CIK <CIK>
20
SIC <ASSIGNED-SIC>
? STREET1 <STREET1>
? STREET2 <STREET2>
? CITY <CITY>
? STATE <STATE>
? ZIP <ZIP>
? PHONE <PHONE>
? STREET1 <STREET1>
? STREET2 <STREET2>
21
? CITY <CITY>
? STATE <STATE>
? ZIP <ZIP>
1 UNDERWRITER <UNDERWRITER>
CIK <CIK>
SIC <ASSIGNED-SIC>
22
END FILING VALUES </FILING-VALUES>
? STREET1 <STREET1>
? STREET2 <STREET2>
? CITY <CITY>
? STATE <STATE>
? ZIP <ZIP>
? PHONE <PHONE>
? STREET1 <STREET1>
? STREET2 <STREET2>
? CITY <CITY>
? STATE <STATE>
? ZIP <ZIP>
1 FILED BY <FILED-BY>
23
? DELETION <DELETION>
CIK <CIK>
SIC <SIC>
? DELETION <DELETION>
? STREET1 <STREET1>
? STREET2 <STREET2>
? CITY <CITY>
? STATE <STATE>
? ZIP <ZIP>
? PHONE <PHONE>
? STREET1 <STREET1>
? STREET2 <STREET2>
24
? CITY <CITY>
? STATE <STATE>
? ZIP <ZIP>
? DELETION <DELETION>
CIK <CIK>
SIC <ASSIGNED-SIC>
? DELETION <DELETION>
25
SEC FILE NUMBER <FILE-NUMBER>
? STREET1 <STREET1>
? STREET2 <STREET2>
? CITY <CITY>
? STATE <STATE>
? ZIP <ZIP>
? PHONE <PHONE>
? STREET1 <STREET1>
? STREET2 <STREET2>
? CITY <CITY>
? STATE <STATE>
? ZIP <ZIP>
26
? DELETION <DELETION>
CIK <CIK>
SIC <ASSIGNED-SIC>
? DELETION <DELETION>
? STREET1 <STREET1>
? STREET2 <STREET2>
? CITY <CITY>
? STATE <STATE>
? ZIP <ZIP>
? PHONE <PHONE>
27
? END BUSINESS ADDRESS </BUSINESS-ADDRESS>
? STREET1 <STREET1>
? STREET2 <STREET2>
? CITY <CITY>
? STATE <STATE>
? ZIP <ZIP>
? DELETION <DELETION>
CIK <CIK>
? SIC <ASSIGNED-SIC>
28
? DELETION <DELETION>
? STREET1 <STREET1>
? STREET2 <STREET2>
? CITY <CITY>
? STATE <STATE>
? ZIP <ZIP>
? PHONE <PHONE>
? STREET1 <STREET1>
? STREET2 <STREET2>
? CITY <CITY>
? STATE <STATE>
? ZIP <ZIP>
29
END FORMER NAME </FORMER-NAME>
1 ISSUER <ISSUER>
? DELETION <DELETION>
CIK <CIK>
SIC <ASSIGNED-SIC>
? STREET1 <STREET1>
? STREET2 <STREET2>
? CITY <CITY>
? STATE <STATE>
? ZIP <ZIP>
? PHONE <PHONE>
? STREET1 <STREET1>
? STREET2 <STREET2>
30
? CITY <CITY>
? STATE <STATE>
? ZIP <ZIP>
CIK <CIK>
SIC <ASSIGNED-SIC>
? DELETION <DELETION>
31
FILM NUMBER <FILM-NUMBER>
? STREET1 <STREET1>
? STREET2 <STREET2>
? CITY <CITY>
? STATE <STATE>
? ZIP <ZIP>
? PHONE <PHONE>
? STREET1 <STREET1>
? STREET2 <STREET2>
? CITY <CITY>
? STATE <STATE>
? ZIP <ZIP>
? PUBLIC-REFERENCE-ACC# <PUBLIC-REFERENCE-ACC>
32
? NEW SERIES AND CLASSES CONTRACTS <NEW-SERIES-AND-CLASSES-
CONTRACTS>
SERIES ID <SERIES-ID>
l SERIES ID <SERIES-ID>
+ SERIES <SERIES>
SERIES ID <SERIES-ID>
33
+ CLASS CONTRACT <CLASS-CONTRACT>
+ MERGER <MERGER>
CIK <CIK>
SERIES <SERIES>
SERIES ID <SERIES-ID>
CIK <CIK>
34
+ SERIES <SERIES>
SERIES ID <SERIES-ID>
*. ACCESSION_NUMBER <ACCESSION-NUMBER>
? PREVIOUS-ACCESSION-NUMBER <PREVIOUS-ACCESSION-NUMBER>
35
3.2.3 Document Header Tag Elements
+ DOCUMENT <DOCUMENT>
? DESCRIPTION <DESCRIPTION>
36
2 FOOTNOTES <F1> - <F99>
2 PAGE <PAGE
Table 10 - Document Text Tag Elements
38
DESCRIPTION: Identifies post acceptance correction filing deletion. This tag is present
after accession number only when the filing is being deleted. Optional.
LENGTH: Tag only
END TAG: NA
CHARACTERISTIC: NA
LIMITS: NA
FORMAT: NA
40
LENGTH: 8
END TAG: NA
CHARACTERISTIC: Date
LIMITS: NA
FORMAT: YYYYMMDD
42
DATA ELEMENT: RECEIVED DATE
TAG: <RECEIVED-DATE>
DESCRIPTION: The received date for Orders or Notices. Optional.
LENGTH: 8
END TAG: NA
CHARACTERISTIC: Date
LIMITS: NA
FORMAT: YYYYMMDD
43
END TAG: NA
CHARACTERISTIC: Alphanumeric
LIMITS: The valid values for this element are “Y” or “N”.
FORMAT: NA
45
LIMITS: NA
FORMAT: NA
50
DATA ELEMENT: DELETION
TAG: <DELETION>
DESCRIPTION: Identifies post acceptance correction file number deletion. This tag is
present after filing values to specify the file number deleted.
Optional.
LENGTH: Tag only
END TAG: NA
CHARACTERISTIC: NA
LIMITS: NA
FORMAT: NA
51
DATA ELEMENT: FILM NUMBER
TAG: <FILM-NUMBER>
DESCRIPTION: Also known as the Document Control Number (DCN) Microfilm number
assigned to submission. Required for each Subject
Company or Registrant, or Owner, not for Filed By or Issuer.
LENGTH: 10
END TAG: NA
CHARACTERISTIC: Alpha-Numeric
LIMITS: NA
FORMAT: YY######
53
DATA ELEMENT: MAIL STREET 1
TAG: <STREET1>
DESCRIPTION: Company Mail Street 1. Optional.
LENGTH: 40
END TAG: NA
CHARACTERISTIC: Alpha-Numeric
LIMITS: NA
FORMAT: NA
55
DATA ELEMENT: PUBLIC REFERENCE ACCESSION NUMBER
TAG: <PUBLIC-REFERENCE-ACC>
DESCRIPTION: Present only in SEC UPLOADS. Reference to a specific submission (via
Accession number). Optional.
END TAG: NA
LENGTH: 20
CHARACTERISTIC: Alpha-Numeric
LIMITS: NA
FORMAT: (10-Char CIK)+"-"+YY+"-"+(6-Char sequence #)
56
DATA ELEMENT: MERGER SERIES AND CLASSES CONTRACTS
TAG: <MERGER-SERIES-AND-CLASSES-CONTRACTS>
DESCRIPTION: Initial tag for identifying merger series and classes (contracts) information.
Related data will be grouped together. The tag is optional per relevant
form type.
LENGTH: Tag only
END TAG: </MERGER-SERIES-AND-CLASSES-CONTRACTS>
CHARACTERISTIC: NA
LIMITS: NA
FORMAT: NA
57
DATA ELEMENT: SERIES NAME
TAG: <SERIES-NAME>
DESCRIPTION: Series name, which was supplied by the filer during receipt new series
information. Required for all scenarios (new, existing, merger) for series
and classes (contracts).
LENGTH: 150
END TAG: NA
CHARACTERISTIC: AlphaNumeric
LIMITS: NA
FORMAT: NA
58
DATA ELEMENT: CLASS CONTRACT NAME
TAG: <CLASS-CONTRACT-NAME>
DESCRIPTION: Class (contract) name, which was supplied by the filer during receipt of new
class (contract) information. Required for all scenarios (new, existing,
merger) for series and classes (contracts).
LENGTH: 150
END TAG: NA
CHARACTERISTIC: AlphaNumeric
LIMITS: NA
FORMAT: NA
59
TAG: <ACQUIRING-DATA>
DESCRIPTION: Initial tag for identifying the acquiring series and class (contract) information
as part of reporting merger information. Required for Merger Series and
Classes Contracts.
LENGTH: Tag only
END TAG: </ACQUIRING-DATA>
CHARACTERISTIC: NA
LIMITS: NA
FORMAT: NA
62
3.3.2 Document Header and Text Tags
The following is a list of each tag and associated tag value information for the document portion of the
current disseminated output DTD. This includes the data element, tag, description and other information
associated with the tag value.
63
FORMAT: NA
64
DATA ELEMENT: XML
TAG: <XML>
DESCRIPTION: Identifies beginning of XML document and XML tagging elements. Optional
under Document text.
LENGTH: Tag only
END TAG: </XML>
CHARACTERISTIC: NA
LIMITS: NA
FORMAT: NA
65
DATA ELEMENT: STUB
TAG: <S>
DESCRIPTION: Identifies a stub header. Optional and repeatable in document text.
LENGTH: Tag only
END TAG: NA
CHARACTERISTIC: NA
LIMITS: NA
FORMAT: NA
66
LENGTH: Tag Only
END TAG: NA
CHARACTERISTIC: NA
LIMITS: NA
FORMAT: NA
A Document Type Definition (DTD) provides the rules that apply SGML to the markup of particular
document types. A DTD should include a formal specification in the form of a document type declaration
of elements types, element relationships and attributes, and references that can be represented by the
markup. The DTD defines the vocabulary of the markup for which SGML defines the syntax.
<!SGML "ISO 8879-1986"
--
!============================================================
!
! EDGAR DISSEMINATION
!
! SGML DECLARATION AND DOCUMENT TYPE DEFINITION
!
! PUBLIC
!
!!============================================================!
--
CHARSET BASESET "ISO 646-1983//CHARSET International
Reference Version (IRV)//ESC 2/5 4/0"
DESCSET 0 9 UNUSED
9 2 9
11 2 UNUSED
13 1 13
14 18 UNUSED
32 95 32
127 1 UNUSED
CAPACITY PUBLIC "ISO 8879-1986//CAPACITY Reference//EN"
SCOPE DOCUMENT
C-1
SYNTAX
SHUNCHAR CONTROLS 0 1 2 3 4 5 6 7 8 9 10 11 12 13
67
14 15 16 17 18 19 20 21 22 23 2425 26
27 28 29 30 31 127 255
BASESET "ISO 646-1983//CHARSET International
Reference Version (IRV)//ESC 2/5 4/0"
DESCSET 0 128 0
FUNCTION RE 13
RS 10
SPACE 32
TAB SEPCHAR 9
NAMING LCNMSTRT ""
UCNMSTRT ""
LCNMCHAR "-.&"
UCNMCHAR "-.&" NAMECASE
GENERAL YES
ENTITY NO
DELIM GENERAL
SGMLREF SHORTREF
SGMLREF
NAMES SGMLREF
QUANTITY SGMLREF NAMELEN 40 LITLEN 9000
ATTCNT 40 GRPCNT 350
GRPGTCNT 350
FEATURES -- only OMITTAG --
MINIMIZE DATATAG NO OMITTAG YES RANK NO
SHORTTAG NO
<!--
! ================ ENTITES ================
Entity references are provided for the '<' and '&' symbols to enable their use when a markup declaration
open code or an entity reference open code respectively is not intended.
Caution: These reference mechanisms are provided and recommended for use as needed in the
preparation of filing text. In the event that filing text presents a valid, yet unintended, entity reference
which is not previously declared and no default entity has been defined, the SGML standard requires that
68
the reference be raised as an error. However, use of these entities to avoid unintended references is not
strictly enforced as a condition for acceptance of EDGAR filings.
The text of disseminated filings may include literal sequences of characters containing ampersands. Such
sequences could possibly present (unintended) valid entity references per the SGML standard. Any
receiver of C-2 EDGAR dissemination data should be prepared to deal with possible exceptions raised as
a result of unintended entity references stemming from character sequences with ampersands.
-->
C-2
<!--
!=============================================================
===!
! PARAMETER ENTITIES
!=============================================================
===!
-->
69
group-members*, abs-
rule?,
securitizer-file-number?,
registered-entity?,
abs-asset-class?" >
C-3
70
<!ENTITY % address "street1?,
street2?,
city?,
state?,
zip?",
phone? >
<!ENTITY % footnotes " f1| f2| f3| f4| f5| f6| f7| f8|
f9|f10|f11|f12|f13|f14|f15|f16|f17|f18|f19|f20|f21|f22|f23|f24|f25|f26|f27|f28|f29|f30|f31|f32|f33
|f34|f35|f36|f37|f38|f39|f40|f41|f42|f43|f44|f45|f46|f47|f48|f49|f50|f51|f52|f53|f54|f55|f56|f57|f
58|f59|f60|f61|f62|f63|f64|f65|f66|f67|f68|f69|f70|f71|f72|f73|f74|f75|f76|f77|f78|f79|f80|f81|f8
2|f83|f84|f85|f86|f87|f88|f89|f90|f91|f92|f93|f94|f95|f96|f97|f98|f99 " >
<!ENTITY % hilites " table | page | %footnotes; ">
<!ENTITY % text "#PCDATA | %hilites; " >
<!--
!=============================================================!
! ELEMENT DECLARATIONS
!=============================================================!
-->
<!-- NOTE: The "deletion" element is defined for use within the following three tag nests:
1) "submission",
2) "filer,filed-by, subject-company, reporting-owner, issuer, or serial-company" and
3) "filing-values", to accommodate all possible dissemination stream (files).
However, within any SGML document instance, "deletion" will be used in no more than 1 of these
three tags nests.
-->
C-4
71
<!ELEMENT submission - - (%subm-front;,
(%registrants;),
is-filer-a-new-registrant?,
is-filer-a-well-known-seasoned-issuer?,
filed-pursuant-to-general-instruction-a2?,
is-fund-24f2-eligible?,
document+ ) >
<!ELEMENT (filer,
filed-by,
72
serial-company,
subject-company,
reporting-owner,
issuer,
filed-for) - - (%regist-data;) >
73
<!-- Registrant data definitions -->
C-5
<!ELEMENT (conformed-name,
cik,
assigned-sic,
relationship,
irs-number,
state-of-incorporation,
fiscal-year-end) - o (#PCDATA) >
<!ELEMENT (form-type,
act,
file-number,
film-number) - o (#PCDATA) >
<!ELEMENT (street1,
street2,
city,
state,
zip,
phone) - o (#PCDATA) >
74
<!ELEMENT (former-conformed-name,
date-changed) - o (#PCDATA) >
<!ELEMENT (owner-cik,
series-id,
series-name, class-
contract-id,
class-contract-name,
class-contract-ticker-symbol) - o (#PCDATA) >
75
C-6
<!ELEMENT (caption,
s,
c,
fn) - o (#PCDATA) >
<!ELEMENT (%footnotes;) - o EMPTY >
<!ELEMENT page - o EMPTY >
]>
76
4. ACRONYMS
Acronym Definition
ADC Alternate Data Center
BOB Beginning of Business
COB Close of Business
COTS Commercial Off-the-Shelf
CSU Channel Service Unit
DCN Document Control Number
DR Disaster Recovery
DRS Dissemination Receipt Server
DSU Date Service Unit
DTD Document Type Definition
EDGAR Electronic Data Gathering, Analysis, and Retrieval
EOD End-Of-Day
ET Eastern Time
JS JavaScript
HTML HyerText Markup Language
HTTPS Hyper Text Transfer Protocol Secure
GIF Graphical Interface Format
IP Internet Protocol
N-SAR Investment Company’s Semi-Annual Report
OS Operating System
PAC Post-Acceptance Corrections
PDF Portable Document Format
PDS Public Dissemination Service
PNG Portable Network Graphics
POC Point of Contact
SEC Securities and Exchange Commission
SGML Standard Generalized Markup Language
TCP Transmission Control Protocol
XBRL eXtensible Business Reporting Language
XML Extensible Markup Language
77