InfoLibrarian™ · Knowledge platform framework

Meaning as a first-class platform capability.

A full enterprise semantic layer—not a query-schema-only layer. Start with the metamodel: the types, relationships, and rules that make meaning governable. Business models sit on top. Glossaries, graphs, lineage, and AI context hang on that foundation. What the industry calls semantic layers and knowledge graphs today is what this framework was designed to do.

Platform → Heritage →

Full Enterprise Semantic Layer Capability Model

More than logical models or query metrics: business language, graph relationships, and mappings to physical systems, without replacing systems of record. Start with the metamodel; business models sit on top of it. Capability view first, detail table below.

InfoLibrarian Platform Capabilities — enterprise semantic layer capability view InfoLibrarian Platform Capabilities layered model: knowledge services; business language; business models sitting on the metamodel; property-graph metamodel foundation; semantic mappings lineage and APIs; physical systems of record including data catalogs. CONSUME LANGUAGE BUSINESS METAMODEL CONNECT PHYSICAL Knowledge services Search · Discovery · Portals · Self-service · Context for apps & AI Business language & controlled meaning Glossaries Controlled vocab Taxonomies Thesauri Folksonomies Business models & ontologies (sit on the metamodel) Ontologies · capabilities · value streams · products · processes · domains · subject areas Metamodel first: the property-graph knowledge graph core EMM foundation · entities · relationships · types · where you start Connect meaning to the estate Semantic mappings Lineage & impact Context services API Physical systems of record (Data Catalogs) Schemas · tables · fields · models · catalogs · applications (not replaced) Business models rest on the metamodel · metamodel is the EMM foundation

Enterprise capability view: consume → language → business models on metamodel → connect → physical

Business glossaries

Shared definitions of business terms and owners

Controlled vocabularies

Governed term sets for consistent naming and classification

Taxonomies

Hierarchical domain structures for navigation and classification

Thesauri

Preferred terms, synonyms, broader/narrower relationships

Folksonomies

Flexible steward or community tags, still under governance

Ontologies

Typed concepts and relationship rules for domain semantics. Business-level, sitting on the metamodel alongside business models.

Business models

Sit on the metamodel: capabilities, value streams, products, processes, domains, subject areas

Metamodel (graph core)

Where you start: entity and relationship types, expressed as a property graph

Knowledge graph (property graph)

Instances of meaning on the metamodel — entities and relationships as first-class objects. A property graph is the knowledge graph.

Semantic mappings

Concept → logical → physical (terms, models, schemas, tables, fields, systems)

Lineage & impact

Dependencies and change impact across the estate

Context services API

Adapters and APIs that expose meaning to applications and portals

Knowledge services

Search, discovery, and self-service for business and technical users

See the Framework in Customer Success →

Enterprise Metadata Management

EMM is where you start: design the metamodel, then capture, connect, and activate meaning across the estate. That foundation powered scalable programs and is more critical now for AI, semantic layers, and knowledge graphs than when it was first proven.

Where EMM goes next · open source

EMM 2.0 — the Enterprise Metadata Management Manifesto

EMM is where you start. EMM 2.0 is where it continues — an open source, vendor-neutral framework on modern graph technologies, published through Data Trust Engineering, founded by Brian Brewer in 2025. The same discipline that ran inside enterprises under licence, now with reusable code, battle-tested patterns and tools you control. No vendor lock-in.

Read the EMM 2.0 Manifesto → datatrustmanifesto.org

Classic era · 2005–2020

Classic Metadata Management & Governance Building Blocks

What the discipline looked like when it ran as a licensed product inside the enterprise. The aspects below are the classic model — EMM 2.0 carries the same concerns onto an open substrate.

Technical Metadata Aspect
  • Big data metadata
  • Metadata ingestion
  • Schema
  • Data lineage
  • Impact analysis
  • Computational
  • Operational metrics
Business Metadata Aspect
  • Property Graphs, Knowledge Graphs, and Ontologies
  • Business glossary
  • Taxonomies
  • Semantics
  • Data products
  • Stewardship workflows
  • Data marketplaces
Enterprise Data Marketplace Aspect
  • Single sign-on
  • Governance dashboards
  • Business perspectives
  • Consumer workflows
  • Democratization
  • Shopping experience
  • AI Chat UX
Metadata Management Program
Operational Observability
Stewardship & Product Lifecycle
Metadata Platforms

EMM 2.0: The Framework, in the Open

Everything above was proven inside enterprises under licence. The same discipline now continues as EMM 2.0 — developed in the open through Data Trust Engineering, with the patterns published rather than sold and AGP as the engine. Metamodel first, still.

EMM — PROVEN IN THE ENTERPRISE2005–2020Metamodel firstCapture · Connect · ActivateShipped into 30+ enterprisesClosed product, licensedGoverned semantics, relationships as datasame disciplineEMM 2.0 — DEVELOPED IN THE OPEN2025 onwardMetamodel firstCapture · Connect · Activate · ProveOpen patterns, open engineData Trust Engineering · AGPGraph databases, local AI, agent-nativeThe method did not change. The substrate did — and this time the patterns are public.