This site is under heavy development. Content and features may change frequently.
UJG / Editor's Draft /
W3C Community Group Draft Report

Architecture

draft

Status of this Document

This report was published by the User Journal Graph Community Group . It is not a W3C Standard nor is it on the W3C Standards Track. Please note that under the W3C Community Contributor License Agreement (CLA) there is a limited opt-out and other conditions apply. Learn more about W3C Community and Business Groups .

Last Update
2026-01-28
Editors
  • Seva Dolgopolov
Group
User Journal Graph Community Group
Repository
View Source
License
W3C-Software-and-Document

1. Abstract

The User Journey Graph (UJG) standardizes user experience as computable data. It decouples the Definition of Intent (Design) from the Observation of Reality (Telemetry). This separation creates a single source of truth for Designers, Developers, and Analysts. As a deterministic protocol, it supports automation by AI agents across these roles, ensuring structural consistency.

2. Conceptual Stack

The standard is organized into five logical layers:

  1. The Core (Transport): The universal JSON-LD envelope. Ensures any tool—human or AI—can parse the file structure without ambiguity.

  2. The Graph (Definition): Defines the "Happy Path." It is the vocabulary for States, Transitions, and Composition (sub-journey referencing).

  3. The Experience (Semantic): Describes the journey in canonical human semantics (Steps, Touchpoints, Phases, Pain Points), enabling qualitative intent to be represented as data.

  4. The Runtime (Execution): Captures the "Actual Path." It records events as a causal chain.

  5. The Mapping (Conformance): Closes the loop. It overlays Reality(Runtime) onto Intent(Graph) to calculate conversion and detect friction.

3. Guiding Principles

  1. Graph First: User experience is an automata, not a list of URLs.

  2. Stable Identity: Entities must be named with URIs to survive refactors.

  3. Separation of Concerns: A "Journey" (the plan) is immutable; a "Session" (the instance) is ephemeral.

  4. Vendor Neutrality: The spec defines data shapes, not visualization rules.

4. Optional Modules

The Editor's Draft also publishes a parallel family of optional modules for capabilities that build on the core UJG layers without expanding the shared interoperability baseline. Earlier drafts called these "supported extensions", but the normative model is now module-oriented: optional capabilities that need interoperable graph terms publish their own ontology, JSON-LD context, and SHACL shape.

Optional modules MAY add semantics above the shared layers, but they MUST NOT silently redefine Core, Graph, Runtime, Experience, Mapping, or Metrics semantics. Capabilities that become universal across compliant implementations should graduate from the optional module family into the main spec family rather than remain optional add-ons.

5. Opaque Extensions

Core extensions remains the pass-through mechanism for vendor-private or deployment-specific JSON payloads on UJG node objects. Opaque extensions do not participate in standardized graph semantics, reference resolution, or profile conformance, even when their payloads happen to contain identifiers or structured JSON objects.