D.1.1. Technology Architecture - EKG/Maturity

[giscus[bot]]

D.1.1. Technology Architecture - EKG/Maturity

Maturity Model for the Enterprise Knowledge Graph (EKG)

https://maturity.ekgf.org/pillar/technology/technology-strategy/technology-architecture/

[jgeluk]

Enterprise Knowledge Graph (EKG) - Technical Architecture

1. Unique Identifiers: Every object in the EKG is assigned a unique, permanent, and web-resolvable identifier. This allows for precise identification and retrieval of data points.

2. Semantic Meaning: The EKG architecture must support the assignment of machine-readable definitions to every data point. This ensures that the meaning of data is clear and can be understood by both humans and machines.

3. Distributed Storage: The EKG can store data points across multiple physical locations. This distributed architecture allows for scalability and ensures that data can be accessed from any point in the network.

4. Open World Assumption: The architecture must be able to handle multiple versions of the truth, reconciling differences based on context. This allows for flexibility in handling data from various sources and with different models.

5. Self-Describing Datasets: The datasets within an EKG are self-describing, providing information about their lineage, provenance, quality, and governance. This enhances transparency and trust in the data.

6. Measurement and Quality Control: The architecture must support the measurement of the quality and characteristics of the managed knowledge. This ensures that the data is fit for its intended purpose and allows for actionable insights.

7. Business Orientation: The architecture must link all information and associated artifacts to defined and prioritized use cases. This ensures that everything in the EKG has a known business justification and purpose.

8. Policy Enforcement: The architecture must support the modeling and automatic execution, enforcement, and auditing of entitlement, privacy, and business policies at the data point level.

9. Integration with Diverse Technologies: The architecture must be able to incorporate a heterogeneous set of technologies and data sources over time. This ensures that the EKG can evolve with the enterprise's needs and technological advancements.

10. Standards Compliance: The architecture should be based on open standards to ensure interoperability and compliance with governance procedures.

In summary, the technical architecture of an EKG is designed to handle complex, interconnected data in a way that is scalable, flexible, transparent, and aligned with business needs. It should be able to integrate with a variety of technologies and comply with open standards for data management.