You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I've realized that our approach to defining controlled vocabulary in the format is a bit unclear, particularly in relation to the NVS (NERC Vocabulary Server). The NVS provides a "concept name," an alternative label, and a definition. For example, see this link.
How do we incorporate these elements into our format descriptions, where we use variable/attribute names, long_names, and standard_names?
Do we map elements between NVS and OG1.0? Do we follow conventions for some and leave flexibility for others?
I believe this is a topic worth discussing for clarification and alignment. It's not urgent, but having an agreement and documenting it somewhere would be beneficial.
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
Uh oh!
There was an error while loading. Please reload this page.
-
Hi,
I've realized that our approach to defining controlled vocabulary in the format is a bit unclear, particularly in relation to the NVS (NERC Vocabulary Server). The NVS provides a "concept name," an alternative label, and a definition. For example, see this link.
How do we incorporate these elements into our format descriptions, where we use variable/attribute names, long_names, and standard_names?
Do we map elements between NVS and OG1.0? Do we follow conventions for some and leave flexibility for others?
I believe this is a topic worth discussing for clarification and alignment. It's not urgent, but having an agreement and documenting it somewhere would be beneficial.
Beta Was this translation helpful? Give feedback.
All reactions