← Back to catalogue
Published

3D Scene / Environment

vr.wm-vrt-007 · wm-vrt-007-3d-scene-environment

Describe and govern one versioned spatial scene and its object graph, dependencies, intended presentation and behavior bindings.

World Models Information and virtual systems INF.VRT.3D

Bundle → Layer → Finding → Questions Filled

3 bundles · 3 layers · 5 findings · 10 questions

Scene composition What the scene contains and how it is arranged.

Scene graph

Nodes, transforms and referenced assets.

Node hierarchy

The objects in the scene and their spatial relations.

  1. Which nodes does the scene contain, and how are they parented and transformed?
  2. Which coordinate system, units and up-axis does the scene use?

Referenced assets

External meshes, textures and materials used.

  1. Which assets does the scene reference, in which versions?
  2. Under which licence may each referenced asset be used?
Interaction and behaviour What can happen in the scene.

Behaviours

Scripts, physics and interactive objects.

Interactive objects

Objects with behaviours, triggers or physics.

  1. Which objects respond to user or agent input, and how?
  2. Which scripts run in the scene, and from which sources?

Access and comfort

Accessibility and comfort settings for users.

  1. Which accessibility and motion comfort options does the scene offer?
  2. Are there content warnings, such as flashing lights, for users?
Versions and provenance How the scene was made and changed.

Authorship and versions

Authors, tools and version history.

Version history

Published versions and their changes.

  1. Which version of the scene is published, and what changed from the previous one?
  2. Who authored it, and with which tools or generators?

Classifiers Filled

Family
World Models
Category
Information and virtual systems
Entry kind
entity
Navigation path
NAV.INF.VRT.3D
Domain
INF.VRT.3D
Industry
Cross-industry
Tags
3dsceneenvironmentinf.vrt.3d

What it is Filled

A 3D scene or environment is a digital spatial composition of objects, geometry, materials, lights, cameras and behaviours arranged in a scene graph, which can be rendered, explored or interacted with. It is the assembled scene, not a single 3D asset, and differs from a whole virtual world with its users and economy and from a digital twin bound to a real counterpart.

In scope

  • Scene identity, revision, graph membership, instances, frames, transforms and bounds
  • Asset bindings, geometry and appearance requirements, animation, interaction declarations and runtime references
  • Accessibility, privacy, provenance, rights evidence, interchange losses and local acceptance records

Out of scope

  • Virtual-world accounts, economies and social governance
  • Avatar identity and personal lifecycle
  • Physical counterpart identity, digital-twin synchronization and truth claims
  • Simulation solver, scenario execution and safety-critical validation
  • Asset master lifecycle, legal rights adjudication, device control and rendering implementation

Why it exists Filled

Describe and govern one versioned spatial scene and its object graph, dependencies, intended presentation and behavior bindings.

Distinguishing features Filled

  • An assembled spatial composition, not a single mesh or texture asset.
  • Distinct from a virtual world, which adds persistent users, accounts and economies.
  • Unlike a digital twin, it need not correspond to any real object or place.
  • The scene graph and its behaviours, not the rendered images, are the thing described.

What robots and AI may and may not do Filled

Must not

  • Use assets in a scene against their licences.
  • Present a scene as a faithful reproduction of a real place or object when it is not.
  • Insert hidden scripts or tracking into a shared scene.
  • Remove authorship or provenance metadata.
  • Place content in a shared scene that harasses or endangers other users.

Only with a human decision

  • Publishing a scene to a public or shared platform.
  • Using a scene for training or safety-critical simulation decisions.

May

  • Load, inspect and describe scene contents and structure.
  • Navigate or act in a scene within the permissions given to the agent.
  • Report missing assets, licence gaps and performance problems.
  • Generate or edit scene drafts for human review.

Moral aspects Filled

  • Immersive scenes can cause motion sickness or seizures, so comfort and warnings matter.
  • Reproductions of real places, people or cultural sites raise questions of consent and respect.
  • Creators of reused assets deserve attribution and fair licensing.

Who is affected

  • Users exploring the scene
  • Asset creators and scene authors
  • People and places depicted

Owners Filled

Steward

The scene author or publisher that holds rights to the composition and maintains its versions.

Roles

Scene steward
Maintains scene identity, scope and release authority references.
Scene author
Proposes graph, asset and behavior changes with provenance.
Binding reviewer
Checks exact profile, conversions and validation evidence.
Experience reviewer
Reviews accessibility, comfort and privacy evidence for the target use.
Repository custodian
Enforces local access, integrity and authorized retention/disposition.

Master systems

  • Digital asset management system
  • Scene or level repository

Links to other meta-models Filled

references

  • WM-VRT-002 - Associate the host world without copying its participants, economy or lifecycle. Candidate optional binding; pin the adopted target revision before use.
  • WM-VRT-008 - Bind a separately mastered avatar representation. Candidate optional binding; pin the adopted target revision before use.
  • WM-VRT-001 - Reference counterpart alignment evidence without certifying twin fidelity. Candidate optional binding; pin the adopted target revision before use.
  • WM-VRT-003 - Delegate physics and simulation execution to a simulation record. Candidate optional binding; pin the adopted target revision before use.
  • WM-VRT-012 - Reference scenario-specific scene selection without owning scenario execution. Candidate optional binding; pin the adopted target revision before use.

aligned

  • glTF 2.0 - Candidate delivery binding; preserve scene selector, identity map and unsupported-feature losses.
  • X3D 4.0 - Candidate interactive scene binding with declared profile and components.
  • OpenUSD - Candidate layered scene description binding; resolve versions, variants and payload context.
  • WebXR Device API - Optional runtime interface only; draft status and capabilities require verification.
  • PROV-O - Conceptual provenance alignment; not a rights or fidelity certificate.

neighbor

  • WM-VRT-002 Virtual / Game World - Registry parent is a candidate contextual association, not mandatory containment or inheritance. A standalone offline scene needs no world. World lifecycle and participants stay external.
  • WM-VRT-008 Virtual Persona / Avatar - A scene may bind an avatar representation; it does not master the persona, account or permissions.
  • WM-VRT-001 Digital Twin - A scene may depict a counterpart without being a twin or proving real-world fidelity. Counterpart identity and synchronization remain external.
  • WM-VRT-003 Simulation and WM-VRT-012 Simulation Scenario - Store scene-specific bindings and expected observations only; solver lifecycle, scenario intent and run execution are delegated.
  • Asset repositories and delivery formats - A scene record is not a file or an asset library. Format-local array indices, paths and display names need a governed identity mapping. USD layers are not Vercy context layers.

parent

  • WM-VRT-002

What else AI and robots need to interact with it Filled

Identity and identifiers required Filled

  • Identified by the repository or platform identifier of the scene and its version.
  • Referenced assets are identified by their own asset identifiers and checksums.

Direct properties not applicable Not applicable

Not applicable

A 3D scene is a digital composition; its units, scale and coordinate system are recorded as scene metadata, not as physical properties.

Recognition optional Filled

  • Marked by a scene graph with nodes, transforms, materials, lights and cameras in a 3D scene format.
  • Often confused with a single 3D asset, a rendered video or image, or a full virtual world.

Capabilities and actions required Filled

  • Can be rendered, explored and interacted with in real time or offline.
  • Can be composed from and decomposed into reusable assets.

Hazards and failure modes required Filled

  • Flashing content or motion that triggers seizures or sickness.
  • Malicious scripts embedded in shared scenes.

Standards and interfaces required Filled

  • glTF 2.0 (ISO/IEC 12113) for transmission of scenes and assets.
  • X3D (ISO/IEC 19775) for interactive 3D scenes.
  • WebXR for presenting scenes in immersive browsers.

Context of use required Filled

  • Used in games, film, architecture, training, simulation and extended reality.
  • Increasingly generated or edited with AI tools.

Sources Filled

  1. glTF 2.0 Specification - Khronos Group
  2. Extensible 3D (X3D), Part 1, clause 4 Concepts - Web3D Consortium
  3. Introduction to USD - OpenUSD project
  4. WebXR Device API - World Wide Web Consortium
  5. XR Accessibility User Requirements - World Wide Web Consortium
  6. PROV-O: The PROV Ontology - World Wide Web Consortium
  7. ISO/IEC 12113 Runtime 3D asset delivery format (glTF 2.0), ISO and IEC
  8. ISO/IEC 19775 Extensible 3D (X3D), ISO and IEC
  9. WebXR Device API, World Wide Web Consortium

Open questions

  • Complete external source checks and immutable version pins, then restore independent provider review before canonical promotion.
  • Develop nested schemas and conversion fixtures for empty scenes, shared graphs, singular transforms, missing assets, variants, unsupported behavior and identity-preserving round trips.
  • Validate target-runtime accessibility, comfort, sensitive-data controls and resource envelopes; extend geodetic, advanced content and multiuser profiles only with additional evidence.
  • Independent external review is absent; Claude and Grok are skipped under the owner waiver.
  • Direct HTTP status and response hashes are unmeasured in this sandbox; the coordinator must run check_sources.py outside it. Browser text retrieval is not HTTP verification.
  • Mutable documentation version pins, complete source claim verification and normative status checks remain open.
  • Nested instance schemas, executable mappings, test scenes, adversarial fixtures and runtime implementation remain future work.
  • Geospatial and geodetic profiles, volumetric and procedural content, point-cloud extensions, detailed audio bindings and multiuser synchronization need separate profiles.
  • Licensing applicability, depicted-subject rights, local privacy rules and safety-critical use require qualified review.

Machine files

Provenance

world-models research · reviewable-draft

Built from: models/wm-vrt-007-3d-scene-environment/spec.yaml, ver-cy/world-models/card-supplements/wm-vrt-007-3d-scene-environment.json