Abstract

The architecture rules, starting with number 2, discuss how the XBRL syntax can be used within the Dutch Taxonomy. Because this concerns hundreds of rules, a technical classification has been made. For each rule the requirement is stated in either Dutch or English. In addition, in any case a clarification in Dutch is given for why the rules have been laid down.

Each rule has the following structure:

Status of this document

As well as sections marked as non-normative, all authoring guidelines, diagrams, examples, and notes in this specification are non-normative. Everything else in this specification is normative.

this document is also available in Dutch

Algemeen

2.01.00.01

Rule 2.01.00.01
Name Taxonomies that are part of the Dutch Taxonomy, or of a PE MUST comply with all rules in this document
Explanation
Introduction date 2010/06/23
Error message
NTA Rule True
PE Rule True
Testable
Section Algemeen

als json

2.01.00.02

Rule 2.01.00.02
Name EACH file in the Dutch Taxonomy or PE MUST be XBRL 2.1 valid
Explanation
Introduction date 2010/06/23
Error message
NTA Rule True
PE Rule True
Testable
Section Algemeen

als json

2.01.00.03

Rule 2.01.00.03
Name Each Dutch Taxonomy entry point schema MUST publish the permitted period of reporting with SBR-Dutch Taxonomy-Management
Explanation
Introduction date 2010/06/23
Error message
NTA Rule True
PE Rule
References SBR-Australië: 46 DI
Testable
Section Algemeen

als json

2.01.00.04

Rule 2.01.00.04
Name Recipients of Dutch Taxonomy entry point schemas MUST indicate if they are capable of processing reports based on that entry point schema
Explanation
Introduction date 2010/06/23
Related to 2.01.00.03
Error message
NTA Rule True
PE Rule
Testable
Section Algemeen

als json

2.01.00.05

Rule 2.01.00.05
Name Re-use of parts of the Dutch Taxonomy are only allowed conform the rules in this wiki concerning reuse of data
Explanation
Introduction date 2010/06/23
Related to GEN-base_en_hergebruik#Overig_hergebruik_in_domeinextensies
Error message
NTA Rule True
PE Rule
Testable
Section Algemeen

als json

2.01.00.06

Rule 2.01.00.06
Name The Dutch Taxonomy MUST NOT refer to external DTSs which are not authorised by SBR-Dutch Taxonomy management
Explanation
Introduction date 2010/06/23
Error message
NTA Rule True
PE Rule True
Testable True
Section Algemeen

als json

2.01.00.07

Rule 2.01.00.07
Name Concepts from NL-GEN or NL-CD taxonomies MUST be used if these are semantically (1. reference, 2. element/@name, 3. standard label, 4. hierarchy) equivalent
Explanation
Introduction date 2010/06/23
Error message
NTA Rule True
PE Rule
Testable
Section Algemeen

als json

2.01.00.08

Rule 2.01.00.08
Name NT domains MUST NOT define resources on NL-GEN or NL-CD concepts with an @xlink:role content http://www.xbrl.org/2003/role/reference, http://www.xbrl.org/2003/role/documentation
Explanation
Introduction date 2010/06/23
Error message
NTA Rule True
PE Rule
References GFM2.0: 1.5.5GFM2.0: 1.9.1
Testable
Section Algemeen

als json

2.01.00.09

Rule 2.01.00.09
Name BOM characters MUST NOT be used in files that form the Dutch Taxonomy
Explanation
Introduction date 2013/05/15
Agreed date 2013/01/16
Error message
NTA Rule True
PE Rule True
References en.wikipedia.org/wiki/Byte_order_mark
Testable True
Section Algemeen

als json

2.01.00.10

Rule 2.01.00.10
Name A taxonomy document in the NT MUST be part of a DTS
Explanation
Introduction date 2015/12/02
Agreed date 2015/12/02
Error message
NTA Rule True
PE Rule
Testable
Section Algemeen

als json

2.01.00.11

Rule 2.01.00.11
Name The maximum length of file names is 140 characters.
Explanation
Introduction date 2017/05/15
Error message
NTA Rule True
PE Rule
Testable True
Section Algemeen

als json

2.01.00.12

Rule 2.01.00.12
Name
Explanation
Related to 2.01.00.06
Error message
NTA Rule
PE Rule True
Testable
Section Algemeen

als json

2.01.00.13

Rule 2.01.00.13
Name
Explanation
Error message
NTA Rule
PE Rule True
Testable
Section Algemeen

als json

2.01.00.14

Rule 2.01.00.14
Name
Explanation
Error message
NTA Rule
PE Rule True
Testable
Section Algemeen

als json

2.01.00.15

Rule 2.01.00.15
Name
Explanation
Error message
NTA Rule
PE Rule True
Testable
Section Algemeen

als json

2.01.00.16

Rule 2.01.00.16
Name
Explanation
Error message
NTA Rule
PE Rule True
Testable
Section Algemeen

als json

XML Schema - Basis

2.02.00.01

Rule 2.02.00.01
Name A schema MUST be based on XML Schema Specification 1.0 of the W3C
Explanation
Introduction date 2010/06/23
Error message
NTA Rule True
PE Rule True
Testable
Section XML Schema - Basis

als json

2.02.00.02

Rule 2.02.00.02
Name A schema MUST contain only content based on XML Specification 1.0 of the W3C
Explanation
Introduction date 2010/06/23
Error message
NTA Rule True
PE Rule True
References SBR-AU: 21 SA
Testable True
Section XML Schema - Basis

als json

2.02.00.03

Rule 2.02.00.03
Name A schema MUST support UTF-8 character set for the content
Explanation
Introduction date 2010/06/23
Related to 2.03.00.03
Error message
NTA Rule True
PE Rule True
References SBR Australië: 22 SAGFM2.0: 1.1.8
Testable True
Section XML Schema - Basis

als json

2.02.00.04

Rule 2.02.00.04
Name A schema MUST contain an XML comment section stating the IP rights, release date and version. These MUST be placed on line two (and following)
Explanation
Introduction date 2010/06/23
Error message
NTA Rule True
PE Rule
References SBR-AU: 7 SA
Testable True
Section XML Schema - Basis

als json

2.02.00.05

Rule 2.02.00.05
Name A schema MUST NOT contain more than one XML comment node
Explanation
Introduction date 2010/06/23
Error message
NTA Rule True
PE Rule True
Testable True
Section XML Schema - Basis

als json

2.02.00.06

Rule 2.02.00.06
Name A schema MUST contain only prefixed element nodes
Explanation
Introduction date 2010/06/23
Error message
NTA Rule True
PE Rule True
References SBR-AU: 26 SA
Testable True
Section XML Schema - Basis

als json

2.02.00.07

Rule 2.02.00.07
Name A schema MUST have its root node (xs:schema) directly after the IP declaration
Explanation
Introduction date 2010/06/23
Error message
NTA Rule True
PE Rule
Testable True
Section XML Schema - Basis

als json

2.02.00.08

Rule 2.02.00.08
Name A schema MUST have a @targetNamespace
Explanation
Introduction date 2010/06/23
Error message
NTA Rule True
PE Rule True
Testable True
Section XML Schema - Basis

als json

2.02.00.09

Rule 2.02.00.09
Name A schema MUST use @attributeFormDefault and @elementFormDefault with the values ‘unqualified’ and ‘qualified’ respectively
Explanation
Introduction date 2010/06/23
Error message
NTA Rule True
PE Rule True
References SBR-AU: 25 SAFRTA 1.0: 4.2.4
Testable True
Section XML Schema - Basis

als json

2.02.00.10

Rule 2.02.00.10
Name A schema MUST NOT include @blockDefault, @finalDefault and @version
Explanation
Introduction date 2010/06/23
Related to 4.01.038, 4.01.040, 4.01.117, 4.01.119, 4.01.122, 2.02.02.09, 2.02.02.10
Error message
NTA Rule True
PE Rule True
References SBR-AU: 24 SI
Testable True
Section XML Schema - Basis

als json

2.02.00.11

Rule 2.02.00.11
Name A schema MUST NOT declare namespaces that are not being used in the schema EXCEPT for the namespace of a schema defining the domain-type of a typed dimension.
Explanation
Introduction date 2010/06/23
Error message
NTA Rule True
PE Rule
References SBR Australië: 27 SA
Testable
Section XML Schema - Basis

als json

2.02.00.12

Rule 2.02.00.12
Name A schema containing linkrole and/or arc role declarations MUST have that node (<xs:annotation><xs:appinfo>) directly behind the schema root node
Explanation
Introduction date 2010/06/23
Related to 4.01.004
Error message
NTA Rule True
PE Rule
Testable True
Section XML Schema - Basis

als json

2.02.00.13

Rule 2.02.00.13
Name REMOVED; A schema MUST NOT link linkbases which do not address elements from that schema EXCEPT for DTS entry point schemas
Explanation
Introduction date 2010/06/23
Decommission date 2011/09/28
Error message
NTA Rule True
PE Rule
Testable
Section XML Schema - Basis

als json

2.02.00.14

Rule 2.02.00.14
Name A schema using <xs:import> nodes MUST place these directly behind <xs:annotation><xs:appinfo>
Explanation
Introduction date 2010/06/23
Error message
NTA Rule True
PE Rule True
Testable True
Section XML Schema - Basis

als json

2.02.00.15

Rule 2.02.00.15
Name A schema MUST NOT import schemas of which no content is being addressed EXCEPT for XBRL specification schemas and schemas defining the domain-type of a typed dimension.
Explanation
Introduction date 2010/06/23
Error message
NTA Rule True
PE Rule True
Testable
Section XML Schema - Basis

als json

2.02.00.16

Rule 2.02.00.16
Name xs:schema/xs:import/@schemaLocation MUST use absolute URIs for files outside a version of the DTS
Explanation
Introduction date 2010/06/23
Related to 4.01.074
Error message
NTA Rule True
PE Rule True
Testable True
Section XML Schema - Basis

als json

2.02.00.17

Rule 2.02.00.17
Name xs:schema/xs:import/@schemaLocation MUST use relative URIs for files inside a version of the DTS
Explanation
Introduction date 2010/06/23
Related to 4.01.074
Error message
NTA Rule True
PE Rule True
Testable True
Section XML Schema - Basis

als json

2.02.00.18

Rule 2.02.00.18
Name xs:schema/xs:include MUST NOT be used
Explanation
Introduction date 2010/06/23
Error message
NTA Rule True
PE Rule True
References GFM2.0: 1.3.1
Testable True
Section XML Schema - Basis

als json

2.02.00.19

Rule 2.02.00.19
Name A schema MUST NOT declare namespace prefixes on element level
Explanation
Introduction date 2010/06/23
Error message
NTA Rule True
PE Rule True
References SBR-AU: 28 SAGFM2.0: 1.1.7http://www.w3.org/TR/xmlbase/#syntax
Testable True
Section XML Schema - Basis

als json

2.02.00.20

Rule 2.02.00.20
Name NT Partners MUST NOT create custom elements and attributes to extend concepts or linkbase content
Explanation
Introduction date 2011/04/06
Related to 4.01.015
Error message
NTA Rule True
PE Rule
References FRTA 2.3.9
Testable
Section XML Schema - Basis

als json

2.02.00.21

Rule 2.02.00.21
Name NT defined elements MUST be referred to by P- or D-links in any DTS entrypoint to have it represented in an instance or presentation.
Explanation
Introduction date 2010/06/23
Related to 2.02.02.04
Error message
NTA Rule True
PE Rule True
Testable
Section XML Schema - Basis

als json

2.02.00.22

Rule 2.02.00.22
Name Only one <xs:annotation> per schema file is allowed
Explanation
Introduction date 2011/11/23
Related to 2.02.00.12
Error message
NTA Rule True
PE Rule
Testable True
Section XML Schema - Basis

als json

2.02.00.23

Rule 2.02.00.23
Name Entrypoint xs:schema MUST have @id.
Explanation
Introduction date 2013/05/15
Agreed date 2012/12/05
Error message
NTA Rule True
PE Rule
Testable True
Section XML Schema - Basis

als json

2.02.00.24

Rule 2.02.00.24
Name A non-entrypoint schema MUST only contain linkbase refs to linkbases that in turn MUST refer to the schema itself.
Explanation
Introduction date 2015/12/02
Agreed date 2015/12/02
Error message
NTA Rule True
PE Rule
Testable
Section XML Schema - Basis

als json

2.02.00.25

Rule 2.02.00.25
Name A schema MUST NOT contain unused role types and arc role types
Explanation
Introduction date 2015/12/02
Agreed date 2015/12/02
Error message
NTA Rule True
PE Rule
Testable
Section XML Schema - Basis

als json

2.02.00.26

Rule 2.02.00.26
Name An entrypoint schema MUST only contain linkbaseRef to presentation, definition and generic linkbases and label linkbases typed industrySpecific, domainSpecific or entitySpecific
Explanation
Introduction date 2015/12/02
Agreed date 2015/12/02
Error message
NTA Rule True
PE Rule
Testable
Section XML Schema - Basis

als json

2.02.00.27

Rule 2.02.00.27
Name A schema MUST NOT contain duplicate linkbaseRefs.
Explanation
Introduction date 2015/12/02
Agreed date 2015/12/02
Error message
NTA Rule True
PE Rule
Testable True
Section XML Schema - Basis

als json

2.02.00.28

Rule 2.02.00.28
Name A DTS reachable from an entry point MUST NOT contain arcs in the same ELR pointing to the same from and to. In case of presentation links the preferredLabel also has to be considered.
Explanation
Introduction date 2015/12/02
Agreed date 2015/12/02
Error message
NTA Rule True
PE Rule
Testable
Section XML Schema - Basis

als json

2.02.00.29

Rule 2.02.00.29
Name
Explanation
Related to 2.02.00.04
Error message
NTA Rule
PE Rule True
Testable True
Section XML Schema - Basis

als json

2.02.00.30

Rule 2.02.00.30
Name
Explanation
Related to 2.02.00.07
Error message
NTA Rule
PE Rule True
Testable
Section XML Schema - Basis

als json

2.02.00.31

Rule 2.02.00.31
Name
Explanation
Error message
NTA Rule
PE Rule True
Testable
Section XML Schema - Basis

als json

2.02.00.32

Rule 2.02.00.32
Name
Explanation
Error message
NTA Rule
PE Rule True
Testable
Section XML Schema - Basis

als json

2.02.00.33

Rule 2.02.00.33
Name Newly created data-types MUST be used by concepts
Explanation
Error message
NTA Rule
PE Rule True
Testable
Section XML Schema - Basis

als json

2.02.00.34

Rule 2.02.00.34
Name
Explanation
Error message
NTA Rule
PE Rule True
Testable
Section XML Schema - Basis

als json

2.02.00.35

Rule 2.02.00.35
Name
Explanation
Error message
NTA Rule
PE Rule True
Testable
Section XML Schema - Basis

als json

2.02.00.36

Rule 2.02.00.36
Name
Explanation
Error message
NTA Rule
PE Rule True
Testable
Section XML Schema - Basis

als json

2.02.00.37

Rule 2.02.00.37
Name
Explanation
Error message
NTA Rule
PE Rule True
Testable
Section XML Schema - Basis

als json

XML Schema - XLink

2.02.01.01

Rule 2.02.01.01
Name A schema MUST be a DTS entrypoint OR define linkroles OR arcroles OR link:parts OR context fragments OR abstract items OR types OR enumerations OR dimensions OR domain(member)s OR hypercubes, NO mixing EXCEPT for tuples.
Explanation
Introduction date 2010/06/23
Error message
NTA Rule True
PE Rule
References SBR Australië: 20 DI / 50 DI / 51 DI / 52 DI / 53 SA / 54 DI
Testable True
Section XML Schema - XLink

als json

2.02.01.02

Rule 2.02.01.02
Name A schema that defines concepts MUST have a linked 2.1 label linkbase A schema defining non-reportable concepts for the presentation hierarchy of tables MUST have a linked generic label linkbase.
Explanation
Introduction date 2010/06/23
Related to 2.02.02.26
Error message
NTA Rule True
PE Rule True
References SBR-AU: 15 SI
Section XML Schema - XLink

als json

2.02.01.03

Rule 2.02.01.03
Name A schema that defines non-abstract items MUST have a linked (2.1) reference linkbase AND/OR a label linkbase with @xlink:role=documentation
Explanation
Introduction date 2010/06/23
Related to 2.02.02.28
Error message
NTA Rule True
PE Rule
References SBR Australië: 16 SI
Testable True
Section XML Schema - XLink

als json

2.02.01.04

Rule 2.02.01.04
Name A schema that defines XML nodes MUST have a linked (generic) label linkbase
Explanation
Agreed date 2010/06/23
Error message
NTA Rule True
PE Rule
Testable True
Section XML Schema - XLink

als json

2.02.01.05

Rule 2.02.01.05
Name An element MUST NOT have more than one label resource in one language, role, arcrole, linkrole. Excempt are 'documentation' and the different 'guidance' roles which may occur more than once
Explanation
Introduction date 2010/06/23
Error message
NTA Rule True
PE Rule True
References FRTA 2.1.11 FRTA 2.1.18
Testable True
Section XML Schema - XLink

als json

2.02.01.06

Rule 2.02.01.06
Name
Explanation
Related to 2.02.01.03
Error message
NTA Rule
PE Rule True
Section XML Schema - XLink

als json

XML Schema - Concepten

2.02.02.01

Rule 2.02.02.01
Name Concept definitions MUST be placed on root level in a schema
Explanation
Introduction date 2010/06/23
Error message
NTA Rule True
PE Rule True
Testable True
Section XML Schema - Concepten

als json

2.02.02.02

Rule 2.02.02.02
Name Concepts MUST NOT be defined more than once in the Dutch Taxonomy EXCEPT for concepts who have a general-special definition link
Explanation
Introduction date 2010/06/23
Related to Architectuurregels 2.03.02.x, 3.02.05.20
Error message
NTA Rule
PE Rule
References FRTA 2.1.1
Testable
Section XML Schema - Concepten

als json

2.02.02.03

Rule 2.02.02.03
Name Abstract tuples MUST NOT occur
Explanation
Introduction date 2010/06/23
Related to 4.01.041
Error message
NTA Rule True
PE Rule True
Testable True
Section XML Schema - Concepten

als json

2.02.02.04

Rule 2.02.02.04
Name All concepts in the substitutionGroup xbrli:item or sbr:presentationItem created by a Dutch Taxonomy partner, with the exception of non-reportable concepts used for the presentation hierarchy of tables, MUST be used in any presentation linkbase from that Dutch Taxonomy partner
Explanation
Error message
NTA Rule True
PE Rule
Testable
Section XML Schema - Concepten

als json

2.02.02.05

Rule 2.02.02.05
Name <xs:element> MUST NOT be used to create new abstract elements that will serve as substitutionGroup for other elements, EXCEPT for SBR-Dutch Taxonomy-management
Explanation
Introduction date 2010/06/23
Related to 4.01.041
Error message
NTA Rule True
PE Rule True
Testable True
Section XML Schema - Concepten

als json

2.02.02.06

Rule 2.02.02.06
Name EXPIRED Non abstract items defined as child of a tuple MUST carry identical @periodType values, where the value ’instant’ is leading over the value ‘duration’. EXCEPT for Dutch Taxonomy partners who want to reduce the number repetitions of concepts through XML Schedule, they can define their own root tuple. All concepts MUST be (grand)child to this root tuple and the aforementioned rule about the xbrli:periodType does not apply to this special root tuple.
Explanation
Introduction date 2010/06/23
Decommission date 2011/05/04
Related to 2.02.02.29, 2.04.00.03
Error message
NTA Rule True
PE Rule
References FRTA 2.2.8
Section XML Schema - Concepten

als json

2.02.02.07

Rule 2.02.02.07
Name Tuples MUST NOT create cycles
Explanation
Introduction date 2010/06/23
Related to FRTA 2.3.6
Error message
NTA Rule True
PE Rule True
Section XML Schema - Concepten

als json

2.02.02.08

Rule 2.02.02.08
Name xs:schema/xs:element/@abstract is mandatory
Explanation
Introduction date 2010/06/23
Related to 4.01.041
Error message
NTA Rule True
PE Rule True
References SBR Australië: 133 SI
Testable True
Section XML Schema - Concepten

als json

2.02.02.09

Rule 2.02.02.09
Name //xs:element/@block is NOT allowed
Explanation
Introduction date 2010/06/23
Error message
NTA Rule True
PE Rule True
References SBR Australië: 134 SI
Testable True
Section XML Schema - Concepten

als json

2.02.02.10

Rule 2.02.02.10
Name //xs:element/@final is NOT allowed
Explanation
Introduction date 2010/06/23
Related to 4.01.044
Error message
NTA Rule True
PE Rule True
References SBR Australië: 135 SI
Testable True
Section XML Schema - Concepten

als json

2.02.02.11

Rule 2.02.02.11
Name //xs:element/@fixed is NOT allowed
Explanation
Introduction date 2010/06/23
Error message
NTA Rule True
PE Rule True
References SBR Australië: 136 SI
Testable True
Section XML Schema - Concepten

als json

2.02.02.12

Rule 2.02.02.12
Name EXPIRED @form MUST NOT be used on <xs:element>
Explanation
Introduction date 2010/06/23
Decommission date 2011/07/04
Related to 4.01.046
Error message
NTA Rule True
PE Rule True
References SBR Australië: 137 SI
Section XML Schema - Concepten

als json

2.02.02.13

Rule 2.02.02.13
Name //xs:element/@id is mandatory
Explanation
Introduction date 2010/06/23
Related to 4.01.047, 3.02.06.01
Error message
NTA Rule True
PE Rule True
Testable True
Section XML Schema - Concepten

als json

2.02.02.14

Rule 2.02.02.14
Name @maxOccurs and @minOccurs MUST be included on nodes where they are allowed
Explanation
Introduction date 2010/06/23
Related to 4.01.048, 2.02.02.30
Error message
NTA Rule True
PE Rule True
Section XML Schema - Concepten

als json

2.02.02.15

Rule 2.02.02.15
Name //xs:element/@nillable is mandatory
Explanation
Introduction date 2010/06/23
Related to FRTA 1.0 (2.1.6), 4.01.051
Error message
NTA Rule True
PE Rule True
Testable True
Section XML Schema - Concepten

als json

2.02.02.16

Rule 2.02.02.16
Name xs:schema/xs:element/@nillable=’false’ MUST be used when xs:schema/xs:element/@abstract=’true’
Explanation
Introduction date 2010/06/23
Error message
NTA Rule True
PE Rule True
Testable True
Section XML Schema - Concepten

als json

2.02.02.17

Rule 2.02.02.17
Name xs:schema/xs:element/@nillable=’false’ MUST be used when xs:schema/xs:element/@substitutionGroup=’xbrli:tuple’ and its derivatives
Explanation
Introduction date 2010/06/23
Error message
NTA Rule True
PE Rule True
Testable True
Section XML Schema - Concepten

als json

2.02.02.18

Rule 2.02.02.18
Name @substitutionGroup MUST be used on root <xs:element> for concepts
Explanation
Introduction date 2010/06/23
Related to 2.02.02.05, 2.02.02.19, 4.01.053
Error message
NTA Rule True
PE Rule True
Testable True
Section XML Schema - Concepten

als json

2.02.02.19

Rule 2.02.02.19
Name @substitutionGroup MUST refer the SBR defined elements (sbr:domainItem, sbr:primaryDomainItem and sbr:domainMemberItem) if the item is used as abstract domain or domainmember
Explanation
Introduction date 2010/06/23
Related to 2.02.02.18, 4.01.041, 4.01.053
Error message
NTA Rule True
PE Rule True
References XDT1.0 Def11 GFM2.0 2.3.18
Section XML Schema - Concepten

als json

2.02.02.20

Rule 2.02.02.20
Name @type of item concepts SHOULD refer to xbrli defined types, its derivations or sbr:placeholder, when @substitutionGroup contains a value from the xbrli namespace or its derivation
Explanation
Introduction date 2010/06/23
Related to 4.01.054
Error message
NTA Rule True
PE Rule True
References XBRL2.1: 5.1.1.3 FRTA1.0: 2.2.1
Section XML Schema - Concepten

als json

2.02.02.21

Rule 2.02.02.21
Name xs:schema/xs:element/@type="xbrli:stringItemType if xs:schema/xs:element/@abstract="true"
Explanation
Introduction date 2010/06/23
Related to 2.02.02.20
Error message
NTA Rule True
PE Rule True
Testable True
Section XML Schema - Concepten

als json

2.02.02.22

Rule 2.02.02.22
Name EXPIRED @xbrli:balance MUST NOT be used on <xs:element> when @abstract=’true’
Explanation
Introduction date 2010/06/23
Decommission date 2011/08/30
Error message
NTA Rule True
PE Rule
Section XML Schema - Concepten

als json

2.02.02.23

Rule 2.02.02.23
Name @xbrli:balance MUST NOT appear on non abstract items that are not reported on a balance sheet or profit and loss statement or as details in the cashflow
Explanation
Introduction date 2010/06/23
Error message
NTA Rule True
PE Rule
References FRTA1.0 2.2.3
Section XML Schema - Concepten

als json

2.02.02.24

Rule 2.02.02.24
Name EXPIRED @xbrli:balance MUST NOT appear on items that are not xbrli:monetaryItemType, or its derivations
Explanation
Introduction date 2010/06/23
Decommission date 2011/08/30
Related to 2.02.02.23
Error message
NTA Rule True
PE Rule
References XBRL2.1: 5.1.1.2 FRTA1.0: 2.2.3 GFM2.0: 2.3.11
Section XML Schema - Concepten

als json

2.02.02.25

Rule 2.02.02.25
Name xs:schema/xs:element/@xbrli:periodType MUST be 'duration' for non-reportable items. For reportable items it SHOULD be 'duration', EXCEPT for reportable items that are are reported at a specific time.
Explanation
Introduction date 2010/06/23
Related to 4.01.056
Error message
NTA Rule True
PE Rule
References XBRL2.1: 5.1.1.1FRTA1.0: 2.2.9SBR-AU: 58 SAGFM2.0: 2.3.12
Testable True
Section XML Schema - Concepten

als json

2.02.02.26

Rule 2.02.02.26
Name A concept MUST have a standard label in the local language
Explanation
Introduction date 2010/06/23
Related to 2.02.02.04
Error message
NTA Rule True
PE Rule
References SBR Australië: 103 SIFRTA 2.1.10
Testable True
Section XML Schema - Concepten

als json

2.02.02.27

Rule 2.02.02.27
Name Dutch Taxonomy domains that want to equip elements with languages other the local language, MUST create labels in that language for the NL-GEN and NL-CD DTSs AND are responsible for the maintenance of these labels
Explanation
Introduction date 2011/04/06
Related to 3.02.15.02
Error message
NTA Rule True
PE Rule
Section XML Schema - Concepten

als json

2.02.02.28

Rule 2.02.02.28
Name xs:schema/xs:element/@substitutionGroup="xbrli:item" AND @abstract="false" MUST have an active reference resource with @xlink:role=standard AND/OR an active label resource with @xlink:role=documentation
Explanation
Introduction date 2010/06/23
Related to 2.02.01.03
Error message
References SBR Australië: 104 SI
Section XML Schema - Concepten

als json

2.02.02.29

Rule 2.02.02.29
Name EXPIRED Tuple children MUST have the same @xbrli:periodType EXCEPT for children of a technical root tuple.
Explanation
Introduction date 2011/04/06
Decommission date 2011/05/05
Related to 2.02.02.06
Error message
NTA Rule True
PE Rule
Section XML Schema - Concepten

als json

2.02.02.30

Rule 2.02.02.30
Name Tuple item children SHOULD have @maxOccurs with the value of 1 (one). Exception: item children which may have different period content in the context of the instance.
Explanation
Introduction date 2011/04/06
Related to 2.02.02.14
Error message
NTA Rule True
PE Rule True
Section XML Schema - Concepten

als json

2.02.02.31

Rule 2.02.02.31
Name Items with @abstract="true" MUST NOT be children of a tuple
Explanation
Introduction date 2011/04/06
Error message
NTA Rule True
PE Rule True
Section XML Schema - Concepten

als json

2.02.02.32

Rule 2.02.02.32
Name REMOVED Tuples MUST NOT have abstract='true'
Explanation
Introduction date 2011/04/06
Decommission date 2011/11/22
Related to 2.02.02.03
Error message
NTA Rule True
PE Rule
Testable
NTA Versions NT14
Section XML Schema - Concepten

als json

2.02.02.33

Rule 2.02.02.33
Name Model groups like @sequence and @choice as tuple children content MUST have @minOccurs=1 IF only one model group exists in the content model. @maxOccurs MAY have a value higher than one if the repetition is needed in the instance for expressing time differences.
Explanation
Introduction date 2011/04/06
Related to 4.01.026, 4.01.125
Error message
NTA Rule True
PE Rule True
Section XML Schema - Concepten

als json

2.02.02.34

Rule 2.02.02.34
Name REMOVED A schema MUST NOT declare namespace prefix' at element level
Explanation
Introduction date 2011/04/06
Decommission date 2011/11/11
Related to 2.02.00.19
Error message
NTA Rule True
PE Rule
References GFM2.0: 1.1.7
Section XML Schema - Concepten

als json

2.02.02.35

Rule 2.02.02.35
Name A concept may not be based on the type nl-types:imageItemType.
Explanation
Introduction date 2017/05/15
Error message
NTA Rule True
PE Rule
Testable True
Section XML Schema - Concepten

als json

2.02.02.36

Rule 2.02.02.36
Name
Explanation
Related to 2.02.02.02
Error message
NTA Rule
PE Rule True
Section XML Schema - Concepten

als json

2.02.02.37

Rule 2.02.02.37
Name
Explanation
Related to 2.02.02.25
Error message
NTA Rule
PE Rule
Section XML Schema - Concepten

als json

2.02.02.38

Rule 2.02.02.38
Name
Explanation
Related to 2.02.02.26
Error message
NTA Rule
PE Rule True
Section XML Schema - Concepten

als json

2.02.02.39

Rule 2.02.02.39
Name
Explanation
Related to 2.02.02.28
Error message
NTA Rule
PE Rule True
Section XML Schema - Concepten

als json

2.02.02.40

Rule 2.02.02.40
Name
Explanation
Error message
NTA Rule
PE Rule True
Section XML Schema - Concepten

als json

2.02.02.41

Rule 2.02.02.41
Name
Explanation
Error message
NTA Rule
PE Rule True
Section XML Schema - Concepten

als json

XML Schema - Linkroles

2.02.03.01

