Universal Category (Domain / Structural Category)

A Universal Category is a high-level taxonomy node used to organize a broad domain and to provide reusable building blocks for many concrete (product-level) categories.

Universal Categories answer: “What broad domain does this product belong to?” Examples: Medical Equipment, Electrical Equipment, Industrial Tools, Process Automation.

What Universal Categories are used for

  • Navigation & discovery: keep large taxonomies readable and searchable.
  • Reusable attribute building blocks: define common attribute groups that many concrete categories reuse (e.g., “Compliance”, “Operating Conditions”, “Installation”, “Safety”, “Documentation requirements”).
  • Governance scope: assign experts/stewards at domain level and inherit governance down the tree.
  • AI classification support: give AI a strong domain anchor (medical vs electric vs chemical) before it picks a concrete category.

How Universal Categories relate to other categories

  • Universal Categories usually sit above concrete categories (as parents or grandparents).

  • Concrete categories inherit:

    • shared attribute groups (if your template inheritance uses the hierarchy),
    • shared terminology guidance,
    • shared governance rules (who reviews what),
    • shared “documentation expectations” (e.g., always require datasheet + certificate in this domain).

What Universal Categories are NOT

  • Not product creation points. You typically do not create canonical products directly in universal categories.
  • Not identity definitions. Identity rules belong to concrete categories (the product-level template).
  • Not “facets”. A universal category is still part of the taxonomy structure; facets are separate browsing dimensions.
  • Keep Universal Categories stable and domain-meaningful (they should not change daily).
  • Avoid “catch-all” nodes that don’t add structure.
  • Prefer “domain/discipline” groupings over marketing groupings.
  • Treat them as template anchors: a place where you maintain common attribute groups once and reuse them everywhere.

Optional note (conceptual analogy)

Universal Categories in Actualog play a similar role to cross-section “aspects” in eCl@ss ADVANCED: reusable, cross-cutting property blocks applied to many product classes. The difference is that eCl@ss “aspects” are a separate structural element (not a taxonomy node), while your Universal Categories are part of your category hierarchy.