Concept declaration, wrapping a GlobalElementDeclaration. It must be in substitution group xbrli:item or xbrli:tuple,
either directly or indirectly.
There are no sub-classes for domain members, because as global element declarations they are defined in the Dimensions specification
in the exact same way that primary items are defined. Therefore primary items and dimension members are indistinguishable.
In order to build a ConceptDeclaration from a GlobalElementDeclaration, the builder needs a SubstitutionGroupMap as context.
The created ConceptDeclaration does not retain that used SubstitutionGroupMap. As a consequence, these concept declaration objects
only make sense in a context where the used substitution group map is fixed. In taxonomies that know their substitution group map, this
is clearly the case. In other words, outside the context of a taxonomy that knows its substitution group map, concept declarations
are not "portable" objects, whereas the underlying global element declarations are.
Concept declaration, wrapping a
GlobalElementDeclaration. It must be in substitution group xbrli:item or xbrli:tuple, either directly or indirectly.There are no sub-classes for domain members, because as global element declarations they are defined in the Dimensions specification in the exact same way that primary items are defined. Therefore primary items and dimension members are indistinguishable.
In order to build a
ConceptDeclarationfrom aGlobalElementDeclaration, the builder needs aSubstitutionGroupMapas context. The createdConceptDeclarationdoes not retain that usedSubstitutionGroupMap. As a consequence, these concept declaration objects only make sense in a context where the used substitution group map is fixed. In taxonomies that know their substitution group map, this is clearly the case. In other words, outside the context of a taxonomy that knows its substitution group map, concept declarations are not "portable" objects, whereas the underlying global element declarations are.