What fundamental data type in USD is most suitable for representing texture files?

The most suitable USD data type for representing texture files is an asset path . NVIDIA’s Learn OpenUSD glossary defines an asset as a named reusable resource and explicitly includes textures among asset examples. It also explains that USD provides a specialized string type called asset so that attributes and metadata referring to external resources can be identified robustly. In USDA syntax, asset-valued strings are delimited with @, such as @textures/albedo.png@.

Option C is correct because texture files are external resources that should participate in USD’s asset-resolution system. Using an asset path allows the resolver to map the authored identifier to an actual file location, versioned asset, package member, or site-specific storage location. Option A is incorrect because tokens are compact identifiers best suited to enumerated values such as purpose, interpolation, or role-like names. Option B is less appropriate because ordinary strings do not communicate that the value is an external asset dependency requiring resolution. This distinction is essential for interchange, packaging, relocation, and pipeline portability. This aligns with Data Exchange → Asset Paths, Asset Resolution, Texture Dependencies, Sdf Value Types, and External Resource References .