Symbiotic Relationship Between Software, Knowledge, and Cognitive Problem/Work

A symbiotic relationship, symbiosis, exists between software, knowledge, and a cognitive problem/work which a subject matter expert is trying to solve/get done.  It seems as though if these four things are not properly matched it is hard to see the value of the software and/or the machine understandable knowledge.

People tend to associate symbiotic relationships with biological organisms.  However, in general terms, a symbiotic relationship refers to an evolved interaction or close interconnection between not only organisms of different species but other "interconnections".  For example:
  • Business partnerships: Companies often form symbiotic relationships in the form of business partnerships in order for both parties to thrive.  One example is a supplier/retailer relationships that benefit both parties.
  • Human relationships: Humans create friendships to support each other emotionally, socially, and/or intellectually.
  • Search engines and users: Search engines offer information and users of the search engine get answers to their questions.
What I am noticing is that if all of these pieces are not put together in a manner that subject matter experts (SMEs) can "touch and feel", they don't tend to understand the potential of the software or of the machine understandable knowledge.

Albert Einstein said, “Imagination is more important than knowledge. For knowledge is limited to all we now know and understand, while imagination embraces the entire world, and all there ever will be to know and understand.”  Just because something does not exist right now does not mean that it will never exist.

Additional Information:

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