Rule 2.02.03.01
Name //link:usedOn="link:calculationLink" MUST NOT be used
Explanation
Introduction date 2010/06/23
Error message
NTA Rule True
PE Rule True
Testable True
Section XML Schema - Linkroles

als json

2.02.03.02

Rule 2.02.03.02
Name A linkrole MUST NOT have a child element <link:usedOn> whose value is not addressed
Explanation
Introduction date 2010/06/23
Error message
NTA Rule True
PE Rule
Testable True
Section XML Schema - Linkroles

als json

2.02.03.03

Rule 2.02.03.03
Name A linkrole URI MUST have a Generic Label; A linkrole MUST have a standard label
Explanation
Introduction date 2012/05/15
Agreed date 2010/06/23
Related to 2.02.01.04
Error message
NTA Rule True
PE Rule
References SBR Australië: 64 DI
Testable True
Section XML Schema - Linkroles

als json

2.02.03.04

Rule 2.02.03.04
Name //link:definition MUST have NL text identical to the linkrole generic label
Explanation
Introduction date 2011/04/06
Agreed date 2010/06/23
Error message
NTA Rule True
PE Rule
Section XML Schema - Linkroles

als json

2.02.03.05

Rule 2.02.03.05
Name A linkrole containing hypercubes MUST contain relationships where the hypercube is either parent or child AND/OR relationships where the primaryDomain is either parent or child.
Explanation
Introduction date 2010/06/23
Error message
NTA Rule True
PE Rule
Section XML Schema - Linkroles

als json

2.02.03.06

Rule 2.02.03.06
Name A linkrole MUST have an unique presentationArc order number, if there are multiple per entrypoint
Explanation
Introduction date 2010/06/23
Error message
NTA Rule True
PE Rule True
Section XML Schema - Linkroles

als json

2.02.03.07

Rule 2.02.03.07
Name <link:definition> content MUST be seen as xs:tokenizedString content
Explanation
Introduction date 2011/04/06
Error message
NTA Rule True
PE Rule
References GFM2.0: 1.3.13
Section XML Schema - Linkroles

als json

2.02.03.08

Rule 2.02.03.08
Name
Explanation
Error message
NTA Rule
PE Rule True
Section XML Schema - Linkroles

als json

XML Schema - Arcroles

2.02.04.01

Rule 2.02.04.01
Name Arcroles MUST NOT be created by Dutch Taxonomy Partners
Explanation
Introduction date 2010/06/23
Related to 4.01.013, 4.02.010
Error message
NTA Rule True
PE Rule True
Testable True
Section XML Schema - Arcroles

als json

2.02.04.02

Rule 2.02.04.02
Name Custom arcroles MUST have a Generic Label in Dutch and English
Explanation
Introduction date 2010/06/23
Error message
NTA Rule True
PE Rule
Section XML Schema - Arcroles

als json

XML Schema - link:parts

2.02.05.01

Rule 2.02.05.01
Name Reference resource parts MUST NOT be created by Dutch Taxonomy Partners
Explanation
Introduction date 2010/06/23
Related to Reference parts
Error message
NTA Rule True
PE Rule True
Testable True
Section XML Schema - link:parts

als json

2.02.05.02

Rule 2.02.05.02
Name SBR reference resource parts MUST have a Generic Label
Explanation
Introduction date 2010/06/23
Related to FRTA 2.1.22
Error message
NTA Rule True
PE Rule
References SBR Australië: 76 DI
Section XML Schema - link:parts

als json

XML Schema - Context elementen

2.02.06.01

Rule 2.02.06.01
Name A custom context element MUST have a Generic Label
Explanation
Introduction date 2012/05/15
Agreed date 2010/06/23
Related to 2.02.01.04
Error message
NTA Rule True
PE Rule
Section XML Schema - Context elementen

als json

2.02.06.02

Rule 2.02.06.02
Name A custom context element MUST have Business Rules documentation how and when to use it, plus a Generic Reference to that documentation
Explanation
Introduction date 2010/06/23
Error message
NTA Rule True
PE Rule
Section XML Schema - Context elementen

als json

2.02.06.03

Rule 2.02.06.03
Name
Explanation
Error message
NTA Rule
PE Rule True
Testable True
Section XML Schema - Context elementen

als json

XML Schema - Type & Enumeraties

2.02.07.01

Rule 2.02.07.01
Name Non xbrli data types MUST be presented to SBR-Dutch Taxonomy-management before publication
Explanation
Introduction date 2010/06/23
Error message
NTA Rule True
PE Rule
Section XML Schema - Type & Enumeraties

als json

2.02.07.02

Rule 2.02.07.02
Name Length restrictions on types SHOULD be prevented (use business rules)
Explanation
Introduction date 2010/06/23
Error message
NTA Rule True
PE Rule True
Testable True
Section XML Schema - Type & Enumeraties

als json

2.02.07.03

Rule 2.02.07.03
Name Enumerations SHOULD be prevented (use domain)
Explanation
Error message
NTA Rule True
PE Rule
Testable True
Section XML Schema - Type & Enumeraties

als json

2.02.07.04

Rule 2.02.07.04
Name <xs:enumeration> MUST use <xs:restriction base=xbrli:stringItemType/> if it is being used as type definition for a concept. Tuples are exempt from this rule.
Explanation
Introduction date 2010/06/23
Error message
NTA Rule True
PE Rule True
Testable True
Section XML Schema - Type & Enumeraties

als json

2.02.07.05

Rule 2.02.07.05
Name <xs:enumeration><xs:value> MUST use generic labels.
Explanation
Introduction date 2010/06/23
Error message
NTA Rule True
PE Rule True
Section XML Schema - Type & Enumeraties

als json

2.02.07.06

Rule 2.02.07.06
Name
Explanation
Related to 2.02.07.03
Error message
NTA Rule
PE Rule True
Section XML Schema - Type & Enumeraties

als json

XML Schema - Dimensies

2.02.08.01

Rule 2.02.08.01
Name Typed dimension elements MUST have a Generic Label
Explanation
Introduction date 2010/06/23
Error message
NTA Rule True
PE Rule
Section XML Schema - Dimensies

als json

2.02.08.02

Rule 2.02.08.02
Name Typed dimension elements MUST be simpleType elements
Explanation
Introduction date 2010/06/23
Error message
NTA Rule True
PE Rule
Section XML Schema - Dimensies

als json

XML Schema - Domeinen en Domeinleden

2.02.09.01

Rule 2.02.09.01
Name See 2.02.02.19
Explanation
Introduction date 2010/06/23
Related to 2.02.02.19
Error message
NTA Rule True
PE Rule
Section XML Schema - Domeinen en Domeinleden

als json

XML Schema - Entrypoint schema’s

2.02.10.01

Rule 2.02.10.01
Name Entrypoint schemas MUST have presentation linkbase(s)
Explanation
Introduction date 2010/06/23
Error message
NTA Rule True
PE Rule
Testable True
Section XML Schema - Entrypoint schema’s

als json

2.02.10.02

Rule 2.02.10.02
Name An entry point schedule in a dimensional DTS MUST contain at least presentation linkbase(s) for non-abstract items.
Explanation
Introduction date 2011/04/06
Error message
NTA Rule True
PE Rule
Section XML Schema - Entrypoint schema’s

als json

2.02.10.03

Rule 2.02.10.03
Name Entrypoint schemas MUST have presentation linkbase(s) for dimension, domain and domain members in dimensional DTSs
Explanation
Introduction date 2010/06/23
Decommission date 2018/03/01
Error message
NTA Rule True
PE Rule
Section XML Schema - Entrypoint schema’s

als json

2.02.10.04

Rule 2.02.10.04
Name
Explanation
Related to 2.02.10.01
Error message
NTA Rule
PE Rule True
Section XML Schema - Entrypoint schema’s

als json

2.02.10.05

Rule 2.02.10.05
Name
Explanation
Error message
NTA Rule
PE Rule True
Section XML Schema - Entrypoint schema’s

als json

2.02.10.06

Rule 2.02.10.06
Name
Explanation
Error message
NTA Rule
PE Rule True
Section XML Schema - Entrypoint schema’s

als json

2.02.10.07

Rule 2.02.10.07
Name
Explanation
Error message
NTA Rule
PE Rule True
Section XML Schema - Entrypoint schema’s

als json

2.02.10.08

Rule 2.02.10.08
Name
Explanation
Error message
NTA Rule
PE Rule True
Section XML Schema - Entrypoint schema’s

als json

2.02.10.09

Rule 2.02.10.09
Name
Explanation
Error message
NTA Rule
PE Rule True
Section XML Schema - Entrypoint schema’s

als json

XML Schema - Overig

2.02.11.01

Rule 2.02.11.01
Name <xs:all> MUST NOT be used
Explanation
Introduction date 2010/06/23
Error message
NTA Rule True
PE Rule True
References FRTA 2.3.7
Testable True
Section XML Schema - Overig

als json

2.02.11.02

Rule 2.02.11.02
Name <xs:annotation><xs:documentation> MUST NOT be used
Explanation
Introduction date 2010/06/23
Related to 4.01.037
Error message
NTA Rule True
PE Rule True
Testable True
Section XML Schema - Overig

als json

2.02.11.03

Rule 2.02.11.03
Name <xs:any> MUST NOT be used by Dutch Taxonomy Partners
Explanation
Introduction date 2010/06/23
Error message
NTA Rule True
PE Rule True
Testable True
Section XML Schema - Overig

als json

2.02.11.04

Rule 2.02.11.04
Name <xs:anyAttribute> MUST NOT be used by Dutch Taxonomy Partners
Explanation
Introduction date 2010/06/23
Related to 2.02.11.03
Error message
NTA Rule True
PE Rule True
Testable True
Section XML Schema - Overig

als json

2.02.11.05

Rule 2.02.11.05
Name <xs:appinfo> MUST NOT be used for other content then elements from the xlink or link namespaces
Explanation
Introduction date 2010/06/23
Error message
NTA Rule True
PE Rule True
References SBR Australië: 125 SA
Testable True
Section XML Schema - Overig

als json

2.02.11.06

Rule 2.02.11.06
Name <xs:attribute> MUST NOT be used by Dutch Taxonomy Partners
Explanation
Introduction date 2010/06/23
Error message
NTA Rule True
PE Rule True
References FRTA 2.3.9
Testable True
Section XML Schema - Overig

als json

2.02.11.07

Rule 2.02.11.07
Name <xs:attributeGroup> MUST NOT be created by Dutch Taxonomy Partners
Explanation
Introduction date 2010/06/23
Error message
NTA Rule True
PE Rule True
References SBR Australië: 127 SA
Testable True
Section XML Schema - Overig

als json

2.02.11.08

Rule 2.02.11.08
Name <xs:choice> MUST NOT be used for simpleType elements
Explanation
Introduction date 2010/06/23
Error message
NTA Rule True
PE Rule True
References SBR Australië: 128 SA
Testable True
Section XML Schema - Overig

als json

2.02.11.09

Rule 2.02.11.09
Name <xs:choice> SHOULD NOT be used for complexType elements
Explanation
Introduction date 2010/06/23
Error message
NTA Rule True
PE Rule True
Testable
Section XML Schema - Overig

als json

2.02.11.10

Rule 2.02.11.10
Name <xs:complexContent> with <xs:extension base="sbr:placeholder"> MUST be used by Dutch Taxonomy Partners when using tuples
Explanation
Introduction date 2010/06/23
Error message
NTA Rule True
PE Rule True
Section XML Schema - Overig

als json

2.02.11.11

Rule 2.02.11.11
Name <xs:complexType> MUST NOT be created by Dutch Taxonomy Partners as a local root node child to <xs:schema>
Explanation
Error message
NTA Rule True
PE Rule True
Section XML Schema - Overig

als json

2.02.11.12

Rule 2.02.11.12
Name <xs:extension> MUST NOT be used by Dutch Taxonomy Partners
Explanation
Introduction date 2010/06/23
Error message
NTA Rule True
PE Rule True
Testable True
Section XML Schema - Overig

als json

2.02.11.13

Rule 2.02.11.13
Name REMOVED <xs:field> MUST NOT be used by Dutch Taxonomy Partners
Explanation
Introduction date 2010/06/23
Decommission date 2013/03/13
Error message xs:field MOET NIET gebruikt worden door NT Partners
NTA Rule True
PE Rule
Section XML Schema - Overig

als json

2.02.11.14

Rule 2.02.11.14
Name <xs:group> MUST NOT be used by Dutch Taxonomy Partners
Explanation
Introduction date 2010/06/23
Error message
NTA Rule True
PE Rule True
Testable True
Section XML Schema - Overig

als json

2.02.11.15

Rule 2.02.11.15
Name <xs:key> MUST NOT be used
Explanation
Introduction date 2010/06/23
Error message
NTA Rule True
PE Rule True
Testable True
Section XML Schema - Overig

als json

2.02.11.16

Rule 2.02.11.16
Name <xs:keyref> MUST NOT be used
Explanation
Introduction date 2010/06/23
Error message
NTA Rule True
PE Rule True
Testable True
Section XML Schema - Overig

als json

2.02.11.17

Rule 2.02.11.17
Name <xs:list> MUST NOT be used
Explanation
Introduction date 2010/06/23
Error message
NTA Rule True
PE Rule True
Testable True
Section XML Schema - Overig

als json

2.02.11.18

Rule 2.02.11.18
Name <xs:notation> MUST NOT be used by Dutch Taxonomy Partners
Explanation
Introduction date 2010/06/23
Error message
NTA Rule True
PE Rule True
Testable True
Section XML Schema - Overig

als json

2.02.11.19

Rule 2.02.11.19
Name <xs:pattern> SHOULD NOT be used
Explanation
Introduction date 2010/06/23
Error message
NTA Rule True
PE Rule True
Testable True
Section XML Schema - Overig

als json

2.02.11.20

Rule 2.02.11.20
Name <xs:redefine> MUST NOT be used by Dutch Taxonomy Partners
Explanation
Introduction date 2010/06/23
Error message
NTA Rule True
PE Rule True
Testable True
Section XML Schema - Overig

als json

2.02.11.21

Rule 2.02.11.21
Name <xs:restriction> MUST NOT be used on <xs:element>, only on <xs:simpleType>
Explanation
Introduction date 2010/06/23
Error message
NTA Rule True
PE Rule True
Testable True
Section XML Schema - Overig

als json

2.02.11.22

Rule 2.02.11.22
Name REMOVED <xs:selector> MUST NOT be used
Explanation
Introduction date 2010/06/23
Decommission date 2013/03/13
Error message
NTA Rule True
PE Rule True
Section XML Schema - Overig

als json

2.02.11.23

Rule 2.02.11.23
Name <xs:unique> MUST NOT be used in the Dutch Taxonomy
Explanation
Introduction date 2010/06/23
Error message
NTA Rule True
PE Rule True
Testable True
Section XML Schema - Overig

als json

XML Linkbase - Basis

2.03.00.01

Rule 2.03.00.01
Name A linkbase MUST comply with W3C XLink Specification 1.0
Explanation
Introduction date 2010/06/23
Error message
NTA Rule True
PE Rule True
References GFM2.0: 1.4.1
Testable True
Section XML Linkbase - Basis

als json

2.03.00.02

Rule 2.03.00.02
Name A linkbase MUST only contain content based on XML Specification 1.0 of the W3C
Explanation
Introduction date 2010/06/23
Related to 2.02.00.02
Error message
NTA Rule True
PE Rule True
References SBR Australië: 29 SA
Testable True
Section XML Linkbase - Basis

