New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

uri for control vocabulary #2

Open

vturpin opened this issue Oct 10, 2024 · 1 comment

Member

vturpin commented Oct 10, 2024

We do not consider so far the uri of the controlled vocabulary.
I take the exemplar of the sensor model for instance.

Sensor model are controlled by vocabularies (sea "ECO_FLBB2" for instance, desribed here: http://vocab.nerc.ac.uk/collection/R27/current/ECO_FLBB2/)

The sensor model entry should define the entry with uri, that is somehow essential for M2M communication when exist.
The schema: https://github.com/OceanOPS/oceanops-json-standard/blob/main/schemas/sensor.schema.json already indentify places where this information could be stored:

sensor_bodc_id
sensor_link_url
sensor_id

Note that in the case of sensor, serveral entry are "controlled vocabulary" and can be linked to a uri:

sensor_name
sensor_agency
sensor_networks
sensor_types
variable_name

Member Author

vturpin commented Oct 10, 2024

Note that this consideration could/should be applicable to any controlled vocabulary.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment