EDGARLink Online XML Technical Specification (Version 18)
Implementation Date: September 14, 2015
This EDGARLink Online (ELO) XML Technical specification provides, to those filers that are interested, a basis for creating XML submissions without the use of the EDGAR OnlineForms/XML Website. The expectation is that software developers, working on behalf of filers, will construct software that will generate an ELO XML submission that can be successfully processed by the EDGAR system.
The ELO Submissions should conform to the EDGARLink Online XML Technical Specification, namely, the XML schemas. Refer to XML schemas for detailed information on the common XML constructs of the EDGAR Filing submissions. For specific information about the data content of the ELO submission types, refer to the EDGAR Filer Manual Volume II available on the SEC’s Public Website (http://www.sec.gov).
EDGAR Release 15.3 introduced the following changes to the ELO XML Technical Specification:
- The new submission form types, SDR-CCO and SDR-CCO/A were added as EDGARLink Online Form Submissions.
- The schema file “eis_Common.xsd” was updated to define new complex types “CONFIDENTIAL_DOCUMENT_TYPE1” and “CONFIDENTIAL_DOCUMENTS_TYPE1” to allow filers to mark documents as confidential.
- The schema file “eis_Common.xsd” was also updated to add document types SDR-CR, SDR-CR/A, SDR-FR and SDR-FR/A that are allowed for submission form types SDR-CCO and SDR-CCO/A and a complex type “STRING_1K_RESTRICTED_TYPE”.
- The schema file “eis_SingleFiler.xsd” was updated to add four new elements “startPeriod”, “endPeriod”, “briefDescription” and “documentsConfidential”.
- The schema file “eis_Common.xsd” was updated to add the new exhibit type EX-36 for submission form types 8-K, 8-K/A, SF-3 and SF-3/A.
- Made the following changes to the document to make it 508 compliant:
- Some of the column headers were not sufficient for JAWS to announce when it was entering data cells in the JAWS “Tables” mode. Enabled the “Repeat as header row at the top of each page” option to resolve the issue.
- Some of the headings in the document did not follow a hierarchy. Corrected the issue by setting the hierarchical order. For example, Heading Level 1, Heading Level 2, Heading Level 3; or Caption or Body text for tables.
- Lists, and the numbering of list items, were not sufficient for JAWS to identify and read. Mapped all the contents which appeared to be a list using the Numbering or Bullet list option.
- Some of the tables in the document spanned across multiple pages with no repeated header rows, which was not sufficient for JAWS to announce the column heading of that cell in the table. Enabled the “Allow row to break across pages” and “Repeat as header row at the top of each page” options to resolve the issue.
- Hyperlinks were not sufficient for JAWS to announce and navigate appropriately. Enabled hyperlinks and ensured JAWS read and navigated to the appropriate URLs.