als json

2.03.00.03

Rule 2.03.00.03
Name A linkbase MUST support the UTF-8 character set for its content
Explanation
Introduction date 2010/06/23
Related to 2.02.00.03
Error message
NTA Rule True
PE Rule True
References SBR Australië: 30 SAGFM2.0: 1.1.8
Testable True
Section XML Linkbase - Basis

als json

2.03.00.04

Rule 2.03.00.04
Name A linkbase MUST draw the IP rights in the XML comment section on line number two (and beyond)
Explanation
Introduction date 2010/06/23
Related to 2.02.00.04
Error message
NTA Rule True
PE Rule
References SBR Australië: 7 SA
Testable True
Section XML Linkbase - Basis

als json

2.03.00.05

Rule 2.03.00.05
Name A linkbase MUST NOT contain more than one XML comment section
Explanation
Introduction date 2010/06/23
Related to 2.02.00.05
Error message
NTA Rule True
PE Rule True
Testable True
Section XML Linkbase - Basis

als json

2.03.00.06

Rule 2.03.00.06
Name A linkbase MUST contain only prefixed nodes
Explanation
Introduction date 2010/06/23
Related to 2.02.00.06
Error message
NTA Rule True
PE Rule True
References SBR Australië: 32 SA
Testable True
Section XML Linkbase - Basis

als json

2.03.00.07

Rule 2.03.00.07
Name A linkbase MUST use @xsi:schemaLocation for schema content being addressed inside the linkbase EXCEPT the W3C XML schema and XBRL XLink schemas
Explanation
Introduction date 2010/06/23
Error message
NTA Rule True
PE Rule True
Section XML Linkbase - Basis

als json

2.03.00.08

Rule 2.03.00.08
Name A linkbase MUST NOT declare namespaces that are not being used in the linkbase
Explanation
Introduction date 2010/06/23
Related to 2.02.00.11
Error message
NTA Rule True
PE Rule
References SBR Australië: 33 SA
Testable True
Section XML Linkbase - Basis

als json

2.03.00.09

Rule 2.03.00.09
Name REMOVED See 2.03.01.01
Explanation
Decommission date 2011/01/01
Error message
NTA Rule True
PE Rule
Section XML Linkbase - Basis

als json

2.03.00.10

Rule 2.03.00.10
Name <link:presentationLink>, <link:labelLink>, <gen:link> en <link:referenceLink> MUST NOT contain relations using @use="prohibit"
Explanation
Error message
NTA Rule True
PE Rule
Testable True
Section XML Linkbase - Basis

als json

2.03.00.11

Rule 2.03.00.11
Name A XBRL 2.1 defined linkbase MUST contain link elements from the same namespace and local name only; the XBRL 2.1 specified
Explanation
Introduction date 2011/04/06
Error message
NTA Rule True
PE Rule True
References GFM 1.4.7
Section XML Linkbase - Basis

als json

2.03.00.12

Rule 2.03.00.12
Name A linkbase MUST contain relationships
Explanation
Introduction date 2011/04/06
Error message
NTA Rule True
PE Rule True
References GFM2.0: 1.4.3
Testable True
Section XML Linkbase - Basis

als json

2.03.00.13

Rule 2.03.00.13
Name A linkbase MUST NOT declare locators that are not being used in the linkbase
Explanation
Introduction date 2015/12/02
Agreed date 2015/12/02
Error message
NTA Rule True
PE Rule
Section XML Linkbase - Basis

als json

2.03.00.14

Rule 2.03.00.14
Name A linkbase MUST NOT declare resources that are not being used in the linkbase
Explanation
Introduction date 2015/12/02
Agreed date 2015/12/02
Error message
NTA Rule True
PE Rule
Section XML Linkbase - Basis

als json

2.03.00.15

Rule 2.03.00.15
Name A linkbase MUST NOT declare roleRef and arcroleRef elements that are not being used in the linkbase
Explanation
Introduction date 2015/12/02
Agreed date 2015/12/02
Error message
NTA Rule True
PE Rule
Section XML Linkbase - Basis

als json

2.03.00.16

Rule 2.03.00.16
Name Extended links MUST NOT contain more than 1 locator referring to the same element, except in the case of locators referred to by children of parent-child arcs in a presentation link, having the same parent and with different preferredLabel attributes, possibly with one arc without preferredLabel.
Explanation
Introduction date 2015/12/02
Agreed date 2015/12/02
Error message
NTA Rule True
PE Rule
Section XML Linkbase - Basis

als json

2.03.00.17

Rule 2.03.00.17
Name
Explanation
Error message
NTA Rule
PE Rule True
Section XML Linkbase - Basis

als json

2.03.00.18

Rule 2.03.00.18
Name
Explanation
Error message
NTA Rule
PE Rule True
Section XML Linkbase - Basis

als json

XML Linkbase - Elementen

2.03.01.01

Rule 2.03.01.01
Name A linkbase MUST NOT use namespaces on element level
Explanation
Introduction date 2010/06/23
Related to 2.02.00.19
Error message
NTA Rule True
PE Rule
Testable True
Section XML Linkbase - Elementen

als json

XML Linkbase - Arcroles

2.03.02.01

Rule 2.03.02.01
Name REMOVED The arcrole ‘general-special’ MUST be used to link concepts with different technical definitions (like @type) but are semantically equivalent
Explanation
Introduction date 2010/06/23
Decommission date 2011/11/23
Related to 2.03.02.08, 2.02.02.02
Error message
NTA Rule True
PE Rule
Section XML Linkbase - Arcroles

als json

2.03.02.02

Rule 2.03.02.02
Name The arcrole ‘essence-alias’ MUST NOT be used
Explanation
Introduction date 2010/06/23
Error message
NTA Rule True
PE Rule True
Testable True
Section XML Linkbase - Arcroles

als json

2.03.02.03

Rule 2.03.02.03
Name The arcrole ‘similar-tuple’ MUST NOT be used
Explanation
Introduction date 2010/06/23
Error message
NTA Rule True
PE Rule True
Testable True
Section XML Linkbase - Arcroles

als json

2.03.02.04

Rule 2.03.02.04
Name The arcrole ‘requires-element’ MUST NOT be used (use business rules)
Explanation
Introduction date 2010/06/23
Error message
NTA Rule True
PE Rule True
Testable True
Section XML Linkbase - Arcroles

als json

2.03.02.05

Rule 2.03.02.05
Name <link:arcroleRef> @xlink:arcrole MUST NOT be used
Explanation
Introduction date 2010/06/23
Related to 4.02.004
Error message
NTA Rule True
PE Rule True
Testable True
Section XML Linkbase - Arcroles

als json

2.03.02.06

Rule 2.03.02.06
Name <link:arcroleRef> @xlink:role MUST NOT be used
Explanation
Introduction date 2010/06/23
Related to 4.02.006
Error message
NTA Rule True
PE Rule True
Testable True
Section XML Linkbase - Arcroles

als json

2.03.02.07

Rule 2.03.02.07
Name The parent and child of an arc MUST be present and valid in the DTS
Explanation
Related to GFM: 1.4.3
Error message
NTA Rule True
PE Rule True
Section XML Linkbase - Arcroles

als json

2.03.02.08

Rule 2.03.02.08
Name REMOVED The arcrole 'general-special' MUST be used with doubled concepts which are temporarily (or a dedicated arcrole which states 'synonym'?)
Explanation
Decommission date 2012/05/01
Related to 2.03.02.01
Error message
NTA Rule True
PE Rule
Section XML Linkbase - Arcroles

als json

XML Linkbase - Referenties

2.03.03.01

Rule 2.03.03.01
Name Reference resources based on XBRL defined link:parts MUST use the ref-2006-02-27.xsd schema
Explanation
Introduction date 2010/06/23
Error message
NTA Rule True
PE Rule True
References FRTA 2.1.21
Section XML Linkbase - Referenties

als json

2.03.03.02

Rule 2.03.03.02
Name A reference resource MUST have an @id
Explanation
Introduction date 2010/06/23
Error message
NTA Rule True
PE Rule True
Testable True
Section XML Linkbase - Referenties

als json

2.03.03.03

Rule 2.03.03.03
Name The @id on a reference resource MUST be unique within the DTS
Explanation
Introduction date 2010/06/23
Decommission date 2016/04/06
Related to 3.02.16.01
Error message
NTA Rule True
PE Rule
Section XML Linkbase - Referenties

als json

2.03.03.04

Rule 2.03.03.04
Name The content of a reference resource MUST be split on the appropriate link:parts
Explanation
Introduction date 2010/06/23
Error message
NTA Rule True
PE Rule True
References FRTA 2.1.19
Section XML Linkbase - Referenties

als json

2.03.03.05

Rule 2.03.03.05
Name ReferenceArcs MUST NOT contain @order.
Explanation
Introduction date 2011/04/06
Error message
NTA Rule True
PE Rule True
References XBRL2.1 3.5.3.9.5
Testable True
Section XML Linkbase - Referenties

als json

2.03.03.06

Rule 2.03.03.06
Name Dimension-domain relationships with @usable="true" MUST NOT have @targetRole.
Explanation
Error message
NTA Rule True
PE Rule True
Section XML Linkbase - Referenties

als json

2.03.03.07

Rule 2.03.03.07
Name Reference resources MUST NOT contain random internet locations. Only locations under supervision of SBR or their NT partners are allowed.
Explanation
Agreed date 2014/11/19
Error message
NTA Rule True
PE Rule
Section XML Linkbase - Referenties

als json

XML Linkbase - Presentatie

2.03.04.01

Rule 2.03.04.01
Name Nesting of non-abstract items in the presentation linkbase MUST follow the nesting of children in tuples, if present
Explanation
Introduction date 2010/06/23
Error message
NTA Rule True
PE Rule True
Section XML Linkbase - Presentatie

als json

2.03.04.02

Rule 2.03.04.02
Name REMOVED @use on presentation relationships SHOULD NOT carry the value ‘prohibited’
Explanation
Introduction date 2010/06/23
Decommission date 2011/12/02
Related to 2.03.00.10
Error message
NTA Rule True
PE Rule
Section XML Linkbase - Presentatie

als json

2.03.04.03

Rule 2.03.04.03
Name @preferredLabel on presentation relationships SHOULD NOT be used with semantically meaningfull label roles (e.g. periodStart and periodEnd)
Explanation
Introduction date 2010/06/23
Decommission date 2019/12/10
Related to Gebruik_van_preferredLabel
Error message
NTA Rule True
PE Rule
Section XML Linkbase - Presentatie

als json

2.03.04.04

Rule 2.03.04.04
Name <link:presentationArc/@order MUST be used
Explanation
Introduction date 2011/04/06
Error message
NTA Rule True
PE Rule True
References GFM 1.6.1
Testable True
Section XML Linkbase - Presentatie

als json

2.03.04.05

Rule 2.03.04.05
Name <link:presentationArc/@order> MUST be unique per parent element per linkrole, if there is more than one discovered
Explanation
Introduction date 2011/04/06
Error message
NTA Rule True
PE Rule True
References GFM 1.6.2
Section XML Linkbase - Presentatie

als json

2.03.04.06

Rule 2.03.04.06
Name If a non-abstract concept is used in several <link:presentationArc> as child element in the same linkrole, then they SHOULD be distinguished by the use of @preferredLabel. The used labels from this child MUST always be of one type (standard, DomainSpecific, IndustrySpecific or EntitySpecific).
Explanation
Introduction date 2011/11/23
Related to 2.03.04.03
Error message
References GFM 1.6.5
Section XML Linkbase - Presentatie

als json

2.03.04.07

Rule 2.03.04.07
Name Abstract concepts that are used in a presentation ELR MUST have children in the same presentation ELR.
Explanation
Introduction date 2015/12/02
Agreed date 2015/12/02
Error message
NTA Rule True
PE Rule
Section XML Linkbase - Presentatie

als json

2.03.04.08

Rule 2.03.04.08
Name Abstract concepts MUST NOT be used in a presentation ELR except for those having the sbr:presentationItem substitutiongroup.
Explanation
Introduction date 2015/12/02
Agreed date 2015/12/02
Error message
NTA Rule True
PE Rule
Section XML Linkbase - Presentatie

als json

2.03.04.09

Rule 2.03.04.09
Name tableBreakdownArc axis = "z" MUST not be used.
Explanation
Introduction date 2016/05/01
Agreed date 2016/05/01
Error message
NTA Rule True
PE Rule
Section XML Linkbase - Presentatie

als json

2.03.04.10

Rule 2.03.04.10
Name In a table, all aspects of a concept modeled in the taxonomy, except aspects of which a maximum of one value can occur, MUST be expressed in the definition of the table.
Explanation
Introduction date 2016/05/01
Agreed date 2016/05/01
Error message
NTA Rule True
PE Rule
Section XML Linkbase - Presentatie

als json

2.03.04.11

Rule 2.03.04.11
Name In a table, concepts must be added using a conceptRelationshipNode UNLESS one single concept from a p-link must be added separately
Explanation
Introduction date 2016/05/01
Agreed date 2016/05/01
Error message
NTA Rule True
PE Rule
Section XML Linkbase - Presentatie

als json

2.03.04.12

Rule 2.03.04.12
Name In a table, if more than one Sbr:domainMemberItem is modeled under a single dimensionItem, these MUST be included using a dimensionRelationshipNode.
Explanation
Introduction date 2016/05/01
Agreed date 2016/05/01
Error message
NTA Rule True
PE Rule
Section XML Linkbase - Presentatie

als json

2.03.04.13

Rule 2.03.04.13
Name In a table period information from the context MUST be included using a ruleNode
Explanation
Introduction date 2016/05/01
Agreed date 2016/05/01
Error message
NTA Rule True
PE Rule
Section XML Linkbase - Presentatie

als json

2.03.04.14

Rule 2.03.04.14
Name In a table typed dimensions MUST be added using an aspectNode.
Explanation
Introduction date 2016/05/01
Agreed date 2016/05/01
Error message
NTA Rule True
PE Rule
Section XML Linkbase - Presentatie

als json

2.03.04.15

Rule 2.03.04.15
Name A Table MUST have a default label in the local language.
Explanation
Introduction date 2016/05/01
Agreed date 2016/05/01
Error message
NTA Rule True
PE Rule
Section XML Linkbase - Presentatie

als json

2.03.04.16

Rule 2.03.04.16
Name Labels for tables MUST be included in by language and table devided separate link bases.
Explanation
Introduction date 2016/05/01
Agreed date 2016/05/01
Error message
NTA Rule True
PE Rule
Section XML Linkbase - Presentatie

als json

2.03.04.17

Rule 2.03.04.17
Name Parameter elements MUST be defined by a schema.
Explanation
Introduction date 2016/05/01
Agreed date 2016/05/01
Decommission date 2017/05/15
Error message
NTA Rule True
PE Rule
Section XML Linkbase - Presentatie

als json

2.03.04.18

Rule 2.03.04.18
Name The periodType of a concept MUST match the period filter in the table.
Explanation
Introduction date 2016/05/01
Agreed date 2016/05/01
Error message
NTA Rule True
PE Rule
Section XML Linkbase - Presentatie

als json

2.03.04.19

Rule 2.03.04.19
Name The dimensional mapping of concepts SHOULD be in accordance with the dimensional filter in the table.
Explanation
Introduction date 2016/05/01
Agreed date 2016/05/01
Error message
NTA Rule True
PE Rule
Section XML Linkbase - Presentatie

