1 Goals

XBRL provides a set of standard data types that may appear in XBRL schemas. These include those specified in [XBRL 2.1], [DIMENSIONS] and any additional modules that are XBRL Recommendations. As XBRL applications emerge, new, non-standard data types having common and useful semantics are being proposed. The goal of the XBRL Data Type Registry (DTR) is to be a public, online data set that documents these non-standard data types and their usage. Additions and other changes to the DTR, like other XBRL International work products, are processed through a series of steps detailed in this document. The goal is to maximise the utility and longevity of the new data types and the taxonomies that use them.

1.1 Relationship to other work

This document pertains to XBRL as defined in the XBRL Specification [XBRL 2.1] and additional modules such as [DIMENSIONS].

1.2 Terminology

The key words MUST, MUST NOT, REQUIRED, SHALL, SHALL NOT, SHOULD, SHOULD NOT, RECOMMENDED, MAY, and OPTIONAL, in this specification, are to be interpreted as described in [IETF RFC 2119].

abstract element, bind, concept, concrete element, context, Discoverable Taxonomy Set (DTS), duplicate items, duplicate tuples, element, entity, equal, essence concept, fact, instance, item, least common ancestor, linkbase, period, taxonomy, tuple, unit, taxonomy schema, child, parent, sibling, grandparent, uncle, ancestor, XBRL instance, c-equal, p-equal, s-equal, u-equal, v-equal, x-equal, minimally conforming XBRL processor, fully conforming XBRL processor and any other terms not specifically defined elsewhere in this document but which are used and defined in the XBRL 2.1 specification. are as defined by [XBRL 2.1] .

CR refers to a Candidate Recommendation of XBRL International.

REC refers to a Recommendation of XBRL International.

DTR refers to the Data Types Registry that is the subject of this specification.

DTRAM refers to the Data Types Registry Approval Manager.

PWD refers to a Public Working Draft of XBRL International.

SWG refers to the XBRL International Base Specification and Maintenance Working Group.

XSB refers to the XBRL International Standards Board .

1.3 Language

The official language of XBRL International's own work products is English and the preferred spelling convention is UK English.

All documentation supporting a registry entry MUST be provided in English, and MAY be provided in additional languages.

1.4 Document conventions

1.4.1 Typographic conventions

1.4.1.1 Definition notation

Definitions are highlighted with green text.

1.4.1.2 Footnote notation

Comments which are informative, but not essential to the understanding of the point at hand, are provided in footnotes. All footnotes are non-normative.

1.4.1.3 Element and attribute notation

When referring to a specific element, it will be identified by its namespace prefix and local name. For example, the root element of a versioning report would be referred to as <ver:report> .

Attributes are also identified by their local name and, where appropriate, their namespace prefix. Attributes are distinguished from elements by prefixing them by an @ symbol. Thus, @id refers to the attribute with the name id.

When referring to any attribute, so long as it has a specific namespace, the local name is replaced by an asterisk ( *). Thus, the notation @xml:* specifies any attribute in the namespace http://www.w3.org/XML/1998/namespace.

1.4.2 Formatting conventions

The following highlighting is used for normative technical material in this document:

Text of the normative example.

The following highlighting is used for non-normative examples in this document:

Text of the non-normative example.

The following highlighting is used for non-normative examples of poor, discouraged or disallowed usage.

Text of the discouraged example.

2 Update Process

This document defines the process by which an entry is added to the DTR.

2.1 Steps to achieve Recommendation status

The submitter creates a submission containing all of the information needed (as specified in [DTR STRUCTURE]) and requests the DTRAM to enter it into the DTR.
The DTRAM MAY suggest alternatives to the proposal and request to the submitter that it be resubmitted as they see fit. In the event that there is more than one submission made for similar requirements, or if the submission is substantially similar to an entry that is already present in the DTR the DTRAM MAY request the submitters to agree a common solution between themselves and resubmit a single joint submission. If this is not acceptable to the submitters, the XSB will be requested to arbitrate.
The DTRAM approves the requirements and conducts a technical evaluation. This shall include an initial check that no submitted type has the same local name as any other type already in the registry If the DTRAM determines that wider technical evaluation is necessary they MAY then refer the submission to the SWG for such technical evaluation.
If requested in the previous step, the SWG reviews the submission. If they are satisified then they recommend to the DTRAM that they approve release of the submission as a CR. If they are not satisfied they advise the DTRAM giving their reasons. The DTRAM in turn notifies the submitter who MAY then either modify the submission and resubmit, withdraw the submission, or appeal to the XSB.
The DTRAM approves the submission and recommends to the XSB that it be released as a CR.
If the publication is approved by the XSB, the data type will be included at CR status in the next CR DTR release. A public notice of this change is made and feedback requested.
A minimum of 30 days of public review follow.
If the data type requires implementers to perform additional validation, then the submission MUST be accompanied by conformance tests that can be used to check the behaviour of processors that implement the data type. The DTRAM or, if they decide to delegate this step, the SWG, verifies that the conformance suite tests are valid and that there are two separate implementations that pass them.
The DTRAM reviews any feedback received. If substantive changes are required, a further CR release is required, repeating the process above from step 5. Otherwise, the DTRAM recommends to the XSB that the data type be promoted to REC status. Alternatively, the DTRAM MAY, based on feedback received, decide to withraw the data type, as described in Section 2.2.
The XSB approves the data type, and it is included at REC status in the next REC DTR release.

