Natural or Neutral Formatted Information

One of the unique aspects of XBRL-based information is that the information is readable both by machines and by humans.  This article explains how that capability is achieved.

Simple "Hello World" Example

Here is a very simple "Hello World" example of XBRL-based information. (Here is the same report in the XBRL International test case format.)

This is the same information rendered for editing a report as opposed to reading the report:

Here is the same information in the form of a sharable viewer which you can use to have a closer look at this small Hello World! example.

Here is the same information in the form of a set of HTML pages that also provide a means of viewing the information from within the machine readable XBRL files.

How This Works

So the rendering of the information that you see by multiple different software vendors in multiple different but all very human readable formats is not a one off.  This  capability is by design. Here is a comparison of renderings from four different software applications which shows the proper rendering of the fundamental logical information patterns.  Here is what I call a "Showcase of Reports" which shows real reporting world use cases. Here is another showcase of reports which gives you more hands on experience with a report viewer provided by one software vendor.

Here is how the renderings are generated.

1. You start with the global standard XBRL technical syntax. That is the only technical artifact you need, no supplemental information needs to be provided for a report.
2. You apply a high-level model into which the technical syntax will always fit.  There is only one logical model, but different published versions of the model which are more or less understandable and some can be more enhanced than others.  The model is there in the XBRL technical specification, but it can be hard for a non-experienced person to see.  XBRL International tries to further explain the model in the XBRL Open Information Model. I try and explain the logical model as best as I can using the Seattle Method.  Here is a draft UML Model created by OMG for the Standard Business Report Model (SBRM).
3. You leverage the logical patterns of the "blocks" or "infons" of the information. Information is not random, there is a logic there in the information.  That logic is used to classify the information patterns.  Each pattern is represented such that the information is easy to understand.
4. Common knowledge is leveraged to make the logical patterns even easier to understand.  For example, there are patterns of single underscores and double underscores in information logic that represents numeric computations.
5. Create specialized software which enables both machines and humans to understand the information they are working with, leveraging #1, #2, #3, and #4 above.  Business reports including financial reports are knowledge graphs. Think semantic hypercube or semantic spreadsheet or something even more dynamic like a semantic pivot table.

While most of my examples show financial reports, these ideas relate to financial reports, other types of business reports, accounting working papers, audit schedules.  The only difference is whether information is financial or nonfinancial, internally prepared or prepared by an independent third party, and the level of granularity.

Think "Natural" or "Neutral" or "Logical Format"

I have been "collecting" the patterns of financial reporting since the very early days of XBRL's creation.  I created what I called "the patterns document".  I referred to these renders first as "neutral" format renderings.  But they are better described more as "natural" format renderings, driven by the logic of the information.  I have been reverse engineering financial reports since public companies have been providing XBRL-based information to the SEC beginning in about 2009.

Now, maybe you don't want a "neutral format", you are more picky.  No problem, you can use Inline XBRL and get "pixel perfect" rendering to the extent of the capabilities of HTML can provide.  But do you really need, or want, to go through the process of creating pixel perfect renderings for every report you want?  It would be near impossible to get people to agree on how information should be presented.  But you cannot dispute the logic of the information.  For example, a "roll up" pattern of information has the same logic for everyone.  That fact can be leveraged.

How This Can be Used

Effectively, these semantic pivot tables are going to change accountancy.  A new more modern approach to accountancy can be constructed using technologies that exist today. Think "logical digital twins".

Imagine one connected accountancy ecosystem, something similar to the Provenance Blockchain financial services ecosystem.  "Accountancy" includes internal management/cost reporting, external compliance reporting, internal and external auditing, financial analysis and regulation.  It includes accounting, reporting, auditing, and analysis.  Some call this "algorithmic regulation".

To make this all work, one needs humans and machines to be able to collaborate when working with the same information.  You do need to deal with the threat of inaccuracy. But that capability exists.

Another Example

Here is another example:

• Luca Viewer
• Pacioli Technical Analysis Validation
• JSON import file
• HTML Rendering
• Inline XBRL
• Raw XBRL Instance

Additional Information:

• Informatics for Accountancy
• Concept Arrangement Patterns
• Member Arrangement Patterns
• PROOF
• Special Purpose Logical Spreadsheet for Accountants
• Logic Systems
• Pesseract