DEVELOPMENT SEC Reporting Taxonomy

Public Review and Comment

The Development SEC Reporting Taxonomy (Development SRT) includes proposed changes since the last release.

We encourage all interested parties to review and comment on the ‘Development SRT’. To encourage feedback, the FASB Taxonomy Online Review and Comment System (TORCS) is operational throughout the year. All comments are tracked and reviewed for potential inclusion in a subsequent taxonomy release. All comments are acknowledged when received but it is not possible to respond directly to individual comments. We have included guidance for using the taxonomy viewer/commenting tool.
 

Guidelines for Providing Comments

Individuals providing comments on the taxonomies are required to register with a “user name” and email address. Please note that all comments will be visible to other registered users. In order to process comments, commentators should (1) describe the issue clearly, (2) provide examples and/or frequency of occurrence, and (3) provide a recommendation.

Please note: Individuals submitting more than 10 comments related to the same issue should not use this system as it delays the processing of the comments. Individuals who wish to provide more than 10 comments related to the same issue should send them directly to xbrlweb@fasb.org.

Changes in the Development SRT are identified by a Change Note (CN). The CN identifies the year-month of the change in the Change Date part (cn-part:ChangeDate). For example, “2017-05,” refers to a change made in May 2017 and identifies the nature of the change with the following (parts have added spaces in this document to assist in readability):
  • Taxonomy Version: identifies in which version of the Taxonomy the change was made.
  • Change Date: identifies the year and month the change was made in the Taxonomy.
  • Modified References: identifies by value of true that the change applies to a reference.
  • Modified Labels: identifies whether the change applies to a Standard, Period Start, Period End, or Total label.
  • Source: identifies the source of the change (e.g. regulatory update).
  • Source Name: identifies the regulatory source of the change (e.g. SEC).
  • New Element: identifies by value of true that the change is because of the addition of an element.
  • Modified Documentation: identifies by value of true that the change applies to a documentation label (definition).
  • Previous Documentation: identifies the previous documentation label when the change applies to a documentation label (definition).
  • Deprecated Date: identifies the date when the element is deprecated.
  • Deprecated Label: identifies the reason for the deprecation and possible replacement elements, if applicable.
  • Element Deprecated: identifies by value of true that the change applies to deprecation of an element.
  • Modified Deprecated Label: identifies by value of true that the change applies to a change in a deprecation label.
  • Modified Balance Type: identifies by value of true that the change applies to a balance type
“Shared Searches” are included to facilitate discovery of the changes. After applying the “Shared Search” and selecting “Highlight Matches” from the status bar at the bottom of the screen, the filter highlights the networks containing changes with pale yellow. Each element that has been modified or added will be highlighted with bright yellow. All items meeting the filter criteria will be listed in the search pane.



THE TAXONOMIES AND SUPPORTING MATERIALS PROVIDED THROUGH THESE LINKS ARE FOR REVIEW PURPOSES ONLY AND ARE NOT TO BE USED OR RELIED UPON FOR ANY PURPOSES OTHER THAN FOR THIS REVIEW AND COMMENT. YOUR USE OF THE TAXONOMIES FOR THESE PURPOSES SHALL BE SUBJECT TO THE TERMS AND CONDITIONS LOCATED AT THE INITIAL LINK TO THE TAXONOMIES.