← Back to catalogue
Published

3D Asset / Scene

vr.wm-med-006 · wm-med-006-3d-asset-scene

Describe one identified 3D media asset or authored scene, its spatial content, dependencies, interpretation profile and evidence for permitted use.

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

Bundle → Layer → Finding → Questions Filled

3 bundles · 4 layers · 6 findings · 12 questions

Content What the asset contains.

Geometry and materials

Shapes and surfaces.

Geometry

The geometric representation, units and level of detail.

  1. Which geometry types does the asset use, and in which unit and axis convention?
  2. Which levels of detail are provided?

Materials and textures

Surface materials and the texture files they reference.

  1. Which material model is used, and are all referenced textures present?
  2. Are textures embedded or referenced externally?

Scene graph

How objects are arranged.

Composition

Nodes, transforms, lights, cameras and animations in the scene.

  1. Which nodes, lights and cameras does the scene contain?
  2. Which external assets does the scene reference, and in which versions?
Format and provenance How the asset is packaged and where it came from.

Packaging

The file format, version and dependencies.

Format and version

The interchange format and its version.

  1. In which format and format version is the asset stored?
  2. Does the file validate against its format specification?

Origin

Who created the asset and from what.

  1. Who created the asset, and was it modelled, scanned or generated?
  2. Does a scan-derived asset reproduce a real person, place or protected object?
Rights What may be done with the asset.

Licence and use

The licence and restrictions that apply.

Licence terms

The licence, attribution and use restrictions for the asset and its parts.

  1. Which licence applies to the asset, and does it differ for its textures or parts?
  2. Which attribution and use restrictions must be kept?

Classifiers Filled

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

What it is Filled

A 3D asset or scene is a digital description of three-dimensional content: meshes or other geometry, materials and textures, and a scene graph that places objects, lights and cameras, together with the rights that govern its use. It covers the asset as a media file or package, not the physical object it may represent, a running simulation, or a virtual world that hosts many scenes.

In scope

  • 3D-specific identity binding, geometry, coordinates, appearance, scene composition and authored motion
  • Resource closure, format profiles, conversion-loss and validation evidence for a particular revision
  • Subject-specific provenance, rights targets, sensitive depiction and retirement constraints

Out of scope

  • Generic media identity, rendition storage, creative-work and publication lifecycles remain externally mastered
  • Physical objects, surveying truth, manufacturing instructions, executable simulations, world hosting and renderer implementation
  • Rights adjudication, policy enforcement, license acceptance, external publication, arbitrary script execution or automatic dependency download

Why it exists Filled

Describe one identified 3D media asset or authored scene, its spatial content, dependencies, interpretation profile and evidence for permitted use.

Distinguishing features Filled

  • It is a media asset that can be stored, versioned and licensed, not the physical object it may depict.
  • A scene composes many assets by reference, so its integrity depends on the versions it points to.
  • Distinct from a 2D image or video, which are rendered views rather than navigable geometry.
  • Distinct from a virtual world or simulation, which host scenes and add behaviour over time.

What robots and AI may and may not do Filled

Must not

  • Strip licence, attribution or provenance information from an asset.
  • Publish a scan of a real person or private property without consent.
  • Use an asset beyond the terms of its licence.
  • Present a generated or modified asset as an unaltered scan of a real object.

Only with a human decision

  • Accepting licence terms on behalf of an organization.
  • Publishing scans of people, private interiors or protected heritage objects.

May

  • Inspect and validate assets against their format specification.
  • Convert assets between interchange formats and report what was lost.
  • Record the licence, author and provenance of each asset and its parts.
  • Generate previews and metadata for catalogues.

Moral aspects Filled

  • Scans can capture people's likeness and private spaces without their knowledge.
  • Creators depend on attribution and licence terms that are easily lost in conversion.
  • Realistic synthetic scenes can mislead when presented as records of real places.

Who is affected

  • 3D artists and creators
  • People and owners of places that are scanned
  • Users of products built on the assets

Owners Filled

Steward

The creator or the organization that commissioned the asset answers for its content, provenance and licence.

Roles

Asset custodian
Maintains master asset identity, authoritative content and lawful disposition
Descriptor steward
Maintains 3D descriptors, reference scope and revision consistency
Technical reviewer
Reviews geometry, mappings, conformance reports and declared losses
Clearance reviewer
Records component rights and sensitive-content decisions within delegated authority
Consumer agent
Reads approved views and refuses unsupported or unauthorized processing

Master systems

  • Digital asset management system
  • Version control for asset files
  • Asset marketplace or library catalogue

Links to other meta-models Filled

extends

  • WM-MED-002 - Proposed specialization of the registry parent Media Asset / Rendition. Its master identity, generic revisions and rendition lifecycle remain authoritative. A concrete version binding must be approved before implementation.

