Make classifier terms consistent in sensorML
Currently we use inconsistent terms for our various actions. Especially it is according to the mount actions (DeviceMountAction on the configurations sensorML, mount for the device event).
The names at the end should be consistent.
Also to mention:
The use of the definition in a term is sometimes confusing. If we point to an entry in a codelist, then the value should match this entry (what kind of generic device action for example).
If the defintion points to a url to describe the entry itself (say longName), then it is more like a class <-> instance relationship. The definition points to a class (longName) and the value to a concrete instance (some name
).
@rainer.haener suggest more the way with a codelist value.