# Edge cases in the proposal for Variant Set Metadata

**URL:** <https://forum.aousd.org/t/edge-cases-in-the-proposal-for-variant-set-metadata/2173>\
**Category:** USD\
**Created:** [January 27, 2025, 7:47pm UTC](https://forum.aousd.org/t/edge-cases-in-the-proposal-for-variant-set-metadata/2173 "2025-01-27T19:47:25Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![ThomasKumlehn](https://avatars.discourse-cdn.com/v4/letter/t/ce7236/32.png) [@ThomasKumlehn](https://forum.aousd.org/u/ThomasKumlehn)\
**Post date:** [January 27, 2025, 7:47pm UTC](https://forum.aousd.org/t/edge-cases-in-the-proposal-for-variant-set-metadata/2173/1 "2025-01-27T19:47:25Z")

</div>

Since the proposed new way would add an optional dictionary `variantDisplayNames` to a `variantSet` s meta data, would this mean another variantSet on the same prim could over it’s (not yet set) content for different languages?  
Also this could tamper with displayGroup and other UI related meta data.

Please either warn about doing so, and/or make UI developers aware of possible unexpected mutations.

As a developer from Europe, I’m very much interested in localized UI texts for end users (think AR Quick Look assets)

@nvmkuruc

---

<div class="post-metadata">

**Author:** ![nvmkuruc](https://avatars.discourse-cdn.com/v4/letter/n/76d3ee/32.png) [@nvmkuruc](https://forum.aousd.org/u/nvmkuruc)\
**Post date:** [February 4, 2025, 8:59pm UTC](https://forum.aousd.org/t/edge-cases-in-the-proposal-for-variant-set-metadata/2173/2 "2025-02-04T20:59:30Z")

</div>

Thanks Thomas. We should certainly add it to the set of test cases to make sure things behave as expected.

Whether or not a variant could override a sibling variant set’s fields would not be changed by the proposal and I think is just dependent on the ordering of the variantSets. Right now in the internal object model, the only field a `variantSet` contains is `variantNames`.