With the release of EDGAR 20.3, changes will be made to the way in which filers can redline revisions in their submissions to the EDGAR system. These changes allow for revisions within Inline XBRL. Existing revision tags have historically been placed loosely around text that has been altered to indicate the revision. In addition, broken character entities, <R> and </R>, could be used in place of tags. Neither of these methods are acceptable for Inline XBRL filings since they both violate that format’s rigid XHTML requirements.
New rules in the EDGAR Filer Manual (EFM) dictate important modifications that allow for revisions to be marked in iXBRL filings.
Traditional EDGAR HTML Filings
According to the EFM, revision tagging in traditional ASCII/EDGAR HTML filings remains unchanged. Users can place revision tags (<R> and </R>) around information they wish to indicate has been revised. For example, in HTML:
<P>The information in this section is <R>nearly</R> certain.</P>
or:
<P>The information in this section is <R>nearly&lg/R> certain.</P>
As always, the revision tags are removed before dissemination, leaving no way to infer their location.
Redlining in Inline XBRL
As per Section 5.2.5.16 of the EFM, redlined text must be indicated using a custom CSS property: -sec-ix-redline. This property must be set to “true” to designate redlined text. Users can place this property in a STYLE attribute along with other CSS properties. Commonly, this CSS property may be used with the STYLE attribute of a SPAN tag to indicate inline revisions. For example:
<P>The information in this section is <SPAN STYLE="-sec-ix-redline: true;">nearly</SPAN> certain.</P>
The custom -sec-ix-redline CSS property may be used with any STYLE attribute. As with traditional <R> tags, the -sec-ix-redline property is not disseminated as part of the document. The property is removed so that there is no way to infer its location. Other CSS properties are disseminated as is. If the property is the only CSS property indicated within a STYLE attribute, the entire attribute will be removed.
GoFiler follows the EFM in its handling of EDGAR and iXBRL formatting. The next software release that coincides with the release of EDGAR 20.3 will support these and all other formal EDGAR changes.
Sources:
EDGAR Filer Manual - Volume II: EDGAR Filing (September 2020) (sec.gov)
