Copyright © 2016 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.
This specification is an extension to the Formula Validation Specification [VALIDATION]. It defines elements and relationships that allow formula authors to associate standard severity levels with assertions.
1.2 Relationship to other work
1.3 Language independence
1.5 Document conventions (non-normative)
1.5.1 Typographic conventions
184.108.40.206 Definition notation
220.127.116.11 Footnote notation
18.104.22.168 Element and attribute notation
22.214.171.124 Error code notation
1.5.2 Formatting conventions
1.6 Namespaces and namespace prefixes
2 Severity elements
3 Assertion-unsatisfied-severity relationships
5 Default Severity
A Schema and Linkbase
A.1 Assertion Severity schema
A.2 Assertion Severity linkbase
C Intellectual property status (non-normative)
D Acknowledgements (non-normative)
E Document history
F Errata corrections in this document
All formula assertions specifications ([VALUE ASSERTIONS], [EXISTENCE ASSERTIONS] and [CONSISTENCY ASSERTIONS]) define a standard XML-based syntax for validations on XBRL business reports. The technical nature of an assertion is that the assertion is either "satisfied" or "unsatisfied". From a business perspective, not all assertions express rules which have the same level of importance, and consequently there is a need to be able to attach differing severities in order to classify the severity of an assertion that is unsatisfied.
This specification defines three standard severity levels and the syntax for associating them such that an appropriate severity is applied when an assertion is unsatisfied.
This specification extends the suite of formula specifications without modifying any existing specifications.
This specification depends upon the XBRL Specification [XBRL 2.1], the XBRL Generic Link Specification [GENERIC LINKS] and the Formula Validation Specification [VALIDATION] which defines assertions. In the event of any conflicts between this specification and the specifications upon which it depends, this specification does not prevail.
The official language of XBRL International's own work products is English and the preferred spelling convention is UK English.
This specification is consistent with the definitions of any of the terms defined in specifications that it depends on.
Comments which are informative, but not essential to the understanding of the point at hand, are provided in footnotes. All footnotes are non-normative.
When referring to a specific element, it will be identified by
its namespace prefix and local name. For example, the root
element for a specification container element would be referred to as
Attributes are also identified by their local name and, where
appropriate, their namespace prefix. Attributes are
distinguished from elements by prefixing them by an
refers to the attribute with the name
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
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 helpful example.
Next paragraph of the helpful example.
Example 3 shows the formatting for non-normative examples of poor, discouraged or disallowed usage.
The example itself.
Namespace prefixes [XML NAMES] will be used
for elements and attributes in
ns is the
namespace prefix and
name is the local name.
Throughout this specification, the mappings
from namespace prefixes to actual namespaces is consistent
with Table 1.
The prefix column in Table 1 is non normative. The namespace URI column is normative.
A severity is
one of the three instantiations of resources,
published in the assertion severity linkbase (A.2).
The name of the severity element conveys the severity level (Error, Warning or OK).
An assertion-unsatisfied-severity relationship MAY be used to associate an assertion with the severity level that should apply when this assertion is not satisfied.
To declare an assertion-unsatisfied-severity relationship an XLink arc MUST:
The arcrole value
is declared in the normative schema for messages.
This specification prescribes certain constraints on the components that may be linked by assertion severity relationships.
The source of an
MUST be an element in the
The target of an assertion-unsatisfied-severity relationship MUST be one of the severity elements (seve:assertionSeverityTargetError).
An assertion MUST NOT be associated with more than one severity element by an assertion-unsatisfied-severity relationship (seve:multipleSeveritiesForAssertionError).
Where an assertion is not associated with a severity element by by an
assertion-unsatisfied-severity relationship, processors
MUST treat the assertion as if it has a severity of
This section contains XML files that form part of this specification. Each document has a standard Publication URL, at which the normative copy of the document is published. A non-normative copy of each document is included in this appendix for convenience.
All references to these documents made for the purposes of DTS Discovery MUST resolve to the Publication URL, after applying XML Base processing (where applicable) and resolving any relative URLs.
It should be noted that the path component of a URL is case-sensitive, and so must match exactly. Further, alternative hosts and schemes that happen to resolve to the same location are not considered equivalent and may not be used. See [URI] for more details on URL equivalence.
The requirement to reference documents by Publication URL does not prevent processors from substituting local copies of the documents for performance or other reasons.
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.
|19 April 2016||
Specification published at Recommendation status.
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 Formula Working Group up to and including 19 April 2016. 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.