Copyright ©2010 XBRL International Inc., All Rights Reserved.
Circulation of this Working Group Note is unrestricted. Other documents may supersede this document. 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.
This primer provides a non-normative overview of the XBRL Versioning Specification and some of the extension modules. The purpose of the primer is to inform prospective users of the basic terminology, construction, usage, and limitations of XBRL Versioning as a mechanism to document differences between two taxonomies, typically due to a version update. The central concepts of Assignments, Actions, and Events are explained with XML examples.
4 Technical and Semantic Differences
5 Key Concepts
6.1 Statutory change resulting in namespace and concept renaming
6.2 Change to dimensional representation of set of concepts
XBRL [XBRL 2.1] enables the capture of structured meta-data for a particular reporting scenario in the form of an XBRL taxonomy. Taxonomies are rarely static objects, and will need to be updated periodically for a range of reasons, including changes in the business requirements upon which they are built (for example, a change to an accounting standard), changes to the technical design of the taxonomy, or simple error corrections. When a new version of a taxonomy is released this has an impact on all users of the taxonomy including:
The XBRL Versioning specification defines an XML syntax for a Versioning Report that is designed to allow taxonomy creators to communicate information about the changes between two taxonomy versions in a structured format that will minimise the impact of the update on the users of the taxonomy. Versioning Reports only concern DTSes and related XBRL instances.
A Versioning Report is distinct from a simple difference report in that a Versioning Report includes information that cannot be obtained from an automated comparison of two DTSs such as identifying concepts with different names that are otherwise equivalent, and communicating information about the motivation behind changes. It is this ability to communicate additional information that yields value in creating a standardised Versioning Report. The goal is to facilitate DTS and related XBRL instance users/consumers in adapting existing systems to accommodate a different DTS and XBRL instance structure.
It should be noted that whilst the primary use case considered in the creation of this specification is the provision of versioning information between two versions of the same taxonomy, the specification makes no assumptions about the relationship between taxonomies involved, and a Versioning Report can be prepared for any pair of DTSs. Furthermore, the specification makes no assumptions that a Versioning Report provides complete documentation of differences between the From DTS and To DTS.
The instance-aspects extension module specifies how to map and address changes to the aspects of fact items of a set of concepts, including dimensional and other aspects, specifying that changes have occurred between different DTS's to items that may be a primary item and its dimension's and domain-members, or other aspects that may distinguish the fact item.
Although the concept of versioning may be thought of to relate to consecutive versions of the same taxonomy, it applies as well to documenting the difference between unrelated taxonomies describing the same business fact, such as between independent Financial Reporting representations that can report equivalent facts or between Global Ledger an Financial Reporting representations.
This primer is non-normative. All normative definitions, formats, and validation rules are contained in the various modular schemas that make up the Versioning Specification.
In order to understand the XBRL Versioning Specification it is necessary to have a suitable background in XML[XML Base], XML Schemas[XML Schema Structures], Linkbases[XLINK], XML Namespaces [XML Names], and XBRL[XBRL 2.1]. In particular, it is necessary to understand specific XBRL concepts around taxonomies, DTSs, XBRL facts, and possibly XBRL dimensions[DIMENSIONS].
The XBRL Versioning Specification is a modular specification designed to allow the author of a Versioning Report to select the level of detail at which changes are documented. The modular approach allows for versioning information on extensions to the XBRL Specification [XBRL 2.1], such as the XBRL Dimensions Specification [DIMENSIONS], to be addressed as extension modules. Extension specifications also provide finer levels of versioning information.
Versioning Reports may use one or more extension specifications in addition to the Base Specification, which is always required. Other module dependencies may also exist.
XBRL Versioning supports both technical differences and
semantic differences between DTSs. Technical
differences are those that can be automatically identified by software
comparing the properties of the pair of information items under observation
has been removed"). Semantic
differences are the explanations of the technical
differences made by the authors of a versioning report (e.g. "Net Value,
as represented by the
element, has been replaced by three
new line items ..."). Given two DTSs and some rules to match
information items from one DTS to the other, the technical
differences are fixed and well defined, however the semantic
differences are unlimited since a DTS does not embed detailed semantic
background for individual XBRL concepts or the association of differences
between two taxonomies. An XBRL Versioning Report provides a mechanism to
capture and document both, including human-readable documentation that may be
useful input to users migrating an application from using one DTS
to another the next.
A Versioning Report describes the technical and semantic differences between an origin DTS, named the From DTS, and a destination DTS, named the To DTS. It does this using a standard format XML instance document that conforms to the structure described in the various XBRL Versioning Report specification modules, as well as a set of linkbase documents. The XBRL Versioning Report document contains the technical differences between the From DTS and To DTS, and references to the associated linkbase documents that describe the semantic differences.
The partitioning of changes documented into versioning modules is shown in Figure 1. A simple Versioning Report that documents only a change of namespace between two DTSs would only require the versioning syntax defined by the Base module. A more advanced Versioning Report that also documented the addition, removal or renaming of concepts would also need to include the Concept Basic module in the same report. Changes to the concepts, such as type, period, or label, are documented with the Concept Extended module. Changes to the identification of facts in XBRL instances, such as to dimensions, segment, scenario, and tuple location, are documented with the Instance Aspects module. Changes to the relationship sets for presentation, calculation, and structure of dimensional syntax, are documented with the Relationship Sets module.
Structurally, a Versioning Report has a simple three-tier hierarchy. This is used to group changes at both the semantic and technical levels. At the highest level there are Assignments which document business level changes. Semantics associated with such changes can then refer to a single Assignment which may in turn capture many Actions, which provide the middle tier of logical changes between DTSs. The lowest-level tier are Events which represent the specific technical changes to map one DTS to another. Independently, the set of all Events provide as much information as the entire Versioning Report regarding the technical changes, however they lack the structure which enables a semantic interpretation and understanding of the reasons for those changes. Generic Events don't directly appear in a versioning report. Instead they are abstract place holders for which each module specification defines specific syntax for change events, such as "add" or "remove".
The base, concept, and relationship-set modules focus on documenting issues of change between two DTSes, such as schema file changes of namespace, concept name or attribute, and linkbase relationships, and the instance aspects module focuses on how facts representing the same reported business item are modeled differently in instances of the respective DTSes in terms of aspects such as the concept and dimension.
The utility of documenting aspect identification changes is for preparation and consumption of an instance document. Mapping software that may convert source data into XBRL, and analytic software that may analyze reported business facts, both need this sort of versioning information, which is from the instance perspective, instead of the taxonomy perspective.
Simple extension of this issue also handles cases where other aspects of business fact identification change, such as segment and scenario identification that becomes dimensional, and tuple located facts that are identified by tuple siblings, cousins, and such, become dimensional facts (or the converse).
The simple example of Figure 2 illustrates a Versioning Report for a statutory change resulting from a new tax year. The base taxonomies only contain four concepts each, and there are only two changes between the 2009 and 2010 versions: the namespace changes (to reflect the change of year and a new taxonomy version), and one concept is renamed (from DebtOutstanding to TotalDebt). The namespace mapping can be done using the Base module. The concept renaming event requires events defined in the Concept Basic module, illustrating the use of modules in a Versioning Report. Using the Mapping rules, all concepts in the new taxonomy that have the same localname as the old taxonomy are considered Equivalent.
As mentioned earlier, the XBRL Versioning Report primarily details technical differences. Semantic differences and interpretation of changes are described via linkbases. The following illustrates a linkbase that documents each Assignment, Action, an Event in the Versioning Report.
This shows the original From DTS for the 2009 taxonomy:
This shows the target To DTS for the 2010 taxonomy:
The example of Figure 3 illustrates a Versioning Report for a technical change resulting from the introduction of dimensions to a replace a hierarchy of concepts. In this case facts representing the same reported business item are modelled differently in instance of the respective DTSes in terms of aspects such as the concept and dimension. The Versioning Report includes description of the assignment, using the Base module, description of the deleted concepts of the hierarchical representation and addition of new concepts of the dimensioned instance. (It is assumed that the dimensions themselves were either in existence or documented separately.)
|Version 1||Version 2|
|A||X (dim D, mbr d1)|
|B||X (dim D, mbr d2)|
|C||X (dim D, mbr d3)|
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 including the participants in the Versioning Working Group.
|20 June 2010||Ian Stokes-Rees||
Created primer document from existing base specification.
|12 September 2010||Herm Fischer||
Initial merge of overview material for instance-aspects and dimensional issues of relationship-sets.
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 Versioning Working Group up to and including 03 November 2010. 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.