als json

2.03.04.20

Rule 2.03.04.20
Name The combination of a typedDimensionAxis and the other aspects on a concept MUST be unique in tables in one entry point.
Explanation
Introduction date 2016/05/01
Agreed date 2016/05/01
Error message
NTA Rule True
PE Rule
Section XML Linkbase - Presentatie

als json

2.03.04.21

Rule 2.03.04.21
Name Parameters MUST be requested through a fn:doc in an XML file.
Explanation
Introduction date 2016/05/01
Agreed date 2016/05/01
Decommission date 2017/05/15
Error message
NTA Rule True
PE Rule
Section XML Linkbase - Presentatie

als json

XML Linkbase - Hypercubes

2.03.05.01

Rule 2.03.05.01
Name A hypercube MUST NOT have more than one sbr:primaryDomain child in an "all" arc per linkrole
Explanation
Introduction date 2010/06/23
Error message
NTA Rule True
PE Rule
Section XML Linkbase - Hypercubes

als json

2.03.05.02

Rule 2.03.05.02
Name REMOVED A Hypercube MUST have an unique list of dimensions as relationship
Explanation
Introduction date 2010/06/23
Decommission date 2011/11/23
Related to 2.03.05.01
Error message
NTA Rule True
PE Rule
Section XML Linkbase - Hypercubes

als json

2.03.05.03

Rule 2.03.05.03
Name REMOVED A hypercube MUST have a dedicated linkrole
Explanation
Introduction date 2010/06/23
Decommission date 2011/12/02
Related to 2.02.03.05
Error message
NTA Rule True
PE Rule
Section XML Linkbase - Hypercubes

als json

2.03.05.04

Rule 2.03.05.04
Name The arcrole hypercube-dimension MUST use @targetRole to address explicit dimension content
Explanation
Introduction date 2010/06/23
Error message
NTA Rule True
PE Rule
Testable True
Section XML Linkbase - Hypercubes

als json

2.03.05.05

Rule 2.03.05.05
Name Hypercube – primary relationships MUST use ‘all’ arcroles
Explanation
Introduction date 2010/06/23
Related to 2.03.05.01
Error message
NTA Rule True
PE Rule
Testable True
Section XML Linkbase - Hypercubes

als json

2.03.05.06

Rule 2.03.05.06
Name A hypercube - primary relationship MUST use @xbrldt:contextElement ="scenario"
Explanation
Introduction date 2010/06/23
Error message
NTA Rule True
PE Rule
Testable
Section XML Linkbase - Hypercubes

als json

2.03.05.07

Rule 2.03.05.07
Name The arcrole hypercube-dimension MUST NOT use @targetRole with a typed dimension
Explanation
Introduction date 2010/06/23
Error message
NTA Rule True
PE Rule
Testable True
Section XML Linkbase - Hypercubes

als json

2.03.05.08

Rule 2.03.05.08
Name Primaries in an entry point that have an "all" arc role, MUST have hypercubes with hypercube-dimension relationships OR have hypercubes that do not have these relationships (not both).
Explanation
Introduction date 2013/05/15
Agreed date 2012/12/05
Decommission date 2022/02/16
Error message
NTA Rule True
PE Rule True
Testable
Section XML Linkbase - Hypercubes

als json

2.03.05.09

Rule 2.03.05.09
Name Primaries in an entrypoint MUST all be dimensionally valid or non-dimensionally valid (not both)
Explanation
Introduction date 2013/05/15
Error message
NTA Rule True
PE Rule
Testable
Section XML Linkbase - Hypercubes

als json

2.03.05.10

Rule 2.03.05.10
Name
Explanation
Error message
NTA Rule
PE Rule True
Section XML Linkbase - Hypercubes

als json

XML Linkbase - Dimensies

2.03.06.01

Rule 2.03.06.01
Name The relationships that configure the dimension SHOULD NOT be regarded as the presentation
Explanation
Introduction date 2010/06/23
Error message
NTA Rule True
PE Rule True
Testable True
Section XML Linkbase - Dimensies

als json

2.03.06.02

Rule 2.03.06.02
Name A dimension MUST have an unique set of domain members
Explanation
Introduction date 2010/06/23
Error message
NTA Rule True
PE Rule True
Section XML Linkbase - Dimensies

als json

2.03.06.03

Rule 2.03.06.03
Name Dimension-domain relationships with @usable="false" MUST use @targetRole
Explanation
Introduction date 2010/06/23
Error message
NTA Rule True
PE Rule True
Testable True
Section XML Linkbase - Dimensies

als json

2.03.06.04

Rule 2.03.06.04
Name The arcrole all (has hypercube) MUST contain @xbrldt:closed="true"
Explanation
Introduction date 2010/06/23
Error message
NTA Rule True
PE Rule
Testable True
Section XML Linkbase - Dimensies

als json

2.03.06.05

Rule 2.03.06.05
Name The arcrole dimension-default MUST NOT be used
Explanation
Introduction date 2011/04/06
Error message
NTA Rule True
PE Rule
Testable True
Section XML Linkbase - Dimensies

als json

2.03.06.06

Rule 2.03.06.06
Name
Explanation
Error message
NTA Rule
PE Rule True
Section XML Linkbase - Dimensies

als json

2.03.06.07

Rule 2.03.06.07
Name
Explanation
Error message
NTA Rule
PE Rule True
Section XML Linkbase - Dimensies

als json

XML Linkbase - Domeinen en Domeinleden

2.03.07.01

Rule 2.03.07.01
Name REMOVED; Non-abstract items that are used as domain member MUST be nested under an item in the sbr:primaryDomainItem substitutionGroup
Explanation
Introduction date 2010/06/23
Decommission date 2011/10/01
Related to 2.03.07.02
Error message
NTA Rule True
PE Rule
Section XML Linkbase - Domeinen en Domeinleden

als json

2.03.07.02

Rule 2.03.07.02
Name REMOVED; Abstract items used as domain member MUST be nested under an abstract item that is a domain
Explanation
Introduction date 2010/06/23
Related to 2.03.07.01
Error message
NTA Rule True
PE Rule
Section XML Linkbase - Domeinen en Domeinleden

als json

2.03.07.03

Rule 2.03.07.03
Name Domain Members MUST NOT be nested amongst themselves with an arcrole domain-member, unless a table linkbase is present in the DTS.
Explanation
Introduction date 2010/06/23
Error message
NTA Rule True
PE Rule True
Section XML Linkbase - Domeinen en Domeinleden

als json

2.03.07.04

Rule 2.03.07.04
Name Domain-member relationships MUST be nested in a Dutch Taxonomy partner owned linkrole IF this linkrole is being addressed in a dimension-domain/@targetRole
Explanation
Introduction date 2010/06/23
Error message
Section XML Linkbase - Domeinen en Domeinleden

als json

2.03.07.05

Rule 2.03.07.05
Name Dimension-domain/@usable="false" MUST be used if the child in the relationship is in the sbr:domainItem substitutionGroup
Explanation
Introduction date 2010/06/23
Related to 2.03.06.03
Error message
NTA Rule True
PE Rule True
Section XML Linkbase - Domeinen en Domeinleden

als json

2.03.07.06

Rule 2.03.07.06
Name
Explanation
Related to 2.03.07.04
Error message
NTA Rule
PE Rule True
Section XML Linkbase - Domeinen en Domeinleden

als json

XML Linkbase - Labels

2.03.08.01

Rule 2.03.08.01
Name The content of @xml:lang for Dutch MUST be ‘nl’
Explanation
Introduction date 2010/06/23
Error message
NTA Rule True
PE Rule True
References SBR Australië: 110 NA
Testable True
Section XML Linkbase - Labels

als json

2.03.08.02

Rule 2.03.08.02
Name The content of @xml:lang for English MUST be ‘en’
Explanation
Introduction date 2010/06/23
Error message
NTA Rule True
PE Rule True
References SBR Australië: 111 SA
Testable True
Section XML Linkbase - Labels

als json

2.03.08.03

Rule 2.03.08.03
Name Label roles that carry semantic meaning SHOULD NOT be used
Explanation
Introduction date 2010/06/23
Decommission date 2019/12/10
Related to Gebruik_van_preferredLabel
Error message
NTA Rule True
PE Rule True
Section XML Linkbase - Labels

als json

2.03.08.04

Rule 2.03.08.04
Name Dutch Taxonomy Partners that use label roles with semantic meaning MUST provide an appropriate warning in the 'Business Rules' documentation
Explanation
Introduction date 2010/06/23
Related to 2.03.08.03
Error message
NTA Rule True
PE Rule True
Section XML Linkbase - Labels

als json

2.03.08.05

Rule 2.03.08.05
Name All Dutch Taxonomy used lable roles MUST appear in the local language
Explanation
Introduction date 2011/04/06
Error message
Section XML Linkbase - Labels

als json

2.03.08.06

Rule 2.03.08.06
Name Label resource in @xlink:role documentation MUST NOT be contradictory to standard references made on the linked concept and v.v.
Explanation
Introduction date 2011/04/06
Error message
NTA Rule True
PE Rule True
Section XML Linkbase - Labels

als json

2.03.08.07

Rule 2.03.08.07
Name The content of <link:label> MUST be regarded as xs:tokenizedString
Explanation
Introduction date 2011/04/06
Related to 3.02.07.14
Error message
NTA Rule True
PE Rule True
Testable True
Section XML Linkbase - Labels

als json

2.03.08.08

Rule 2.03.08.08
Name LabelArcs MUST NOT contain @order.
Explanation
Introduction date 2011/11/23
Related to 2.03.03.05
Error message
NTA Rule True
PE Rule True
References XBRL2.1 3.5.3.9.5
Testable True
Section XML Linkbase - Labels

als json

2.03.08.09

Rule 2.03.08.09
Name REMOVED Elementen MUST NOT have label resources carrying equal linkrole/arcrole/role/xml:lang values
Explanation
Introduction date 2011/11/23
Decommission date 2011/12/02
Related to 2.02.01.05
Error message
NTA Rule True
PE Rule
Section XML Linkbase - Labels

als json

2.03.08.10

Rule 2.03.08.10
Name The content of <link:label> MUST NOT contain any rendering hints.
Explanation
Agreed date 2014/06/04
Error message
NTA Rule True
PE Rule True
Testable True
Section XML Linkbase - Labels

als json

2.03.08.11

Rule 2.03.08.11
Name A label resource MUST have an @id
Explanation
Introduction date 2015/12/02
Agreed date 2015/12/02
Error message
NTA Rule True
PE Rule True
Testable True
Section XML Linkbase - Labels

als json

2.03.08.12

Rule 2.03.08.12
Name An industrySpecific, domainSpecific en entitySpecific label MUST NOT be inconsistent with the semantics of a concept.
Explanation
Introduction date 2016/05/01
Error message
NTA Rule True
PE Rule
Section XML Linkbase - Labels

als json

2.03.08.13

Rule 2.03.08.13
Name
Explanation
Error message
NTA Rule True
PE Rule True
Testable True
Section XML Linkbase - Labels

als json

2.03.08.14

Rule 2.03.08.14
Name
Explanation
Error message
NTA Rule True
PE Rule True
Testable True
Section XML Linkbase - Labels

als json

2.03.08.15

Rule 2.03.08.15
Name
Explanation
Error message
NTA Rule
PE Rule True
Section XML Linkbase - Labels

als json

2.03.08.16

Rule 2.03.08.16
Name
Explanation
Error message
NTA Rule
PE Rule True
Section XML Linkbase - Labels

als json

2.03.08.17

Rule 2.03.08.17
Name
Explanation
Error message
NTA Rule
PE Rule True
Section XML Linkbase - Labels

als json

XML Linkbase - Controle regels

2.03.09.01

Rule 2.03.09.01
Name Calculation linkbases MUST NOT be used
Explanation
Introduction date 2010/06/23
Error message
NTA Rule True
PE Rule True
Testable True
Section XML Linkbase - Controle regels

als json

2.03.09.02

Rule 2.03.09.02
Name <variable:factVariable> MUST contain a unique combination of attributes and filters.
Explanation
Introduction date 2016/05/01
Error message
Section XML Linkbase - Controle regels

als json

2.03.09.03

Rule 2.03.09.03
Name <formula:formula> MUST NOT be used
Explanation
Introduction date 2010/06/23
Error message
NTA Rule True
PE Rule True
Testable True
Section XML Linkbase - Controle regels

als json

2.03.09.04

Rule 2.03.09.04
Name With XBRL Formula assertions the result "false" MUST be used for an error situation
Explanation
Introduction date 2016/05/01
Error message
NTA Rule True
PE Rule
Section XML Linkbase - Controle regels

als json

2.03.09.05

Rule 2.03.09.05
Name FactVariables with @fallbackValue MUST have a check on the existence of the fact in messages that contain fact aspects.
Explanation
Introduction date 2016/05/01
Error message
NTA Rule True
PE Rule
Section XML Linkbase - Controle regels

als json

2.03.09.06

Rule 2.03.09.06
Name Assertions that don't fire MUST NOT exist
Explanation
Decommission date 2016/05/01
Error message
NTA Rule True
PE Rule
Section XML Linkbase - Controle regels

als json

2.03.09.07

Rule 2.03.09.07
Name Formula messages labels and references MUST be in separate linkbases, per language
Explanation
Introduction date 2016/05/01
Error message
Section XML Linkbase - Controle regels

als json

2.03.09.08

Rule 2.03.09.08
Name Assertions MUST have a generic label or a generic reference to documentation
Explanation
Introduction date 2016/05/01
Error message
Section XML Linkbase - Controle regels

als json

2.03.09.09

Rule 2.03.09.09
Name <formula:consistencyAssertion> MAY NOT be used.
Explanation
Introduction date 2016/05/01
Error message
NTA Rule True
PE Rule
Testable True
Section XML Linkbase - Controle regels

als json

2.03.09.10

Rule 2.03.09.10
Name An assertion MAY NOT have a satisfied message, through a http://xbrl.org/arcrole/2010/assertion-satisfied-message arc.
Explanation
Introduction date 2016/05/01
Error message
NTA Rule True
PE Rule
Testable
Section XML Linkbase - Controle regels

als json

2.03.09.11

Rule 2.03.09.11
Name Each assertion MUST have an unsatisfied message, through a http://xbrl.org/arcrole/2010/assertion-unsatisfied-message arc.
Explanation
Introduction date 2016/05/01
Error message
NTA Rule True
PE Rule
Section XML Linkbase - Controle regels

als json

2.03.09.12

Rule 2.03.09.12
Name A message MUST consist of the label and additional comfort information. Comfort information consists of: * per fact variabele and general variabele for a fact: ** Concept name, contextRef, unitRef, value, optional default value * per general variabele for context or unit: ** @id
Explanation
Introduction date 2016/05/01
Error message
NTA Rule True
PE Rule
Section XML Linkbase - Controle regels

als json

2.03.09.13

Rule 2.03.09.13
Name A message SHOULD be formulated according to the RuleSpeak rules.
Explanation
Introduction date 2016/05/01
Error message
NTA Rule True
PE Rule
Section XML Linkbase - Controle regels

als json

2.03.09.14

Rule 2.03.09.14
Name Custom functions MUST NOT occur. Use the XII CFI, or request the function to be added to the CFI.
Explanation
Introduction date 2016/05/01
Error message
NTA Rule True
PE Rule
Section XML Linkbase - Controle regels

als json

2.03.09.15

