Enterprise Ontology-like Things

Ontology-like things (a.k.a. knowledge graph systems) are becoming increasingly important.  Ontology-like things are machine-readable maps that help you understand your data and turn that data into information to make use of that data.

It is critically important to get those ontology-like things right because they will drive work in the information age.  As this LinkedIn post points out "layering" is important when you construct your "enterprise ontology" and provides this graphic of what layers make up such an enterprise ontology:

There are other dynamics also.  Modularity when creating ontologies is important so that pieces can be reused effectively.  Access is also important; some ontologies will be publicly available while other ontologies will be private.

Remember; when you think of "ontology", recognize that there are many different approaches to representing "ontology-like things" in machine-readable form: (larger image)


Quality matters.  Currently, there is not really an agreed upon way of measuring the quality of an ontology-like thing.  But good, quality ontology-like things will work; bad ontology-like things will not get you where you want to go.

Ontology-like things need to be maintained and have other life-cycle considerations.

Today, there is a lot of knowledge represented in unstructured and semi-structured form that needs to be structured.  Also, while some knowledge that can be considered "structured" or "semi-structured"; that structure might be for the presentation of knowledge as contrast to the meaning of that knowledge which make using or reusing that knowledge challenging.

Some, but not all, knowledge will be transitioned from unstructured and semi-structured formats with a focus on the meaning of information as contrast to the presentation of information.


A key thing to understand is that eventually hybrid AI will prevail. As Alan Morrison points out in this article; different AI have different capabilities.  As knowledge "moves around" between unstructured, semi-structured and structured forms with a focus on presentation versus meaning; the right balance will emerge.

All this knowledge will be connected in some way into a "fabric" or "mesh" or "assembly" of knowledge.  Lean Six Sigma techniques and principles will be applied to keep quality where it needs to be.  Enterprises that leverage this fabric will potentially prevail over those that do not as new approaches to performing tasks and processes are created.  Imagine something like Engine B's "Copilot"  that sits on top of a financial reporting scheme that is connected to a properly created XBRL taxonomy. that works within an expert system for creating financial reports.  Many have talked about "algorithmic regulation" (see page 18) but few can actually do it.  Apply design patterns and logic patterns to build powerful yet safe software systems using not "silo thinking" but rather "systems thinking".

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