Notion of the "Semantic Hive" or "Hive Plot"

Someone was explaining something to me and they used the term "semantic hive".  This blog post explains what I think a semantic hive is.  It could be the case that they are using that term "semantic hive" to describe something different; but I believing that what I am describing is necessary. Another term for what I am trying to describe is "hive plot".

To create a problem solving system you need to be sure to include all of the pieces of that system.  One of those pieces is the knowledge from some area of knowledge.  Users of that knowledge need to be committed to that knowledge in order for the system to work the way they want/need the problem solving system to work. But reality can get very messy.  The Cnyfin Framework, which is a sensemaking tool, helps one organize an area of knowledge into categories.  Those categories are:

  • Best practices: things that tend to be obvious even to people outside an area of knowledge. There tends to be only one way to do something which makes sense.
  • Good practices: things that are a bit more complicated but the subject matter experts within an area of knowledge that have skills and experience tend to agree on these practices.  Different groups can use different good practices as a matter of policies.
  • Emergent practices: things that are even more complex and subject matter experts within an area of knowledge tend to disagree with one another as to what the good practices are which leads to multiple different views, each which is reasonable based on the principles of an area of knowledge and the logical patterns of the situation. There tends to be tight, identifiable clusters of answers.  (For example, if accounting standards have ambiguity and accountants apply fundamental principles to figuring out a situation and say each of the Big 4 CPA firms; PWC, Deloitte, EY, KPMG; each come up with a view on how to handle that situation; each view could be correct)
  • Novel practice: this is similar to emergent practices except that there are no identifiable logical patterns of the situation and no identifiable principles that can be applied; but logical answers can be figured out but the clustering of answers is more spread out, not as tight.
A "semantic hive" or a "hive plot" is a group that has a similar view and have similar "ontological commitment" or "knowledge commitment". Effectively, each "semantic hive" or "hive plot" is mutually exclusive: you belong to one semantic hive or another semantic hive, you cannot belong to both because that would be illogical.

Here is an example.  Say you wanted to create a knowledge graph of the semantics of the U.S. Constitution.  If you tried to get everyone to agree with one single knowledge graph, this could be quite a challenge.  But, if you broke up the group of people trying to do this into "semantic hives" or "hive plots" such as "democrat" and "republican" and/or "conservative" and "liberal" figuring out what goes into that knowledge graph becomes significantly easier.  Then, you could use the semantic hive or hive plot created by the group you subscribe to most to perform reasoning.

A similar example related to financial reporting might be two areas of significant variability that I have notices in financial reports.  One is where the line item "Income (Loss) on Equity Method Investments" belongs on the income statement.  Another is the classification of equity as "Equity" or as "Temporary Equity" on the balance sheet.

What a "semantic hive" or "hive plot" offers is flexibility in the representation of knowledge in a knowledge graph. It also offers clarity as to which knowledge graph you subscribe to.  Perhaps there is a better or different term; this is more about the idea than the exact term.



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