# "doc" metadata field removal for schemas?

**URL:** https://forum.aousd.org/t/doc-metadata-field-removal-for-schemas/1825
**Category:** USD
**Created:** [September 4, 2024, 11:52pm UTC](https://forum.aousd.org/t/doc-metadata-field-removal-for-schemas/1825 "2024-09-04T23:52:25Z")
**Posts on this page:** 1
**Showing post:** 2

<div class="post-metadata">

### Author: ![mati-nvidia](https://sea2.discourse-cdn.com/flex016/user_avatar/forum.aousd.org/mati-nvidia/32/18_2.png) [@mati-nvidia](https://forum.aousd.org/u/mati-nvidia)
#### Post date: [September 5, 2024, 3:23am UTC](https://forum.aousd.org/t/doc-metadata-field-removal-for-schemas/1825/2 "2024-09-05T03:23:45Z")

</div>

I thought you outlined a really good plan here: [The purpose of UsdObject's Documentation metadata - #2 by dsyu](https://forum.aousd.org/t/the-purpose-of-usdobjects-documentation-metadata/1403/2)

Sounds like the plan has changed since then? How come?

I think a generalized `doc` metadata to provide asset-specific documentation seems useful. I would personally prefer to see:

1. `doc` and `GetDocumentation()` to be empty by default and repurposed to serve as asset-specific documentation.
2. To have a new API for `userDoc` and `userDocBrief`.

Also `schemaDoc` makes more sense in my mind than `userDoc` for that purpose.

Just my two cents on it. I don’t think we have anything built on this right now, but these were considerations I was making for future ASWF Assets WG contributions.

---

_[View the full topic](https://forum.aousd.org/t/doc-metadata-field-removal-for-schemas/1825)._