cp-0501-File-Character |
Disallowed character '{text}' in file {file} at line {line} col {column} |
5.2.1.1 |
cp-0501-File-Name |
Document file name {filename} must start with a-z or 0-9, contain lower case letters,
., -, _, and end with {suffix}.
|
5.1.1 |
cp-0501-File-Name-Length |
Document file name {filename} must not exceed 32 characters. |
5.1.1 |
cp-0502-File-Entity-Code |
Disallowed entity code {text} in file {file} line {line} column {column} |
5.2.2.6 |
ix-0502-Standard-Namespace-Prefix |
The prefix {submittedPrefix} must be replaced by {recommendedPrefix} for standard
namespace {namespace}
|
5.2.5 |
ix-0514-Hidden-Fact-Not-Found |
The value of the -sec-ix-hidden style property, {id}, does not correspond to the id
of any hidden fact.
|
5.2.5.14 |
cp-0302-Sdr-Has-Non-Sdr-Exhibit |
An SDR filing contains non-SDR exhibit type {exhibitType} document type {documentType}. |
6.3.2 |
cp-0302-Sdr-Missing-Files |
{docType} report missing files: {missingFiles}. |
6.3.2 |
cp-0302-Sdr-Missing-Standard-Schema |
{documentType} submission must use a US GAAP standard schema. |
6.3.2 |
cp-0303-Valid-File-Extension |
The document type and naming of "{filename}" 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.REF - XBRL Taxonomy Extension
Reference Linkbase document *.xml 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 Please ensure that
you comply with the document type and naming provided.
|
6.3.3 |
cp-0303-Valid-File-Extension |
Invalid linkbase file name: {filename}, has no extended link element, cannot determine
link type.
|
6.3.3 |
cp-0306-Href-Xpointers |
Href {elementHref} may only have shorthand xpointers |
6.3.6 |
cp-0308-More-Than-One-Ins |
The submission contains more than one instance for exhibit type {exhibitType}. Remove
all but one or change the exhibit types.
|
6.3.8 |
cp-0308-Sdr-Has-Multiple-K-Reports |
SDR filing has multiple K SDR reports for {entities}. |
6.3.8 |
cp-0310-Missing-Schema |
The submission is missing required schema attachment {documentType}. |
6.3.10 |
du-0311-Xml-Base-Used |
The attribute xml:base appears in on element {element} in {refSource}. Please remove
the attribute.
|
6.3.11 |
fs-0403-Fact-Xbrl-Error |
Fact {fact} of context {contextID} has an XBRL error |
6.4.3 |
cp-0501-Entity-Identifier-Scheme |
Your identifier for the CIK code, {identifier}, or scheme {scheme}, in context {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 {count} was(were) found: {context}. |
6.5.4 |
cp-0505-Segment-Child-Not-Explicit-Member |
There must be no segments with non-explicitDimension content, but {count} was(were)
found: {content}.
|
6.5.5 |
du-0507-Duplicate-Contexts |
The instance document contained more than one context equivalent to {context} ({context2}).
Please remove duplicate contexts from the instance.
|
6.5.7 |
du-0508-Unused-Context |
The instance document contained a context {contextIDs} 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 {endContexts} endDate and {startContexts} startDate have a duration of one
day; that is inconsistent with document type {documentType}.
|
6.5.9 |
fs-0510-Start-And-Instant-Dates-Not-Distinct-Inconsistent-With-Document-Type |
Contexts {contexts} have an overlap of one day; that is inconsistent with document
type {documentType}.
|
6.5.10 |
du-0511-Duplicate-Units |
There is more than one unit equivalent to {unitID} ({unitID2}). Please remove all
but one and resubmit.
|
6.5.11 |
du-0512-Duplicate-Facts |
The instance document contained an element, {fact} that was used more than once in
contexts equivalent to {contextID}. Please ensure there are no duplicate combinations
of concept and context in the instance.
|
6.5.12 |
du-0514-English-Text-Missing |
Element {fact} in context {contextID} 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} fact contains unbalanced tags, in {refSource}. (For example, <BR> must be
followed by </BR>; values of attributes such as "align" must be quoted, as in align="center".)
XML parser messages: {error}.
|
6.5.15 |
cp-0515-Text-Block-Not-Well-Formed-XML |
A {fact} fact contains unbalanced tags, in {refSource}. (For example, <BR> must be
followed by </BR>; values of attributes such as "align" must be quoted, as in align="center".)
XML parser messages: {error}.
|
6.5.15 |
cp-0515-Text-Block-Not-Well-Formed-XML |
A {fact} fact contains unbalanced tags, in {refSource}. (For example, <BR> must be
followed by </BR>; values of attributes such as "align" must be quoted, as in align="center".)
XML parser messages: {error}.
|
6.5.15 |
cp-0516-Prohibited-Html-Body |
A {fact} fact, in {refSource}, contains text that is not valid for the content of
the HTML "body" tag: {error}.
|
6.5.16 |
cp-0516-Prohibited-Html-Body |
A {fact} fact, in {refSource}, contains text that is not valid for the content of
the HTML 'body' tag: {error}.
|
6.5.16 |
cp-0516-Prohibited-Html-Body |
A {fact} fact, in {refSource}, contains text that is not valid for the content of
the HTML 'body' tag: javascript in '{attribute}' for <{element}>.
|
6.5.16 |
cp-0516-Prohibited-Html-Body |
A {fact} fact, in {refSource}, contains text that is not valid for the content of
the HTML 'body' tag: external reference in '{attribute}' for <{element}>.
|
6.5.16 |
cp-0516-Prohibited-Html-Body |
A {fact} fact, in {refSource}, contains text that is not valid for the content of
the HTML 'body' tag: reference to a graphics file which doesn't have expected content
'{attribute}' for <{element}>.
|
6.5.16 |
cp-0516-Prohibited-Html-Body |
A {fact} fact, in {refSource}, contains text that is not valid for the content of
the HTML 'body' tag: reference to a graphics file which isn't openable '{attribute}'
for <{element}>, error: {error}.
|
6.5.16 |
cp-0516-Prohibited-Html-Body |
A {fact} fact, in {refSource}, contains text that is not valid for the content of
the HTML 'body' tag: reference to a graphics file which isn't .gif or .jpg '{attribute}'
for <{element}>
|
6.5.16 |
cp-0516-Prohibited-Html-Body |
A {fact} fact, in {refSource}, contains text that is not valid for the content of
the HTML 'body' tag: nested <table> elements.
|
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-0519-Required-Context |
Required context (no segment) not found for document type {documentType}. |
6.5.19 |
dq-0520-DocumentType-Missing |
Submission type {subType} must have a non-empty value for DocumentType in {context} |
6.5.20 |
dq-0520-DocumentType-Value |
In submission type {subType}, DocumentType value must have {value} in the {context}. |
6.5.20 |
dq-0521-EntityCentralIndexKey-Missing |
Submission type {subType} must have a non-empty value for EntityCentralIndexKey in
{context}
|
6.5.21 |
dq-0521-EntityRegistrantName-Missing |
Submission type {subType} must have a non-empty value for EntityRegistrantName in
{context}
|
6.5.21 |
cp-0523-Non-Matching-Cik |
The submission CIK, {filerIdentifier} does not match either the EntityCentralIndexKey,
{entityIdentifer}, or context identifier CIK(s) {entityIdentifer}, {entityIdentifer2},
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.3 |
cp-0523-Non-Matching-Cik |
The EntityCentralIndexKey, {value}, does not match the context identifier CIK {entityIdentifier}.
Please include a correct matching EntityCentralIndexKey and context identifier CIK(s)
in the filing.
|
6.5.23 |
cp-0523-Non-Matching-Cik |
The submission CIK, {filerIdentifier} does not match the EntityCentralIndexKey. Please
include a correct matching EntityCentralIndexKey in the filing.
|
6.5.23 |
cp-0523-Non-Matching-Cik |
The context identifier CIK {entityIdentifier} is not 10 digits, for required context(s).
Please include a correct context identifier CIK in the filing.
|
6.5.23 |
cp-0524-Multiple-L-Sdr-Reports-For-Entity |
There is more than one L SDR Exhibit having EntityRegistrantName {entity}. Change
one of the names or remove one of the L SDR exhibits.
|
6.5.24 |
cp-0524-Registrant-Name-Mismatch |
The Official Registrant name, {prefix}, does not match the value {value} in the Required
Context. Please correct dei:EntityRegistrantName.
|
6.5.24 |
du-0525-Domain-As-Fact |
The domain item {fact} cannot appear as a fact, in {refSource}. Please remove the
fact from context {contextID}.
|
6.5.25 |
im-0526-Entity-Common-Shares-Outstanding |
An instance with dei:DocumentType of {documentType} must have one dei:EntityCommonStockSharesOutstanding
fact for each class of stock or units outstanding.
|
6.5.26 |
du-0527-Footnote-Substitution-Group |
Footnote link {footnoteLinkNumber} has a child element {elementName} that is not allowed.
Please remove it.
|
6.5.27 |
du-0528-Footnote-Custom-Footnote-Role |
Footnote {xlinkLabel} has a role {role} that is not allowed. Please replace it with
the default footnote role.
|
6.5.28 |
du-0528-Footnote-Role-Missing |
Footnote {xlinkLabel} is missing a role. Please provide the default footnote role. |
6.5.28 |
du-0529-Footnote-Custom-Loc-Role |
Footnote locator {xlinkLabel} has a custom role, {role} that is not allowed. Please
replace it with the default footnote role.
|
6.5.29 |
du-0530-Footnote-Custom-Arcrole |
Footnote relationship {arcToLabel} has a custom arc role {arcrole} that is not allowed.
Please replace it with the default (fact-footnote) arcrole.
|
6.5.30 |
du-0532-Footnote-Locator-Portable |
Footnote {locLabel} refers to a location, {locHref}, 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 {footnoteLabel} and text '{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 {xlinkLabel}, line {refLine}, contains text that is not valid for the content
of the HTML "body" tag: {error}.
|
6.5.34 |
cp-0534-Prohibited-Html-Footnote-Body |
Footnote {xlinkLabel}, line {refLine}, contains text that is not valid for the content
of the HTML "body" tag: javascript in '{attribute}' for <{element}>.
|
6.5.34 |
cp-0534-Prohibited-Html-Footnote-Body |
Footnote {xlinkLabel}, line {refLine}, contains text that is not valid for the content
of the HTML "body" tag: XML error {error}
|
6.5.34 |
cp-0534-Prohibited-Html-Footnote-Body |
Footnote {xlinkLabel}, line {refLine}, contains text that is not valid for the content
of the HTML "body" tag: invalid external reference in '{attribute}' for <{element}>:
{value}
|
6.5.34 |
cp-0534-Prohibited-Html-Footnote-Body |
Footnote {xlinkLabel}, line {refLine}, contains text that is not valid for the content
of the HTML "body" tag: reference to a graphics file which doesn't have expected content
'{attribute}' for <{element}>
|
6.5.34 |
cp-0534-Prohibited-Html-Footnote-Body |
Footnote {xlinkLabel}, line {refLine}, contains text that is not valid for the content
of the HTML "body" tag: reference to a graphics file which isn't openable '{attribute}'
for <{element}>, error: {error}
|
6.5.34 |
cp-0534-Prohibited-Html-Footnote-Body |
Footnote {xlinkLabel}, line {refLine}, contains text that is not valid for the content
of the HTML "body" tag: reference to a graphics file which isn't .gif or .jpg '{attribute}'
for <{element}>
|
6.5.34 |
cp-0534-Prohibited-Html-Footnote-Body |
Footnote {xlinkLabel}, line {refLine}, contains text that is not valid for the content
of the HTML "body" tag: nested <table> elements.
|
6.5.34 |
du-0536-Name-Length-Limit |
Unit {unitID} contains a measure element whose local-name in UTF-8 has more than 200
bytes. Shorten the measure name.
|
6.5.36 |
du-0537-Nonzero-Digits-Truncated |
Fact {fact} of context {contextID} decimals {decimals} value {value} has insignificant
digits {insignificantDigits}. Please correct the fact value and resubmit.
|
6.5.37 |
du-0538-Context-Has-Period-Forever |
Context {contextID}s uses period <xbrli:forever>. Please remove it and resubmit. |
6.5.38 |
cp-0539-Typed-Dimension-Not-Standard |
Typed dimensions must be defined in standard taxonomy schemas, contexts: {contextIDs}
dimensions: {dimensions}.
|
6.5.39 |
dq-0540-EntityExTransitionPeriod-EntityEmergingGrowthCompany-Dependency |
In submission type {subType}, EntityExTransitionPeriod must have a value if EntityEmergingGrowthCompany
has value "true" in context {contextID}, else it should not be provided.
|
6.5.40 |
cp-0540-SRT-Concepts-For-IFRS-Concepts |
Taxonomy axis concepts from the SRT taxonomy should be used for the following IFRS
axis concepts: {ifrsSrtConceptsUsed}.
|
6.5.40 |
cp-0540-SRT-Members-For-SRT-Axes |
Taxonomy axes from the SRT taxonomy should use SRT or extension members for the following
IFRS member concepts: {ifrsSrtConceptsUsed}.
|
6.5.40 |
du-0701-Schema-Include-Present |
The schema contains an 'include' element, in {refSource}. Please remove it and resubmit. |
6.7.1 |
fs-0703-Extension-Has-Standard-Namespace-Authority |
The target namespace, {targetNamespace} cannot have the same authority ({targetNamespaceAuthority})
as a standard taxonomy, in {schema}. 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 {targetNamespace}
in {schema}. Please recheck your submission and adhere to the target namespace requirements.
|
6.7.4 |
du-0705-Namespace-Authority |
Taxonomy schema {schema} namespace {targetNamespace} must be a valid URI with a valid
authority for the namespace.
|
6.7.5 |
du-0707-Recommended-Prefix-Disallowed |
The schema does not supply a prefix for {targetNamespace} without an underscore character,
in file {schema}. Please provide or change a prefix
|
6.7.7 |
cp-0708-No-Embedded-Linkbases |
Your filing contained embedded linkbases in {schema}. Please recheck your submission
and remove all embedded linkbases.
|
6.7.8 |
du-0709-Role-Namespace-Mismatch |
Role {roleType} does not begin with {targetNamespace}'s scheme and authority, in {refSource}.
Please change the role URI or target namespace URI.
|
6.7.9 |
du-0710-Role-Type-Duplicates |
Role {roleType} was declared more than once ({numberOfDeclarations} times, in {refSources}).
Please remove all but one declaration.
|
6.7.10 |
du-0711-Role-Type-Declaration-Incomplete |
The role {roleType} did not provide a usedOn element for all three link types (presentation,
calculation and definition), in {refSource}. Change the declaration to be for all
three types of link, and resubmit.
|
6.7.11 |
rq-0712-Role-Definition-Mismatch |
The definition "{definition}" of role {roleType} does not match the expected format,
in {refSource}. Please check that the definition matches {number} - {type} - {text}.
|
6.7.12 |
du-0713-Arcrole-Namespace-Mismatch |
Relationship role {arcroleType} does not begin with {targetNamespace}'s scheme and
authority, in {refSource}. Please change the relationship role URI or target namespace
URI.
|
6.7.13 |
du-0714-Arcrole-Type-Duplicates |
Relationship arc role {arcroleType} is declared more than once ({numberOfDeclarations}
duplicates, {refSources}). Please remove all but one of them.
|
6.7.14 |
du-0715-Arcrole-Definition-Missing |
Relationship role declaration {arcroleType} is missing a definition, in {refSource}.
Please provide a definition.
|
6.7.15 |
cp-0716-Element-Name-Same-As-Base |
Your extension taxonomy contains an element, {concept}, which has the same name as
an element in the base taxonomy, {standardConcept}. 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 {concept}. Please recheck
your submission.
|
6.7.17 |
du-0718-Nillable-Not-True |
Element {concept} is declared without a "true" value for the nillable attribute, in
{refSource}. Please set the value to "true".
|
6.7.18 |
cp-0719-No-Tuple-Element |
You provided an extension concept which is a tuple, {concept}. Please remove tuples
and check your submission.
|
6.7.19 |
du-0720-Typed-Domain-Ref-Disallowed |
There is an xbrldt:typedDomainRef attribute on {concept}, in {refSource}. Please remove
it.
|
6.7.20 |
du-0721-Abstract-Is-Instant |
Element {concept} is declared as an abstract item with period type "instant", in {refSource}.
Please change it to "duration" or make the element not abstract.
|
6.7.21 |
du-0723-Axis-Dimension-Name-Mismatch |
The substitution group "xbrldt:dimensionItem" is only consistent with an element name
that ends with "Axis". Please change $local-name({concept}) or change the substitutionGroup,
in {refSource}.
|
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 $local-name({concept}) or change the substitutionGroup,
in {refSource}.
|
6.7.24 |
du-0725-Substitution-Group-Custom |
The substitution group attribute value {substitutionGroup} of element $local-name({concept})
is not allowed, in {refSource}. Please change it to one of "xbrli:item", "xbrldt:dimensionItem"
or "xbrldt:hypercubeItem".
|
6.7.25 |
du-0726-LineItems-Abstract-Name-Mismatch |
The element $local-name({concept}) ends with "LineItems" but is not abstract. Please
change $local-name({concept}) or the value of the "abstract" attribute, in {refSource}.
|
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 $local-name({concept}) or change the type,
in {refSource}.
|
6.7.27 |
du-0728-Domain-Member-Is-Instant |
Element $local-name({concept}) is declared as a us-types:domainItemType with period
type "instant", in {refSource}. Please change it to "duration" or change the item
type.
|
6.7.28 |
du-0729-Name-Length-Limit |
Shorten this declaration name to 200 bytes or fewer in UTF-8: {name} |
6.7.29 |
du-0730-Uri-Length-Limit |
Shorten this declaration URI to 255 bytes or fewer in UTF-8: {value}. |
6.7.30 |
du-0731-Fraction-Item-Type |
Element {concept} is declared as a fraction item type. Change or remove the declaration
and resubmit.
|
6.7.31 |
rq-0732-Nonnnumeric-Must-Be-Duration |
Declaration of element {concept} in {schema} must have xbrli:periodType of 'duration'
because its base type is not numeric.
|
6.7.32 |
du-0903-Relationship-Ineffectual |
The {arcrole} relationship from {conceptFrom} to {conceptTo}, link role {linkroleDefinition},
in the submission is ineffectual. Please remove or correct the relationship.
|
6.9.3 |
fs-0904-Resource-Role-Missing |
The {element} element requires an xlink:role such as the default, "http://www.xbrl.org/2003/role/label",
in {refSource}. Please recheck submission.
|
6.9.4 |
fs-0905-Custom-Resource-Role-Used |
The {element} element has a role, {roleDefinition}, that is not defined in a standard
taxonomy, resource labeled {xlinkLabel}, in {refSource}. Please recheck submission.
|
6.9.5 |
fs-0906-Custom-Arcrole-Referenced |
An arcroleRef element refers to {xlinkHref}, an arcrole, {refURI}, that is not defined
in a standard taxonomy, in {refSource}. Please recheck submission.
|
6.9.6 |
cp-0907-Linkbases-Distinct |
Your filing contained extended type links with roles of different namesapces and local
names, {element} and {element2} in the same linkbase, {refUrl}. 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 {priority} has a value of ten or greater, on arc {arcElement},
in {refSource}. 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 {concept}
in {refSources2_n}. Please check your submission and correct the labels.
|
6.10.1 |
cp-1002-Element-Used-Has-Duplicate-Label |
Concept {concept} has duplicated labels for role {role} lang {lang}. |
6.10.2 |
cp-1003-Element-Used-Standard-English-Label |
You have submitted an instance using an element {concept} with {lang} for role {role}
in instance {refSource}. Labels are in {refSources2_n}. Please check your submission
and correct the labels.
|
6.10.3 |
du-1004-English-Standard-Labels-Duplicated |
More than one element has {text} as its English standard label ({concept} in {refSource}
and {concept2} in {refSource3}). 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, "{text}", to an existing concept in
the standard taxonomy, {concept}. Please remove this definition.
|
6.10.5 |
rq-1006-Label-Disallowed |
Element {concept} has more than 511 characters or contains a left-angle-bracket character
in the label for role {role}, in {refSource}. Please correct the label.
|
6.10.6 |
du-1008-Label-Not-Trimmed |
The label {text} of element {concept} has leading or trailing white space, in {refSource}.
Please remove it.
|
6.10.8 |
du-1009-Numeric-Label-Role |
Non-numeric element {concept} has a label role for numeric elements: {role}. Please
change the role attribute.
|
6.10.9 |
rq-1201-Presentation-Order-Missing |
The presentation relationship from {conceptFrom} to {conceptTo} does not have an order
attribute, in {refSource}. Please provide a value.
|
6.12.1 |
rq-1202-Presentation-Order-Duplicates |
More than one presentation relationship in role {linkroleDefinition} has order value
{order}, in {refSources}. Change all but one so they are distinct.
|
6.12.2 |
cp-1203-Element-Used-Not-Presented |
Element {concept} is used in a fact or context in the instance, but is not in any
presentation relationships. Element is defined in {refSources2_n}. Add the element
to at least one presentation group.
|
6.12.3 |
rq-1204-English-Preferred-Label-Missing |
Element {concept} has no English value for role {preferredLabel}, but there is a presentation
relationship from {fromConcept} to {concept} that requires it, in {refSource}. Provide
a label with xml:lang equal to "en-US".
|
6.12.4 |
rq-1205-Preferred-Label-Duplicates |
Relationships from {fromConcept} to {concept} in role {linkroleDefinition} do not
have distinct values for the preferredLabel attribute, in {refSources}. Change all
but one value of preferredLabel.
|
6.12.5 |
du-1401-Calculation-Relationship-Order-Missing |
The calculation relationship from {conceptFrom} to {conceptTo} does not have an order
attribute, in {refSource}.
|
6.14.1 |
fs-1402-Calculation-Relationship-Weight-Not-Unitary |
Weight value {weight} on the calculation relationship from {conceptFrom} to {conceptTo}
must be equal to 1 or to -1, in {refSource}. Please recheck submission.
|
6.14.2 |
fs-1403-Calculation-Relationship-Has-Different-Period-Types |
Element {conceptFrom} and element {conceptTo} have different period types, but there
is a calculation relationship between them in role {linkroleDefinition}, in {refSource}.
Please recheck submission calculation links.
|
6.14.3 |
fs-1404-Circular-Calculation |
Element {concept} is summed into itself in calculation group {linkroleDefinition}.
Please recheck submission.
|
6.14.4 |
du-1405-Facts-In-Calculations-Presentation-Missing |
Context {contextId} has facts of elements {conceptFrom} and {conceptTo}, with a calculation
relationship in {linkroleDefinition}, but these elements are not in any common corresponding
presentation relationship group. The calculation relationship is in {refSource}.
|
6.14.5 |
du-1601-Definition-Relationship-Order-Missing |
The Definition relationship from {conceptFrom} to {conceptTo} does not have an order
attribute, in {refSource}.
|
6.16.1 |
du-1603-Dimension-Domain-Target-Mismatch |
There is a dimension-domain relationship from {conceptFrom} but its target element
{conceptTo} is not a domain, in {refSource}. Please change the relationship or change
the type of the target element.
|
6.16.3 |
fs-1604-Domain-Is-Tangled |
Element {conceptFrom} appears in overlapping sets of members in a Directed Relationship
Set in role {linkroleDefinition}; 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 {concept} is a primary element of more than one Table in relationship group
{linkroleDefinition}, to tables {hypercubes} in {refSources2_n}. 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 {hypercube} 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 {primaryItem}, in {refSource}. Please recheck submission.
|
6.16.6 |
fs-1607-Axis-Excluded-Not-In-Table |
Members of axis {dimension} are excluded, in role {linkroleDefinition}, from primary
item {primaryItem} but not included in any table. Please modify the relationships
to make it consistent.
|
6.16.7 |
fs-1608-Table-Excludes-Itself |
Element {hypercube} is a table that negates itself in {linkroleDefinition} for primary
item {primaryItem}. 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 {arcroleURI} from {fromConcept} to {toConcept} in
link role {linkroleDefinition} has no consecutive relationships, in {refSource}. Remove
the targetRole attribute, or provide a consecutive relationship.
|
6.16.9 |
cp-1801-Custom-Element-Has-Reference |
Your filing provides a reference, "{xml}", for a custom concept in extension taxonomy,
{concept}. Please remove this reference.
|
6.18.1 |
cp-1802-Standard-Element-Has-Reference |
Your filing attempted to add a new reference, "{xml}", to an existing concept in the
standard taxonomy, {concept}. Please remove this reference.
|
6.18.2 |
cp-2200-Prohibited-Href-Or-Schema-Location |
File "{url}" referenced in {refUrl} is not supported. Please see http://www.sec.gov/info/edgar/edgartaxonomies.shtml
for a listing of supported files.
|
6.22.0 |
cp-2203-Incompatible-Inline-DocumentType |
DocumentType {documentType} is incompatible with inline XBRL. |
6.22.3 |
cp-2203-Incompatible-Schemas |
References for conflicting standard taxonomies {conflictClass} are not allowed in
same DTS {namespaceConflicts}
|
6.22.3 |
cp-2203-Incompatible-Taxonomy-DocumentType |
DocumentType {documentType} is incompatible with the {conflictClass} taxonomy. |
6.22.3 |
rq-2604-Embedding-Command-Invalid-Member |
In ''{linkroleName}'', the embedded report created by the fact {fact} with the context
{contextID}, the domain members {members} are not presentation descendants of {axis}.
|
6.26.4 |
rq-2604-Embedding-Command-Malformed-Axis |
In ''{linkroleName}'', the embedded report created by the fact {fact} with the context
{contextID}, the token {token}, at position {position} in the list of tokens, is malformed.
This token can only be 'period', 'unit', 'primary' or identify an Axis by its namespace
prefix, underscore, and element name.
|
6.26.4 |
rq-2604-Embedding-Command-Malformed-Direction-Token |
In ''{linkroleName}'', the embedded report created by the fact {fact} with the context
{contextID}, the token {token}, at position {position} in the list of tokens, is malformed.
Each iterator can only start with 'row' or 'column'.
|
6.26.4 |
rq-2604-Embedding-Command-Malformed-Member |
In ''{linkroleName}'', the embedded report created by the fact {fact} with the context
{contextID}, the keyword(s) {tokenlist} is not '*', a valid member qname or list of
valid member qnames.
|
6.26.4 |
rq-2604-Embedding-Command-Malformed-Style-Token |
In ''{linkroleName}'', the embedded report created by the fact {fact}, with the context
{contextID}, the style keyword {style} is not one of 'compact' or 'nodisplay'.
|
6.26.4 |
rq-2605-Embedding-Command-Missing-Iterator |
In ''{linkroleName}'', the embedded report created by the fact {fact} with the context
{contextID}, there are no valid {roworcol} commands{iftransposed}. Change one of the
{axes} to a {colorrow} or add a {roworcol} command with an additional axis.
|
6.26.5 |
rq-2605-Embedding-Command-Missing-Iterator-After-Transposition |
In ''{linkroleName}'', the embedded report created by the fact {fact} with the context
{contextID}, there are no valid {roworcol} commands{iftransposed}. Change one of the
{axes} to a {colorrow} or add a {roworcol} command with an additional axis.
|
6.26.5 |
rq-2608-Too-Many-Annual-Return-Facts |
In ''{linkroleName}'', the embedded report created by the fact {fact} with context
{contextID}, there are {numYears} Annual Return Facts, but there must not be more
than 20.
|
6.26.8 |