Units. DegC, Degc90, DEGC ITS90 and so on

[BrianKingNOC]

There is little or no control over PARAMETER_UNITS that DACs can choose

Even if we don't have a NVS controlled vocab, these could be chosen once and used by all vendors.

This would only need to be changed if a new sensor measured a new parameter.

It is possible that one parameter could be reported in different units by different sensors
but there could still be a list of unique units that vendors agree to use from the outset.

[SBS-EREHM]

I think we need a controlled vocabulary solution, but it will be a challenge to make sure that a specific parameter's units are appropriate, e.g., "PARMETER" : "SDN:R25::BACKSCATTERINGMETER_BBP700" has the units "PARAMETER_UNITS": "m-1".

Question: Does the real Argo filechecker already do this? We need to discuss home much of that functionality is duplicated.

Note: The current schema validator and controlled vocab checker is (code/python/ParseValidate.py) was really intended as demo code, rather than the final word.

• Any JSON parser that supports schema validation can check and instance (sensor, platform, or float .json file) against the Schema set.
• Checking of controlled vocab against NVS requires code, currently implemented in ParseValidate.py.
• Checking that the "right" choice ("m-1") is correct for a given parameter ("SDN:R25::BACKSCATTERINGMETER_BBP700") requires even more (currently unwritten) code (whether or not "m-1" is in an NVS controlled vocab)