• Blog
  • Downloads
  • Purchase
  • Contact
TopQuadrant, Inc
  • Solutions
    • Wrap Column 1
      • Learn How Data Governance is Better Enabled using Knowledge Graphs
      • Manage Taxonomies or Ontologies
      • Manage Your Reference Data
      • Lower Cost Of Regulatory Compliance
    • Wrap Column 2
      • Manage Metadata and Data Lineage
      • Bridge Metadata Silos to Connect Business and Technical Data
      • Improve Search
  • Products
    • Wrap Column 1
      • TopBraid Enterprise Data Governance (TopBraid EDG)
      • TopBraid EDG Packages
      • ► EDG–Vocabulary Management
      • ► EDG–Metadata Management
      • ► EDG–Reference Data Management
      • ► EDG–Business Glossaries
    • Wrap Column 2
      • TopBraid EDG Additional Modules
      • ► TopBraid Tagger and AutoClassifier
      • ► TopBraid Explorer
      • IDE:
      • TopBraid Composer – Maestro Edition
  • Services
    • Wrap Column 1
      • Professional Services
      • Solution JumpStart Program
      • Support Portal
      • Learning Center
    • Wrap Column 2
      • Training Overview
      • TopBraid EDG Training
      • Intro to Semantic Standards with TopBraid Composer
      • TopBraid Technology Training
  • Resources
    • Wrap Column 1
      • Product Videos
      • Webinars
      • White Papers
      • Learning Center
    • Wrap Column 2
      • Product Documentation
      • FAQ
      • Support Portal
      • Case Studies
  • Company
    • Wrap Column 1
      • Customer Case Studies
      • News and Events
      • Careers
    • Wrap Column 2
      • About Us
      • Partners
  • Technology
    • Wrap Column 1
      • TopBraid Technology Overview
      • TopBraid Teamworks Framework
      • TopBraid Data Platform
      • What Are Knowledge Graphs?
    • Wrap Column 2
      • SHACL
      • GraphQL
      • SPARQL Web Pages (SWP)
      • SPARQLMotion
      • SPIN (SPARQL Rules)
Select Page

Why Effective Metadata Management Needs Knowledge Graphs

by Jesse Lambert | Jul 27, 2020 | The Semantic Ecosystems Journal, Data Governance, TopBraid EDG, Data Lineage, metadata management, Knowledge Graphs

In a recent report, “Augmented Data Catalogs: Now an Enterprise Must-Have for Data and Analytics Leaders, September 2019“, Gartner discusses the importance of Knowledge Graphs for effective metadata management. The report points out that a solution supporting effective metadata management must span data catalogs, business glossaries, data lineage information, rules, semantic connections and more. Spanning all these items requires connecting them, and that is what a Knowledge Graph is very good at. Further, it creates connections in a flexible and evolvable way.

A key problem with the traditional approaches and products for data and metadata management is that they are not easily connectable, and result in more metadata silos. These silos don’t help in making data more valuable, usable, searchable, discoverable (or any of the other good ‘-able’ words).

 

 

 

So what is a Knowledge Graph? 
First, it is not a black box. It is yours to define, evolve and use, because it is based on open standards for semantic graphs.  These open standards allow it to represent any knowledge domain.  And by represent, I mean to capture in a graph not only facts about entities you are interested in, but also classes properties and rules that define these entities.  No more hard-coding of business logic in code.  Knowledge Graphs are a “smart” approach to meaningfully bridging enterprise metadata silos by:
 

  • Enabling connections between any kind of data
  • Capturing and preserving meaning
  • Supporting the business value of data (e.g., data quality, lineage, etc.)diagram below shows:

For example, the diagram below shows:

 

  • In the lower section of the diagram, a Knowledge Graph fragment saying that a person (James) has a parent (Andrew) and his eyes are blue – these are our data facts.
  • In the middle section, a Knowledge Graph fragment saying a person will have two parents, an eye color and that a male parent is a father – our model of a person.
  • In the upper section, a Knowledge Graph fragment capturing a rule that says that if both parents have blue eyes, that person has blue eyes as well – further extension or enrichment of the model with rules.

With this, even if we did not know James’ eye color, but knew that his parents eye color and their eyes were blue, our Knowledge Graph could infer that James has blue eyes.

All the layers of the Knowledge Graph – data facts, models, rules, reside together or are connectable.

Let’s now take a look at another example, shown in the next diagram. For governance, version control, access, and many other reasons, you may want (and need) to maintain different knowledge graphs. Below we have three different knowledge graphs named KG1, 2, and 3:

  • In the first, KG1, we are doing data asset management, for example, mapping data elements to glossary terms, elements to elements, flagging PII, assigning stewardship, and other great things.
  • In KG2, we are doing technical asset management
  • In KG3 the focus may be on the enterprise asset management

As separate, naturally modular, efforts, each of them is very manageable and relatively quick to be created, but by bringing them together we can self-compose information that never existed before.

For example, we may have a dataset with a PII data element in KG1 and a policy restricting physical location of PII storage in KG3. Bringing the graphs together, infers that the dataset is located in an area the policy is applicable; thereby, enabling us to enforce the policy.

