Name | Variations | Error Codes | Remarks
--- | --- | --- | ---
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.