General Conceptual Data Mapping Guidance

Document Versioning

The conceptual data mapping document is a living document that should serve as a single source of truth for stakeholders. The document should be kept up-to-date with changes to:

1. The source data format

2. OpenUSD

3. An official data mapping implementation

We recommend using a document version and last revision date to keep track of any updates to the document. Previous versions of the document can be archived for reference for older versions of the software, but there should be one current version, typically associated with the latest release of the official data mapping implementation.

Asset Structuring

Conceptual data mapping’s goal is to produce a high fidelity translation that is faithful to the source data format. Directly mapping data from the source ensures clarity for developers and end users, making the OpenUSD output closely resemble their original content in the DCC. NVIDIA’s published reference documentation outlines best practices for structuring assets. It provides a framework for creating and evaluating asset structures based on four principles: Legibility, Modularity, Performance, and Navigability. It is useful to learn about these principles, but also understand that these principles may be prioritized or valued differently across organizations. There isn’t a one-size-fits-all solution. Therefore for ISVs, we recommend prioritizing Legibility and Navigability with a direct mapping. This makes it approachable for third-party developers to focus on the last mile and adapt the output OpenUSD data via post-processing (e.g. with a script or export hook) to suit their organization or client’s preferred asset structure.