Vocabulary and Data Catalog

On this page

This module teaches an architect how to use vocabulary as the shared language for mapped and governed data.

Learning objective

Understand vocabulary as the data language that mapping, search, filtering, stewardship, and governance all depend on.

What to learn

  • the purpose of vocabulary and vocabulary keys;
  • data-first vs model-first creation approaches;
  • how vocabulary usage reveals where a model is already embedded in the platform;
  • why missing or ambiguous keys create architectural friction later.

Vocabulary usage

Create vocabulary

Vocabulary keys

Exercises

  1. Open one existing vocabulary and inspect its usage.
  2. Identify one ambiguous or missing key.
  3. Draft how one new source should map into the current vocabulary model.
  4. Decide whether the scenario is better served by data-first or model-first vocabulary creation.

Architect judgment to reinforce

If the shared language is weak, everything downstream becomes harder: mapping, search, filters, validations, and stewardship decisions.