# EDGAR XBRL Validation Errors
Message ID | Message | Subsection
cp-0200-Standard-Taxonomies-Version-Conflict | The same roles are declared in us-roles-2008-03-31.xsd and us-roles-2009-01-31.xsd. Please recheck your submission and remove the conflict. | 6.2.0
cp-0303-Valid-File-Extension | The document type and naming of "{...}" naming is not consistent with one or more of the following: EX-101.INS - XBRL Instance document (Required) *.xml EX-101.SCH - XBRL Taxonomy Extension Schema document *.xsd EX-101.CAL - XBRL Taxonomy Extension Calculation Linkbase document *.xml EX-101.DEF - XBRL Taxonomy Extension Definition Linkbase document *.xml EX-101.LAB - XBRL Taxonomy Extension Labels Linkbase document *.xml EX-101.PRE - XBRL Taxonomy Extension Presentation Linkbase document *.xml EX-101.REF - XBRL Taxonomy Extension Reference Linkbase document *.xml Please ensure that you comply with the document type and naming provided. | 6.3.3
Uri-Shorthand-Pointers | Illegal shorthand pointer syntax {...} referenced by {...} in {...} on line {...} | 6.3.6
Use-Of-Xml-Base-Attribute-Illegal | Illegal use of xml:base to {...} referenced by {...} in {...} on line {...} | 6.3.11
cp-0501-Entity-Identifier-Scheme | Your identifier for the CIK code, {...}, or scheme {...}, in context {...}, did not adhere to the standard naming convention of <identifier scheme="http://www.sec.gov/CIK">xxxxxxxxxx</identifier>". Please recheck your submission and comply with the standard naming convention. | 6.5.1
cp-0504-No-Scenario | There must be no contexts with scenarios, but {...} was(were) found: {...}. | 6.5.4
cp-0505-Segment-Child-Not-Explicit-Member | There must be no segments with non-explicitDimension content, but {…} was(were) found: {…} | 6.5.5
du-0507-Duplicate-Contexts | The instance document contained more than one context equivalent to {...}. Please remove duplicate contexts from the instance. | 6.5.7
du-0508-Unused-Context | The instance document contained a context {...} that was not used in any fact. Please remove the context from the instance. | 6.5.8
fs-0509-Start-And-End-Dates-Not-Distinct-Inconsistent-With-Document-Type | Context {...} endDate and {...} startDate have a duration of one day; that is inconsistent with document type {...}. | 6.5.9
fs-0510-Start-And-Instant-Dates-Not-Distinct-Inconsistent-With-Document-Type | Contexts {...} and {...} have an overlap of one day; that is inconsistent with document type {...}. | 6.5.10
du-0511-Duplicate-Units | There is more than one unit equivalent to {...}. Please remove all but one and resubmit. | 6.5.11
du-0512-Duplicate-Facts | The instance document contained an element, {...} that was used more than once in contexts equivalent to {...}. Please ensure there are no duplicate combinations of concept and context in the instance. | 6.5.12
du-0514-English-Text-Missing | Element {...} in context {...} has text with xml:lang other than "en-US" without matching English text. Please provide a fact with xml:lang equal to "en-US". | 6.5.14
cp-0515-Text-Block-Not-Well-Formed-XML | A {...} fact contains unbalanced tags, in {...}, line {...}. (For example, <BR> must be followed by </BR>; values of attributes such as "align" must be quoted, as in align="center".) XML parser messages: {...}. | 6.5.15
cp-0516-Prohibited-Html-Body | A {...} fact, in {...}, line {...}, contains text that is not valid for the content of the HTML "body" tag: {...}. | 6.5.16
fs-0517-Decimals-Not-Precision | Your filing contained elements using the precision attribute. Please recheck your submission and replace the precision attribute with the decimals attribute. | 6.5.17
cp-0520-Document-Period-End-Date-Existence | You did not include the following data: DocumentPeriodEndDate. Please include DocumentPeriodEndDate. | 6.5.20
cp-0520-Document-Type-Existence | You did not include the following data: DocumentType Please include DocumentType. | 6.5.20
cp-0520-Document-Type-Value | Your dei:DocumentType has an illegal value, {...}. Please correct it. | 6.5.20
fs-0520-Amendment-Description-Without-Amendment-Flag | AmendmentFlag is not true in context {...}, so do not provide an AmendmentDescription in that context. | 6.5.20
Existence-DEI-EntityCentralIndexKey | You did not include the following data: EntityCentralIndexKey for the required context. Please include EntityCentralIndexKey. | 6.5.21
cp-0521-Amendment-Flag-Existence | You did not include the following data: AmendmentFlag. Please include AmendmentFlag. | 6.5.21
im-0521-Amendment-Flag-Value | The value provided for Amendment Flag, {...}, is not a valid boolean value (true or false). Please include a valid AmendmentFlag. | 6.5.21
im-0521-Document-Period-End-Date-Value | You did not include the following data: DocumentPeriodEndDate. Please include DocumentPeriodEndDate. | 6.5.21
im-0521-Entity-Current-Reporting-Status | You did not include the following data: EntityCurrentReportingStatus. Please include EntityCurrentReportingStatus. | 6.5.21
im-0521-Entity-Filer-Category | You did not include the following data: EntityFilerCategory. Please include EntityFilerCategory. | 6.5.21
im-0521-Entity-Common-Shares-Outstanding | The instance document has Document Type of {...} but does not have a value for the number of common shares outstanding, dei:EntityCommonStockSharesOutstanding. | 6.5.21
im-0521-Entity-Public-Float | The instance document has dei:DocumentType of {...} but does not have a value for the public float, dei:EntityPublicFloat. | 6.5.21
im-0521-Current-Fiscal-Year-End-Date | Document type {...} requires a value for dei:CurrentFiscalYearEndDate in the Required Context. | 6.5.21
im-0521-Well-Known-Seasoned-Issuer | Document type {...} requires a value for dei:EntityWellKnownSeasonedIssuer in the Required Context. | 6.5.21
im-0521-Entity-Voluntary-Filers | Document type {...} requires a value for dei:EntityVoluntaryFilers in the Required Context. Please recheck your submission and provide the current voluntary filer information. | 6.5.21
cp-0521-Entity-Registrant-Name | The Official Registrant name, {...}, does not match the value {...} in the Required Context. Please correct dei:EntityRegistrantName. | 6.5.21
cp-0523-Non-Matching-Cik | The submission CIK, {...} does not match either the EntityCentralIndexKey, {...}, or context identifier CIK(s) {...}, or is not 10 digits, for required context(s). Please include a correct matching EntityCentralIndexKey and context identifier CIK(s) in the filing. | 6.5.23
cp-0524-Registrant-Name-Mismatch | The Official Registrant name, {...}, does not match the value {...} in the Required Context. Please correct dei:EntityRegistrantName. | 6.5.24
du-0525-Domain-As-Fact | The domain item {...} cannot appear as a fact, in {...} line {...}. Please remove the fact from context {...}. | 6.5.25
du-0527-Footnote-Substitution-Group | Footnote link {...} has a child element {...} that is not allowed. Please remove it. | 6.5.27
du-0528-Footnote-Custom-Footnote-Role | Footnote {...} has a role {... } that is not allowed. Please replace it with the default footnote role. | 6.5.28
fs-0528-Footnote-Role-Missing | Footnote {...} has missing role. | 6.5.28
du-0529-Footnote-Custom-Loc-Role | Footnote locator {...} has a custom role, {...} that is not allowed. Please replace it with the default footnote role. | 6.5.29
du-0530-Footnote-Custom-Arcrole | Footnote relationship {...} has a custom arc role {...} that is not allowed. Please replace it with the default (fact-footnote) arcrole. | 6.5.30
du-0532-Footnote-Locator-Portable | Footnote {...} refers to a location, {...}, that does not begin with "#" so that any change to the file name would render the XBRL invalid. | 6.5.32
cp-0533-Dangling-Footnote | The footnote with label {...} and text "{...}" is not connected to any fact. Please remove the footnote, or link it to a fact. | 6.5.33
cp-0534-Prohibited-Html-Footnote-Body | Footnote {...}, line {...}, contains text that is not valid for the content of the HTML "body" tag: {...}. | 6.5.34
du-0701-Schema-Include-Present | The schema contains an "include" element, in {...} line {...}. Please remove it and resubmit. | 6.7.1
cp-0702-Target-Is-Standard-Taxonomy-Namespace | The target namespace, {...} at location {...} cannot be the same as a standard taxonomy. Remove the import element or change the target namespace. | 6.7.2
fs-0703-Extension-Has-Standard-Namespace-Authority | The target namespace, {...} cannot have the same authority ({...}) as a standard taxonomy, in {...}. Please change your target namespace. | 6.7.3
cp-0704-Taxonomy-Valid-Target-Namespace | You did not adhere to the requirements for target namespace, for {...} in {...}. Please recheck your submission and adhere to the target namespace requirements. | 6.7.4
du-0707-Recommended-Prefix-Disallowed | The schema does not supply a prefix for {...} without an underscore character, in file {...}. Please provide or change a prefix | 6.7.7
cp-0708-No-Embedded-Linkbases | Your filing contained embedded linkbases in {...}. Please recheck your submission and remove all embedded linkbases. | 6.7.8
du-0709-Role-Namespace-Mismatch | Role {...} does not begin with {...}'s scheme and authority, in {...} line {...}. Please change the role URI or target namespace URI. | 6.7.9
du-0710-Role-Type-Duplicates | Role {...} was declared more than once ({...} times, in {...}). Please remove all but one declaration. | 6.7.10
du-0711-Role-Type-Declaration-Incomplete | The role {...} did not provide a usedOn element for all three link types (presentation, calculation and definition), in {...} line {...}. Change the declaration to be for all three types of link, and resubmit. | 6.7.11
rq-0712-Role-Definition-Mismatch | The definition "{...}" of role {...} does not match the expected format, in {...} line {...}. Please check that the definition matches {number} - {type} - {text}. | 6.7.12
du-0713-Arcrole-Namespace-Mismatch | Relationship role {...} does not begin with {...}'s scheme and authority, in {...} line {...}. Please change the relationship role URI or target namespace URI. | 6.7.13
du-0714-Arcrole-Type-Duplicates | Relationship arc role {...} is declared more than once ({...} duplicates, {...}). Please remove all but one of them. | 6.7.14
du-0715-Arcrole-Definition-Missing | Relationship role declaration {...} is missing a definition, in {...} line {...}. Please provide a definition. | 6.7.15
cp-0716-Element-Name-Same-As-Base | Your extension taxonomy contains an element, {...}, which has the same name as an element in the base taxonomy, {...}. Please ensure that this extension is appropriate and if so, please change the extension concept name. | 6.7.16
cp-0717-Element-Id | You did not adhere to the declarations for concepts by containing an "id" attribute whose value begins with the recommended namespace prefix of the taxonomy, followed by an underscore, followed by an element name, for the concept {...}. Please recheck your submission. | 6.7.17
du-0718-Nillable-Not-True | Element {...} is declared without a "true" value for the nillable attribute, in {...} line {...}. Please set the value to "true". | 6.7.18
cp-0719-No-Instance-Tuple-Elements | Your instance document contains one or more tuple element(s), please remove all tuple(s) from your instance document. | 6.7.19
cp-0719-No-Tuple-Element | You provided an extension concept which is a tuple, {...}. Please remove tuples and check your submission. | 6.7.19
du-0720-Typed-Domain-Ref-Disallowed | There is an xbrldt:typedDomainRef attribute on {...}, in {...} line {...}. Please remove it. | 6.7.20
du-0721-Abstract-Is-Instant | Element {...} is declared as an abstract item with period type "instant", in {...} line {...}. Please change it to "duration" or make the element not abstract. | 6.7.21
du-0722-Abstract-Type-Not-String | Element {...} is declared as an item with type {...}, in {...} line {...}. Please change it to xbrli:stringItemType or make the element not abstract. | 6.7.22
du-0723-Axis-Dimension-Name-Mismatch | The substitution group "xbrldt:dimensionItem" is only consistent with an element name that ends with "Axis". Please change {...} or change the substitutionGroup, in {...} line {...}. | 6.7.23
du-0724-Table-Hypercube-Name-Mismatch | The substitution group "xbrldt:hypercubeItem" is only allowed with an element name that ends with "Table". Please change {...} or change the substitutionGroup, in {...} line {...}. | 6.7.24
du-0725-Substitution-Group-Custom | The substitution group attribute value {...} of element {...} is not allowed, in {...} line {...}. Please change it to one of "xbrli:item", "xbrldt:dimensionItem" or "xbrldt:hypercubeItem". | 6.7.25
du-0726-LineItems-Abstract-Name-Mismatch | The element {...} ends with "LineItems" but is not abstract. Please change {...} or the value of the "abstract" attribute, in {...}, line {...}. | 6.7.26
du-0727-Domain-Type-Name-Mismatch | The type "us-types:domainItemType" is only allowed with an element name that ends with "Domain" or "Member". Please change {...} or change the type, in {...}, line {...}. | 6.7.27
du-0728-Domain-Member-Is-Instant | Element {...} is declared as a us-types:domainItemType with period type "instant", in {...} line {...}. Please change it to "duration" or change the item type. | 6.7.28
du-0903-Relationship-Ineffectual | The {...} relationship from {...} to {...}, link role {...}, in the submission is ineffectual. Please remove or correct the relationship. | 6.9.3
fs-0904-Resource-Role-Missing | The {...} element requires an xlink:role such as the default, “http://www.xbrl.org/2003/role/label”, in {...} line {...}. Please recheck submission. | 6.9.4
fs-0905-Custom-Resource-Role-Used | The {...} element has a role, {...}, that is not defined in a standard taxonomy, resource labeled {...}, in {...} line {...}. Please recheck submission. | 6.9.5
fs-0906-Custom-Arcrole-Referenced | An arcroleRef element refers to {...}, an arcrole, {...}, that is not defined in a standard taxonomy, in {...}, line {...}. Please recheck submission. | 6.9.6
cp-0907-Linkbases-Distinct | Your filing contained extended type links with roles of different namesapces and local names, {...} in the same linkbase, {...}. Please recheck your submission and ensure that all extended-type links in a single linkbase have the same namespace and local name. | 6.9.7
du-0909-Relationship-Priority-Not-Less-Than-Ten | The priority attribute {...} has a value of ten or greater, on arc {...}, in {...}, line {...}. Please change the priority to value less than 10 and resubmit. | 6.9.9
cp-1001-Element-Used-Standard-Label | You have submitted an instance using an element without an en-US standard label {...} in {...} line {...}. Please check your submission and correct the labels. | 6.10.1
cp-1003-Element-Used-Standard-English-Label | You have submitted an instance using an element {...} with {...} for role {...} in instance {...} line {...}. Labels are in {...}. Please check your submission and correct the labels. | 6.10.3
du-1004-English-Standard-Labels-Duplicated | More than one element has {...} as its English standard label ({...} in {...}, line {...} and {...} in {...}, line {...}). Please change or remove all but one label. | 6.10.4
cp-1005-Custom-Documentation-Standard-Element | Your filing attempted to add a new definition, "{...}", to an existing concept in the standard taxonomy, {...}. Please remove this definition. | 6.10.5
rq-1006-Label-Disallowed | Element {...} has more than 511 characters or contains a left-angle-bracket character in the label for role {...} , in {...} line {...}. Please correct the label. | 6.10.6
du-1008-Label-Not-Trimmed | The label {...} of element {...} has leading or trailing white space, in {...} line {...}. Please remove it. | 6.10.8
rq-1201-Presentation-Order-Missing | The presentation relationship from {...} to {...} does not have an order attribute, in {...} line {...}. Please provide a value. | 6.12.1
rq-1202-Presentation-Order-Duplicates | More than one presentation relationship in role {...} has order value {...}, in {...}, line {...} and {...} in {...}. Change all but one so they are distinct. | 6.12.2
cp-1203-Element-Used-Not-Presented | Element {...} is used in a fact or context in the instance, but is not in any presentation relationships. Element is defined in {...} on line {...}. Add the element to at least one presentation group | 6.12.3
rq-1204-English-Preferred-Label-Missing | Element {...} has no English value for role {...}, but there is a presentation relationship from {...} to {...} that requires it, in {...}, line {...}. Provide a label with xml:lang equal to "en-US". | 6.12.4
rq-1205-Preferred-Label-Duplicates | Relationships from {...} to {...} in role {...} do not have distinct values for the preferredLabel attribute, in {...}, line {...} and {...} in {...}. Change all but one value of preferredLabel. | 6.12.5
du-1401-Calculation-Relationship-Order-Missing | The calculation relationship from {...} to {...} does not have an order attribute, in {...} line {...}. | 6.14.1
fs-1402-Calculation-Relationship-Weight-Not-Unitary | Weight value {...} on the calculation relationship from {...} to {...} must be equal to 1 or to -1, in {...} line {...}. Please recheck submission. | 6.14.2
fs-1403-Calculation-Relationship-Has-Different-Period-Types | Element {...} and element {...} have different period types, but there is a calculation relationship between them in role {...}, in {...}, line {...}. Please recheck submission calculation links. | 6.14.3
fs-1404-Circular-Calculation | Element {...} is summed into itself in calculation group {...}. Please recheck submission. | 6.14.4
du-1405-Facts-In-Calculations-Presentation-Missing | Context {...} has facts of elements {...} and {...}, with a calculation relationship in {...}, but these elements are not in any common corresponding presentation relationship group. The calculation relationship is in {...} line {...}. | 6.14.5
du-1601-Definition-Relationship-Order-Missing | The {...} relationship from {...} to {...} does not have an order attribute, in {...} line {...}. | 6.16.1
du-1603-Dimension-Domain-Target-Mismatch | There is a dimension-domain relationship from {...} but its target element {...} is not a domain, in {...}, line {...}. Please change the relationship or change the type of the target element. | 6.16.3
fs-1604-Domain-Is-Tangled | Element {...} appears in overlapping sets of members in a Directed Relationship Set in role {...}; remove it as a target of one of its domain-member relationships. Please recheck submission | 6.16.4
fs-1605-Primary-Element-Has-Redundant-Tables | Element {...} is a primary element of more than one Table in relationship group {...}, to {...} in {...}, line {...}, and to {...} defined in {...}, line {...}. Please modify the "all" relationships that have the element as a source so that it has only one primary axis. | 6.16.5
fs-1606-Not-All-Relationship-Is-Closed | The notAll relationship for table {...} must have the closed attribute set to 'false' so that it can achieve its intended purpose of excluding combinations of domain values, on relationship from {...}, in {...}, line {...}. Please recheck submission. | 6.16.6
fs-1607-Axis-Excluded-Not-In-Table | Members of axis {...} are excluded, in role {...}, from primary item {...} but not included in any table. Please modify the relationships to make it consistent. | 6.16.7
fs-1608-Table-Excludes-Itself | Element {...} is a table that negates itself in {...} for primary item {...}. Modify the "all" and "notAll" relationships that have the element as a target. Please recheck submission. | 6.16.8
fs-1609-Target-Role-With-No-Consecutive-Relationships | A table is malformed because the {...} from {...} to {...} in link role {...} has no consecutive relationships, in {...}, line {...}. Remove the targetRole attribute, or provide a consecutive relationship. | 6.16.9
cp-1801-Custom-Element-Has-Reference | Your filing provides a reference, "{...}", for an custom concept in extension taxonomy, {...}. Please remove this reference. | 6.18.1
cp-1802-Standard-Element-Has-Reference | Your filing attempted to add a new reference, "{...}", to an existing concept in the standard taxonomy, {...}. Please remove this reference. | 6.18.2
cp-2200-Prohibited-Href-Or-Schema-Location | File "{...}" referenced in {...} is not supported. Please see http://www.sec.gov/info/edgar/edgartaxonomies.shtml for a listing of supported files. | 6.22.0
Prohibited-Href-Or-Schema-Location | Illegal Href or schemaLocation to {...} referenced by {...} in {...} on line {...} | 6.22.2