List of Rules

Automatable EFM Rules

#LabelID
1Filers MUST use the DEI DocumentPeriodEndDate element to tag the document's end date of report or period of filing.edgar-dei-e:DocumentPeriodEndDate
2Document Type '{$document-type}' is not valid.edgar-dei-e:DocumentTypeInvalid
3Filers MUST use the DEI DocumentType element to identify the document (form) type that is represented by this document.edgar-dei-e:DocumentTypeMissing
4Document Type '{$document-type}' is not valid for specified document submission type.edgar-dei-e:DocumentTypeNotMatchedToSubmissionType
5Filers MUST use the DEI EntityCentralIndexKey element to identify the company's CIK (central index key) code.edgar-dei-e:EntityCentralIndexKey
6Filers MUST use the DEI EntityRegistrantName element to enter the company's name.edgar-dei-e:EntityRegistrantName
7The Entity Registrant Name is not recognizededgar-dei-e:EntityRegistrantNameMismatch
8The contents of the dei:EntityCentralIndexKey fact in the Required Context must equal the content of the xbrli:identifier element in that context.edgar-dei-e:InvalidEntityCentralIndexKeyContent
9An instance covering a reporting period must contain a Required Context that is an xbrli:context having xbrli:startDate equal to 00:00:00 on the first day of the reporting period and xbrli:endDate equal to 24:00:00 on its last day.edgar-dei-e:RequiredContextMissing
10The content of an arcroleURI attribute in UTF-8 must not exceed 255 bytes in length.edgar-e:ArcroleUriTooLong
11The target of an effective arc with an xlink:arcrole attribute equal to 'http://xbrl.org/int/dim/arcrole/notAll' should be the target of an arc with an xlink:arcrole attribute equal to 'http://xbrl.org/int/dim/arcrole/all' in the same base set.edgar-e:AxisExcludedNotInTable
12The xsd:element substitutionGroup attribute must equal 'xbrldt:dimensionItem' if and only if the name attribute ends with 'Axis'.edgar-e:AxisIffDimensionItem
13Element link:calculationArc requires an order attribute.edgar-e:CalculationArcMissingOrderAttribute
14If an instance contains nonempty facts for the source and target of an effective calculation arc, then the source and target must appear in effective presentation arcs in the DTS of the instance.edgar-e:CalculationConceptMissingFromPresentation
15A calculation may not contain directed cycles (for example, a=b+c; b=d+a)edgar-e:CalculationCycles
16The content of an xsd:complexType name attribute in UTF-8 must not exceed 200 bytes in length.edgar-e:ComplexTypeNameTooLong
17An element used in a fact or xbrldi:explicitMember in an instance must have an English standard label in the DTS of that instance.edgar-e:ConceptMissingStandardEnglishLabel
18An element used in an instance must participate in at least one effective presentation arc in the DTS of that instance.edgar-e:ConceptNotInPresentation
19The nillable attribute value of an xsd:element must equal 'true'.edgar-e:ConceptNotNillable
20If the value of attribute xbrldt:targetRole on an effective definition relationship is not empty, then that relationship must have at least one effective consecutive relationship (as defined by the XBRL Dimensions specification).edgar-e:DanglingConsecutiveRelationship
21Element link:definitionArc requires an order attribute.edgar-e:DefinitionArcMissingOrderAttribute
22An xsd:element with a type attribute equal to 'xbrli:monetaryItemType' that does not have an xbrli:balance attribute must have a definition that disambiguates its sign.edgar-e:DisambiguateMonetaryItem
23The xsd:element name attribute must end with 'Domain' or 'Member' if and only if the type attribute equals or is derived from 'domainItemType' in a standard taxonomy schema target namespace.edgar-e:DomainOrMemberIffDomainItemType
24A DTS must not contain more than one link:arcroleType element with equal values of the arcroleURI attribute.edgar-e:DuplicateArcroleTypeURI
25An element used in a fact or xbrldi:explicitMember in an instance must have at most one label for any combination of the xlink:role attribute and the xml:lang attribute in the DTS of that instance.edgar-e:DuplicateConceptLabel
26The name attribute of an xsd:element must not equal any xsd:element name attribute in a standard taxonomy.edgar-e:DuplicateConceptLocalName
27An instance must not contain duplicate ('s-equal') xbrli:context elements.edgar-e:DuplicateContext
28The DTS of an instance must have no distinct elements having the same English standard label.edgar-e:DuplicateEnglishStandardLabel
29Duplicate fact (same concept, context, and units)edgar-e:DuplicateFact
30A DTS must not contain more than one link:roleType element with equal values of the roleURI attribute.edgar-e:DuplicateRoleTypeURI
31An instance must not contain duplicate ('s-equal') xbrli:unit elements.edgar-e:DuplicateUnit
32Each document file name must contain no more than one hyphen (-). Invalid Document Name: {coyotefn:document-uri($document-root)}edgar-e:EdgarFileNameDuplicateHyphen
33Each document file name must contain exactly one period (.). Invalid Document Name: {coyotefn:document-uri($document-root)}edgar-e:EdgarFileNameDuplicatePeriod
34Each document file name must contain no more than one underscore (_). Invalid Document Name: {coyotefn:document-uri($document-root)}edgar-e:EdgarFileNameDuplicateUnderscore
35Each document file name must contain only the following characters: lowercase letters (a-z), numbers (0-9), a period (.), a hyphen (-), or an underscore (_). Invalid Document Name: {coyotefn:document-uri($document-root)}edgar-e:EdgarFileNameInvalidCharacter
36Each document file name must start with a letter (a-z). Invalid Document Name: {coyotefn:document-uri($document-root)}edgar-e:EdgarFileNameNotStartAZ
37Each document file name must no longer than 32 characters in length. Invalid Document Name: {coyotefn:document-uri($document-root)}edgar-e:EdgarFileNameTooManyCharacters
38The content of an xsd:element name attribute in UTF-8 must not exceed 200 bytes in length.edgar-e:ElementNameTooLong
39Non-English Fact requires corresponding fact in Englishedgar-e:EnglishFactRequired
40The text of link:label '{$resource}' must not have leading or trailing XML whitespace.edgar-e:ExtraLabelWhitespace
41Context {$context/@id} MUST be referenced from a fact (or it MUST be removed)edgar-e:ExtraneousContext
42Every nonempty link:footnote element must be linked to at least one fact.edgar-e:ExtraneousFootnote
43A label linkbase must not have a definition for an element defined in a standard taxonomy.edgar-e:IllegalOverrideOfStandardDescription
44A link:roleType declaration with link:usedOn containing link:presentationArc, link:definitionArc or link:calculationArc must also have a link:usedOn for the other two.edgar-e:InconsistentUsedOn
45A link:linkbase in a submission must have no ineffectual arcs.edgar-e:IneffectualArc
46If the abstract attribute of xsd:element is 'true', then the type attribute must be 'xbrli:stringItemType'.edgar-e:InvalidAbstractConceptDataType
47If the abstract attribute of xsd:element is 'true', then the xbrli:periodType attribute must be 'duration'.edgar-e:InvalidAbstractConceptPeriodType
48The value of the priority attribute must be strictly less than 10.edgar-e:InvalidArcPriority
49The text preceding a sharp sign '#' in an xlink:href attribute of link:arcroleRef must be a standard taxonomy.edgar-e:InvalidArcroleRef
50The arcroleURI attribute of a link:arcroleType element must begin with the same <scheme> and <authority> parts as the targetNamespace attribute.edgar-e:InvalidArcroleTypeURI
51A company extension reference linkbase must not add, remove, or change references for any element declared in a standard taxonomy schema.edgar-e:InvalidBaseReference
52Element link:calculationArc requires a weight attribute equal to 1 or -1.edgar-e:InvalidCalculationWeight
53When EDGAR encounters characters that it does not recognize, it inserts a circumflex (^) and ususally suspends the submission.edgar-e:InvalidCircumflex
54Element declarations for concepts shall contain an 'id' attribute whose value begins with the recommended namespace prefix of the taxonomy, followed by an underscore, followed by the element name. This concept's ID should be '{coyotefn:preferred-prefix($concept/fn:root()/*/@targetNamespace)}_{$concept/@name}', not '{$concept/@id}'edgar-e:InvalidConceptID
55If the xsd:element substitutionGroup attribute is not equal to 'xbrldt:dimensionItem' or equal to 'xbrldt:hypercubeItem' then it must equal 'xbrli:item'.edgar-e:InvalidConceptSubstitutionGroup
56Invalid taxonomy file combinations: please see http://www.sec.gov/info/edgar/edgartaxonomies.shtml edgar-e:InvalidDocumentCombination
57Elements with a type attribute equal to or a restriction of 'domainItemType' in a standard taxonomy schema target namespace must not appear as facts in an instance.edgar-e:InvalidDomainItemType
58If xsd:element type attribute equals or is derived from 'domainItemType' in a standard taxonomy schema target namespace then the xbrli:periodType attribute must equal 'duration'.edgar-e:InvalidDomainItemTypePeriodType
59The xlink:arcrole attributes 'http://xbrl.org/int/dim/arcrole/domain-member' and 'http://xbrl.org/int/dim/arcrole/dimension-domain' must have no undirected cycles in any Directed Relationship Set as defined in XBRL Dimensions 1.0.edgar-e:InvalidDomainMemberCycles
60The URI content of the xlink:href attribute, the xsi:schemaLocation attribute and the schemaLocation MUST NOT contain '#element'edgar-e:InvalidElementInXPointer
61Element xsd:schema must not contain any occurrences of 'embedded' linkbases.edgar-e:InvalidEmbeddedLinkbase
62The entire 10-digit Central Index Key (CIK) code assigned by the SEC as the unique company identifier shall be used as the company identifier: the current incorrect value is '{$entity/xbrli:identifier}'edgar-e:InvalidEntityIdentifier
63The entity identifer scheme must be 'http://www.sec.gov/CIK', not '{$entity/xbrli:identifier/@scheme}'edgar-e:InvalidEntityScheme
64The URI content of the xlink:href attribute, the xsi:schemaLocation attribute and the schemaLocation attribute, after XML base resolution, must be relative and contain no forward slashes, or a recognized external location of a standard taxonomy schema file.edgar-e:InvalidFileReference
65The xlink:arcrole attribute of a link:footnoteArc element must be defined in the XBRL Specification 2.1.edgar-e:InvalidFootnoteArcXLinkArcrole
66An link:footnoteLink element must have no children other than link:loc, link:footnote, and link:footnoteArc.edgar-e:InvalidFootnoteLinkChild
67The xlink:role attribute of a link:footnote element must be defined in the XBRL Specification 2.1.edgar-e:InvalidFootnoteXLinkRole
68Each XBRL instance document MUST have a document file name formatted like: <Ticker Symbol><more letters>-CCYYMMDD.xml. Invalid Document Name: {coyotefn:document-uri($document-root)}edgar-e:InvalidInstanceFileNameFormat
69This label MUST NOT have any occurrences of '<'edgar-e:InvalidLabelContentSpecialCharacters
70This label MUST NOT have more than 510 charactersedgar-e:InvalidLabelContentTooLong
71This label MUST NOT have a) leading or trailing whitespace; b) sequential embedded whitespace (for example two spaces in a row) or c) whitespace that is not a SPACE character (such as a TAB)edgar-e:InvalidLabelContentWhitespace
72Each XBRL linkbase document MUST have a document file name formatted like: <Ticker Symbol><more letters>-CCYYMMDD_<relationship file abbreviation>.xml. Invalid Document Name: {coyotefn:document-uri($document-root)}edgar-e:InvalidLinkbaseFileNameFormat
73A link:footnoteLink link:loc xlink:href attribute must start with the sharp sign "#".edgar-e:InvalidLocatorHref
74Numeric facts must use the 'decimals' attribute not the 'precision' attribute.edgar-e:InvalidPrecisionAttribute
75Element xsd:schema must bind a Recommended Namespace Prefix for the targetNamespace attribute that does not contain the underscore character.edgar-e:InvalidPreferredPrefix
76An element that has a company specific namespace must not have a referenceedgar-e:InvalidReference
77The roleURI attribute of a link:roleType element must begin with the same <scheme> and <authority> as the targetNamespace attribute.edgar-e:InvalidRoleTypeURI
78The xbrli:scenario element must not appear in any xbrli:context.edgar-e:InvalidScenarioElement
79Each XML schema document MUST have a document file name formatted like: <Ticker Symbol><more letters>-CCYYMMDD.xsd. Invalid Document Name: {coyotefn:document-uri($document-root)}edgar-e:InvalidSchemaFileNameFormat
80If an xbrli:segment element appears in a context, then its children must be one or more xbrldi:explicitMember elements.edgar-e:InvalidSegmentChild
81A calculation linkbase of a standard taxonomy should not be included in the DTS of an instance.edgar-e:InvalidStandardCalculationLinkbase
82A definition linkbase of a standard taxonomy should not be included in the DTS of an instance.edgar-e:InvalidStandardDefinitionLinkbase
83A label linkbase of a standard taxonomy should not be included in the DTS of an instance.edgar-e:InvalidStandardLabelLinkbase
84A presentation linkbase of a standard taxonomy should not be included in the DTS of an instance.edgar-e:InvalidStandardPresentationLinkbase
85A reference linkbase of a standard taxonomy should not be included in the DTS of an instanceedgar-e:InvalidStandardReferenceLinkbase
86The xsd:schema targetNamespace attribute must not equal the targetNamespace attribute of any standard taxonomy schema.edgar-e:InvalidTargetNamespaceAuthority
87The targetNamespace attribute must match http://<authority>/<versionDate>; The <scheme> must be 'http'.edgar-e:InvalidTargetNamespaceFormat
88The targetNamespace attribute must be a valid URI with a <versionDate> in CCYYMMDD format that identifies the release date of the schema.edgar-e:InvalidTargetNamespaceVersionDate
89Invalid taxonomy file reference: please see http://www.sec.gov/info/edgar/edgartaxonomies.shtml edgar-e:InvalidTaxonomyFile
90An xsd:element must not have an xbrldt:typedDomainRef attribute.edgar-e:InvalidTypedDimension
91The xsd:element substitutionGroup attribute must not be 'xbrli:tuple'.edgar-e:InvalidUseOfTuple
92Facts of type 'text block' whose un-escaped content contains markup must satisfy the content model of the BODY tag as defined in 5.2.2edgar-e:InvalidXhtmlBodyContent
93The content of a link:footnote element must satisfy the content model of the BODY tag as defined in 5.2.2.edgar-e:InvalidXhtmlFootnoteContent
94Attribute xml:base must not appear in any Interactive Data document.edgar-e:InvalidXmlBase
95The xsd:schema must not have an xsd:include element.edgar-e:InvalidXsInclude
96If xsd:element name attribute must end with 'LineItems' then the abstract attribute must equal 'true'.edgar-e:LineItemsMustBeAbstract
97A link:arcroleType element must have a link:definition.edgar-e:LinkArcroleTypeMissingDefinition
98The link:definition MUST NOT have leading or trailing XML whitespace or newlines, or other extraneous whitespace, such as double spacesedgar-e:LinkRoleTypeDefinitionContainsExtraneousWhitespace
99The link:definition must match look like '[SortCode] - [Type] - [Title]', where Type is one of 'Statement', 'Disclosure', 'Schedule', or 'Document'edgar-e:LinkRoleTypeDefinitionRegexpFailure
100A link:roleType element must contain a link:definition child element whose content will communicate the title of the financial statement section, the level of facts in the instance that a presentation arc in the base set of that role would display, and sort alphanumerically into the order that statements and footnotes appear in the official HTML/ASCII document. Definition is missing, or doesn't match '<sort code> - <title>'edgar-e:LinkRoleTypeMissingDefinition
101The local name part of the content of xbrli:measure in UTF-8 must not exceed 200 bytes in length.edgar-e:MeasureTooLong
102The source and target of an effective calculation arc must have equal values of the xblri:periodType attribute.edgar-e:MismatchedCalculationPeriodType
103The xlink:role attribute of a link:footnote element must be defined in the XBRL Specification 2.1.edgar-e:MissingFootnoteXLinkRole
104The xlink:role attribute of an element with a type='extended' attribute or a type='resource' attribute must be present and must not be empty, and must look like a URLedgar-e:MissingXlinkRole
105All extended link elements in a single linkbase must have the same namespace and local name.edgar-e:MixedLinkbase
106XBRL document names are case sensitive.edgar-e:MultiCaseFileNames
107The DTS of an instance must contain in each base set, for each source element, at most one effective arc with an xlink:arcrole attribute equal to 'http://xbrl.org/int/dim/arcrole/all'.edgar-e:MultipleHypercubeDefinitions
108Filing MUST contain at least one calculationedgar-e:MustHaveAtLeastOneCalculation
109If an element used in an instance is assigned a label in the DTS whose xml:lang attribute does not start with 'en', then the DTS must also contain a link:label for the same element and all other attributes with an xml:lang attribute that starts with 'en'.edgar-e:NoCorrespondingEnglishLabel
110XBRL documents names shall not contain any invalid or extended ASCII characters (e.g. foreign language characters). Invalid Document: {coyotefn:document-uri($document-root)}edgar-e:NonASCIIDocumentName
111All content MUST be ASCIIedgar-e:NonAsciiContent
112The xlink:role attribute of an element with an xlink:type attribute of 'resource' must be present and must be defined in XBRL 2.1 or a standard taxonomy.edgar-e:NonStandardXlinkRole
113An effective arc with an xlink:arcrole attribute equal to 'http://xbrl.org/int/dim/arcrole/notAll' must have an xbrldt:closed attribute set to 'false'edgar-e:NotallHypercubeNotOpen
114The target of an effective arc with an xlink:arcrole attribute equal to 'http://xbrl.org/int/dim/arcrole/notAll' should be the target of an arc with an xlink:arcrole attribute equal to 'http://xbrl.org/int/dim/arcrole/all' in the same base set.edgar-e:NotallTargetMissingFromAll
115The link:presentationArc element requires an order attribute.edgar-e:PresentationArcMissingOrderAttribute
116If element used in an instance is the target in the instance DTS of more than one effective presentation arc in a base set with the same source element, then the presentation arcs must have distinct values of the preferredLabel attribute.edgar-e:PresentationRequiresPreferredLabel
117All effective presentation arcs in the same base set with the same source element must have distinct values of the order attribute.edgar-e:PresentationRequiresUniqueOrder
118The content of a roleURI attribute in UTF-8 must not exceed 255 bytes in length.edgar-e:RoleUriTooLong
119The content of an xsd:simpleType name attribute in UTF-8 must not exceed 200 bytes in length.edgar-e:SimpleTypeNameTooLong
120The target of an effective arc with an xlink:arcrole attribute equal to 'http://xbrl.org/int/dim/arcrole/notAll' must not be the target of an effective arc with an xlink:arcrole attribute equal to 'http://xbrl.org/int/dim/arcrole/all' in the same base set.edgar-e:TableExcludesItself
121The xsd:element name attribute must end with 'Table' if and only if substitutionGroup attribute equals 'xbrldt:hypercubeItem'.edgar-e:TableIffHypercubeItem
122The target of an effective arc with an xlink:arcrole attribute equal to 'http://xbrl.org/int/dim/arcrole/dimension-domain' or 'http://xbrl.org/int/arcrole/dimension-default' must be a Domain or Member.edgar-e:TargetMustBeDomainOrMember
123The calendar date of <versionDate> in the targetNamespace should never be later than the calendar date in the document name of the submission.edgar-e:TargetNamespaceDateTooLate
124The content of a targetnamespace attribute in UTF-8 must not exceed 255 bytes in length.edgar-e:TargetNamespaceTooLong
125If the un-escaped content of a fact with base type us-types:textBlockItemType or a type derived by restriction of the type 'escapedItemType' in a standard taxonomy schema namespace contains the "<" character followed by a QName and whitespace, "/>" or ">", then the un-escaped content must contain only a sequence of text and XML nodes.edgar-e:TextBlockInvalidXml
126All xbrli:identifier elements in an instance must have identical content.edgar-e:TooManyIdentifiers
127If "UTR" in a standard namespace is declared in the DTS of an instance, then the value of each unitRef. attribute on each fact of a type in that registry must refer to a unit declaration consistent with the data type of that fact, where consistency is defined by that registry.edgar-e:UnitRegistryViolation
128XBRL Instance document {coyotefn:document-uri($document-root)} MUST have a .xml file extensionedgar-e:WrongExtensionInstance
129XBRL Linkbase document {coyotefn:document-uri($document-root)} MUST have a .xml file extensionedgar-e:WrongExtensionLinkbase
130XML Schema document {coyotefn:document-uri($document-root)} MUST have a .xsd file extensionedgar-e:WrongExtensionSchema