Copyright © XBRL International Inc., All Rights Reserved.
Circulation of this Recommendation is unrestricted. This document is normative. Recipients are invited to submit comments to email@example.com, and to submit notification of any relevant patent rights of which they are aware and provide supporting documentation.
B Schemas (normative)
C Intellectual property status (non-normative)
D Acknowledgements (non-normative)
E Document History (non-normative)
F Errata Corrections incorporated in this document
xs:enumeration feature allows enumerated
types to be defined. Such types have a fixed list of allowed values that cannot
be changed until the next version of the schema is published. XBRL projects
often require "extensible enumerations", which leave extension taxonomies free
to augment the list of allowed values for a concept, just as they are free to
add new members to the domain of an explicit dimension.
For multi-language projects, it is also important that labels can be provided for the enumeration values in each language.
Finally, it is often useful to refer to existing domain hierarchies in fact values. For example, a taxonomy might define a Region dimension, with members representing various countries. As well as using these members to qualify facts (e.g. "Sales in France" versus "Sales in Spain"), the taxonomy may define concepts that expect countries as values (e.g. a "Head office location" concept). Taxonomy authors should be free to define a domain of countries once, and use it in both contexts.
This specification provides a syntax for associating a concept with a domain of members, and validation rules to constrain the allowed values for the concept to the members of that domain. This meets the extensibility, labelling and reuse requirements outlined above.
This specification depends upon the XBRL Specification [XBRL 2.1] and the XBRL Dimensions Specification [DIMENSIONS]. In the event of any conflicts between this specification and the specifications upon which it depends, this specification does not prevail.
This Specification uses a number of namespace prefixes when describing elements and attributes. These are:
An extensible enumeration is defined by using a concept declaration with a
special data type and attributes that identify a domain of valid members.
For a concept with type
enum:enumerationItemType, or a type
derived from this, the following constraints apply:
@enum:domainattribute MUST be specified. If this condition is not satisfied, enumte:MissingDomainError MUST be raised.
@enum:domainattribute MUST identify a concept in the taxonomy that is in the
xbrli:itemsubstitution group and not in the
xbrldt:dimensionItemsubstitution groups. If this condition is not satisfied, enumte:InvalidDomainError MUST be raised.
@enum:linkroleattribute MUST be specified. If this condition is not satisfied, enumte:MissingLinkRoleError MUST be raised.
@enum:headUsableattribute MAY be specified to control whether the member identified by
@enum:domainshould itself be included in the domain.
The domain of enumeration values for a concept of type
enum:enumerationItemType is the
set of usable domain members obtained by following domain-member relationships starting from the
domain head in the extended link role identified by the
@enum:linkrole attribute. If the concept has an
@enum:headUsable attribute with an effective value of 'true', then the domain of enumeration values also includes the domain head, otherwise it does not.
Within [DIMENSIONS] the domain-member relationships that form a domain have the attribute
@xbrldt:usable to provide a way of excluding members from the domain.
But because @xbrldt:usable only applies to the target of an effective domain-member relationship, the
@enum:headUsable attribute exists to provide a way to exclude the head member itself.
This is required because no incoming arcs which have the domain head as their target are taken into account
when establishing the domain of enumeration values.
Facts reported against concepts with a type of
enum:enumerationItemType with a non-nil value MUST have a value that is in the domain of enumeration values for the concept.
enumie:InvalidFactValue MUST be raised if this condition is not satisfied.
The following is the XML schema provided as part of this specification. It is normative. A non-normative version (which should be identical to this except for appropriate comments indicating its non-normative status) is also provided as a separate file for convenience of users of the specification.
XBRL taxonomies using this extensible enumeration specification MAY import extensible-enumerations.xsd schema and MUST be schema valid according to the schema validation rules defined in [XML Schema Structures] and [XML Schema Datatypes]. Any XML Schema validation error MAY stop extensible enumeration processors from continuing to validate extensible enumeration definitions.
XBRL instances using the elements whose type is defined in extensible-enumerations.xsd MUST be XML Schema valid according to validation rules defined in [XML Schema Structures] and [XML Schema Datatypes]. Any XML Schema validation error MAY stop the processing of the instance document.
NOTE: (non-normative) Following the schema maintenance policy of XBRL International, it is the intent (but is not guaranteed) that the location of a non-normative version of this schema on the web will be as follows:
This document and translations of it may be copied and furnished to others, and derivative works that comment on or otherwise explain it or assist in its implementation may be prepared, copied, published and distributed, in whole or in part, without restriction of any kind, provided that the above copyright notice and this paragraph are included on all such copies and derivative works. However, this document itself may not be modified in any way, such as by removing the copyright notice or references to XBRL International or XBRL organizations, except as required to translate it into languages other than English. Members of XBRL International agree to grant certain licenses under the XBRL International Intellectual Property Policy (www.xbrl.org/legal).
This document and the information contained herein is provided on an "AS IS" basis and XBRL INTERNATIONAL DISCLAIMS ALL WARRANTIES, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO ANY WARRANTY THAT THE USE OF THE INFORMATION HEREIN WILL NOT INFRINGE ANY RIGHTS OR ANY IMPLIED WARRANTIES OF MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE.
The attention of users of this document is directed to the possibility that compliance with or adoption of XBRL International specifications may require use of an invention covered by patent rights. XBRL International shall not be responsible for identifying patents for which a license may be required by any XBRL International specification, or for conducting legal inquiries into the legal validity or scope of those patents that are brought to its attention. XBRL International specifications are prospective and advisory only. Prospective users are responsible for protecting themselves against liability for infringement of patents. XBRL International takes no position regarding the validity or scope of any intellectual property or other rights that might be claimed to pertain to the implementation or use of the technology described in this document or the extent to which any license under such rights might or might not be available; neither does it represent that it has made any effort to identify any such rights. Members of XBRL International agree to grant certain licenses under the XBRL International Intellectual Property Policy (www.xbrl.org/legal).
This document could not have been written without the contributions of many people.
|29 October 2014||Paul Warren||
Released as Recommendation.
This appendix contains a list of the errata that have been incorporated into this document. This represents all those errata corrections that have been approved by the XBRL International Specification Maintenance Working Group (SWG) up to and including 29 October 2014. Hyperlinks to relevant e-mail threads may only be followed by those who have access to the relevant mailing lists. Access to internal XBRL mailing lists is restricted to members of XBRL International Inc.
No errata have been incorporated into this document.