Agreed to add clarifying text to Part 8.

• Should be a whole number.
• A negative whole number implies precision left of the decimal.
• non-whole numbers would be rounded as usual.

Needs Errata for 1.03 & 1.04

Propose we use this text to replace the current descripton of ValuePrecision:

ValuePrecision specifies the maximum precision that the Server can maintain for the item based on restrictions in the target environment.
ValuePrecision can be used for the following DataTypes:
• For Float, Double, and Decimal values it specifies the number of digits after the decimal place when it is a postivie number. It specifies the number digits to the left of the decimal place which are insignificate when it is a negative number. For example a ValuePercision of -2 specifies that the percision of the Value is to the nearest 100. The ValuePercision should always be a whole number and it shall always be interpreted as a whole number by rounding it to the nearest whole number.
• For DateTime values it indicates the minimum time difference in nanoseconds. For example, a ValuePrecision of 20 000 000 defines a precision of 20 ms. The ValuePercision should always be a positive whole number and it shall always be a postive number which is interpreted as a whole number by rounding it to the nearest whole number.
• ValuePrecision can also be used for other subtypes of Double (like Duration) and other Number subtypes that can be represented by a Double.
The ValuePrecision Property is an approximation that is intended to provide guidance to a Client . A Server is expected to silently round any value with more precision that it supports. This implies that a Client may encounter cases where the value read back from a Server differs from the value that it wrote to the Server. This difference shall be no more than the difference suggested by this Property.

Changed as suggested in release version 1.05.0.
Also updated Errata for 1.03 and 1.04.

Agreed to changes in 1.05 and Errata.