Rule 2.03.09.15
Name Multi instance processing MUST NOT occur.
Explanation
Introduction date 2016/05/01
Error message
NTA Rule True
PE Rule
Section XML Linkbase - Controle regels

als json

2.03.09.16

Rule 2.03.09.16
Name Chaining MUST NOT occur.
Explanation
Introduction date 2016/05/01
Error message
NTA Rule True
PE Rule
Section XML Linkbase - Controle regels

als json

2.03.09.17

Rule 2.03.09.17
Name Fallback values MAY NOT clash with the evaluation in the assertion (for example true/false versus a 0)
Explanation
Agreed date 2016/05/01
Error message
NTA Rule True
PE Rule
Section XML Linkbase - Controle regels

als json

2.03.09.18

Rule 2.03.09.18
Name Formula and message linkbases MUST be discovered in the de DTS in an entrypoint.
Explanation
Introduction date 2016/05/01
Error message
NTA Rule True
PE Rule
Section XML Linkbase - Controle regels

als json

2.03.09.19

Rule 2.03.09.19
Name An assertion MUST use an http://xbrl.org/arcrole/2016/assertion-unsatisfied-severity arc to indicate the severity of the result
Explanation
Introduction date 2016/05/01
Error message
NTA Rule True
PE Rule
Section XML Linkbase - Controle regels

als json

2.03.09.20

Rule 2.03.09.20
Name
Explanation
Related to 2.03.09.02
Error message
NTA Rule
PE Rule True
Section XML Linkbase - Controle regels

als json

2.03.09.21

Rule 2.03.09.21
Name
Explanation
Related to 2.03.09.07
Error message
NTA Rule
PE Rule True
Section XML Linkbase - Controle regels

als json

2.03.09.22

Rule 2.03.09.22
Name
Explanation
Related to 2.03.09.08
Error message
NTA Rule
PE Rule True
Section XML Linkbase - Controle regels

als json

2.03.09.23

Rule 2.03.09.23
Name
Explanation
Error message
NTA Rule
PE Rule True
Section XML Linkbase - Controle regels

als json

XML Linkbase - Overig

2.03.10.01

Rule 2.03.10.01
Name @xlink:actuate MUST NOT be used
Explanation
Introduction date 2010/06/23
Related to 4.02.003
Error message
NTA Rule True
PE Rule True
Testable True
Section XML Linkbase - Overig

als json

2.03.10.02

Rule 2.03.10.02
Name @xlink:show MUST NOT be used
Explanation
Introduction date 2010/06/23
Related to 4.02.007
Error message
NTA Rule True
PE Rule True
Testable True
Section XML Linkbase - Overig

als json

2.03.10.03

Rule 2.03.10.03
Name @xlink:title MUST NOT be used
Explanation
Introduction date 2010/06/23
Related to 4.02.008
Error message
NTA Rule True
PE Rule True
Testable True
Section XML Linkbase - Overig

als json

2.03.10.04

Rule 2.03.10.04
Name link:linkbase/@id MUST NOT be used
Explanation
Introduction date 2010/06/23
Error message
NTA Rule True
PE Rule True
Testable True
Section XML Linkbase - Overig

als json

2.03.10.05

Rule 2.03.10.05
Name link:linkbase/@xsi:nil MUST NOT be used
Explanation
Introduction date 2010/06/23
Error message
NTA Rule True
PE Rule True
Testable True
Section XML Linkbase - Overig

als json

2.03.10.06

Rule 2.03.10.06
Name link:linkbase/@xsi:noNamespaceSchemaLocation MUST NOT be used
Explanation
Introduction date 2010/06/23
Error message
NTA Rule True
PE Rule True
Testable True
Section XML Linkbase - Overig

als json

2.03.10.07

Rule 2.03.10.07
Name link:linkbase/@xsi:type MUST NOT be used
Explanation
Introduction date 2010/06/23
Error message
NTA Rule True
PE Rule True
Testable True
Section XML Linkbase - Overig

als json

2.03.10.08

Rule 2.03.10.08
Name link:loc/@xlink:role MUST NOT be used
Explanation
Introduction date 2010/06/23
Error message
NTA Rule True
PE Rule True
Testable True
Section XML Linkbase - Overig

als json

2.03.10.09

Rule 2.03.10.09
Name link:roleRef/@xlink:arcrole MUST NOT be used
Explanation
Introduction date 2010/06/23
Error message
NTA Rule True
PE Rule True
Testable True
Section XML Linkbase - Overig

als json

2.03.10.10

Rule 2.03.10.10
Name link:roleRef/@xlink:role MUST NOT be used
Explanation
Introduction date 2010/06/23
Error message
NTA Rule True
PE Rule True
Testable True
Section XML Linkbase - Overig

als json

2.03.10.11

Rule 2.03.10.11
Name link:roleType/@id MUST be used
Explanation
Introduction date 2010/06/23
Error message
NTA Rule True
PE Rule True
Testable True
Section XML Linkbase - Overig

als json

2.03.10.12

Rule 2.03.10.12
Name link:documentation MUST NOT be used
Explanation
Introduction date 2010/06/23
Error message
NTA Rule True
PE Rule True
Testable True
Section XML Linkbase - Overig

als json

2.03.10.13

Rule 2.03.10.13
Name A <link:resource> with @type="extended", MUST have @xlink:role
Explanation
Introduction date 2011/04/06
Error message
NTA Rule True
PE Rule True
References GFM 1.4.4
Section XML Linkbase - Overig

als json

2.03.10.14

Rule 2.03.10.14
Name link:resource/@xlink:role MUST have XII or SBR content
Explanation
Introduction date 2011/04/06
Related to 2.03.10.13
Error message
NTA Rule True
PE Rule True
Section XML Linkbase - Overig

als json

2.03.10.15

Rule 2.03.10.15
Name
Explanation
Error message
NTA Rule
PE Rule True
Section XML Linkbase - Overig

als json

XBRL Instance - Basis

2.04.00.01

Rule 2.04.00.01
Name Instances MUST NOT contain extensions on the Dutch Taxonomy DTS entrypoint
Explanation
Introduction date 2010/06/23
Decommission date 2011/01/01
Error message
NTA Rule True
PE Rule
Section XBRL Instance - Basis

als json

2.04.00.02

Rule 2.04.00.02
Name Instances SHOULD NOT contain footnote linkbases
Explanation
Introduction date 2010/06/23
Decommission date 2011/01/01
Error message
NTA Rule True
PE Rule
Section XBRL Instance - Basis

als json

2.04.00.03

Rule 2.04.00.03
Name Tuple children MUST NOT contain deviating @contextRef values in one 'set' of the tuple in the instances EXCEPT root tuples
Explanation
Introduction date 2010/06/23
Decommission date 2011/01/01
Related to 2.02.02.06
Error message
NTA Rule True
PE Rule
Section XBRL Instance - Basis

als json

2.04.00.04

Rule 2.04.00.04
Name A fact MUST have its concept present in a presentation linkbase discovered by the DTS entrypoint
Explanation
Introduction date 2010/06/23
Decommission date 2011/01/01
Error message
NTA Rule True
PE Rule
Section XBRL Instance - Basis

als json

2.04.00.05

Rule 2.04.00.05
Name Instance files MUST have an unique name with the recipient
Explanation
Decommission date 2011/01/01
Error message
NTA Rule True
PE Rule
Section XBRL Instance - Basis

als json

2.04.00.06

Rule 2.04.00.06
Name Instances MUST publish a 'default' language with xbrli:xbrl/@xml:lang.
Explanation
Decommission date 2011/01/01
Error message
NTA Rule True
PE Rule
Section XBRL Instance - Basis

als json

2.04.00.07

Rule 2.04.00.07
Name Instances MUST use the standardized namespace prefixes (see 3.02.04.04)
Explanation
Decommission date 2011/01/01
Error message
NTA Rule True
PE Rule
Section XBRL Instance - Basis

als json

2.04.00.08

Rule 2.04.00.08
Name Instance files MUST have the .xbrl extension
Explanation
Decommission date 2011/01/01
Error message
NTA Rule True
PE Rule
Section XBRL Instance - Basis

als json

2.04.00.09

Rule 2.04.00.09
Name
Explanation
Error message
NTA Rule
PE Rule True
Section XBRL Instance - Basis

als json

XBRL Instance - xbrli:context

2.04.01.01

Rule 2.04.01.01
Name Instances MUST NOT contain multiple contexts where the content is identical
Explanation
Decommission date 2011/01/01
Error message
NTA Rule True
PE Rule
Section XBRL Instance - xbrli:context

als json

2.04.01.02

Rule 2.04.01.02
Name Instances MUST NOT contain unused contexts
Explanation
Decommission date 2011/01/01
Error message
NTA Rule True
PE Rule
Section XBRL Instance - xbrli:context

als json

2.04.01.03

Rule 2.04.01.03
Name Instances MUST NOT contain contexts where xbrli:periodEnd from one context is identical to xbrli:periodStart from the other context
Explanation
Decommission date 2011/01/01
Error message
NTA Rule True
PE Rule
Section XBRL Instance - xbrli:context

als json

2.04.01.04

Rule 2.04.01.04
Name Contexts MUST NOT contain dates which represent time
Explanation
Decommission date 2011/01/01
Error message
NTA Rule True
PE Rule
Section XBRL Instance - xbrli:context

als json

XBRL Instance - xbrli:unit

2.04.02.01

Rule 2.04.02.01
Name Instances MUST NOT contain multiple units where the content is identical
Explanation
Decommission date 2011/01/01
Error message
NTA Rule True
PE Rule
Section XBRL Instance - xbrli:unit

als json

2.04.02.02

Rule 2.04.02.02
Name Instances MUST NOT contain unused contexts (XII-FRIS 2.7.2)
Explanation
Decommission date 2011/01/01
Error message
NTA Rule True
PE Rule
Section XBRL Instance - xbrli:unit

als json

XBRL Instance - facts

2.04.03.01

Rule 2.04.03.01
Name Facts MUST NOT be present more than once (more than once as in: identical item, context reference, unit reference)
Explanation
Decommission date 2011/01/01
Error message
NTA Rule True
PE Rule
Section XBRL Instance - facts

als json

2.04.03.02

Rule 2.04.03.02
Name Facts MUST report non-numerically facts in the 'default' language (@xml:lang), other languages are not forbidden
Explanation
Decommission date 2011/01/01
Error message
NTA Rule True
PE Rule
Section XBRL Instance - facts

als json

2.04.03.03

Rule 2.04.03.03
Name Facts MUST NOT use @precision
Explanation
Decommission date 2011/01/01
Error message
NTA Rule True
PE Rule
Section XBRL Instance - facts

als json

2.04.03.04

Rule 2.04.03.04
Name Elements which are modelled as tuple children MUST NOT be reported on root level
Explanation
Decommission date 2011/01/01
Error message
NTA Rule True
PE Rule
Section XBRL Instance - facts

als json

2.04.03.05

Rule 2.04.03.05
Name Tuple children from the same tuple occurrence MUST NOT refer contexts that have different content in <xbrli:entity>, <xbrli:segment> or <xbrli:scenario>
Explanation
Introduction date 2011/05/04
Decommission date 2011/01/01
Related to 2.02.02.06, 2.02.02.29
Error message
NTA Rule True
PE Rule
Section XBRL Instance - facts

als json

XBRL Instance - footnotes

2.04.04.01

Rule 2.04.04.01
Name Instances MUST NOT contain footnotes or links
Explanation
Decommission date 2011/01/01
Error message
Section XBRL Instance - footnotes

als json

Naamgeving - Bestanden en directories

3.02.01.01

Rule 3.02.01.01
Name Folder names MUST be English (UK spelling)
Explanation
Introduction date 2010/11/17
Error message
NTA Rule True
PE Rule
Section Naamgeving - Bestanden en directories

als json

3.02.01.02

Rule 3.02.01.02
Name Folder names MUST be lower case and MUST NOT contain spaces.
Explanation
Introduction date 2010/11/17
Error message
NTA Rule True
PE Rule
Testable True
Section Naamgeving - Bestanden en directories

als json

3.02.01.03

Rule 3.02.01.03
Name Folder names MUST contain less than 15 characters
Explanation
Introduction date 2011/09/28
Error message
NTA Rule True
PE Rule
Testable True
Section Naamgeving - Bestanden en directories

als json

3.02.01.04

Rule 3.02.01.04
Name Folders that are part of the Dutch Taxonomy MUST fit the structure of table F
Explanation
Introduction date 2010/11/17
Related to NT_Naamgeving#Tabel_F:_Directorie_namen
Error message
NTA Rule True
PE Rule
Testable True
Section Naamgeving - Bestanden en directories

als json

3.02.01.05

Rule 3.02.01.05
Name File names MUST be lower case
Explanation
Introduction date 2010/11/17
Error message
NTA Rule True
PE Rule
Testable True
Section Naamgeving - Bestanden en directories

als json

3.02.01.06

Rule 3.02.01.06
Name File names MUST be indicative about their content
Explanation
Introduction date 2010/11/17
Error message
NTA Rule True
PE Rule
Section Naamgeving - Bestanden en directories

als json

3.02.01.07

Rule 3.02.01.07
Name The indicative part of XML schema file names MUST be in the local preferred language
Explanation
Introduction date 2010/11/17
Error message
Section Naamgeving - Bestanden en directories

als json

3.02.01.08

Rule 3.02.01.08
Name Linkbase file names MAY be in English or the local preferred language
Explanation
Introduction date 2010/11/17
Error message
NTA Rule True
PE Rule
Section Naamgeving - Bestanden en directories

als json

3.02.01.09

Rule 3.02.01.09
Name Linkbase content, as defined by XBRL 2.1 (label, reference, presentation, definition, calculation) and modules (formula and tables), MUST be expressed in the linkbase file name conform table A
Explanation
Introduction date 2010/11/17
Related to NT_Naamgeving#Tabel_A:_Linkbase_bestandsnaam_extensies
Error message
NTA Rule True
PE Rule True
Testable True
Section Naamgeving - Bestanden en directories

als json

3.02.01.10

Rule 3.02.01.10
Name Linkbase content as specified in the Generic Link 1.0 specification, MUST be expressed in the linkbase file name conform table B
Explanation
Related to NT_Naamgeving#Tabel_B:_Generic_Linkbase_bestandsnaam_extensies
Error message
NTA Rule True
PE Rule True
Testable True
Section Naamgeving - Bestanden en directories

als json

3.02.01.11

Rule 3.02.01.11
Name Linkroles used in a linkbase MAY be expressed in the linkbase file name
Explanation
Introduction date 2010/11/17
Related to NT_Naamgeving#Met_.28resource.29_role_vermelding
Error message
NTA Rule True
PE Rule
Section Naamgeving - Bestanden en directories

als json

3.02.01.12

Rule 3.02.01.12
Name Arcroles used in a linkbase MAY be expressed in the linkbase file name
Explanation
Introduction date 2010/11/17
Related to NT_Naamgeving#Met_arcrole_vermelding
Error message
NTA Rule True
PE Rule
Section Naamgeving - Bestanden en directories

als json

3.02.01.14

Rule 3.02.01.14
Name Filenames MUST start with the Dutch Taxonomy partner assigned code followed by a hyphen
Explanation
Introduction date 2013/05/15
Error message
NTA Rule True
PE Rule
Section Naamgeving - Bestanden en directories

als json

3.02.01.15

Rule 3.02.01.15
Name
Explanation
Related to 3.02.01.07
Error message
NTA Rule
PE Rule True
Section Naamgeving - Bestanden en directories

