Name | Variations | Error Codes | Remarks
--- | --- | --- | ---
EDGAR Filer Manual v41 6.5.1 page 6-8 | 2 | Entity-Identifier-Scheme |
EDGAR Filer Manual v41 6.5.2 page 6-8 | 3 | Cik-Element-Context-Mismatch | REMARK: Variations 001ng and 002ng may produce error 60523 depending on implementation.
EDGAR Filer Manual v41 6.5.3 page 6-9 | 2 | Invalid-Cik | REMARK: this will inevitably generate two errors
EDGAR Filer Manual v41 6.5.4 page 6-9 | 3 | No-Scenario |
EDGAR Filer Manual v41 6.5.7 page 6-9 | 1 | Duplicate-Contexts |
EDGAR Filer Manual v41 6.5.8 page 6-9 | 1 | Unused-Context |
EDGAR Filer Manual v41 6.5.9 page 6-10 | 12 | Start-And-End-Dates-Not-Distinct-Inconsistent-With-Document-Type | REMARK: 6.5.9 applies to context start dates compared against context end dates, irrespective of segments.
EDGAR Filer Manual v41 6.5.11 page 6-10 | 4 | Duplicate-Units | REMARK: Abbreviations are from Base Units
EDGAR Filer Manual v41 6.5.12 page 6-10 | 10 | Duplicate-Facts |
EDGAR Filer Manual v41 6.5.13 page 6-11 | 1 | Duplicate-Facts | REMARK: This rule establishes what the default value of xml:lang is and therefore can only be indirectly violated by the violation of some other rule. Therefore the only error code that appears here is du-60512-Duplicate-Facts which normally would appear in 6.5.12.
EDGAR Filer Manual v41 6.5.14 page 6-11 | 6 | English-Text-Missing |
EDGAR Filer Manual v41 6.5.15 page 6-11 | 15 | Text-Block-Not-Well-Formed-XML | REMARK: In XML it is vital to distinguish the DOM from its various serializations. For a text block, the DOM node starts as an element with one child text node; exactly one. It is that child text node that you now treat as a string, wrap <body> and </body> around it, then re-parse and validate against edbody.dtd; the grammar for the % Flow entity is clear. REMARK: By contrast, the content of a footnote according to XBRL 2.1 is any alternating sequence of text nodes and element nodes drawn with names in the xhtml namespace. The serialization does not (and cannot) matter. The additional constraint on footnotes imposed by EDGAR is that a footnote cannot just contain any old sequence of text and element DOM nodes. It has to be a sequence of DOM nodes that would be valid if they were the children of a body node instead. You do not read the footnote as a text node (that might have ampersands and angle brackets), as if it were itself a serialization. You take that sequence of DOM nodes, make them the children of a <body> node and validate. REMARK: Only restrictions of the textBlockItemType are relevant because the base type xbrli:stringItemType is declared final in the XBRL 2.1 schema and cannot be extended.
EDGAR Filer Manual v41 6.5.16 page 6-12 | 32 | Prohibited-Html-Body | REMARK: Restrictions on the content of href are documented in EFM 5.2.2.1. There is a DTD (edbody.dtd in the "lib" folder) used for validation of unescaped content, but a change to Schema (and therefore disallowing named entities) may occur at some time in the future. The DTD by itself does NOT check for nested <table> elements, but they are disallowed, as variation _030ng shows. REMARK: For reference only, here are tags forbidden, keeping in mind that all permitted tags are lower case: <acronym/> <applet/> <area/> <base/> <basefont/> <bdo/> <button/> <col/> <colgroup/> <del/> <fieldset/> <font/> <form/> <frame/> <frameset/> <iframe/> <input/> <ins/> <label/> <legend/> <map/> <meta http-equiv="name" content="content"/> <noframes/> <noscript/> <object/> <option/> <param/> <q/> <s/> <S/> <script/> <select/> <style/> <textarea/> REMARK: Variations 018 through 022 require http://www.xbrl.org/dtr/type/nonNumeric-2010-12-16.xsd in edgartaxonomies.xml
EDGAR Filer Manual v41 6.5.17 page 6-12 | 3 | Decimals-Not-Precision |
EDGAR Filer Manual v41 6.5.19 page 6-12 | 6 | Required-Context-Missing | REMARK: The absence of required context will cause several other errors in section 6.5, this has a separate error code to help users identify the root error of the cascade. REMARK: At this point there is only one distinction, between 485BPOS and 497 which require a one day duration, and all other filings having any duration. At some point in the future this will be extended to include columns that indicate the allowable range of durations, for example:
EDGAR Filer Manual v41 6.5.20 page 6-13 | 192 | Amendment-Flag-Existence Amendment-Description-Without-Amendment-Flag Amendment-Flag-Without-Amendment-Description Document-Type-Existence Document-Period-End-Date-Existence Document-Type-Value Document-Type-Not-Matched-To-Submission-Type | REMARK: There is a mapping from submission types recognized by EDGAR, to the valid values of the dei:DocumentType element, as follows. From the 2012 DEI schema onward, all of the document type values shown are allowed; in earlier schemas you may find that the less common filing types must use other values:
EDGAR Filer Manual v41 6.5.21 page 6-14 | 209 | Entity-Registrant-Name Central-Index-Key Current-Fiscal-Year-End-Date Well-Known-Seasoned-Issuer Entity-Voluntary-Filers Entity-Current-Reporting-Status Entity-Filer-Category Entity-Public-Float Document-Fiscal-Year-Focus Document-Fiscal-Period-Focus |
EDGAR Filer Manual v41 6.5.22 page 6-16 | 2 |  | REMARK: The second variation is logically part of 6.5.20, but it generates no errors so that shouldn't matter.
EDGAR Filer Manual v41 6.5.23 page 6-16 | 6 | Non-Matching-Cik |
EDGAR Filer Manual v41 6.5.24 page 6-16 | 13 | Registrant-Name-Mismatch | REMARK: The syntax of the cikList is comma separated 10-digit numbers [0-9]{10}(,[0-9]{10})* REMARK: The syntax of the cikNameList is "|Edgar|" separated text (.)+(\|Edgar\|,(.)+) REMARK: Continued at 902-sdr-60524
EDGAR Filer Manual v41 6.5.25 page 6-16 | 7 | Domain-As-Fact | REMARK: Only restrictions of the type are relevant because the base type xbrli:stringItemType is declared final in the XBRL 2.1 schema and cannot be extended.
EDGAR Filer Manual v41 6.5.26 page 6-16 | 68 | Common-Shares-Inconsistent-With-Document-Type | REMARK: The rule does not strictly require definition links, only that the contexts use xbrli:explicitMember elements in contexts.
EDGAR Filer Manual v41 6.5.27 page 6-17 | 5 | Footnote-Substitution-Group | REMARK: Although these variations each show only one error code, depending on a vendors' implementation, validation errors may occur prior to the error listed, or other errors may cascade after Footnote-Substitution-Group. In particular, the schema fales of the ng variations should throw error 6.7.27 because they use a substitutionGroup disallowed by that rule; the point being that 6.7.27 would not apply to a standard taxonomy but 6.5.27 would still be an error. As long as all variations marked NOGOOD are rejected because of the disallowed substitutionGroup, a validator may be considered as legitimately passing this testcase.
EDGAR Filer Manual v41 6.5.28 page 6-17 | 3 | Footnote-Custom-Footnote-Role Footnote-Role-Missing | REMARK: The content of the link:definition element is irrelevant because the entire declaration is forbidden. These variations may also signal errors 6.9.4 and 6.9.5 for the schemas, or 6.8.3, but the point is that this test is still meaningful even if the schemas with offending role declarations happened to be in standard taxonomies.
EDGAR Filer Manual v41 6.5.29 page 6-17 | 1 | Footnote-Custom-Loc-Role |
EDGAR Filer Manual v41 6.5.32 page 6-17 | 1 | Footnote-Locator-Portable |
EDGAR Filer Manual v41 6.5.33 page 6-17 | 3 | Dangling-Footnote | REMARK: It would have been better instead of referring to "link:footnote element" to refer to "link:footnoteLink child element with @xlink:type of 'resource'". Likewise instead of "link:footnoteArc element" refer to "link:footnoteLink child element with @xlink:type of 'arc'". Then you will never get spurious errors if element substitutionGroups were to be allowed.
EDGAR Filer Manual v41 6.5.34 page 6-17 | 9 | Prohibited-Html-Footnote-Body | REMARK: XBRL footnotes are not text blocks. Any quoted HTML appearing in an XBRL footnote is just a string. All processing should treat it as a string and nothing more.
EDGAR Filer Manual v41 6.5.35 page 6-17 | 71 | Incompatible-Numeric-Type-And-Unit | REMARK: International types declared at www.xbrl.org can appear in the same DTS with US data types. REMARK: The example values in the table above may not be completely consistent with any specific Unit Types Registry. REMARK: The triggering condition of "element UTR present in a standard namespace" is present in the DEI 2012 taxonomy, but not in any prior version of DEI.
EDGAR Filer Manual v41 6.5.36 page 6-19 | 16 | Name-Length-Limit | REMARK: the unit "u 100 twobyte 1 onebyte" means there is a measure whose local name consists of 100 two-byte unicode characters and one single-byte character.
EDGAR Filer Manual v41 6.5.37 page 6-19 | 6 | Nonzero-Digits-Truncated |
EDGAR Filer Manual v41 6.5.38 page 6-19 | 1 | Context-Has-Period-Forever |
EDGAR Filer Manual v41 6.5.39 page 6-19 | 3 | Segment-Child-Not-Explicit-Member Typed-Dimension-Not-Standard |