Open Lore NetworkOLN
Network/Register/Canonical Entity Type Vocabulary
Gap Register
G-048Public

Canonical entity-type vocabulary — network vs franchise

Tier 2 — Structurally thin, not launch-blocking
Status
Open — not started
Owner
Creator
Why now
The bare-slug URL scheme is only collision-safe and AEO-consistent if the set of entity types is a fixed, shared vocabulary.
Related
Entry 002, Entry 026, B-003

Fix the controlled vocabulary of entity types, split into network-level reserved root paths (real-world) and franchise-level in-universe types, and define the cross-franchise alias relationship.

Why this matters

Entry 026 makes canon the default, unmarked namespace addressed by type (/lotr/characters/gandalf, /person/ian-mckellen). That only holds if types are a controlled vocabulary. Open decisions:

  • Network-level types (reserved top-level root paths, for real-world / cross-franchise subjects): person, and likely studio / company, work, place… — which ones, and their exact slugs.
  • Franchise-level types (in-universe, under /{franchise}/): characters, locations, artifacts, events, works, species, organizations… — the canonical list and singular/plural conventions.
  • Cross-franchise dedup / aliasing — when a shared figure appears in multiple franchises, the network entity is the canonical home and franchise references are aliases (ties to Entry 002 canonical-entity architecture and B-003 cross-franchise entity handling). Define the relationship and its rel=canonical behavior.
  • Type stability — a slug must survive a type re-classification (301 + stable internal id), since the URL is presentation, not identity.