references

  • WM-MED-006 - Optional external component asset descriptors, pinned per scene occurrence. Self-model references do not imply recursive containment or permission to change another asset.

aligned

  • glTF 2.0 - Conceptual mapping only. Pin the selected profile and verify losses and required features; no implemented or certified conformance is claimed.
  • OpenUSD scene description - Conceptual mapping only. Pin the selected profile and verify losses and required features; no implemented or certified conformance is claimed.
  • X3D 4.0 - Conceptual mapping only. Pin the selected profile and verify losses and required features; no implemented or certified conformance is claimed.
  • PROV-O - Conceptual mapping only. Pin the selected profile and verify losses and required features; no implemented or certified conformance is claimed.
  • ODRL 2.2 - Conceptual mapping only. Pin the selected profile and verify losses and required features; no implemented or certified conformance is claimed.

neighbor

  • WM-MED-002 Media Asset / Rendition - Registry parent retained as a proposed EXTEND binding. Reuse its master asset and revision identity; this model adds only 3D descriptors and specialized checks. A pinned parent schema is an adoption hold, not a claim of tested inheritance.
  • WM-MED-006 referenced component assets - Scene occurrence identity, component asset identity and payload digest differ. References do not transfer ownership or imply that one scene controls a shared component lifecycle.
  • Physical subject, simulation and rendering services - A depiction is not its real subject. Authored animation and behavior declarations can be catalogued without executing them; runtime state and scheduling remain outside the descriptor.
  • Rights, evidence and production records - Carry scoped references and attributed assertions. A creator, uploader, custodian and rights holder are separate roles; neither a file header nor a digest establishes title or legal permission.

parent

  • WM-MED-002

What else AI and robots need to interact with it Filled

Identity and identifiers required Filled

  • An asset is identified by a repository or library identifier with a version, and often a content hash of its files.
  • Scenes refer to their component assets by path or URI and version.

Direct properties not applicable Not applicable

Not applicable

A 3D asset is digital content; its dimensions and units are data in the file, not physical measurements an agent takes.

Recognition required Filled

  • A 3D asset is recognized by its file format, header and the presence of geometry, materials and scene nodes.
  • Often confused with a rendered image of the scene or with the physical object it models.

Capabilities and actions required Filled

  • Assets can be rendered, converted, optimized, composed into scenes and versioned.
  • Scenes can be loaded by many engines and viewers when a common format is used.

Hazards and failure modes required Filled

  • Licence breach when parts of an asset carry different terms.
  • Malformed or very large files that crash viewers or hide malicious content.
  • Privacy loss when scans reveal people or private spaces.

Standards and interfaces required Filled

  • glTF 2.0, published as ISO/IEC 12113.
  • X3D, ISO/IEC 19775.
  • Universal Scene Description for layered scene composition.

Context of use required Filled

  • Used in games, film, product design, heritage documentation, digital twins and online retail.
  • Copyright and image rights law govern the use of assets and scans.

Sources Filled

  1. glTF 2.0 Specification - Khronos Group
  2. Introduction to USD - OpenUSD contributors
  3. Encoding Stage Linear Units - OpenUSD contributors
  4. X3D Architecture - Concepts - Web3D Consortium
  5. X3D Architecture - Lighting component - Web3D Consortium
  6. PROV-O: The PROV Ontology - World Wide Web Consortium
  7. ODRL Information Model 2.2 - World Wide Web Consortium
  8. glTF-Validator documentation - Khronos Group
  9. ISO/IEC 12113 Runtime 3D asset delivery format - Khronos glTF 2.0 (ISO/IEC)
  10. ISO/IEC 19775-1 Extensible 3D (X3D) Architecture and base components (ISO/IEC)

Open questions

  • Verify source redirects, status, immutable snapshots, exact versions and selected claim support outside the sandbox.
  • Pin and test the media parent and format/consumer profiles with scenes covering mixed metrics, shared resources, missing textures, unsupported features, topology changes and stale clearance.
  • Develop dedicated profiles for advanced geometry, shader graphs, geospatial content and use-specific quality constraints without expanding this model into a runtime engine.
  • Restore independent external review and complete qualified adoption-policy review before canonical promotion.
  • Executable nested instance schemas, inheritance binding and consumer fixtures
  • Full shader graphs, procedural systems, CAD/BIM tolerances, geospatial reference systems, volumetric and neural representations require dedicated profiles
  • Complete format-extension coverage, resource security testing and cross-engine visual equivalence
  • Jurisdiction-specific rights, privacy and retention rules and independent external review

Machine files

Provenance

world-models research · reviewable-draft

Built from: models/wm-med-006-3d-asset-scene/spec.yaml, ver-cy/world-models/card-supplements/wm-med-006-3d-asset-scene.json