Re: [netmod] New Version Notification for draft-kwatsen-netmod-artwork-folding-07.txt

[tom petch <[e-mail]>]

---- Original Message -----
From: "Kent Watsen" <[e-mail]>
Sent: Monday, September 24, 2018 9:49 PM

> Hi Tom,
>
> > I would like a paragraph in this I-D to the effect that editors
should
> > take care of this and that this phenomenon is nothing to do with the
> > technique described here, a sort of non-Applicability statement so
that
> > we do not, in future, get too long lines as
> >
> >      /* optical interface func needs to expand for Fiber Channel,\
> > \ SONET and SDH */
> >
> > instead of turning them into
> >
> >      /* optical interface func needs to expand
> >         for Fiber Channel, SONET and SDH */
>
> Section 4.2 addresses this.  In particular, the last line says:
>
>   As such, it is RECOMMENDED that authors do as much as possible
within
>   the selected format to avoid long lines.
>
> Good enough?

No:-)  The authors of YANG modules seem not to understand that it
applies to them, or incorrectly use the tools that would apply were they
correctly used.  I had in mind something such as

OLD
 [RFC7994][RFC7994]sets out the requirements for plain-text RFCs and
   states that each line of an RFC (and hence of an Internet-Draft) must
   be limited to 72 characters followed by the character sequence that
   denotes an end-of-line (EOL).

NEW
[RFC7994]sets out the requirements for plain-text RFCs and
   states that each line of an RFC (and hence of an Internet-Draft) must
   be limited to 72 characters followed by the character sequence that
   denotes an end-of-line (EOL).  This applies to all of an RFC,
including,
   for example, the comments or description clauses in a YANG module,
   and to artwork.

Not sure why you have [RFC7994] twice.

Tom Petch

> Kent // contributor

>