Reading Type of measurements cannot be commodities.

Situation: The definition of saref:hasMeterReadingType is "A relationship identifying the reading type of a measurement (e.g. Water, Gas, Pressure , Energy , Power, etc.)". And SAREF contains the axiom: subClassOf( Device AllValuesFrom(saref:hasMeterReadingType UnionOf (saref:Commodity saref:Property )). However, it is ambiguous to assert that a metering function measures water, electricity, or other commodities, which intrinsically have no unit of measure. It is better to assert that a metering function measures some property.

Proposal: change the definition of saref:hasMeterReadingType to: A relationship that links a Metering Function to the property that it can make measurement of (e.g. Pressure , Energy , Power, etc.). And change the axiom to: subClassOf( saref:Device AllValuesFrom(saref:hasMeterReadingType saref:Property ).

added clarity issue in saref-portal label

saref:hasMeterReadingType is named following bad practice.

the definition is: "A relationship identifying the reading type of a metering function (e.g., Water, Gas, Pressure , Energy , Power, etc.)"

Proposal:

1. delete SensingFunction, MeteringFunction, ActuatingFunction
2. define a codelist for functions kinds, (we love codelists now) that contain sensing, metering, actuating, and others
3. define forFeatureOfInterest (resp. forPropertyOfInterest, resp. forProperty) to link Function to the feature of interets, property of interest, property it senses, meters, actuates, etc.
4. also use these three generic properties to link the device to the feature of interest, property of interest, property it is used for. (they would be super properties of measureProperty and measureFeatureOfInterst, and controlsPRoperty and controlsFeatureOfInterest)

I agree to the proposed changes.

As of SAREF V3.2.1,

1. SensingFunction, MeteringFunction, ActuatingFunction, are deprecated
2. instances of saref:Function are function kinds. sensing, metering, actuating, and others, could be instances of saref:Function.
3. saref:observes and saref:controls can be applied to functions (and other classes)

Proposal for SAREF V4:

1. delete deprecated classes
2. define a couple instances of saref:Function

I move this issue to saref-core, as it isn't related to extensions

moved from saref-portal#15 (moved)

changed milestone to %V4.1.1

added 2 - Needs implementation label

TNO agrees, propose closing.

removed 2 - Needs implementation label

added 5 - Propose closing label