The schema editor has JSON, YAML and Terms tabs. The Terms tab is a very reduced view of the vocabulary bindings.
The separate schema documentation rendering is considerably richer: it lists properties and constraints, expands an allOf so that inherited definitions are visible, and links out to the mapped ontology terms. That rendering is what makes a verbose schema readable, and even a simple shape such as a quantity value is verbose enough to need it.
Suggested: bring the Terms tab up to that rendering, or link through to it, so that a user editing a schema can read it in the same form that a consumer sees.
Raised at the MaterialsCommons WP2 hands-on workshop, 15 September 2026.
The schema editor has JSON, YAML and Terms tabs. The Terms tab is a very reduced view of the vocabulary bindings.
The separate schema documentation rendering is considerably richer: it lists properties and constraints, expands an
allOfso that inherited definitions are visible, and links out to the mapped ontology terms. That rendering is what makes a verbose schema readable, and even a simple shape such as a quantity value is verbose enough to need it.Suggested: bring the Terms tab up to that rendering, or link through to it, so that a user editing a schema can read it in the same form that a consumer sees.
Raised at the MaterialsCommons WP2 hands-on workshop, 15 September 2026.