In 2.0, observations come from technicians, lab procedures, and computations as well as instruments - "sensor" is the wrong word for the general concept. Fields: name, code (was method_code), type (was method_type, CV), description, definition (URI, was method_link), and optional sensor_model, sensor_model_manufacturer, sensor_model_definition for actual instruments; drop hard-coded encoding_type. With ProcessingLevel, Method answers "how is this datastream produced" at design time; the transaction FKs answer it per value at runtime.
In 2.0, observations come from technicians, lab procedures, and computations as well as instruments - "sensor" is the wrong word for the general concept. Fields: name, code (was method_code), type (was method_type, CV), description, definition (URI, was method_link), and optional sensor_model, sensor_model_manufacturer, sensor_model_definition for actual instruments; drop hard-coded encoding_type. With ProcessingLevel, Method answers "how is this datastream produced" at design time; the transaction FKs answer it per value at runtime.