Once a data type has been published at REC status, it may only be modified by errata corrections to address defects in the current definition. Any such changes MUST be approved by the DTRAM and XSB and will be included in the next release of the DTR.

2.2 Withdrawing a Data Type

Unless a data type has reached REC status it may be withdrawn from the DTR at any time upon request of the original submitter. Such request MUST be made to the DTRAM.

The DTRAM may also request the withdrawl of a pre-REC data type. Any such request MUST be approved by the XSB.

A withdrawn datatype will be excluded from all subsequent DTR releases.

A data type with REC status MAY NOT be withdrawn in this manner but MUST follow the process in Section 2.3 for rescinding a Recommended data type.

2.3 Rescinding a Recommended Data Type

A data type may be rescinded by approval of the XSB. The data type will not be included in future releases of the DTR, but previously published releases will not be updated.

2.4 Acknowledged data types

Earlier versions of this document allowed for an "ACKNOWLEDGED" status. This status is deprecated, and data types in the DTR at this status have been adopted at CR status.

3 DTR releases

In order to make changes to the registry more manageable for implementers, and to avoid making "in place" changes to published schemas, changes to data types in the DTR are grouped into public releases. Public releases are one of two types:

CR DTR releases contain all data types that have been approved at either CR or REC status. Such releases are published only at versioned URLs, and do not result in an update the DTR index that is published at a fixed, unversioned location on the xbrl.org website. The release includes all REC and CR data types, including those that have been published in previous releases.
REC DTR releases contain only data types that have been approved to REC status. Such releases are published at versioned URLs, and the DTR index that is published at a fixed, unversioned location on the xbrl.org website is updated to match the latest release. The release includes all REC data types, including those that have been published in previous releases.

Appendix A References

DIMENSIONS: XBRL International Inc.. "XBRL Dimensions 1.0"
Ignacio Hernández-Ros, and Hugh Wallis.
(See http://www.xbrl.org/Specification/XDT-REC-2006-09-18.htm)
DTR STRUCTURE: XBRL International Inc. "Data Types Registry - Structure 1.1"
Mark GoodhandHugh WallisPaul Warren.
(See https://www.xbrl.org/Specification/dtr/CR-2018-01-17/dtr-structure-1.1-CR-2018-01-17.html)
IETF RFC 2119: IETF (Internet Engineering Task Force). "RFC 2119: Key words for use in RFCs to Indicate Requirement Levels"
Scott Bradner.
(See http://www.ietf.org/rfc/rfc2119.txt)
XBRL 2.1: XBRL International Inc.. "Extensible Business Reporting Language (XBRL) 2.1 Includes Corrected Errata Up To 2013-02-20"
Phillip Engel, Walter Hamscher, Geoff Shuetrim, David vun Kannon, and Hugh Wallis.
(See http://www.xbrl.org/Specification/XBRL-2.1/REC-2003-12-31/XBRL-2.1-REC-2003-12-31+corrected-errata-2013-02-20.html)

Appendix B Intellectual property status (non-normative)

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).

Appendix C Acknowledgements (non-normative)

This document could not have been written without the contributions of many people.

Appendix D Document history (non-normative)

Date	Author	Details
04 July 2017	Paul Warren	Version 1.1 of process. Removes "acknowledged" status, bundles updates into versioned registry releases.
11 October 2017	Paul Warren	Initial PWD of v1.1.
17 January 2018	Paul Warren	CR of v1.1.
13 February 2019	Paul Warren	PR of v1.1.

Appendix E Errata corrections in this document

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 Data Type Registry Approval Manager up to and including 13 February 2019. 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.

Data Type Registry - Process 1.1

Proposed Recommendation 13 February 2019

Status

Abstract

Table of Contents

Appendices

Definitions