RE: section 4.6.2 of review-guidelines

["Wijnen, Bert (Bert)" <bwijnen@lucent.com>]

Sometimes it is indeed pretty clear that the text in the 
description clause is redundant. I have seen:

   DESCRIPTION "...
                The default value is zero."
   DEFVAL  { 0 }

That seems pretty redundant to me. I always advise to take that
text out. But (as stated by others), I do not think we need
to force/mandate that. The above is indeed redundant, but there is
no errro/flaw present. So let us not make it a CLR. Just recommend
that they might as well take that text out of the DESCRIPTION clause
(when it is indeed clearly redundant).

Thanks,
Bert 

> -----Original Message-----
> From: Harrie Hazewinkel [mailto:harrie@lisanza.net]
> Sent: zaterdag 5 juni 2004 16:30
> To: Mreview
> Cc: Harrie Hazewinkel
> Subject: section 4.6.2 of review-guidelines
> 
> 
> HI,
> 
> I was wondering what others think of the following.
> It maybe is a little subjective, since I mentioned it
> sometimes in reveiws but is not really incorrect.
> 
> The issue is that I sometimes have noticed that in the
> DESCRPTION clause a textual equivalent of for instance the
> DEFVAL-clause, or UNITS is given.
> I personally dislike this, since it for of all MUST go
> into a DEFVAL-clause or UNITS-clause and as a result
> is redundant. Therfore, I beleive we should
> add some text in section 4.6.2 regarding this.
> 
> I understand it may be seen as a CLR, but then again
> an editor simply creates himself more work by adding
> the textual information that is/must be part in the
> FORMAL clauses.
> 
> 
> 
> Harrie
> 
>