Re: Document definitions

From: Bill Davidsen (davidsen@tmr.com)
Date: Tue Aug 03 2004 - 10:40:02 CDT


Shmuel (Seymour J.) Metz wrote:
> In <20040801153005.GB17926@dora.tertius.net.au>, on 08/02/2004
> at 01:30 AM, Thorfinn <thorfinn@tertius.net.au> said:
>
>
>>No, just a totally pointless one.
>
>
> Not pointless, because *IF* an RFC is accepted that adds a MIME
> parameter, having the requirement here will allow for a quicker
> phasein.

And if an RFC is accepted which uses some other delimiter then this will
be in the way, and if no future RFC is accepted it will be a useless bit
of requirement for all time.

Sounds like "Field of Dreams" to me, build it and they will come. Put a
hook in the code and someone will do something with it. Bah! Add
requirements when they are requirements.

In addition, it would make future adoption *slower*, because existing
software would be coded to treat it as a comment inducer, and would
never see parameters.

Don't hang useless docoration on an existing header in hopes that it
might be useful.

-- 
    -bill davidsen (davidsen@tmr.com)
"The secret to procrastination is to put things off until the
  last possible moment - but no longer"  -me



This archive was generated by hypermail 2.1.7.