Data Manager - ObservableProperty with parameters - create identifiers for property+parameters

[EnocMartinez]

As a...

instrument integrator / data manager

I want to...

Create standardized identifiers for observable properties which contain not only the variable to be measured (e.g. sea water temperature), but also add relevant information about the context (e.g. measured at 20 m depth) within the identifier itself

So that...

they do not share the exact same identifier, but are still grouped by property. If they have the same identifier (sea_water_temperature) some systems can get "confused" and mix datasets or simply reject new data with the same observable property (e.g. Sensor Observation Service).

Examples:

• An instrument that provides sea water current at different depths.
• Data processed with some relevant parameters, e.g. Sound Pressure Level within 100 and 150 Hz integrated during 60s.

Domain(s)

Ocean observing systems (however it can be applied to any complex observable property, regardless the domain)

Addition Information

Sometimes I use controlled vocabulary links with URL parameters as a workaround:

{property url}?{parameter}={value}{units}

e.g. http://mmisw.org/ont/cf/parameter/sea_water_temperature?depth=20m

However in this example "depth" and "m" can be easily interpreted by humans, but it is not a strong semantic definition. An alternative could be to use vocabularies for "depth" and "meters":

{property url}?{parameter url}={value}{units url}

However the identifiers grows to a huge and ugly url no longer readable by humans:

http://mmisw.org/ont/cf/parameter/sea_water_temperature?http://mmisw.org/ont/cf/parameter/depth
=20http://vocab.nerc.ac.uk/collection/P06/current/ULAA/

[mabablue]

Dear @EnocMartinez could you please check whether the assigned labels fit as use cases for your user story? Please check this table to find a better or additional use case which matches better your user story.

[EnocMartinez]

Dear @mabablue, these labels look fine for this user story.