UJG / UJG 1.0 Release Candidate 1 /
W3C Community Group Draft Report

Artifact

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 .

Status
CG-DRAFT
Version
1.0-rc1
Published
2026-07-27
Last Update
2026-07-28
Editors
  • Seva Dolgopolov
Group
User Journal Graph Community Group
Repository
View Source
License
W3C-Software-and-Document

1. Overview

This optional module defines a minimal vocabulary for addressable artifacts that can participate as resources in a journey.

An artifact is a portable identity for a file, media object, archive, token, invite, report, protocol object, generated document, or other resource that participates in a journey. An Artifact is a concrete [UJG Effect] EffectResource, so effects can reference artifacts through generic producedRefs and consumedRefs. An artifact can also identify the source and target touchpoints where that resource is produced and consumed, and it can reference a localized human-facing name. The module does not define storage backends, transfer protocols, upload widgets, media processing, or artifact lifecycle state. Modules and profiles can specialize Artifact when they need more domain-specific semantics.

2. Terminology

  • Artifact: An addressable resource that may be produced, consumed, exchanged, or referenced during a journey.

  • Artifact name: A localized MessageMeta referenced by an artifact as its human-facing name.

  • Produced artifact: An artifact created, emitted, prepared, exported, generated, or made available by an Effect.

  • Consumed artifact: An artifact accepted, imported, read, redeemed, or otherwise used by an Effect.

  • Artifact source touchpoint: The touchpoint where an artifact is produced, exported, or made available.

  • Artifact target touchpoint: A touchpoint where an artifact is consumed, imported, redeemed, or otherwise used.

3. Artifact

An Artifact is an addressable portable resource identity and a concrete EffectResource. It can be referenced by producing or consuming effects, and it can identify source and target touchpoints when the resource crosses touchpoint boundaries. It does not define transfer, storage, rendering, security, or lifecycle semantics.

  1. An Artifact MUST be identified by an IRI.

  2. An Artifact MAY declare at most one nameRef.

  3. Every nameRef value MUST reference a MessageMeta.

  4. An Artifact MAY declare at most one sourceTouchpointRef.

  5. Every sourceTouchpointRef value MUST reference a Touchpoint.

  6. An Artifact MAY declare one or more targetTouchpointRefs.

  7. Every targetTouchpointRefs value MUST reference a Touchpoint.

  8. nameRef, sourceTouchpointRef, and targetTouchpointRefs MUST NOT create hidden Graph edges, change traversal behavior, assert delivery, or change Runtime event ordering.

classDiagram
  class Touchpoint
  class MessageMeta
  class EffectResource
  class Artifact {
    id
    nameRef
    sourceTouchpointRef
    targetTouchpointRefs
  }
  EffectResource <|-- Artifact
  Artifact --> MessageMeta : nameRef
  Artifact --> Touchpoint : sourceTouchpointRef
  Artifact --> "0..*" Touchpoint : targetTouchpointRefs

Example JSON node:

json 
{
  "@id": "urn:artifact:account-archive",
  "@type": "Artifact",
  "nameRef": "urn:l10n:message-meta:account-archive-name",
  "sourceTouchpointRef": "urn:touchpoint:old-server",
  "targetTouchpointRefs": ["urn:touchpoint:new-server"]
}
{
  "@id": "urn:artifact:account-archive",
  "@type": "Artifact",
  "nameRef": "urn:l10n:message-meta:account-archive-name",
  "sourceTouchpointRef": "urn:touchpoint:old-server",
  "targetTouchpointRefs": ["urn:touchpoint:new-server"]
}

4. Localized Names

artifact:nameRef links an Artifact to one MessageMeta that provides the artifact's human-facing name. Locale-specific Message nodes MAY use opaque values and argumentNames.

nameRef is descriptive metadata on the artifact. It does not determine production, consumption, transfer, storage, availability, rendering, or lifecycle state.

5. Effect Integration

The Artifact module introduces artifact-owned references:

  • artifact:nameRef links an Artifact to the localized MessageMeta used as its human-facing name.

  • artifact:sourceTouchpointRef links an Artifact to the Touchpoint where it is produced, exported, or made available.

  • artifact:targetTouchpointRefs links an Artifact to one or more Touchpoints where it is consumed, imported, redeemed, or otherwise used.

Production and consumption relationships are defined by [UJG Effect], not by this module. Effects use producedRefs and consumedRefs to point to Artifact nodes. Producers SHOULD NOT use those references to create hidden Graph traversal or to replace Graph Transition semantics.

Touchpoint metadata belongs to the Artifact, not the producing or consuming Effect. Effects declare only producedRefs and consumedRefs; the referenced artifact declares where it crosses touchpoint boundaries.

6. Non-Goals

Artifact does not define:

  • upload, download, or preview presentation

  • media-kind taxonomies

  • storage, CDN, filesystem, or database details

  • protocol delivery semantics

  • artifact lifecycle, freshness, or cache policy

  • validation of artifact payload contents

  • cross-touchpoint effect semantics beyond artifact-owned touchpoint metadata

The archived artifact implementation extension remains useful for generator-specific upload and preview hints, but those hints are not part of this module.

7. Normative Artifacts

This module is published through the following artifacts:

  • artifact.ttl: ontology, published at https://ujg.specs.openuji.org/tr/1.0/ns/artifact

  • artifact.context.jsonld: JSON-LD term mappings, published at https://ujg.specs.openuji.org/tr/1.0/ns/artifact.context.jsonld

  • artifact.shape.ttl: SHACL validation rules, published at https://ujg.specs.openuji.org/tr/1.0/ns/artifact.shape

Examples in this page compose the Core context with the Artifact context. Examples that use effects also compose the Effect context; examples that use touchpoint metadata also compose the Surface context; examples that use nameRef also compose the Localization context.

7.1. Ontology

The normative Artifact ontology is defined below and is published at https://ujg.specs.openuji.org/tr/1.0/ns/artifact.

7.2. JSON-LD Context

The normative Artifact JSON-LD context is defined below and is published at https://ujg.specs.openuji.org/tr/1.0/ns/artifact.context.jsonld.

7.3. Validation

The normative Artifact SHACL shape is defined below and is published at https://ujg.specs.openuji.org/tr/1.0/ns/artifact.shape.

The rules below define the remaining module semantics beyond the structural constraints captured by the SHACL shape.

  1. Identity only: Artifact identifies a resource; it does not define transfer, storage, rendering, security, or lifecycle semantics.

  2. Effect resource: Artifact is a concrete EffectResource and MAY be referenced by Effect producedRefs or consumedRefs.

  3. Graph preservation: Artifact references MUST NOT create hidden graph edges or change Graph traversal behavior.

  4. Localized artifact names: nameRef belongs on Artifact and references one MessageMeta. It is descriptive metadata and does not define rendering, transfer, storage, or lifecycle semantics.

  5. Artifact-owned touchpoint metadata: sourceTouchpointRef and targetTouchpointRefs belong on Artifact, not on Effect; effects only produce or consume resources.

  6. Graceful degradation: Consumers that do not implement this module MAY ignore Artifact semantics, but SHOULD preserve recognized JSON-LD data during read-transform-write when possible.

8. Examples

8.1. Minimal Example

8.2. Localized Name Example

8.3. Cross-Touchpoint Artifact Example

This example models a federated share as the resource crossing touchpoints. Effects only declare whether they produce or consume that resource.