Naming and Paths#
Capability: Naming and Paths (NP)
(Details)
Overview#
The Naming and Paths capability defines requirements for consistent naming conventions and path structures in USD assets. This includes prim naming, file naming, and directory structure requirements to ensure assets are portable, maintainable, and follow industry best practices.
Summary#
This capability establishes standardized naming conventions and path structures for USD assets, ensuring consistency across different environments and platforms. It covers prim naming, file naming, directory organization, and path length limitations.
Granularity#
Prim Level: Individual prim naming conventions
File Level: USD file naming standards
Directory Level: Asset directory structure requirements
Path Level: Path length and character limitations
Requirements#
Tags |
Summary |
Compatibility |
Validator |
|---|---|---|---|
🔑 |
core-usd |
||
🔑 |
core-usd |
||
🔑 |
Asset directories shall use consistent naming and logical organization |
core-usd |
|
🔑 |
core-usd |
||
🔑 |
Assets must follow a specific folder structure with the asset name as the root folder |
core-usd |
|
🔑 |
Asset metadata must be stored in the USD file or a sidecar JSON file |
core-usd |
|
🔑 |
core-usd |
||
🔑 |
All asset, reference, and payload paths must resolve to files that exist |
core-usd |