Further, you can look at a Knowledge Graph with different lenses on. Below is a high-level, interactive lineage diagram (we call it a LineageGram) that is dynamically generated by metadata about our data ecosystem and the model describing it. In this example, metadata plays a role of the data facts captured in the Data Governance system. The model allows us to approach the information as a message that we can drill into when we need to explore deeper into the what and how.

For instance, on the right is a Patient Discharge Form. Suppose we want to understand the impact of changing one or more fields on the form? Here we see how complex processing of a patient discharge actually is, and this LineageGram allows us to assess the impact of this change. The paths of the lineage are interactive (clickable) and you can follow your nose as you see fit. Clicking on the Data Flow icon, I’m presented with that derivation (second image below).

I want to conclude this blog with a quote from Gartner’s report that I found to be insightful: “…a knowledge graph grows and becomes more comprehensive as more metadata sources are ingested, and business users enrich it with context and semantics.”

Recent Posts

  • Data Cataloging with Knowledge Graphs
  • Information governance 101: The regulatory compliance survival kit
  • Overview of TopBraid EDG Ontologies
  • Q4 2020 Newsletter
  • Automating the Mapping of Data Elements to Business Terms

Recent Comments

  • Brenton on Creating Web Services with the TopBraid Platform
  • naprzegladarkegry.blogspot.com on TopBraid Enterprise Vocabulary Net
  • Irene Polikoff on How to: Publish your Linked Data with TopBraid Live SPARQL Endpoints
  • Irene Polikoff on Ontologies and Data Models – are they the same?
  • Chino on How to: Publish your Linked Data with TopBraid Live SPARQL Endpoints

Archives

  • January 2021
  • November 2020
  • October 2020
  • September 2020
  • August 2020
  • July 2020
  • June 2020
  • May 2020
  • April 2020
  • March 2020
  • February 2020
  • January 2020
  • December 2019
  • November 2019
  • October 2019
  • September 2019
  • August 2019
  • July 2019
  • June 2019
  • May 2019
  • April 2019
  • March 2019
  • December 2018
  • November 2018
  • October 2018
  • August 2018
  • July 2018
  • June 2018
  • May 2018
  • March 2018
  • February 2018
  • January 2018
  • December 2017
  • November 2017
  • October 2017
  • September 2017
  • August 2017
  • July 2017
  • June 2017
  • May 2017
  • April 2017
  • March 2017
  • February 2017
  • January 2017
  • December 2016
  • November 2016
  • October 2016
  • September 2016
  • August 2016
  • July 2016
  • June 2016
  • May 2016
  • April 2016
  • February 2016
  • January 2016
  • December 2015
  • November 2015
  • October 2015
  • September 2015
  • August 2015
  • July 2015
  • June 2015
  • May 2015
  • April 2015
  • March 2015
  • February 2015
  • January 2015
  • December 2014
  • November 2014
  • October 2014
  • September 2014
  • August 2014
  • July 2014
  • June 2014
  • May 2014
  • April 2014
  • March 2014
  • February 2014
  • December 2013
  • November 2013
  • October 2013
  • July 2013
  • June 2013
  • May 2013
  • April 2013
  • March 2013
  • January 2013
  • July 2012
  • June 2012
  • May 2012
  • April 2012
  • February 2012
  • December 2011
  • November 2011
  • September 2011
  • August 2011
  • July 2011
  • June 2011
  • April 2011
  • March 2011
  • February 2011
  • January 2011
  • December 2010
  • November 2010
  • October 2010
  • August 2010
  • July 2010
  • May 2010
  • April 2010
  • March 2010
  • February 2010
  • January 2010
  • December 2009
  • November 2009
  • October 2009
  • September 2009
  • July 2009
  • June 2009

Categories

  • Uncategorized
  • The Semantic Ecosystems Journal
  • topbraid
  • life sciences
  • SPARQL
  • Ontologies
  • Semantic
  • metadata management
  • GDPR
  • GDPR
  • metadata management
  • Governance
  • GraphQL
  • Big Data
  • Linked Data
  • Reference Data Management
  • TopBraid RDM
  • Data Governance
  • ontology
  • collaborative ontology management
  • TopBraid EVN
  • TopBraid EDG
  • SHACL
  • TopBraid EDG
  • Data Lineage
  • FIBO
  • Financial Services
  • Data Lineage
  • FIBO
  • Linked Data
  • Linked Data
  • TopBraid EVN
  • SHACL
  • Ontologies
  • IDMP
  • TopBraid EVN
  • Financial Services
  • News
  • Mentions
  • Press Release
  • Newsletter
  • Events
  • Webinars
  • Knowledge Graphs
  • taxonomies
  • Data Cataloging
  • Business Glossaries

Meta

  • Log in
  • Entries feed
  • Comments feed
  • WordPress.org
  • About Us
  • Privacy Statement
  • Legal
  • Terms of Use
  • Twitter
  • RSS
Copyright 2020 TopQuadrant, Inc. All Rights Reserved.