skills.rest
cartography-cncf
cartography-cncfOFFICIAL
Explore all skills by this author →
GitHub

enrich-ontology

Map Cartography nodes into the Ontology system via semantic labels or canonical nodes.

4.0k|550|Updated Feb 27, 2019
Search Tags:#ontology#schema#data-integration#cartography#semantic-labels#ontology-nodes#canonical-nodes
One-click install
npx skills add https://github.com/cartography-cncf/cartography --skill enrich-ontology
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: enrich-ontology
Source: https://github.com/cartography-cncf/cartography/tree/main/.agents/skills/enrich-ontology
Command: npx skills add https://github.com/cartography-cncf/cartography --skill enrich-ontology

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Map Cartography nodes into the Ontology system using semantic labels (UserAccount, DeviceInstance, Tenant, Database, ObjectStorage, FileStorage) or canonical nodes (User, Device). Use when the user asks to add ontology mapping, expose a node as a semantic label, normalise identity / device data across providers, enable cross-module queries, or wire _ont_* properties.

Core Features & Use Cases

  • Semantic labeling: adds labels (e.g. UserAccount) and prefixed properties (ont*) to source nodes during ingestion to enable cross-provider queries.
  • Canonical nodes: create (:User:Ontology) / (:Device:Ontology) nodes that aggregate data from multiple sources.
  • Schema-driven mapping: provides rules and examples for OntologyFieldMapping, ExtraNodeLabels, and required fields to drive ontology integration.

Quick Start

Map a Cartography node into the Ontology system.

Frequently Asked Questions about enrich-ontology

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I map Cartography nodes into an ontology system?▼

To map Cartography nodes into an ontology system, you apply semantic labels like UserAccount or DeviceInstance and prefix properties to source nodes during ingestion to enable cross-provider queries.

What is the difference between semantic labels and canonical nodes for data integration?▼

Semantic labels add tags like UserAccount to source nodes during ingestion, whereas canonical nodes create aggregate entities like (:User:Ontology) that consolidate identity and device data from multiple providers.

Do I need specific schema field mappings to normalize identity data across providers?▼

Yes, normalizing identity data across providers requires ontology field mappings with primary identifiers marked as required fields, alongside support for ExtraNodeLabels to drive the integration.

What is the best way to enable cross-module queries across different data providers?▼

The best way to enable cross-module queries is wiring `_ont_*` properties and applying semantic labels to source nodes, which normalizes identities and allows queries to span across different data providers.

When should I not use canonical nodes for ontology mapping?▼

You should avoid using canonical nodes when your scenario strictly requires preserving individual provider context without aggregation, as canonical nodes consolidate multiple sources into single normalized entities.

Related Skills

Explore More Data & Analytics Skills→
cartography-cncfcartography-cncf
4.0k

create-module

Scaffold a complete Cartography intel module with sync pattern and tests.

Official
Advanced
faisalanjumfaisalanjum
3

test-re-3layer-bot

Execute Cypher queries against a Neo4j graph database to retrieve company tickers.

Community
Basic
cartography-cncfcartography-cncf
4.0k

analysis-jobs

Add JSON-encoded Cypher analysis jobs to Cartography modules for post-sync graph enrichment.

Official
Advanced
TeamSparkAITeamSparkAI
18

mcpgraph

Build no-code MCP servers using YAML graphs with JSONata and JSON Logic.

Official
Advanced