Skip to content

C.4.4. Risk & Control Framework

Model-driven EKG access control mechanisms.

The capability Risk & Control Framework (C.4.4) is part of the capability area Data Governance in the Data Pillar.

Model-driven EKG access control mechanisms.

Warn

Work in progress

Note

The EKG Platform Team is about the delivery aspects of delivering new technical functionality in the service layer that manages the EKG aka the EKG/Platform. This is not about managing the "EKG Center of Excellence" as a whole.

  • The organization has one (or many) officially designated glossaries
  • Level of review by subject matter experts (SMEs)
  • Level of change management including versioning, approval, audit trail
  • Level of communication and ready availability
  • Terms have a full business definition
  • Business definitions also use a vocabulary with cross-references
  • Definitions traced to their source with change triggering
  • Level of examples including edge case instances, which can expose vagueness or ambiguity
  • All terms mapped to an ontology definition
  • Level of review by ontology experts
  • Level of review by application experts or data experts
  • Level of coverage of use cases
  • Relationship to official business glossaries or data dictionaries
  • Mapping to business models including processes, objectives, key performance indicators (KPIs)
  • Segregation of vocabularies by community
  • Reuse of glossaries across communities
  • Support for different natural languages
  • Searchability
  • Completeness of reverse mapping from ontologies to in-scope glossary for terms and definitions
  • Generation of glossaries from ontologies
  • Relationship amongst terms (synonyms, abbreviations)
  • Export to alternative representations e.g. web page, spreadsheet
  • Managing proper nouns (names of business entities, products etc) and mapping to individuals in the EKG

Maturity Level 1

  • Business terms for EKG use cases are captured and mapped to an ontology (possibly as simple labels)

Maturity Level 2

  • Relevant terms (for EKG use cases) are associated with the use case independently of their corresponding ontologies

Maturity Level 3

  • Existing glossaries within the organization, within the scope of supported use cases, are mapped to ontologies and imported into the EKG
  • Terms are grouped into vocabularies for reuse in different communities
  • Vocabularies include local textual definitions as well as being mapped to ontologies
  • Community level vocabularies able to import common vocabularies reusable in many communities: allow for multiple levels from local to global
  • Support for synonyms and abbreviations within vocabularies
  • Vocabularies use general principles of modularity
  • Ontologies presented to different communities in their own language
  • Natural language used for definitions links to other terms used
  • Terms are searchable via the knowledge graph interface
  • Generate vocabularies from existing data models or ontologies
  • Ontology logic is presented to business users as natural language

Maturity Level 4

  • Ontology logic is presented to business as natural language
  • EKG is the authoritative source for all terms, scoped by community, context and use case
  • The governance processes for all new terms (and changes) are managed directly within the EKG
  • The results of ontology inferencing are presented in business natural language
  • Use of ontology logic to validate use of vocabulary terms
  • Management of homonyms and disambiguation of terms---through being mapped to different concepts
  • Use of business terms in natural language queries
  • Techniques for disambiguation e.g. allowing business users to select the intended meaning
  • Use of textual analytics to suggest modifications to vocabulary/ontology (lemmatization)
  • Use of vocabularies to match internal databases or external data sources for linked data, and establish sameAs links

Maturity Level 5

  • Terminology is used to support natural language processing (NLP) of unstructured data for the EKG
  • Use of reference data from the EKG to support entity resolution (in EKG context or elsewhere)

Value

Warn

Work in progress. Explain how EKG contributes value and how this capability or capability- enables higher levels of maturity for the EKG (which in turn provides more value to the business)

Traditional Approach

Warn

Work in progress. Explain how things are done today in a non-EKG context

EKG Approach

Warn

Work in progress. Explain how the given Capability or Capability Area would look like in a mature EKG context.

Use Cases

Warn

Work in progress. List examples of use cases that contribute to this capability, making the link to use cases in the catalog at https://catalog.ekgf.org/use-case/..

Comments