als json

Naamgeving - NT Partners

3.02.02.01

Rule 3.02.02.01
Name Each Dutch Taxonomy domain MUST use the assigned code conform table C
Explanation
Introduction date 2010/11/17
Related to 3.02.01.14, NT_Naamgeving#Tabel_C:_NT_Partij_afkortingen_voor_gebruik_in_XML
Error message
NTA Rule True
PE Rule
Section Naamgeving - NT Partners

als json

Naamgeving - Namespace URI

3.02.03.01

Rule 3.02.03.01
Name xs:schema/@targetNamespace content MUST be unique within the Dutch Taxonomy
Explanation
Introduction date 2010/11/17
Error message
NTA Rule True
PE Rule True
References GFM2.0: 1.3.3
Section Naamgeving - Namespace URI

als json

3.02.03.02

Rule 3.02.03.02
Name xs:schema/@targetNamespace components MUST be separated by the slash (/) sign
Explanation
Introduction date 2010/11/17
Error message
NTA Rule True
PE Rule
Testable True
Section Naamgeving - Namespace URI

als json

3.02.03.03

Rule 3.02.03.03
Name xs:schema/@targetNamespace MUST NOT be longer than 255 characters
Explanation
Introduction date 2010/11/17
Error message
NTA Rule True
PE Rule True
References GFM2.0: 1.3.33
Testable True
Section Naamgeving - Namespace URI

als json

3.02.03.04

Rule 3.02.03.04
Name xs:schema/@targetNamespace MUST use only a-z0-9_-/.: characters
Explanation
Introduction date 2010/11/17
Error message
NTA Rule True
PE Rule True
Testable True
Section Naamgeving - Namespace URI

als json

3.02.03.05

Rule 3.02.03.05
Name xs:schema/@targetNamespace MUST start with "http://www.nltaxonomie.nl"
Explanation
Introduction date 2010/11/17
Error message
NTA Rule True
PE Rule
Testable True
Section Naamgeving - Namespace URI

als json

3.02.03.06

Rule 3.02.03.06
Name xs:schema/@targetNamespace MUST contain components: http://www.nltaxonomie.nl / {folder path} / {schema name} / {year}. In the order generic - specific.
Explanation
Introduction date 2012/05/01
Error message
NTA Rule True
PE Rule
Testable True
Section Naamgeving - Namespace URI

als json

3.02.03.07

Rule 3.02.03.07
Name
Explanation
Related to 3.02.03.05
Error message
NTA Rule
PE Rule True
Section Naamgeving - Namespace URI

als json

Naamgeving - Namespace prefix

3.02.04.01

Rule 3.02.04.01
Name xs:schema/@targetNamespace MUST have a prefix
Explanation
Introduction date 2010/11/17
Error message
NTA Rule True
PE Rule True
References GFM2.0: 1.3.7
Testable True
Section Naamgeving - Namespace prefix

als json

3.02.04.02

Rule 3.02.04.02
Name Namespace prefix" MUST be unique within the Dutch Taxonomy
Explanation
Introduction date 2010/11/17
Error message
NTA Rule True
PE Rule True
Section Naamgeving - Namespace prefix

als json

3.02.04.03

