In other words, records should be returned with information on this field no matter what values are present. The query should be constrained by at least one field. The second list of fields specifically address the secondary use of this resource vocabulary, recording other information that might be useful to the end-user. These fields should be considered non-searchable attributes of the resource. Note that while this vocabulary may define how values and constraints may be represented as text, it does not define how the field itself is represented as this is considered implementation-dependent.
Field names are merely conceptual handles for the given definitions.
Implementations of this vocabulary should define how each field maps to its representation. The name of the organization responsible creating the data. This can be observatory name, mission name, or general project name. The type of organization responsible for creating the data. Meanings of vocabulary terms to be defined.