Name | Variations | Error Codes | Remarks
--- | --- | --- | ---
EDGAR Filer Manual v41 5.2.5 page 5-34 | 89 | EFM.5.02.05.doctypeDisallowed EFM.5.02.05.disallowedMetaContent EFM.5.02.05.xhtmlNamespaceMissing exception:AssertionError EFM.5.02.05.externalReference html:syntaxError EFM.5.02.05.activeContent html:syntaxError EFM.5.02.05.disallowedElement html:syntaxError EFM.5.02.05.disallowedElement html:syntaxError EFM.5.02.05.disallowedElement html:syntaxError EFM.5.02.05.disallowedElement html:syntaxError EFM.5.02.05.disallowedElement html:syntaxError EFM.5.02.05.disallowedElement html:syntaxError EFM.5.02.05.disallowedAttribute html:syntaxError EFM.5.02.05.disallowedAttribute html:syntaxError EFM.5.02.05.disallowedAttribute EFM.5.02.05.nestedTable EFM.5.02.05.schemaLocationDisallowed EFM.5.02.05.anchorElementPosition EFM.5.02.05.graphicFileType EFM.5.02.05.standardNamespacePrefix |
EDGAR Filer Manual v41 5.2.5.12 page 5-40 | 1 |  |
EDGAR Filer Manual v41 5.2.5.12 page 5-40 | 10 | ix11.11.1.1:transformValueError ix11.10.1.1:transformValueError |
EDGAR Filer Manual v41 5.2.5 page 5-34 | 2 |  |
EDGAR Filer Manual v41 5.2.5 page 5-34 | 4 |  | REMARK: The image is referenced correctly and the _htm.xml output is correct; the renderer happens not to handle XHTML in footnotes well.
EDGAR Filer Manual v41 5.2.5.13 page 5-40 | 1 | ix11.8.1.3:headerDisplayNone |
EDGAR Filer Manual v41 5.2.5.13 page 5-40 | 7 | EFM.5.02.05.14.hidden-fact-not-referenced EFM.5.02.05.14.hidden-fact-eligible-for-transform EFM.5.02.05.14.hidden-fact-multiple-references EFM.5.02.05.14.hidden-fact-not-found |
EDGAR Filer Manual v41 5.2.5.11 page 5-39 | 1 | EFM.5.02.05.xmlBaseDisallowed |
EDGAR Filer Manual v41 5.2.5.11 page 5-39 | 1 | EFM.5.02.05.tupleDisallowed |
EDGAR Filer Manual v41 5.2.5.11 page 5-39 | 3 | EFM.5.02.05.targetDisallowed |
EDGAR Filer Manual v41 5.2.5.11 page 5-39 | 1 | EFM.5.02.05.fractionDisallowed |
EDGAR Filer Manual v41 5.2.5 page 5-34 | 1 |  |
Inline XBRL Format Tests NED (Not EDGAR Dependent) | 3 | ix11.10.1.1:transformValueError ix11.10.1.2:invalidTransformation |
Inline XBRL Test Suite v39: Transformation Registry 3 (TR3) tests, Not EDGAR Dependent | 6 | ix11.10.1.1:transformValueError ix11.11.1.1:transformValueError ix11.10.1.2:invalidTransformation ix11.11.1.1:transformValueError |
Inline XBRL Test Suite v39: NonFraction tests, Not EDGAR Dependent | 30 | ix11.10.1.2:nestedNonFractionProperties ix11.10.1.1:attributeNotExpected ix11.10.1.2:nonFractionChildren xmlSchema:attributesExtraneous xmlSchema:valueError ix11.10.1.2:nestedNonFractionProperties ix11.10.1.1:nonFractionTextAndElementChildren ix11.10.1.2:nonFractionChildren ix11.10.1.2:nestedNonFractionIsNil ix11.10.1.2:nestedNonFractionProperties ix11.10.1.1:attributeRequired xmlSchema:valueError ix11.10.1.1:transformValueError ix11.10.1.2:invalidTransformation ix11.10.1.1:nonFractionTextAndElementChildren xbrl.4.6.3:missingPrecisionDecimals xbrl.4.6.3:nilPrecisionDecimals ix11.10.1.2:contextReference ix11.10.1.2:unitReference ix11.10.1.2:nestedNonFractionProperties |
Inline XBRL Test Suite v39: NonNumeric tests, Not EDGAR Dependent | 14 | ix11.11.1.1:attributeNotExpected xmlSchema:attributesExtraneous ix11.11.1.1:attributeNotExpected ix11.11.1.1:transformValueError ix11.11.1.1:attributeRequired ix11.11.1.1:attributeNotExpected ix11.11.1.2:invalidTransformation ix11.11.1.2:contextReference |
Inline XBRL Test Suite v39: Exclude tests, Not EDGAR Dependent | 3 | ix11.5.1.1:ancestorNodeRequired |
Inline XBRL Test Suite v39: IDs tests, Not EDGAR Dependent | 10 | xml.3.3.1:idMustBeUnique |
Inline XBRL Test Suite v39: Continuation tests, Not EDGAR Dependent | 16 | ix11.4.1.2:continuationReferences ix11.4.1.2:continuationCycle ix11.11.1.2:continuationChainNested ix11.11.1.2:continuationTarget ix11.4.1.2:continuationReferences ix11.6.1.2:continuationChainNested ix11.11.1.2:continuationMissing ix11.4.1.2:continuationChainNested ix11.4.1.2:continuationMissing ix11.4.1.2:continuationNotReferenced xml.3.3.1:idMustBeUnique ix11.4.1.1:ancestorNodeDisallowed ix11.4.1.2:continuationNotReferenced ix11.4.1.2:continuationTarget ix11.4.1.2:continuationCycle |
Inline XBRL Test Suite v39: Relationship tests, Not EDGAR Dependent | 7 | ix11.13.1.2:relationshipReferencesMixed ix11.13.1.1:attributeNotExpected xbrl.5.1.4.3:cycles ix11.13.1.1:qualifiedAttributeNotExpected |
Inline XBRL Test Suite v39: Footnote tests, Not EDGAR Dependent | 12 | ix11.6.1.1:qualifiedAttributeNotExpected ix11.6.1.1:attributeRequired xml.3.3.1:idMustBeUnique ix11.6.1.2:continuationMissing ix11.6.1.1:childNodesOrTextRequired ix11.13.1.2:relationshipFromRef ix11.13.1.2:relationshipToRef ix11.6.1.2:footnoteLang |
Inline XBRL Test Suite v39: Header tests, Not EDGAR Dependent | 4 | ix11.8.1.3:headerMissing html:syntaxError ix11.8.1.1:childNodesAllowed |
Inline XBRL Test Suite v39: Hidden tests, Not EDGAR Dependent | 5 | ix11.9.1.1:childNodesRequired ix11.9.1.1:childNodesAllowed ix11.9.1.1:parentNodeRequired ix11.8.1.1:childNodesAllowed |
Inline XBRL Test Suite v39: References tests, Not EDGAR Dependent | 16 | ix11.12.1.2:missingReferences ix11.12.1.1:qualifiedAttributeDisallowed xml.3.3.1:idMustBeUnique ix11.12.1.2:missingReferences ix11.12.1.2:referencesNamespacePrefixConflict ix11.12.1.1:childNodesAllowed ix11.8.1.1:childNodesAllowed ix11.12.1.1:parentNodeRequired ix11.12.1.2:referencesAttributeDuplication ix11.12.1.2:referencesTargetId ix11.12.1.2:referencesNamespacePrefixConflict ix11.12.1.2:referencesAttributeDuplication ix11.12.1.2:referencesNamespacePrefixConflict |
Inline XBRL Test Suite v39: Resources tests, Not EDGAR Dependent | 4 | ix11.14.1.2:missingResources xmlSchema:attributesRequired |
Inline XBRL Test Suite v39: BaseURI tests, Not EDGAR Dependent | 2 | ix11.8.1.1:qualifiedAttributeNotExpected html:syntaxError |
Inline XBRL Test Suite v39: IDs tests, Not EDGAR Dependent | 6 | ix11.6.1.2:footnoteLang ix11.9.1.1:qualifiedAttributeNotExpected ix11.8.1.1:qualifiedAttributeNotExpected |
EDGAR Filer Manual v41 6.3.2 page 6-5 | 2 | Both-EX-100-And-EX-101 Attachment-Type | REMARK: Variation 001ng cannot be tested without the edgarSubmission XML document. REMARK: This test is continued at ../../902-sdr/60302-sdr-doctype/
EDGAR Filer Manual v41 6.3.3 page 6-6 | 3 | Valid-File-Extension | REMARK: File names are case sensitive, and since January 2011, uppercase characters have been permitted.
EDGAR Filer Manual v41 6.3.4 page 6-6 | 2 | Invalid-Html-In-Footnote Invalid-Html-In-Linkbase | REMARK: This test suite does NOT test to see that only the subset of ASCII allowed by 5.2.1.1 are used.
EDGAR Filer Manual v41 6.3.5 page 6-6 | 6 | Invalid-Characters | REMARK: the files e60305001ng-20111231.xml and e60305002ng-20111231_lab.xml are not even good XML, so don't try to process them as such. REMARK: this testcase is also a convenient place to test compliance with EFM section 5.2 listing a few common but disallowed characters.
EDGAR Filer Manual v41 6.3.6 page 6-7 | 8 | Fragment-Not-Shorthand-Xpointer | REMARK: xml:base is forbidden. REMARK: RFC 2396 defines URI syntax
EDGAR Filer Manual v41 6.3.8 page 6-7 | 2 | More-Than-One-Ins | REMARK: The EDGAR submission system has an Exhibit type and this is passed into the validator.
EDGAR Filer Manual v41 6.3.10 page 6-7 | 1 | Missing-Schema |
EDGAR Filer Manual v41 6.3.11 page 6-7 | 10 | Use-Of-Xml-Base-Attribute-Illegal |
EDGAR Filer Manual v41 6.4.3 page 6-8 | 29 | Xbrl21-Invalid | REMARK: XBRL 1.0 Dimensional validity is required also. REMARK: This obviously does not test all XBRL 2.1, only those areas that have been known to cause problems. REMARK: At this time, only one instance is allowed per submission.
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-Dimension Typed-Dimension-Not-Standard |
EDGAR Filer Manual v41 6.7.1 page 6-32 | 1 | Schema-Include-Present | REMARK: Because this applies only to company extensions, in principle there could be a test in which a standard taxonomy schema having an 'include' element would be 'GOOD', but there is no such standard taxonomy schema.
EDGAR Filer Manual v41 6.7.3 page 6-32 | 7 | Extension-Has-Standard-Namespace-Authority | REMARK: For purposes of this test edgartaxonomies.xml is the authoritative source of "standard taxonomies".
EDGAR Filer Manual v41 6.7.4 page 6-32 | 8 | Taxonomy-Valid-Target-Namespace |
1 |  |
EDGAR Filer Manual v41 6.7.7 page 6-34 | 3 | Recommended-Prefix-Disallowed | REMARK: This only applies to a company extension schema. A standard taxonomy could in principle have an underscore in their namespace prefix, but there is no such standard taxonomy and therefore no such test variation.
EDGAR Filer Manual v41 6.7.8 page 6-34 | 1 | No-Embedded-Linkbases | REMARK: This applies only to company extension schemas. In principle a standard taxonomy is allowed to have an embedded linkbase. But there is no such standard taxonomy and therefore no such test variation. REMARK: there are no variations for linkbases other than link:labelLink, but the rule does apply to all of them.
EDGAR Filer Manual v41 6.7.9 page 6-34 | 3 | Role-Namespace-Mismatch | REMARK: http://www.ietf.org/rfc/rfc2396.txt notes that the host component of a URL is case insensitive, a URI in Interactive Data documents has a case-sensitive host component. The same rfc allows characters in URIs that are not normally thought of as legal; variation 000gd exercises that in a minimal way without wading into the complex realm of XML character escaping versus URI character escaping. REMARK: This applies only to company extension schemas. In principle a standard taxonomy could have a different authority part in the targetNamespace and a role or arcrole declaration. There being no such standard taxonomies, there are no such 'gd' variations.
EDGAR Filer Manual v41 6.7.10 page 6-34 | 2 | Role-Type-Duplicates | REMARK: this applies to the entire DTS, not just each individual schema which is what the similar XBRL 2.1 constraint applies to.
EDGAR Filer Manual v41 6.7.11 page 6-34 | 4 | Role-Type-Declaration-Incomplete | REMARK: this applies only to company extension schemas, so that exceptions in the us-roles-YYYY-MM-DD.xsd schemas are not invalid.
EDGAR Filer Manual v41 6.7.12 page 6-35 | 8 | Role-Definition-Mismatch | REMARK: This applies only to company extension schemas, so that exceptions in the us-roles-YYYY-MM-DD.xsd schemas are not invalid.
EDGAR Filer Manual v41 6.7.13 page 6-36 | 2 | Arcrole-Namespace-Mismatch | REMARK: This applies only to company extension schemas. In principle a standard taxonomy schema could violate this, but there are no such taxonomy schemas and so no 'good' variation. REMARK: An arcrole definition should not have to match the same pattern as presentation definitions, but we do so in this testcase to avoid spurious errors.
EDGAR Filer Manual v41 6.7.14 page 6-37 | 2 | Arcrole-Type-Duplicates | REMARK: this applies to the entire DTS not just company extension schemas.
EDGAR Filer Manual v41 6.7.15 page 6-37 | 2 | Arcrole-Definition-Missing | REMARK: The test for emptiness is done after trimming. REMARK: this applies only to company extension schemas, so if there were any exceptions standard schemas those would not be invalid.
EDGAR Filer Manual v41 6.7.16 page 6-37 | 6 | Element-Name-Same-As-Base | REMARK: For purposes of this test, the copy of edgartaxonomies.xml in the "lib" folder defines "standard taxonomy".
EDGAR Filer Manual v41 6.7.17 page 6-37 | 3 | Element-Id | REMARK: This only applies to the company extension schemas. If there were a standard taxonomy schema that violated this, it would nevertheless be good. There being no such standard taxonomy, there is no such test variation.
EDGAR Filer Manual v41 6.7.18 page 6-37 | 2 | Nillable-Not-True | REMARK: This only applies to the company extension schemas. If there were a standard taxonomy schema that violated this, it would nevertheless be good. There being no such standard taxonomy, there is no such test variation. REMARK: This is only meant to apply to element declarations in an xbrli substitution group. In the current EDGAR release, non-XBRL element declarations are effectively useless, but nevertheless variation 000gd tests that case.
EDGAR Filer Manual v41 6.7.19 page 6-37 | 1 | No-Tuple-Element | REMARK: This only applies to company extension schemas, although it happens to hold for all standard taxonomies. At one time ICI 2006 was the basis of other variations, but it now has been removed from edgartaxonomies.xml, so there are no such variations.
EDGAR Filer Manual v41 6.7.20 page 6-37 | 1 | Typed-Domain-Ref-Disallowed | REMARK: This only applies to company extension schemas, although it also holds for all standard taxonomies. If there were a standard taxonomy that used xbrldt:typedDomainRef then there would be 'good' test variation covering it.
EDGAR Filer Manual v41 6.7.21 page 6-37 | 1 | Abstract-Is-Instant | REMARK: This only applies to company extension schemas, although it does hold for all standard taxonomies other than the ICI 2006 taxonomy. The ICI 2006 taxonomy can only be used with EX-100 attachments, to which rules in Chapter 6 do not apply.
EDGAR Filer Manual v41 6.7.23 page 6-37 | 2 | Axis-Dimension-Name-Mismatch | REMARK: This only applies to company extension schemas, although it does hold for all standard taxonomies other than the ICI 2006 taxonomy. The ICI 2006 taxonomy can only be used with EX-100 attachments, to which rules in Chapter 6 do not apply.
EDGAR Filer Manual v41 6.7.24 page 6-38 | 2 | Table-Hypercube-Name-Mismatch | REMARK: This only applies to company extension schemas, although it does hold for all standard taxonomies other than the ICI 2006 taxonomy. The ICI 2006 taxonomy can only be used with EX-100 attachments, to which rules in Chapter 6 do not apply.
EDGAR Filer Manual v41 6.7.25 page 6-38 | 2 | Substitution-Group-Custom | REMARK: This only applies to company extension schemas, although it does hold for all standard taxonomies. If there were any such standard taxonomy it would be included in a 'good' test variation. REMARK: This does allow @substitutionGroup to be absent, so it would allow non-XBRL elements and that may have some use in some future EDGAR release.
EDGAR Filer Manual v41 6.7.26 page 6-38 | 2 | LineItems-Abstract-Name-Mismatch | REMARK: This only applies to company extension schemas, although it does hold for all standard taxonomies. If there were any such standard taxonomy it would be included in a 'good' test variation.
EDGAR Filer Manual v41 6.7.27 page 6-38 | 8 | Domain-Type-Name-Mismatch | REMARK: This only applies to company extension schemas, although it does hold for all standard taxonomies.
EDGAR Filer Manual v41 6.7.28 page 6-38 | 4 | Domain-Member-Is-Instant | REMARK: this only applies to company extension schemas, although it holds for all standard taxonomies. If there were a standard taxonomy that violated the rule, it would appear in a 'good' test variation.
EDGAR Filer Manual v37 6.7.29 page 6-38 | 12 | Name-Length-Limit | REMARK: the phrase "u100twobyte1onebyte" means there is a local name that consists of 100 two-byte unicode characters and one single-byte character.
EDGAR Filer Manual v41 6.7.30 page 6-38 | 6 | Name-Length-Limit |
EDGAR Filer Manual v41 6.7.31 page 6-38 | 3 | Fraction-Item-Type |
EDGAR Filer Manual v41 6.7.32 page 6-38 | 22 | Nonnumeric-Has-Instant-Period-Type | REMARK: Element declarations that are abstract must have period type 'duration' due to 6.7.21, and declarations derived from domainItemType must have period type 'duration' whether abstract or not due to 6.7.28. This validation covers all other non numeric types. REMARK: The nonnumeric base types are:
xbrli:anyURIItemType
xbrli:base64BinaryItemType
xbrli:booleanItemType
xbrli:dateItemType
xbrli:dateTimeItemType
xbrli:durationItemType
xbrli:gDayItemType
xbrli:gMonthDayItemType
xbrli:gMonthItemType
xbrli:gYearItemType
xbrli:gYearMonthItemType
xbrli:hexBinaryItemType
xbrli:languageItemType
xbrli:NameItemType
xbrli:NCNameItemType
xbrli:normalizedStringItemType
xbrli:QNameItemType
xbrli:stringItemType
xbrli:timeItemType
nonnum:escapedItemType
dei:yesNoItemType
xbrli:stringType
EDGAR Filer Manual v41 6.9.3 page 6-45 | 16 | Relationship-Ineffectual | REMARK: The text of EFM v22 fails to capture all intended cases and will be expanded as follows in a subsequent release:
EDGAR Filer Manual v41 6.9.4 page 6-45 | 1 | Resource-Role-Missing | REMARK: Note that type='extended' is handled by XBRL 2.1 so this really only applies to type='resource', and there are other rules for reference and footnote that would trigger errors if the xlink:role were missing. Therefore just one variation for the label resource, for now. Also note that this only applies to a company extension linkbase.
EDGAR Filer Manual v41 6.9.5 page 6-45 | 3 | Custom-Resource-Role-Used | REMARK: type='extended' is handled by XBRL 2.1 so this really only applies to type='resource', moreover, footnote and reference would be handled by other rules so this is only for labels. REMARK: This only applies to a company extension linkbase. There is no standard taxonomy linkbase that violates this rule, but if there were, it would be included in a 'good' test variation. REMARK: the roles declared in these tests have link:definition text that conforms to 6.7.12 even though 6.7.12 was only meant to apply to roles that are used on link:presentation.
EDGAR Filer Manual v41 6.9.6 page 6-45 | 2 | Custom-Arcrole-Referenced | REMARK: This applies only to company extension taxonomies. The arc roles declared in http://www.xbrl.org/2005/xbrldt-2005.xsd are okay because that is a standard taxonomy location. The arc roles declared in US GAAP 2009 are not in a standard taxonomy location.
EDGAR Filer Manual v41 6.9.7 page 6-46 | 1 | Linkbases-Distinct | REMARK: Although this error is caught at the EDGARLink submission (transport) level it is easy to verify before attempted submission. REMARK: This only applies to a company extension linkbase. There is no standard taxonomy linkbase that violates this rule, but if there were, it would be included in a 'good' test variation.
EDGAR Filer Manual v41 6.9.9 page 6-46 | 2 | Relationship-Priority-Not-Less-Than-Ten | REMARK: This only applies to a company extension linkbase. The RR 2010 and 2012 standard taxonomy linkbases contain links with priority attributes of 10, and rr 2012 is therefore a 'good' test variation.
EDGAR Filer Manual v41 6.10.1 page 6-46 | 11 | Element-Used-Standard-Label | REMARK: The xlink:role value on the LabelLink element is not relevant. REMARK: Also, case 015ng and 016ng will cause a 6.10.13 error as well as a 6.10.1 error.
EDGAR Filer Manual v41 6.10.2 page 6-46 | 6 | Element-Used-Has-Duplicate-Label | REMARK: the value of xlink:role on the LabelLink is not relevant.
EDGAR Filer Manual v41 6.10.3 page 6-47 | 6 | Element-Used-Standard-English-Label |
EDGAR Filer Manual v41 6.10.4 page 6-47 | 4 | English-Standard-Labels-Duplicated | REMARK: this restriction applies to all elements, not just those used in the instance.
EDGAR Filer Manual v41 6.10.5 page 6-47 | 2 | Custom-Documentation-Standard-Element | REMARK: This only applies to company extension linkbases. If edgartaxonomies.xml were to list a standard taxonomy linkbase containing 'documentation' label roles, then that standard taxonomy linkbase would be included in a 'good' testcase variation.
EDGAR Filer Manual v41 6.10.6 page 6-47 | 5 | Label-Disallowed | REMARK: This only applies to company extension label linkbases. If a standard taxonomy label linkbase appearing in edgartaxonomies.xml violated this rule it would be included in a 'good' test variation.
EDGAR Filer Manual v41 6.10.8 page 6-47 | 3 | Label-Not-Trimmed | REMARK: This only applies to company extension label linkbases. If a standard taxonomy label linkbase appearing in edgartaxonomies.xml were to violate this rule, then it would be included in a 'good' test variation.
EDGAR Filer Manual v41 6.10.9 page 6-47 | 16 | Numeric-Label-Role |
EDGAR Filer Manual v41 6.12.1 page 6-52 | 1 | Presentation-Order-Missing | REMARK: This only applies to company extension linkbases. If a standard taxonomy linkbase appearing in edgartaxonomies.xml violated this rule it would be included in a 'good' test variation.
EDGAR Filer Manual v41 6.12.2 page 6-52 | 2 | Presentation-Order-Duplicates | REMARK: this rule applies whether either of the elements in the presentation arcs used in an instance or not REMARK: This only applies to company extension linkbases. If a standard taxonomy linkbase appearing in edgartaxonomies.xml violated this rule it would be included in a 'good' test variation.
EDGAR Filer Manual v41 6.12.3 page 6-52 | 7 | Element-Used-Not-Presented |
EDGAR Filer Manual v41 6.12.5 page 6-52 | 5 | Preferred-Label-Duplicates |
EDGAR Filer Manual v41 6.12.6 page 6-53 | 2 | Multiple-Root-Nodes |
EDGAR Filer Manual v41 6.12.7 page 6-53 | 4 | Period-Type-Preferred-Label-Mismatch |
EDGAR Filer Manual v41 6.12.8 page 6-53 | 2 | Axis-Requires-Domain-Child | REMARK: This is not the same condition as implemented in rendering engine 3.3.0.814, but it is logically sound.
EDGAR Filer Manual v41 6.12.9 page 6-53 | 3 | Presented-Units-Incomplete-Order |
EDGAR Filer Manual v41 6.14.1 page 6-54 | 1 | Calculation-Relationship-Order-Missing | REMARK: This only applies to company extension linkbases. If a standard taxonomy linkbase appearing in edgartaxonomies.xml violated this rule it would be included in a 'good' test variation.
EDGAR Filer Manual v41 6.14.2 page 6-54 | 1 | Calculation-Relationship-Weight-Not-Unitary | REMARK: This only applies to company extension linkbases. If a standard taxonomy linkbase appearing in edgartaxonomies.xml violated this rule it would be included in a 'good' test variation.
EDGAR Filer Manual v41 6.14.3 page 6-54 | 1 | Calculation-Relationship-Has-Different-Period-Types | REMARK: This only applies to company extension linkbases. If a standard taxonomy linkbase appearing in edgartaxonomies.xml violated this rule it would be included in a 'good' test variation. In fact, because there are no standard taxonomies that violate the rule, there is not even a variation that tests whether such a bad arc would be okay if prohibited.
EDGAR Filer Manual v41 6.14.4 page 6-54 | 3 | Circular-Calculation | REMARK: This only applies to company extension linkbases. If a standard taxonomy linkbase appearing in edgartaxonomies.xml violated this rule it would be included in a 'good' test variation. In particular, add this test: calculation arcs form a directed cycle, but one of the imported standard arcs is prohibited, GOOD.
EDGAR Filer Manual v41 6.14.5 page 6-54 | 10 | Facts-In-Calculations-Presentation-Missing |
EDGAR Filer Manual v41 6.16.1 page 6-56 | 1 | Definition-Relationship-Order-Missing | REMARK: This only applies to company extension linkbases. If a standard taxonomy linkbase appearing in edgartaxonomies.xml violated this rule it would be included in a 'good' test variation.
EDGAR Filer Manual v41 6.16.3 page 6-57 | 2 | Dimension-Domain-Target-Mismatch | REMARK: Note that it is not necessary for the target element to be used in the instance, for this to be a violation.
EDGAR Filer Manual v41 6.16.4 page 6-57 | 14 | Domain-Is-Tangled | REMARK: DRS discovery begins at dimension-domain relationships. Whether the domain member appears in instance facts is not relevant.
EDGAR Filer Manual v41 6.16.5 page 6-57 | 2 | Primary-Element-Has-Redundant-Tables | REMARK: This constraint does not take primary item inheritance into account, and therefore rules out the simplest uses of unions of 'all' hypercubes. A future release may take primary item inheritance into account and therefore implementors may wish to issue a warning in situations like that shown in variation 002gd. REMARK: This only applies to company extension linkbases. Because the standard linkbases now all have priority 10 on their definition arcs, there is no way to prohibit them and so that variation of the test is not included here.
EDGAR Filer Manual v41 6.16.6 page 6-57 | 1 | Not-All-Relationship-Is-Closed | REMARK: This only applies to company extension linkbases. If a standard taxonomy linkbase appearing in edgartaxonomies.xml violated this rule it would be included in a 'good' test variation.
EDGAR Filer Manual v41 6.16.7 page 6-57 | 3 | Axis-Excluded-Not-In-Table | REMARK: Ordinarily there would be a test here which would have a prohibited notAll arc somewhere; can't do that in this test because no standard taxonomy has a notAll, and the prohibition on ineffectual arcs prevents me from putting one in here. So those were variations 001 and 003 and they are not in here. REMARK: This rule is intended to ensure that the notAll arc does not forbid members of a dimension that is not even relevant to a hypercube. domain-member relationships between P1 and P2 are not relevant, since neither all nor notAll are ever consecutive from domain-member. Note that the rule assumes, but does not require, that the target roles on HcDim1 and HcDim2 are different, so that the members of Dim1 are different in HC1 and HC2. REMARK: The rule, as written, fails to make explicit that the condition can only be evaluated with respect to some primary item; without some primary item as a common ancestor, dimensions are irrelevant to each other. In variation 003ng, the element EntityTaxIdentificationNumber has a notAll, but no all (and neither does any ancestor in that role).
EDGAR Filer Manual v41 6.16.8 page 6-58 | 2 | Table-Excludes-Itself | REMARK: This rule complements 6.16.7 by ensuring that HC1 and HC2 are distinct. The combination of this constraint, 6.16.4, and XBRL Dimensions 1.0 constraint's prohibition of undirected cycles in HcDim relationships prevents using @targetRole to give the same HC element different members of the same axis.
EDGAR Filer Manual v41 6.16.9 page 6-58 | 9 | Target-Role-With-No-Consecutive-Relationships | REMARK: Consecutive relationships are defined at http://www.xbrl.org/Specification/XDT-REC-2006-09-18.htm#_2.1.1 and consist only of the following initial-following arc role pairs: all, hypercube-dimension; not-all, hypercube-dimension; hypercube-dimension, dimension-domain; dimension-domain, domain-member; domain-member, domain-member. Note that domain-member is never followed by all, not-all, or any arcrole other than domain-member.
EDGAR Filer Manual v41 6.18.1 page 6-58 | 2 | Custom-Element-Has-Reference | REMARK: A company extension also cannot remove or change references in standard taxonomies (this is a technical consequence of the rule prohibiting URI fragments other than shorthand xpointers). REMARK: This only applies to company extension linkbases. If there were a reference linkbase in edgartaxonomies.xml, then it would be included in a 'good' test variation.
EDGAR Filer Manual v41 6.18.2 page 6-59 | 1 | Standard-Element-Has-Reference | REMARK: 6.19 reads "A company extension also cannot remove or change references in standard taxonomies (this is a technical consequence of the rule prohibiting URI fragments other than shorthand xpointers)." but this does not explicitly say the obvious point that you can't ADD authoritative references, either.
EDGAR Filer Manual v41 6.22.1 page 6-60 | 10 |  | REMARK: There is no such section 6.22.1, it is meant to refer to 'taxonomies that we allow'. For purposes of this test edgartaxonomies.xml is the ONLY authoritative source of "standard taxonomies". This test checks the allowed files in groups according to family and version (i.e., release). REMARK: This test leaves out USFRTF and ICI given that none of the other EDGAR validations apply to them.
EDGAR Filer Manual v41 6.22.2 page 6-60 | 20 | Prohibited-Href-Or-Schema-Location | REMARK: There is no such section 6.22.2, it is meant to refer to 'files that are likely to be referenced but that actually we do not allow.'. Keep in mind that http://www.sec.gov/info/edgar/edgartaxonomies.xml is the ONLY authoritative source of "standard taxonomies". In this test suite we test a subset of the disallowed files, one at a time. REMARK: Test variations that reference disallowed versions of the DEI schema may produce downstream errors as a consequence of the unloadable schema and elements in that dei namespace being undefined.
EDGAR Filer Manual v41 6.22.3 page 6-60 | 4 | Inconsistent-Schemas | REMARK: There is no such section 6.22.3, these tests were originally meant only to verify that 2008 taxonomies work together but do not work with the 2009 or subsequent taxonomies because of the XBRL 2.1 level conflict between roleType declarations (when their allowed linkbases are included in the mix). Eventually, taxonomies of different vintages are expected to coexist in a DTS without XBRL-level errors and this testcase will not be necessary. In the meantime and until further notice, other filing considerations mean that some taxonomies remain incompatible as listed below. Linkbase versions are only relevant insofar as there are schemas that would appear in the DTS as a consequence of processing that linkbase.
EDGAR Filer Manual v41 6.22.5 page 6-60 | 4 | Prohibited-Href-Or-Schema-Location | REMARK: There is no such section 6.22.5, it is meant to refer to 'files that are likely to be referenced but that actually we do not allow.'. Keep in mind that http://www.sec.gov/info/edgar/edgartaxonomies.xml is the ONLY authoritative source of "standard taxonomies". In this test suite we test a subset of the disallowed files, one at a time.
EDGAR Filer Manual v41 6.24.01 page 6-60 | 3 |  |
EDGAR Filer Manual v41 6.24.02 page 6-60 | 2 |  |
EDGAR Filer Manual v41 6.24.03 page 6-61 | 1 |  |
EDGAR Filer Manual v41 6.24.04 page 6-61 | 1 |  |
EDGAR Filer Manual v41 6.24.05 page 6-61 | 1 |  |
EDGAR Filer Manual v41 6.24.06 page 6-61 | 3 |  |
EDGAR Filer Manual v41 6.24.07 page 6-62 | 5 |  |
EDGAR Filer Manual v41 6.24.08 page 6-63 | 2 |  |
EDGAR Filer Manual v41 6.24.09 page 6-63 | 3 |  |
EDGAR Filer Manual v41 6.24.10 page 6-64 | 2 |  |
EDGAR Filer Manual v41 6.24.11 page 6-64 | 3 |  |
EDGAR Filer Manual v41 6.24.12 page 6-65 | 1 |  |
EDGAR Filer Manual v41 6.24.13 page 6-65 | 1 |  |
EDGAR Filer Manual v41 6.24.14 page 6-65 | 1 |  |
EDGAR Filer Manual v41 6.24.15 page 6-65 | 2 |  |
EDGAR Filer Manual v41 6.24.16 page 6-66 | 1 |  |
EDGAR Filer Manual v41 6.24.17 page 6-66 | 1 |  |
EDGAR Filer Manual v41 6.24.18 page 6-67 | 1 |  |
EDGAR Filer Manual v41 6.24.19 page 6-67 | 2 |  |
EDGAR Filer Manual v41 6.24.20 page 6-68 | 2 |  |
EDGAR Filer Manual v41 6.24.21 page 6-68 | 1 |  |
EDGAR Filer Manual v41 6.24.22 page 6-69 | 1 |  |
EDGAR Filer Manual v41 6.25.01 page 6-69 | 3 |  |
EDGAR Filer Manual v41 6.25.02 page 6-70 | 1 |  |
EDGAR Filer Manual v41 6.26.1 page 6-71 | 3 | All-Facts-Filtered |
EDGAR Filer Manual v41 6.26.2 page 6-71 | 5 | Instant-Without-Matching-Duration |
EDGAR Filer Manual v41 6.26.3 page 6-71 | 2 | No-Matching-Durations |
EDGAR Filer Manual v41 6.26.4 page 6-71 | 8 | Embedding-Command-Malformed-Direction-Token Embedding-Command-Malformed-Axis Embedding-Command-Malformed-Style-Token Embedding-Command-Malformed-Member Embedding-Command-Invalid-Member |
EDGAR Filer Manual v41 6.26.5 page 6-72 | 5 | Embedding-Command-Missing-Iterator |
EDGAR Filer Manual v41 6.26.6 page 6-72 | 1 | Axis-Has-No-Order | REMARK: When triggered, this warning is preceded by 6.12.06-Multiple-Root-Nodes warning because without the axis in the presentation group, no facts with that axis would appear at all.
EDGAR Filer Manual v41 6.26.7 page 6-72 | 1 | Bar-Chart-Has-No-Facts |
EDGAR Filer Manual v41 6.26.8 page 6-72 | 1 | Too-Many-Annual-Return-Facts |
EDGAR Filer Manual v41 6.26.9 page 6-72 | 1 | primary-axis-on-rows |
EDGAR Filer Manual v41 9.2.15 page 9-199 | 18 | Sdr-Has-Multiple-K-Reports Submission-Document-Type Sdr-Missing-Standard-Schema Sdr-Missing-Files No-Embedded-Linkbases Sdr-Missing-Files No-Embedded-Linkbases Sdr-Missing-Files No-Embedded-Linkbases Sdr-Missing-Files No-Embedded-Linkbases No-Link-Element | REMARK: This continues ../../603-filing-syntax/603-02-not-both-ex100-and-ex101
EDGAR Filer Manual v41 6.3.8 page 6-7 | 2 | Submission-Document-Type Disallowed-Combination-Of-Exhibits | REMARK: This is a continuation of 603-08
EDGAR Filer Manual v41 6.5.24 page 6-16 | 5 | Multiple-L-Sdr-Reports-For-Entity | REMARK: Continued from 60524
EDGAR Filer Manual v41 9.2.15 page 9-199 | 2 |  | REMARK: This continues ../../624-rendering/21-multiple
EDGAR Filer Manual v41 9.2.15 page 9-199 | 2 |  | REMARK: This continues ../../701-inline/efm