Rule 3.02.04.03
Name Namespace prefix" that are reserved by organizations for international specifications (e.g.. W3X and XII), MUST NOT be redefined
Explanation
Introduction date 2010/11/17
Error message
NTA Rule True
PE Rule True
References [http://www.xbrl.org/Specification/XBRL-RECOMMENDATION-2003-12-31+Corrected-Errata-2008-07-02.htm#_1.6 XBRL 2.1]
Section Naamgeving - Namespace prefix

als json

3.02.04.04

Rule 3.02.04.04
Name The assigned namespace prefix for the schema that declares the its targetnamespace, MUST be adhired by all other Dutch Taxonomy schema"s
Explanation
Introduction date 2010/11/17
Error message
NTA Rule True
PE Rule True
Section Naamgeving - Namespace prefix

als json

3.02.04.05

Rule 3.02.04.05
Name Dutch Taxonomy namespace prefix' MUST start with the abbreviation that is assigned to each Dutch Taxonomy partner conform table C, followed by a hyphen, followed by a range of characters from {a-z, -, 0-9}
Explanation
Introduction date 2010/11/17
Related to NT_Naamgeving#Tabel_C:_NT_Partij_afkortingen_voor_gebruik_in_XML
Error message
NTA Rule True
PE Rule True
Testable True
Section Naamgeving - Namespace prefix

als json

3.02.04.06

Rule 3.02.04.06
Name Namespace prefix' SHOULD not exceed 20 characters
Explanation
Introduction date 2010/11/17
Error message
NTA Rule True
PE Rule True
Testable True
Section Naamgeving - Namespace prefix

als json

3.02.04.07

Rule 3.02.04.07
Name A namespace declared by organizations that create international specifications MUST follow the assigned prefix conform table D
Explanation
Introduction date 2010/11/17
Related to NT_Naamgeving#Tabel_D:_Gereserveerde_namespaces_en_prefixes
Error message
NTA Rule True
PE Rule True
References GFM2.0: 1.3.2
Testable True
Section Naamgeving - Namespace prefix

als json

Naamgeving - Element @name

3.02.05.01

Rule 3.02.05.01
Name Concept names MUST be in the English language (UK spelling)
Explanation
Introduction date 2010/11/17
Error message
NTA Rule True
PE Rule True
Section Naamgeving - Element @name

als json

3.02.05.02

Rule 3.02.05.02
Name Concept names MUST use upper camelcase
Explanation
Introduction date 2010/11/17
Error message
NTA Rule True
PE Rule True
References FRTA 2.1.4
Testable True
Section Naamgeving - Element @name

als json

3.02.05.03

Rule 3.02.05.03
Name Concept names MUST be self explanatory
Explanation
Introduction date 2011/09/28
Error message
NTA Rule True
PE Rule True
Section Naamgeving - Element @name

als json

3.02.05.04

Rule 3.02.05.04
Name Concept names MUST use only a-zA-Z0-9_- characters
Explanation
Introduction date 2010/11/17
Error message
NTA Rule True
PE Rule True
Testable True
Section Naamgeving - Element @name

als json

3.02.05.05

Rule 3.02.05.05
Name Concept names MUST NOT have interpunctuation and abbreviations, complete expression is needed with the EXCEPTION of abbreviations that are part of general accepted vocabulary of which everybody (everybody meaning: parties involved in working with the Dutch Taxonomy) should know the meaning
Explanation
Introduction date 2010/11/17
Error message
NTA Rule True
PE Rule True
Section Naamgeving - Element @name

als json

3.02.05.06

Rule 3.02.05.06
Name Concept naming order MUST adhere to placing the main subject first followed by lesser subject(s) and/or specification(s)
Explanation
Introduction date 2010/11/17
Error message
NTA Rule True
PE Rule True
Section Naamgeving - Element @name

als json

3.02.05.07

Rule 3.02.05.07
Name ADVICE: Concept names MUST NOT refer to periods in time, units or reporting entities EXCEPT for abstract concepts
Explanation
Introduction date 2012/05/01
Error message
References FRTA1.0: 2.1.2 FRTA1.0: 2.2.2 GFM2.0: 2.3.6
Section Naamgeving - Element @name

als json

3.02.05.08

Rule 3.02.05.08
Name Concept names MUST NOT contain any 'serial' references
Explanation
Introduction date 2010/11/17
Error message
NTA Rule True
PE Rule True
References FRTA 2.3.3
Section Naamgeving - Element @name

als json

3.02.05.09

Rule 3.02.05.09
Name Concept names MUST NOT express datatypes only
Explanation
Introduction date 2010/11/17
Error message
NTA Rule True
PE Rule True
Section Naamgeving - Element @name

als json

3.02.05.10

Rule 3.02.05.10
Name REMOVED; Concept names MUST NOT restate the name of their parent tuple
Explanation
Decommission date 2011/09/28
Error message
NTA Rule True
PE Rule True
Section Naamgeving - Element @name

als json

3.02.05.11

Rule 3.02.05.11
Name REMOVED Concepts in de substitutionGroup sbr:domainMemberItem MUST have the suffix 'Member'
Explanation
Introduction date 2012/01/01
Decommission date 2013/05/15
Error message
NTA Rule True
PE Rule True
Section Naamgeving - Element @name

als json

3.02.05.12

Rule 3.02.05.12
Name REMOVED Concepts in de substitutionGroup sbr:domainItem MUST have the suffix 'Domain'
Explanation
Introduction date 2012/01/01
Decommission date 2013/05/15
Error message
NTA Rule True
PE Rule True
Section Naamgeving - Element @name

als json

3.02.05.13

Rule 3.02.05.13
Name REMOVED Concepts in the substitutionGroup xbrldt:dimensionItem MUST have the suffix 'Axis' if they represent an explicit dimension
Explanation
Introduction date 2012/01/01
Decommission date 2013/05/15
Error message
NTA Rule True
PE Rule True
References GFM2.0: 1.3.25
Section Naamgeving - Element @name

als json

3.02.05.14

Rule 3.02.05.14
Name REMOVED Concepts in the substitutionGroup xbrldt:dimensionItem MUST have the suffix 'TypedAxis' if they represent a typed dimension
Explanation
Introduction date 2012/01/01
Decommission date 2013/05/15
Error message
NTA Rule True
PE Rule True
Section Naamgeving - Element @name

als json

3.02.05.15

Rule 3.02.05.15
Name REMOVED Concepts in the substitutionGroup xbrldt:hypercubeItem MUST have the suffix 'Table'
Explanation
Introduction date 2012/01/01
Decommission date 2013/05/15
Error message
NTA Rule True
PE Rule True
References GFM2.0: 1.3.26
Section Naamgeving - Element @name

als json

3.02.05.16

Rule 3.02.05.16
Name REMOVED Concepts in de substitutionGroup sbr:presentationItem MUST have the suffix 'Title'
Explanation
Introduction date 2010/11/17
Decommission date 2013/05/01
Error message
NTA Rule True
PE Rule True
Section Naamgeving - Element @name

als json

3.02.05.17

Rule 3.02.05.17
Name Concept names SHOULD have words or set of words that are used frequently, in the same order in the name except for the first position
Explanation
Introduction date 2010/11/17
Error message
NTA Rule True
PE Rule True
Section Naamgeving - Element @name

als json

3.02.05.18

Rule 3.02.05.18
Name REMOVED: Concepts in de substitutionGroup presentationTuple MUST have the suffix 'Presentation' on their name
Explanation
Decommission date 2011/09/28
Error message
NTA Rule True
PE Rule
Section Naamgeving - Element @name

als json

3.02.05.19

Rule 3.02.05.19
Name REMOVED: Concepts in de substitutionGroup specificationTuple MUST have the suffix 'Specification' on their name
Explanation
Decommission date 2011/09/28
Error message
NTA Rule True
PE Rule
Section Naamgeving - Element @name

als json

3.02.05.20

Rule 3.02.05.20
Name REMOVED: Concept names MUST be unique within the Dutch Taxonomy
Explanation
Decommission date 2011/09/28
Related to 2.02.02.02
Error message
NTA Rule True
PE Rule
References GFM2.0: 1.3.18
Section Naamgeving - Element @name

als json

3.02.05.21

Rule 3.02.05.21
Name The content of an xsd:element, xsd:complexType, or xsd:simpleType name attribute in UTF-8 must not exceed 200 bytes in length.
Explanation
Introduction date 2011/09/28
Error message
NTA Rule True
PE Rule True
References GFM2.0: 1.3.32
Testable True
Section Naamgeving - Element @name

als json

Naamgeving - Element @id

3.02.06.01

Rule 3.02.06.01
Name The xs:element/@id MUST be unique within the Dutch Taxonomy.
Explanation
Introduction date 2010/11/17
Error message
NTA Rule True
PE Rule True
References FRTA1.0: 2.1.5 GFM2.0: 1.3.19
Section Naamgeving - Element @id

als json

Naamgeving - Element Standaard label

3.02.07.01

Rule 3.02.07.01
Name The standard label MUST be a true representation of the meaning of the concept
Explanation
Introduction date 2010/11/17
Error message
NTA Rule True
PE Rule True
Section Naamgeving - Element Standaard label

als json

3.02.07.02

Rule 3.02.07.02
Name Standard labels MUST be clear, consistent and recognizable
Explanation
Introduction date 2011/09/28
Error message
NTA Rule True
PE Rule True
Section Naamgeving - Element Standaard label

als json

3.02.07.03

Rule 3.02.07.03
Name REMOVED: Standard labels MUST have the same pattern in their wording
Explanation
Decommission date 2011/09/28
Error message
NTA Rule True
PE Rule
Section Naamgeving - Element Standaard label

als json

3.02.07.04

Rule 3.02.07.04
Name REMOVED: Standard labels MUST NOT use: ? sign
Explanation
Decommission date 2011/09/28
Error message
NTA Rule True
PE Rule
Section Naamgeving - Element Standaard label

als json

3.02.07.05

Rule 3.02.07.05
Name Labels SHOULD have a capital first letter
Explanation
Introduction date 2011/09/28
Error message
Section Naamgeving - Element Standaard label

als json

3.02.07.06

Rule 3.02.07.06
Name Labels with the "standard" role MUST NOT exceed 255 characters
Explanation
Introduction date 2010/11/17
Error message
NTA Rule True
PE Rule True
Section Naamgeving - Element Standaard label

als json

3.02.07.07

Rule 3.02.07.07
Name REMOVED: tandard labels MUST contain at least one noun
Explanation
Decommission date 2011/09/28
Error message
NTA Rule True
PE Rule
Section Naamgeving - Element Standaard label

als json

3.02.07.08

Rule 3.02.07.08
Name Standard labels SHOULD NOT contain incomprehensable acronyms
Explanation
Introduction date 2010/11/17
Error message
NTA Rule True
PE Rule True
Section Naamgeving - Element Standaard label

als json

3.02.07.09

Rule 3.02.07.09
Name Standard labels SHOULD NOT contain abbreviations. Abbreviations must be written in full EXCEPT those abbreviations that are part of common writing for which anyone (anyone as in: parties that work with the Dutch Taxonomy) is expected to understand them
Explanation
Introduction date 2011/09/28
Error message
NTA Rule True
PE Rule True
Section Naamgeving - Element Standaard label

als json

3.02.07.10

Rule 3.02.07.10
Name REMOVED: Standard labels that contain sequences of three or more MUST use the comma as separator
Explanation
Decommission date 2011/09/28
Error message
NTA Rule True
PE Rule
Section Naamgeving - Element Standaard label

als json

3.02.07.11

Rule 3.02.07.11
Name REMOVED: Standard labels MUST avoid gender specific language
Explanation
Decommission date 2011/09/28
Error message
NTA Rule True
PE Rule
Section Naamgeving - Element Standaard label

als json

3.02.07.13

Rule 3.02.07.13
Name REMOVED: Numbers less than 20 MUST be written in text EXCEPT when a number greater than 21 is in the same line, in the latter case all numbers are numeric not in text
Explanation
Decommission date 2011/09/28
Error message
NTA Rule True
PE Rule
Section Naamgeving - Element Standaard label

als json

3.02.07.14

Rule 3.02.07.14
Name REMOVED: Double spaces or whitespace, leading or trailing spaces MUST NOT be used
Explanation
Decommission date 2011/09/28
Related to 2.03.08.07
Error message
NTA Rule True
PE Rule
Section Naamgeving - Element Standaard label

als json

3.02.07.15

Rule 3.02.07.15
Name Standard labels MUST NOT be overly descriptive
Explanation
Introduction date 2012/05/01
Error message
NTA Rule True
PE Rule True
Section Naamgeving - Element Standaard label

als json

3.02.07.16

Rule 3.02.07.16
Name If labels are unclear, adverbs MUST be used to clearify the meaning
Explanation
Introduction date 2010/11/17
Error message
NTA Rule True
PE Rule True
Section Naamgeving - Element Standaard label

als json

3.02.07.17

Rule 3.02.07.17
Name The word "Other" MUST NOT be used as a separate standard label
Explanation
Introduction date 2010/11/17
Error message
NTA Rule True
PE Rule True
Section Naamgeving - Element Standaard label

als json

3.02.07.18

Rule 3.02.07.18
Name Words that are an indication for free text concepts, MUST be at the rear of the standard label
Explanation
Introduction date 2010/11/17
Error message
NTA Rule True
PE Rule True
Section Naamgeving - Element Standaard label

als json

3.02.07.19

Rule 3.02.07.19
Name Words that are an indication for non-monetary and non-text concepts MUST be at the rear of the standard label
Explanation
Introduction date 2010/11/17
Error message
NTA Rule True
PE Rule True
Section Naamgeving - Element Standaard label

als json

3.02.07.20

Rule 3.02.07.20
Name Standard labels SHOULD NOT express all includings and excludings
Explanation
Introduction date 2010/11/17
Error message
NTA Rule True
PE Rule
Section Naamgeving - Element Standaard label

als json

3.02.07.21

Rule 3.02.07.21
Name REMOVED: Standard labels for concepts that can hold positive and negative values MUST state the 'negated' text in round brackets
Explanation
Decommission date 2011/09/28
Error message
NTA Rule True
PE Rule
Section Naamgeving - Element Standaard label

als json

3.02.07.22

Rule 3.02.07.22
Name The calculation or valuation method that is applicable to some concepts, MUST be last in the standard label preceeded by a comma
Explanation
Introduction date 2010/11/17
Error message
NTA Rule True
PE Rule True
Section Naamgeving - Element Standaard label

als json

3.02.07.23

Rule 3.02.07.23
Name REMOVED: Standard labels on abstract concepts MUST have a suffix that refers to the use of the concept
Explanation
Decommission date 2011/09/28
Error message
NTA Rule True
PE Rule
Section Naamgeving - Element Standaard label

als json

3.02.07.24

Rule 3.02.07.24
Name REMOVED: Standard labels MUST NOT use the word 'Total', use totalLabel role
Explanation
Decommission date 2011/09/28
Error message
NTA Rule True
PE Rule
Section Naamgeving - Element Standaard label

als json

3.02.07.25

Rule 3.02.07.25
Name REMOVED: Tuple children concepts MUST NOT have standard labels that repeat the content of the tuple standard label
Explanation
Decommission date 2011/09/28
Error message
NTA Rule True
PE Rule
Section Naamgeving - Element Standaard label

als json

3.02.07.26

Rule 3.02.07.26
Name REMOVED: Standard labels MUST be put in the singular form
Explanation
Decommission date 2011/09/28
Error message
NTA Rule True
PE Rule
Section Naamgeving - Element Standaard label

als json

3.02.07.27

Rule 3.02.07.27
Name Standard labels SHOULD NOT contain references to the reference resource content
Explanation
Introduction date 2011/09/28
Error message
NTA Rule True
PE Rule True
Section Naamgeving - Element Standaard label

als json

3.02.07.28

Rule 3.02.07.28
Name Standard labels MUST fall in line with the concept name definition
Explanation
Introduction date 2011/09/28
Error message
NTA Rule True
PE Rule True
References GFM2.0: 2.3.7
Section Naamgeving - Element Standaard label

als json

3.02.07.29

Rule 3.02.07.29
Name Standard labels (and other) MUST fall in line with the definition of the concept
Explanation
Introduction date 2012/05/01
Error message
NTA Rule True
PE Rule True
References (FRTA 2.1.13)
Section Naamgeving - Element Standaard label

als json

3.02.07.30

Rule 3.02.07.30
Name Words MUST have a consistent spelling and usage within one language and label resource role
Explanation
Introduction date 2012/05/01
Error message
NTA Rule True
PE Rule True
References (FRTA 2.1.15)
Section Naamgeving - Element Standaard label

als json

3.02.07.31

Rule 3.02.07.31
Name Standard labels MUST NOT restrict input on the fact
Explanation
Introduction date 2011/09/28
Error message
NTA Rule True
PE Rule True
References (FRTA 2.3.5)
Section Naamgeving - Element Standaard label

als json

3.02.07.32

Rule 3.02.07.32
Name The languagecode is leading in determining the characterset for the label, limited by ISO/IEC-8859-15 (Latin-9)
Explanation
Introduction date 2010/11/17
Error message
NTA Rule True
PE Rule True
Section Naamgeving - Element Standaard label

als json

Naamgeving - Element type @name

3.02.08.01

Rule 3.02.08.01
Name Custom datatypes names for concepts MUST be a restriction from XII defined datatypes
Explanation
Introduction date 2010/11/17
Decommission date 2016/04/06
Error message
NTA Rule True
PE Rule
Section Naamgeving - Element type @name

als json

3.02.08.02

Rule 3.02.08.02
Name Datatype names MUST use characters a-zA-Z0-9_- only
Explanation
Introduction date 2010/11/17
Error message
NTA Rule True
PE Rule
Testable True
Section Naamgeving - Element type @name

als json

3.02.08.03

Rule 3.02.08.03
Name Datatypes for specialized concepts, MUST have a name fitting with their use (e.g.. nlzipItemType)
Explanation
Introduction date 2010/11/17
Error message
NTA Rule True
PE Rule
Section Naamgeving - Element type @name

als json

3.02.08.04

Rule 3.02.08.04
Name Dataypes for generic use MUST have a name based on the XML datatypes (e.g.. string, integer, nonPositiveInteger, date ...)
Explanation
Introduction date 2010/11/17
Decommission date 2022/02/16
Error message
NTA Rule True
PE Rule
Testable
Section Naamgeving - Element type @name

als json

3.02.08.05

Rule 3.02.08.05
Name Datatypes for generic use MUST address the facets in their name conform table E
Explanation
Introduction date 2012/05/01
Error message
NTA Rule True
PE Rule
References Naamgeving_hulptabellen#Tabel_E:_XML_Facets_die_in_de_datatype_naam_worden_opgenomen
Section Naamgeving - Element type @name

als json

3.02.08.06

Rule 3.02.08.06
Name The name of a datatype with met <xs:restriction base="xbrli:*ItemType">, for generic use MUST have the suffix 'ItemType'
Explanation
Introduction date 2010/11/17
Error message
NTA Rule True
PE Rule
Testable True
Section Naamgeving - Element type @name

als json

3.02.08.07

Rule 3.02.08.07
Name REMOVED Datatypes that address enumerations MUST have the prefix 'cd_' in their name
Explanation
Decommission date 2011/04/01
Error message
NTA Rule True
PE Rule
Section Naamgeving - Element type @name

als json

3.02.08.09

Rule 3.02.08.09
Name Typenames MUST use lower camelcase and MAY use numbers and underscore
Explanation
Introduction date 2013/05/15
Agreed date 2013/02/27
Error message
NTA Rule True
PE Rule
Testable True
Section Naamgeving - Element type @name

als json

Naamgeving - Linkrole URI

3.02.09.01

Rule 3.02.09.01
Name REMOVED Linkrole URI's MUST be unique in the Dutch Taxonomy
Explanation
Introduction date 2010/11/17
Error message
NTA Rule True
PE Rule
References GFM2.0: 1.3.10
Section Naamgeving - Linkrole URI

als json

3.02.09.02

Rule 3.02.09.02
Name Linkrole URI"s MUST be in lowercase.
Explanation
Introduction date 2010/11/17
Related to 3.02.09.10
Error message
NTA Rule True
PE Rule
Testable True
Section Naamgeving - Linkrole URI

als json

3.02.09.03

Rule 3.02.09.03
Name Linkrole URI"s MUST use characters a-z0-9_-: only
Explanation
Introduction date 2010/11/17
Error message
NTA Rule True
PE Rule
Testable True
Section Naamgeving - Linkrole URI

als json

3.02.09.04

Rule 3.02.09.04
Name Linkrole URI"s MUST NOT be longer than 255 characters
Explanation
Introduction date 2010/11/17
Error message
NTA Rule True
PE Rule
References GFM2.0: 1.3.33
Testable True
Section Naamgeving - Linkrole URI

als json

3.02.09.05

Rule 3.02.09.05
Name REMOVED Linkrole URIs MUST start with http://www.nltaxonomie.nl
Explanation
Introduction date 2010/11/17
Decommission date 2013/05/15
Error message
NTA Rule True
PE Rule
References 3.02.09.10
Section Naamgeving - Linkrole URI

als json

3.02.09.06

Rule 3.02.09.06
Name REMOVED Dutch Taxonomy linkrole URI's MUST have the following construction: http://www.nltaxonomie.nl / {folder path} / {functional name} - {dim}
Explanation
Introduction date 2010/11/17
Decommission date 2013/05/15
Related to 3.02.09.10
Error message
NTA Rule True
PE Rule
Section Naamgeving - Linkrole URI

als json

3.02.09.10

Rule 3.02.09.10
Name Dutch Taxonomy linkrole URI"s MUST follow the sequence: urn:{NT partner prefix}:linkrole:{functional name}
Explanation
Introduction date 2013/05/15
Agreed date 2012/12/05
Error message
NTA Rule True
PE Rule
Section Naamgeving - Linkrole URI

als json

Naamgeving - Linkrole @id

3.02.10.01

Rule 3.02.10.01
Name REMOVED; Linkrole @id MUST be unique within the Dutch Taxonomy
Explanation
Decommission date 2012/01/01
Error message
NTA Rule True
PE Rule
Section Naamgeving - Linkrole @id

als json

3.02.10.02

Rule 3.02.10.02
Name Linkrole @id MUST NOT exceed 255 characters
Explanation
Introduction date 2010/11/17
Error message
NTA Rule True
PE Rule True
Testable True
Section Naamgeving - Linkrole @id

als json

3.02.10.03

Rule 3.02.10.03
Name Linkrole @id MUST be unique in the Dutch Taxonomy
Explanation
Introduction date 2011/09/28
Related to 3.02.06.01
Error message
NTA Rule True
PE Rule True
Section Naamgeving - Linkrole @id

als json

Naamgeving - @xlink:label (op locator en resource)

3.02.11.01

Rule 3.02.11.01
Name Locator @xlink:label names SHOULD be constructed from: @id from the XML node, underscore, "loc"
Explanation
Introduction date 2012/05/01
Error message
NTA Rule True
PE Rule
Testable True
Section Naamgeving - @xlink:label (op locator en resource)

als json

3.02.11.02

Rule 3.02.11.02
Name ADVICE: Reference resource @xlink:label names MUST be constructed from: namespace prefix of the schema that declares the linkrole URI, underscore, unique string based on the resource content, underscore, unique part of the role, underscore, 'ref'
Explanation
Introduction date 2012/05/01
Related to 3.02.11.04
Error message
NTA Rule True
PE Rule
Testable True
Section Naamgeving - @xlink:label (op locator en resource)

als json

3.02.11.03

Rule 3.02.11.03
Name @xlink:label names MUST use a-zA-Z0-9_-. characters only
Explanation
Introduction date 2010/11/17
Error message
NTA Rule True
PE Rule True
Testable True
Section Naamgeving - @xlink:label (op locator en resource)

als json

3.02.11.04

Rule 3.02.11.04
Name ADVICE: Label resource @xlink:label names MUST be constructed from: namespace prefix of the schema that declares the linkrole URI, underscore, element name from the concept to which the label connects, underscore, unique part of the role, underscore, language code from @xml:lang
Explanation
Introduction date 2012/05/01
Related to 3.02.11.02
Error message
NTA Rule True
PE Rule
Section Naamgeving - @xlink:label (op locator en resource)

als json

Naamgeving - link:part @name

3.02.12.01

Rule 3.02.12.01
Name New link:parts MUST 'fit' the existing set of (XII) link:parts
Explanation
Introduction date 2010/11/17
Error message
NTA Rule True
PE Rule True
Section Naamgeving - link:part @name

als json

3.02.12.02

Rule 3.02.12.02
Name Link:parts names MUST follow concept naming rules
Explanation
Introduction date 2010/11/17
Error message
NTA Rule True
PE Rule True
Section Naamgeving - link:part @name

als json

Naamgeving - Enumeratie waarden

3.02.13.01

Rule 3.02.13.01
Name Enumerations MUST use a restriction on xbrli:stringItemType
Explanation
Introduction date 2011/09/28
Decommission date 2022/02/16
Error message
NTA Rule True
PE Rule True
Testable
Section Naamgeving - Enumeratie waarden

als json

3.02.13.02

Rule 3.02.13.02
Name ADVICE: Enumeration values MUST be in the local language
Explanation
Introduction date 2010/11/17
Error message
Section Naamgeving - Enumeratie waarden

als json

3.02.13.03

Rule 3.02.13.03
Name
Explanation
Related to 3.02.13.02
Error message
NTA Rule
PE Rule True
Section Naamgeving - Enumeratie waarden

als json

Naamgeving - Context elementen

3.02.14.01

Rule 3.02.14.01
Name XML children elements for xbrli:segment and xbrli:scenario MUST follow concept naming conventions
Explanation
Introduction date 2010/11/17
Error message
NTA Rule True
PE Rule True
Section Naamgeving - Context elementen

als json

Naamgeving - Taal aspecten

3.02.15.01

Rule 3.02.15.01
Name XML nodes that can appear in instances MUST have standard labels in the local language
Explanation
Error message
NTA Rule True
PE Rule True
Section Naamgeving - Taal aspecten

als json

3.02.15.02

Rule 3.02.15.02
Name Language beyond the local language MAY be offered
Explanation
Introduction date 2010/11/17
Related to 2.02.02.27
Error message
Section Naamgeving - Taal aspecten

als json

3.02.15.03

Rule 3.02.15.03
Name
Explanation
Related to 3.02.15.02
Error message
NTA Rule
PE Rule True
Section Naamgeving - Taal aspecten

als json

Naamgeving - @id (op resource)

3.02.16.01

Rule 3.02.16.01
Name @id content on resources SHOULD be unique in the Dutch Taxonomy. If multiple resources in the Dutch Taxonomy have the same @id, the content of the resources MUST be idential.
Explanation
Introduction date 2011/09/28
Error message
NTA Rule True
PE Rule True
Section Naamgeving - @id (op resource)

als json

Naamgeving - @id (op enumeratiewaarden)

3.02.17.01

Rule 3.02.17.01
Name Enumeration @id values MUST be unique within the Dutch Taxonomy.
Explanation
Introduction date 2011/09/28
Error message
NTA Rule True
PE Rule True
Testable
Section Naamgeving - @id (op enumeratiewaarden)

als json

TEST

5.02.01.01

Rule 5.02.01.01
Name Teaxonomy-set must be all-inclusive
Explanation -
Introduction date 2021-01-30
Agreed date 2021-01-29
Error message
NTA Rule True
PE Rule
Testable
Severity WARNING
Section TEST

als json