RE: Gauge32 as an INDEX (was: Index values of zero)

["C. M. Heard" <heard@pobox.com>]

On Wed, 22 Jan 2003, Wijnen, Bert (Bert) wrote:
> Can we also add here that it would be good practice to document
> in the [DESCRIPTION] clause why a zero value is used and what it
> means in cases wehre it is actually a valid index.

OK, how about this:

   - For integer-valued objects that appear in an INDEX clause or for
     integer-valued TCs that are to be used in an index column:

     - Unsigned32 with a range that excludes zero is RECOMMENDED for
       most index objects.  It is acceptable to include zero in the
       range when it is semantically significant or when it is used as
       the index value for a unique row with special properties.   Such
       usage SHOULD be clearly documented in the DESCRIPTION clause.

     - Integer32 or INTEGER with a non-negative range is acceptable.
       Again, zero SHOULD be excluded from the range except when it is
       semantically significant or when it is used as the index value
       for a unique row with special properties, and in such cases the
       usage SHOULD be clearly documented in the DESCRIPTION clause.

     - Use of Gauge32 is appropriate for index objects that have gauge
       semantics.

//cmh