Name | Variations | Error Codes | Remarks
--- | --- | --- | ---
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 |
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 | 10 | Domain-Type-Name-Mismatch | REMARK: This only applies to company extension schemas, although it does hold for all standard taxonomies. REMARK: The original wording required a specific US type, not a type derived from it. Now, types in any standard namespace can trigger this rule. 006gd flips to 006ng as a consequence.
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