One Accountant's Perspective on Knowledge Graphs

Here is one accountant's perspective on knowledge graphs.  My overall philosophy and technique is summarized in the document Logical Digital Twins of Financial Reports which is an accumulation of about 20 years of trying to figure out knowledge graphs.  The methodology that I use summarized by the Seattle Method.  The tools that I use can be understood by using Auditchain Luca, and here is information relating to using that software. And finally, these use cases and test cases helps you understand what I can do with knowledge graphs.

Happy to take any feedback what improves that I am trying to do with knowledge graphs. Ping me on LinkedIn.

I have been told by others that I have a unique approach to knowledge graphs.  This blog post summarizes that approach which has a focus on high quality, leverages a high level model to manage complexity to make creating software approachable to business professionals, uses Lean Six Sigma principles and philosophies, and I come at this holistically.


Admittedly, I am what has been described as an "accidental taxonomist" (another term used is "dinker").   That could be a good thing in some ways and perhaps a bad thing in other ways.  My approach to figuring out knowledge graphs started by being very naïve but I think that I ended up at a better place because of that naiveite.  Allow me to explain.

My professional background is as a certified public accountant (CPA, also known as a CA).  I have a degree in business with a concentration in accounting, I started my career as an auditor with Price Waterhouse, and ended up becoming an accounting information systems consultant.  My career took a significant turn in 1998 when I introduced the idea of what became XBRL to my professional trade association, the American Institute of Certified Public Accountants (AICPA).  XBRL is now a global standard used around the world. The FASB publishes the taxonomy for US GAAP and the IFRS Foundation publishes an XBRL taxonomy for International Financial Reporting Standards (IFRS). The U.S. Securities and Exchange Commission (SEC) has been collecting financial reports from public companies using XBRL for over ten years and the European Single Market Authority (ESMA) has been doing the same for listed companies for I believe three years.

I learned to program a bit using VBA in Excel and then also used Microsoft Access and VBA to build all sorts of tools that would help me in my daily work.  Then my involvement in creating the Extensible Business Reporting Language (XBRL) technical specification and more importantly the XBRL taxonomies for US GAAP and IFRS I was thrust into a completely new world.

Literally, I could not tell you the difference between "syntax" and "semantics" in 2002.  But I was building XBRL taxonomies, things did not seem to work the way it seemed they should work, I did not understand why, and so I started trying to figure out why things did not work.  That lead me down a path which is documented in what amounts to my "lab notebook".

Listening to people like John Sowa, Barry Smith, Frank Puppe, Bob Kowalski, Harold Boley, William Kent, and others; I recognized that many others were trying to figure out the same sorts of things that I was trying to figure out.

The conclusions that I ended up reaching are instantiated in the documentation and examples that I have come up with.  If anyone thinks there is a better way; I am all ears.  I just want to figure all this out and apply it to financial accounting, reporting, auditing, and analysis.  At the same time I might suggest that what I have learned might be useful to others in other areas of knowledge.

Comments

Post a Comment

Popular posts from this blog

Relational Knowledge Graph System (RKGS)

Image
Relational Knowledge Graph System (RKGS) is an interesting idea that combines the relational paradigm and the knowledge graph paradigm.  This documentation, Why RKGS , explains the idea. This gets even more interesting with the notion of "relational AI".  RelationalAI is described as follows by the company of the same name, Relational.ai : “RelationalAI is a cloud-based relational knowledge graph management system, with state of the art probabilistic processing and declarative reasoning at scale to make developing Data Applications a superpower for your business.” This notion of knowledge graphs represented in relational databases fits into my belief that knowledge graphs have two aspects: the expression SYNTAX and the logic of what is expressed or SEMANTICS. While the LOGIC of a knowledge graph is always the same regardless of technical syntax used to express that logic; there are many, many different technical syntaxes that can be used to represent a knowledge graph. There
Read more

Graph Hairball

Image
Knowledge graph system logic, the "things" and "relations between things" that  graph theory calls "vertices" (a.k.a. nodes, points, entities, things) and "edges" (a.k.a.  links, lines, relations, associations), looks like a big graph hairball as some people call it an example of which you can see here: Why?  This common view of a graph is because there has to be some "general view" of the information provided by the graph.  This is just like a general view of the information within a relational database is a table ; a set of ROWS and COLUMNS for exactly one table at a time. So what is interesting is that with a graph database the default view is everything in the graph of knowledge.  Whereas the default view of everything in a relational database is one table at a time. Further, it does not really matter whether the information that populates your knowledge graph comes from, say, CSV files, Excel, JSON, XBRL, RDF, PROLOG or whateve
Read more

PLATINUM Business Use Cases, Test Cases, Conformance Suite

Image
A brick wall is made of exactly two things: bricks, mortar. But a brick wall created by a master craftsman, or mason, and a brick wall created by a “weekend warrior” with no knowledge of masonry will be very different. Master craftsmen are created and that process takes time and effort. This blog post is a first prototype that brings several things together into one useful resource for business professionals.  It pulls together the human readable information of the Showcase of Reports   and the machine readable information of the Conformance Suite of XBRL-based Financial Reports Prepared using the Seattle Method .  Then, I want to incorporate the information found in these PLATINUM XBRL-based Financial Report Examples . The three resources can be useful and used independently; but they are even more useful when used together.  Business professionals really could not care a less about the technical details of getting some result that they want.  But technical professionals need to under
Read more