Factor out representation of values

[GoogleCodeExporter]

Description of the issue

Currently, we have a class Range for ranges of values and associated
ValueType, where the ValueType indicates the datatype (eg., float, int,
time) and units of measure.

Some classes have a hasValue datatype property. In some cases, the class
also has a link to Range (eg., MeasurementCapability). Having two ways to
refer to values looks a bit redundant/unclean.

I'm proposing:

- create a base class TypedValue with property:
  TypedValue hasValueType ValueType

Whenever an entity needs to link to a typed value (be it a single value, a
range of values, or other form of value), it will use a property with range
in TypedValue.

- make Range subclassOf TypedValue (thus inheriting the hasValueType prop)

- create a class SimpleValue as subclass of TypedValue for single-valued cases:
  SimpleValue subclassOf TypedValue
  SimpleValue hasValue string

Original issue reported on code.google.com by caru...@gmail.com on 21 May 2010 at 12:50

[GoogleCodeExporter]

+ class TypedValue --> Done.

+ property TypedValue hasValueType ValueType --> Done.

* make Range subclassOf TypedValue --> Done.

+ class SimpleValue subclassOf TypedValue --> Done.

+ property SimpleValue hasValue Any --> Done.

Use the TypeValue class:

+ property hasTypedValue with range TypedValue and domain the union of the 
following
classes: -- done

    * MeasurementCapability
    * PhysicalProperty
    * EnvironmentalToleranceLimit

* remove explict value-related properties for these as they are subclasses of
PhysicalProperty: -->done

    * Weight -- done
    * Dimension --> done

- remove class MeasurementRange --> done
Rationale: its superclass MeasurementCapability already has a property for the 
value
(which can be a Range, but also other possible kind of value).

Original comment by caru...@gmail.com on 23 May 2010 at 12:36

• Changed state: Done

[GoogleCodeExporter]

Original comment by caru...@gmail.com on 23 May 2010 at 12:46

• Added labels: Change